So my M8 GPE is S-Offed, bootloader unlocked, and rooted. The new 4.4.3 update came out today, and I wanted to upgrade to that. I downloaded the OTA on my device from one of the threads for the GPE OTA here, and when I went in CWM to flash it, it said something about the build.prop being unable to verify/find.
I read somewhere (I think on Android Central) that someone else was trying to do a very similar thing (with a different phone though). Their build.prop was edited, and it needed to be stock to accept the update. Some people advised him to just get the stock build.prop, put it in the folder, and make a backup of the one he had for it to update (and then he could put the other back).
After reading that, I went to the thread on here with the M8 GPE dumps, downloaded the one for 4.4.2, and extracted the build.prop and did what I explained above.
After that, I went to the recovery, and tried to flash the OTA. Still didn't work, and had the same error. I went to reboot, and after pressing that the screen went black. I wasn't able to get to the splash screen after that, just the screen that says Google with the unlocked padlock at the bottom.
I can't get anything now, and would really like to fix this ASAP. It's not my main phone (my main number is in my iPhone), so it's not as bad as it could have been, but it's really annoying.
I'm starting to think that maybe build.props are device specific? It really didn't make sense that it didn't work the first time, because there were plenty of articles saying that rooted Nexus 5s with custom recoveries could just flash OTAs like I initially tried to (because the GPE phones are so similar, and there's nothing out there about the M8 GPE, I figured everything should be similar).
Anyone have any ideas? I realized I was probably a little quick to go messing around, but I really didn't think installing an OTA could cause this much trouble
Thanks!
To be more clear:
The only thing I can get is this. And that's by holding power+volume up or power+volume up and down for 10 seconds. Nothing happens when I hold power+down or just power (even for a minute):
{
"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"
}
Sent from my iPhone 5s using Tapatalk
Can you get in to recovery or in the bootloader? Sorry can't see your picture seems broken
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hawkysoft said:
Can you get in to recovery or in the bootloader? Sorry can't see your picture seems broken
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1
Why the heck will you edit build.prop when it was not modified.
Time to flash custom recovery and restore a GPE nandroid
Don't lock the bootloader in any case
---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------
Need stock recovery to flash ota on most phones
Hawkysoft said:
Can you get in to recovery or in the bootloader? Sorry can't see your picture seems broken
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It says Google with an unlocked padlock on the bottom. The background is totally black. No combination of buttons can get me anywhere else.
Sent from my iPhone 5s using Tapatalk
SaHiLzZ said:
+1
Why the heck will you edit build.prop when it was not modified.
Time to flash custom recovery and restore a GPE nandroid
Don't lock the bootloader in any case
---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------
Need stock recovery to flash ota on most phones
Click to expand...
Click to collapse
I wasn't sure if it was edited by S-Off, AdAway, or rooting.
I now remember reading somewhere that if you reflagged stock recovery and did the update that would work... Now I understand why I have the stock recovery on my PC
I totally forgot about that while I was doing this. I didn't remember until now for some reason. If power+down doesn't do anything, what can I do?
Sent from my iPhone 5s using Tapatalk
SolarTrans said:
I wasn't sure if it was edited by S-Off, AdAway, or rooting.
I now remember reading somewhere that if you reflagged stock recovery and did the update that would work... Now I understand why I have the stock recovery on my PC
I totally forgot about that while I was doing this. I didn't remember until now for some reason. If power+down doesn't do anything, what can I do?
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Can you at the very least pick up the phone when connecting to a PC? If so you could send command from there to boot into bootloader and work from there?
SolarTrans said:
I wasn't sure if it was edited by S-Off, AdAway, or rooting.
I now remember reading somewhere that if you reflagged stock recovery and did the update that would work... Now I understand why I have the stock recovery on my PC
I totally forgot about that while I was doing this. I didn't remember until now for some reason. If power+down doesn't do anything, what can I do?
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
It will HAVE to work.
Press and hold Volume Down + Power.. and it will get you in bootloader mode.
BerndM14 said:
Can you at the very least pick up the phone when connecting to a PC? If so you could send command from there to boot into bootloader and work from there?
Click to expand...
Click to collapse
No nothing... When the Google logo shows up, it shows up as a DVD drive with no disk in it until the logo disappears a couple seconds later.
Sent from my iPhone 5s using Tapatalk
SaHiLzZ said:
It will HAVE to work.
Press and hold Volume Down + Power.. and it will get you in bootloader mode.
Click to expand...
Click to collapse
I just did that for 5 minutes straight. Nothing happened D:
Sent from my iPhone 5s using Tapatalk
SolarTrans said:
No nothing... When the Google logo shows up, it shows up as a DVD drive with no disk in it until the logo disappears a couple seconds later.
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Odd then, when the phone usually boots while connected to PC it already gets picked up by the PC, though it won't load most things for sure. When I tried to install an app and it wanted to reboot it got hung up on the splash screen too, none of the hardware buttons worked(Like you're experiencing now, though I know your problem is more than just an app). When I plugged it into PC it gave the notification sound on PC that it was loading drivers, I just opened the command prompt, adb devices and it showed the device connected, could reboot into bootloader form there.
BerndM14 said:
Odd then, when the phone usually boots while connected to PC it already gets picked up by the PC, though it won't load most things for sure. When I tried to install an app and it wanted to reboot it got hung up on the splash screen too, none of the hardware buttons worked(Like you're experiencing now, though I know your problem is more than just an app). When I plugged it into PC it gave the notification sound on PC that it was loading drivers, I just opened the command prompt, adb devices and it showed the device connected, could reboot into bootloader form there.
Click to expand...
Click to collapse
See it isn't doing that on the PC though. I have the drivers, but it doesn't notice it while it's off
Sent from my iPhone 5s using Tapatalk
SolarTrans said:
See it isn't doing that on the PC though. I have the drivers, but it doesn't notice it while it's off
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Of course.
I mean though, the necessary drivers already load up as soon as the phone starts up, hence why you can use command prompt in fastboot mode even though the phone itself didn't fully start up, but if adb doesn't pick up your phone then I guess it won't be much help then to get you into fastboot mode or even send a command to reboot the device into fastboot.
So no hardware and software method to do this
BerndM14 said:
Of course.
I mean though, the necessary drivers already load up as soon as the phone starts up, hence why you can use command prompt in fastboot mode even though the phone itself didn't fully start up, but if adb doesn't pick up your phone then I guess it won't be much help then to get you into fastboot mode or even send a command to reboot the device into fastboot.
So no hardware and software method to do this
Click to expand...
Click to collapse
Yeah... You can see the unlocked padlock on the bottom when you can get it to show something, so I'm afraid to send it to Google.
I've looked around on the internet, and I haven't seen anyone who's been unable to boot anything because they changed the .prop...
If there's some way to maybe drain the battery completely so they can't even turn it on a little bit, that may help
What about holding the power button for a minute?
SaHiLzZ said:
What about holding the power button for a minute?
Click to expand...
Click to collapse
Don't think it'll work. I had it happen to me as well, like I said in my one post up there. Tried to install the Root Companion for GSAM Battery Monitor, it wanted a reboot to complete, pushed the button to do reboot and it got hung up right after device turned "off" to reboot, it didn't even show HTC logo or nothing. Tried pushing button combinations, holding power in etc it didn't do anything, none of the hardware reboot methods worked.
Plugged in USB cable and hooked it up to computer, opened my command prompt in adb folder and checked to see if it picked up the device. It did and I rebooted the device from the command prompt, no problem. So I don't know the hardware combinations hardly ever works, but what I find odd is that the 'software' (Through command prompt) doesn't work either. He said that it picks up the device as DVD drive with no disk, so surely the computer picked it up, so adb should as well Strange that it doesn't, I would have thought it could pick up the device as soon as it gets powered on, hence why we can just connect it in fastboot when we boot directly into it(Hardware method). Does it load seperate drivers(For PC) for a fastboot boot and a normal one?
Oh well... Use it for BBQ fire, buy a new one
I checked adb devices, and nothing showed up... Damn shame. How about this? Break screen>send to HTC advantage>get free replacement?
Sent from my iPhone 5s using Tapatalk
To reboot the phone you have to hold volume UP and power for about 20 seconds. Do this and as soon as the Google logo goes away hold volume DOWN only. It should then boot into the boot loader and you can then carry on from there...don't connect it to your PC until you're in the bootloader
Update: so for whatever reason, the phone was draining battery the entire time while it was "off" now, after totally draining the battery, I'm able to get it to show it's charging and access recovery mode.
Can I manually change by prop file from there, or should I just restore the OS?
Sent from my iPhone 5s using Tapatalk
Related
Hello fellow Android-Users,
I'm having a problem with my rooted HOX. I've been using the IceColdJelly-Rom for a few days and after using PimpMyRom this morning, my HOX is stuck at the white HTC Splash Screen. I guess i must have choosen some settings, that don't work with my HOX. My first guess is that it is something about the CPU-Kernel or anything related since i checked some options regarding it?
Unfortunatly i cant even boot into recovery. I tried using adb-tools but "adb devices" shows no devices even through windows is beeping when i plug the usb-cable in.
I'm a little desperate because all the threads i have seen mention that they still could boot into recovery.
I can hard-reboot it holding the Power-Button until the buttons are flashing, but holding volume-Down does'nt do anything while rebooting.
Thanks to the unremoveable Battery, I cant even turn it off. It always reboots.
Any suggestions?
sanguis89 said:
Hello fellow Android-Users,
I'm having a problem with my rooted HOX. I've been using the IceColdJelly-Rom for a few days and after using PimpMyRom this morning, my HOX is stuck at the white HTC Splash Screen. I guess i must have choosen some settings, that don't work with my HOX. My first guess is that it is something about the CPU-Kernel or anything related since i checked some options regarding it?
Unfortunatly i cant even boot into recovery. I tried using adb-tools but "adb devices" shows no devices even through windows is beeping when i plug the usb-cable in.
I'm a little desperate because all the threads i have seen mention that they still could boot into recovery.
I can hard-reboot it holding the Power-Button until the buttons are flashing, but holding volume-Down does'nt do anything while rebooting.
Thanks to the unremoveable Battery, I cant even turn it off. It always reboots.
Any suggestions?
Click to expand...
Click to collapse
Download Recovery
adb devices doesn't show any device cause you are not fully booted, you neeed to reflash the recovery by typing:
Code:
fastboot flash reocvery path/to/recovery.img
then you should be able to boot to recovery and flash a new rom...
Thank you very much for the answer!
using the fastboot commands results in "waiting for device". I checked google and people said that the HTC Drivers must be installed, so I reinstalled the HTC Sync Suite and rebooted Windows and the HOX. I am still getting "Wating for device"...
Edit: I will try to install the android SDK to see if thats the problem.
Edit2: Ok, I've read some discussions and followed there instructions but sofar nothing worked.
I have installed the Android SDK with the Tools and Platform-Tools, installed HTC Drivers and tried using the original Laptop where i unlocked the bootloader. Nothing worked.
The Phone is listed in the Device Manager of Windows in several Categorys such as a harddrive disc, a cd disc drive and as the mobile device "E:\".
I am running out of ideas what might be the problem...
Have you tried "fastboot erase cache" without the commas and then see if you can get into recovery
sent from my One X using xda venom premium
bogfather said:
Have you tried "fastboot erase cache" without the commas and then see if you can get into recovery
sent from my One X using xda venom premium
Click to expand...
Click to collapse
Thanks for the tip, but this also results in "waiting for device"
sanguis89 said:
Thanks for the tip, but this also results in "waiting for device"
Click to expand...
Click to collapse
Stupid question but is your Phone in fsstboot mode?
Sent from my HTC One X using xda app-developers app
matt95 said:
Stupid question but is your Phone in fsstboot mode?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I can't get pass the white HTC Splash Screen. Holding Volume-Down while turning the phone on makes nothing. Tried this several times. The Phone just makes the starting sound and regulates the Screenbrightness.
sanguis89 said:
I can't get pass the white HTC Splash Screen. Holding Volume-Down while turning the phone on makes nothing. Tried this several times. The Phone just makes the starting sound and regulates the Screenbrightness.
Click to expand...
Click to collapse
That's why it says <waiting for device>... So you're not able to access to bootloader? This is almost impossible... Keep Pressed power+vol down
Sent from my HTC One X using xda app-developers app
matt95 said:
That's why it says <waiting for device>... So you're not able to access to bootloader? This is almost impossible... Keep Pressed power+vol down
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
After turning my phone literally 40 Times on and off trying to get into the Bootloader there is only on thing left to say: Thank you, sir.:laugh:
I then followed your previous instructions and was able to flash a new boot.img and reinstall another rom.
I was already accepting the fact that my beloved HOX would only be a expensive candle til the power runs out :silly:
I am going to dedicate a beer to you later.
Really appreciating the help. Thanks!
sanguis89 said:
After turning my phone literally 40 Times on and off trying to get into the Bootloader there is only on thing left to say: Thank you, sir.:laugh:
I then followed your previous instructions and was able to flash a new boot.img and reinstall another rom.
I was already accepting the fact that my beloved HOX would only be a expensive candle til the power runs out :silly:
I am going to dedicate a beer to you later.
Really appreciating the help. Thanks!
Click to expand...
Click to collapse
No need to buy me a beer I'm here to help and I'm glad to hear that I've succeeded in it
Hi everyone,
I bought my HTC One X today and was told to install Cyanogen Mod 10 on it to get the best out of it. I have followed a couple of guides but i have completely screwed this up!! After following the instructions (well thought i did anyway) i have gotten to the point where my phone is stuck in the boot loop (spinning circle thing).
I have tried following guides everywhere but i'm getting completely lost and getting more and more frustrated because i dont understand anything that is being explained.
So is there any way of getting my phone back to normal or some form of working condition because i would hate to have broken something i just bought within 7 hours of having it
Any help is much appreciated.
FXhnd77 said:
Hi everyone,
I bought my HTC One X today and was told to install Cyanogen Mod 10 on it to get the best out of it. I have followed a couple of guides but i have completely screwed this up!! After following the instructions (well thought i did anyway) i have gotten to the point where my phone is stuck in the boot loop (spinning circle thing).
I have tried following guides everywhere but i'm getting completely lost and getting more and more frustrated because i dont understand anything that is being explained.
So is there any way of getting my phone back to normal or some form of working condition because i would hate to have broken something i just bought within 7 hours of having it
Any help is much appreciated.
Click to expand...
Click to collapse
I guess you dint flash the boot.img..When you open the CM 10 zip file you will find the boot.img there...just extract it to a known location and flash the boot.img file and then install the rom as you did b4...that will solve the problem
Dont worry, nothing bad has happened to your phone and its just a extra step to be followed till v get s-off
:good:
kskendsup said:
I guess you dint flash the boot.img..When you open the CM 10 zip file you will find the boot.img there...just extract it to a known location and flash the boot.img file and then install the rom as you did b4...that will solve the problem
Dont worry, nothing bad has happened to your phone and its just a extra step to be followed till v get s-off
:good:
Click to expand...
Click to collapse
Do this 1st fast boot erase cache then flash the boot.IMG
Sent from my Xoom using xda app-developers app
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
Just thought I'd share this what I copied from a good source what helped me when I started flashing my hox but I use Linux so I don't have a clue about any window issues
.) Open the .zip file and copy 'boot.img' to your fastboot folder. Or the folder you use
.) Turn off your phone and enter the bootloader (Hold the Volume Down and Power Keys while off).
) Select 'Fastboot' by pushing the Power Key.
.) Plug your phone into your computer using a USB cable.
.)Now go to your computer and open a command window inside the fastboot folder (Hold SHIFT + Right Click on any white-space).
.) Type 'fastboot devices.'
) Type 'fastboot erase cache' and push enter. This can fix problems with bootloops or bootfailures.
.) Type 'fastboot flash boot boot.img' and push enter. It should say 'OKAY' if successful.
.) On your phone, select 'HBOOT' using the Power Key and scroll down to 'Recovery' using the Volume Down Key. Push to Power Key again to select it.
Once in recovery you can navigate by tapping the screen or by using the Power and Volume Up/Down Keys.
.) Select 'wipe data/factory reset' and accept the warning screen.
) Now select 'advanced' and select 'wipe dalvik cache.'
) Select 'mounts and storage' and then 'mount USB storage.'
.) Copy the .zip file you downloaded (Don't unzip it!) onto the SD card of your phone.
.) Unmount USB Storage on your phone and navigate back to the Recovery Homescreen.
.) Now select 'install zip from sdcard' followed by 'choose zip from sdcard.'
.) Select the .zip file and let it install.
Sent from my Xoom using xda app-developers app
I actually love the both of you!!! My phone is working again
REALLY appreciate it! :laugh:
Thank you
Stuck in CM Boot Loop - please help!!
Hi guys,
I too am a bit of a noob in this. I had similar problems and then followed the instructions listed above. I saved the following files to my SD Card:
cm-10.2.0-RC1-endeavoru.zip
gapps-jb-20130813-signed.zip
First time round, after I rebooted the device, I managed to get through and set up my WiFi, log into my Google Account, but just as my Google account was registering and beginning to restore my apps, my phones screen suddenly reverted to the boot loop (spinning circle thing). Furthermore, the LED indicator is now steadily flashing in Red!
I am completely stuck here and any assistance this forum can provide will be much appreciated.
Thanks in advance!
someshj1577 said:
Hi guys,
I too am a bit of a noob in this. I had similar problems and then followed the instructions listed above. I saved the following files to my SD Card:
cm-10.2.0-RC1-endeavoru.zip
gapps-jb-20130813-signed.zip
First time round, after I rebooted the device, I managed to get through and set up my WiFi, log into my Google Account, but just as my Google account was registering and beginning to restore my apps, my phones screen suddenly reverted to the boot loop (spinning circle thing). Furthermore, the LED indicator is now steadily flashing in Red!
I am completely stuck here and any assistance this forum can provide will be much appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Flash the boot.img!!!!
Thant said:
Flash the boot.img!!!!
Click to expand...
Click to collapse
Thanks Thant!
Just so you know, I first flashed the boot.img file (extracted it from the ROM package), then followed the steps in the post above.
This time round, the phone started up and I went through the initial set-up steps. Logged in to my Google account, everything seemed to work fine until I went to Play Store to check my apps. I briefly saw that my backed-up apps were downloading, then suddenly the phone went back to the CM boot screen (circular thing). That's how the phone has stayed.
What further do you guys advise?
Thanks.
someshj1577 said:
Thanks Thant!
Just so you know, I first flashed the boot.img file (extracted it from the ROM package), then followed the steps in the post above.
This time round, the phone started up and I went through the initial set-up steps. Logged in to my Google account, everything seemed to work fine until I went to Play Store to check my apps. I briefly saw that my backed-up apps were downloading, then suddenly the phone went back to the CM boot screen (circular thing). That's how the phone has stayed.
What further do you guys advise?
Thanks.
Click to expand...
Click to collapse
INSTRUCTIONS
First time installing CyanogenMod 10.2 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Unlock your device via http://www.htcdev.com
Flash the latest official ClockworkMod-Recovery via Fastboot
Copy GApps and CM10.2 ZIPs to your SDCard
Boot into Recovery
Flash CM10.2 zip from SDCard
Flash GApps zip from SDCard
Flash the boot.img included in the CM10.2 zip via Fastboot
DO A DATA WIPE / FACTORY RESET
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Thant said:
INSTRUCTIONS
First time installing CyanogenMod 10.2 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Unlock your device via http://www.htcdev.com
Flash the latest official ClockworkMod-Recovery via Fastboot
Copy GApps and CM10.2 ZIPs to your SDCard
Boot into Recovery
Flash CM10.2 zip from SDCard
Flash GApps zip from SDCard
Flash the boot.img included in the CM10.2 zip via Fastboot
DO A DATA WIPE / FACTORY RESET
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
Thanks again, Thant! Your help is much appreciated.
Got the phone working with CM10.2, I played around with it for about 5 minutes, but not it has become unresponsive again. Pressing the power button to unlock the phone doesn't wake the screen, only the three soft buttons at the bottom light up, then nothing. If I leave the phone alone for a few minutes, it will wake up. I have since tried restarting the phone and it is working for the moment. I will report back if the screen hangs again.
Thanks again for your help.
someshj1577 said:
Thanks again, Thant! Your help is much appreciated.
Got the phone working with CM10.2, I played around with it for about 5 minutes, but not it has become unresponsive again. Pressing the power button to unlock the phone doesn't wake the screen, only the three soft buttons at the bottom light up, then nothing. If I leave the phone alone for a few minutes, it will wake up. I have since tried restarting the phone and it is working for the moment. I will report back if the screen hangs again.
Thanks again for your help.
Click to expand...
Click to collapse
Please try something for me.Turn on the screen and do a pressure between the right down side on main camera and display and see if the display flickering or do something strange.
Thant said:
Please try something for me.Turn on the screen and do a pressure between the right down side on main camera and display and see if the display flickering or do something strange.
Click to expand...
Click to collapse
Nope. Nothing. Although, I have noticed that the screen is taking a long time to wake up. When I press the pwer button, the screen should wake immediately, on the lock screen, but it is taking up to 2-3 minutes to wake. I have just now also noticed that when moving between screens or pulling the notification and app drawer, the display gets garbled and pixelated and screen flickers. It then sorts itself out.
I will try and capture a video of it happening and post it back here, if it helps.
someshj1577 said:
Nope. Nothing. Although, I have noticed that the screen is taking a long time to wake up. When I press the pwer button, the screen should wake immediately, on the lock screen, but it is taking up to 2-3 minutes to wake. I have just now also noticed that when moving between screens or pulling the notification and app drawer, the display gets garbled and pixelated and screen flickers. It then sorts itself out.
I will try and capture a video of it happening and post it back here, if it helps.
Click to expand...
Click to collapse
It is something like this
Thant said:
It is something like this
Click to expand...
Click to collapse
Yes, that's exactly what's going on. Although, I've been working with the device for a few hours now and I haven't seen the pixelated screen, but I have seen a delay in the screen waking to the lock screen.
Hardware..
Sent from my HTC One X using xda app-developers app
someshj1577 said:
Yes, that's exactly what's going on. Although, I've been working with the device for a few hours now and I haven't seen the pixelated screen, but I have seen a delay in the screen waking to the lock screen.
Click to expand...
Click to collapse
You have Black Screen of Dead sorry my friend you must to change the mainboard on the phone if you have warranty go back to full stock(stock rom and stock recovery), RELOCK the bootloader and send it for repair and hope they will repair free of charge if no warranty changing the mainboard will cost you some monеy. And I am right if you turn on the screen and you do pressure in the my point in previous post you will see the flickering and all the thing in this video. Sorry again
{
"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"
}
imhotap said:
Hardware..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Right you are!
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
Thant said:
You have Black Screen of Dead sorry my friend you must to change the mainboard on the phone if you have warranty go back to full stock(stock rom and stock recovery), RELOCK the bootloader and send it for repair and hope they will repair free of charge if no warranty changing the mainboard will cost you some monеy. And I am right if you turn on the screen and you do pressure in the my point in previous post you will see the flickering and all the thing in this video. Sorry again
Click to expand...
Click to collapse
Thank for your help! Glad to know guys like you are around!!
My phone's out of warranty, I'm afraid. I will carry on using it until it completely dies on me!!
I have searched high and low for an answer to my problem for the past 5 hours. Haven't found a solution or guide on XDA or anywhere else that can help, so I am making this post as my last effort.
I bought an unlocked GSM Galaxy Nexus off of ebay knowing that it was stuck in a boot loop. I figured it could be fixed. I may be wrong.
I AM ON A MAC The pictures have Windows but I am running Parallels and it sucks.
--------
Ok, so here is my problem lies, when turning the device on normally I get this screen:
{
"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 get this for a few seconds, then it goes away, vibrates, and comes back ..... over and over.
I can get to both Odin mode and Fastboot:
This is no problem.
I even managed to get CWM on the phone and to come up:
My issue now is that I can't get ADB to work .. Wugs ToolKit won't work ... Galaxy Nexus ToolKit wont work ... nothing.
I can't be 100% sure that USB Debugging is enabled as I can't get past the Google Logo.
Is there anything that can be done to save this phone ... or is it a fancy paperweight?
I have an N4, I just bought this because the seller had no clue how to fix it, and it was a good deal. (not to mention I was planning to use it as a dev device for apps and such)
Thanks everyone!!!
Use the terminal on the Mac. I also have a Mac. Let me find u the files needed for adb and fast boot for macs.
Sent From My Miui Powered Galaxy Nexus
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
OK. This was the guide I used when I first got my nexus s 4g but I also used it for my galaxy nexus. Follow the instructions and make sure u use the correct files for your phone. forum.xda-developers.com/showthread.php?t=1129759
Sent From My Miui Powered Galaxy Nexus
Well crap .... after trying to use Fastboot (as ADB doesn't seem to want to recognize my device) I am stuck at the Google logo with the unlocked padlock.
I can still get in to CWM Recovery and Fastboot, but I am 100% lost on what to do now. I can not find a solution anywhere that works
clay_cauley said:
Well crap .... after trying to use Fastboot (as ADB doesn't seem to want to recognize my device) I am stuck at the Google logo with the unlocked padlock.
I can still get in to CWM Recovery and Fastboot, but I am 100% lost on what to do now. I can not find a solution anywhere that works
Click to expand...
Click to collapse
Did you try using anther pc? Maybe windows can manage this out.. I don't know what else to suggest..
Sent from my Galaxy Nexus
Jar3112 said:
Did you try using anther pc? Maybe windows can manage this out.. I don't know what else to suggest..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Unfortunately so ---- Windows XP and Windows 7 both ... I may try again tomorrow : /
Ok, so here is my status now ---
Flashed stock image using Odin. Said it was completed and successful. Gave a big "PASS" message.
Rebooted phone, and watched the Google logo bootloop for 30mins.
On the plus side, my phone is now getting recognized as an ADB Interface --- but only in Fastboot. When I enter Stock Recovery or CWM Recovery, I can no longer use adb.
1 step closer, or totally effed?
clay_cauley said:
Ok, so here is my status now ---
Flashed stock image using Odin. Said it was completed and successful. Gave a big "PASS" message.
Rebooted phone, and watched the Google logo bootloop for 30mins.
On the plus side, my phone is now getting recognized as an ADB Interface --- but only in Fastboot. When I enter Stock Recovery or CWM Recovery, I can no longer use adb.
1 step closer, or totally effed?
Click to expand...
Click to collapse
Flash the image, bootloader and radio and that should get you booted
Same Problem
jaymazz13 said:
Flash the image, bootloader and radio and that should get you booted
Click to expand...
Click to collapse
So I just had this happen to me over lunch, after an hour of trying to re-flash stock image, bootloader, and radios, i'm still getting the Google boot up screen. I too can get into flashboot, but I can not get into recovery... Suggestions?
Sorry, I know this threads a little old, but it was the same problem I am having, wasn't sure if anyone found a solution.
Thanks in advance...
marker2002 said:
So I just had this happen to me over lunch, after an hour of trying to re-flash stock image, bootloader, and radios, i'm still getting the Google boot up screen. I too can get into flashboot, but I can not get into recovery... Suggestions?
Sorry, I know this threads a little old, but it was the same problem I am having, wasn't sure if anyone found a solution.
Thanks in advance...
Click to expand...
Click to collapse
Does ur computer recognize ur device when u plug it in?
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Does ur computer recognize ur device when u plug it in?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it does, but only in fast boot.
Other things I found:
-My battery is full. When I plug it in it shows it's charging then shows me battery life, shows full.
-When I turn it on, it gets stuck at Google screen
-When I go into fastboot my computer recognizes it, but after flashing anything to it, it just continues to be stuck on the Google start-up screen
Update since I've written this post... when I plug it in, it wont go past the 'showing that it's charging screen" I have to wait till it shows battery status before I can go into fast boot, and now it wont even do that... neat. Headed home, then i'll swap batteries and try it all again.
marker2002 said:
Yes it does, but only in fast boot.
Other things I found:
-My battery is full. When I plug it in it shows it's charging then shows me battery life, shows full.
-When I turn it on, it gets stuck at Google screen
-When I go into fastboot my computer recognizes it, but after flashing anything to it, it just continues to be stuck on the Google start-up screen
Update since I've written this post... when I plug it in, it wont go past the 'showing that it's charging screen" I have to wait till it shows battery status before I can go into fast boot, and now it wont even do that... neat. Headed home, then i'll swap batteries and try it all again.
Click to expand...
Click to collapse
any updates?
hi clay_cauley .. I have the same problem..did y find any worked solution??
RiotSauce said:
any updates?
Click to expand...
Click to collapse
Hi all, I have the same issue I'll try all the above even though half of it sounds half Chinese to me XD (not a developer, heh).
Cheers,
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
UPDATE: So it wasn't bricked it, as I was able to return to the home screen. After a day of using it though, with the Nexus being buggy (freezing and crashing), it just died. I can't boot it or anything. It's plugged in, but nothing's happening.
Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Download factory image and do a factory restore:
https://developers.google.com/android/nexus/images#razorjss15q
I personally don't like toolkit. Recommend to root it yourself step by step.
I, being very technically unsavvy, have no idea what to do with the images.
Alright, here's the good news. You haven't bricked your nexus. You can and will fix this yourself, without a tool kit.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2379797
Then read it again and again until you understand the steps to fix your tablet. I was in your shoes once, years before toolkits were available and I learned how to fix worse problems then you have currently. Take your time.
Desperate User said:
I, being very technically unsavvy, have no idea what to do with the images.
Click to expand...
Click to collapse
Great user name given what you just posted
Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Same thing happened to me a month ago. Most important thing, don't freak out. Hold power for 20sec to hard reboot, then as soon as google logo appears hold down volume button to enter bootloader screen. From there you can do anything
http://forum.xda-developers.com/showthread.php?t=2391301
Did you boot into the phone after you unlocked the bootloader but before you tried to root? Do you have a custom recovery installed?
doe you have a custom recovery?
if so check if you still have your internal storage, i had the same problem as you but there is a bug going around when u unlock your bootloader your internal memory is wiped see this threat for feather explaining: http://forum.xda-developers.com/showthread.php?t=2380913
In my case i booted to fastboot and did the command fastboot -w and then it created new user partitions and then i could flash the stock image and then it worked again
Hope i helped u
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't know, maybe you should make your own thread rather than hijack mine.
Desperate User said:
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
Click to expand...
Click to collapse
owh, does it al least charger when u plug it in?
silvan g said:
owh, does it al least charger when u plug it in?
Click to expand...
Click to collapse
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything.
Click to expand...
Click to collapse
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Click to expand...
Click to collapse
If you're not rooted, it's just a stock update. There isn't any more risk than there is for any stock version, and you shouldn't lose data. If you buy a Nexus 7 2013 a few months down the line, after current stock with JWR66N is sold out, I believe it'll come with that update out of the box.
Desperate User said:
I don't know, maybe you should make your own thread rather than hijack mine.
Click to expand...
Click to collapse
I understand you're frustrated, but that was a little rude...he's just trying to get help, just like you.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Click to expand...
Click to collapse
Unrecognized in ADB or fastboot? Can you get into bootloader (boot while holding power and volume-down)? If you haven't tried fastboot while the phone is in the bootloader, and you can get into bootloader, try "fastboot devices." If you can do that, download a custom recovery and flash it from fastboot. Then format data and reboot.
silvan g said:
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
Click to expand...
Click to collapse
Done and nothing
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img for the LTE or fastboot boot openrecovery-twrp-2.6.0.0-flo.img for the WiFi version.
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Guhrasoh said:
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Click to expand...
Click to collapse
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Desperate User said:
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Click to expand...
Click to collapse
How long has it been charging? I'd give it a couple hours, then try the bootloader again.
I rooted the watch successfully and then attempted to revert to stock using the instructions here: http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
. Midway through the restore of the system.img, my computer crashed and now the watch is stuck at the Huwaei logo. I can no longer connect to the watch over adb - attemps to do so show that the watch is "offline." Is all hope lost or is there anything I can try?
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Edit...if it shows connected but offline, just try unplugging it and plugging it back in again.
Sent from my Nexus 6 using Tapatalk
brizey said:
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
davpel said:
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
Click to expand...
Click to collapse
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
brizey said:
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
Click to expand...
Click to collapse
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
If you can get into the bootloader, maybe try restoring these instead? http://forum.xda-developers.com/huawei-watch/general/huawei-watch-stock-rooted-images-t3224930
davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
brizey said:
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
Click to expand...
Click to collapse
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
davpel said:
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
Click to expand...
Click to collapse
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
1/4 Life said:
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
Click to expand...
Click to collapse
Tried that. I get the double vibration, but no bootloader.
FWIW, I just looked at a few of the 5.1 OTAs for other watches. I think the OTAs will work even if rooted. I looked at skin1980's init autoroot script, and I don't think it really touches any of the base system files...it only adds in the binaries. The updater script does a hash on all of the files that it is going to patch, then patches them if the hashes are OK. Given that we are not really touching the system files by flashing a custom ROM, I think we can make the OTA zips work. The kernel will likely not flash, but we can always build a new one from source if needed.
brizey said:
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
Click to expand...
Click to collapse
And i dont know why. I dd them like i said and they are completely stock.
davpel said:
Tried that. I get the double vibration, but no bootloader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
1/4 Life said:
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
Click to expand...
Click to collapse
Thanks, but tried the LG method as well (both the swipe and the tap) and had the same results -- or lack thereof.
Has anyone else tried restoring to stock with success from Skin's files?
myke66 said:
Has anyone else tried restoring to stock with success from Skin's files?
Click to expand...
Click to collapse
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
davpel said:
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Click to expand...
Click to collapse
Agree 100%. I am returning my first watch, and flashed it back to stock and relocked the bootloader with no issues using the revised instructions. Going to keep my new one stock I think...got to cut down on the toys (Nexus 6, Nexus 7, iPhone 5s, custom PC, G37, surveillance system, house LED lighting conversion, etc. etc. Momma ain't happy, and I really want to spend more time with the kiddos.)
Who the hell needs to ROOT a damn smart watch?! I could see when it was 2 years ago with the first Samsung smart watch to sideload Android apps but this.... This is just stupid. Congrats
Sent from my SM-N910T using Tapatalk