Database Users

ClockworkMod Recovery and Modaco's "Paul's Rom

Has anybody TRY flashing Modaco's "Paul's Rom" after ClockworkMod Recovery ? Do we have a green light to do so, or should we wait for further instructions ?
Thank you all.

I am not sure if this is safe yet since it is a different region. Wait until someone confirms though.

yvyv said:
Has anybody TRY flashing Modaco's "Paul's Rom" after ClockworkMod Recovery ? Do we have a green light to do so, or should we wait for further instructions ?
Thank you all.
Click to expand...
Click to collapse
he posted the download in the vibrant forum they have over there.. i'll test it

I'm actually a Modaco add-free member from my nexus one days but I don't see a " U.S Vibrant " section, he does how ever has a GalaxyS, I wonder if we good, I think paul is out for the weekend but I have a feeling we good to go..

Where is there a Vibrant forum? I only see a Galaxy S one on his site.

BigWorldJust said:
Where is there a Vibrant forum? I only see a Galaxy S one on his site.
Click to expand...
Click to collapse
i don't really remember where he posted it,
but i downloaded it and am gonna try it..
i'll look and see if i can figure out where it was

This is a holding topic for discussion of ROM compatability with the Samsung Vibrant / Captivate devices (Galaxy S variants).
I don't see any major reason why ROMs wouldn't be compatible, but I guess we'll find out soon enough. I may look into picking up a Vibrant so I can test future ROM releases on it.
Anyone have anything to add?
Click to expand...
Click to collapse
http://android.modaco.com/content/s...m/314109/vibrant-captivate-rom-compatibility/
Posted on Jul 21 2010, 20:04

alright flashing one of his deodexed versions that he posted in a thread for the vibrant
wish me luck..
if it works i'll find the link for you guys

link to modaco roms for vibrant
for those of you who wanna test it out.. booted up for me but i'm looking into functionality right now

How is it working?
Sent from my SGH-T959 using XDA App

rizzxx7 said:
How is it working?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Seems kinda like the one from MS_guru.. except a little more stable
i haven't been getting all the random reboots that are on ms_gurus, it still is buggy when you plug it into the computer (goes to the MTP Application.. ugh), wifi is working well (except rom manager still won't let me flash recovery through there because it says the wifi isn't stable enough or something), its pretty fast but i'd rather a stock rom than this
i noticed on that page i linked you guys to that they had a link for a download to a stockrom2.1.zip.. i'm going to test that one out as well

I am at work waiting for the word that its a go cause this stock build is killing me! Keep us posted!
Sent from my SGH-T959 using XDA App

one of the links provided has a thread where someone flashed this on a Vibrant and it stuck on boot.
Looks like Ryanolson7 has already gotten past that issue.. should work but I too will wait to hear
Made a backup in the mean while using nandroid and bought the premium version of Rom Manager to support Koush.

ryanolson7 said:
Seems kinda like the one from MS_guru.. except a little more stable
i haven't been getting all the random reboots that are on ms_gurus, it still is buggy when you plug it into the computer (goes to the MTP Application.. ugh), wifi is working well (except rom manager still won't let me flash recovery through there because it says the wifi isn't stable enough or something), its pretty fast but i'd rather a stock rom than this
i noticed on that page i linked you guys to that they had a link for a download to a stockrom2.1.zip.. i'm going to test that one out as well
Click to expand...
Click to collapse
If you have Recovery installed "update.zip" you don't have keep going back to rom manager and worry about "wi-fi" issues any more because is already installed in your system, just download quick boot from the market, allow su permision, reboot in recovery click reinstall packages and in 1 second you there...

The stock rom on that site is MS_gurus, not the real tmobile stock

