Hey guys... I need some help, ive been having a couple issues. Im a bit of a noob , however i have been doing my reading and ive been trying to do research on a the issues that ive been having. No luck.
So, i started noticing issues minor glitches in my phone with certain things, no big deal, i'll try another rom. Im currently on CM 5.06 and ive tried upgrading to 5.07-5.08 or even Froyo and downgrading to early builds of Eclair like the stock ere27. Not happening, whenever im in recovery mode and im trying to flash any new rom it says:
Error No Signature & Verification Failed..
I realize that to be on Froyo and CM 5.08 i need the 4.06 radio which i have sucessfully loaded via fastboot i think..
I got this error when i was doing it:
Error: Could not get pipe properties
So, im kinda bummed that im stuck with this rom and i could use a little help
Related
I've been running 2.2 now for over a month with no problems but noticed it was a little bit laggy so Installed and applied the one click lag fix from the marketplace which worked beautifully. I noticed later on that my computer would no longer recognize my device which is a big problem so I did a factory reset but that didn't help at all so I decided to reflash to stock. Problem is now my phone keeps flashing the i9000m splash screen over and over. I'm flashing with I9000UGJK3.tar which is stock 2.2, ive tried repartitioning since I did have the lag fix using the s1_odin_20100512.pit file and im still stuck on this damn screen. I have no issues getting into download mode or anything like that but i've spent the past few hours reading posts on here and trying to fix this and I just can't figure it out. Help anyone?
JK3 is 2.1 if I remember right. JL2 is the 2.2 for bell phones. I think the problem is you were on JL2, which has a secondary boot loader, which means you can't flash a 2.1 rom on it. Try flashing with JL2.
According to samfirmware - I9000UGJK3 Version 2.2 2010 November. I'll try flashing with that anyways and see what happens. Thanks for replying!
Worked!!! Thanks so much! Looks like i was using the wrong version, although both were 2.2 the one you suggested worked like a charm!
Worked!!! Thanks so much! Looks like i was using the wrong version, although both were 2.2 the one you suggested worked like a charm! Well it boots up into the OS now but for some reason I can't use the internet over 3g, only wifi :S
you may have to enter your apn settings
Hy everyone!
I have found a very interesting problem regarding my kaiser130 and android...or maybe the problem is in the user?
Anyhow my problem is that no matter which android build i try,no matter which kernel and which radio i dont have working wifi and data connection.
At first everything worked fine but then i had some problems and i didnt have time to fiddle around with android because it wasnt too stable and i had many FC-s so i had to go back to winmo.I had 6.1 on it before,have put on hardspl3.34 then started flashing android and after that i put back winmo from a shipped package with ruu . Now i have more time and i started to experiment with android again.I wanted to use cyanogenmod 6.1.2 but had the wifi-error problem but as i saw many other people had the same so i thought i'd go back to another build,namely incubus26jc's super froyo rls16 i used that for days but then when i had to use the apn or wifi it didnt work...or actually wifi worked but only with static ip,i tried switching kernels from a base one downloaded with atools to clemsyns and scoots but nothing worked for me better yet it even got worse it started producing the wifi-error again.I use the most recent radio tried both the emo version and the atw to no success tried installing both to nand sys on nand data ext2 data.img but nothing seems to be working and now no matter which build i try everytime i get the wifi-error and apn isnt working.Can it be that my bootloader is tarting to fail?Or is my kernel getting corrupted?
Oh and i always applied the appropriate module updates for each kernel.
Can somebudy suggest something useful or i was thinking that is it possible to very hard reset the phone i mean to put it back the way it was?Format the nand put back a normal spl,i dont mind trying thing again but i need the data connection and the wifi.
Oh and i forgot to mention the most interesting thing,when i turn on data it actually turns on and in the modem i can see that it even gets an ip address from my phone provider.
Earlier today i went to flash a newer version of the viper rom. I have done this quite a few times and know the whole process of flashing a rom so i don't feel i am a n00b. So after the rom flashed it was stuck in bootloader and the recovery was gone. I got a recovery back on it and restored what i had saved prior to this. Now i keep getting this error process com.htc.htcdialer isnt responding and the phone does just keeps restarting after about a minute or so. I have looked around quite a bit for a fix but cant seem to come across one and hope someone here can point me in the right direction. And i also noticed it wont seem my sim card either. I did the unlock and was using T-mobile with no probs until i tried to flash that rom....Thanks for any help
I'm having the same issue with my Sprint htc one
Edde3d said:
Earlier today i went to flash a newer version of the viper rom. I have done this quite a few times and know the whole process of flashing a rom so i don't feel i am a n00b. So after the rom flashed it was stuck in bootloader and the recovery was gone. I got a recovery back on it and restored what i had saved prior to this. Now i keep getting this error process com.htc.htcdialer isnt responding and the phone does just keeps restarting after about a minute or so. I have looked around quite a bit for a fix but cant seem to come across one and hope someone here can point me in the right direction. And i also noticed it wont seem my sim card either. I did the unlock and was using T-mobile with no probs until i tried to flash that rom....Thanks for any help
Click to expand...
Click to collapse
I'm currently running ViperOne 5.7.0 I tried updating to 5.8.0 and even 6.0.0. Neither would work. Kept getting the same results as you. And, same as you, I tried looking at a lot of different places for solutions, unfortunately I can't find any.
UPDATE: I found out that the culprit was twrp 2.7.0.0 so I flashed twrp 2.7.0.4b and it allowed me to flash ViperOne 6.0.0
Try flashing the latest radio.
Hello All,
I'm a relative newbie and have an issue with my HTC One (M7UL). I've had the phone about a year and it's unlocked (still with S-ON). I've changed the ROM loads of times but now I've got a problem. I think the problem started recently when I couldn't get the OTA updates with Cyanogen to install. I formatted the phone via TWRP, something I've done loads of times and generally do before installing a new ROM. I've tried to sideload several suitable ROM's (CM11, CM10, ARHD etc.), but they all fail. I've never had a problem before. The most recent failure has caused me give up.
I've taken a screenshot following the most recent failure (attached).
Any help would be greatly apperciated.
Many thanks.
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.