Develop Bugs

hermes different roms upgrades

Hello All experts,
All of a sudden my jasjam accepts upgrading to different roms, the only problem that it reach 100 and then it gets stuck on 100 % screen then the rom wizard asks to recover but if hard reset the device it works without any issue does any one have any ideas of how solve this I have tried several solutions here but no luck I am using vista I thought this might be a vista thing but its not because I tried the same rom or others and its the same result.

are u flashing via usb or sd card

I always flash with USB
USB is what I use and vista is the OS I use

install ClearTemp and then use it to reset/clear the ppc (100) Boot Count to 0 (if that's what your talking about).

If your using hardspl v9 (spl2.60) you can run into that issue. If your not needing to dink with things in the bootloader, you really don't need it.
Roll back to hardspl v7

?
where I can get the clear temp

I wouldn't worry about cleartemp unless it's absolutely necessary - in the past couple of days, I've been flashing roms from a MicroSD card using HardSPL (I think it's version 6 or 7, I put it on a while ago) - it's really fast and very safe to do. Also no problems with freezes during flashing, once it's flashed you just soft reset and set up your device

Can't flash newer roms

Alright guys, I did quite a bit of research. Basically all roms before 6.5.1 flash just fine. But, only a very select few with 6.5.1 and the newest manilla, seem to flash with error. This is all just so odd.
You name it, I have tried it. On two pc's, and flashing from the microSD card, and yes I formatted the card to FAT32 first.
Flashing from the pc and microSD card always results precisely the same with every rom. This tells me that there is absolutely no doubt that it is, the phone itself...
I flashed the first version of HARDspl, both manual and automatic, and did the same with the latest version of hardspl. I have tried more combination's of roms and radios than I can even recall.
After some researching of the, flash error code 226, I read more than a few people stating that similar problems were the result of an inability to write to the Extended ROM in the phones flash memory. I guess its also called ExtROM.
This made sense to me because ALL of the rom flashes that fail, do so in the last 94-99%. This obviously tells me that the error is in the last bit of info attempting to be written to the device.
Basically I am stuck. No idea how to flash the newer roms, specifically the EnergyROMS.
Help?

Does anyone have any advice?

Okay this is weird. I can flash any newer rom that has TF3D 2.1 but only a select few that have 2.5xx. Weird right?
Seriously? No one has any advice for me? I am really held back by this, I love this forum and I love trying new roms.
I guess I have covered all bases and no one knows what to say...
It seems like a portion of my TP2's primary partition is damaged somehow...
I dont know how to rewrite over that, I have tried two different T-Mobile stock roms with their appropriate radios. I always do a hard reset after every flash.
Any input please? Even if you have no advice just some response would be great, thanks.

Is there such a thing as flashing too much?

Recently acquired a used 8525 and have been checking out tons of custom ROMS but today my phone locked up and wouldn't do anything. I am flashed to 2.10 HardSPL and was running the stock "like" 6.5 ROM on the front page of the Hermes forum. Phone would start up but locked up at the first HTC splash screen. I tried resetting and removing the battery but it would hang at the same spot. I flashed to a different ROM and everything seems OK. The 6.5ROM ran fine for a few days when it was installed. Is it possible to damage the internal memory by flashing and reflashing constantly or is the issue more than likely a software problem?

You need to flash the at&t stripped rom between those custom roms. That will "straighten out" any odd memory issues like what your experiencing.
And I'm guessing it would take several thousand (or more) rewrites of the memory to mess it up. Probably similar to compact flash, or a thumb drive. Maybe one of the more knowledgeable ones around here know.

Thanks for the info. Do I simple flash the stripped AT&T rom from the bootloader and then do the same for the custom rom afterwards?

Yup! And it seems just flashing the at&t stripped rom seems to be fine, no need to let it go through setup and all of that. I generally wait for it to get to the "tap here" screen, then go into boot loader and reflash.

I'm having the same issue one my 8525.
I can't do ANYTHING because my phone is stuck saying smart mobility.
And, a black screen.
How do I....
Do I simple flash the stripped AT&T rom from the bootloader and then do the same for the custom rom afterwards?
I've downloaded your stripped AT&T room... now what? I dont know about bootloader

Ok. It looks like I finally have SOMETHING other than that screen.
I just did a hard reset.
Is there anything I should do BEFORE this happens again?

Install Hard SPL V7 if you get to the today screen... Go to here - http://forum.xda-developers.com/showthread.php?t=296722
page 116, post 1160 to use the sd card method...
This should make it easier to recover your Hermes if something goes wrong.
Cheers...
SD card MUST be 2Gb or less and formatted FAT32. Check your spelling - hermimg.nbh...

I'm fully functioning now... I have installed HARD SPL before.. do I re do it?
Or, what?
all is working normal now

Nah, once it's there, there is no need to redo it. It will stick between flashings.