yvyv said:
If you have Recovery installed "update.zip" you don't have keep going back to rom manager and worry about "wi-fi" issues any more because is already installed in your system, just download quick boot from the market, allow su permision, reboot in recovery click reinstall packages and in 1 second you there...
Click to expand...
Click to collapse
well i have recovery working by just going into stock recovery and flashing update.zip (clockwork recovery) but i was just testing out some ROMs that had potential to work on vibrants
rsfaze said:
one of the links provided has a thread where someone flashed this on a Vibrant and it stuck on boot.
Looks like Ryanolson7 has already gotten past that issue.. should work but I too will wait to hear
Made a backup in the mean while using nandroid and bought the premium version of Rom Manager to support Koush.
Click to expand...
Click to collapse
well that was a .zip of pauls rom that was themed as stock android.. i got the other one to boot called 'GalaxysDeodexed'.. still isn't stock quality though
do you guys know if we can flash his nandroid to our phones so we can have stock? if so, rsface, you should upload your nandroid somewhere and link us to it.. if you're willing to.. because the 'stock' roms out there are crap.. not even close to stock.
daweedk1991 said:
The stock rom on that site is MS_gurus, not the real tmobile stock
Click to expand...
Click to collapse
hopefully its not... they had it in a zip so it MIGHT not be his.. but i did see a link that links to MS_guru

oh and if you guys wanna get back to stock
check out this thread
http://forum.xda-developers.com/showthread.php?t=734475

Ryan, where did you put the .zip file ? SD card internally in the phone or external/removable card where movie and other stuff came..
Please be specific.
Thank you..
-------------------------------------
Sent via the XDA Tapatalk App

[Q] got new vibrant update worked fine, should i?

Ok, after the last tmo/samsung update bricked my vibrant i got my replacement left it stock and let it update. it worked fine. Question is, should I root, incase they send another update i cannot refuse and it bricks my phone again. It's just that the lag fix makes it twice as fast. But i don't like bricked phones.

Root
Clockwork
Backup
Flash Fusion
Enjoy
# no lag fix #

s15274n said:
Root
Clockwork
Backup
Flash Fusion
Enjoy
# no lag fix #
Click to expand...
Click to collapse
+1
Sent from my Samsung Vibrant on Bionix 1.9.1

well, i'm a noob with this. any tuts on all that? I figured out how to use odin to flash diff roms on my phone and had no issues. but all that Idk. yes I know I can prolly search for all of it, but that took me hours last time. any help would be awesome. thanks.

Click the link in my signature. That thread took a LOT of work, but it should have eveything you need to know. If it does not, let me know what I can do to make it better.

i will try tonite, thanks. I search alot for this stuff and the ppl here seem to be the best. you guys are awzum.

s15274n said:
Click the link in my signature. That thread took a LOT of work, but it should have eveything you need to know. If it does not, let me know what I can do to make it better.
Click to expand...
Click to collapse
s15274n said everything I had to say... the both times he posted.
It's easy once you read and understand. And i'm almost certain you could've fixed your last 'bricked' phone if you searched.

I searched. the first was a soft brick sticking at vibrant logo. I fixed it, but I didn't have a stock backup i flashed, it was a "stock rom" i found on here somewhere. But when it bricked the second time it wouldn't power up, no battery on screen when charging, nothing. But, I will give it a go this way and see what happens, I have 2 now, so eh. It's fun, but I am jsut getting into it. like I flashed it with one of the froyo roms, but the sound wouldn't work for nothing, i searched and no one else using that rom had that problem that i could find. So i know there was something i didn't do. I just wanna makesure i can get it back to stock if i need to.

don't forget to check if your phone is hardware locked.
Sent from my SGH-T959 using XDA App

iynfynity said:
don't forget to check if your phone is hardware locked.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Wish I had got bricked good. Got the replacement and its not hardware locked so flash away

Ok, so I did all that you mentioned seemed to work fine, but this fusion rom doesn't seem like much. now don't flame yet, i am just talkin. but it doesn't look like it changed much other than add launcher pro and as for lag. it's not as slow as stock but with ryans lag fix my quadrant score was 2550 and i'm getting 950 on this. although i have to say the gps snapped to lock. that was great.i really like the froyo rom i flashed before if i could have figured our how come my sound wasn't working and everyone else did not have that issue.

