Develop Bugs

[Q] Why Won't Myn's Rom Flash?

This is almost the 4th time I have tried flashing this rom. Never gets past the Evo 4G white screen at all. I have tried 3 different ways.
Clockwork (2 different versions)
RA
Download through Rom Manager
I then tried flashing CM 6.1 just to see if it would work and it worked just fine. I am downloading the file from the Myn official thread. It's Rls 4. Seeing how big the thread is and all the people using it, I know it works for tons of people.
I do all the steps as in wipe all the data and everything.
Any ideas on what could be the problem?

barats said:
This is almost the 4th time I have tried flashing this rom. Never gets past the Evo 4G white screen at all. I have tried 3 different ways.
Clockwork (2 different versions)
RA
Download through Rom Manager
I then tried flashing CM 6.1 just to see if it would work and it worked just fine. I am downloading the file from the Myn official thread. It's Rls 4. Seeing how big the thread is and all the people using it, I know it works for tons of people.
I do all the steps as in wipe all the data and everything.
Any ideas on what could be the problem?
Click to expand...
Click to collapse
The RLS4 does not work well with the new radios..did u update your radios? Also if you did RLS5 is coming out very soon which does work with the new radios. If that is your situation I would recommend flashing a 3.70 rom that is out until RLS5 comes out. If you didnt update your radios i would ask in the myn thread about your situation. Lots of developments lately with recoveries and Hboots that you may want to look into to make sure you are runnig the correct recovery for your evo.

Actually I did update my new radios. When I probably should not have. My build is 3.3 and I had the 1.9 PRI and it caused my phone to stay in 100% wake and drain the battery constantly even with no use. Went back to 1.7 and it worked like a charm.
How can I flash back down to an older version radio? I have not tried this and I believe this may be the problem

Thanks man!!
Installed the older radio version and it started up like a charm!

barats said:
Thanks man!!
Installed the older radio version and it started up like a charm!
Click to expand...
Click to collapse
What version?
Sent from my PC36100 using XDA App

barats said:
Thanks man!!
Installed the older radio version and it started up like a charm!
Click to expand...
Click to collapse
Glad I could help dude

gqstatus0685 said:
What version?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
last OTA update upgraded the radios for the evo...look in android development you can find caulkins thread about the new radios. He has an all in one package that can upgrade your radios or downgrade if need be.
edit: Look in my sig the updated wimax link

[Q] GPS issues

new to rooting and flashing roms. there is onw problem I am having. When I flash a rom gps suddenly goes out the window, none of the indicators pop up in the notification bar, maps and navigation have a problem finding my location, and most of the time my phone doesn't know where I am. Now if I unroot back to stock everything goes back to normal which is weird to me but what I would like to ask the community is that, What can I do to fix this issue? Do I need to flash a fix or is there nothing I can do?

I'm sure you've already done this but you did go in to your location settings menu and checked the ones that apply? I haven't heard of this and it must not be a hardware issue if it works fine on stock..

that's what I thought... honestly I haven't tried all the roms (mostly just the stock roms) but I have flashed at least four, all with the same results. I would just keep it stock so I have a fully working phone but the only unrooted flash I know of is on the Unlockr site which will unroot it back to 2.1 and I don't know if I can live that far in the past

The other weird thing is in locations there is an option for location on and E911 . The E911 is checked on and it says that E911 cannot be checked off on any mobile device. Ask the other times it gives me an option. I am currently running Magnolia Final's latest version
Sent from my ADR6300 using XDA App

Check out berzerkers get back to stock thread in development. It has get back to stock instructions
LiquidLight RC 1.1
invisiblek #28
Amoled

Cryous said:
Check out berzerkers get back to stock thread in development. It has get back to stock instructions
LiquidLight RC 1.1
invisiblek #28
Amoled
Click to expand...
Click to collapse
will it be stock 2.1 or froyo?

automaddux said:
will it be stock 2.1 or froyo?
Click to expand...
Click to collapse
I have a stock froyo Ruu that you flash through hboot If you want it
Sent from my ADR6300 using XDA App

newtoroot said:
I have a stock froyo Ruu that you flash through hboot If you want it
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
sure thanks man

automaddux said:
sure thanks man
Click to expand...
Click to collapse
when I flash through hboot should I wipe as if I'm flashing another rom? I flashed a 2.2 ruu before the OTA went out and I ended up bootlooping and everything forced closed on me. I think that's what made me root in the first place.

