HAHAHAHAHAHAHAHAHAHAHAHAHA ohhhhhh sooo late.....I'm surprised that they even bothered with our phone!
http://www.xda-developers.com/andro...cha-aria-droid-incredible-status-t-mobile-g2/
http://www.htcdev.com/bootloader/
It's nice of them though!
It's still a big deal. Even though AlphaRevX/Revolutionary have been pretty reliable, there's always a risk of bricking the device when using them. It also shows they were serious about their commitment to no longer lock bootloaders and increases the chances of me buying an HTC phone in the future.
Oh I would totally buy another HTC phone...very well built phones! And I did say that it was nice of them....I am glad that they are following through with their word. I just am pretty surprised that they actually bothered with the Aria....
does this affect S-OFF / S-On NAND-lock etc?
I believe the phone will still be S-ON that's why revolutionary.io is still the best bet
Has anyone tried this yet?
Sent from my Liberty using XDA App
I tried this out on my spare Aria. After unlocking it, the phone still says "S-ON" on the HBOOT screen -- HOWEVER -- I was able to install CWM using this method, and after installing a rooted ROM, I was able to write to the system partition while booted. In other words, even though it still says S-ON, it appears to actually be S-OFF.
I think that with HTCdev bootloader unlock you can't flash radios or hboots.
You can write to the system partition, root, change rom, flash recovery but it's not S-OFF.
drumist said:
It's still a big deal. Even though AlphaRevX/Revolutionary have been pretty reliable, there's always a risk of bricking the device when using them.
Click to expand...
Click to collapse
Bull****. There is as much risk using HTC's unlock scheme as there is using Revolutionary.
Further, HTC's unlock scheme is gimped - not flashing custom roms completely in CWM, you need to use fastboot to flash the boot image. The radio partition is locked, and it's definitely not S-OFF.
Revolutionary is the far better way to go, no matter how you look at it.
attn1 said:
Further, HTC's unlock scheme is gimped - not flashing custom roms completely in CWM, you need to use fastboot to flash the boot image.
Click to expand...
Click to collapse
Are you sure about that? I have two Arias, one with S-OFF via AlphaRevX and another that I upgraded to HBOOT 1.03 and unlocked using HTC's tool. Using your build of CWM 5.0.2.3 on both. I installed CM7 on both phones and I don't notice any problems with the phone that was unlocked with HTC's tool.
I did a nandroid backup on both phones, and the boot.img from both backups have an identical MD5 hash. Seems like CWM is able to flash the boot image just fine. Am I missing something?
You cannot fash splash screen with HTCDev method. It is not truely S-Off.
Sent from my HTC ThunderBolt using XDA Premium App
oneders65 said:
You cannot fash splash screen with HTCDev method. It is not truely S-Off.
Click to expand...
Click to collapse
My phone shows a CM7 splash screen.
Now I'm wondering, does it matter that I had S-OFF on this phone at one point in time (via AlphaRevX) before returning it to HBOOT 1.02 w/ S-ON using this method? I'm wondering if the reason these things are still writable on my device is because the process of "reverting" to HBOOT 1.02 didn't actually remove S-OFF from my device (even though it says S-ON on the HBOOT screen).
---------- Post added at 06:03 AM ---------- Previous post was at 05:33 AM ----------
If I re-lock the phone (fastboot oem lock), then I definitely lose the ability to write to the system partition while booted, so I don't think that was it. I'm definitely confused.
drumist said:
Are you sure about that? I have two Arias, one with S-OFF via AlphaRevX and another that I upgraded to HBOOT 1.03 and unlocked using HTC's tool. Using your build of CWM 5.0.2.3 on both. I installed CM7 on both phones and I don't notice any problems with the phone that was unlocked with HTC's tool.
I did a nandroid backup on both phones, and the boot.img from both backups have an identical MD5 hash. Seems like CWM is able to flash the boot image just fine. Am I missing something?
Click to expand...
Click to collapse
Did you already have CM7 on it? Wipe data and flash a sense ROM and see what happens.
attn1 said:
Did you already have CM7 on it? Wipe data and flash a sense ROM and see what happens.
Click to expand...
Click to collapse
I had run the AT&T 2.2.2 RUU on the device before I upgraded to the 1.03 HBOOT, so it had the boot image from the 2.2.2 RUU on it before I did the HTC unlock.
CM7, CM6, and Liberated 2.2.2 all work fine. Boots, shows appropriate splash screen, and as far as I can tell there aren't any issues although I haven't really used it much beyond just booting it up and testing a few things.
drumist said:
I had run the AT&T 2.2.2 RUU on the device before I upgraded to the 1.03 HBOOT, so it had the boot image from the 2.2.2 RUU on it before I did the HTC unlock.
CM7, CM6, and Liberated 2.2.2 all work fine. Boots, shows appropriate splash screen, and as far as I can tell there aren't any issues although I haven't really used it much beyond just booting it up and testing a few things.
Click to expand...
Click to collapse
Splash screen, not boot animation.
Displays before the rom or recovery boots.
Default splash screen is white with green HTC letters...
I'm gonna switch my phone over to this and see if I lose any functionality...
Edit: Well, can't flash splash screens.. but I can change stuff in system and it stays with a reboot, even though it says S-ON..
drumist said:
I had run the AT&T 2.2.2 RUU on the device before I upgraded to the 1.03 HBOOT, so it had the boot image from the 2.2.2 RUU on it before I did the HTC unlock.
CM7, CM6, and Liberated 2.2.2 all work fine. Boots, shows appropriate splash screen, and as far as I can tell there aren't any issues although I haven't really used it much beyond just booting it up and testing a few things.
Click to expand...
Click to collapse
I think you mean boot animation and not splash screen. The splash screen is the white screen with HTC that displays before the CM7 boot animation begins.
Your Hboot says S-ON or S-OFF?
attn1 said:
I think you mean boot animation and not splash screen. The splash screen is the white screen with HTC that displays before the CM7 boot animation begins.
Your Hboot says S-ON or S-OFF?
Click to expand...
Click to collapse
Sorry, yes. I have not tried to replace the splash screen.
The HBOOT says S-ON but has the text "unlocked" at the top line (after using the HTCdev unlock).
drumist said:
Sorry, yes. I have not tried to replace the splash screen.
The HBOOT says S-ON but has the text "unlocked" at the top line (after using the HTCdev unlock).
Click to expand...
Click to collapse
Well I just had to test it. You're correct. On Aria, the unlocked bootloader, while not complete S-OFF, allows full rom flashing from recovery. Awesome. This is all most users would need. It doesn't work as well on Inspire.
I still think the revolutionary way is more complete and *easier*.
Related
seems that someone has obtained to have s-off on desire ! have a look at this . maybe the n1 would be the next (i hope).
It's not needed on the N1, S-OFF for the Desire is the same as the N1 with an unlocked bootloader.
yeah, but with an s-off hboot we could relock the bootloader.
100% completely irrelevant on the N1.
Also, you can't re-lock the boot loader, it is permanent, per the warning you were given when you did it.
What if I want to reflash the unlocked splash screen with the locked one for cosmetic reasons (to hide the lock)? It is a little bit relevant.
G0belet said:
What if I want to reflash the unlocked splash screen with the locked one for cosmetic reasons (to hide the lock)? It is a little bit relevant.
Click to expand...
Click to collapse
That is something I had thought about doing, I must admit.
I didn't try it, but looked for it for completely another reasons (changing the splash screen). Looks like you can't flash "splash1" partition on Nexus, it fails. If you want - you can download splash1.img from any resolution-compatible device (EVO, for example), and try to flash.
Even with S-OFF:
Code:
C:\Users\Rusty\Desktop>fastboot flash splash1 evosplash1.rgb565
< waiting for device >
sending 'splash1' (750 KB)... OKAY [ 0.166s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.237s
That answers that then.
I never tried to downgrade my HBOOT but if I'm not mistaken, there's a way to flash mtd1 if my memory serves, and before upgrading you see the HTC logo instead of the Nexus One logo. Again I never had to downgrade my HBOOT but I think there might be a way to see how that img file works, and see if we can change the splash. That's a wild guess at this point.
EDIT: I mean mtd0. Can't we dump it to see what's in it?
The new G2 permroot procedure seems to involve running some sort of kernel module which then allows you to reflash HBOOT with an engineering bootloader and get S-OFF. If you subsequently restore to stock using PC10IMG.zip, the stock bootloader relocks to S-ON.
Would this not be theoretically possible with the N1? There are Nexus One units out there with an engineering bootloader that can go to S-OFF without a permanent watermark. If the ENG HBOOT can be flashed from inside the OS, it could be a way to get S-OFF reversibly.
The ENG HBOOT on the Nexus One is larger than the SHIP one, so apparently it's a no go.
G0belet said:
I never tried to downgrade my HBOOT but if I'm not mistaken, there's a way to flash mtd1 if my memory serves, and before upgrading you see the HTC logo instead of the Nexus One logo. Again I never had to downgrade my HBOOT but I think there might be a way to see how that img file works, and see if we can change the splash. That's a wild guess at this point.
EDIT: I mean mtd0. Can't we dump it to see what's in it?
Click to expand...
Click to collapse
You have HBOOT images (FRG83 and KO-KR FRF91 came with HBOOT 0.35 update, for example), so you don't need to try to dump them. Nobody invested time in hacking them, I believe, because it's not a priority work.
You can customize the partition sizes through command line, but it doesn't override things for fastboot itself - making it impossible to update HBOOT with Eng HBOOT, which is larger and doesn't fit on the HBOOT partition.
I'm not sure MTD0 flashed to MISC partition does anything to HBOOT itself. If it does - it might be possible to flash Desire S-OFF HBOOT on Nexus and deal with the differently partitioned ROM (or revert back to Nexus partitioning with command line override method). Anyway, it won't really bring Nexus back to stock, so it misses the point for all those that want to have their bootloader relocked. Even with substituted splash1 to match locked Nexus, going into bootloader will show a version Nexus doesn't have. Flashing back Nexus HBOOT will return the "unlocked" sign, since it wouldn't be locked.
And it looks like Desire HBOOT is still within the smaller partition size and doesn't enlarge it to fit Nexus Eng SPL.
Jack_R1 said:
I'm not sure MTD0 flashed to MISC partition does anything to HBOOT itself. If it does - it might be possible to flash Desire S-OFF HBOOT on Nexus and deal with the differently partitioned ROM (or revert back to Nexus partitioning with command line override method). Anyway, it won't really bring Nexus back to stock, so it misses the point for all those that want to have their bootloader relocked. Even with substituted splash1 to match locked Nexus, going into bootloader will show a version Nexus doesn't have. Flashing back Nexus HBOOT will return the "unlocked" sign, since it wouldn't be locked.
And it looks like Desire HBOOT is still within the smaller partition size and doesn't enlarge it to fit Nexus Eng SPL.
Click to expand...
Click to collapse
I checked, turns out mtd0 contains UART settings and the phone's CID... I can't see anything about logos and such.
Still, I think we could have a modified HBOOT with extended commands, making flashing splash0 and splash1 doable. And if we flash HBOOT back to the stock one through flash_image, it won't flash the splash screens again, so the splash change will stick. If you flash the one without a lock (splash0 I imagine) over splash1, and go back to stock HBOOT, won't it just stick?
This is just thinking here. Still, we need some kind of ENG HBOOT, or at least backport some functions of the ENG HBOOT to the SHIP one to allow splash screen flashing.
Also, the goal here is not necessarily to go back to stock and relock the bootloader in any way. It's mostly because the lock bugs me, and if there was a way to hide it, I'd gladly do it. I don't care about my bootloader not being the same anymore, or my phone not being stock I just like the clean look of the Nexus logo without the lock.
There is only one splash partition, there is no splash0 on those phones, AFAIK.
The thing is very simple: playing with HBOOT isn't safe - which means, if you flash a wrong one, your phone is done. Devs don't bother working on it, and rightfully so - when they have tasks of much higher priority, like G2's eMMC, they don't bother working on something that works already. I'm not going to be the one that tries flashing Desire HBOOT without certain knowledge, what will it do to Nexus - I don't live in Nexus-supported country. If you have a spare Nexus and are willing to exercise its warranty - flash Desire Eng HBOOT and see if it works.
I thought spcustom was basically splash1 with the lock, but turns out it's the screen that shows when you "fastboot oem unlock".
This is the bottom 768000 bytes of spcustom.img I found in a PASSIMG (most of you know that screen already though):
Maybe HBOOT actually adds the lock at the bottom of the screen. Or HBOOT composites the bottom part of spcustom and splash1. Can't say, I'm no engineer.
I actually know it's dangerous to do all this, and once again it's just a thinktank. I'm just trying to locate anything that could help more knowledgeable people to start working on this.
cmstlist said:
The new G2 permroot procedure seems to involve running some sort of kernel module which then allows you to reflash HBOOT with an engineering bootloader and get S-OFF. If you subsequently restore to stock using PC10IMG.zip, the stock bootloader relocks to S-ON.
Would this not be theoretically possible with the N1? There are Nexus One units out there with an engineering bootloader that can go to S-OFF without a permanent watermark. If the ENG HBOOT can be flashed from inside the OS, it could be a way to get S-OFF reversibly.
Click to expand...
Click to collapse
What it does is toggles power to the mmc and then force it to reinitialize as if suspended to disable the write-protect of the emmc. The N1 doesn't use emmc though so I think the protection of the hboot is done in some other way.
Rusty! said:
The ENG HBOOT on the Nexus One is larger than the SHIP one, so apparently it's a no go.
Click to expand...
Click to collapse
From what I've heard, the hboot partition on the retail N1s is actually the same size as the eng hboot. Open the eng hboot in a hex-editor and you'll see there is quite a lot of padding at the end and various other places. It might fit.
i read in general or q/a that someone did a warranty on there n1 and got it back a lock bootloader again, they had it unlocked. this was some ways back.. but there is a way to relock it, as there is some cases with ppl that have a unlock boot still get warranty and get it back with a lock boot...
Jack_R1 said:
There is only one splash partition, there is no splash0 on those phones, AFAIK.
The thing is very simple: playing with HBOOT isn't safe - which means, if you flash a wrong one, your phone is done. Devs don't bother working on it, and rightfully so - when they have tasks of much higher priority, like G2's eMMC, they don't bother working on something that works already. I'm not going to be the one that tries flashing Desire HBOOT without certain knowledge, what will it do to Nexus - I don't live in Nexus-supported country. If you have a spare Nexus and are willing to exercise its warranty - flash Desire Eng HBOOT and see if it works.
Click to expand...
Click to collapse
Yes, it isn't safe to muck around with HBOOT.
I bricked my desire by flashing a corrupt HBOOT patch, but it was my fault for not checking the md5.
And I would do it again. (But a checked file ;-))
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
!!!UPDATE!!!
Whats Completed,
S-OFF
Custom Recovery
ENG Bootloader.
HBOOT 2.02.0000 is completely cracked.
Advantage of hboot 2.02 > 0.76?
[email protected] said:
Advantage of hboot 2.02 > 0.76?
Click to expand...
Click to collapse
THIS !!!!!!!! >
2.02 is non engineering hboot... so i would think there is not much point... but than again... i think probably 99% of us dont even touch those options.
Uh nothing that i know of, except that HBOOT 2.02 that i have found will NOT downgrade to .76 as they patched it, I tried the eng-PC36IMG.zip, unrevoked etc. They do not root, nand unlock and install recovery.
eng-PC36IMG.zip skips installing the bootloader wich is the HBOOT.
Unrevoked Errors out and will not get past the HBOOT and throws a error saying lost connection.
So far can not downgrade the stupid hboot. This is what happens.
http://img215.imageshack.us/img215/1126/img20101102215418.jpg
amoamare said:
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
Click to expand...
Click to collapse
How did you get s off? Ive been trying everything for the past week
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
amoamare said:
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
Click to expand...
Click to collapse
How did you do it?
Hex edit? Cough cough.
Like i said, more info will be released in a bit. I'm waiting for a response from someone.
kenny21 said:
How did you get s off? Ive been trying everything for the past week
Click to expand...
Click to collapse
If you have s-off then you should be able to make a PC36IMG.zip out of one of these hboots found here http://forum.xda-developers.com/showthread.php?t=801568
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
amoamare said:
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
Click to expand...
Click to collapse
so, will this fix let us root the phone and load recovery and flash roms again? im so tired of being stock lol.
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
amoamare said:
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
Click to expand...
Click to collapse
could we have an ETA on your fix? i would love to try it before i go to sleep ;(
Like i said just waiting on a message from someone and will post from there.
amoamare said:
Like i said just waiting on a message from someone and will post from there.
Click to expand...
Click to collapse
Thanks for the effort. I bought an Evo today with 2.02 Hboot on it. I was afraid to be stuck with stock for a long time.
Ok 2.02 has been successfully cracked all the way.
http://d.imagehost.org/0355/IMG_20101102_233241.jpg
ENG bootloader has been loaded on. All fastboot cmds are restored. Sweet.
Hi all,
today i discovered something strange and i like to get your opinion on that:
I am not able to do s-off things in fastboot even if i have s-off!
Situation:
Phone: Desire Z
HBOOT: stock 0.85.0005
FW: 1.34..
Rooted: did root, supercid and s-off via gfree and verified via gfree_verify - even hboot showes up S-OFF
ROM: GingerVillain 1.5
Recovery: ClockworkMod 3.0.0.5
Problem:
First of all, i myself have no problem, but i started experimenting after a friend semi-bricked his desire z with same setup.
I did a nandroid backup and when i boot into hboot and do a 'fastboot flash recovery recovery.img' (with my nandroid recovery.img) i always get a remote: not allowed.
Now from my point of view this should only happen if I have a S-ON and should be impossible with S-OFF ?! Even using 'fastboot oem rebootRUU' does not change anything.
The thing that concerns me about that is: If something destroys both system and recovery, your pretty much screwed + bricked because hboot is not allowed to write to something other then cache and all of this basic stuff doesn't work:
- flash recovery with CW
- flash a complete zip
- flash an other hboot
- RUU
When I rooted my phone i have read everywhere that eng-hboots are not necessary any longer. But it appears that they are the only thing that helps and you have to install them as long as you have a working ROM.
Any thoughts on that issue / can you reproduce this / are fastboot actions logged anywhere?
You need a ENG. HBoot to use fastboot commands, doesn't matter if your s-off.
yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005? i did some experimentation with a goldcard, but at least remote commands didn't change in behaviour..
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here
DragonTEC said:
yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005?
Click to expand...
Click to collapse
maybe thru a modified PC10IMG.zip
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here
Click to expand...
Click to collapse
My thoughts exactly, its kind of a safety if you can't boot into android.
i'm not sure if a PC10IMG.zip will help at all.. my friend tried flashing both 1.34 and 1.72 RUU ROMs as PC10IMG and this didn't change anything.. in fact, the 1.72 even didn' install the new .00008 hbott, so i thing there is some heavy write protection in the hboot making it more or less useless..
what i can imagine that works is aa gokldcard with sppimg.zip, but i haven't yet found one for the desire z..
i have the feeling that this is a huge problem because with a short research i have found at least 3 threads of people having bricked their phone exactly this way and are now stuck.. some of the experts here might pay attention to this problem and in my opinion you should also consider removing the 'a eng-hboot is not needed, don't use it' advice from the rooting section of the wiki..
So what exactly is your problem.
You destroyed recovery and system?
If yes, and you used gfree to get Super-CID just install an PC10IMG that has a version higher or equal to the main version in you misc partition. And then do the whole downgrading, rooting, flashing recovery again.
If you are not Super-CID you might need a goldcard in addition if the CID of the phone is not supported by the PC10IMG that you whant to install.
have fun Guhl
It is almost impossible to brick this phone. The only possible way might be a failed copy of the eng-hboot and this is why the warning is and stays in the wiki.
Sent from my HTC Vision using XDA App
I thought so, too, but when flashing a newer original RUU using the PC10IMG.zip, the flash process runs okay, but after the restart nothing (still hangs in HTC screen, no new hboot) changes so apparently no changes are made..
So from my point of view the phone is more or less bricked.. i guess maybe some custome PC10IMG with an eng-hboot might change this, but i only found one for the G2 and wasn't able to find one for the DZ.. Thats why I thing that removing the 'UNNECESSARY' advice is justified (of course i don't want the warning advice that this can brick the phone to be removed)..
Just wondering why this is so special? I flashed just for the hell of it but now I'm kinda curious why the devs and a few others recommend it.
Sent from my HTC Glacier using XDA App
If you do run into an issue like a soft brick, it is easier to fix your phone as it allows you to use fastboot on your computer. I'm no pro, but I am pretty sure that is the correct answer, I'm sure someone else will chime in.
if thats the case, thats pretty nice. may explain why i couldnt flash a splash screen through fastboot before i flashed the engineering bootloader.
mustk1ll20 said:
if thats the case, thats pretty nice. may explain why i couldnt flash a splash screen through fastboot before i flashed the engineering bootloader.
Click to expand...
Click to collapse
The reason alot of us recommend it is pretty simple. HTC Locks the bootloader so we cannot flash specific images to our phone. OR Specific sections of a ROM build. If you can flash the Engineering screen it will allow you to flash stuff from the HBoot. SO if you find your self in pickle and the phone will not mount specific sections you can always revert to HBoot to flash it. The reason you cannot flash the splash image is the same reason, it's locked and will not allow you to do it, it's one of the few things they locked down.
neidlinger said:
The reason alot of us recommend it is pretty simple. HTC Locks the bootloader so we cannot flash specific images to our phone. OR Specific sections of a ROM build. If you can flash the Engineering screen it will allow you to flash stuff from the HBoot. SO if you find your self in pickle and the phone will not mount specific sections you can always revert to HBoot to flash it. The reason you cannot flash the splash image is the same reason, it's locked and will not allow you to do it, it's one of the few things they locked down.
Click to expand...
Click to collapse
This.
Theres an epidemic of people getting softbricks lately, that we can't get fixed because of not having the eng bootloader installed.
neidlinger said:
The reason alot of us recommend it is pretty simple. HTC Locks the bootloader so we cannot flash specific images to our phone. OR Specific sections of a ROM build. If you can flash the Engineering screen it will allow you to flash stuff from the HBoot. SO if you find your self in pickle and the phone will not mount specific sections you can always revert to HBoot to flash it. The reason you cannot flash the splash image is the same reason, it's locked and will not allow you to do it, it's one of the few things they locked down.
Click to expand...
Click to collapse
option94 said:
This.
Theres an epidemic of people getting softbricks lately, that we can't get fixed because of not having the eng bootloader installed.
Click to expand...
Click to collapse
looks like i made the right choice to flash this then. thanks for the info guys. gonna try changing my splash screen now make this thing even more mine. lol
also if i did soft brick it i would use ADB while the phones at the hboot screen correct? i had it on the hboot screen while it was plugged in to my computer and noticed a install driver thing pop on, but couldnt install because i didnt have the driver. said somethikng like android 1?
i am new to this so if you can bare with me. I recently Unlocked and rooted my G2 and i also installed a custom recovery (ClockworkMod). I have been trying to install a custom but have been having problems with this. what happens is i use recovery to install rom from sdcard and it looks like it installs, i mean it says it is successful but when i reboot it gets stuck on HTC boot screen. I do not know what else to do, please help. oh and i also have tried to do this with a few diffirent ROM's.
Just a guess, but it sounds like you didn't wipe before installing a rom. From the main recovery menu, choose factory reset/wipe data and cache. When that is done, you can install whatever ROM you'd like. If you're installing an AOSP rom, don't forget to flash the google apps (gapps) after the ROM.
What ROM are you attempting to install. If it is newer sense based you may need the desire z boot.
Sent from my Nexus 7 using xda premium
pkb6212003 said:
i am new to this so if you can bare with me. I recently Unlocked and rooted my G2 and i also installed a custom recovery (ClockworkMod). I have been trying to install a custom but have been having problems with this. what happens is i use recovery to install rom from sdcard and it looks like it installs, i mean it says it is successful but when i reboot it gets stuck on HTC boot screen. I do not know what else to do, please help. oh and i also have tried to do this with a few diffirent ROM's.
Click to expand...
Click to collapse
As someone else said, looks like yo didn't bother to factory-reset/wipe via recovery before attempting to apply a brand new rom.
Flashing the rom doesn't wipe everything for you before hand, it would be like trying to install Windows 7 on top of Windows XP without bothering to remove windows XP and you end up with this mixed up mess of the two that doesn't work.
PS: Didn't you already ask this in another thread? (almost seems like word-for-word what another 1st time poster said)
thank you
thank you for the suggestions, i will try right now and let you know. i thought i did a full wipe, but maybe i didn't, i will try again.
Also this is the first time i have ever posted here. oh and one of the rom's i have cyanogenmod 7.2.0
HTC G2
tried what you suggested and still got the same thing, or is there something else i could try?
maybe you are getting corrupt ROM downloads? have you tried checking if md5sums match? since this is your first time, here is a link to a windows md5 sum checker
c00ller said:
maybe you are getting corrupt ROM downloads? have you tried checking if md5sums match? since this is your first time, here is a link to a windows md5 sum checker
Click to expand...
Click to collapse
I like how 4EXT Recovery can let you check the md5sum of any file on the SD card before you decide to flash it, so you can compare to the source.
May be radio problem
Sent from my Desire Z using XDA
G2 ROMS
the roms i have downloaded are all good, i even tried to redownload them and tried a couple other downloads, same thing though.
HTC G2
santajin said:
May be radio problem
Sent from my Desire Z using XDA
Click to expand...
Click to collapse
What do you mean? What could be wrong with the radio?
pkb6212003 said:
the roms i have downloaded are all good, i even tried to redownload them and tried a couple other downloads, same thing though.
Click to expand...
Click to collapse
Which roms? did you verify that you meet all the requirements? (for example some newer roms, particularly some ICS attempts, need the newer *.19 radio).
For example I couldn't get EliteMod ICS booting until I upgraded my radio to 26.13.04.19 from the old *.26 one (also the T-Mobile Wifi Calling app requires the new radio too).
PS: It's generally more helpful if you list out all your specs, i.e.: your Phone's Hboot (hboot version, SHIP vs ENG, S-OFF vs S-ON, Radio Version), Recovery type/version, and what roms you are trying.
Hi, are you simply unlocked using the HTC bootloader unlocker? If so, another thing to consider is you may need to flash the boot.img thru fastboot along with installing the ROM thru recovery. I don't think HTC unlock lets you flash to the boot partition in recovery, so if the ROM you flash uses a custom kernel, it won't boot until you flash that seperately thru fastboot.
I flashed a new rom and got stuck on the white HTC screen too but after taking the battery out for about 30s it just booted right up. Happened a few times now so it could be that.
I have had that same problem doing a full wipe and also wiping the cache and dalvik before I install a new rom works for me, I have had the same situation AFTER a time and as desirez_pete stated removing the battery for 30 seconds and rebooting did the trick.
HTC G2 SPECs
Sorry i have been away for so long, still am unable to install custom ROM, I was reading the threads and noticed someone asked for my specs here they are -
VISION PVT SHIP S-ON
HBOOT-0.82.0009
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
The Phone is Unlocked and rooted and my recovery version is ClockworkMod Recovery v5.8.1.0 touch
also when ever i have tried to optain S-OFF i get eMMC- Boot Failed
any help from here i would be very thankful.
pkb6212003 said:
Sorry i have been away for so long, still am unable to install custom ROM, I was reading the threads and noticed someone asked for my specs here they are -
VISION PVT SHIP S-ON
HBOOT-0.82.0009
MICROP-0425
RADIO-26.13.04.19_M
eMMC-boot
The Phone is Unlocked and rooted and my recovery version is ClockworkMod Recovery v5.8.1.0 touch
also when ever i have tried to optain S-OFF i get eMMC- Boot Failed
any help from here i would be very thankful.
Click to expand...
Click to collapse
" SHIP S-ON" doesn't look unlocked to me.
HTC G2 SPECs
kbeezie said:
" SHIP S-ON" doesn't look unlocked to me.
Click to expand...
Click to collapse
When i boot into the bootloader and at the top of the screen it says "UNLOCKED" just like i just typed
deleted, didn't read.
pkb6212003 said:
When i boot into the bootloader and at the top of the screen it says "UNLOCKED" just like i just typed
Click to expand...
Click to collapse
Means went thru the HTCDev site which is kind of a sissy-unlock, compared to going with the XDA guide which would have gotten you a fully unlocked bootloader, SIM unlocked, ENG/S-OFF, the works.