gt_byrd said:
Ok, so I did all that you mentioned seemed to work fine, but this fusion rom doesn't seem like much. now don't flame yet, i am just talkin. but it doesn't look like it changed much other than add launcher pro and as for lag. it's not as slow as stock but with ryans lag fix my quadrant score was 2550 and i'm getting 950 on this. although i have to say the gps snapped to lock. that was great.i really like the froyo rom i flashed before if i could have figured our how come my sound wasn't working and everyone else did not have that issue.
Click to expand...
Click to collapse
There are a few options available on TeamWhiskey website:
1. Fusion with stock kernel
2. Fusion with JAC kernel
3. Fusion with KK kernel
All of the above do not include any lagfixes, except a manual invocation via ADB for RyanZA's equivalent, a.k.a mount /data on a virtual EXT2 partition.
Optionally you can load Voodoo EXT4 based lagfix on non stock kernel options.
Another project is underway with TW own overclocked kernel and z4mod.
And as far as not much, compare the system resource utilization on stock Vibrant and on Vibrant with Fusion (with stock kernel option) - the guys over at TW have squeezed as much as possible out of TouchWiz to make the phone snappier, and as an added bonus they have removed most of the bloatware for you as well leaving the Media Hub for those who might wanna use it.

No Internal Memory showing:(((

after several attempts to install darky 8.1 rom, I went back to my DL30 froyo clean but I do not have internal memory free, and I cant install any root explorer or manager root because its saying that I have to free some memory, I do not have nothing of apps expect those that come with update, this update work previously normal. Please any help I am stuck with non install phone.
Very dissociated.

Hmmm. The zero memory issue is usally means a flash over an existing ext4 (voodoo) kernel while voodoo is still enabled. But what I am really curious about is what a "darky 8.1" rom is and what device was it intended for? And do you have a link to the darky rom so that we may be able to help you better. but it sounds like you need one of the all in one odin packages from the development section.
good day.

You flashed a captivate rom???? On a fascinate??? That should answer your question right there....
I dont see how you didn't brick the thing.

chopper the dog said:
Hmmm. The zero memory issue is usally means a flash over an existing ext4 (voodoo) kernel while voodoo is still enabled. But what I am really curious about is what a "darky 8.1" rom is and what device was it intended for? And do you have a link to the darky rom so that we may be able to help you better. but it sounds like you need one of the all in one odin packages from the development section.
good day.
Click to expand...
Click to collapse
Here it is http://forum.xda-developers.com/showthread.php?t=814091
but what odin file I need, this is really terrible, I do not understand, how this could happen... but thanks in advance.

chopper the dog said:
Hmmm. The zero memory issue is usally means a flash over an existing ext4 (voodoo) kernel while voodoo is still enabled. But what I am really curious about is what a "darky 8.1" rom is and what device was it intended for? And do you have a link to the darky rom so that we may be able to help you better. but it sounds like you need one of the all in one odin packages from the development section.
good day.
Click to expand...
Click to collapse
should I disable voodoo

Why would you flash a rom meant for another phone?
Sent from my SCH-I500 using XDA App

I did not know that is just for galaxy s SGS

OP, check yo pm.
good day.

siberian85 said:
I did not know that is just for galaxy s SGS
Click to expand...
Click to collapse
Good rule of thumb, if it isn't in this Fascinate-specific forum, don't flash it.

And if that package fixes it. Continue on to THIS THREAD. And then continue on to the EB01 stuff.
good day.

Chopper... I did the same thing accidently flashed darky's rom. can you send me what you sent the other guy and i can try that to fix my phone. i can get into download mode, nothing else.

[Kernel][KH3][KI1/KI2]Boog Kernel[Updated 9/29/11]w/Clockwork Recovery init.d support

Ok, here it is guys! I know all you stock captivators have been anticipating this!
This is the stock KH3 and now KI1/KI2 kernel with clockwork recovery injected. Also my first go at a project like this.
The only issue I see is that /system won't unmount, so no nandroid backups (they won't restore). /system will now unmount, but restoring a nandroid backup will totally bork your phone, don't even try! (unless you are ready to odin/heimdall back!)
I have to give a huge thanks to eXistZ, he helped point me in the right direction, and generously gave me scripts he uses. And let me bug him on a regular basis. Thanks dude! And a thanks to Chainfire for pointing me in the right direction to finding why system wouldn't unmount.
Anyone is available to use the kernel any way they like. Cook it in roms released here, flash it to your personal rom, or stock KH3! Take it apart, look at the pieces, see if you can make it better! I am far from a pro at this, and it may not be perfect, use at your own risk..yada yadda.
Nandroid is still broken, still looking into it.
Update 9/11/11
I am releasing this now, because it appears that the /system not unmounting issue causes problems for full wipe roms, with big system changes. This should help. Just don't try to do a nandroid restore, it will make your phone hang at the at&t logo! You have been warned!
It is also possible to format /system from cwm if anyone feels the need (you can't boot after, so only do so if you are also planning on also installing a rom).
The links below should be fixed to point at the new versions.
KH3
Here is the odin flashable version flash it first if your on stock: Link Mirror
Here is the KH3 cwm flashable kernel5! Flash it second to get init.d support if your on stock or don't already have cwm LINK It has init.d support and the same tweaks listed for the KI1/KI2 kernel below.
Here is a heimdall package for stock kh3 with the cwm kernel3 built in. Link It will wipe your phone! Make A backup as necessary. Hopefully it can help people go from stock to a custom rom in fewer steps, or recover from a soft brick Let me know if you find an issue with it. It contains factory.rfs, dbdata.rfs, chache.rfs, param.lfs, modem.bin and the cwm_kernel zImage.
KI1 KI2
Update 9/29/11
I'm just going to do one version for KI1/KI2 now that it appears the same kernel will work on both.
Here is the original odin flashable kernel to give you cwm, flash it first to get cwm if you don't already then flash the cwm with init support. Link And my original post with the stock kernel.
Now for the good stuff!
mtcarey modded my kh3 kernel here, to add init.d support, made changes to allow ADB / DDMS to run as root, and symlinks from Busybox to "ls" and "ps" have been removed from /sbin so that DDMS will work correctly. They now fall back to Toolbox links in /system/bin. Thank him in his thread! Awesome work! I think I have all of those mods pulled to ki1/ki2, plus:
+ Juwe11's LMK settings
+ Tweaked Kernel Scheduler Settings
+ Tweaked IO Scheduler Settings
+ Tweaked Ondemand Governor/Sampling Rate
+ Tweaked Readahead to 512 on internal/external SDs (mmcblk blocks)
You can get it here: Link Mirror
If your on stock you will need to flash the odin version to get cwm then the new tweaked one for the init.d scripts, /etc/init.d/S99complete is needed! If you remove it, the phone won't boot!
For any of you losing root when you flash my kernel or for anyone on straight stock, you can get root by flashing ChainsDD root: http://forum.xda-developers.com/showthread.php?t=682828 or what I mention below.
If your on straight stock and don't already have cwm, flash my odin version first, then ChainsDD from the above link, or:
Grab my cwm zip that I made from ChainsDD and my latest kernels (with tweaks)
KH3 and root
KI1/KI2 and root
Hopefully those will help.

SWEET!
This Man Is A Beast, like the good one on X-men!!
Great Job.
You all reading this and wondering;
= its Stable
= its has awsome batterylife
= easy to use
= and worry free.
GO TEAM PHOENIX!!!
For those wanting the stock E3 recovery back....(for the life of me I don't know why) I will be posting it here today.

hah, a fellow ohioan would be the one to release this. good work bud.

So...are you guys gonna make my cappy NOT suck anymore?
Sent from my GT-I9000

Awesome! You rock dude, thanks!

Great job ! Appreciate the hard work by all !!

Dont forget to vote his thread.
a-hem' Fivestar*

Amazing!
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!

Thanks a lot...
U R THE BEST!.. Good luck with your future work. Hope to see more work from u.
Thanks again for all the hard work.

keller.jeff said:
So...are you guys gonna make my cappy NOT suck anymore?
Sent from my GT-I9000
Click to expand...
Click to collapse
Send it to me, I don't think they suck!
But, yeah, custom stuff on your phone can only make it better.

Awesomeness.....!!!!

Sweet! Nice job y'all!

Any reboot during call issues like on kf1? I know its early on, but wondering if anyone has experienced this on any kh3 version. Thanks for ur work. No cwm has kept me from trying kh3. Can't wait to flash.
Sent from my SAMSUNG-SGH-I897 using XDA App

i know what crash you are talking about, and i had it too on kf1, but have yet to experience it on h3. that doesnt mean its gone though because i havnt given it the same stressing as f1.

Da Bomb...

Did this break data connection for anyone?
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!

I would like to know how to do this. But I will try to do it by myself first.
If I getting stuck please let me PM for your help

I've heard word of "the best" battery life. Can anyone attest to this? I can't believe that from Samsung's track record....

Great work!! Flashing after post. Far as battery life. Every phone and phone user is different. So life varies. Me I crank brightness up use wifi, and GPS always. Like tonight buying a car 260 mile round trip used GPS to get there started with 100% and was. On 26% whenever I got there. Just appreciate that you have a device that makes your life easy and fun! I always turn wifi off and do my best to conserve battery. The captivate is truely a bad ass device. My brother was over last night. And we were playing with phones. He dropped his iPhone 4 and used my cappy cause its better he said
Sent from my SAMSUNG-SGH-I897 using XDA App

great work dude.......

[HELP] 3G restarts my phone

Hi everyone,
I recently flashed cyanogenmod 7.2 onto my HTC Wildfire and it kept restarting for an odd reason, I restored back to SplashMOD and it still has the same problem. I've turned 3G off and it seems to be fine, its just when I turn 3G on
Any help?

Maybe you overclocked your phone at 768MHz.... it isn't very stable
Sent from my Wildfire using xda app-developers app

Yeah i had the same problem
Just flash the latest radio, that fixed the problem for me
Sent from my HTC Wildfire using Tapatalk 2

I haven't overclocked it, where and how do I update the radio?

See the complete wildfire index thread in the development section.
It's a sticky so you will find it at the top
It contains everything u need: ROMs list, all recovery versions, all radio versions, kernels and allot more
Sent from my HTC Wildfire using Tapatalk 2

lo2ay said:
See the complete wildfire index thread in the development section.
It's a sticky so you will find it at the top
It contains everything u need: ROMs list, all recovery versions, all radio versions, kernels and allot more
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
It says my phone needs to be GSM (I'm guessing that means unlocked) which my phone isn't. What is a good radio to flash? and do i need to do it before i flash a rom?

GSM means that it's a standard phone that works in any country. ie: it's not CDMA, which mean that it doesn't need special frequencies from the service provider.
Sent from my HTC Wildfire using Tapatalk 2

undeniableturnip said:
It says my phone needs to be GSM (I'm guessing that means unlocked) which my phone isn't. What is a good radio to flash? and do i need to do it before i flash a rom?
Click to expand...
Click to collapse
like lo2ay already said GSM ("Global System for Mobile Communications") doesn''t mean "unlocked" and has nothing to do wih it.
But in case you didn't unlock your phone - and I'm not getting you totally wrong - this brings up a much more interesting question: if you don't have an unlocked Wildfire - how the hell have you been able to flash a ROM anyway? I'd guess one of the following might match your situation:
- you have a different phone (not a HTC Wildfire)
- you just thought you're going to flash a ROM but did something else instead
- your Wildfire is unlocked and you don't know it
Are you really serious about what you've done? What tutorial/how to did you use to flash Cyanogen Mod?
And yes: if your phone is a Wildfire (buzz) and not unlocked/rooted you can't flash a new radio because you can't flash anything custom...

I think he was meaning sim unlocked?
Forum fishing.... Who's biting!

slymobi said:
I think he was meaning sim unlocked?
Click to expand...
Click to collapse
oh yes - I've been thinking about that for a few seconds - you're probably right.
Regarding my own little problem which I've also discussed a bit desperately here: may I ask you what you would try next with all your Wildfire experience? (I've never been really convinced that the V6 Supercharger or 3G Turbocharger scripts could be involved but after reading that a few people got that bootloop prob with 3G after messing around with them it looked so obvious).
I feared to investigate any further because I had the feeling it could cost a lot of time... so when I went on to solve the problem it turned out I was right with that: I've flashed the 7.2 stable today - with doing just a dalvik and system wipe without success and then a complete wipe - no success either.
I fear to revert back to a true stock rom (including s-off again) as it took me a lot of sweat to do that initially (that has been just in the middle of transformation from revolutionary to alpha rev with all the goldcard stuff etc.) - too make it short: what would you do?
Thx in advance for some input on this...

I would first check my mtd size settings! If you dont know what custom mtds are it means your not using them,if you are using them then you must remember to flash the bravo boot file straight after your rom flash before booting! If this is not your issue then i would do a clean flash of a rom. I.e wipe system, cache, dalvik cache, go into mount and storage and do all available wipes NOT sdcard, then flash the rom. If all fails then i would 1st try a reflash of a custom recovery and repeat previous clean rom flash. Now if it still didnt play ball i would scream at it, throw it at a wall then regret that step and move on to ruu.exe and start afresh lol.
On the v6 etc etc issue. Ive publicly said many times how much i hate this script and others like it! But this is only my opinion as i have had issues using them too in the early days. An app i use still to this day which gives you complete control over the effects of these scripts is autokiller memory optimizer. I will link to a thread i made some time ago to explain this app which can be found on the market.
This again can and most likely will be argued or debated as to its function but in my experience its a must have when used correct.
http://forum.xda-developers.com/showthread.php?p=20909644
Forum fishing.... Who's biting!

slymobi said:
I would first check my mtd size settings! If you dont know what custom mtds are it means your not using them,if you are using them then you must remember to flash the bravo boot file straight after your rom flash before booting! If this is not your issue then i would do a clean flash of a rom. I.e wipe system, cache, dalvik cache, go into mount and storage and do all available wipes NOT sdcard, then flash the rom. If all fails then i would 1st try a reflash of a custom recovery and repeat previous clean rom flash. Now if it still didnt play ball i would scream at it, throw it at a wall then regret that step and move on to ruu.exe and start afresh lol.
On the v6 etc etc issue. Ive publicly said many times how much i hate this script and others like it! But this is only my opinion as i have had issues using them too in the early days. An app i use still to this day which gives you complete control over the effects of these scripts is autokiller memory optimizer. I will link to a thread i made some time ago to explain this app which can be found on the market.
http://forum.xda-developers.com/showthread.php?p=20909644
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
Sorry i only just noticed your link so my advice was for current op issue. However yes i believe these scripts are the cause im afraid. Still i would give you the same advice again as above or try a clean sense rom flash.
You can get safe ruu flashable zips too so as not to lose security or root so try these before going the exe route.
Hope you get a fix.
Regards slym.
Forum fishing.... Who's biting!

Thanks for the quick reply
slymobi said:
I would first check my mtd size settings! If you dont know what custom mtds are it means your not using them,if you are using them then you must remember to flash the bravo boot file straight after your rom flash before booting!
Click to expand...
Click to collapse
Yep I'm using custom mtds - that's exactly the reason I don't like to flash once in a week LOL. I'm aware of flashing the bravo boot directly before rebooting.
I.e wipe system, cache, dalvik cache
Click to expand...
Click to collapse
done
go into mount and storage and do all available wipes NOT sdcard
Click to expand...
Click to collapse
for that I'm sure I didn't do all (because I've done the factory reset anyways) but perhaps it helps to do it explicitly...? shouldn't hurt
If all fails then i would 1st try a reflash of a custom recovery
Click to expand...
Click to collapse
ummh, never done that before - can you point me to a tut or how to?
Now if it still didnt play ball i would scream at it, throw it at a wall then regret that step and move on to ruu.exe and start afresh lol
Click to expand...
Click to collapse
oh, so I'd say you're relaxed like Buddha as this came to mind much earlier
On the v6 etc etc issue. Ive publicly said many times how much i hate this script and others like it! But this is only my opinion as i have had issues using them too in the early days
Click to expand...
Click to collapse
yes I know - I've read a few of them I've been satisfied with the script but I'm also quite sure that it depends on too many things if it works good on the phone.
An app i use still to this day which gives you complete control over the effects of these scripts is autokiller memory optimizer. I will link to a thread i made some time ago to explain this app which can be found on the market.
http://forum.xda-developers.com/showthread.php?p=20909644
Click to expand...
Click to collapse
nice, thx, I'll have a look when that sweet old crappy thing will run again LOL
Thx again for quick response -> off to the laboratories now

Nice quote edits, you have way too much time on your hands lol.
For recovery flashing head to development sticky and 3xenos complete wildfire thread has it all mate. I use the terminal emulator method as adb and fastboot dont play well with me.
Lol buddah.
Some users stating a radio flash may fix the bootlooping? Wont harm to try!! Just make sure its a wildfire radio
Forum fishing.... Who's biting!

slymobi said:
Nice quote edits, you have way too much time on your hands lol
Click to expand...
Click to collapse
nah, easy when I'm on my PC - don't do that in Tapatalk though LOL (swype or not)
For recovery flashing head to development sticky and 3xenos complete wildfire thread has it all mate. I use the terminal emulator method as adb and fastboot dont play well with me.
Click to expand...
Click to collapse
thx - and for adb - it's the opposite here: I don't like ADBin' LOL
Some users stating a radio flash may fix the bootlooping? Wont harm to try!! Just make sure its a wildfire radio
Click to expand...
Click to collapse
I know but I've already tried that twice
And no good news: either wiping everything and doing with or without custom mtd didn't do. Immediately when the network icon shows up (on Google accounts login) reboot... - but wait... one more question: what about formatting boot? should i do this, too?
However, I'll try a sense ROM now and the "safe" RUU afterwards - cross fingers...

eventcom said:
nah, easy when I'm on my PC - don't do that in Tapatalk though LOL (swype or not)
thx - and for adb - it's the opposite here: I don't like ADBin' LOL
I know but I've already tried that twice
And no good news: either wiping everything and doing with or without custom mtd didn't do. Immediately when the network icon shows up (on Google accounts login) reboot... - but wait... one more question: what about formatting boot? should i do this, too?
However, I'll try a sense ROM now and the "safe" RUU afterwards - cross fingers...
Click to expand...
Click to collapse
Format boot..... Yeah why not, i always have.
Really strange this though as you have virtually wiped the phone clean. I thinks you gonna have to ruu it
Forum fishing.... Who's biting!

slymobi said:
Format boot..... Yeah why not, i always have
Click to expand...
Click to collapse
done also - without any effect
Really strange this though as you have virtually wiped the phone clean. I thinks you gonna have to ruu it
Click to expand...
Click to collapse
yup. I've tried to install Rempuzzle - but that hangs around 30 mins - so I will try the custom recovery first...

eventcom said:
done also - without any effect
yup. I've tried to install Rempuzzle - but that hangs around 30 mins - so I will try the custom recovery first...
Click to expand...
Click to collapse
Its sounds like you got things covered and know what your doing but just in case? You do have sdext partition for flashing rempuzzle yes?
Forum fishing.... Who's biting!

slymobi said:
Its sounds like you got things covered and know what your doing but just in case? You do have sdext partition for flashing rempuzzle yes?
Click to expand...
Click to collapse
LOL yes but thx for the reminder anyway

Now it's getting really weird... I've just put in a different SIM (out of the family) - different carrier. (the idea came to my mind somehow). Looks like the phone doesn't reboot with that.
If that's true and not by accident - what does that mean now? Usually I'd think about the radio - but I've completely wiped the phone (including a sense install in between) - could this be a hardware problem?
I guess I'll do the RUU thingy anyway. So I'll start to gather information on that.
If anyone has a good suggestion to do that as easy and quick as possible - I'd appreciate any suggestions.
--- EDIT ---
If someone has a suggestion for a small Sense ROM (yeah I know) I'd prefer to do that first...