where do i go to get it

Having the same issue my GPS has not worked for like the past 6 months if anyone has found a fix to the problem. I'm running lous #8 the new evo radio .04.08
Sent from my ADR6300 using XDA App

Can't get ROM's to flash, can someone help?

I picked up an Epic today, and for the life of me, I cant seem to get things to flash right. I'm no stranger to this sort of thing (G1, MTS, HD2, NS4G)... but this phone is just giving me trouble.
First time I tried things, I followed everything here: http://forum.xda-developers.com/showthread.php?t=1091680
The oneclick worked without a problem, the rom appeared to flash fine in clockwork, but would not boot. I'd get the samsung logo, then a black screen, and there i'd sit. Couldn't get past it. After several wipes and reflashes, I decided to start over and Odin back to stock.
So now, on round two, I followed this instead: http://forum.xda-developers.com/showthread.php?t=1076967. Same idea, just, as I understand, a newer version of clockwork? Again, root and clockwork installed fine. I followed the instructions to convert to EXT4 to the letter, which all went without error. I then flashed this: http://forum.xda-developers.com/showthread.php?t=873347. I made sure to get the EXT4 version. Flashed, rebooted, and it gets stuck at the Samsung logo.
So, odin back to stock again. Can anyone help me try to figure out what I am missing here? I've followed all instructions completely to the letter, and the best I can tell I'm using the correct roms. Any ideas?

Maybe simple, but I know in the clockwork menu when you are flashing the rom there are two choices that look similar. One is update and one update from zip. Make sure you are choosing the right one.

Atlienzz said:
Maybe simple, but I know in the clockwork menu when you are flashing the rom there are two choices that look similar. One is update and one update from zip. Make sure you are choosing the right one.
Click to expand...
Click to collapse
I'm choosing the right one. I've got plenty of experience finding my way around clockwork, which is why i'm so baffled as to why this isn't working. I'm no stranger to the steps involved here. Either I'm not understanding something, or i'm flashing the wrong roms. Just trying to figure out where i'm going wrong.

What ROMS have you tried?

Atlienzz said:
What ROMS have you tried?
Click to expand...
Click to collapse
Just two two linked in the first post.

So, I got the RFS version of Supernova to flash (but without root?). My problem seems to be lying within EXT4. Any ideas?

Viper87227 said:
So, I got the RFS version of Supernova to flash (but without root?). My problem seems to be lying within EXT4. Any ideas?
Click to expand...
Click to collapse
If you used CWM 3.0.2.5 it does not convert to EXT4. You have to run another script to convert before flashing an EXT4 ROM. You have to flash the ROM before booting right after the conversion.

Try running this script from CWM just make sure you have the ext4 room you want to use on the card LOL yes I have made that mistake DOH!
https://www.dropbox.com/s/2099ptlhb6wacs5/RFS2EXT4.zip

Try using clockworkmod 3.1.0.1 and flash sfr 1.1.1 again.... On sfr 1.1.1 do NOT wipe anything before you flash
Sent from my Evo Killer using XDA Premium App

tazfanatic said:
Try running this script from CWM just make sure you have the ext4 room you want to use on the card LOL yes I have made that mistake DOH!
https://www.dropbox.com/s/2099ptlhb6wacs5/RFS2EXT4.zip
Click to expand...
Click to collapse
Do this ^^^
Root with one click root CWM 3.0.2.5, then flash the above through clockwork. Then let it convert and after its done converting flash Syndicate Rom 1.1.1 right after

qbking77 said:
Do this ^^^
Root with one click root CWM 3.0.2.5, then flash the above through clockwork. Then let it convert and after its done converting flash Syndicate Rom 1.1.1 right after
Click to expand...
Click to collapse
Appears to have worked this time, its booting now. Thanks for the help guys!

Well... I broke it. I'm rather confused by how things work with this phone.
I did what ya'll said, and as told, did not wipe (despite reaaaally wanting to.) The rom booted and such, but I had lots of problems. I attributed this to lack of wiping. I really wanted a fresh go.
So, I decided to try again. I wiped and reflashed this rom. Now... won't boot again, just sits on a black screen. I don't get it. Why am I not allowed to wipe data when using this rom?