[android] Problem with NAND :/

Hello!
Ive got a problem aftter flashing a *.nbh for NAND android :/ It just hanged on the splash screen. No any linux logs

If you can still get bootloader, try reflashing, sometimes it fails for no apparent reason, if that still does not work, try formatting the SD, recopy the nbh, reflash again.
If all else fails, you may be one of those who cannot flash to nand, I have 2 kais130's one flashes every time, the other, about 1 in 15 times is successful.

zenity said:
If you can still get bootloader, try reflashing, sometimes it fails for no apparent reason, if that still does not work, try formatting the SD, recopy the nbh, reflash again.
If all else fails, you may be one of those who cannot flash to nand, I have 2 kais130's one flashes every time, the other, about 1 in 15 times is successful.
Click to expand...
Click to collapse
I can still get bootloader, a reflashed, today i putted new SDHC card and i try to reflash nbh. Only 1 time after flash I can see linux logs, I can to install it too, but when ill reboot phone then hangs like early :/

Ok first which Android build are you trying?
When you say reboot, are you using the reset button or pulling the battery after flashing, ( using reset can cause problems, the correct method is flash, pull battery, wait, replace battery ).
Which nbh are you trying to flash? If you had android working then you may want to go back to the nbh you used before.

zenity said:
Ok first which Android build are you trying?
When you say reboot, are you using the reset button or pulling the battery after flashing, ( using reset can cause problems, the correct method is flash, pull battery, wait, replace battery ).
Which nbh are you trying to flash? If you had android working then you may want to go back to the nbh you used before.
Click to expand...
Click to collapse
Im using kaisimg-panel1-428-12-03-10, im using a reset button not battery trick. Im using warm donut biuld. As I said i can boot android from NAND just 1 time, not anymore

Well the best nbh's for the kaiser are still the sourceforge ones at least for stability, the 20/02/2010 ones, yes there are newer ones, but they may require some pretty advanced editing of some system files before they run properly, and may not be fully compatible with the donut build.
I think it may be better to use one of these : http://sourceforge.net/projects/androidhtc/files/2010-02-20/kaisereclair/

I have the same issue with dzos latest. I posted it in the bluetooth thread as to not open any unneeded topics. The fix he posted 11-03-10 for bluetooth booted fine, this one gives me the same issue. Remember this stuff is all relatively experimental so try not to panic when using the very latest since it might not work.

Apparently there is a problem with the latest nbh's, I'd just reflash an earlier NBH, this should fix the problem.

I'm having the exact same problem. Everything seems to get installed properly but once I take out the battery to reboot it just hangs on the splash screen. I've tried several builds and reformatted the card several times... always the same result. In one of the posts I cam across it was mentioned that you first have to go in to win mobile to turn off a pin # and that can cause the system to hang if not done. I can't find the post anymore and I'm not sure what they were talking about.

kcbronc said:
I'm having the exact same problem. Everything seems to get installed properly but once I take out the battery to reboot it just hangs on the splash screen. I've tried several builds and reformatted the card several times... always the same result. In one of the posts I cam across it was mentioned that you first have to go in to win mobile to turn off a pin # and that can cause the system to hang if not done. I can't find the post anymore and I'm not sure what they were talking about.
Click to expand...
Click to collapse
Yeah I read about disabling the pin thing in Win Mo as well, but unfortunately this was after I flashed Android to NAND. Mine hangs at the splash screen as well, but if you put the KAISDIAG.nbh file in the root of your SD card, from the Hard SPL threads, the phone will boot and get to the Android installer, but will then come up with errors when choosing to install to NAND. Unfortunately, I can't even go back to Win Mo because of this.

ROM Won't Flash

Jeeze, after all the tinkering that I have done with this phone in back in the days, you'd think I would know what to do in this situation haha. But if anyone is still out there, I'm having a bit of an issue. The one rom I want to flash on this phone so I can temporarily use it for a few days whilst in between upgrading phones, Desire Gingerbread Sense v1.2 refuses to flash for some reason. I keep getting Status 0, installation aborted in CWM and I have never had the issue in the past, same file I have used in the past as well. I originally thought it might be due to it having an EXT 4 filesystem from a prior rom, but I flashed a few GB roms and then tried reflashing it, and still spitting out the same thing. If I solve this on my own I'll post my remedy, just found it odd.
-Edit-
Welp, exhausted all options. Redownloaded the file, tried different recoveries, formatted my SD card, etc to no avail. Turns out in the end it wasn't worth it since the SIM slot no longer reads SIM cards. So, time to bust out my ancient iPhone 2G as a temporary phone for a few weeks xD
-11/29/15 Edit-
Yet another update on this. I'm one to not give up on certain things so I mildly opened up the phone and managed fixed the sim slot, no progress on the rom getting to flash though