Develop Bugs

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.

Stuck/freeze (Hero) while downgrade. Not working now at all!!

Helo dear friends!
It started with a wish to put some Hebrew in a Hero.
I have the Orange hero in Spain. Upgraded to official rom- 2.73.61.5, worked fine.
Now i am trying to downgrade it, so i can root it, so i can put some fun stuff in (like Hebrew).
Did the gold card, which i understood is needed if the hero is CID locked (i think it is). Then failed few times with error 140 when tried the 1.76.405.6 and 1.76.405.1... rom links.
Then tried to downgrade to 2.73.405.5 rom as someone suggested here, and the process started happily! downloaded Splash1 ok, system ok, userdata ok, boot ok, bootloader ok, then GOT STUCK ON "radio-V2 - updating" got to 85% then froze! (attached a picture).
This happened few times, sometimes never even started to download, was just froze at the beginning of the process with: "zip header checking..."
So every-time this happened i had to disconnect it, even take out battery, and try again. I also found out that for some-reason things moved forward when restarting windows which by the way is on parallels (mac) ...
(maybe that's part of the problem)
Now the hero is stuck on that screen, picture attached.
Any idea someone? first how do i bring a dead hero back to life?
Then, anything else to move forward...
Thanks in advance! will appreciate your help.

If anything, I'd first check the card!!
As your phone is CID-locked, I gather it might also help if you install the unlocked SPL (there's a separate thread here). After that, you may try a regular upgrade method through the recovery (I think you should wipe first).
Hope it helps!

Thanks avs333...
mmm... i am a bit short on the terms.. so, i just started to read about SPL ... (my eyes.. it burns ...
Anyways I found a this thread, is that what you mean?
What do you mean by "check the card"? the hero is still on that white error screen, waiting for some "food" to come in, it's the only thing coming up, the VM is recognizing the connection, and letting the process of downgrading begin (until it freezes).
Windows is not recognizing it as a card or storage device, so i am not shore i can access the card (if needed) .... or you mean the SPL process is doing that already?
Botom line, what about the card ?
Another friend here suggested i should try with a real PC ...
What is "wipe first"?
Thanks allot appreciate the help... hero too...

Yes, that's the right thread. I'm not 100% sure if it would help, but I'd try that anyway.
By "checking the card" I meant just to pull it out of hero and test it on a real computer (there are many programs to do that, but you need a card reader).
And "wipe" is a procedure which clears the memory regions before you install any updates. Basically, it's not always needed, but sometimes it's critical.
Also, there are ROMs without radio, if it stucks on that stage, you may try them!

Test it how? i have a card reader, the computer recognizes it... now what? (funny i thought it was formatted/deleted completely when i did the gold-card, there is a folder there, of one the apps i think "rosie_scroll"... do you think it's a problem?)...
Should i try do a gold again? is there a way doing it outside of the hero?with the card reader?
YEsterday i try the download twice more it got stuck even on an earlier stage before the Radio... so i am not shore at all what is the problem...
So do i wipe after i do install unlocked SPL?

Anyhow, was trying to access the card again for remake of the gold card. first formatted it with a sd card format program... but could not access the card/device via cmd, looking for adb devices...
Tried the downgrade again, and it fails with error 131, something about not correct ROm.
Finally decided to try going back to ground zero, and tried downloading the official rom i had before, and it came back to life. and with the VM (windows on mac).
Now i wonder what is the best first step i should do to finally free this phone?
I know it's CID locked by now (maybe i am wrong?) so should i do the install unlocked SPL first like you suggested?
Or should i redo the gold-card method? another rom?
Is there a better way to start over, now that i came back to ground zero? do you know who might give me a good second opinion here?
Lots of questions?
Should i stop?
Thanks allot avs333?
Guanarteme?

Guanarteme sorry I had qquite a lot of problems today, of another kind, women you know, sometimes it's a bit more involved...
As I understand, the way is to try some other ROM (they are plenty around here), why cling to that one? I had *a lot* of disasters so far, not of your kind maybe, still disappointing but *never* fatal.
Do make sure you have 100% charged the hero before any procedure! And be terribly cool, that thing is just a bunch of microschemes, it must not put you off, and you'll be victorious!
So my suggestion is to try other ROMs until you succeed. And of course you should not give up before you have a device which is ideal for you. You have already paid a lot of money for that!
The locked/unlocked state is simple, you see S-OFF instead of S-ON when you boot (as for the screenshot you've posted). I cannot overly appreciate the power of this SPL feature because my device was initially unlocked, but for you guys with the locked phones it might be a chance.
Good luck!!

hey you could try the ROMS here
http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/
they are pre rooted and come without radio.
but i think to use this u may need to have a patched recovery as these are in update.zip format. and i think(not sure) that only RUU works with goldcard.

Thanks, i managed to push recovery, without downgrading or gold card. worked fine... then root, then rom then radio... no PC! how cool!
Cheers!

avs333 said:
Guanarteme sorry I had qquite a lot of problems today, of another kind, women you know, sometimes it's a bit more involved...
As I understand, the way is to try some other ROM (they are plenty around here), why cling to that one? I had *a lot* of disasters so far, not of your kind maybe, still disappointing but *never* fatal.
Do make sure you have 100% charged the hero before any procedure! And be terribly cool, that thing is just a bunch of microschemes, it must not put you off, and you'll be victorious!
So my suggestion is to try other ROMs until you succeed. And of course you should not give up before you have a device which is ideal for you. You have already paid a lot of money for that!
The locked/unlocked state is simple, you see S-OFF instead of S-ON when you boot (as for the screenshot you've posted). I cannot overly appreciate the power of this SPL feature because my device was initially unlocked, but for you guys with the locked phones it might be a chance.
Good luck!!
Click to expand...
Click to collapse
.................
Hey avs333, hope women stuff does not put you down...
The hero stuff... well... it swallow your time, when the women is not around
But here we go, i fixed it. No downgrade, no gold card... just did a format to the card, pushed the latest recovery, and from there all was a beauty, up with fast root, and modaco 3.1, then radio, then hebrew fonts, and vualla! all is fine and kicking, and i did not use PC even (well except to download the ZIP file of the 3.1 rom from the net).
Thanks for your time anyways... take good care!

ROMS conflicting and a clean start

So, I flashed my frist rom back in April. I tried out the Energy Rom. Last night I tried out the Core Cell Evo Rom. This Rom started to give me trouble so I flashed to the current energy rom. I'm still new to this, so I think I may have made some kind of mistake that I'm not aware of.
I noticed that when I flashed to the new energy rom, the splash screen for the cell rom came up. Now whenever I try to change the date and time on my phone, it kinda locks up. I think it still functions, but because the screen is frozen I can't see what to press so I end up doing a restart. Does anyone know how I can remove all the remnants of the cell rom? I thought when you flash a new rom, it's supposded to completely get rid of the old rom?

First run TASK29, then flash preffered ROM, after that do HARD RESET, and then it must be OK

Some ROMs include a new splash screen, and some don't. The EnergyROM series doesn't include a splash screen, so that's why you can still see the Core splash screen.
You can find utilities to replace this if you search for "splash screen".
Task29 won't affect this (i.e. it doesn't touch the splash screen, nor the radio either), but it does a good job at wiping the ROM area itself.
If the problem still happens after a task29 and a flash (i.e. the lockups), then you should post about this in the thread relevant to the ROM you're running.

Thanks for the info guys. I'm at work but I'll try out the task29 thing when I get home. I didn't post this in the energy rom thread because I didn't want to seem like I was directing my problem at that rom until I had a good idea of what was going on. If the problems still persist, then that's where my next post will be.

You can always reflash a stock ROM. That will give you the original spash screen back and then you can flash the custom ROM again.

Well, it wasn't the splash screen that I was worried about. Seeing the splash screen made me think that the core cell rom was conflicting with the energy rom. After hearing what steviewevie had to say on the subject, I know otherwise. I'll also install a custom splash screen later now that I know that can be done to.

You can go here for the steps to change the splash screen its actually pretty easy and fun.
http://forum.xda-developers.com/showthread.php?t=576703

Ok, I ran Task29 and I've installed the stock rom. Do I need to do another HardSPL before I can flash a new rom?

No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it

creglenn said:
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
Click to expand...
Click to collapse
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.

sigma20xx said:
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
Click to expand...
Click to collapse
HardSPL was designed to stay on the phone, even if you flash stock ROMs. You have to specifically run the relocker utility (from the HardSPL thread) if you want to go back to the stock SPL (e.g. for warranty return).

MOD Note
I'm moving your thread to General. This has nothing to do with ROM development. Custom ROM usage yes, but not Development.
Russ741

[Q] Can't flash Hardspl after Kaiser immersion in water

First, the story: Kaiser / leaky shower / drip drip drip / RIP!
My kaiser has gradually come back from the dead after drying on my desk for a month.
I can no longer flash anything except the stock 6.1 winmo rom. I've tried all methods: SD & USB both work for the said stock rom but nothing else.
My tricolor screen reads: KAIS130/ SPL 3.28.0000 / CPLD-8
I'd like to flash android back on this thing but I can't Any clue?
I have mtty access too if it helps. When I flash anything through usb or SD card, I'm stuck at 0% or on the "loading screen".
I've read many threads here but no solution works for me. I'm not excluding the idea that something may have fried permanently in this kaiser so I'm more looking for some troubleshooting directions, to make sure.

Water immersion can cause a lot of problems, not so much from the water itself, but rather the deposition of metal across leads and junctions caused by electrolysis of the solder used to join components to the pcb.
Provided the damage is not too widespread it is sometimes possible to revive the device, however it requires a complete disassembly and careful inspection of practically every component and connection on the mainboard, and the careful brushing clean of any 'furry' component terminations or leads.
I am surprised that it actually boots and is able to be flashed with WM.
If it is a stock SPL then you will need to HardSPL it anyway, since it will not allow you to flash anything other than stock otherwise.
Note that as far as I am aware, 3.28 is a stock spl, rather than HardSPL which is usually 2.29 or above.
Another thing, have you tried running android from SD? I know it is not quite the same, but if it works on SD, there is no reason for it not to be nand'able

This is actually the second time my Kaiser has been drowned in water (first time is now referred to as "the 2009 faulty Roman air-conditionning incident" and it took 6months for the Kaiser to recover) and full disassembly and cleaning helped A LOT in both cases (green stuff inside). I can now say that my Kaiser is water-proof At least it's built like a tank - except for the cheap breakable plastic shell.
I tried so many complicated solutions that I didn't even try android on SD I'll look into it tomorrow.
PS: Latest stock rom from Hong Kong can't be flashed ("not allowed"), only my French rom is flashable.

Provided you can flash something 6.1 you can run android from SD, and also should be able to HardSPL it to allow flashing of other roms, including the android nand boot nbh.
I think it's incredible that your kaiser has survived this twice, I'd take good care of it from now on, third time you may not be as fortunate

coincoinlapin said:
First, the story: Kaiser / leaky shower / drip drip drip / RIP!
My kaiser has gradually come back from the dead after drying on my desk for a month.
I can no longer flash anything except the stock 6.1 winmo rom. I've tried all methods: SD & USB both work for the said stock rom but nothing else.
My tricolor screen reads: KAIS130/ SPL 3.28.0000 / CPLD-8
I'd like to flash android back on this thing but I can't Any clue?
I have mtty access too if it helps. When I flash anything through usb or SD card, I'm stuck at 0% or on the "loading screen".
I've read many threads here but no solution works for me. I'm not excluding the idea that something may have fried permanently in this kaiser so I'm more looking for some troubleshooting directions, to make sure.
Click to expand...
Click to collapse
if you flased the 1.65 radio version i have heard people having issues with it. i think somewhere on this forum there are instructions to get a different version on which wil then reopen your ability to flash the custom roms.

Yes
ghghgh14702 said:
if you flased the 1.65 radio version i have heard people having issues with it. i think somewhere on this forum there are instructions to get a different version on which wil then reopen your ability to flash the custom roms.
Click to expand...
Click to collapse
Radio could interrupt some things. But then again, with jumpspl or sspl (dont know which one is correct, the one with the froggy icon) makes you go into bootloader mode from ram if im correct. You should be able to hardspl then...

The radio version which does that is 1.65.17.10, which is not available from the Ultimate Radio Thread, for that very reason, it is only that particular radio, not the other radios in the 1.65 series that causes the problem.
I am using the 1.65 radio in my sig, and have flashed and reflashed many times, with no problems.

zenity said:
The radio version which does that is 1.65.17.10, which is not available from the Ultimate Radio Thread, for that very reason, it is only that particular radio, not the other radios in the 1.65 series that causes the problem.
I am using the 1.65 radio in my sig, and have flashed and reflashed many times, with no problems.
Click to expand...
Click to collapse
sorry, knew it was one of the 1.65, since he said he flashed an official rom if he has 1.65 it will be that version so I didn't look up the complete version as that was enough info for him.

I was too optimistic...The Kaiser recovered only for two days - I tried haret to load Android from SD, but it hung at some point.
Now there's a new error message, which also appeared after the first drowning: The sim door is open ... device will shut down in 10 secs. ZAP!
@MathijsNL
I'll have to look into your Froggy thing

[Q] General rooting and ROM questions

Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks

http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!

Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?

K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.

did you debrand? http://forum.xda-developers.com/showthread.php?t=835777

Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!

Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!

Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.

deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.

makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.

redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?

G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF

i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.