qbking77 said:
Do this ^^^
Root with one click root CWM 3.0.2.5, then flash the above through clockwork. Then let it convert and after its done converting flash Syndicate Rom 1.1.1 right after
Click to expand...
Click to collapse
+1 what he said also after u flash you might want to enable journaling
https://www.dropbox.com/s/ix6vr18uid3q4uh/JournalingOn.zip
Where your phone seems to be a little temperamental I would recommend it for the best experience.

It says on the rom page not to wipe... I didnt wipe coming from midnight rom and acs script took care of everything while flashing... I havent had one fc and no problems yet.... I wonder what the issue is
Sent from my Evo Killer using XDA Premium App

Decided to just completely start from scratch. I did exactly this:
Odin back to stock
One-click 3.0.2.5
RFS2EXT4
Flash SFR-1.1.1
Didn't wipe anything, this is ALL I did. This worked. I still don't understand why I had all this trouble in the first place? Is it the phone, or am I doing something I shouldn't? It seems like the issue is with wiping before flashing. So, what happens if I want to try a different ROM? I can't imagine I need to Odin back to stock every time...

tazfanatic said:
+1 what he said also after u flash you might want to enable journaling
https://www.dropbox.com/s/ix6vr18uid3q4uh/JournalingOn.zip
Where your phone seems to be a little temperamental I would recommend it for the best experience.
Click to expand...
Click to collapse
What does this do? Doing a google search gave me instructions on how to enable/disable journaling, but it's not a term i'm familiar with and nothing actually explained why I'd want to do this.

This issue is with stock EC05. It has something weird going on especially the OTA that requires wiping. Same for the new Bonsai release, wipes only needed colming from stock EC05.
Do you BONSAI?

Viper87227 said:
What does this do? Doing a google search gave me instructions on how to enable/disable journaling, but it's not a term i'm familiar with and nothing actually explained why I'd want to do this.
Click to expand...
Click to collapse
Journaling allows for the extra write to the phone so there is no corruption if you have to pull the battery or you drop it and the battery falls out. If it is not enabled then you might get a lot of FC's after replacing battery and booting up. Also FYI with this phone when you shut it off and the screen is black and the home lights are out it is NOT truly OFF until you fell the quick VIBRATION then it is truly off.
You shouldn't have to go back to stock each time but it seems that you might be having some other issue. You using the stock USB cable? Might want to get a good one from a store other then Sprint. Just a suggestion I have seen a ton of issue's related to the stock cable.

tazfanatic said:
Journaling allows for the extra write to the phone so there is no corruption if you have to pull the battery or you drop it and the battery falls out. If it is not enabled then you might get a lot of FC's after replacing battery and booting up. Also FYI with this phone when you shut it off and the screen is black and the home lights are out it is NOT truly OFF until you fell the quick VIBRATION then it is truly off.
You shouldn't have to go back to stock each time but it seems that you might be having some other issue. You using the stock USB cable? Might want to get a good one from a store other then Sprint. Just a suggestion I have seen a ton of issue's related to the stock cable.
Click to expand...
Click to collapse
No. I am using the cable from a Nook.

Viper87227 said:
No. I am using the cable from a Nook.
Click to expand...
Click to collapse
Ok as long as it is better than the stock one LOL

[Q] PC36IMG ERROR AT HBOOT.I think i have soft bricked my phone. NEED HELP. PLEASE!!!

HI. I AM FAIRLY NEW TO THE ROM FLASHING SCENE. HAVE BEEN SUCCESSFUL FOR THE LAST FEW MONTHS AT FLASHING ROMS. THEN I THINK I STEPED OUT OF BOUND AND BEGAN TO TRY FLASHING NEW KERNELS. HAVE BEEN SEARCHING WEB ALL DAY ON WHAT COULD HAVE HAPPENED. FROM WHAT I HAVE READ I MAY HAVE FLASHED A KERNEL FROM ONE MOD TO ANOTHER. OR POSSSIBLY INTERRUPTED THE ZIP INSTALL OR FLASH. NOW WHEN I TRY TO FLASH BACK UP ROMS THEY BOOT LOOP OR JUST STAY ON BOOT SCREEN. SAYS NO PC36IMG at the hboot screen. please help.

Are you using the newest HBOOT from HTC? I heard that you can't flash kernels on it...
Maybe the .zip didn't download completely. What kernel did you try to flash, can you even access recovery?

