[p1-backstory][p2-problem][p3-symptoms][p4-cause][p5-question]
links have been removed due to forum restrictions, to see the post with links at:
connordoherty.blogspot.com/2013/03/xda-post-q-nexus-boot-shows-up-on-xt912.html
I recently got a secondhand Verizon Motorola Droid Razr XT912, intending to unlock it and use it with my t-mobile account. Coming from iPhone, I've never used android before so i took a few weeks to grow accustomed to the stock OS before rooting it. I learned it, and eventually, although it took several days, I also rooted it.
But today, when I attempt to boot the device, i see this glowing X logo, which my friend thinks might be the nexus logo (bootloader?), forever.
Never goes anywhere, just stays on X. I can only reboot it by holding power+volume down which makes it again boot to the X. I'm not sure if this is considered a boot loop - seeing as it doesn't actually loop, just hangs endlessly. It seems my only way of shutting the device off (power button does nothing) is to enter the boot selection menu (Vol up+down at startup) and choose the "AP fastboot" option and in that mode i can power down with a tap of the power button. all the other options bring me to the X, except recovery, an ill-android-logo-with-exclamation-point.
How did I get to this point? I tried to flash a ROM to replace the stock Motorola Android - trying first AOKP: First I backed up using myBackup, then I chose the link for "spyder" at the download list and followed a guide telling me to download this app and I did, but a different guide told me I would need CWM so i got that too. I didn't know how to add anything from within the app so i reboot to get too the boot menu, and chose the AOKP zip file - which worked for a bit but proceeded no further after "Booting...". I tried several times and messed around with the menu but I thought maybe I needed CWM so I chose that zip and it didn't work either.
Has anyone been in a similar situation? It sure seem like I bricked it. I discovered Recovery Mode has a hidden menu when you press the volume buttons, but choosing "install update from external storage (SD card)" then it fails as in valid for every zip I have tried. I thought maybe it needed to be signed or official so i downloaded what i found to be the stock update Blur_Version.6.16.211.XT912.Verizon.en.US.zip and that was accepted but eventually failed as well. The factory reset option there does nothing. I tried using the Fastboot method as well but it never finishes without stopping, on 6/18 or 2/18 or anything for a different reason each time.
What haven't I tried?
Related
I'll put the question first for those not wanting to read the details.
I cannot get into CWM (internal) on my 16GB nook tablet. I can boot to CWM (external), but nothing works. When I try to activate ANY menu option, it takes me to a blank screen with the CWM hat logo in the background. Pressing power returns me to the main menu. Not even "reboot device" works. Can someone help? (I want to do a backup before i flash a JB Rom (internal), and to flash a JB Rom)
Now the long part:
I purchased and rooted my NT in December 2011 (about the 21st) using the snowball root (incase you are not familiar, as I don't see any post about it now, it was a modified zerg root borrowed from Albert's root method that with one menu option allowed rooting, recovery, and removal of certain nook apps and the addition of your choice of three launchers). I used it successfully on three nooks within a month or so, but this is the only one I did the complete nook removal option to.
Root works fine, but debug does not. When I run the NT hidden settings app to turn on debug mode, the developer options are listed twice (one compete set followed by another), this did not happen until after rooting, before they were only listed once. The bottom set was correctly checked to allow debug mode, and its how I rooted; however titanium backup says debug is not enabled every time I load it. (No complaints from RTB Pro) So I go into the developer settings and found two sets, the top one not checked... When I check it I get the pop-up warning, if I uncheck the bottom one, then debug does not work, if I check the bottom one I don't get the pop-up warning. With both checked, adb works, otherwise it does not. It had been this was since December 2011, and has not really prevented me from doing anything, although as the pop-up warns somethings may not work (converting apps to/from system, merging system app updates, restoring system app backups) and cause titanium to hang, but after a manual force close of titanium, most of the time the change was successfully completed.
Now, moving on one day I was being up my phone and thought "I can't remember the last time I did a nandroid of my nook" so I used RTB to reboot into recovery, the nook booted right back up into android, no errors, no different screen than a normal boot (with the nook --> hack logo, which incidentally takes about 12 minutes to boot every time, not sure if that is normal). So I tried an adb reboot recovery, but adb said no devices were attached. I went back into NT hidden settings and due enough debug was unchecked on the top, but still checked on the bottom (I've learned it lose it every reboot), do I rechecked it, got the pop-up, and went on my way. Adb reboot recovery also restarted my nook back into the OS, not into CWM.
I started to think that I may never have installed CWM, so I checked the root package I downloaded and viewed the script, first thing it does its copy the recovery image to the device, even before rooting, then installs it right after rebooting, post root hack. I thought maybe the posh was bad flash, so I searched XDA, downloaded a newer CWM, and manually adb pushed it to the phone and dd it per the instructions in the XDA thread. Reboot recovery, still nothing.
Please note I CAN get the factory reset screen to show up, but really don't want to try it without a backup, as I've been using my nook like this for 12 months and only have a titanium backup of the apps.
So I made a CWM SD from the NT thread here on XDA and booted to it :-/ intending on flashing 6.0.12 CWM to the internal emmc, the recovery on the SD was 5 something and none of the menu options worked, as mentioned above pressing power while any are selected gives a new screen with the background image, but no options. Pressing power again takes me to the main screen (same thing when selecting reboot device).
So I found a newer CWM SD package on XDA and swapped them out, this time a newer version 5.5.x, no change in how it works, so downloaded 6.0.12 and renamed the recovery image file and booted the SD. Small change this time (beyond the new version number and the option to power off, which also does nothing), when pressing the power button to select a menu option, the screen refreshes, but continues to display the same menu choices for all options in the menu.
I have also tried pushing each of these recovery images to the device and using adb to dd them to the recovery partition. Three nook will only boot the SD clockwork image.
Yes I made sure to select internal images for dd to the nook and external images for the SD.
So last night I installed nook tab recovery flasher, it said it successfully installed, before I clicked yes to allow it root access... the pressed the reboot recovery button, no good. So I downloaded and installed goo manager from the market and had it flash TWRP, same thing, reboot recovery ignores it.
Now to repeat my question, anyone have any clue how I can get recovery working spp I can make a nandroid and flash a JB Rom? (I know I can make a backup using adb, and Iam pulling one now, but I am wanting a recovery (that works) on my nook.)
Also, I am willing to try an adb push install of the Rom, I think I can make it work (although Ihave never tried it, on any device, I might be able to do it without further help), but I do not see how a new Rom will make any difference on my recovery situation and if I screw up, it would be comforting to know I had a working recovery at least.
Sent from my VS920 4G using Tapatalk 2
For selecting an option in recovery is N button not power one
Sent from my Xperia S using my fingers to swype.
Your question belongs in Q&A with all other questions and not in development. Only work being shared belongs there.
Thanks
AvRS
Caught that, and was able to flash CWM 6.1.15 (emmc) from the SD; but still cannot get to it.
Power+ nook= regular boot
Power+ vol up+N= regular boot
Power+ vol up= regular boot
Power+ vol down+N= regular boot
Rom toolbox pro reboot recovery = regular boot
Adb reboot recovery= regular boot
However, using goo manager to reboot recovery works, sort of...
I get the cyanoboot screen, hold N, use the menu to get to emmc internal recovery and I get CWM.
Now the problem starts about 3-7 minutes later (have not tried timing it, but it seems to be the exact same length of time each time), the nook reboots, don't matter what I am doing, using it, creating a nandroid, adb push or adb pull out apparently flashing cm10...
I decided to try a flash of cm 10 from a 11-28 build with multi touch firmware for 10 points. All was good, but I had to step away for about 2 minutes... I sneaked a peek and all was well, then when I got back my nook was on the "read forever" logo and has now been that way for 20 minutes. I checked the updater script in the Rom and it does NOT have a reboot command at the end.
I'll give it another 20 before ring to get back to CWM with out goo manager...
Sent from my VS920 4G using Tapatalk 2
Update
So, no change. Hiding the power button shut it off, I also tried plugging the usb cable in to activate boot, this causes a regular boot, which at this tinge never gets to "nook" but stays on "n" "read forever" which makes me laugh as it is currently the only thing I will "read forever" until I fix it.
Next up is to try to flash from an SD.
Update to my update
Booted from the SD, wiped everything three times, flashed the Rom, rebooted and ended up with TWRP, multi-touch and JB. Reinstalling apps through the market now, hoping previous issues are gone.
I have a problem with one of my Lenovo A830 phones.
I bought it from Etotalk, so it came rooted, and with their custom version of the Lenovo Stock ROM and their custom version of CWM 5.5 installed.
I tried formatting my SD card and then doing a factory data reset from within the operating system. (I was intending to install MIUI V5 after rebooting into recovery).
However, on rebooting, the device is now caught in an infinite boot loop, and I am not able to boot into recovery mode (by holding down power and both volume keys). It loads the initial splash screen, then shows a few seconds of the Android character and some whirring cogs before rebooting.
I am able to boot into Factory mode (power and volume up) or Meta mode (power and volume down). Factory mode has a number of options, but they are all in Chinese characters, which I am unfortunately not able to read.
I did notice that my SD card seemed to be write protected when I tried to format it in my computer and to copy on the new ROM - I solved this by putting it in a different phone and reformatting it. I wonder whether the factory reset process has write protected something it shouldn't have?
Does anyone know how I might best proceed? I've been digging around on the forums, and tried a few things, but there's nothing which seems to provide a coherent solution for this problem.
I've got the latest Android SDK Tools, MTK Droid Tools 2.4.8, SP Flash Tool 3.1312, some additional ADB drivers (120827 v3.7) that I'm not sure how to install, the latest MIUI V5 ROM (3.8.16), and the latest stock Lenovo ROM (S118 from Need A ROM, just in case I need it).
Maybe different SP Flash Tools version?
I had trouble using SP Flash Tools v3.1312 with A830. Once I switched to v3.1304.0.119 I was able to flash both the original ROM and the custom MIUI one without serious issues. I'm unable to post the download link but google it.
One other thing is that when connecting the phone, it usually loads the something something Preloader driver, which is no good (even if it gives you Download OK). When attempting to flash either ROM, try pressing both the power and volume up buttons while connecting the phone (after pressing Download), only way it worked for me.
Good luck!
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
tominglis said:
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
Click to expand...
Click to collapse
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
claudiuionel said:
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
Click to expand...
Click to collapse
Hi I had similar "reboot loop" problem this morning after a phone factory reset.
I have no idea how I solved that but the following was the steps I tried:
1. Install the MTK6589_PdaNET_ADB_VCOM_Drivers. Skip the USB connection during setup. Start the PdaNET after setup finished.
2. Insert battery inside the phone and connect the phone with the computer by USB
In my case, the phone reboot loop once, and the lenovo screen appeared in the second restart. The phone hanged. I unplugged the cable, took out the battery, insert the battery again and start the phone normally again and it is working now.
I recommend installing the recovery rom after you have fixed the phone.
Goodluck
My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?
Is there a rooting section or something? I feel as if this may be in the wrong section (if so, please move it thanks)
So, today, I decided that I wanted to unlock, root, and install a custom ROM on my htc m9. Now, on my previous phone, I only rooted and installed a custom kernal, all of which were apps that I used on my phone to do all the work. for the m9, there are no apps that root the phone for you so I looked up a few tutorials. (I'll list what I did in case you find something I did wrong
list of my guides :
droidviews.com/root-htc-one-m9-marshmallow
.droidviews.com/how-to-root-htc-one-m9-and-install-twrp-recovery-on-it/
and I used htc dev to unlock my phone's bootloader
unlocking my bootloader.
Unlocking my bootloader was successful, when I go into download mode (the black screen to be clear) it says unlocked
installing twrp
There was a lot of issues when installing since all but one of the guides kept saying go into bootloader mode, bootloader mode this, bootloader mode that (which is the white screen). After some searching, I realized that they really meant download mode... two different things... I believe twrp was successfully downloaded since I am able to access twrp when I go into bootloader mode, then recovery mode, and I end up in twrp.
rooting
so, according to the guide, I move the supersu zip files into my internal storage (anywhere). then go into twrp, press install, select the zip file, then swipe to flash.
well, I did just that, however, when I go to turn on my phone, I get stuck on the htc load screen, It's not a boot loop, it's just that white screen that says htc... I can't do anything else. holding down the power button does nothing (even for 10 seconds)... update, after typing this, I get a nice animation, then I'm stuck on the white screen that says htc one...holding the power button again does nothing, power button, and volume down does nothing... I think if I hold the power button and volume up, I turn off the phone, meaning I can access download mode, boot loader mode, etc. So... now what? clearly, following instruction has got me not where (bummer) and my lack of experience has also gotten in trouble (it could be worse? right?) what can I do to fix this?
note: my previous phone, I soft bricked it and I was able to flash the stock rom with LG flash tool, but there's no such thing as htc flash tool...
**The problem as it stands**
My Galaxy S6 Active is stuck in a sort of bootloop, except it never seems to attempt a boot. If it was turning on, without any combination of keys, it would go to the "No Command" screen. From there all I can do is force reset (power + volume down) to get it to restart to the same place or as it displays the Samsung splash screen, press volume up + power + home, it goes to the download screen. From the download screen, I can use my pc to flash a rom (that may not be correct) to the device and according to Odin, that is a success but my device freezes on "erasing".
Imgur album with pictures of the accessible screens (http://imgur.com/a/Rd9ND)
**Description of the problem when it was booting**
At seemingly random times, the device would freeze and the only way to get it to do anything was to reset it. Sometimes it would enter a bootloop but through key combinations, I would be able to get it out. One time after a bootloop, I had the sense to back up the device's storage, so luckily I have that.
**What I've done**
- I have tried wiping the storage in device recovery -- when it was accessible, I can no longer get to it.
- I have tried using Kies/Smart Switch emergency software recovery -- but when provided with the model name and serial number they would both crash.
- When the device booted, I tried using the standard recovery feature in Smart Switch. I can't remember the exact message but it was something along the lines of "This device does not support initializing"
- I have tried using Odin to flash ROMs (again, I may be using this incorrectly) to the device. I have only tried Samsung release ROMs, meaning ones that have not been modified by a 3rd party. I followed the second and third methods of a guide on XDA forums (https://forum.xda-developers.com/ga...e/downloading-flashing-att-galaxy-s6-t3260744). Odin never throws an error and it always says it was successful. During the device's initialization with this new ROM, it gets to 32% then goes to "Erasing". A few seconds later the animation freezes. I can leave the device here for hours but nothing happens. So I believe more than the animation is frozen.
- I tried using ADB recovery via the device's recovery mode (when it was accessible) but from what I can gather, Samsung uses a proprietary ADB interface that would not work with what I was trying to do (I was following method 3 of the previously mentioned guide (https://forum.xda-developers.com/ga...e/downloading-flashing-att-galaxy-s6-t3260744). I would always get a message saying "ADB server out of date".
I may have done more than that but that's what I can recall.
Any help would be appreciated. Even if you know of a better place to post this, let me know.
Thanks
My s6 active did the same thing on 08/24/17. I have not yet found a solution.