i bricked one HTC Dream (G1) Black PVT 35 with new radio but **** it, i went and bought another g1 and was bold enough to try again and it worked, so that was cool, installed the newest haykuro update and learned i didnt like it as much as i liked jf 1.5, so i downloaded the newest jf 1.5 build and flashed my phone to it and it sits on the g1 screen, so i was like omg, thinking i bricked my new g1, but i didnt i was able to get back in the bootloader, so i whiped again and tried my famous jf 1.5 and it sat on the g1 screen again, so i said wtf, so i went back to the haykuro build, i decided to choice the g build since its the one i like, and it worked fine and went passed the g1 screen, so with the new sql, im i only limited to HTC Magic builds ??
1st G1 really bricked? maybe you can access adb even if you're in G1 screen?
Cant explain why, but i've personally run HK 6.0 (current) and dudecake 1.1 (plan on returning for 1.2 release) and roomate is on JF 1.5, all with new SPL
ESKIMOn00b said:
Cant explain why, but i've personally run HK 6.0 (current) and dudecake 1.1 (plan on returning for 1.2 release) and roomate is on JF 1.5, all with new SPL
Click to expand...
Click to collapse
umm interesting, yea i gave up on the first g1, its dead lol theres not going to be a fix to that, the computer doesnt even reconize it when its sitting on the g1 screen, imma add insurance, wait a month and send the bricked one in as it malfunctioned and just resell the one they send me to cover my lost.
but anyways i guess i will try the jf 1.5 again, maybe if i redownload it , i might get lucky
ESKIMOn00b said:
Cant explain why, but i've personally run HK 6.0 (current) and dudecake 1.1 (plan on returning for 1.2 release) and roomate is on JF 1.5, all with new SPL
Click to expand...
Click to collapse
after 2 hours i figured it out, since i had a new g1 i had a new sdcard, it was not Partitioned, i did the FAT32 / EXT2 Partitions on the MicroSD and tried my famous jf 1.5 and it worked fine
yea wait for a month and wait for the mass cupcake update and tell them that you're phone died while updating the cupcake lolz
jrherras said:
yea wait for a month and wait for the mass cupcake update and tell them that you're phone died while updating the cupcake lolz
Click to expand...
Click to collapse
lol even better idea, i sure in the hell will do that
OR tell them you thought your G1 froze while updating then you took the battery out
Related
Hi!
I have JF 1.42 RC 33 with root enabled on my G1 from polish network Era.
Then I've decided to switch to JF 1.5 ADP, so first I've installed radio update from htc web page and after this i 've installed 1.5. After succesfull instalation my phone restarts after few minutes and loops on android logo. It is immposible to switch it off. I can only take off battery. Only way to use it once again is to go to recovery mode, then wipe it, and install JF 1.5 one more time. But after this my phone once again is working till first reboot. I've tryied JF 1.5, the Dudes and Hayakuro updatesl but it is same situation. Reboot and loop on android logo.
Now I have JF 1.43 RC9 and new radio 2.22. I've also tryied to install one more time radio update and JF 1.5 update, but it doesn't help. What elsa I can do?
Also I have newest version on Hard SPL. But I did't changed it since I've rooted phone.
szymarek said:
Hi!
I have JF 1.42 RC 33 with root enabled on my G1 from polish network Era.
Then I've decided to switch to JF 1.5 ADP, so first I've installed radio update from htc web page and after this i 've installed 1.5. After succesfull instalation my phone restarts after few minutes and loops on android logo. It is immposible to switch it off. I can only take off battery. Only way to use it once again is to go to recovery mode, then wipe it, and install JF 1.5 one more time. But after this my phone once again is working till first reboot. I've tryied JF 1.5, the Dudes and Hayakuro updatesl but it is same situation. Reboot and loop on android logo.
Now I have JF 1.43 RC9 and new radio 2.22. I've also tryied to install one more time radio update and JF 1.5 update, but it doesn't help. What elsa I can do?
Also I have newest version on Hard SPL. But I did't changed it since I've rooted phone.
Click to expand...
Click to collapse
There are actually a few threads for people running into issues including myself. Mine turned out to be an issue form apps2sd that I have in my thread
http://forum.xda-developers.com/showthread.php?t=511709
There is also http://forum.xda-developers.com/showthread.php?p=3731933
and http://forum.xda-developers.com/showthread.php?t=511955
Ok, so wanted to start this because I have seen ALOT of people have this issue and I myself have loaded Hero and Non Hero ROMs onto a few MyTouch's and get this issue randomly. Figured we could start a thread devoted to people willing to test what the issue could be and people willing to try and help come up with a solution or at least pinpoint the cause of the problem.
Please try to keep this thread to the point as always guys!
I can tell you right now that I had two brand new MyTouch's today and did the exact same procedure on both and put QTek's latest Hero ROM on them and one has the blurry screen and one does not. The SPL was NOT changed from the .2006 SPL, simply loaded the FlashRec.apk, loaded Amon Ra's Recovery image, and wiped and applied the Qtek Hero ROM.zip.
Also it only happens to me when loading a Hero ROM, Cyanogen or any Non Hero works fine without any blurriness on BOTH devices.
This has happened multiple times ALL with the exact same procedure. So as far as I can tell it isn't the SPL or the ROM.
Any ideas what we can do to these MyTouch's to try and narrow something down to what the difference is between the two?
I have the same problem with mine. I rooted using the gold card method. Immediately after rooting I flashed a 32B radio then threw haykuros SPL on it. I have no problem with any of cyanogens ROMs nor with eViL 1.9 & 2.0.
I have tried:
JACxHEROski v1.4 - no fuzzys
JACxHEROski v1.6r2 - fuzzys (I'm thinking it has something to do with the kernel.)
Qtek - fuzzys
ZeroXD - fuzzys
and obviously didn't work. I'm willing to test any ideas anyone has because I'm ready to throw this phone out the window
spyz88 said:
I have the same problem with mine. I rooted using the gold card method. Immediately after rooting I flashed a 32B radio then threw haykuros SPL on it. I have no problem with any of cyanogens ROMs nor with eViL 1.9 & 2.0.
I have tried:
JACxHEROski v1.4 - no fuzzys
JACxHEROski v1.6r2 - fuzzys (I'm thinking it has something to do with the kernel.)
Qtek - fuzzys
ZeroXD - fuzzys
and obviously didn't work. I'm willing to test any ideas anyone has because I'm ready to throw this phone out the window
Click to expand...
Click to collapse
Kernel is a good place to start
Do you know what kernel versions the 4 ROMs you mention use or where we can find that info (short of bugging the crap out of the 3 developers lol)?
Hi, although I don't experience this problem, I noticed that my screen became blurry when it rotated (as it darkens it becomes blurry as well), when I was using Amon_RA's 1.2.1 ROM with his 1.0.1 kernel. I initially thought it was on purpose (it looked kinda nice), but after I flashed to his latest kernel, 1.1.0, the blurring on rotation no longer occurs. So I'd say there's a high chance it's the kernel...
Wysie said:
Hi, although I don't experience this problem, I noticed that my screen became blurry when it rotated (as it darkens it becomes blurry as well), when I was using Amon_RA's 1.2.1 ROM with his 1.0.1 kernel. I initially thought it was on purpose (it looked kinda nice), but after I flashed to his latest kernel, 1.1.0, the blurring on rotation no longer occurs. So I'd say there's a high chance it's the kernel...
Click to expand...
Click to collapse
That is most likely the "Animation" option being on or off.
Goto Settings > Sound and Display then turn ON Animation and see if that brings back you darkening/blurriness you are referring to.
If it does then it isn't the issue we are referring to, but thanks for the input! Appreciate any help/ideas we can get to solve this crap lol
Just tried that, no difference. So it may be the kernel... I've posted about it on Amon_RA's thread, maybe he can help with it more .
I have MT3G and have never experienced the blurry screen. I downgraded the SPL to 005 with the glod card method. I have C1.4 recovery. Have been runing Fatal1ty's HERO and now Zero's HERO...
I dont see how it would be the kernel. It is most likely something to do with the drivers. I wonder if there is more than one manufacturer for the touch screen or video chip or different versions.
What was the purchase date on the phones that get the blurry screen. I doubt that is software (unless somehting is enabled that is causing it to crash), it has to be hardware. There are too many people that dont get the problem running the same ROMs.
Well as far as from the threads I combed through I found this info. It seems as if:
eViL is using JAC-SKI's kernel.
ZeroXd is using JAC-SKI's also.
JACxHEROski 1.6 says its using Amon_Ra's kernel.
I know they cant all be using Amon_Ra's kernel. As far as version numbers I have no patience to figure it out now. I think I have to also agree with zambezy that it might be a hardware issue. It has to be. Same ROM's different hardware. I really should have kept my G1. The grass is always greener...
really stupid question but what sdcards are you guys using with blurry screens?
zambezy said:
I have MT3G and have never experienced the blurry screen. I downgraded the SPL to 005 with the glod card method. I have C1.4 recovery. Have been runing Fatal1ty's HERO and now Zero's HERO...
I dont see how it would be the kernel. It is most likely something to do with the drivers. I wonder if there is more than one manufacturer for the touch screen or video chip or different versions.
What was the purchase date on the phones that get the blurry screen. I doubt that is software (unless somehting is enabled that is causing it to crash), it has to be hardware. There are too many people that dont get the problem running the same ROMs.
Click to expand...
Click to collapse
I got these from others (didn't purchase them myself) so not sure when or where they got them, can't really ask them either.
But I am noticing the problem more and more frequently than when the phone first came out, so maybe there is something to the purchase date idea.
But again, how could it JUST be hardware, if some people can get other ROMs to function properly, ya know? It seems so random, certain ROMs work and certain ones don't and the ones that work for one person don't for another so the ROMs themselves must play some part, right?
spyz88 said:
Well as far as from the threads I combed through I found this info. It seems as if:
eViL is using JAC-SKI's kernel.
ZeroXd is using JAC-SKI's also.
JACxHEROski 1.6 says its using Amon_Ra's kernel.
I know they cant all be using Amon_Ra's kernel. As far as version numbers I have no patience to figure it out now. I think I have to also agree with zambezy that it might be a hardware issue. It has to be. Same ROM's different hardware. I really should have kept my G1. The grass is always greener...
Click to expand...
Click to collapse
Yea and I found that the kernel is the same on the two phones I am using right now (one works and one doesn't)...
Not kernel safe to say I think...
I was having this same problem on jacxrom orginally. Currently i unrooted, did the one click root, used the modified spl and cyanogens recovery and flashed the new jacxrom and working like a chram now.
Jrbourque said:
really stupid question but what sdcards are you guys using with blurry screens?
Click to expand...
Click to collapse
A brand new 8gb class 6 card
im just givin my 2cents in this and i think its the kernal i once used one of evil d's roms and gave mt the blur then he did another rom and fixed that so iunno but i feel its the kernal cuz wen i uploaded his new rom no blur just my 2cents
Not sure how much this adds BUT, I just unrooted my MT3G today and went the Goldcard method instead of One-Touch method. I first installed the ZeroXD with RAv1.2.1. This resulted in a blurry screen. I wiped and reformatted and tried my luck with eViL HeRo v2xx 32B and RAv1.2.1 and its running fine. First Hero ROM I have actually gotten to run without Blurring.
Could someone with a blurry screen and a 32A try to fastboot this kernel and see if the blur is fixed or not?
Code:
fastboot boot kernel.RAv1.1.0
The above command will not flash you a new kernel, it will just boot it.
Amon_RA said:
Could someone with a blurry screen and a 32A try to fastboot this kernel and see if the blur is fixed or not?
Code:
fastboot boot kernel.RAv1.1.0
The above command will not flash you a new kernel, it will just boot it.
Click to expand...
Click to collapse
I have tried this kernel with RAv1.2.1H ROM, and the screen still blurry.
Only RAv1.1.0H ROM have no blurry screen on my 32A.
Could you add Chinese Simplified to RAv1.1.0H ROM for me?
http://forum.xda-developers.com/showthread.php?t=554653
Thanks a lot!
I have the blury screen using any cyanogen mod ROMs...hero Roms are okay, just slow.
Used Amon's HBR to unroot, then flashed with the RAV1.2 recovery
Using red T-Mo mytouch (manf. 7/26)
About to replace with an entire new device.
Long shot.... : Could someone extract /system/lib/hw/lights.msm7k.so from RAv1.1.0 and push it to their blurry ROM and reboot?
My mytouch is same to this
pintspin said:
i am using following
1.33.2010 Engineering SPL 32Aboard HTC brand
i have flashed followign roms in sequence with results.. against them .
1, AMon _Ra rom ( 1.1.0) working perfectly fine...! no BLUR
2, H-hero-1.79.482.3-32A-RAKrnl.zip blurring
3, v3_Full_Hero_32a-gbo_v2 blurring
4, hofo ion rom 1.05 32a blurring
5, JACxROM v1.3 blurring
6, myhero-1.0.0 blurring
7, RA-IONv1.2.1H.ziRom-RA-IONv1.2.1H.zip blurring
8, Rom-RA-IONv1.2.0H.zip blurring
9, cyanm-4.0.2-32a.zip blurring
1o .....again.... went back to AmonRa 1.1 the best working rom for me so far....! i beleive all the new roms after 1.1 update are having some problem ....
one more thing i noticed that after flashing...every rom was working perfectly means NO BLUR but it will be blurring just after the screen go to sleep for once and when it came back from sleep it becomes blurry and the GAMMA seems to be increased automatically
Click to expand...
Click to collapse
I have a G1 that I tried to root and mod. Using the the downgrade method to RC29. I've been reading and waiting untill I felt comfortable trying to mod it. When the one click method came out I ordered my 8gb class 6 sd card. By the time it came, the hole was patched. So got rc29 and Cy recovery1.4 did the telnet and got root. When I went to recovery it was Android Recovery not Cy. Even though I had Nandroid b/u 2.2 and it said Zen's recovery build. I did this 3 times with same results. Next I went to drizzy hero full rom. It said to update radio and spl using a link on the page. The link took me to haykuro's radio and hard slp. Installed the radio first (using the update.zip) then the spl. The radio worked, the spl has me stuck on the G1 screen. I've tried everything that I can think of.
Now I slipped my sim into a my touch 2 pro. Is it me or is this what Ive been tring to get all along. This phone is SWEET!! Plus I've been seeing more upgrades and stuff for WM than Android lately. I'm no dev, obvioulsy my G1 is prob. bricked, but it sure seems like you can do almost anything with WM that you can with Android. Except change O/S. My mind is open on any opinions or ideas. (still like to fix G1) (mt2p is still on 6.1, should I upgrade?)
I rooted my G1 and went from rc-29 to Jf 1.43 Holiday[http://jf.andblogs.net/2009/02/11/jfv143/] and everything works but i want to move on to hero or 2.0 or maybe motoblur or something. any rom i try to load the same way i got to "holiday" sends my phone into a never ending loop or sits @ the g1 screen so i just go back to the jf rom and wipe and reload it....can anyone help me? im not able to find any info on how to downgrade from a jf or move to a different rom.
MaysDroid said:
I rooted my G1 and went from rc-29 to Jf 1.43 Holiday[http://jf.andblogs.net/2009/02/11/jfv143/] and everything works but i want to move on to hero or 2.0 or maybe motoblur or something. any rom i try to load the same way i got to "holiday" sends my phone into a never ending loop or sits @ the g1 screen so i just go back to the jf rom and wipe and reload it....can anyone help me? im not able to find any info on how to downgrade from a jf or move to a different rom.
Click to expand...
Click to collapse
There is a great guide over at http://wiki.cyanogenmod.com, but for the upgrade from jf is easy just follow the instruction's over here at http://wiki.cyanogenmod.com/index.php/How_to_upgrade_from_JesusFreke_1.5. Hope this helps.
sweet that worked!! running cyangn 4.1.9999 or sumthing now and its great!! the cyanogen wiki was perfect!
yes i flashed a rom quite a few days ago- did a wipe on everything -rom loaded everything runs find ... twisted sense 1.5 with kernel that comes with sorry for my spelling trying to figure out whats going on anyway back to the problem at hand
im having issues were i could be doing anything on my tb all of a sudden it resets to the htc loading screen im like ok just a minor thing but it is now getting on my nerves i feel like i might of done something wrong yet im very cautious on how i flash rom using rom manager and its up to date of course. so i was thinking should i change it back to stock to see if that might cure my reset woes ? or just unroot and take it back ? any suggestions are helpful
This seems to be a known issue and is related to the new radio. Did you flash that?
*** UPDATE ***
I reverted back to...
-baseband verison
1.02.00.0103_2r
-kernel ver.
2.6.32.21-gb05544a [email protected] #1
tue mar. 1
-build number
1.12.605.6 CL338893 release-keys
-still rooted with S-on instead of S-off
Still doing the reset here and there...
yes i did flash the radio
Try reverting your radio back to stock (there is a thread in the Dev section) and see if it helps. I have been having this issue too, but it isn't bothering me enough right now to change it. Also I'm not sure if you can use the new framework with the old radio -- you may have to use an older ROM.
thats what im going to try
I have the new radio and I have never experienced resetting with any of the roms, etc. I might just be one of the lucky ones!
- thanks for rubbing it in -lol
Thats good...
i might be considering taking my tb back to get another if this doesnt work
lol my TB is stock and restarted 4 times by itself yesterday
crazed_z06 said:
lol my TB is stock and restarted 4 times by itself yesterday
Click to expand...
Click to collapse
do you have the new radio ? or out of box stock?
cjmcmillion said:
*** UPDATE ***
I reverted back to...
-baseband verison
1.02.00.0103_2r
-kernel ver.
2.6.32.21-gb05544a [email protected] #1
tue mar. 1
-build number
1.12.605.6 CL338893 release-keys
-still rooted with S-on instead of S-off
Still doing the reset here and there...
Click to expand...
Click to collapse
ok-
baseband changed to - 1.16.00.0223r
kernel changed to 2.6.32.21-gb05544a [email protected] #1
sat feb 19th
s-on and no longer rooted
hopefully no more resets if so im returning for another tb...
not giving up on a great device
cjmcmillion said:
ok-
baseband changed to - 1.16.00.0223r
kernel changed to 2.6.32.21-gb05544a [email protected] #1
sat feb 19th
s-on and no longer rooted
hopefully no more resets if so im returning for another tb...
not giving up on a great device
Click to expand...
Click to collapse
Damn that was harsh! lol really the first thing should have been to try a different kernel. It has become known with the tb they are not all created equal. Kernels or I should say switching them can make a big difference.
LeoD said:
Damn that was harsh! lol really the first thing should have been to try a different kernel. It has become known with the tb they are not all created equal. Kernels or I should say switching them can make a big difference.
Click to expand...
Click to collapse
yes i tried those before hand...but decided hey lets do a fresh start
which i reverted back to stock since i do enjoy the rooting process
in which i followed the ....
[ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
http://forum.xda-developers.com/showthread.php?t=996616
followed by installing the radio on this thread the top...
Flashed -> CDMA Radio version: 1.16.00.0402w_1
LTE radio version that came with 1.13.605.7...
Thanks To Adrynalyne -
[RADIO] The Obligatory Thunderbolt Radio Thread
http://forum.xda-developers.com/showthread.php?t=1045081
Then i Installed the Rom Twisted Sense 1.5 running
kernel 2.6.32.21_bamf_4.42 which everything is running
smooth like silk now....Thanks Hedney3!!! Pick the Rom up here >>>>
http://forum.xda-developers.com/showthread.php?t=1040413
i suggest picking up the battery calibrator and ZDbox in the
market -
Well my problem with resetting still exisits i returned to stock now
i seem to still be having this problem...
so hopped over to verizon to speak with someone about this and they
told me this was a functionality of the phone that they could send
me a replacement out but would cost me shipping and handling and also
stated if they didnt find anything wrong with it that i would have to
pay full retail !!! i was like BS *&^&&%^%^ *^%^%$&^$% well you get
the point.
i still have the same tbolt just trying to figure out what to do now was thinking of returning for another tbolt but fear
that this so called " functionality " of the phone ... any suggestions?
my phone was fine until I decided to flash the new radio. I reverted back to stock radio and I'm still getting reboots
yes same here i told verizon about my tbolt self resets like once every hour if im on it they told me it was a part of the functionality of the tbolt
My old one did that.
My old TBolt did that, kind of like resetting the Sense interface (which takes forever). I called them and talked with a really nice guy, and he explained a hard reboot should fix it (which didn't and I lost my call, and got connected with a capital B the next time around _-_)
I also was having issues with the memory card getting "wiped" (data still there, just not viewable in phone) and (the kicker) my phone would reach temperatures of 69degC while charging, while off.
That last one had them change it out right quick.
No automatic resets at all here, and I've had it on and using it most of the time throughout the LTE outage and after. No resets when on EvDO/HRPD; no resets when on LTE/eHRPD; no resets when on EvDO/eHRPD. It only resets when I tell it to!
As for the connection, well... I do get the occasional dropout on LTE. More problems tonight than most nights with that. But EvDO seems to be pretty stable as always.
i didnt have any problems during the outage since im not in a 4g lte area
cjmcmillion said:
yes i tried those before hand...but decided hey lets do a fresh start
which i reverted back to stock since i do enjoy the rooting process
in which i followed the ....
[ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
http://forum.xda-developers.com/showthread.php?t=996616
followed by installing the radio on this thread the top...
Flashed -> CDMA Radio version: 1.16.00.0402w_1
LTE radio version that came with 1.13.605.7...
Thanks To Adrynalyne -
[RADIO] The Obligatory Thunderbolt Radio Thread
http://forum.xda-developers.com/showthread.php?t=1045081
Then i Installed the Rom Twisted Sense 1.5 running
kernel 2.6.32.21_bamf_4.42 which everything is running
smooth like silk now....Thanks Hedney3!!! Pick the Rom up here >>>>
http://forum.xda-developers.com/showthread.php?t=1040413
i suggest picking up the battery calibrator and ZDbox in the
market -
Click to expand...
Click to collapse
Just a FYI for you, I do not have problems with reboots nor do I have most problems most say they are having, however my tb just did not like twisted sense 1.5. For me anyway I couldn't stay on it very long.
I have an idea if you want to give it a try. it will take some time and effort but on the other hand it just might save you the trouble of having to return your tb.
First, do a full wipe of data/cache, do it twice to be sure. flash BAMF, (either one don't matter). once you boot up go to settings/SD & phone storage and do a factory reset. let it reset and come back up. it will take a while to boot and you might even get errors which is ok.
Now hit the power button and reboot into recovery again wipe data/cache 3x, wipe cache 3x.
now try to install your rom. just for the heck of it at least for now stay away from twisted sense. I would use BAMF at least till you see if this solves your problem.
once you have your rom installed flash imoseyon's (SAFE) kernel.
If you do try this let me know how you make out. This has solved many issues for me in the past many times.
actually I stand corrected it was NOT twisted sense that gave me a problem it was tesla coil that I had problems with. so your choice there.