HBOOT 6.16.1002. i was flashing a tiamat kernel. didnt like it and when i tried another one is when it happened. not sure if i did all the wipes. was late and was getting tired

by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE

trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
well tiamat will not work on any mik rom that i know of because (all?) mik roms are sense roms. if its a sense rom then you need a sense kernel. aosp rom needs aosp kernel. go into recovery and flash a sense kernel. that should fix your bootloop

Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out

trevanti00 said:
by the way iwas running cynogen mod 7.1 rooted with revolutionary. when i flashed a few kernals some wouldnt work so i tried ra recoery and they installed. i then installed TWOP RECOVERY. TRIED TO INSTAL A MIK ROM AND THATS THE FIRST TIME I GOT THE BOOTLOOP AND IT WAS LIKE THAT EVERYSINCE
Click to expand...
Click to collapse
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium

-EViL-KoNCEPTz- said:
Twrp recovery more than. Likely killed your phone, if you had read the thread you would have known it is no longer supported for the evo for this very reason,as it has been known to permanently brick evos with no fix by screwing up the partitions
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?

Damn it. So am i screwed or is their a solution

trevanti00 said:
Damn it. So am i screwed or is their a solution
Click to expand...
Click to collapse
did your s turn back on after the bootloop ?

What did he do to fix it. Do you have a thread on that

I am s off

No it is still off

trevanti00 said:
No it is still off
Click to expand...
Click to collapse
then TWRP most likely didnt cause it. His situation was different from what your experiencing so what he did will most likely will be different from what youll have to do. Also if TWRP caused it you would be back to s-on

Well could you give it a shot and trouble shoot with me. I been at it eveery since last night

trevanti00 said:
Well im guessing that was the problem then. Well at least i know the source of the problem. Now can it be fixed. Can you give me a sense kernal to try out
Click to expand...
Click to collapse
here is one...http://forum.xda-developers.com/showthread.php?t=1496488

Flash amon ra in hboot and get off of twrp b4 u end up screwed first and foremost then try wiping everything in amon ra except sdcard and battery stats and flash a new rom and see if it will boot up if you can't get recovery to load you may need to try running an ruu and starting from scratch
Sent from my PC36100 using xda premium

evo4gnoob said:
1 survivor i know of and that is the great captain_throwback . Whats with all these bricks lately lol?
Click to expand...
Click to collapse
Ppl not reading enough or rushing thru things is my guess *shrugs*
Sent from my PC36100 using xda premium

ok trying that now.

problem solved. thank you guys a million times. i knew i would run into a brick sooner or later. lesson learned. i have always read all the post before flashing but was tired and got lazy. will never happen again. again THANK YOU GUYS.

Boot loop after revolutionary

Hey guys,
I just got a Incredible 2 and started the root/s-off process.
First I had to downgrade it to 2.3.3 and then ran revolutionary. All worked fine and I even installed the CWM.
The problem is that now it gets stuck on a pretty weird boot loop.
Every time I install a new ROM (stock or not) it boots and everything works fine. But as soon as I turn it off, it gets stuck on this infernal boot loop and the only way for it to stop is flashing a new ROM and doing it all over again.
Anyone has any clue what this could be?
Thanks
Ariel

Are you doing a full wipe? Do you have the latest radio? That is needed with the new firmware 6.xxx
Sent from my Incredible 2 using xda app-developers app

Solved it...
I was doing a full wipe and I had the latest radio (1.09.01.0722). Aparently this was the problem.
I found an older radio (1.09.01.0322) and some guy saying that I needed it if I started having bootloops. And it works!
Thanks tho

Yntarius said:
Solved it...
I was doing a full wipe and I had the latest radio (1.09.01.0722). Aparently this was the problem.
I found an older radio (1.09.01.0322) and some guy saying that I needed it if I started having bootloops. And it works!
Thanks tho
Click to expand...
Click to collapse
LOL that's the newest one.

sjpritch25 said:
LOL that's the newest one.
Click to expand...
Click to collapse
Yeah, the naming is a little odd, I think it's supposed to be the month created then the year, but obviously .0622 and .0722 didn't follow that. .0312 is the latest (March 2012).

Dont use revolutionary
Try using another root method. Do it manually if you have too. I don't remember how i rooted my inc2 but it wasnt with revolutionary. Ive had it forever so the root methods may have changed. Just try a different method and see what happens.