The battery ran out of my N10 after using the tool kit on it. It did not die while I was trying to root/install custom bootloader, but it died while I was on the fastboot screen. I also think the recovery had an issue because it showed a black screen with an android laying down with a red exclamation mark on it. I'm thinking the red exclamation mark is because of the recovery? Before it died on me, I couldn't get past the nexus X on the screen... it died on me while trying to get past this issue. I thought maybe it would work if I could flash the stock recovery but the battery died before I could get to that.
When I try to boot up the tablet with the charger in it, I get the battery icon in the center of a dark screen with a lightning bolt on it. Before, I think it had an empty battery image on it. I had it charging all day today while I was at work and still no dice.
Any ideas as to what I did? I am going to hate myself if I bricked my tablet after flashing so many roms on so many phones. This sucks
I would charge the N10 as long as possible (I'd say at least an hour) from the wall, while completely off. Then unplug it, and hold down Power + Vol Up + Vol Down (all 3 physical buttons), and see if it takes you to fastboot. If you can get to this, your tablet isn't bricked. Only case you wouldn't be able to access fastboot is if a command was ran to erase the bootloader, and a bootloader was never flashed back (for now, there is 0 reason to even touch the bootloader, but I have no idea what a toolkit might do).
As for the Android lying on it's side with the red !, you have to press Power + Vol Up (or some combination like that) to actually get to the recovery screen (safety measure I guess).
As for the some other tips:
- If you unlock the bootloader, you'll most likely have to either reflash the factory image, or flash a custom recovery and flash a custom ROM over USB OTG. I believe an oem unlock causes the ROM to delete some files or something for safety measures (on the Nexus 7, it would actually do a factory reset on it's own, but the Nexus 10 does not)
- I recommend learning how to use fastboot and adb on their own instead of relying on a toolkit for the long run
I agree. I tried to reload the factory image with the toolkit and after it reboots i get that android with the red !... tried it three times, each time it wouldnt let me boot past the X, and each time i re-flashed, I got the same error with the android and the red !. That's why I thought maybe I had to put the stock recovery back in... I've been reading that CWM doesn't work well with the N10... ahh this bytes lol
djhaf said:
I agree. I tried to reload the factory image with the toolkit and after it reboots i get that android with the red !... tried it three times, each time it wouldnt let me boot past the X, and each time i re-flashed, I got the same error with the android and the red !. That's why I thought maybe I had to put the stock recovery back in... I've been reading that CWM doesn't work well with the N10... ahh this bytes lol
Click to expand...
Click to collapse
I might suggest manually downloading the factory image from: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-87340b80.tgz and extracting it's folder, and running the flash-all.bat file inside. Google's batch file wipes and reflashes the bootloader, wipes the current ROM and reflashes stock, and then boots the device. I'm not too sure if the toolkit does the same process or not though.
The folder to extract is mantaray-jop40c, and this is what should be inside:
{
"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 it runs the following:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-mantaray-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Click to expand...
Click to collapse
If it can't find fastboot or adb for some reason, try downloading this (adb and fastboot Windows executables from latest platform-tools) and putting the 2 files in the mantaray-jop40c folder:
http://puu.sh/1vr4X
And if the batch file still doesn't want to work, try editing it to remove the PATH thing, or just use this edited batch file: http://puu.sh/1vr7c
I'll try... if this thing boots up lol. When I press the three buttons while it's plugged in I see the battery charging icon... as soon as I take out the cable it doesn't do anything. I had it charging through the wall all day today... 12 hours =\
djhaf said:
I agree. I tried to reload the factory image with the toolkit and after it reboots i get that android with the red !... tried it three times, each time it wouldnt let me boot past the X, and each time i re-flashed, I got the same error with the android and the red !. That's why I thought maybe I had to put the stock recovery back in... I've been reading that CWM doesn't work well with the N10... ahh this bytes lol
Click to expand...
Click to collapse
Go back to where the android on its back with exclamation point. Then hold Power and briefly click on volume up and let go. This should take you to the menus. Then just factory reset and you should be able to get past the boot up processes.
Sent from my SPH-L710 using xda app-developers app
djhaf said:
I'll try... if this thing boots up lol. When I press the three buttons while it's plugged in I see the battery charging icon... as soon as I take out the cable it doesn't do anything. I had it charging through the wall all day today... 12 hours =\
Click to expand...
Click to collapse
It might take a little bit of time for it to do anything also. I would say hold the 3 buttons down for at the most 20 seconds and wait for the N10 to vibrate.
jjdevega said:
Go back to where the android on its back with exclamation point. Then hold Power and briefly click on volume up and let go. This should take you to the menus. Then just factory reset and you should be able to get past the boot up processes.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
dude i love you thank you so much!!!!!
for some reason none of my chargers were charging the tablet, but charged my phone. had to use my sisters.... strange.
your advice got me through the boot issue and now i'm up and running.
THANK YOU!!!!!!!!
Related
So i rooted my phone this morning using motofail2go and it was successful. after browsing around and stuff i come across a app called Beats Audio. I installed it and it said the phone needed to reboot. it turned off and turned on but when the motorola logo disappears nothing else happens. the screen will stay black. i thought wiping the data and cahce partitions the phone will go back to working condition but no luck it still did the same thing. i tired RSDlite 6.1.4 but after hitting start it immediately failed. in the boot options everything else besides AP Fastboot goes to a black screen and does nothing. when i looked around for the RSD tutorials they all said that RSD will recongize the device as XT907 but for me RSD showed it as Fastboot SCORPION_MINI S. can you please help me? i would be very greatful
{
"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"
}
If you do power and volume down buttons together will it boot then ?
jtommyj said:
If you do power and volume down buttons together will it boot then ?
Click to expand...
Click to collapse
i tried everything. i held the power and volume buttons and i get to the boot mode selection menu and my choices are
Normal bootup
Recovery
AP Fastboot
Factory
BP Tools
i clicked on everything and they all do the same thing which is the motorola logo will show for a few seconds like normal then it'll go to a black screen and do nothing.
AKG0214 said:
i tried everything. i held the power and volume buttons and i get to the boot mode selection menu and my choices are
Normal bootup
Recovery
AP Fastboot
Factory
BP Tools
i clicked on everything and they all do the same thing which is the motorola logo will show for a few seconds like normal then it'll go to a black screen and do nothing.
Click to expand...
Click to collapse
Go too ap fast boot mode on the device, plug it in too PC, start rsdlite 6.1.4, point rsd too the fast boot files "~680mb file" let it extract it, then after it fails, click the "browse files button" on rsd, it should be pointed too an XML file, "right-click" and edit the file, if not possible locate the file via windows explorer, once you right click and begin editing, you should remove any lines with the words "OEM " or "var" that means, lines such as "get var" or the "OEM fb-set-clear" lines, just delete them completely, and save the file.. try it again, if it fails just delete the line "gpt_main.bin" and you should have no errors,
Sorry for the formatting this was done on mobile asap, if you don't understand or cant do it, please locate the XML on your computer and attach it here, or PM me the XML and I will gladly edit it for you..
AKG0214 said:
i tried everything. i held the power and volume buttons and i get to the boot mode selection menu and my choices are
Normal bootup
Recovery
AP Fastboot
Factory
BP Tools
i clicked on everything and they all do the same thing which is the motorola logo will show for a few seconds like normal then it'll go to a black screen and do nothing.
Click to expand...
Click to collapse
I know you'll get to that menu by holding ~both~ volume buttons and the power but did you just do the volume down and power ?
It's a little unclear from your answer as that is supposed to be the failsafe boot mode and worked for me under similar circumstances
tadgerloks said:
Go too ap fast boot mode on the device, plug it in too PC, start rsdlite 6.1.4, point rsd too the fast boot files "~680mb file" let it extract it, then after it fails, click the "browse files button" on rsd, it should be pointed too an XML file, "right-click" and edit the file, if not possible locate the file via windows explorer, once you right click and begin editing, you should remove any lines with the words "OEM " or "var" that means, lines such as "get var" or the "OEM fb-set-clear" lines, just delete them completely, and save the file.. try it again, if it fails just delete the line "gpt_main.bin" and you should have no errors,
Sorry for the formatting this was done on mobile asap, if you don't understand or cant do it, please locate the XML on your computer and attach it here, or PM me the XML and I will gladly edit it for you..
Click to expand...
Click to collapse
i deleted all the lines that had oem and var into but also failed but i haven't tried delete the gpt_main.bin yet. i managed to get to the charging screen but it was at 14% and i want to try to turn it on at some point. but im not sure if it was the beats audio that messed up my phone. cuz when i rooted it i never thought of turning it off and rebooting it to see if any problems occurred but after reading tons of reviews about the app it seems like it was the app that caused it cuz a few other people came facing the same problem. but thanks you for the information i really appreciate the help
AKG0214 said:
i deleted all the lines that had oem and var into but also failed but i haven't tried delete the gpt_main.bin yet. i managed to get to the charging screen but it was at 14% and i want to try to turn it on at some point. but im not sure if it was the beats audio that messed up my phone. cuz when i rooted it i never thought of turning it off and rebooting it to see if any problems occurred but after reading tons of reviews about the app it seems like it was the app that caused it cuz a few other people came facing the same problem. but thanks you for the information i really appreciate the help
Click to expand...
Click to collapse
Let it charge too 60% before trying too flash from rsd, and keep the XML file edited then try again once its charged, I know mine didn't complete when I tried at 9% but after 60% I tried again and it went through flawlessly
tadgerloks said:
Let it charge too 60% before trying too flash from rsd, and keep the XML file edited then try again once its charged, I know mine didn't complete when I tried at 9% but after 60% I tried again and it went through flawlessly
Click to expand...
Click to collapse
i didnt know battery life was so crucial to recovery cuz i just tried the xml without editing it and i got to 17/22 so im going to try again at 70% cuz this phone kinda charges fast lol but thanks for all the help guys i really appreciate it.
The same happened to me and I just reflashed the ICS again and all is fine.
Sent from my magnificent Droid RAZR M using XDA Premium!
Yeah I reccomnd charging it , anything above 50% is fine, nd use the edited one, for some reason leaving it unedited causes problems, or sloppy restores
tadgerloks said:
Yeah I reccomnd charging it , anything above 50% is fine, nd use the edited one, for some reason leaving it unedited causes problems, or sloppy restores
Click to expand...
Click to collapse
i'll send you the stock xml doc for you to edit it if thats okay with you. this problem wouldnt matter as much if my phone was also used for work but seeing how my boss and my bosses boss contacts me at this phone and it "had" all my clients information on it and work orders.
Well I feel bad for your data, if you wiped through recovery, or when you restore through fast boot, here's hoping you had some stuff backed up ie contacts notes alarms calendars etc. But once the phone is working Google sync should help with that so no worries
tadgerloks said:
Well I feel bad for your data, if you wiped through recovery, or when you restore through fast boot, here's hoping you had some stuff backed up ie contacts notes alarms calendars etc. But once the phone is working Google sync should help with that so no worries
Click to expand...
Click to collapse
i left it on the charger all night and when i woke up i opend up RSD open the edited xml doc you sent me put th ephone is fast boot mode then hooked it up to the compter and hit start every goes well but once it hits system.img ext4 it fails after a few seconds.
i have to give mad props to everyone that helped my thank you so much my phone is back to woeking again but now ever time i turn in on its in ap fast boot but at the botton it says Fastboot Reason: Sticky hit factory_fastboot but i usually just go back to the boot selection menu and hit normal power up. it works though
To get rid of the sticky fast boot just flash it again, I had same issue, just restore one or 2 more times and it will go away, it is a hassle dealing with it after a while
tadgerloks said:
To get rid of the sticky fast boot just flash it again, I had same issue, just restore one or 2 more times and it will go away, it is a hassle dealing with it after a while
Click to expand...
Click to collapse
the weird thing is that when i select ap boot from the boot options screen and tried flashing it. it would quit at system.img.ext4 no matter what i did but i was messing with the volume buttons (out of boredom) and the ap fastboot came up instantly instead of the boot menu. i looked at the bottom and i dont remeber what it said but it was different then selecting it from boot menu. so i left it alone and attempted to flash it again and next thing i know it worked. and the sticky menu doesnt bother me as long as my phone works im happy lol so the issue is resolved and i can get back to work again lol here is proof
<--- epic game btw
AKG0214 said:
the weird thing is that when i select ap boot from the boot options screen and tried flashing it. it would quit at system.img.ext4 no matter what i did but i was messing with the volume buttons (out of boredom) and the ap fastboot came up instantly instead of the boot menu. i looked at the bottom and i dont remeber what it said but it was different then selecting it from boot menu. so i left it alone and attempted to flash it again and next thing i know it worked. and the sticky menu doesnt bother me as long as my phone works im happy lol so the issue is resolved and i can get back to work again lol here is proof
<--- epic game btw
Click to expand...
Click to collapse
Dead trigger?
Sent from my Xoom using xda app-developers app
Dyelon said:
Dead trigger?
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
Yupp dead trigger, gorgeous graphics too, runs like a dream on high settings
Except for me with the jb leak, I'm seeing lots of glitches in graphics compared to ics.
Sent from my XT907 using xda app-developers app
rav3nous said:
Except for me with the jb leak, I'm seeing lots of glitches in graphics compared to ics.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Well its working fine for me on jb, but hey every device is different I guess, and I hardly play it, trying too pass mc3 and nova 3 instead
Hello, i was trying to charge my nexus 4 couse it wouldn't turn on but after an hour it still didn't turn on.
So after trying a liitle wile to turn it on i held all three buttons (power, volume up & down) and now it says "Download Mode".
{
"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"
}
Never heard of this mode. Try connecting ur phone to pc and see if it gets detected. That would be nice to know.
gt-kingz said:
Never heard of this mode. Try connecting ur phone to pc and see if it gets detected. That would be nice to know.
Click to expand...
Click to collapse
srry just restarted (it don't appear on the computer, can check with lsusb on ubuntu but not now)
How to do it!
How to get into Download Mode
Boot into bootloader and hold all three buttons
It's LG's version of Samsung's Odin mode. However, there isn't a leak of the utility yet.
There is a long tutorial on how to use it in the Nexus 4 service manual floating around.
Basically it's worthless for us until that utility leaks.
El Daddy said:
It's LG's version of Samsung's Odin mode. However, there isn't a leak of the utility yet.
There is a long tutorial on how to use it in the Nexus 4 service manual floating around.
Basically it's worthless for us until that utility leaks.
Click to expand...
Click to collapse
I'm not entirely sure, but I think that "Download mode" interfaces with LGNPST. From my understanding, it's not publicly available, but...
Anyway, this is an interesting thread.
efrant said:
I'm not entirely sure, but I think that "Download mode" interfaces with LGNPST. From my understanding, it's not publicly available, but...
Anyway, this is an interesting thread.
Click to expand...
Click to collapse
Interesting indeed. So it looks like I'm wrong. Most of that stuff is way over my head though.
Sent from my Nexus 7 using xda premium
When I first rooted I flashed a bad recovery that deleted all my stuff and got into DL mode 3 times, I panicked. Somehow I managed to get back into boot loader and after that flashed stock boot.IMG and re-rooted...
Sent from my Nexus 4 using xda app-developers app
309041291a said:
When I first rooted I flashed a bad recovery that deleted all my stuff and got into DL mode 3 times, I panicked. Somehow I managed to get back into boot loader and after that flashed stock boot.IMG and re-rooted...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i'm in the same situation and appropriate anybody's help to get me back into the right track.
So what happened with this? Mine just did the same while doing the rooting of my phone. I've been using MSKIP's tutorial amongst other youtube videos showing his option in depth. No idea what happened but now I'm stuck in this "brick" or "soft brick" mode like you guys were saying earlier. What is the solution? I don't see any other pages in this thread and I'm a total noob with this stuff.
**Edit**
Fixed mine, was waiting for a while like it said but I finally powered it one, did a factory reset, and re-did everything else that comes with the 1 CLICK FOR ALL button on mskip's toolkit. Everything is perfect now and I hacked it, whoo hoo!
easy fix... working..
Jbele said:
Hello, i was trying to charge my nexus 4 couse it wouldn't turn on but after an hour it still didn't turn on.
So after trying a liitle wile to turn it on i held all three buttons (power, volume up & down) and now it says "Download Mode".
Click to expand...
Click to collapse
this same problem happened to me today.. don't worry there is a fix...
1.Get into bootloader ( Press all three buttons at same time)
2.flash google factory image from fastboot. get factory images from here... https://developers.google.com/android/nexus/images ..
3.If you dont know how to flash use mskip's toolkit for nexus 4 and flash it... (best for new users like me) get mskip's toolkit from here... http://forum.xda-developers.com/showthread.php?t=1995688
ALL THANKS TO MSKIP'S TOOLKIT
if you have queries or want detailed information comment below
NICE FEELING WHEN YOU SEE DOWNLOAD MODE... WORTH EXPERIENCING THE MINI HEART ATTACK..
DON'T WORRY ITS NEARLY IMPOSSIBLE TO BRICK NEXUS 4..
:good::good::good: ALL THE BEST:good::good::good:
HOPE THIS WORKS
shengovind said:
this same problem happened to me today.. don't worry there is a fix...
1.Get into bootloader ( Press all three buttons at same time)
2.flash google factory image from fastboot. get factory images from here... https://developers.google.com/android/nexus/images ..
3.If you dont know how to flash use mskip's toolkit for nexus 4 and flash it... (best for new users like me) get mskip's toolkit from here... http://forum.xda-developers.com/showthread.php?t=1995688
ALL THANKS TO MSKIP'S TOOLKIT
if you have queries or want detailed information comment below
NICE FEELING WHEN YOU SEE DOWNLOAD MODE... WORTH EXPERIENCING THE MINI HEART ATTACK..
DON'T WORRY ITS NEARLY IMPOSSIBLE TO BRICK NEXUS 4..
:good::good::good: ALL THE BEST:good::good::good:
HOPE THIS WORKS
Click to expand...
Click to collapse
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
havlaz said:
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
Click to expand...
Click to collapse
You should try to get into the fastboot mode first, when the phone is off, Hold Power + Volume Download button. If you can get in the fastboot menu, then use instruction above to reflash your device.
If you can't, you might be able to recover your phone using Download Mode: http://forum.xda-developers.com/showthread.php?t=2347060
havlaz said:
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
Click to expand...
Click to collapse
Red light due to battery low..
All you have to do is charge the phone for about six hours on the wall charger..
Then try booting your phone ..
If there's only bootloader and phone isn't booting flash factory from fastboot..
Plug it to wall charger over night.. Then try to get to download mode..
Try this to get out of red light only if there is absolutely no other way..: http://forum.xda-developers.com/showthread.php?t=2250454
If there is no boot loader whatsoever even after trying for a hell lot of time, only download mode, then do this..
http://forum.xda-developers.com/showthread.php?t=2347060
sent from my Prevert nexus
psak said:
i'm in the same situation and appropriate anybody's help to get me back into the right track.
Click to expand...
Click to collapse
When you are in download mode, press and hold Vol Down and Power, that should bring up fastboot mode, which you can use to flash another recovery...
[email protected] said:
When you are in download mode, press and hold Vol Down and Power, that should bring up fastboot mode, which you can use to flash another recovery...
Click to expand...
Click to collapse
Try Pressing power button alone for 10 sec or so...
Should do the trick
Having the same problem. I was on purity rom(4.4.3), with default purity kernel. I flashed the Ak poseidon kernel, with Ukm. It booted fine , was on phone for about 4 minutes, and then I ran antutu benchmark. Before that I didn’t change anything via synapse app. Then when I ran test on antutu phone went off. Non of the buttons were responding. I plugged the phone into wall charger and pressed all 3 buttons. Then the download mode appeared. Left it like that on the charger , went to sleep. When I woke up the phone was turned off. Today I was flashing factory img ( 4.4.3. occam). Following the instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 [/URL]. Everything went ok no problem in the cmd , only the thing was , when I had to fastboot the booth loader, then the phone stuck in power on loop . ( reboots, then it says google, and reboots again) I was able to stop this by holding volume down, then it goes into bootloader. Finished flashing factory img, like it says on the tut. And the same thing happens. The phone won’t boot, And it is not responding when it is unplugged. Please help :/
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
shengovind said:
Red light due to battery low..
All you have to do is charge the phone for about six hours on the wall charger..
Then try booting your phone ..
If there's only bootloader and phone isn't booting flash factory from fastboot..
Plug it to wall charger over night.. Then try to get to download mode..
Try this to get out of red light only if there is absolutely no other way..: http://forum.xda-developers.com/showthread.php?t=2250454
If there is no boot loader whatsoever even after trying for a hell lot of time, only download mode, then do this..
http://forum.xda-developers.com/showthread.php?t=2347060
sent from my Prevert nexus
Click to expand...
Click to collapse
I will try to reconnect the battery now, maby that will help----
Fixed it !
ripped.animal said:
Having the same problem. I was on purity rom(4.4.3), with default purity kernel. I flashed the Ak poseidon kernel, with Ukm. It booted fine , was on phone for about 4 minutes, and then I ran antutu benchmark. Before that I didn’t change anything via synapse app. Then when I ran test on antutu phone went off. Non of the buttons were responding. I plugged the phone into wall charger and pressed all 3 buttons. Then the download mode appeared. Left it like that on the charger , went to sleep. When I woke up the phone was turned off. Today I was flashing factory img ( 4.4.3. occam). Following the instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 [/URL]. Everything went ok no problem in the cmd , only the thing was , when I had to fastboot the booth loader, then the phone stuck in power on loop . ( reboots, then it says google, and reboots again) I was able to stop this by holding volume down, then it goes into bootloader. Finished flashing factory img, like it says on the tut. And the same thing happens. The phone won’t boot, And it is not responding when it is unplugged. Please help :/
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
I will try to reconnect the battery now, maby that will help----
Click to expand...
Click to collapse
After reconnecting the battery, I managed to boot the device. But i got gazzlion errors, non of the apps were responding. I got the msg to delete the partion or my device will not function properly. Since I have already flashed the factory img I booted to stock recovery. And deleted all user data , (factory reset). Then the device booted normally. I have lost my recovery img but what the hell I don’t care now Flashed the CMW touch, and super user. Now everything works fine
Fix - Volume Up + Power
I had the same problem this morning and found an easier fix on Google product forums.
Push Volume Up + Power button until it works. Worked for me
<not able to paste link as I'm still a n00b user and this is among my first ten posts here. Ok, this is my FIRST post here>
I got the same thing too...
Hi All,
Little background, I don't own OnePlus 2; I got one from a friend of mine and he already soft brick it, phone turns on and goes to stock recovery with these options (Install form SD, Install form USB, Wipe data and cache, Advanced, Reboot) so i only have these options to work with. Also I can boot into fastboot as well. Unfortunately bootloader is locked and I am unable to unlock it (restricted bla bla bla). So all I am looking for is to restore it back to stock state, just want this dam thing to boot up again. Any help would be nice. I am actively reading up threads on xda and other sites and there is a lot of information. Thanks in advance
If I were you
First try wiping data and cache from stock recovery and try to boot.
If don't work since you have stock recovery you can flash signed full zip, I suggest to grab 2.2.x from next link (don't use beta 3.0)
http://forum.xda-developers.com/showthread.php?t=3209863
If still don't work as last resource try this guide
http://forum.xda-developers.com/showthread.php?t=3269543
It supposed to be official service images I guess no need to have bootloader unlooked.
Sent from my ONE A2005 using Tapatalk
fburgos said:
If I were you
First try wiping data and cache from stock recovery and try to boot.
If don't work since you have stock recovery you can flash signed full zip, I suggest to grab 2.2.x from next link (don't use beta 3.0)
http://forum.xda-developers.com/showthread.php?t=3209863
If still don't work as last resource try this guide
http://forum.xda-developers.com/showthread.php?t=3269543
It supposed to be official service images I guess no need to have bootloader unlooked.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Thanks, ill try the steps mentioned, Fingers crossed this will work
fburgos said:
If I were you
First try wiping data and cache from stock recovery and try to boot.
If don't work since you have stock recovery you can flash signed full zip, I suggest to grab 2.2.x from next link (don't use beta 3.0)
http://forum.xda-developers.com/showthread.php?t=3209863
If still don't work as last resource try this guide
http://forum.xda-developers.com/showthread.php?t=3269543
It supposed to be official service images I guess no need to have bootloader unlooked.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Tried fist 2 steps, no use. phone reboots and boots back into recovery. its like i am bootlooping into recovery. trying the 3rd method fingers crossed.
Tried all methods and none worked.
{
"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 tried again and bam process went through, i got this green message in Chinese and phone automatically boots into recovery mode.
Any thoughts on what should be my next step ?
Edit: the exit button is not active so i was thinking the process is still ongoing, giving another 10 minutes before proceeding forward.
Ok lots of things happened in past few hours.
1. Was able to Unbrick/Recover OnePlus 2 Back to stock 100% via (http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543)
2. was able to flash from usb via stock recovery Oxygen OS 2.0 (http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863).
3. Phone was stuck on reboot to recovery so read some ware the use command "fastboot continue" and it worked. was able to boot into android and was able to setup, no problem but the phone was in safe mode.
4. Rebooted the device and back to stock recover. Now need help to get to the rom and bypass the recovery.
Edit: I am able to enter rom every time with "fastboot continue" command. the android boots in safe mode and i am unable to boot normally or even without command.
I think i have narrowed down the issue to broken volume down button. When you think about it, it makes sense. If you turn on the device and press and hole volume down u go to recovery which is exactly what my phone is doing. And when i use fastboot continue command it boots the OS in safe mode which is done when you press and hold volume down while booting. Now I am planning to get the stuck volume down button fixed. If was able to unlock the bootloader i might be able to flash twrp and boot into system from there but alas no luck there.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
I remember Exodus developer raja-m had issues with his volume buttons, send it to repair I think you should try that
Sent from my ONE A2005 using Tapatalk
As suspected the stuck volum down button was the culprit, got it fixed and phone is working like it never had any issue. Pesky little bugger
I've searched far and wide for an answer to my problem and I've returned with nothing. It's been almost 24 hours without my phone and I think I'm losing it. I've downloaded and tried LGUP (alongside Uppercut), LG FlashTool 2014, LG Bridge, LG DLLs, etc and nothing has worked to flash my phone to stock with the KDZ. The closest I've gotten it to work is with LGUP but stupid me, I managed to edit the buildprop before it went self destruct and changed the device identifier to a Google Pixel XL and LGUP refuses to cooperate. Any help is appreciated. Please. :good:
I've managed to get into fastboot. I'm sure I can do something from here but idk what to put. Any help is appreciated once 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"
}
kilakoust said:
I've searched far and wide for an answer to my problem and I've returned with nothing. It's been almost 24 hours without my phone and I think I'm losing it. I've downloaded and tried LGUP (alongside Uppercut), LG FlashTool 2014, LG Bridge, LG DLLs, etc and nothing has worked to flash my phone to stock with the KDZ. The closest I've gotten it to work is with LGUP but stupid me, I managed to edit the buildprop before it went self destruct and changed the device identifier to a Google Pixel XL and LGUP refuses to cooperate. Any help is appreciated. Please. :good:
I've managed to get into fastboot. I'm sure I can do something from here but idk what to put. Any help is appreciated once again
Click to expand...
Click to collapse
My guess is that you're rooted considering you've edited the build.prop? Why not enter recovery and flash a stock rom?
kilakoust said:
I've searched far and wide for an answer to my problem and I've returned with nothing. It's been almost 24 hours without my phone and I think I'm losing it. I've downloaded and tried LGUP (alongside Uppercut), LG FlashTool 2014, LG Bridge, LG DLLs, etc and nothing has worked to flash my phone to stock with the KDZ. The closest I've gotten it to work is with LGUP but stupid me, I managed to edit the buildprop before it went self destruct and changed the device identifier to a Google Pixel XL and LGUP refuses to cooperate. Any help is appreciated. Please. :good:
I've managed to get into fastboot. I'm sure I can do something from here but idk what to put. Any help is appreciated once again
Click to expand...
Click to collapse
Can you not get into TWRP?? I believe its the same way as everyone else..\
Hold the volume down button and the power button and as soon as you see the LG logo left go of the power button and press it again. This manual step is a pain in the arse, but it will get you there eventually. Since youre rooted, you also get the "This device is corrupted screen" yes? The LG logo popup you are looking for is right before that.
What I do for easy and fast access is this. I keep the back cover off and hold the volume down button for ease. I hold the power button, let go, and press it again and ususally that first try doesnt work. As soon as I see the corrupt screen I take the battery out very quickly and put it back in and repeat the process. After a few tries the LG logo will hang before the corrupt screen and that gives you the time you need to let go of the power button and then hold it again until the factory reset screen comes up. Just hit yes twice... It will go into TWRP.
Biff627 said:
Can you not get into TWRP?? I believe its the same way as everyone else..\
Hold the volume down button and the power button and as soon as you see the LG logo left go of the power button and press it again. This manual step is a pain in the arse, but it will get you there eventually. Since youre rooted, you also get the "This device is corrupted screen" yes? The LG logo popup you are looking for is right before that.
What I do for easy and fast access is this. I keep the back cover off and hold the volume down button for ease. I hold the power button, let go, and press it again and ususally that first try doesnt work. As soon as I see the corrupt screen I take the battery out very quickly and put it back in and repeat the process. After a few tries the LG logo will hang before the corrupt screen and that gives you the time you need to let go of the power button and then hold it again until the factory reset screen comes up. Just hit yes twice... It will go into TWRP.
Click to expand...
Click to collapse
Wow a yeah later and this helped me. my superv20 mod took a poop for no reason at all and i couldn't boot or get into recovery for what ever reason but this key combo if done twice worked to get me into recovery.
cbissa18 said:
Wow a yeah later and this helped me. my superv20 mod took a poop for no reason at all and i couldn't boot or get into recovery for what ever reason but this key combo if done twice worked to get me into recovery.
Click to expand...
Click to collapse
I'm glad that this helped you out. Getting into recovery with root was always a pain.
Biff627 said:
I'm glad that this helped you out. Getting into recovery with root was always a pain.
Click to expand...
Click to collapse
yeah not sure why, its like it doesnt stick smh. but it does you just have to toy with it....
cbissa18 said:
yeah not sure why, its like it doesnt stick smh. but it does you just have to toy with it....
Click to expand...
Click to collapse
Well with the corrupt screen, it seems that the time frame that would allow you into Recover/TWRP is shorted. So pulling the battery after trying usually gave me more than enough time to boot into it. Probably not the best for the phone though xD
Hi all,
I was wondering what anyone can tell me about the problem I've got with my Le Eco Le Pro 3 phone. So, I had access to the phone before I jammed both the volume up and down buttons, which caused me to go into fastboot mode. Initially I would get the trusty ole platform tools and just "fastboot continue" the phone into the regular boot. It worked the first time, but I guess the volume down button was still jammed and I got myself into a little bit of a loop. Now, instead of going into fastboot mode, I go straight into Recovery Mode, which I've had to translate because it was in Chinese. The two options I have in recovery mode are to "clear data and do a factory reset" or "install an update.zip". Now, I instead opted to exit out of Recovery mode by pressing the bottom left option, but it just boots back into Recovery mode. I haven't rooted the phone and I have no usb debugging enabled because the issue sort of popped up outta nowhere. Initially, I probably should have just backed up all the data on the device and not had to go through any troubles, but that's why I'm making this post. I would also like to further note that I do have a lockscreen code, so if that "encrypts" the data (making it harder to get to, I guess) is my only guess.
I read on another thread where I can essentially unlock the bootloader through fastboot mode and then be able to enable USB debugging that way and maybe manually remove the files from my phone and just factory reset it to see if I can get the phone running. I also looked into just straight up factory resetting it, but I would probably have to root it before I do so that I can run a third party tool to get the data after the reset. I'm also quite new to this whole issue but I'm stressed and straight out of options.
I would also like to note that there was a blue light when I had tried starting the phone on the upper right hand corner where it would indicate the battery level. The whole recovery boot loop could have been caused by a battery malfunction, but I do get a response from the device in fastboot mode (so I think the phone is not entirely dead). It also charged up to 100% without issue.
Basically, I just wanted to see what anybody had to say about my problem and if you all have any advice (like how do I backup a phone that is not rooted).
Many thanks in advance.
I've also posted an image with the recovery mode
{
"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"
}
help please
polarbearpole said:
help please
Click to expand...
Click to collapse
Did you try to fastboot boot TWRP?
Sent from my ONEPLUS A6010 using Tapatalk
The phone doesn't have TWRP and has stock ROM. Installing TWRP would require me to OEM unlock it and then flash the current bootloader (thus replacing the original recovery boot). Unless I'm completely wrong and there is a way to install TWRP without losing the data on the phone, then I would love to be enlightened because I'm at my wits end.
I tried charging it to 100% and restarting it but it just leads me to the recovery screen. I'm not entirely sure if the phone volume buttons are still jammed, because that could still be the case.
polarbearpole said:
The phone doesn't have TWRP and has stock ROM. Installing TWRP would require me to OEM unlock it and then flash the current bootloader (thus replacing the original recovery boot). Unless I'm completely wrong and there is a way to install TWRP without losing the data on the phone, then I would love to be enlightened because I'm at my wits end.
I tried charging it to 100% and restarting it but it just leads me to the recovery screen. I'm not entirely sure if the phone volume buttons are still jammed, because that could still be the case.
Click to expand...
Click to collapse
Fix the buttons the phone should boot
Sent from my ONEPLUS A6010 using Tapatalk
Alrighty, so a little update. I got the phone's buttons removed but it still boots into the recovery mode. The metal button on the side was removed but the button module remains. It's just not jammed any longer, which now begs the question: Why is it still booting in Recovery mode? I am currently charging it to 100% to see maybe it could be bugged with the battery, but that is the update so far. Button module is no longer jammed but we are still booting into the Recovery mode.
Any suggestions would definitely help in my 2 month long battle with this phone.
Btw, I also replaced the screen because the repairman who removed the buttons broke the original one and the new screen responds to all touch.