Hello everyone!
I received three days ago a HTC HD2. It was the first time I ever had an HTC, so it seemed a little wierd at first. The phone was not new, so it had saved many applications and contacts that I didn't need. So, without being very good documented, I made a reset from its settings. Then I saw that it didn't reset totally. Still, the google acount of the previous owner remained saved, and so did the contacts. Then I read about ClockWorkMod recovery and I devided to try, by a tutorial, to delete everything using CWM. It all went good, but after I wiped everything, when it started, it gave an error saying something like "no kernel in NAND". I read more about this issue and then I decided to instal another ROM,and I did, following a tutorial, install GingerBread 2.3.7. After I encountered some problems , because at first I installed it using a wrong version of CWM and it stucked at the booting screen( that X ), I made it from the second try. Now , the phone is moving pretty good, but the problem is that sometimes, if I lock it and immediately after that I try to unlock it, the screen flushes a little( turns grey , from black, as if it would work somewhere inside, but is not working completely) and it is annoying. I would be pleased if you would recommend to me a solution to this problem or another ROM, maybe a more stable one, with the exact steps I have to make in order to be a clean instalation. ( starting from this point, when I have installed this ROM, what I would have to do to install another, if I have to install another bootloader, or another version of CWM, and so on) .
I know that there are many topics on this matter on the forum, but I am really noobie, and I need a little bit more details, because I don't really understand what every thing, in a topic about a ROM, refers to.
Thank you!
Related
I've been flashing new ROMS on an 8525 for a couple of years now, but I'm new to the 8925.
I've been reading a lot, I think I understand the relation between SPL and the ROMs now, but I'm still puzzled.
I keep getting a lot of cruft left behind from prior ROMs and don't know how to get rid of it. for example about three ROMs ago, I flashed the "Mobile Vista" from ansar. Now I still get his Today theme, and there are still a lot of apps installed that read "ansar..."
I've tried removing the battery before flashing, making sure the SPL version is OK with the ROM doing hard resets - nothing seems to let this device start from a "clean slate".
I'm trying to find a ROM I can be happy with, which is why I'm trying so many, but I can't fairly evaluate aon one ROM if I don't know what I've really got installed.
TIA
Walt
I've never heard of anything like that happening Are you sure it is the today theme, or just the boot splash? That would be most likely.
As far as the programs, maybe most of them are from ansar? Which ROM are you using right now?
I just flashed the PDA Corner latest version (15) and it seems to be behaving now. Prior ROMS I tried this morning included Athine, Garmin and Phoenix.
Prior to flashing PDA Corner, I did an "Erase memory" (hard reset from software) and removed the battery for about 10 minutes. Maybe that's what did it. I agree, I've never seen anything like this before, I always thought that flashing the ROM reased everything, but then I started reading about SPL on the Kaiser somehow being more than just a bootloader so I got concerned.
And yes, it was the Today screen including clock, wallpaper, etc. The splash screen on bootup actually did change to the one corresponding to the new ROM.
Thanks.
Walt
When flashing a new ROM, when you get to the "Tap screen to begin" do you perform a Hard Reset?
If not, I suggest you start doing now.
Also, merschle (ex-moderator and Artemis cook) recommended flashing a ROM twice with a Hard Reset in between. I don't do this, but it just might help
Ta
Dave
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Billun said:
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Click to expand...
Click to collapse
I hard reset three times then I flash an OEM ROM, then I hard reset three more times to be sure. I know it's anal, but it works for me.
I don't know how you're flashing try the SD Card method.
It's safer and more reliable.
The SPL & Rom have closer relationship than on your older device.
A sign of have the wrong SPL or needing to change to another SPL is freezing. If you notice your device is freezing or non-responsive, flash the recommended SPL by the chef.
Don't worry any, I was the same when I upgraded from the Wizard...gotta learn all over again.
Ok, I've got a bit of a problem with one of my old phones. I've sold it some time ago, but I still take care of it. Here's the problem.
I've reinstalled it, and it was working. Then I've sent my friend a file with a splash screen, because the one included in the ROM was white and not very pretty. So I've created the splash the way I make it for my Raphael. He flashed it, using ActiveSync, but the process stopped at 85%, and no escape from the bootloader. So I've downloaded my old tools and created new splash, it happened to be about 1MB smaller. Ok, so we've flashed the stock ROM, then we flashed the ROM that was working before the splash screen flash (that offcourse removed the new splash, but the OS wasn't working). So, the "new" ROM started to say that the device is out of space when we "Tap the device to continue" after Hard-Reset. Another HR didn't help. Flashed the stock ROM again, but it didn't loaded. We flased another ROM, now the device is working, but the total aviable memory in the device is 15MB (it should be more than 50). The odd thing is, that there are contacts left from the previous owner (that's the second person that uses the phone after me). So is it possible to completely reformat the internal memory, so everything has to be flashed clean, and there are no left overs from previous users. The device is Hermes, we've tried using HERMDIAG but no success.
Thanks in advance and sorry for my VERY BAD English.
I guess, no one knows what can be done.
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Next step is to use the Eclipse debugger and read the debug output once it crashes/reboots. The output from the debugger will provide more information about what happened so you can start narrowing the problem down more.
It's a memory or cpu problem (i guess) . Try the cpu a bit lower. I hope it will help you
If you have flashed your phone allot, and you have under clocked your CPU first, it may be a NAND issue. It has been a problem on my end with the HTC HD2 after like 1000+ flashes. You should be able to use a tool to check for bad NAND blocks, don't remember off the top of my head what it was called when I used it but that's something you could do. That is all (if) you have not tried to under-clock your CPU first and make sure the ROM is not bugging out like it sounds like it is.
Another way to test your NAND is to try a SD ROM that runs on your MicroSD card.
I have flashed many ROMS to my phone and about 3 months ago I flashed MIUI rom v5 simply because I thought it would be cool. I no longer want it, it's just getting boring, so I want another ROM, pretty much any ROM, Cyanogen, Carbon, AOKP, I've tried them all. some won't even flash, it says failed before I can boot up the device so I have to restore back to MIUI. although some do, and there's a problem, there is an error message that keeps popping up when I do anything, I think it says something about a keyboard but it goes away too fast to read it. that wouldnt be such a nuisance if the home button would work. on the MIUI ROM the home button works fine, but on any other ROM that hasn't mysteriously failed, the home button won't do a thing. It's not a problem with the home button either, if I try to go home with PIE controls, it does nothing, nor if I activate software keys. I'm not sure if it's a problem but when I install a ROM other than MIUI, it completely skips the introduction thing, you know, where you set up everything like the wifi and your account and such, it just goes straight to the homescreen and has these problems. I'm installing these ROMS through TWRP which has had many successes, so I can't help but think it's the MIUI ROM that has messed up my device, any help would be appreciated.
Firstly, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? What are your bootloader details? I need to see the first five lines. What version of TWRP are you using? What are the full filenames of the ROMs that you've tried? Please answer all above questions, I need as much exact information as possible to help you properly.
There are a few reasons why the ROM installs are failing in TWRP: the ROM isn't meant for your phone, you're using the incorrect version of TWRP (some are very buggy), the download is corrupted, you are on the incorrect firmware version that the ROM installer is checking for. The reason the intro is skipping and you're getting a bunch of errors on ROMs that do install is probably because you haven't installed gapps, or you've installed the wrong gapps.
I'm certain we can fix whatever is wrong, it's most likely something very simple you've missed. As long as you give the information required this should be easy.
Sent from my Evita