My beloved N1 is becoming increasingly unreliable. It will sometimes lock up completely and then I am unable for a time to get it to boot. Often it will sit at the 4 color X bootloader splash forever. Sometimes it will go straight to a screen that looks like a display test - colored bars on most of the screen and those skateboarding androids at the bottom. I've tried wiping various things, re-flashing with all the latest stock google stuff, both via fastboot and via PASSIMG. The problem still seems to be getting worse.
The question is am I out of luck? Is there some thing I haven't tried that might make it reliable again? What has happened to the poor thing?
I really regret not being able to pass this excellent device on when I upgrade to something else.
I'm considering buying a Nexus S to replace it.
Other things I've tried: Swapped out the microSD, removed the SIM, cleared the cache partition, used my spare battery (real HTC battery, briefly sold by Google). Nothing so far does anything to make it work better.
I can sometimes get into fastboot and lauch a recovery image, for instance, but when I do get it booted it will last a day or so and then die again.
Ah, perhaps not a good sign? (from clockwork, erasing cache...)
-- Wiping cache...
Formatting /cache...
mtd: not erasing bad block at 0x01480000
mtd: not erasing bad block at 0x024e0000
mtd: not erasing bad block at 0x03d60000
mtd: not erasing bad block at 0x03ea0000
mtd: not erasing bad block at 0x04b60000
mtd: not erasing bad block at 0x05240000
mtd: not erasing bad block at 0x05aa0000
Cache wipe complete.
So the flash chip on my N1 is going bad?
Dang, I reverted to Froyo and it's been stable since…
Never mind. Still crashy. New phone ahoy.
Sent from my Nexus S using XDA App
Related
Text at the bootloader screen:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Serial
-------------------
When this first happened I was able to use mtty to boot to the OS. Now when I plug it up to my PC it changes from "Serial" to "USB" however I get the warning that Windows does not recognize the USB device.
Occasionally the device will boot to the OS but when I attempt to insert my SIM card (I've removed it so I can continue to use my service) the device reboots and goes straight to the bootloader screen. When it boots to the OS and I don't insert my SIM card ActiveSync doesn't recognize it.
I had been using Dutty's Duttys_Diamond_Rom_Ruu_Signed_5.2.1588_1.65.16.25_V1 ROM at this point. I then tried to flash the Official AT&T ROM found in this thread. Didn't help. I've tried flashing HardSPL 3.56. Didn't help.
Can I still save this thing? What else can I do? Am I missing something obvious here?
My phone ran into the same issue in the last 24hrs. Leaving the battery out for an hour "fixed" it, only to have it reoccur overnight.
Bump. I could really use some help on this issue.
Have you tried reflashing the rom using a microsd card? What spl version are you running?
Alibaba0101 said:
Have you tried reflashing the rom using a microsd card? What spl version are you running?
Click to expand...
Click to collapse
Multiple times. I've tried reflashing the Duttys ROM I was using (see original post) and the official AT&T ROM, which is what is now installed on the device. I am/was running HardSPL 1.0 and I tried flashing HardSPL 3.56 from my micro SD card but the text at the bootloader screen is still:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Which leads me to believe that I am still running HardSPL 1.0
Just now the device attempted to boot to the OS but froze at the green WM6.1 screen. I then tried a soft reset and it went back to the bootloader screen. It seems that leaving the battery out for some time will allow the device to boot to the OS. Next time I attempt to boot it up I'll insert my SIM card and see if I get anywhere with that.
Here's a thought. When I bought my Tilt AT&T sent me a new SIM card but I never bothered to have my old SIM card transferred to the new one. I've been using my old Cingular SIM card. Could this an issue? I had read that some older versions of HardSPL may have trouble with older SIM cards...
So I took out the battery and let it sit for a while, put my SIM card and the battery back in and it booted to the OS. Sweet. However, the screen is unresponsive to touch and does not shift from portrait to landscape when I slide the screen. Also, Activesync did not recognize the device.
I removed my SIM card and it booted to the bootloader but Windows did not give me the error that it didn't recognize the USB device so I opened MTTY and was able to connect.
Here's the info 8 message:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 262 (0x106) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x740
Partition[2], type=0x25, start=0xD80, total=0xB540
Partition[3], type=0x4, start=0xC2C0, total=0xF000
CE Total Length(with sector info) = 0x61C1600
CE CheckSum Length(without sector info) = 0x6160000
Cmd>
I'm going to toss in my unregistered SIM and force boot to the OS... at least I can charge the damn battery now.
EDIT: I inserted my unregistered SIM and tried to force boot to the OS using MTTY but the screen went black and I've got a red light. Removed the battery and rebooted to the bootloader. Now Windows no longer recognizes the device. But I'm confident I'll be able to boot to the OS later. But I've gotta get ready for work now. Frustration!
Did you try this?
http://forum.xda-developers.com/showthread.php?t=420683
Alibaba0101 said:
Did you try this?
http://forum.xda-developers.com/showthread.php?t=420683
Click to expand...
Click to collapse
This looks promising. I had seen this but forgot about it because I hadn't had any luck booting to the OS. I'll definitely try this when I get home.
tri-color phone screen
hey, i had the same problem and i fixed it. i took the battery out and saw the 4 golden tabs behind the battery. there was two tabs that u could pull out. i lightly pulled them out a little bit. the problem was that the tabs wouldnt hit the battery to charge it. thats why it put the tri colored screen on the front. also my charger fit into the charging hole in the phone, but it had to be moved around to much that it did not fit exactly. I have been rough with the charger so it moved the inside of my phone around. i put the charger in the phone and moved it around gently around untill the light lit up on the front at the top by the word at&t. after it was completly charged, i turned it on and it worked perfectly. i hope this helps in whoever may have this problem because i know it sucks!
Thanks
One of my superiors wanted me to dispose of his old v1615/Kaiser, saying "...this isn't working. Dispose of it properly." Ever the fiddler, I wanted to know if it could be used again, and in so doing I found xda-dev!
I've been searching around, and reading up - Wikis and forum posts - but I've yet to find a solution to my problem: the Kaiser hangs at the Vodafone logo. I found the MTTY instructions threads etc., so to clarify the situation here is a MTTY dump (first two carriage returns and commands included...):
Cmd>
Cmd>set 16 0
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x9040, total sector=0x12280
Storage start block=598, total block=1162
Total Bad Block in CE: 0
Erase physical block from 886 to 2032
formatstorage Bad block found: 1201
formatstorage Bad block found: 1795
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
At this point it hangs, and drops the USB connection - presumably while the device is reseting the device tree - rendering MTTY useless.
Has anyone come across this issue?
I've not experienced that but I do recall reading similar posts. What happens when you attempt to hard reset using the soft keys and stylus method (as described in the users manual and wiki)? You need to walk before running and this should be the first step before going anywhere near the device with mtty or similar tools. Make sure it's been charging for a few hours so the battery is full or nearly so and ensure you know which buttons to press and are careful just to press the soft keys only. This operation can be fiddly and a few times my attempts at a soft key induced hard reset have failed because my big fat fingers have also ended up pressing other buttons at the same time.
Before finding xda-developers.com I tried a soft reset, which didn't have any effect whatsoever. I've tried soft resetting four times - probably out of frustration.
After those failed, I did a hard reset, which also had no effect. In fact, the MTTY dump on the original post is what happened directly after the first hard reset.
The device is still functional, but it seems unusable for now.
could be a corrupt rom, try flashing another rom
just remembered it isn't hardspl'
phuedx said:
I did a hard reset, which also had no effect.
Click to expand...
Click to collapse
Precisely what does that mean - what happened? If absolutely nothing happened and it didn't start the hard reset procedure (with a little progress bar displayed on the screen), then try hard resetting again (making sure you're only pressing the correct buttons at the same time as when you poke the stylus in) because it may have been finger trouble (it's easy to get this wrong).
I Cook roms so I flash about 15 or 20 times a day. I have a problem suddenly where my TP wont flash.
I get into bootloader and GET USB at the bottom
SPL-0.85.Olinex on the top which mean all should be ok but when i flash it gets stuck on 0 persent
I tried a stock rom, I tried Task 29 flash ...all does the same.
I tried flashing via sd card but it gets stuck on Loading
I tried mtty and did task 28/9 set etc etc and that still works but nothing else
Any ideas?
Its a GSM Rhodium 100 By the way
Grumps said:
I Cook roms so I flash about 15 or 20 times a day. I have a problem suddenly where my TP wont flash.
I get into bootloader and GET USB at the bottom
SPL-0.85.Olinex on the top which mean all should be ok but when i flash it gets stuck on 0 persent
I tried a stock rom, I tried Task 29 flash ...all does the same.
I tried flashing via sd card but it gets stuck on Loading
I tried mtty and did task 28/9 set etc etc and that still works but nothing else
Any ideas?
Its a GSM Rhodium 100 By the way
Click to expand...
Click to collapse
I was doing this while working on my version of the new AT&T ROM and started seeing WIERD issues like it would flash then when it loaded it would say a file was missing. Soft reset and it wouldnt say that but 10 minutes later it would act up again.
I thought I had a brick and was about to call warranty return and flash back to stock. I did the stock flash first (the new one that I was building mine from) and I havent had a problem since. I then put back my modded ROM and have reflashed another 50 times with no problems. That was in Aug.
Grumps said:
I Cook roms so I flash about 15 or 20 times a day. I have a problem suddenly where my TP wont flash.
I get into bootloader and GET USB at the bottom
SPL-0.85.Olinex on the top which mean all should be ok but when i flash it gets stuck on 0 persent
I tried a stock rom, I tried Task 29 flash ...all does the same.
I tried flashing via sd card but it gets stuck on Loading
I tried mtty and did task 28/9 set etc etc and that still works but nothing else
Any ideas?
Its a GSM Rhodium 100 By the way
Click to expand...
Click to collapse
Have you tried on a different PC maybe? I hope you get this sorted out dude, good luck!
hx4700 Killer said:
I was doing this while working on my version of the new AT&T ROM and started seeing WIERD issues like it would flash then when it loaded it would say a file was missing. Soft reset and it wouldnt say that but 10 minutes later it would act up again.
I thought I had a brick and was about to call warranty return and flash back to stock. I did the stock flash first (the new one that I was building mine from) and I havent had a problem since. I then put back my modded ROM and have reflashed another 50 times with no problems. That was in Aug.
Click to expand...
Click to collapse
I was getting the same problems the las week or so a few times it was doing this where it got stuck on 0% but i would just reste and it would work but now its dead. i tried our stock rom in SA and tried from TMUS and ATT but nothing would take. I PM'd oli and cmonex. MAybe they know sumting about mtty that we dont.
seeM_ZA said:
Have you tried on a different PC maybe? I hope you get this sorted out dude, good luck!
Click to expand...
Click to collapse
Jip tried two other one my home pc with Win 7 and my chicks laptop with xp as well but nothing...
The odd thing is that when i switch it off and put it on charge and i unplug it from the charger the orange charge light stays on
check if your windows have automatic updates recently? i posted in your romthread and then made a search to try help you out love you are using threaded e-mail and need your updates , i read some had issues back in the blackstone forum that their usb drivers updated and then had same issue as you, so one remotley possible issue could be your usb drivers somehow mysteriously changed.
but i am not sure just trying to help
mtty output with casrd inserted
set 14 0
HTCST ÚÈÒHTCE
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Network ID is 0xFFFFFFFF
Other SKU
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 HC card
TURBO mode : SD Clk rate 24 MHz
SD Init OK
SDFATChkConf: RhOpenFile() failed RHODCONF.txt
hmmhmm1222 said:
check if your windows have automatic updates recently? i posted in your romthread and then made a search to try help you out love you are using threaded e-mail and need your updates , i read some had issues back in the blackstone forum that their usb drivers updated and then had same issue as you, so one remotley possible issue could be your usb drivers somehow mysteriously changed.
but i am not sure just trying to help
Click to expand...
Click to collapse
Ok ill try thanx. surely it should flash with sd card as well
surley it would... but i find sd card method works sometimeson some roms and other times not, not sure why tho
Nope
No drivers or anything was updated. So thats not the problem
Dammit surely someone must know.
Goin to bed now will try more tomorrow
thx anyways guys
Grumps said:
I Cook roms so I flash about 15 or 20 times a day. I have a problem suddenly where my TP wont flash.
I get into bootloader and GET USB at the bottom
SPL-0.85.Olinex on the top which mean all should be ok but when i flash it gets stuck on 0 persent
I tried a stock rom, I tried Task 29 flash ...all does the same.
I tried flashing via sd card but it gets stuck on Loading
I tried mtty and did task 28/9 set etc etc and that still works but nothing else
Any ideas?
Its a GSM Rhodium 100 By the way
Click to expand...
Click to collapse
Yes it is, move alone now.
PPL nothing to see here!
Is there a way in mtty to replace the spl maybe with file upload or something so i can get it repaired under warranty
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Rhodium, Bootloader Version : 0.85.OliNex
Built at: Jun 23 2009 17:31:14
Copyright (c) 1998-2006 High Tech Computer Corporation
Board ID=0x80
CPU ID=0x4117B362
TURBO HW =1
TURBO SW =1
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 32 (0x20) is reversed block
BLOCK 127 (0x7F) is bad block
OS NOT FOUND !!!
There is a way to flash the stock SPL via SD card. Check out the HardSPL thread and a search should find it.
steviewevie said:
There is a way to flash the stock SPL via SD card. Check out the HardSPL thread and a search should find it.
Click to expand...
Click to collapse
I tried that as well. Stays stuck on loading. Will try some more maybe it will come right
I am having the same problem with my Rhodium. Heres what i get from mtty:
set 14 0
HTCST ÚÈÒHTCE
Cmd>task 29
Format BINFS start
CE start start block=321, total block=3775
ERASE block 2778 FAIL !!!
Write 0xFF start page=0x5040, total page=0x3AFC0
Format BINFS end
Cmd>task 8
Cmd>
I have been trying for hours and hours mtty task 29 and reset and try to load ROM, it still is not working...........
Maybe maybe not
I found a guy close to my office who says he has some flashing software he bought. he reckons he can flash it abck to stock like it came from the factory. Says it will take about 45 minutes cause if it doesnt work he has to open the phone and bridge ic's or something and then flash it. says i can watch him do it. Will charge me 35$ if he gets it right. Will go there in the morning and try and get it sorted. Maybe i can get the software from him somehow. Will let you know
Grumps said:
I found a guy close to my office who says he has some flashing software he bought. he reckons he can flash it abck to stock like it came from the factory. Says it will take about 45 minutes cause if it doesnt work he has to open the phone and bridge ic's or something and then flash it. says i can watch him do it. Will charge me 35$ if he gets it right. Will go there in the morning and try and get it sorted. Maybe i can get the software from him somehow. Will let you know
Click to expand...
Click to collapse
Umm, good luck with that
Yeah, keep us updated on that please...
Right now, mine is stuck on an infinite loop. It wont turn on without being plugged in. When plugged in, I still cant turn it on with the Hardware buttons, but it shows the orange light like its charging. About 5 mins later, it shows the Touch Pro 2 screen, then shuts itself back off. Over and over.
Hey guys, I'm in a bit of a fix. I had an HP Touchpad that I gave up for dead 6 months back, but after browsing on here for a bit I found Jscullins' tpdebrickv004, which miraculously brought the thing back to life. Thing is, it also might have corrupted my partitioning, because the touchpad wouldn't boot up into either webOS or Cyanogenmod after its battery charged all the way.
I ran the webOS doctor which threw an error at 8%, so I looked that up and it seemed to be a partition error. Alright, fixing the internal storage didn't seem to be that big of a deal, so I followed this tutorial here and here, and after both of those webOS doctor went to 12% before throwing an error while flashing.
All the guides I've found online (and I've dug pretty deep) for fixing the 12% haven't given me any luck (like the one here). I've followed all the steps from here, but nothing changed.
In addition, when running ACMEInstaller, there is a resizefat error thrown:
Code:
Initial installation detected, changing LVM layout...
Shrinking media partition size...
/etc/init.d/S90partition: line 63: /webos/usr/sbin/fsck.vfat: not found
/etc/init.d/S90partition: line 70: /sebos/bin/resizefat: not found
resizefat failed! Aborting! Please reboot
I can't figure it out, so I'm reaching out to you guys - is there any way I can save this tablet, and if so, is there any information you guys might need so that you can help me do it? It's different from the problem everyone else is having, which is where webOS doctor freezes, not one where it throws a direct error. I've tried things from threads all over the place, but nothing's ever worked. If there's any help forthcoming, that'd be great, and it'd also help out anyone else with this same problem.
EDIT: Alright, the problem's been solved thanks to jcsullins over at #webos-internals! It was discovered that the touchpad I assumed to be 16Gb was actually 32Gb. To fix the problem, simply reuse tpdebrick with the 32 argument, resize the partitions according to the 32Gb storage, use webDoctor 3.0.0, and you're set!
Hard reset through recovery mode stuck on "Formatting /data" on Nexus 6 phone
So my phone wasn't charging correctly. It was not charging while plugged in and I was a little worried that I might have messed something up. After searching on forums and others problems, I did find something that I had not tried, a factory reset. Now, I would just like to make it clear that in this situation I am a complete idiot and panic over these things, so my actions are truly idiotic. It is 2 A.M. and I didn't have a new charging cable, so I did not try swapping the cables. The only option left that I had hope with was hard resetting my nexus six. I looked up a video on it, and did every move correctly. I confirmed I want the reset to be done and all it has been stuck at is saying exactly this:
Supported API: 3
-- Wiping data...
Formatting /data...
It has been stuck on this screen for at least 45 minutes, and on most forums people say it lasts like 20 minutes. I am freaking out right now guys, please help.
Be patient. If you had a lot of data it takes a while for the device to both format and encrypt the internal storage.