After doing a ton of reading and searching, I still have no idea what my phone is doing. It seems bricked…but only sometimes/partially?
To begin with, I am using ViperXL 3.2.8, elementalX kernel, TWRP 2.5.000 and have been happily using it that way for the summer.
Today I was using facebook to accept a friend request and it suddenly force closed on me. “ oh well” I thought, it’s always been buggy and slow. Hit ok on the msg, then put my phone down. After about a minute, Google play services force closed. Then others began closing, cascading to the point of things like “android core” force closing. My phone then crashed and restarted (its done THAT part before, somewhat often too. Very annoying). I cannot remember exactly, but I think that it then restarted, took foreverrrr to come up, then unlocked the phone and everything started force closing again, faster than I could hit “OK”. Crashed again, restarted…this time got stuck on the Viper boot logo. Let it do that for a while, then restarted by holding power button. Came up, same thing happened. Next I went into TWRP to clear cache and dalvik. When I tried, it fails with the message “cannot mount /cache” about 3 times. Then I went to reboot it, come up and says something like “it doesn’t look like your phone is rooted, would you like to install SuperSU?” whether I click yes or no doesn’t matter, TWRP hangs for a little while and then the phone shuts off.
At this point, I'm mildly panicking, so do some searching. I noticed that “android.process.acore” closed a lot, and it came up that facebook could be an issue. After several tries, got booted up far enough to attempt uninstalling the app. It completed, but the phone then instantly crashed. Checking afterwards, it’s still there. Also, when I do get to into android (about 70% of the time it hangs at the boot animation) and try to access developer tools to enable USB debugging, settings instantly force closes. Same with venom tweaks when I try to change CPU voltage (I'm under-clocked and under-volted, trying to get better battery life..this thing is a total hog for some reason). Oh, and when I get booted up for long enough it’ll come up saying that “internal storage is corrupted and may have to be formatted”.
It gets weirder. Thinking that perhaps TWRP is somehow corrupted, I attempted to flash a different version (2.6 first, then 2.3.3.1). “fastboot flash recovery TWRP.img” completes just fine, no errors. But when I go to recovery, 2.5.0.0 is still there! How it that possible? Also, “fastboot erase cache” completes fine too, regardless of what TWRP says. But I'm not convinced it’s doing anything at this point. Another odd thing, the phone will not successfully reboot with either “fastboot reboot-recovery” or selecting it in the bootloader menu. It shuts off, then the charge light comes on (to indicate booting) but then goes off again before anything comes on screen.
One more thing: when I tried "fastboot oem lock" it fails with "status read failed (too many links)".
I apologize if this is disjointed, I’ve tried a lot of things in a short time and they kind blend together a little.
TL;DR:
Every process on the phone force closes on boot
TWRP cannot mount /cache
TWRP cannot be updated, even though fastboot succeeds
My phone is posessed!
HELP!
Thanks in advance, at this point I'm ready to try anything, if only to get it so I can give it to AT&T and get a different one!
If you put your phone into bootloader does it stay there happily? You could try an RUU, but it's risky at this point if the phone is so unstable.
Sent from my Evita
timmaaa said:
If you put your phone into bootloader does it stay there happily? You could try an RUU, but it's risky at this point if the phone is so unstable.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the quick reply! It does stay in bootloader quite nicely, that's about the only thing it does at this point. Is it safe to flash an RUU being S-off, unlocked and CID 11111111? I was actually planning on trying that next. Also would the proper one be named "RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105"?
Thanks!
Yeah you're s-off so you'll be fine. Click the link in my signature, you'll find links to RUU threads in there.
Sent from my Evita
timmaaa said:
Yeah you're s-off so you'll be fine. Click the link in my signature, you'll find links to RUU threads in there.
Sent from my Evita
Click to expand...
Click to collapse
Great, thanks! I'll report back any results I get...hopefully those results wont be a steaming pile of slag
Flash the RUU and run it like that for a couple of days to see if the problems persist.
The initial problems could well have been because you were using TWRP 2.5, it's full of bugs. After running stock, and if it's fine, when you're gonna flash custom ROMs again make sure you use TWRP 2.6, it's in perfect working order.
Sent from my Evita
timmaaa said:
Flash the RUU and run it like that for a couple of days to see if the problems persist.
The initial problems could well have been because you were using TWRP 2.5, it's full of bugs. After running stock, and if it's fine, when you're gonna flash custom ROMs again make sure you use TWRP 2.6, it's in perfect working order.
Sent from my Evita
Click to expand...
Click to collapse
New problem: When I go to RUU, it gets to the part where it reboots my phone back into bootloader and fails. the phone shuts off and then the charge light comes on, so good so far, then it goes out (like it tries to boot) but then come back on and nothing happens. After a minute or 3 the RUU errors out since it can no longer see the phone. The same thing happens if I try to tell it to reboot bootloader from the bootloader...this is weird.
Also, I cannot relock my phone! All I get is:
Code:
fastboot oem lock ->
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.955s
Side note, the output from "fastboot getvar version-main" is blank. My phone somehow seems to have every glitch known to man right now!
I can get USB debugging enabled! Well, only because it has always seemed to toggle every other time I hook my phone to the computer...but still, I can get to adb commands now. However, I'm not really sure that got me anywhere at this point
Put your phone into bootloader/fastboot manually and then run the RUU. Don't worry about relocking.
Sent from my Evita
timmaaa said:
Put your phone into bootloader/fastboot manually and then run the RUU. Don't worry about relocking.
Sent from my Evita
Click to expand...
Click to collapse
That's what I've tried doing, the RUU decides to reboot it from being in bootloader back to bootloader for some reason, and that's where it gets hung up.
I'm beginning to think there is something seriously wrong with my cache, bc after I get my phone to boot the only really reoccurring stopped process is android.process.acore, which according to Google has something to do with programs and how they access cache?
Thanks for the help thus far!
Try the fastboot command:
fastboot erase cache
Try that a few times, then try RUU again.
Sent from my Evita
timmaaa said:
Try the fastboot command:
fastboot erase cache
Try that a few times, then try RUU again.
Sent from my Evita
Click to expand...
Click to collapse
Will do. So a few minutes ago I got to 10% with the RUU, this time run with the phone booted and in USB debug mode. Got to the HTC logo on a black background, it sent the RUU..then went into "waiting for bootloader" while my phone non-booted, as usual.
While I was doing some research, I left the phone at the bootup animation for like 10 min, and it finally booted with a message about a UUID (might have been UDID, not sure) mismatch. Don't know if any of this means anything, but it's certainly very odd.
Forgot this earlier, but sometimes it will boot for a while and go to a black screen, with the backlight still on.
Thanks again!
So, I've been trying things, and I have discovered that I am completely unable to make any file system changes whatsoever. Oh sure, I can mount the sd card in TWRP and delete/move things. But after a reboot, it acts like I never touched it, and it's right back to how it was before. Same with flashing a recovery. I've even tried getting it to boot and using adb to shell in and delete files that way, but still no change.
I'm running out of things to try....I almost want to take it in to AT&T and see if I can at least pay them to do something about it...heck, at this point I'd pay for a refurb phone!
Anyone has any ideas, let me know
to Flash an RUU if the ruu installer is giving you errors:
1)extract rom.zip from ruu.exe; google it, basically you open the ruu installer and search your temporary(Appdata in windows) files for rom.zip
2)fastboot oem rebootRUU
3)fastboot flash zip rom.zip (with atleast 70% battery as it takes a while)
charge the phone from any custom recovery if you cant boot it up to charge it(preferably twrp as it turns screen off to charge quicker)
That doesn't accomplish the same result as running an RUU at all, it's just like flashing a ROM.
Sent from my Evita
Vcek said:
to Flash an RUU if the ruu installer is giving you errors:
1)extract rom.zip from ruu.exe; google it, basically you open the ruu installer and search your temporary(Appdata in windows) files for rom.zip
2)fastboot oem rebootRUU
3)fastboot flash zip rom.zip (with atleast 70% battery as it takes a while)
charge the phone from any custom recovery if you cant boot it up to charge it(preferably twrp as it turns screen off to charge quicker)
Click to expand...
Click to collapse
Thanks for the reply! I just tried that, and when I run "fastboot oem rebootRUU" it does the same thing as before: shuts off, the charge light comes on, then goes of for 2-3 seconds, then comes back on and the screen is off and it stays that way. However, I then ran "fastboot flash zip rom.zip" and while it said "waiting for device" got it back into fastboot mode. Then this:
Code:
< waiting for device >
sending 'zip' (576544 KB)...
OKAY [ 26.127s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 26.169s
no this must be run from RUU mode, try unlocking your bootloader first(then relocking it)
timmaaa said:
That doesn't accomplish the same result as running an RUU at all, it's just like flashing a ROM.
Sent from my Evita
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i am talking about this kind of rom.zip
Yeah I know that, but that only updates the ROM partition to stock which isn't what we're aiming for. We're trying to do a complete return to stock, all partitions, which that method won't accomplish.
Sent from my Evita
the ruu installer does nothing more than flashing the rom.zip which contains all the partitions(21 partitions including hboot,sbl's,radio,touch,data,system,boot,recovery).
Ask around, I think you'll find that method doesn't do the whole job.
Sent from my Evita
It seems that the issue here is that my phone cannot get into RUU mode, since it cannot complete a reboot when sent a software command. As I said before, when I execute "fastboot oem rebootRUU", it shuts off but then won't come back on. Same with "fastboot reboot", "fastboot reboot-bootloader", and any adb reboot command. This issue also occurs when rebooting from the actual boot loader menu, as well as recovery. However, in TWRP, if I hit "reboot recovery", it won't come back up. But if I hit "reboot bootloader" (or system, I believe), it will in fact come back up.
Thanks for the replies! If I can only get to RUU mode I think we can fix this
Related
Hello XDA-Developers. Long time lurker, first time poster. After watching the "Noob" video, I feel compelled to apologize in advance for needing to call on your greater experience and knowledge.
The specs (If there's anything left out that you might need, let me know. If I can get to it, I'll post it):
Model: Samsung/Google Nexus S GT-i9020A
Bootloader Ver: I9020XXKA3
Baseband Ver: I9020UCKD1
Carrier: Bootloader says ATT, my actual carrier is Telus.
ROM: Cyanogenmod 7.1 RC1 Experimental
Kernel: Netarchy's Nexus S CFS 1.3.6 Stable
CWM Ver: 3.0.2.4
The problem:
I've been running CM7 for the last couple of months (since I got the phone). I woke my phone, opened the Market, and it suddenly went into a boot loop; not from the beginning Google logo though, just the Nexus S boot screen, and very laggy. I let it try to boot for a while, and did a battery pull when it was (to my apparently idiotic mind) obviously not going to. Put the battery back in and it just sat there on the Google logo for a good half hour.
Here's where things get a little curious. I pulled the battery again, and PWR+VOL UP to get to the bootloader. Load up CWM, and lo and behold, I can't mount the internal SD or the DATA partition. Thus, I can't restore, can't flash anything new, and I've got a phone good for a whole lot of nothing.
What I've done so far:
I've spent the last 9 (yes, nine.) hours searching the internet with increasingly more vague and unrelated search terms. The best solution I've found so far: "Take out the SD card, pull everything off of it and format it. Put it back in to the phone, and presto!" A caveat that you all know: The Nexus S has no removable SD card.
One of the first things I tried, having only fastboot at my disposal, has turned out to be the worst thing I could have possibly done. I tried locking then unlocking the bootloader again, to wipe everything and start from an empty phone. Well, the boot loader won't unlock again. Fastboot sees my Nexus S, fastboot oem unlock yields the familiar "Unlock Bootloader?" screen, and when I select Yes.... Nothing happens. The phone stops responding, the command prompt sits there with "c:\fastboot-path>fastboot oem unlock ..."
Now, the solution to this, according to some, is to wait long enough and do a battery pull to finish unlocking the bootloader. This has yielded no results. Further research indicates that the internal storage may have some kind of hardware problem, a known issue with the Nexus S. Being forced to look at sending the phone in for repairs, I've become a little desperate. I need to removed the CWM somehow. I've got the stock recovery.img, but I'm stuck with a locked bootloader. I did a lot of research into using ODIN to recover the phone back to stock, but I can't get the phone into Download Mode. Using the VOL UP+DOWN then plugging it into USB throws me directly into the screen asking me to unlock my bootloader... except there's no way to say yes or no.
At this point, I'm seriously panicking. This is my only phone, and I'm really quite broke. I can't afford to pay for repairs if they find the phone is out of their ridiculously strict warranty. I can't afford to be without a way to get a hold of me when I'm not standing next to my fiancée or staring at my GMail inbox... Quite literally, my job depends on this phone.
Help me XDA-Developers... You're my only hope.
Update: Odin seems to detect the phone even though it doesn't say download mode, BUT the part of the recovery that writes data fails, and it just hangs. I can't restore using that either, I guess.
Update 2: Forgot to mention, the "Download Mode" screen looks like the unlock bootloader prompt (the green title and the first three paragraphs), and under that it has "USB Control Init//USB Control Init End". When I run Odin, the words "Verify Image (IPBL) ... Success" appear in read above the USB Control Init message. It's at this point it hangs and does nothing for over an hour. After a battery pull, the message "Complete(Write) operation failed." comes up in Odin.
Is there anything I can do here?
sorry im just heading to bed so this is more of a reminder for me to post tomorrow but
what does it say when you try and mount the sd in clockwork? have to tried taking a logcat?
don't panic.
CWM Mount /sdcard returns the error "Error mounting /sdcard!". The same goes for /system and /data.
As far as a logcat goes, fastboot sees the Nexus S, but the ADB shell does not. Sits at "waiting for device" indefinitely if I try at the bootloader. If I try in CWM Recovery, it returns the error: "/shbin/sh: exec: line 1: logcat: not found".
Something must have happened to my /boot partition as well. Doesn't hang at the Google logo anymore, just dumps me back into the bootloader, with a message at the top saying "FASTBOOT MODE - NO BOOT OR RECOVERY IMG". Given that the CWM recovery is still there, I have no idea what's going on with that one.
I am not sure but I think that you are not in the Download Mode. You should see big "Download mode" text on your screen. And you can't boot your phone because you wiped it already with the unlock command therefore the message - no boot no recovery. ADB doesn't work in bootloader.
Question - when you boot into bootloader does it says locked or unlocked? I think that your NAND memory is corrupted, flashing with ODIN could help but you need to see the "Download mode" text in order to flash with ODIN.
My bootloader is currently locked, which is turning out to be a real headache. I can't get the "fastboot oem unlock" command to complete. As I type this, I let the command run for ~15250 seconds (yes, 15 thousand) and did a battery pull, given no indication that it had completed.
Does your Download mode look like this? If yes, that is right. Have you also checked that your Device is recognized from Windows and that the drivers for the download mode are installed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@brainmaster: The drivers seem to be installed properly. "fastboot devices" shows the proper serial. My "Download Mode" does NOT look like that. I'll post a picture as soon as I can. The best way to describe the screen I get when doing the "VOL UP+DOWN" button combination while plugging in the USB is the top half of the screen is the first three paragraphs of the "Unlock Bootloader?" prompt, and the bottom half is the bottom part of the bootloader screen.
It's the only method (other than a 301K resistor on a micro-USB) that I've found to get the Nexus S into download mode. Is there another way?
As an aside, are there different drivers for Download Mode? My phone shows up as "Android 1.0" when using fastboot or the screen that's supposedly "Download Mode", and from when I first rooted the phone, I know it shows up as "Nexus S" when plugged in and actually booted into a ROM. I've applied the Samsung ADB interface drivers to those, and the fastboot works. Obviously I can't check the ADB shell right now.
That is the thing - you are not in the Download mode. If you wore then you will see "Samsung CDMA Modem Device" installed (that is for mine although its GSM device).
And the Download mode should look like that photo with two additional text lines.
I think that its bricked, sorry.
You could pull out battery and let it so for at least 5 minutes, and then try the Download mode - you are doing it right: Vol Down + Vol Up (When the Phone is off) and then plug the USB Cable in the PC.
Thanks for the replies, brainmaster.
Is there a way of completely bricking the phone at this point? I'm trying to figure out a way that the phone will appear to still be under warranty. The only issue is the CWM: if I could get rid of that somehow, then I'd be golden to send this sucker in for repairs.
Only problem is my bootloader's locked.
Don't take 100% for sure, but I think that you already wiped the CWM, since there is no boot image then there is also no recovery.
I still have access to CWM Recovery :|
Have you tried:
fastboot erase recovery
Yes, but the fastboot returns the error that the bootloader is locked and that I should run fastboot oem unlock to run the erase.
Well, all my troubleshooting efforts failed, even the 301k resistor jig. I sent the phone in for repairs on Friday, August 5th. As of today, I learned it's with Samsung's technician right now, and nobody's called about a voided warranty, so here's hoping.
Figured I wouldn't leave the thread at a dead end, in case anyone stumbled onto this from google/xda search:
Samsung sent the repair ticket back to the Telus store with the repair code "REPLACE", so they just gave me a new handset. I have no idea why they just said replace but I have my Nexus back, and that's all that's important.
So are you gonna re-root your Nexus, LOL? Or too much of a headache?
Hah, I rooted and stuck CM7 on it within two hours of knowing the new one I got wasn't busted. Stock just doesn't cut it, potential headaches or not.
Serious Nexus S is serious.
litanyoffail said:
Hah, I rooted and stuck CM7 on it within two hours of knowing the new one I got wasn't busted. Stock just doesn't cut it, potential headaches or not.
Serious Nexus S is serious.
Click to expand...
Click to collapse
LOL!! Yeah, I'm new to the Nexus from HTC Evo 4g and I was on the fence whether to root or not, but I'm gonna take the plunge!! Very unlikely to brick a device except in the most unfortunate of circumstances!
The last week I have been struggling to unbrick my i9023 Nexus S. Without any luck... Let's start at the beginning, how I bricked my Nexus S. If you don't think this is relevant you can skip it.
Stay with me because it's going to be a long thread...
How I bricked my Nexus S
I was running a CM9 Nightly (from around 10 March) until a week ago, together with the matrix CFS 18.0 kernel. I had a problem with rebooting. Every time I rebooted, it would take 2 or 3 tries before it actually started. First it would just reboot again, or even freeze. So after almost a month I was kinda tired of that problem, so I decided to flash a new CM9 Nightly, the one from 7 April. I flashed the Nightly like I always do, wipe cache/dalvik, and I also flashed the new matrix CFS 18.5 kernel, + the latest gapps and the reloadedICS mod. It was working fine. I rebooted a couple of times more into recovery because I wasn't happy with the reloadedICS mod. Everything was still working fine.
The battery was draining very quickly though. I was watching TV for an hour and when I decided to go to bed the battery was already dead. So I put it in the charger because I wanted to check my facebook before I went to bed. It booted fine, but when I started loading facebook in the browser, my phone freezed. I wasn't really alarmed because, well, let's face it, that's the risk with nightlies. So I pulled out the battery, something I have done a lot of times since I started rooting/flashing. After that: dead. No reaction. No charging icon when it was plugged in the charger. No vibration when I pressed the power button, nothing. A brick...
What I've tried
Although it is uncommon, I wasn't the first to brick a Nexus S. Apparently it had something to do with updating to ICS 4.0.4, on which the april 7 nightly was based on I guess.
Luckily there was AdamOutler's Unbrickable Resurrector. After some setbacks I managed to get the Resurrector working. And against all odds I "unbricked" my Nexus S on the first try! Well, I got it into download mode (home and search button). The only problem was that I still didn't have a screen. The home and search button were lit up, but the screen was still black... And according to most people, it isn't supposed to be black...
Ignoring that fact, I downloaded fastboot and tried to flash bootloader.img, as instructed. It didn't work because my bootloader wasn't unlocked, something that struck me as very weird because it definitely was unlocked before the brick. So I tried to unlock the bootloader. But for that, you need a screen... With a lot of luck I managed to unlock the bootloader. Don't ask me how, but after a few tries I succeeded.
I was making progress. And I was happy about that . So I tried to flash the bootloader again. But it still didn't work. "Write failed". After some internet research I found out wat the problem was. It had something to do with the bootloader and radio being a different version. I used the command "fastboot getvar all" and it told me the following:
- Bootloader version: i9020XXKA3
- Radio version: i9020XXXXX
Apparently the radio version isn't supposed to be XXXXX, and that's why I couldn't flash bootloader.img or radio.img. Also, this is the reason that I couldn't boot my device in the first place.
Obviously I wasn't the only person with this problem. I found a guy that had the same problem as me. He used the command "fastboot boot recovery3101.img", using an older version of CWM recovery. If you used that command, your phone would always boot into recovery, so that you can flash a new OTA.
So I downloaded that older version of CWM, and I tried the same command. And it worked! The home and search button were off and the menu and back button were on! But, still no screen. And the guy that used the same command did have a screen...
I had no clue on what to do next, so I pressed the power button, in the hope that I could boot my device directly into recovery after that. I pressed the power button, the backlight of the soft keys went out... and that was my poor Nexus S' last breath of life...
I tried the resurrector tool after that... "failed to write"...
So, am I really f***ed?
I just can't comprehend that my Nexus S could be dead forever... The hardware is fine, it's just the software that keeps it from booting up! The idea of that is crazy... Certainly with a Nexus S for christ's sake!
So, what am I to do? I kinda gave up hope...
UPDATE: SITUATION ATM
1) With AdamOutler's Unbrickable Resurrector I can get into download mode. Sometimes it doesn't work but when I pull out the battery it works again.
Now I can flash every partition with fastboot, except for;
- the bootloader (which is XXKA3)
- the radio (which is XXXXX)
The probable cause for this is the fact that "secure: on", according to "fastboot getvar all". This is very weird because no one on the internet has a Nexus S with "secure: on". It is some security for i.a. HTC devices.
When flashing the bootloader or radio, I get the following error:
sending 'bootloader/radio' <file size>...
OKAY [time]
writing 'bootloader/radio'...
FAILED <remote: Write Fail>
finished. total time: time
Click to expand...
Click to collapse
Using "fastboot -w update image-******.zip":
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
After that the flash goes fine. When it reboots, my phone is dead again. This is because the radio didn't change with this zip. If there would be a radio in that zip, it would not have worked anyway.
The radio is booted first in android, and because of this I can't do anything (the XXXXX version is wrong). This is probably also why the recovery doesn't work properly (see below). And the "secure: on" prevents me from flashing another radio.
2) With "fastboot boot recovery.img" I can get in the recovery mode. ADB "shell" works, and so does "push" and "pull". The screen is black, though. Even with a very strong flashlight I still can't see anything. I can only see 2 or 3 lines (it is different with each recovery). When I press the volume buttons to scroll, I see no changes at all on my screen.
What I have tried in recovery:
- Installing an OTA zip. I can ADB "push" an OTA zip. I have checked that with ADB "shell". Since I can't see anything I have to guide myself using pictures from CWM menus. But nothing happens. There is no sign that the install worked. The only sign that I'm actually in recovery is that the menu and back softkey are lit up, and that when I press the power button without pressing the volume buttons first, my phone powers off (this is because "reboot system now" is on top of the list in recovery, I guess).
- ADB pushing anything on /sdcard. When I turn off my phone after that and resurrect it again, the file is gone. This could be because my memory is dead. But isn't this because the resurrector removes it? Anyway, when I push a file with ADB, it definitely is on my sdcard. Only after rebooting and resurrecting it isn't...
NOTE: Rebooting/booting in whatever mode doesn't work. The only two things I can do are listed above. The moment I plug out my device, I have to use the resurrector again. Because of this there it makes no sense to flash a recovery, since I can't boot anyway. The only way I can get into recovery is by using "fastboot boot recovery.img".
NOTE 2: Recovery.log shows some errors. I will post the whole log soon...
Possible solutions?
A) How can I flash a different radio, despite of "secure: on"?
B) Can we change "secure: on" to "secure: off"? For HTC users this is as normal as "fastboot oem unlock", but there is no one on the internet that has a Nexus S with "secure: on".
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
polobunny said:
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
Click to expand...
Click to collapse
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Androyed said:
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Click to expand...
Click to collapse
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
polobunny said:
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
Click to expand...
Click to collapse
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Androyed said:
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Click to expand...
Click to collapse
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
polobunny said:
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
Click to expand...
Click to collapse
I have used other batteries (luckily I have friends with a Nexus S), but that doesn't change anything.
The big question is, how can I get into download mode again? The resurrector worked at first, but when I flashed CWM to the boot partition and rebooted after that, I can't get any signs of life out of my Nexus S. Resurrector doesn't work anymore, nothing...
The weird thing is, the moment I used the "fastboot boot recovery.img" command, windows stopped recognising the device. But according to the soft keys, it did go from download mode into recovery mode. I still didn't see anything, but I guess that's because the SLCD bug.
I guess I should not have had rebooted when I was finally in recovery...
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
polobunny said:
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
Click to expand...
Click to collapse
Nope, no problem at all.
The only way I could get some life out of it, was by using the resurrector tool. But now even that isn't possible anymore...
Is it actually possible to really perma-brick a Nexus S? Or are people just saying that because they lack the knowledge to unbrick it. I'm pretty sure it can't be a hardware problem. It is the software that is preventing it to boot up. That's what a brick is, right?
WOW, GOOD NEWS!
After a few (totally random) tries, I managed to resurrect my phone again! I am now in the download mode. From here I can use fastboot boot recovery.img. I still don't have a screen though...
When I get into recovery (without screen), what should I do then? Because previous time, windows stopped recognizing my phone... Should I push an OTA to my Nexus S BEFORE I use fastboot boot recovery.img? And if so, how? And if I do so, how on earth am I going to manage to install that zip without a screen? There are a lot of files on my sd card... An option would be to wipe them all, if that's possible. Another option would be to give it something starting with a 1 or an A so that it comes up on top of the list.
The problem is that I can't flash anything because of that i9020XXXXX radio version.... Is there any way I can flash another radio? Just flashing with fastboot doesn't work because of that XXXXX version...
Got it into recovery again! Windows recognized USB mass storage for a second, but not anymore.
Using a flashlight I can see that there is SOMETHING on the screen, but when I press the volume buttons to scroll nothing changes...
Another breakthrough! I installed ADB drivers, and now I got ADB working!
Can you control CWM recovery from the computer, using ADB? Because now all I have to do is flash an OTA, but I can't see anything, not even with a flashlight...
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
wmdunn said:
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
Click to expand...
Click to collapse
I'm not really good at the technical stuff either. I'm like this dog:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I can learn quickly. I know how to push a file to the SD Card using ADB. I also now how to wipe all user data using fastboot. Combining that, I have a SD Card with only 1 file: the OTA I want to flash. That should make thinks a lot easier since I can't see a damn on my screen.
My problem wouldn't even that bad, if it weren't three problems combined. Normally when people unbrick their phone with the resurrector, they can flash a bootloader.img. But I can't, because of that i9020XXXXX baseband version. I tried to flash another radio.img but that doesn't work either. To top this off, my screen doesn't work. Even with a flashlight I only see that there's SOMETHING on the screen, but I don't see any changes when I press the volume buttons for example.
The problem with not seeing anything is that I don't know if what I did, worked. I can't confirm anything. Maybe when I flash the OTA it says: update failed. But I can't see that so how would I know?
That's why I was hoping for a way to not only push files to the SD Card using ADB and wipe all user data using fastboot, but also for a way to install zip from SD Card using ADB/fastboot.
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Harbb said:
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Click to expand...
Click to collapse
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
[Q] i9023 very freaking bricked, lost all hope...
Pls help i am also facing same problem i have given NS to service center they said they will be changing its mother board is there any thing can b done.
Androyed said:
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
Click to expand...
Click to collapse
Try installing factory images from fastboot, You dont need the screen for that just get it to download mode.
http://forum.xda-developers.com/showthread.php?t=1572307
in cmd it says waiting for device and nothing happened its blank
Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2
So, where to start?
I'll start with my broken screen:
1 -new screen ordered (complete assembled LED+digitizer)
2 -installed the new screen, put phone back together and turned ON
3 -phone immidiately went into bootloop!
4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)
5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger
6 -ordered new battery, it arrived today. Phone got back on and into bootloader.
7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!
8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5
The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on
There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.
I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.
Sverrebob said:
So, where to start?
I'll start with my broken screen:
1 -new screen ordered (complete assembled LED+digitizer)
2 -installed the new screen, put phone back together and turned ON
3 -phone immidiately went into bootloop!
4 -did some google research and found this site and figured out how to get into bootloader (vol down+pwr)
5 -bootloader works fine, but left it on too long with phone not on charger (battery might have died?) phone not turning on and red LED blink while in charger
6 -ordered new battery, it arrived today. Phone got back on and into bootloader.
7 -unlocked bootloader by using the HTCDEV com site, and their method. worked fine!
8 -then turning phone back on after a failed restart after the bootloader unlock, and it wont turn on taking me back to stage 5
The phone was connected via usb during the bootloader unlock and the restart after. But I never got it back on
There is one thing I am curious about aswell - the phone get very hot around the SD-card slot and it smells warm electronics. I dont know if this is normal but I cant say I noticed this before when the phone was working. I am very sure that I re-assembled the phone correctly after replacing the LED+digitizer as both these parts came to me already assembled.So only thing I did was removing the screen case with the LED and digitizer and replacing it with the new one.
I really hope anyone have ANY input on this as I would really like to get my phone back on and working so I can root it.
Click to expand...
Click to collapse
Pull out the battery then place again and after that try to go into bootloader ..
Also phone showing red light while charging ?
ahsan64 said:
Pull out the battery then place again and after that try to go into bootloader ..
Also phone showing red light while charging ?
Click to expand...
Click to collapse
I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks
The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts?
EDIT: Yes when this problem occurs the red LED blinks "on long" "off long" while the phone is in charger.
Sverrebob said:
I let the phone cool down (it get's very hot very fast!) and removed battery and replaced it again, phone ON and in bootloader now, thanks
The heat issue still remains tho, I wonder if this might be the source of this unstable situation with the phone not turning back on and then suddenly after a cooldown it does... any thoughts?
Click to expand...
Click to collapse
Are you using Stock Rom or Custom Rom ..
The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..
ahsan64 said:
Are you using Stock Rom or Custom Rom ..
The heat issue is normal but sometime it's due to overclocking 2d/3d GPU ..
Click to expand...
Click to collapse
The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...
Sverrebob said:
The phone is completely stock except the replaced screen. I encountered the bootloop after replacing the screen and it's been like that since...
Click to expand...
Click to collapse
Two methods:
1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .
NOTE: You can skip step 2(S-OFF PART) in above guide
2: Or just find official RUU and install it and see if phone boots ..
ahsan64 said:
Two methods:
1: Follow this GUIDE if phone Hboot is 1.27 or 1.29 and flash any custom Rom .
NOTE: You can skip step 2(S-OFF PART) in above guide
2: Or just find official RUU and install it and see if phone boots ..
Click to expand...
Click to collapse
Ok I will try this thanks!
Just got the phone back on and into bootloader, had to let it cool off again to get it on. I feel somewhat connected to the other thread in this forum - "Dead sensation" ...
Update :
I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.
Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?
And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/
De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/
Sverrebob said:
Update :
I cant seem to access the sd card when I have my phone in Fastboot usb mode and since my rom is f**ked I cant boot into the phone either.
Also recovery fails, probably due to fastboot still active, any way to turn that off when I cant get past bootloader?
And if anyone know how I can access the sd card from phone on my PC I would appreciate it :/
De-assembled my phone again just to recheck all connectors etc, all seems just fine... really confused on whats up with this phone now :/
Click to expand...
Click to collapse
it would be better to use a ruu.exe and see how it goes then
http://forum.xda-developers.com/showthread.php?t=1672425
my bootloader reads as follows:
***relocked***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
my cid is HTC__Y13 and my version-main is 3.33.401.53
using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M
I dont know if this is correct, I dont see anything resembling my cid in there.
note: bootloader is relocked using
Code:
fastboot oem lock
as the http://forum.xda-developers.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...
Sverrebob said:
my bootloader reads as follows:
***relocked***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
my cid is HTC__Y13 and my version-main is 3.33.401.53
using this info I can only find this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M
I dont know if this is correct, I dont see anything resembling my cid in there.
note: bootloader is relocked using
Code:
fastboot oem lock
as the http://forum.xda-developers.com/showthread.php?t=1672425 guide says. Following that guide now but is confused on the RUU to get. Gonna try with the RUU I have downloaded now and I'll let you know how it goes...
Click to expand...
Click to collapse
Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?
I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.
Sverrebob said:
Ok I completed the exe RUU file and it told me it was completed, STILL I only get green HTC logo and bootloop. Entering bootloader the pgone tells me the battery voltage is too low, will this prevent the phone from booting normally?
I have it on FASTBOOT AC now and hope it will charge, then I'll try to restart the phone and see if I can boot it.
Click to expand...
Click to collapse
after charge use the command to reboot from bootloader if it fails normally
fastboot reboot
rzr86 said:
after charge use the command to reboot from bootloader if it fails normally
fastboot reboot
Click to expand...
Click to collapse
Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.
Recovery from bootloader menu also end up the same way as above.
Factory reset aswell.
Also, every time I get into bootloader it does this check you can see on this screenshot here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any inputs on this, or is this normal when the SD card is empty?
During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?
I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.
It kinda cooks down to some hardware fail, atleast in my opinion? I'm really at my wits end here
Sverrebob said:
Tried that several times already, same thing happens, white screen with green HTC , goes into the usual bootloop.
Recovery from bootloader menu also end up the same way as above.
Factory reset aswell.
Also, every time I get into bootloader it does this check you can see on this screenshot here
Any inputs on this, or is this normal when the SD card is empty?
During the white bootloop screen with green HTC the SD card does get recogniced by my PC and shows up in explorer briefly before phone reboots again, so it cant be the SD card reader can it?
I consider myself pretty much advanced when it comes to techology and I have been reading up on all this stuff around phones and what you can do with them. I feel I have gotten a pretty basic understanding so far, and from my point I really does not see why my phone wont behave normal.
It kinda cooks down to some hardware fail, at least in my opinion? I'm really at my wits end here
Click to expand...
Click to collapse
Hi, gonna try help out
firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue
Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)
thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please
heavy_metal_man said:
Hi, gonna try help out
firstly, your screen shot. that will always happen when you boot into the bootloader with an sd card in the phone. doesnt matter whats on it, it will always check it for those files if it detects it. its not an issue
Second, when you try to boot into recovery, does it ever make it? or does it always sit at the splash screen. ( the white background with the green htc letters.)
thirdly, if you are willing to unlock your bootloader again can you place the attached recovery.img and place it into your adb/fastboot folder, and then when in fastboot usb issue the command fastboot boot recovery.img , hopefully it will boot into 4ext recovery temporarily, and allow you to try get some system information. (assuming your new touch screen works ) you may get some warnings if/when 4ext boots up. make a note of all of them and reply to here please
Click to expand...
Click to collapse
I appreciate the reply
It have never gotten into recovery, it always stuck at the "splash screen" and have done so with both 4EXT and CWM.
thirdly: I unlocked the bootloader and put your attached recovery.img into the fastboot folder, ran the command with phone in "fastboot usb" and ended up on splash screen as always, it stays there for a few seconds then it goes black. It seems like the phone is rebooting but the screen remains black. I do, however, get the well-known sound of an usb device beeing attached and removed again, with a few seconds silence in between. Screen remains black. To solve this mysterious "bootloop" I remove the USB cable, gives it half a minute and do the vol-down pwr button method and then I am back in the bootloader again.
Just for fun I have tried the recovery menu in bootloader with the phone not connected to usb, same splash screen here. It just seems that my phone really dont want the recovery to work :/
extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...
weird!
ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:
Code:
C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.493s]
booting...
OKAY [ 0.002s]
finished. total time: 1.495s
Sverrebob said:
extra info: figured out that the screen went black after one splash screen due to me pressing vol-down. It apparently does 3 reboots showing splash screen, then a couple mysterious black screen reboots and then another splash screen reboot three times... I have stopped this weird cycle now to save my poor battery, but it seems that it would just have continiued this behavior of 3 splash screen reboots - 2 black - 3 splash and so on...
weird!
ALSO; this is the response from fastboot command I get when trying to boot the recovery from there:
Code:
C:\android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.493s]
booting...
OKAY [ 0.002s]
finished. total time: 1.495s
Click to expand...
Click to collapse
did you try to boot into safe mode?
once you will see the splash screen hold volume down until it gets you to the safe mode
see if it works
rzr86 said:
did you try to boot into safe mode?
once you will see the splash screen hold volume down until it gets you to the safe mode
see if it works
Click to expand...
Click to collapse
Thank you for the tip, unfortunately it didnt seem to work
I pressed volume down as soon as the splash screen appeared after I executed the <fastboot boot recovery.img> and it just hang there for a few seconds then the phone rebooted and I ended up in the bootloader again.
Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.
Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me just a hunch I have
Sent from my Nexus 7 using Tapatalk 4
heavy_metal_man said:
Hmmm. This is very strange indeed. My theory is that your internal partitioning may be messed up, so when the phone tries to boot things are not in the right place. But that doesn't explain why it won't fastboot boot, as fastboot boot should boot the .IMG into the ram and not attempt to flash it. It may well be down to a hardware fault. If your ruu ran without any errors then it should have fixed any partition errors. You could try extracting the boot.IMG from the ruu and use the fastboot boot boot.IMG command and see if that gets you any farther.
Also when your phone goes into the black after the splash screen, can you keep it connected to the PC and issue the command adb devices for me just a hunch I have
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
So get this, tried to <fastboot boot recovery.img> again in order to obtain this black screen and do your <adb devices> and nothing! It's like the phone heard you and decided to "behave".....
It did 10 perfectly normal reboots with the splash screen every time, and the 4th and 5th time it even vibrated once...!
This whole charade is almost a little funny to me now, but clown phone or not, I'm not giving it up yet
I managed to google how-to extract the boot.img file from the RUU exe, it was a rather tidious operation
I found a very well explained guide on it here; https://sites.google.com/site/androidbyyorzua/home/tutorials/extracting-rom-files-from-htc-ruu
And not suprisingly all I got out of it was a error msg
Code:
C:\android>fastboot boot boot.img
creating boot image...
creating boot image - 3868672 bytes
downloading 'boot.img'...
OKAY [ 0.984s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.999s
Something wrong with my phones RAM maybe?
EDIT: I tried the fastboot command to flash the rom.zip and this is how it went.
Code:
C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.499s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: not allowed)
finished. total time: 57.819s
Tried it again with bootloader RELOCKED and it took alot more time and was slightly different, but still same error msg
Code:
C:\android>fastboot flash zip rom.zip
sending 'zip' (436283 KB)...
OKAY [ 57.685s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 134.679s
I was on Digitalhigh GPE with the Elite Kernel and the Verizon firmware offered on their thread (http://forum.xda-developers.com/showthread.php?t=2716306) and my power button wasn't working. Pressing it wouldn't turn the screen on/off and holding it wouldn't access the power menu. Holding it to restart/hboot would work so the power button was obviously not broken and I decided to just reset everything. After a failed ruu, my phone keeps switching between the ruu screen (pic attached) and the htc 4 ! screen. I tried the exe ruu (http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103) but it didnt work because the phone just keeps rebooting itself into the htc 4 ! screen. I don't have extensive experience with adb/fastboot commands, but tried flashing both the L hboot and RUU offered in that thread and got the "error: cannot load" response. Everything was backed up before I ruu'ed but my google/xda searches havent gotten me anywhere.
KeltischDeutscher said:
I was on Digitalhigh GPE with the Elite Kernel and the Verizon firmware offered on their thread (http://forum.xda-developers.com/showthread.php?t=2716306) and my power button wasn't working. Pressing it wouldn't turn the screen on/off and holding it wouldn't access the power menu. Holding it to restart/hboot would work so the power button was obviously not broken and I decided to just reset everything. After a failed ruu, my phone keeps switching between the ruu screen (pic attached) and the htc 4 ! screen. I tried the exe ruu (http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103) but it didnt work because the phone just keeps rebooting itself into the htc 4 ! screen. I don't have extensive experience with adb/fastboot commands, but tried flashing both the L hboot and RUU offered in that thread and got the "error: cannot load" response. Everything was backed up before I ruu'ed but my google/xda searches havent gotten me anywhere.
Click to expand...
Click to collapse
Pay attention to the thread... He makes a statement about this issue there.
To flash, put it into the fastboot folder (which should be the platform-tools folder within the Android SDK) and open a command window there. Use the command 'fastboot flash zip nameoffile.zip. It should work. Until it can successfully flash, you are boned.
If this doesn't work, I have one more method you can try.
ironbesterer said:
Pay attention to the thread... He makes a statement about this issue there.
To flash, put it into the fastboot folder (which should be the platform-tools folder within the Android SDK) and open a command window there. Use the command 'fastboot flash zip nameoffile.zip. It should work. Until it can successfully flash, you are boned.
If this doesn't work, I have one more method you can try.
Click to expand...
Click to collapse
Retried that and it failed again. After doing another oem reboot command (which I did idk how many times during the process), the phone randomly got passed the ruu screens, into the white htc boot screen with red text, started up and seems to be working fine. After work I'm going to retry the ruu via the exe this time
Edit: Now it seems that my motion launch, auto-rotate, and proximity sensors aren't working so the only way I can use it at work is to plug/unplug the usb to turn the screen on.
KeltischDeutscher said:
Retried that and it failed again. After doing another oem reboot command (which I did idk how many times during the process), the phone randomly got passed the ruu screens, into the white htc boot screen with red text, started up and seems to be working fine. After work I'm going to retry the ruu via the exe this time
Edit: Now it seems that my motion launch, auto-rotate, and proximity sensors aren't working so the only way I can use it at work is to plug/unplug the usb to turn the screen on.
Click to expand...
Click to collapse
Now flash a custom recovery via flashify and try flashing a custom rom.
KeltischDeutscher said:
Retried that and it failed again. After doing another oem reboot command (which I did idk how many times during the process), the phone randomly got passed the ruu screens, into the white htc boot screen with red text, started up and seems to be working fine. After work I'm going to retry the ruu via the exe this time
Edit: Now it seems that my motion launch, auto-rotate, and proximity sensors aren't working so the only way I can use it at work is to plug/unplug the usb to turn the screen on.
Click to expand...
Click to collapse
From the looks of your screen shot you ended up there because certain partitions failed to flash. That' the protect mode your phone will go into in the case of even a partial failure on flash. You need to reflash the entire RUU again and not "force" it past that screen. INVALID DSP info is NOT A good thing to see.
Personally I would flash the RUU in fastboot RUU mode using the htc_fastboot I have posted.....
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
From the looks of your screen shot you ended up there because certain partitions failed to flash. That' the protect mode your phone will go into in the case of even a partial failure on flash. You need to reflash the entire RUU again and not "force" it past that screen. INVALID DSP info is NOT A good thing to see.
Personally I would flash the RUU in fastboot RUU mode using the htc_fastboot I have posted.....
Click to expand...
Click to collapse
Finally had some time to sit down and try this. Basically not sure what to do because the phone always reboots before the flashing process is done for the 0P6BIMG.zip sd and ruu mode methods. Same with just entering hboot, sits for 7 seconds max then reboots
KeltischDeutscher said:
Finally had some time to sit down and try this. Basically not sure what to do because the phone always reboots before the flashing process is done for the 0P6BIMG.zip sd and ruu mode methods. Same with just entering hboot, sits for 7 seconds max then reboots
Click to expand...
Click to collapse
See if you are able to get the hboot.zip to flash (you will probably have to be quick on commands).
dottat said:
See if you are able to get the hboot.zip to flash (you will probably have to be quick on commands).
Click to expand...
Click to collapse
Yeah, whenever I try to enter fastboot now (Fastboot oem rebootRUU ), the command window just hangs on < waiting for device > and the phone restarts. Fastboot devices does list my phone
KeltischDeutscher said:
Yeah, whenever I try to enter fastboot now (Fastboot oem rebootRUU ), the command window just hangs on < waiting for device > and the phone restarts. Fastboot devices does list my phone
Click to expand...
Click to collapse
try renaming the zip to 0P6BIMG.zip and putting on your ext SD. See if bootloader is able to flash that.
dottat said:
try renaming the zip to 0P6BIMG.zip and putting on your ext SD. See if bootloader is able to flash that.
Click to expand...
Click to collapse
Says it succeeded, gives me the power button to reboot option, and reboots itself before i hit power. Still at the same situation
KeltischDeutscher said:
Says it succeeded, gives me the power button to reboot option, and reboots itself before i hit power. Still at the same situation
Click to expand...
Click to collapse
Hmm... try now this one in bootloader (renamed and placed on your ext-sd)
https://www.androidfilehost.com/?fid=95916177934540511
dottat said:
Hmm... try now this one in bootloader (renamed and placed on your ext-sd)
https://www.androidfilehost.com/?fid=95916177934540511
Click to expand...
Click to collapse
Yeah, right after it begins the process after I hit the volume up button, it restarts while updating splash 1
KeltischDeutscher said:
Yeah, right after it begins the process after I hit the volume up button, it restarts while updating splash 1
Click to expand...
Click to collapse
Did it immediately restart to bootloader or attempt to boot to os?
dottat said:
Did it immediately restart to bootloader or attempt to boot to os?
Click to expand...
Click to collapse
os
Edit: Also - just for an extra description of the situation - when I got to work after trying to reflash this afternoon, I noticed my power button started working again. Data/wifi still work fine, but music (cant play anything), motion launch, auto screen rotation, audio or video (youtube, websites, gallery, etc) are still not functional and occasionally the entire ui will disappear and freeze for a few seconds.
Haven't been able to flash any fixes. After using my m8 more, I've also seen that the calls and anything voice related are also down and the phone freezes up quite a bit, plenty of FC's.
KeltischDeutscher said:
Haven't been able to flash any fixes. After using my m8 more, I've also seen that the calls and anything voice related are also down and the phone freezes up quite a bit, plenty of FC's.
Click to expand...
Click to collapse
Install teamviewer and pm me the id and passcode. Make sure you have stuff backed up off your internal sd card first. We will get this straightened out.
dottat said:
Install teamviewer and pm me the id and passcode. Make sure you have stuff backed up off your internal sd card first. We will get this straightened out.
Click to expand...
Click to collapse
So I finally had time and installed team viewer today and when I booted to start backing up everything, the phone didnt automatically restart itself in hboot this time (over the past couple days I've been having barely any FC's or hang ups) so I tried the ruu you posted again and it finished. First time, it hung on the Verizon logo after boot, I ruu'd again and it fully booted, when the android app optimizing was finished, it gave me the acore force close, did a factory reset and everything (autorotation, music, power button, etc) is back to Verizon stock and working with no force closes/problems so far. Thanks for your files/help, dottat :good: