[Q] Hung Galaxy Nexus - General Questions and Answers

Galaxy Nexus Rooted running Jelly Bean 4.2 (bigxie_magurTA_JOP40C_odexed-signed) received a Google? up date notice for 4.2 like an idiot thought it was 4.21 and started it. Phone now hung. after a lot of messing about I am stuck at Google Screen. When Connected to PC, Device manager shows it under Portable Devices as Samsung Mobile MPT Device.
When I boot into bootloader it shows as Android Phone, Android ADB Interface. When I go into Recovery (ClockworldMod Recovery V 6.0.1.0) it shows as Android Phone, Samsung Android ADB Interface I've done all I can think of Wiped every hoping to get somewhere or back to stock or something.
I cant get anything on the phone. Everything I have tried is either waiting for device or cant find device
I did read that from recovery holding power key and pressing up key will reset it but that dosnt work in ClockworldMod
When I installed 4.2 I removed the Zip so I couldn't install that and now As I have wiped the phone There is nothing to Install
I have pulled the battery and sim card held power key down. left the phone on Google screen overnight
1 Can I get rid off ClockworldMod
2 How do I get into the phone to flash a ROM?
Any help would be very welcome
PC running Win 8
Thanks

fixed
solved problem with nexus root toolkit 1.6.1

Related

[Q] Nexus s 4g major problems

I have the nexus s 4g flashed to boost mobile. it has ran great for over a year now. i have flashed many roms and kernals to it and it has worked like a charm with only the occational hickup. but a few weeks ago when i would power it down and change may battery it would start to get stuck on the google screen. i could pull the battery a few times and it would eventually take off and work fine for a few day and then do it again. this last time it done it i cant get it to go past the google screen for nothing. i can get into the fast boot mode and also into clockworkmod touch recovery but when i go into flash zip from sd it say error loading sd, when i plug it into my computer it conects when in fastboot but i cannot access my sd memory at all. i tried the pdanet but it wont work due to no access to the sd. i downloaded the program wugs nexus tool kit and tried to flash stock and unroot with option bootloop / soft-brick in my boot loader. the program seems like it is working, it takes control of my phone restarts bootloader a few times then says restarting your now stock phone, but my phone just sits in bootloader. i have tried to manually reboot system and it just goes to the google screen and stops. when i power on my phone the google logo comes up, flashes away for a split second then pops back up with the leds at the bottom of my phone on this time but thats all i can get. please help i dont know what to try next. let me know if any of you have had this problem before and what you did to get it fixed. Please help i miss my Nexus...
** UPDATE *** Well i havnt really given up on my Nexus but i gave in and bought a new Galaxy S II so i could have a working smart phone again. Ill still be working on the Nexus in my spare time so ill update if i have any luck.
Sent from my SPH-D710 Galaxy S II running Crossbones JB ROM with matrix using xda app-developers app

Stuck in a boot loop (CM 10.1 loading screen) and cant access Bootloader

Hey guys, I guess i've run into some deep sh**. I was trying to update the firmware version to the 3.33 one and all was going fine until the phone reboot. It now is stuck on the CM 10.1 boot logo and wont load the rom. I previously had the CM 10.1 installed and working fine, but my phones service sucked. In an attempt to install the new firmware with the radio to see if my signal would be fixed, i think i have messed up the phone.
I tired to access the bootloader by holding the vol down + power throughout the htc load screen, but it keeps continuing to the CM logo (i couldn't access the bootloader this way even when the phone was working normally, i had to hold the power button and reboot into bootloader).
Before doing the PG58IMG.zip update i took some screenshots:
I had the 1.27.11 H-Boot and 4EXT recovery installed.
Any help is appreciated guys, i am seriously pulling my hair out trying to fix this problem.
**********************************************************************************************************************************************
Edit: I got it working after a ****storm
I reinstalled drivers following this : http://forum.xda-developers.com/showthread.php?t=1152148
i launched cmd and set the correct directory for the tools section. i typed "adb devices"
It listed available device:
C:\adt\sdk\tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH18********* recovery
The device is recognized by the computer (my phone is off the whole time, but plugged into the computer)
next type "adb reboot recovery" , your device should power on and boot to the default recovery
Next, I wiped cache + davilk , then rebooted normally. The phone wen past the CM logo and began optimizing apps, then went back to the regular homescreen. I thought i permanently bricked the device, but I got it working. Hopefully this helps someone out there who will struggle with the same issue.

[Q] Flashed stock ROM with flashify (rooted phone), unable to get past recovery

Good evening ,
Yesterday I did a very stupid thing, I was trying to update my phone to 5.0 Lollipop, I found a way to do it with flashify but instead of taking the custom rom image I chose the stock rom downloaded from ASUS website, since then the phone won't go past the ASUS logo, I can only get into recovery mode, can't get into fastboot. I tried deleting the cache and then factory reset, to no avail, phone turns on, ASUS logo appears and then the screen goes black, then blank and that forever.
I tried to user fastboot with the phone plugged in recovery mode, ADB recognizes it, device manager sees it (both Android ADB and USB Composite Device), no exclamation mark, latest drivers installed, both from Intel and Google but it doesn't show up when running the cmd fastboot devices, nothing worked, I don't what else to do, hope someone can help me.
Asus Padfone Infinity Lite, 32GB TW version, can't remember the number though
Thanks for reading!!

Kyocera Brigadier not booting.

Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?

Recovery mode, gone. OS, dead.

I have an old glaxaxy ace which i decided to root and i kind of failed. By failed, i mean that when i attempt to boot up the phone with the power button, the screen gradually goes from the samsung logo to white- white bars appear and slowly fill the screen going up to full brightness. I fiddled around a bit, trying to install the stock os that came with the phone (i think it was jelly bean 4.12), and i managed to delete recovery mode. No idea how, but it simply shows the samsung logo and then turns off when i try to get into it. I have never rooted or flashed which is why i was trying on this old galaxy ace (that is like £50 nowadays).
Anyway, how can i recover recovery mode -lol-. My laptop doesn't recognise it (before it recognised it as an external storage device) and i don't renember what the model is.
Wiryfuture said:
I have an old glaxaxy ace which i decided to root and i kind of failed.
Click to expand...
Click to collapse
Which Galaxy Ace, is it? And more details on the phone if you can

Categories

Resources