im trying several different roms and both of which have resulted in the splash logo and nothing else, it just hangs there. one of the roms was the kingkkklair droid eris2 g1 and i followed all of the directions it just didnt work. please help!
Could you share more info?
What phone do you have?
What radio/spl?
Are you sure you read and followed instructions?
are you sure you posted this in the right section?
turn the phone off, restart it by pressing back and power together and tell us the version information. most likely you have a 32a and you're trying to install roms for 32b or vice versa...
Not ROM Development related.
Moved to General.
Reziukas said:
Could you share more info?
What phone do you have?
What radio/spl?
Are you sure you read and followed instructions?
Click to expand...
Click to collapse
By viewing his recent posts, it appears that he is using a MyTouch 1.2 device.
ref: http://forum.xda-developers.com/showthread.php?p=5782312#post5782312
OP, you need to wipe before flashing any rom.
Please provide SPL, Radio versions as well as ext partition type (ext2, ext3, ext4) as well as rom details.
Bonus points if you can provide a logcat from ddms.bat and use pastebin.com to provide it to us.
My theory, the wrong ext paritition is being used. Some SenseUI roms require an ext3 partition.
Or...
A wipe of data, dalvik-cache, ext partition is likely needed.
no i have a 32b phone im sure, i got rid of that other phone and now have this one. my radio is 2.22.19.261 and my hboot is 1.33.0006. i followed the directions exactly and the roms are not working at all. here is the link to the rom please help me out. http://forum.xda-developers.com/showthread.php?t=644275&highlight=kingklick
I think i found out the problem. It said i need the latest radio, whatever that is. do you know what the latest radio for the mytouch is?
metaltorizo said:
I think i found out the problem. It said i need the latest radio, whatever that is. do you know what the latest radio for the mytouch is?
Click to expand...
Click to collapse
I'm pretty sure it's 2.22.23.02 but your current radio should work too (i think).
Do you have an ext partition?
If yes, what kind?
If yes, did you wipe the entire partition?
If no to either question, that's likely your problem.
Did you wipe your data?
If no that's likely your problem.
Do you know how to use logcat?
If yes then give us a logcat of what is going on while your phone tries to boot.
If no then use the command prompt and type 'adb shell logcat' wiith your phone connected to your pc.
Can you use other roms?
If yes then which ones have you tried?
If no then try different versions (preferably that don't have special requirements such as spl, ext partitions, swap, etc.
And check here if it's an issue with rooting your device.
http://forum.xda-developers.com/showthread.php?t=551920&highlight=click+root
I think that applies to your specifications.
Also try asking in that particular thread too. More than likely someone else in that thread has your same configuration and can give you more advice.
In all honesty, if you can flash other roms and are just busting your butt just to flash a Sense UI rom, you will be inevitably disappointed. They are fun at first but later on during the day you will probably become frustrated. MyTouch devices were not made to support the Sense UI interface. All devices that have Sense UI (aka Rosie, aka Hero) have at least twice the ram, faster cpu and more rom space. It'll be like installing Vista on a Pentium 2 computer with only 64mb of ram (just an example). Even if you could get it to work, it will eventually start running like dirt. It's not 100% stable or functional. The lack of bluetooth is an ongoing issue that most developers had pretty much given up on. So basically you are posting several threads and spending countless hours trying to get a rom flashed on your phone that will have no bluetooth and in a matter of hours will only provide slow constant and slow reloading with an occasional lockup/freeze/reboot. And I know that you're thinking 'But it looks really neat!' Really... stability and functionality will always win over eye candy. So go through the trouble, experiment with it if you wish but in a few days time you will be wanting to flash a more stable rom and all of this trouble that you are going through will be for nothing. Just my advice though.
Good luck.
Yes, i had a ext4 partition, and i did a full wipe before flashing. how do you delete the entire ext partition?
metaltorizo said:
Yes, i had a ext4 partition, and i did a full wipe before flashing. how do you delete the entire ext partition?
Click to expand...
Click to collapse
Wipe it from Recovery.
Depending on what rom and what recovery you are using you can just
cd /sd-ext (for Cyanogen 5.0.7+ roms)
cd /system/sd for most other roms (older roms)
then rm -r *
Related
Maybe I'm more of a noob than I thought.
I bought a vanilla G1 on 1.5 locked to T-Mobile.
Unlocked it so I could use it on 3, no troubles there.
What I want to do is get 2.2 Froyo running, with ElegantSteel theme. Obviously the latter is more of a want, and I'm more concerned with just getting a working 2.2 on my device.
If someone could help me, tell me what I'm doing wrong that'd be great, what I've tried is below.
I installed HardSPL, so I'm now 10.95.3000
Believed I had rooted it.. I did the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
However, it gave no real indication that anything was working, I just trusted, as I have no real past experience with Android.
So I tried several times to flash different ROMs, to no avail. Each time it returns:
Installing from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
Every time. With several different ROM's. Is the problem that I didn't root properly or what?
Thanks in advance for your time reading and helping,
Fordy.
There are several things which might cause, that your flashing fails:
1) amon-ra-1.5.2 is a bit old, should not have directly influence on flashing, but if you want to use the custom-mtd method, and you have to
2) HardSPL is providing only the standard partition layout of the phones flash memory, i.e. a /system partition of about 70MB which is not enough to flash a FroYo-ROM. To change this, you have to apply Firerat's custom-mtd patch, which enables you to change the layout as you want.
Below in my signature you can find the appropiate links. I suggest to you, to read these threads, especially the OPs. Than you will be able to prepare your phone in a wys, that flashing a FroYo rom should work.
Thanks so much for the reply.
I will check that out, however, since my post I have also tried ClockMod & 1.7 images, as well as DangerSPL.
Despite upgrading radio to 2.x DangerSPL seemed to temporarily brick my phone, and I had to reflash the .nbh to get it running again.
I don't know if that makes any difference to your response? (Ie. DangerSPL doesn't have the same 70MB limit maybe, and therefore that's not the cause, I don't know.)
Thanks again, I'l read up on your links anyway so if that is still correct to do, I'll know what I'm doing.
I'm not entirely convinced it is rooted..
Every time I reflash I have to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
again, which I thought wasn't necessary? I also have to re "enter, enter, telnetd, enter" before I can connect to localhost.
And once I have, if I type "su" it simply says:
su: not found
# #
And it shouldn't say "not found" - correct?
I don't understand what I've done wrong.
Also, how can I backup so that if it fails again, I don't have to keep running through initial setup everytime I reflash?
So if I flash HardSPL as update.zip again, and then is this FireRat also an update.zip job, after the SPL?
And then I can continue as I did?
Thanks, Fordy.
F***.
Never mind.
I bricked it. Good and proper.
No getting past T-Mob splash, no recover, no nothing.
£93 down the drain. S***.
Sad to hear, that you bricked your phone, but that was most likely due to flashing DangerSPL. Reading the MTD-post you would have seen, that DangerSPL is never(!) needed.
One advice to all you guys starting to root your phones and flashing custom-roms: Read first, if you are unsure ask, read again and then flash ...
Sent from my Htcclay's Superfly G1 BTX using XDA App
I did indeed flash Danger, bt that didn't brick it.
Or rather, it was recoverable. It just wouldn't boot. I could get into recovery and fastboot etc. and just reflashed the .nbh
The second time however, was even more stupid, I decided the custom MTD looked to fiddly, and just followed a easy to follow guide by KenMood, which said the 2005 SPL was necessary.
I'd read elsewhere that 2005 should never be used, as it as high brick rate and doesn't offer anything over the 2003, so I downloaded and flashed a Haykuro SPL - that, I believe, is where I was stupid.
Ah well.
I'll sell it for parts on eBay, and pick up another. It's a worthwhile experience I guess, just costly.
If you use HardSPL and an MTD patch - is there any danger of bricking it? I'm much more wary now, as I don't want to waste two.
So if I get another..:
1) Revert to RC7 with DREAIMG.nbh
2) Root and install Recovery.img in telnet
3) Upgrade radio to -what?-
4) Flash HardSPL? -which one?, link?-
5) Flash MTD patch -link?-
6) Flash 2.2 ROM -which one? CM 6.0 work ok despite the wiki requiring Danger?-
I think I mucked up last time around because I had so many guides open, with none of them completely relevant to me, I was trying to mix and match thebits that I thought were relevant. I obviously got it wrong.
If you could fill the gaps (Links to correct radio, SPL, MTD patch, ROM) and verify that the order there is correct, and I havn't missed anything, that'd be fantastic. I really want a working 2.2 G1, but don't want to brick another.
Thanks,
Fordy.
F012DY said:
I did indeed flash Danger, bt that didn't brick it.
Or rather, it was recoverable. It just wouldn't boot. I could get into recovery and fastboot etc. and just reflashed the .nbh
The second time however, was even more stupid, I decided the custom MTD looked to fiddly, and just followed a easy to follow guide by KenMood, which said the 2005 SPL was necessary.
I'd read elsewhere that 2005 should never be used, as it as high brick rate and doesn't offer anything over the 2003, so I downloaded and flashed a Haykuro SPL - that, I believe, is where I was stupid.
Ah well.
I'll sell it for parts on eBay, and pick up another. It's a worthwhile experience I guess, just costly.
If you use HardSPL and an MTD patch - is there any danger of bricking it? I'm much more wary now, as I don't want to waste two.
So if I get another..:
1) Revert to RC7 with DREAIMG.nbh
2) Root and install Recovery.img in telnet
3) Upgrade radio to -what?-
4) Flash HardSPL? -which one?, link?-
5) Flash MTD patch -link?-
6) Flash 2.2 ROM -which one? CM 6.0 work ok despite the wiki requiring Danger?-
I think I mucked up last time around because I had so many guides open, with none of them completely relevant to me, I was trying to mix and match thebits that I thought were relevant. I obviously got it wrong.
If you could fill the gaps (Links to correct radio, SPL, MTD patch, ROM) and verify that the order there is correct, and I havn't missed anything, that'd be fantastic. I really want a working 2.2 G1, but don't want to brick another.
Thanks,
Fordy.
Click to expand...
Click to collapse
The first two steps I've never done because I used the 1-click method, but it seems ok for me. Probably somebody else can confirm these steps.
The other steps are as you described (all information is available in my signature), but here again in more detail:
3) Upgrade radio to 2.22.23.02 You find it on Post #76
4) Flash SPL? 1.33.2003, available in the same thread and same Post as above
5) Flash MTD patch described here
6) Flash 2.2 ROM : Depends on you, what you want to have. CM6 will work fine, also each other FroYo-ROM, but remember using the mtd-patch
Have been trying my best to figure this out, but so many steps. Lame I know but...
I've got a Rogers 32A SPL 1.33.0010 SAPP50000 3.22.20.17. After buying it used with a Hero ROM almost a year ago, I managed to flash CM6-FroyoRedux-1.6-32a which worked (great!) for almost a year. Lately it has been getting really flakey with lots of FC and problems connecting to wifi.
So I thought a re-flash of ROM should fix things up. No luck, same problems. Super flakey, lots of FC (even with base install). Does that mean I have a hw problem?
So thought I would try another more up to date ROM. Tried CyanogenCARZ-7.1.0... and Ginger Yosi 1.2.1 and a few other but none would flash properly (Recovery on the phone is ClockworkMod Recovery v2.5.0.1 - is that the problem? If so can anyone direct me to easy steps to change this? Found some others but me to dumb, or they to hard to follow b/c no luck. I have done ROM messing about for years, more recently with Dell Streak, but it seemed to be much easier.)
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Where should I go from here?
Thanks for your help, and sorry for being so dumb.
Don't worry, it's natural to have questions whwn confronted with such a confusing phone. I would recommend going to the RUU sticky in the development section, and flashing back to stock. If you still gets fcs and the like on stock, it is likely a hardware issue. Otherwise, we can just reroot and flash another custom rom. Let me know how it goes!
Sent from my Sapphire/dream using XDA App
What you need is a simple (full)wipe.
The problem when applying new roms or re-flashing the same rom is that the userdata and cache partitions are not cleaned.
Userdata = all the app and settings you have accumulated through the years.
Cache = as the name says.
When the partitions are not wiped, then complication can and most likely will occur when (re)flashing roms.
So, inside the recovery, chose to wipe all the partition you can find. Then you flash the rom you want. Wait 5-15 min for it to load and you should be good to go.
paulheth said:
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Click to expand...
Click to collapse
Rooted = have SU binaries... my guess = YES you are rooted.
Perfect SPL does not influence rom flashing since you are working from recovery.
If you are flashing from fastboot, then SPL will have a dominant position.
Looking more like hardware.
Seems it may be a hardware issue? Even with the stock RUU rom from HTC there are still sim recognition and wifi flakiness issues.
Any chance a radio re-flash/update would help?
Please, dear XDA'ers, take a little bit of time apart for a newbie at rooting. :l
I'm an Annoying Noob to you, as you probably already guessed. But I made this account, because I want to root my phone to Android gingerbread, with a -STABLE- sense (2.1+)3.0 UI.
So I had my eyes on THIS one: http://forum.xda-developers.com/showthread.php?t=1038694
BUT! I'm REALLY a noob at rooting. I've tried HaRET rooting, with a Nexus android Rrom, well... That didn't go too well, because via my SD things would become veeeery slow after a while. So I NAND rooted my phone to Android Gingerbread 2.3.3. I'm quiete happy with it, but it's not really the HTC feeling I get when I look at the UI.
So I saw sense 3.0 and fell in love.
Well enough about that. I have an HTC HD 2, it's NAND rooted and it's European... ALL I want is a STABLE sense 3.0 rom... That works for my phone.
Now I was wondering, if I would instal it... Would it work properly for me? None of us are sure. So that's why I want to back-up my ROM. With Clockwork rom recovery tool... you know, from the market. Well I get a very annoying error every time I try to back-up my data. I did flash the app to it's most current version, but when I want to make a back-up, my phone just reboots... and does... basically, nothing.
I don't want to mess up my phone entirely. So what should I do first, dear XDA'ers? Please, I just don't want my data to get lost. I tried multiple tutorials but none seem to have the answer to my problem!
sense 2.1 and sense 3 roms aren't stable yet. they have graphic glitches and camcorder problems. but if you don't consider these problems you can live with it. i may recommend http://forum.xda-developers.com/showthread.php?t=1075703 and http://forum.xda-developers.com/showthread.php?t=1124757. in order to prepare your phone for different nand roms you ca use http://forum.xda-developers.com/showthread.php?t=1090783.
mutil said:
sense 2.1 and sense 3 roms aren't stable yet. they have graphic glitches and camcorder problems. but if you don't consider these problems you can live with it. i may recommend http://forum.xda-developers.com/showthread.php?t=1075703 and http://forum.xda-developers.com/showthread.php?t=1124757. in order to prepare your phone for different nand roms you ca use http://forum.xda-developers.com/showthread.php?t=1090783.
Click to expand...
Click to collapse
I will try this, and if I can't figure it out I will come back to this thread and whine more.
In any case, I think it's appropriate to thank you, it's the least I can do.
btw i think your phone has hspl 2.08 and mgldr?!
rom manager dont work with magldr.
To make a backup boot into cwm manually:
hold power down while rebooting -> magldr screen should appear
Then navigate to ad recovery-> backup and restore..rest should be clear.
..i wonder, how you installed nand roms, without to know how to boot to recovery? oO
j4n87 said:
rom manager dont work with magldr.
To make a backup boot into cwm manually:
hold power down while rebooting -> magldr screen should appear
Then navigate to ad recovery-> backup and restore..rest should be clear.
..i wonder, how you installed nand roms, without to know how to boot to recovery? oO
Click to expand...
Click to collapse
I just raped my phone I think. I had HSPL installed, and MAGLDR and I think some other stuff too, so I used the first rom the first poster linked, and I downloaden the two files it told me to download in the instructions... I installed the custom RUU from that first rom, and then my phone kinda died. It only said "HTC" in green, and it diidn't do anything. So I flashed it back to WinMob 6.5. Now I have WinMob 6.5 (rom 1.66 or something I think) and I'm not sure what to do next. I don't want to brick my phone and I don't want WinMob 6.5 either.
*Sigh* I wonder if I'll ever understand rooting.
So just to clarify, I have HSPL (I'm sure it's the correct one too.) And I have MAGLDR installed on my phone. And I don't get the instructions from said thread.
<_> My brain is molten.
if you have come until mgldr don't give up. download the nand tool kit i mentioned a few posts before.choose and download a simple rom for beginning (you may take tyweens typhoon) put it in your sd. after that you will take a few steps. don't be afraid,many people (including me) faced same problems.
mutil said:
if you have come until mgldr don't give up. download the nand tool kit i mentioned a few posts before.choose and download a simple rom for beginning (you may take tyweens typhoon) put it in your sd. after that you will take a few steps. don't be afraid,many people (including me) faced same problems.
Click to expand...
Click to collapse
Thing is, I don't want a simple rom... I'm stubborn like that, hehehe...
I want a sense 3.0 rom, but I'm not sure how to follow the instructions in the thread. It uses terms I've never heard from before...
Well, if there's a stable android 2.3.3/2.3.4 rom with sense 2.1, I'd consider that! Also, I hate the MAGLDR boot screen... you know, "Go go go!" I saw a rom with a very smooth and pretty boot screen... I'd try that too!
i just say if you can succeed to flash one, then you will learn the steps. after that you can try a different rom everyday,as i do
mutil said:
i just say if you can succeed to flash one, then you will learn the steps. after that you can try a different rom everyday,as i do
Click to expand...
Click to collapse
I will, hahaha. I just want my phone to be a real HTC phone, so I'm looking for a rom that actually has sense... If you have a suggestion...?
since your hd2 is eu, you should also use sd-ext partition have you done this?
mutil said:
since your hd2 is eu, you should also use sd-ext partition have you done this?
Click to expand...
Click to collapse
Yes, I have. I made a 2 gig EXT-4 partition. I just don't know what to do with it. I have Radio Leo installed, MAGLDR, HSPL... CWM and all that.
I tried flashing the two roms you suggested in your first post but they are stuck on the boot screen. I don't know what I'm doing wrong...
have you made necessary cwm partitions using usb flasher and nand toolkit?
and how did you make a 2 gb ext4 partition
okay, I might be a newb here, but i see something's wrong with energie rom's connectivity. I've moved from winmo, did everything under instructions, rom booted, no data connection, no wifi connectivity - the router is in the same room as the phone, but wifi network is not detected. Any ideas where's the problem? thx in advance.
xdakilas said:
okay, I might be a newb here, but i see something's wrong with energie rom's connectivity. I've moved from winmo, did everything under instructions, rom booted, no data connection, no wifi connectivity - the router is in the same room as the phone, but wifi network is not detected. Any ideas where's the problem? thx in advance.
Click to expand...
Click to collapse
Well that's strange since they all work, is this the first rom you used from winmo, or did you try out the CM7or other non-sense roms and did the connectivity work? If this is the first after winmo then use another rom, i suggest a CM7 http://forum.xda-developers.com/showthread.php?t=933951. However if you already tried out other roms and they work previously, then a re-installation might be in the offing. Hope this helps.
Try this rom if u love sense on the Mighty HD.... http://forum.xda-developers.com/showthread.php?t=1769081
fsxpilipinas said:
Well that's strange since they all work, is this the first rom you used from winmo, or did you try out the CM7or other non-sense roms and did the connectivity work? If this is the first after winmo then use another rom, i suggest a CM7 http://forum.xda-developers.com/showthread.php?t=933951. However if you already tried out other roms and they work previously, then a re-installation might be in the offing. Hope this helps.
Try this rom if u love sense on the Mighty HD.... http://forum.xda-developers.com/showthread.php?t=1769081
Click to expand...
Click to collapse
thx,
i've tried reflashing radio to one lower version, than 2.15.50.14, didn't work. Then downloaded Mighty HD, but haven't tried yet, since i'm trying to uderstand the partitioning instructions in that thread, but I will try this rom first, then cm7, if unlucky with sense rom and write it back
Its always good practice to start from the beginning for a rom to work well besides the tremendous write-up, usually all are stated in the OP of the dev.. You encounter less problems with the CM and MIUI roms in installation, but the sense roms need a lot of patience. A Tmous definitely has a different setup procedure in the Enegy Rom than an EU due to differences in file layout blah blah blah. I'll just sum up my installation procedure of Team Blue Droid Sense Rom linked in my last post. (I know its stated in the dev's OP but detailing it a little).
1. My HD2 at least 50percent charged or fully charged (recommended) if I miss something you have a lot of backup power for another try.
2. Entered the tricolor Flash Screen first then plugged the USB cable.
3. Then opened as administrator HD Toolkit (ksubedi).
a. Task29 (a minute or so) then pressed volume down as soon as it rebooted to return to the tricolor screen
b. Flash chosen radio (in my case 2.07.50.27_2) I know its old but works fine and battery friendly.:laugh: [Just remember should have50 in Tmous]:good: (takes around 2 to 3 minutes).... back to the tricolor.
c. Installed MGLDR (less than a minute) and pressed the power button upon reboot and released it when the MGLDR choices appear.
d. Went to USB flasher, partitioned 250mb and 7mb for the rom on Tmous as stated by the dev. Partition completed in a minute or so.
e. Back to MGLDR, went to AD Recovery. CWM loads... Wipe as stated in dev's OP. You may create sd-extension in CWM..advanced..set partition.. usually 1024, but 2048 and 0 swap for this rom since it will load files in there around 450mb I guess so that you have more space for apps. [my case i have 1.5GB ext4 set through mini partition tool].
---at this point power down, remove sdcard and copy ROM zip file to the sdcard. Boot to CWM and install the rom. Do not reboot upon completion, power down your HD2. Remove the battery and put it back and PowerUp. [The last statement is just for luck...]
---This is where you have to be patient.. wait. (If it doesn't boot after 15minutes, remove battery and boot again).
Success stories on rom installation is a matter of patience and searching and reading (a lot!). There's no perfect rom but you can try all of them, thanks to the devs of the HD2. So far Sundawg's sense makes sense for me. For an aging unit we cannot get all we want anymore yet it survives and its CLASSIC! (For this rom just use two panels adding more panels eats RAM. Since this is for daily use, install only the apps you really need..) Thanks hope this helps.
So I managed to get the stock froyo desire ROM installed. All of a sudden my phone wont get data, I did the apn fix I found, my phone also wont load any of my tmobile information and the charger keeps charging and then stops charging and the phone feels real choppy. I'm new to this phone, and use to others where you simply root, install recovery, rom and be done. I'm reverting back to stock win 6.5, which method would be the most popular and stable for installing android?
Nickdroid86 said:
So I managed to get the stock froyo desire ROM installed. All of a sudden my phone wont get data, I did the apn fix I found, my phone also wont load any of my tmobile information and the charger keeps charging and then stops charging and the phone feels real choppy. I'm new to this phone, and use to others where you simply root, install recovery, rom and be done. I'm reverting back to stock win 6.5, which method would be the most popular and stable for installing android?
Click to expand...
Click to collapse
Why would you possibly use the stock Desire ROM? It's so outdated, it was really just a proof of concept. It isn't even rooted. Find a ROM you like, then flash CWM (with the correct partition size as per the ROM you chose) and then the ROM with any addons you choose. There are tonnes of detailed guides, use search .
this is the thing that confuses me, I actually downloaded the NexusHD2 Rom, but I couldn't figure out how to install it, I don't think I had a recovery unless the magdlr is the recover(?) Also I was under the impression from what I read that when you download a rom on the computer it comes with an installer built in .DAF or something like that? It was just your average .zip rom, which I got from the NAND development section. I'm so confused with this phone lol. I'm so use to the basic android root and rom and all that. Is magldr the way to go? I want a way thats got a lot of development and stable roms.
Nickdroid86 said:
this is the thing that confuses me, I actually downloaded the NexusHD2 Rom, but I couldn't figure out how to install it, I don't think I had a recovery unless the magdlr is the recover(?) Also I was under the impression from what I read that when you download a rom on the computer it comes with an installer built in .DAF or something like that? It was just your average .zip rom, which I got from the NAND development section. I'm so confused with this phone lol. I'm so use to the basic android root and rom and all that. Is magldr the way to go? I want a way thats got a lot of development and stable roms.
Click to expand...
Click to collapse
This phone isn't complicated, you're just not reading properly In terms of ROMs, once again the Stock Desire ROM is the only exception to the trend, but all other ROMs are flashed via CWM. Read the guide in my sig and it should be fairly clear, if it isn't then you probably shouldn't be flashing anything at all. The outline is:
1. HSPL
2. Radio version 2.08.50 or above (I think. Best solution if you aren't sure is to flash 2.15.50.14).
3. MAGLDR 1.13
4. (step you seem to be confused about) CWM with correct partition size for the ROM
5. (optional) Repartition for A2SD
6. ROM (as a .zip, like any other Android phone)
7. Any extras you may want to flash e.g. Kernels, tweaks, GApps etc.
Nigeldg said:
This phone isn't complicated, you're just not reading properly In terms of ROMs, once again the Stock Desire ROM is the only exception to the trend, but all other ROMs are flashed via CWM. Read the guide in my sig and it should be fairly clear, if it isn't then you probably shouldn't be flashing anything at all. The outline is:
1. HSPL
2. Radio version 2.08.50 or above (I think. Best solution if you aren't sure is to flash 2.15.50.14).
3. MAGLDR 1.13
4. (step you seem to be confused about) CWM with correct partition size for the ROM
5. (optional) Repartition for A2SD
6. ROM (as a .zip, like any other Android phone)
7. Any extras you may want to flash e.g. Kernels, tweaks, GApps etc.
Click to expand...
Click to collapse
Not to sound rude, but I'm not stupid, I've rooted over 50 of my personal android phone since the Eris was brand new, I'm not a newb, but this hd2 thing use to be much different back in 09 when it came out.
I did skip the recovery step and the partition. I'm installing nexushd2 2.7 now. I saw the 4.1.1 version was just released, I'll have to check that out now.
Nickdroid86 said:
Not to sound rude, but I'm not stupid, I've rooted over 50 of my personal android phone since the Eris was brand new, I'm not a newb, but this hd2 thing use to be much different back in 09 when it came out.
Click to expand...
Click to collapse
Oh sorry, I didn't mean that. I just meant that a little in depth reading goes a long way. I'm sure you're perfectly capable of flashing things and yes the HD2 is different but it's genuinely just as easy if not easier than flashing other phones. Having said that, the only other phone I've flashed is my Dad's SGS3 which was pretty much as easy as the HD2. The reason I think the HD2 is better/easier is that there's pretty much no common way that I know of of bricking an EU HD2. Obviously sometimes people just get bad flashes or through years of flashing get bad blocks, but normally people are fine no matter what they do (within reason of course).
Nigeldg said:
Oh sorry, I didn't mean that. I just meant that a little in depth reading goes a long way. I'm sure you're perfectly capable of flashing things and yes the HD2 is different but it's genuinely just as easy if not easier than flashing other phones. Having said that, the only other phone I've flashed is my Dad's SGS3 which was pretty much as easy as the HD2. The reason I think the HD2 is better/easier is that there's pretty much no common way that I know of of bricking an EU HD2. Obviously sometimes people just get bad flashes or through years of flashing get bad blocks, but normally people are fine no matter what they do (within reason of course).
Click to expand...
Click to collapse
I thanked your other post, I'm so far successfully booting ICS now on my hd2.
Glad to hear it