Develop Bugs

Noob needs help with fixing cyanogen boot loop

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!!

[HELP]Galaxy Nexus Stuck on Google Logo bootloop

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,

Help! I Think I Soft Bricked my M8 GPE..?

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

Rooted Elephone P8000 stucks at Boot Logo after OTA Update

Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?

vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!

kevvyboy said:
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
Click to expand...
Click to collapse
Thanks a lot fot pointing this out.
Managed to get the recovery options menu.
However wiping the cache didn't help.
After doing the "root integrity check" got this:
{
"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"
}
do you think this can be fixed w/o reflashing an entire rom?

Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash

kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Sad... anyway would you please direct me to where I can download the flash tool and stock ROM? Thanks.

kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.

pitrus- said:
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
Click to expand...
Click to collapse
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?

vagifn said:
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
Click to expand...
Click to collapse
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...

pitrus- said:
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
Click to expand...
Click to collapse
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.

vagifn said:
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
Click to expand...
Click to collapse
You belive this b***** that feed you on official forum? OTA should work on any device software config.

ruonim said:
You belive this b***** that feed you on official forum? OTA should work on any device software config.
Click to expand...
Click to collapse
I didn't read official forum. However you do loose your warranty if device is rooted, thus the device manufacturer owes you nothing. OTA worked fine before I rooted my device.
Btw, I got my phone back to life by re-flashing the entire ROM, just in case.

Hello my friend
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.

allianzcred said:
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
Click to expand...
Click to collapse
Already did, thanks. Will never combine Root and OTA together again

Helpp?Stuck On Battery 0% Icon (Vs985)

Hi Guys ,My Vs985 is still stuck on 0% battery icon when i power it on
{
"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"
}
And When I Put it On Charger It Stay at this screen
I Charge it for 8 9 hours but the battery stay 0% and the red light blinking
Also,
I put The Battery On A Standard Charger And She Showed As Charger 100% So I think the problem is From The phone.
Hope U'll help me to fix thiis asap

up up help plzz urgent

can u mby get it in download mode? It seems that some part of bootloader is damaged. But thats just my non proffesional statement

nothing new need help plzz

help plzz guyss

No One Can Help Me Here Rip Xda

Hamza058 said:
No One Can Help Me Here Rip Xda
Click to expand...
Click to collapse
reflash your rom dont wipe just reflash put it in recovery if you cant get in recovery the get in dowload reflash the stock fw then flash twrp boot to twrp then restart your phone go back to twrp flash your rom and gapps restart the phone again wait for it to boot go threw the set up then go in flash su and bump boot and restart then get back to me the other guy who commented is close its not just that the firmware is corrupt and the charge isnt going in to the battery if you can get another temporary battery just to boot to see if it boots before you follow the steps but make sure you follow them to a T cause im not resposable for a bricked device or any acts of god or nuclear explosion
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
nio97 said:
can u mby get it in download mode? It seems that some part of bootloader is damaged. But thats just my non proffesional statement
Click to expand...
Click to collapse
your close its the firmware itself thats corrupt he may need to go back to stock
its never fun to restore to stock to reflash the rom

Have a similair issue. Using TWRP. I solved it by going into recovery and press reboot to system.

vanputten80 said:
Have a similair issue. Using TWRP. I solved it by going into recovery and press reboot to system.
Click to expand...
Click to collapse
sometimes but sometimes the rom can have a just unlucky bug and cause it to not charge so try all options before you reflash

XS37 said:
reflash your rom dont wipe just reflash put it in recovery if you cant get in recovery the get in dowload reflash the stock fw then flash twrp boot to twrp then restart your phone go back to twrp flash your rom and gapps restart the phone again wait for it to boot go threw the set up then go in flash su and bump boot and restart then get back to me the other guy who commented is close its not just that the firmware is corrupt and the charge isnt going in to the battery if you can get another temporary battery just to boot to see if it boots before you follow the steps but make sure you follow them to a T cause im not resposable for a bricked device or any acts of god or nuclear explosion
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
your close its the firmware itself thats corrupt he may need to go back to stock
its never fun to restore to stock to reflash the rom
Click to expand...
Click to collapse
Hii But I Don't Have Download Mode,Recovery Mode..nothing,only show that battery sign ;I Can Only Acces To Qload (9008)

I Try With Another Battery And still the same problem

Hamza058 said:
Hii But I Don't Have Download Mode,Recovery Mode..nothing,only show that battery sign ;I Can Only Acces To Qload (9008)
Click to expand...
Click to collapse
how are you accessing qload?
and the is a way but let me look threw my notes
---------- Post added at 08:33 PM ---------- Previous post was at 08:22 PM ----------
Hamza058 said:
Hii But I Don't Have Download Mode,Recovery Mode..nothing,only show that battery sign ;I Can Only Acces To Qload (9008)
Click to expand...
Click to collapse
how are you entering qloader mode and yes there is a way to do it using qload right now your phones probably a brick give me a few to check my notes and ill see if i can find somthing

XS37 said:
reflash your rom dont wipe just reflash put it in recovery if you cant get in recovery the get in dowload reflash the stock fw then flash twrp boot to twrp then restart your phone go back to twrp flash your rom and gapps restart the phone again wait for it to boot go threw the set up then go in flash su and bump boot and restart then get back to me the other guy who commented is close its not just that the firmware is corrupt and the charge isnt going in to the battery if you can get another temporary battery just to boot to see if it boots before you follow the steps but make sure you follow them to a T cause im not resposable for a bricked device or any acts of god or nuclear explosion
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
your close its the firmware itself thats corrupt he may need to go back to stock
its never fun to restore to stock to reflash the rom
Click to expand...
Click to collapse
XS37 said:
how are you accessing qload?
and the is a way but let me look threw my notes
---------- Post added at 08:33 PM ---------- Previous post was at 08:22 PM ----------
how are you entering qloader mode and yes there is a way to do it using qload right now your phones probably a brick give me a few to check my notes and ill see if i can find somthing
Click to expand...
Click to collapse
by shortcut the pins

Hamza058 said:
by shortcut the pins
Click to expand...
Click to collapse
follow this to a t
https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359

XS37 said:
follow this to a t
https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
i know this method already and flash images by it many times

Hamza058 said:
i know this method already and flash images by it many times
Click to expand...
Click to collapse
oh sorry i figured you might not have seen it but to explain why i think you have a corrupt power/bootloader/emmc so this would be the only fix i can think of

XS37 said:
oh sorry i figured you might not have seen it but to explain why i think you have a corrupt power/bootloader/emmc so this would be the only fix i can think of
Click to expand...
Click to collapse
thnx for help dude hope will get fixed soon

Hamza058 said:
thnx for help dude hope will get fixed soon
Click to expand...
Click to collapse
me to im in the middle of trying this with myn as myn has no firmware at all cant access nothing so i had to try the shorting of my pins to check it to try and fix it
good luck me buddy

were you able to fix the problem? if you did, would you mind to share the solution?

not yet