I have a UK Xoom, which I seem to have screwed up a bit.... I unlocked it and flashed the EOS ICS thing on it and it was running not great, so I reflashed it to the stock 3.0, but I put the wrong one on (without the 3g bit on... doh!!), reflashed again to the right one (which worked fine BTW). Anyhoo, its updated to ICS OTA and it was running fine, till a few days ago when it would just randomly crash, so I decided to try to start again from scratch.
Before all of this, I did try to factory reset the thing but all I get is an android guy lying on its back with an exclamation mark on a red triangle
After that, the first thing I did was download the Android SDK, Motorola drivers and the image files. Then I unlocked the Xoom with the fastboot oem unlock. It goes through the motions... are you sure blah blah, and I select yes, and yes again. It then reboots. So I put it back in fastboot support, try to flash it and on the screen of the Xoom it says "Device still locked". OK. Fastboot oem unlock, blah blah, yes, yes reset. Back into fastboot, try to unlock it and still the same. Then I tried locking it, unlocking it again and its still the same.
I have no idea why its not doing anything... can anyone shine some light on this??
Related
My phone keeps resetting all the time so I can't sync to PC using Active Sync.
I can however start bootloader.
Is there any way to flash HARD SPL via flash card?
(my phone hasn't flashed yet to hard spl or any other rom unsupported by HTC)
Tried to flash phone using official rom update from bootloader.
Updated succesfully unfortunately same restarts after update.
Also tried to flash HARD SPL from bootloader and it detects phone, even starts flashing and stops on 0% then shows connection error. After this restarts as before.
If your phone is messed up and it's never been flashed/hacked, the best thing is to return it for warranty/repair (although it may be too late for that).
You can't flash hard spl from the sd card, so don't bother trying. You may just brick the phone doing it. Read the hard spl thread for instructions and tips on flashing. Make sure that you flash the proper hard spl (and roms/radios) for your device. Its sounds like you may have flashed the wrong firmware, although you haven't really told us what you've done. Constant re-booting is pretty typical when cdma is flashed to gsm, or vice versa. If you flashed the wrong bootloader, then you might as well throw the phone away.
Actually I DIDN'T flashed anything before it happened. At least I didn't.
I bought phone one week ago on auction. Phone worked smoothly. There was a problem with photo camera taking negative like photos. It wasn't important for me so I didn't even tried to flash new rom. That's all. Phone worked fine until todays morning. I woke up hearing reapeated welcome sound over and over. So I just removed battery to turn phone off. During the day tried to update official rom (from htc site) succesfully. But it didn't changed anything.
Try hard resetting the phone. Also, try removing the sim and sd cards. If it continues to re-boot, you may be in trouble. It could already have hard spl on it, so put it in bootloader and see if it's there or not.
Well, now I'm sure I'm in trouble.
In bootloader mode screen doesn't show "1.90.OliNex". I assume, there's no HardSPL.
Hard reset is not possible since I can't start windows mobile. It stops in phase: "Preparing your device for first use...".
It started working unexpectedly!
I've just tried to flash one of original roms available and after rejection, phone restarted and logged to windows succesfully.
Of course I've flashed HARD SPL and now everthing is working fine.
Unfortunately, after a week phone gone into "loop of restarts" again.
Yeah, i finally made it. I bought a TMO-DE One S (With S4 Processor) 5 Days ago, unlocked the Bootloader (HBoot 1.09), rooted and SuperCID´d it, installed CWM Touch and installed TrickDriod V8.0 incl. its Tweak Package. After that i installed another Radio and everything was fine. It could have been SO easy, but i just HAD to do more, and now its soft-bricked.
At all TrickDroid is a really good ROM, but i hated the thingy that it shows G symbol instead of H when getting HSPA speeds. So i decided to dump it and go for a 4.0.4 / Sense 4.1 Stock Rom without branding instead until a JB / Sense Rom comes out. And thats were the trouble started. i flashed the stock rom with CWM, installed the boot.img that came shipped with it and booted it up. I did a full wipe before flashing. It booted up, Sense Stock Background Image came on and it showed "Unfortunately Wiper App is closed" at the "Preparing phone storage" stage. After OK´ing that another Screen came up about some system service wouldnt respond (dont know the exact Text anymore) wich i could close or wait for it. No matter what i do, or if i do nothing, after ~20 seconds the phone crashes and restarts. After the first restart the phone only boots into a black screen but with the Android bar at the top is working with time, battery-charging and a warning smybol. But the Phone wont react to anything i do except for lockscreen button. When its "online" i can push files via adb to the internal SDCard so i thought it wouldnt be a big problem. i pushed ONE MaximuS V2.5 ROM to the SD Card, booted into CWM and installed it. then flashed the boot.img of it via fastboot and booted it up. but nothing happens. still black screen with bar on top and not reacting phone that reboots every 20 seconds. i allready tried full wipe, cache wipe, dalvik cache wipe and i dont really know what to do now.
A broken SD Partion cant be since i can push files via ADB to it and install them with CWM. But whatever i try to install every ROM boots only in this blackscreen. its clearly not hanging in bootloader, but in android itself. I dont really know what to do, and returning to my dealer is no option since Rooting, SuperCID´ing and flashing another ROM. You maybe have a Idea what to do now?
Peace
TK
PS: Sorry for my bad english, hope you can understand it
Edit: Okey, i got something. i formatted everything i could in CWM, and now (as its now supposed) it hangs in bootloader since no system is there for booting. The good thing is in CWM i get ADB Connection so i can still push files to the SDCard. Im now trying installing a ROM again. So at least i have a starting Point if it fails again
Edit 2: Okey, found it. The "Stock" ROM is broken, not my Phones Fault. and MaximuS just doesnt install right so nothing was changed. Installed TrickDroid again for testing and everything is fine again. Close this one...
I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP
I tried to update my XYboard 10.1 yesterday that I bought used with an OTA update. I am guessing it was the 4.1 update because it was on ICS prior to the update. It failed during the update, and it loaded into the "dual core" screen, then went black with the backlight on and didn't boot.
I tried a one click method to reflash Honeycomb back to the device, but no matter what I do, it won't finish flashing. I tried redownloading the files, and no change. The first time it froze flashing "bootloader", I tried a few more times and it didn't work. So I downloaded a different set of fastboot files and tried to flash them, and now it's stuck flashing "radio". I have let it sit for a half hour and it won't flash past that.
I am not sure how messed up this tablet is but I am stuck, can anyone help me get ANY operating system on this thing so it is at least useable? it is not rooted, I can flash to it but everything I have tried fails. Tried factory reset and cleared cache through recovery and that didn't work, and now I can't even access recovery. Right now all I can access is fastboot flash mode.
I bought this for my girlfriend and I am giving it to her tomorrow and I can't get this freaking thing to work.
Yesterday a strange thing occured to me. My phone got bricked but a simple battery re-plug was enough to fix it. Here's what's happened:
For about 2 weeks it had been telling me that there's new update available (4.4.3., I think), but I've downloaded and installed several times. After every reboot (after downloading and installing update) the notification about it popped up again. So the last time I did it, I plugged in the cable during the update (even though the power was at 82%) and when I came back, the phone was bricked. I could only start it if it was powered by a cable and after the "Google with the padlock at the bottom" screen it went dark again. Same thing with Recovery boot. I thought I would need to factory reset, but then I tried pulling the battery out and plugging it back in and the device is fine.
I have a rooted 32GB, bootloader version HHZ11k. Any idea what might have caused this issue and how to avoid it in the future?
Intresting. A lot of people's phone got bricked and behaving similar. Like bootloader gets locked after unlocik. Emmc acts like it is write protected or something. Maybe a simple battery replug could solve this issue?
Tapatalk-kal küldve az én Nexus 5-el
dexvility said:
Yesterday a strange thing occured to me. My phone got bricked but a simple battery re-plug was enough to fix it. Here's what's happened:
For about 2 weeks it had been telling me that there's new update available (4.4.3., I think), but I've downloaded and installed several times. After every reboot (after downloading and installing update) the notification about it popped up again. So the last time I did it, I plugged in the cable during the update (even though the power was at 82%) and when I came back, the phone was bricked. I could only start it if it was powered by a cable and after the "Google with the padlock at the bottom" screen it went dark again. Same thing with Recovery boot. I thought I would need to factory reset, but then I tried pulling the battery out and plugging it back in and the device is fine.
I have a rooted 32GB, bootloader version HHZ11k. Any idea what might have caused this issue and how to avoid it in the future?
Click to expand...
Click to collapse
No such thing as "temporary brick" or "soft-brick". Those terms are ridiculous. If your phone were to be bricked, it would not turn on, would not boot into recovery, would not boot into bootloader, and would not boot into the secondary bootloader. Your device would be completely dead.
Since you're rooted you can't take the OTA normally, you have to flash the OTA.zip in recovery manually. Which is why it tells you that there's a new update, because you never successfully updated in the first place.
I suggest you read these:
http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217