Related
Hi guys!!
I'm really desperate.
Today I installed copilot 8, after a while the phone when goes in standby doesn't wake up anymore. When I press the menu button it remains down.
So I tried to reflash myhero 1.1.2 but in vain, and if I try to wipe I get the boot loop on hero logo.
The rotation doesn't work.
Please help me!!!!
Format your ext partition, wipe and flash again.
I use copilot 8 and the same ROM and I haven't that kind of issues on the full version of myhero v1.1.2! On a previous version on the 2.6.29 kernel when never I closed the copilot 8 the system crashed. Then I flashed the red's HTC kernel 2.6.27 and the issue never happened to me again. On this new version, the GPS is working fine for me! I just installed a fresh and clean ROM..
Do you deleted the save folder on the copilot 8, before re-installing the app or it was a fresh install? Is mandatory whenever you re-install the app.
When you install it, be sure you don't have this folder, no matter what is the situation!
Edit: I didn't read the second part of your issue.. Evil is right.. no other solution
It was the first install!
It can be a kernel problem?
Evil, when I try to wipe it goes in loop with the hero logo, do you think that formatting will work?
eViL D: said:
Format your ext partition, wipe and flash again.
Click to expand...
Click to collapse
I did it!
I also tried to change kernel with the three different versions but the problem is still alive!!!
Something new?
daeron666 said:
Something new?
Click to expand...
Click to collapse
I had this prob too.. after my micr sd card was set as damaged by the android sys and i wasn't able to start the device as well. But, the device was able to boot without the microsd card. Try it too. If so backup the information in your pc and format and remove the partitions of the microsd card (if you didn't do it before)!
I tried it, but the bug remains, I think it's something in the OS...
daeron666 said:
I tried it, but the bug remains, I think it's something in the OS...
Click to expand...
Click to collapse
My friend, the best solution is really to try it..install other rom, just for testing! ,,at least to have something to work on it.. step by step.. I use the same ROM, the newest version of copilot (and I previously was with olders ones without prob too), swapper, overclock, 2.6.29 red's kernel (without BFS), Engineered SPL, no radio changes, bla bla..
Gives a description of what is the state of your gear..
I already started to think that it can happen that some piece of hardware on the device is broken, but lets see.. no false alarms,,
Let's try to understand the status!
Of course! I have a 32a with no radio update, engineering spl 2010 and .29 kernel bfs. I Aldo tried without bfs but in vain.
The last thing left to do is trying another ROM....but there's a low level formatting method?
daeron666 said:
Of course! I have a 32a with no radio update, engineering spl 2010 and .29 kernel bfs. I Aldo tried without bfs but in vain.
The last thing left to do is trying another ROM....but there's a low level formatting method?
Click to expand...
Click to collapse
If there is, it was never spoken here.. the only way I see the internal phone partitions formating is when applying a new room...
Remove the sdcard/copilot directory and reinstall copilot
OR
Format your SDcard and reinstall copilot
Amon_RA said:
Remove the sdcard/copilot directory and reinstall copilot
OR
Format your SDcard and reinstall copilot
Click to expand...
Click to collapse
My friend, I think he tried that!
ricardomega said:
My friend, I think he tried that!
Click to expand...
Click to collapse
Yes of course, I tried that!
I also tried several roms, but nothing changes!
What can I do?
I'm really desperate.
daeron666 said:
Yes of course, I tried that!
I also tried several roms, but nothing changes!
What can I do?
I'm really desperate.
Click to expand...
Click to collapse
But without the copilot no issues, right? I'm using the copilot v8.0.0.328 kfc3.0 and you??
Excuse me, I'll explain better:
The problem is ALWAYS, with or without copilot, with or without sd...
daeron666 said:
Excuse me, I'll explain better:
The problem is ALWAYS, with or without copilot, with or without sd...
Click to expand...
Click to collapse
No need for excuses.. Man, "just" in my opinion.. you might have some broken hardware on your device.. I can't find any other answer. Flash back everything original like it should be and send it to warranty. There's SPL collections, there's original ROM's from HTC, etc etc..
I'm sorry.. I'm unable to help you.. Maybe someone has other idea, or something, but in opinion you a broken device..
Removed at the request of the dev, official release will be available soon !
Ok the second link isn't working, so my best solution is to use the original recovery image, that you used to have, to do this i simple rerooted my phone, and pushed the flash file and it worked perfect, no errors or fc's so far!
The ROM link has been killed by MediaFire.... reup?
http://www.mediafire.com/?jjmm3nczjog
MediocreHippie said:
http://www.mediafire.com/?jjmm3nczjog
Click to expand...
Click to collapse
That's the recovery.... not the ROM image. It's only 33 MB??
bagpipes88 said:
That's the recovery.... not the ROM image. It's only 33 MB??
Click to expand...
Click to collapse
That's actually it!
Which link, darchs rom ? or is it the second link, i know for a fact that the second link doesnt work, all others do
bagpipes88 said:
That's the recovery.... not the ROM image. It's only 33 MB??
Click to expand...
Click to collapse
No, that's it. The FroYo ROMs are tiny.
Holy crap, i thought because it simply said recovery it was the recovery image, not the entire rom. well my sd card will thank me!!!!!
yea it works, the froyo rom is small, thats why it runs so smoothly on your device
Not bad, although I'll personally be waiting for some of the bugs to be fixed before I head on up to Froyo.
Looking forward to it
EDIT: Dongs.
IF ANYONE runs into a "sd card no mounted" " no sdcard" problem you need to wipe the ext. part of your sd card if you have one, also remember to wipe before beginning a new rom flash, do the nanadroid backup and wipe dalvik cache for saftey just in case
does this change your hboot and make it impossible to go back to 2.1?
New GoogleShits by CarbonKang
balistc said:
New GoogleShits by CarbonKang
http://www.4shared.com/file/t-ASRmfg/GoogleShitz.html
Click to expand...
Click to collapse
what is different in this one? So I may update the post with it
ima wait to were the bugs are fixed(well some one big one camera but this is BIG) lastly anyone thing this will evenly be put into a flash-able rom(with our recovery images)
neuro_genesis said:
does this change your hboot and make it impossible to go back to 2.1?
Click to expand...
Click to collapse
Not necessarily, this removes the RA you have currently, and it will act as if you are "unrooted"
ajnavarro said:
what is different in this one? So I may update the post with it
Click to expand...
Click to collapse
this removes the wrong build.prop file
ajnavarro said:
what is different in this one? So I may update the post with it
Click to expand...
Click to collapse
Quote CarbonKang: Here I fixed up the GoogleShitz a bit. Don't forget to wipe data. Also since I'm on darchdroid and i cant test can someone tell me if it is now showing flash and such.
They said the original had problems??
Hi guys & gals.
I am a keen flasher, even an OCRF http://forum.xda-developers.com/showthread.php?t=823702
But restoring all your themes & 170+ applications could take me a better part of half a day, hence I was apprehensive.
Well, this time around I tried something different. IT WORKS. No need to backup your settings. No need to Factory reset, Wipe data before hand. DONT DO THEM. No need to remove your old lagfix (Sztupy's 0.3 ONLY). No need to remove your tweaks. No need to backup your apps & whatelse.
Here is what I did, Went into Recovery, checked which lagfix I was using, what tweaks were turned on, noted them down.
Downloaded V7, put it on my sdcard as update.zip, went into recovery & applied update.zip.
When my phone rebooted into recovery, I went back & reapplied all my settings. Lagfix & tweaks.
When I restarted, everything was as it was 3 minutes ago, but only with V7. I mean NOT A SINGLE FC, everything in its place, & believe me I have a VERY costomized 5 pages of ADW with 170+ apps, 800+contacts, 500 log entreis for calls, sms APN settings, JUST EVERYTHING..
I hope this helps someone.YOU CANT HOLD ME RESPONSIBLE IF IT BREAKS YOUR PHONE. This experience is being shared with good intentions.
I am very sure its Sztupy's modified CWM that makes this possible.
Check the last few posts in Doc_Kalpik's post, they are painfully, undoing the lag fix, backing things up, flashing & then restoring. 6 hrs of life GONE.
IF IT HELPS SAY IT HERE, might help others.
OK, after testing this method for 7.5 hours, here is my revised review. Before I did this, My gmail, sms, noLED & a lot of other apps were giving me FC's, Now thats GONE. The market was totally unreliable, starting the download, doesn't finish, downloads get linked, (that was the worst) & all sorts of issues. MARKETS NOW WORKS FLAWLESSLY.
EarlZ confirms that using this method he has come from V5.1.1 to V7 without issues.
Nice one. I'll give it a try.
you where on doc's-kalpik v6 before ?
Cypher_X said:
you where on doc's-kalpik v6 before ?
Click to expand...
Click to collapse
Yes,
No need to Factory reset, Wipe data before hand. DONT DO THEM.
I am a happy OCRF now.
The same can be done from v5.x doc_kalpik roms.
But as usual, backup first, better safe than sorry
DocRambone said:
The same can be done from v5.x doc_kalpik roms.
But as usual, backup first, better safe than sorry
Click to expand...
Click to collapse
standard procedure for me
well Ragin ... maybe i AM an OCRF
phone is charging right now and as soon as it reaches 100 i'm gonna go for it!
Can't wait anymore
lol
better to disable lagfix before (specially the dbdata != rfs).
if u need to reflash with odin and dbdata is not rfs, it will be wiped.
thoriig said:
better to disable lagfix before (specially the dbdata != rfs).
if u need to reflash with odin and dbdata is not rfs, it will be wiped.
Click to expand...
Click to collapse
Not Needed. I did it without.
Understand I was on Doc_kalpik's V6 & came to V7.
Cypher_X said:
standard procedure for me
well Ragin ... maybe i AM an OCRF
phone is charging right now and as soon as it reaches 100 i'm gonna go for it!
Can't wait anymore
lol
Click to expand...
Click to collapse
This is meant for the vast majority who really follow word by word the written instructions on the ROM's first post.
Check the last few posts in Doc_Kalpik's post, they are painfully, undoing the lag fix, backing things up, flashing & then restoring. 6 hrs of life GONE.
Yea Ragin thanks for the info, it works! Just to share, i'm fr V6 Advance ext4. Now waiting for the battery mod to be released
ragin said:
This is meant for the vast majority who really follow word by word the written instructions on the ROM's first post.
Check the last few posts in Doc_Kalpik's post, they are painfully, undoing the lag fix, backing things up, flashing & then restoring. 6 hrs of life GONE.
Click to expand...
Click to collapse
6 hrs of life gone lmao!
¤Sent live and direct from my¤
¤SGS GT-I9000¤
¤GMT+0¤
pele78 said:
6 hrs of life gone lmao!
¤Sent live and direct from my¤
¤SGS GT-I9000¤
¤GMT+0¤
Click to expand...
Click to collapse
6 Hours of life gone waiting to see if SH*T happens, then start all over.
ragin said:
6 Hours of life gone waiting to see if SH*T happens, then start all over.
Click to expand...
Click to collapse
Haha I know, its such a common thing.
¤Sent live and direct from my¤
¤SGS GT-I9000¤
¤GMT+0¤
hi guys
one question
do you use CWR for back up or other app
So if its done we rename it via update.zip and use 2e recovery nothing gets wiped as compared to the choose zip file from CWM ?
EarlZ said:
So if its done we rename it via update.zip and use 2e recovery nothing gets wiped as compared to the choose zip file from CWM ?
Click to expand...
Click to collapse
IF you are running Doc_Kalpik's v6 with ULK, you can switchover to V7 by this method. Yea, remane it as update zip, enter into Sztupy's CWM, flash sdcard:update.zip
yup works. but i went to choose the .zip file to flash. works the same. (as long as the kernel supports the same filesystem as you have chosen for the lagfix, then all will be well )
sunwee said:
yup works. but i went to choose the .zip file to flash. works the same. (as long as the kernel supports the same filesystem as you have chosen for the lagfix, then all will be well )
Click to expand...
Click to collapse
I guess I am gonna stick with Sztupy's ULK no matter what FW I chose in future.
ragin said:
IF you are running Doc_Kalpik's v6 with ULK, you can switchover to V7 by this method. Yea, remane it as update zip, enter into Sztupy's CWM, flash sdcard:update.zip
Click to expand...
Click to collapse
Im at v5.1.1 so no go ?
EarlZ said:
Im at v5.1.1 so no go ?
Click to expand...
Click to collapse
Try it brother, it should work, if it works, I will mention it on the first post with your name.
Thought I'd better post this before everyone flashes these sbfs and looses downgradability (is that a word?)
So as you may have worked out this process is if you have never flashed a non downgradable .sbf i.e you have never flashed 2.51 eclair or the 2.2 GB/US 2.2 froyo. If you flashed these then this won't work for you and youve lost downgrability.
Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here
Need the system.img nandroid and boot/devtree.sbf – Download here
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear
• Flash the Chinese .sbf by RSD lite
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder)
• Once restored pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done.
If you want to use the GB release then just restore the system.img from the GB release.
Enjoy and don't get locked in peoples.
Thanks to adlx whom I enjoyed working with to figure this out - team effort! +as always Sorensiim for the hosting!
I don't think you actually need to flash anything other than boot/devtree.
I tried TMO with uk2.51 and it was just fine.
And if someone followed your post exactly as it is now. Chances are they'd
get their phone bricked (since many are already on 2.51).
Easy to fix for sure, but since it is most likely meant for less experienced
users, we really don't want that, right?
BTW
Thanks for writing it up.
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
EDIT: Credit goes to adlx, as it was his file (mis-remembered...should have known better from the file name though). Using Higgsy's instructions and links and adlx's update, I now have a working working US 3.42 with the Motoblur setup bypassed. Thanks to all those who made that possible.
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
No you can't. Nandroid backup and/or SBF won't do anything on that front.
As I am on the UK sbf, this will not be of much use to me. Thankfully, I have no issues with that sbf, so I do not need this.
That said, thank you from those who do.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
what do you mean by "on that front"?
means that fix package consists some fundamental codes that had thoroughly change the hardware control? and nandroid backup as well as SBF could not overwrite that part?
Forgot to put in the post this is if you have not flashed a non downgradable .sbf before, although I would have thought people would be able to work that out by the nature of the thread.
This will work and will fix you cam flash if you are coming from 2.21+2.35 Eclair ROMs or 2.2 Chinese ROM where you haven't flashed a non downgradable .sbf
Higgsy said:
If you want to use the GB release then just restore the system.img from the GB release.
Click to expand...
Click to collapse
Can you provide a link to that image?
Raccroc said:
Quick question for you Higgsy...
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I never posted that! and I never used that fix! On the US 3.4.2 you can't skip setup, on the GB 3.4.2 you can skip set up.
conradlyn said:
sorry to bother, but as I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?
and thank you for your work....
Click to expand...
Click to collapse
If you never installed a non downgradable sbf as per the updated op then yes.
racca said:
No you can't. Nandroid backup and/or SBF won't do anything on that front.
Click to expand...
Click to collapse
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Raccroc said:
On one of the original T-Mobile Froyo threads, you posted update files to bypass the Motoblur Setup ("Skip_Blur_adlx-signed" worked fantastically...much thanks!).
Are those modifications included in these posted files already?
EDIT: Went ahead and tried it both with and without the update. Answer is that you cannot skip Moto Setup with this install; however, the Skip_Blue_adlx-signed update will allow you to if the update is applied before leaving recovery.
Click to expand...
Click to collapse
I think I did post this Skip_Blur_adlx-signed, as I'm adlx lol (although I'm registred here as adlxdum). And yes, it has to be flashed RIEGHT AFTER restoring the nandroid, as I stated. (I can't find the post...)
EDIT: was http://forum.xda-developers.com/showpost.php?p=10930470&postcount=149
Thanks mate, my DEFY is perfect now.
Muznyu said:
Thanks mate, my DEFY is perfect now.
Click to expand...
Click to collapse
Whoop!!!!!!!!!!!!!!!!!!!!!!
Higgsy said:
If you never installed a non downgradable sbf as per the updated op then yes.
Click to expand...
Click to collapse
too bad that you didn't mention this when the post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
conradlyn said:
too bad that you didn't mention this when post was originally created. when i see this answer, my defy has already been stuffed with 2.2 GB.
Click to expand...
Click to collapse
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Higgsy said:
My advice to anyone when something new comes out (not that its any consolation I'm sorry) is to sit back and watch how things pan out, rather than jumping in.
Click to expand...
Click to collapse
i also tried to hold on to this rule even before i bought my defy, but just can't reject the temptation of new ROMs...
you couldn't imagine how much i hate myself now, damn!
i could only pray for a real fix on the flash light by great guys like you, Higgsy
Higgsy said:
appriciate you helping people mate, but let me answer the questions that people have on a procedure that I have written #justsayin
Click to expand...
Click to collapse
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
racca said:
I might have misread the question
What I meant was that this is not likely to fix the green light problem,
which is not what's asked obviously.
Click to expand...
Click to collapse
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Higgsy said:
It does fix the green light problem, I wouldn't have posted it if I hadn't spent hors testing to find a fix for the problem lol
Click to expand...
Click to collapse
man, it is astonishing to see that it does fix, it seems that the green light indeed could be fix. but how?
is it only can be done by your operation procedure, or some independent files could be ported and flashed to fix?
Thanks a lot Higgsy. I'll try your turorial. Could I translate your topic to put it on a French forum ? (i'll put a link to the original thread)
So I have a small problem with my One S (S4).
Whatever ROM I flash I also have to flash fastboot boot.img wheter it's really needed for the ROM or not.
But that's not all.
Every time I want to reboot my phone, whatever ROM it is.. i get stuck in a bootloop and I have to fastboot flash boot.img again.
So basically I can't reboot/restart my phone without connecting it with USB and fastboot..
Really. Not even 1 reply?
Thats what I get for waiting a week and not bumping the thread awesome
I think you got no responses cause this is covered everywhere from OP's to many posts on it in the threads. So, unless I misunderstand your post, you have to flash the boot image all the time if you are on hboot > than .09. Or, you will bootloop. If this is what is happening you need to read up more in the threads before flashing the rom. Also, highly recommend you wipe system along with data and caches before flashing new rom.
Good Luck on it--
rugmankc said:
I think you got no responses cause this is covered everywhere from OP's to many posts on it in the threads. So, unless I misunderstand your post, you have to flash the boot image all the time if you are on hboot > than .09. Or, you will bootloop. If this is what is happening you need to read up more in the threads before flashing the rom. Also, highly recommend you wipe system along with data and caches before flashing new rom.
Good Luck on it--
Click to expand...
Click to collapse
Ya I think you did misunderstand because it sounds like it works but each time he reboots he needs to flash boot.img again which is odd.
HD2kty. said:
Really. Not even 1 reply?
Thats what I get for waiting a week and not bumping the thread awesome
Click to expand...
Click to collapse
No need for the comment like that more so when no one really knows what's up but try Flash Image GUI to flash the boot.img and see how things play out.
Thanks guys !
HD2kty. said:
Thanks guys !
Click to expand...
Click to collapse
So is it fixed then? and if yes how?
Darknites said:
So is it fixed then? and if yes how?
Click to expand...
Click to collapse
Yeah, missed the "every reboot" comment--sorry
If you did resolve it HD2kty, good to let us know so someone else may be helped.
Hope you did get it sorted. Only thing left would be to reformat sdcard and see. As long as you were wiping system also--