This morning I flashed last nights CM12.1 Nightly. After it finished I hit reboot and let it do its thing for awhile, only to come back to a blank screen, I rebooted thinking I'd just hop into safestrap, flash a recovery, and be back to normal, but for God knows why, it wasn't letting me get into safestrap.
The next logical step was to run it through unbricking procedure which since RSDlite doesn't like me I have a batch file setup to run it through the manual commands which worked at first, but then I found myself sitting at the stock boot animation for an extended period of time. Not being sure of how long this normally takes because I haven't had to unbrick this phone in awhile, I just let it go.
Realized it was stuck, and decided I'd run through manually and see how that went. Went through the commands, got a couple errors for a low battery but just running the command again seemed to get it through, then I finished, told it to reboot, and then it went right ****ing back into AP Fastboot, saying that there was a boot failure and that cdrom and system weren't flashed correctly. No big deal right? So I go back to run the commands to flash them all again, and now the battery level has completely made me it's new *****.
I have no money to purchase a factory cable, but I feel that if given instructions I could handle it myself. I've seen that the RAZR has a way to get around the low battery level but it didn't seem to work on the Bionic. SO, if anyone has any words of advice, instructions, or methods they want me to try, any and all help would be greatly appreciated. :good:
I know this won't be helpful, but I ran into the same problem. The only solution I found was to use a different battery.
Keep searching around...i found a work-around, but I couldn't tell you exactly where. It involved using an extra usb cable, splicing, and 'straight wiring' the battery. It worked for me is all I can say.
Sent from my HTC6500LVW using Tapatalk
Luckily only cdrom and system didn't flash properly, simply by plugging the USB into AC power first was able to trick the phone into thinking the battery was fine. I was able to get those flashed and it booted just fine.
Related
Hi everyone,
I have a problematic Nexus One. I've googled the issue and read all the corresponding threads and none of them seem to have boot loop issues as bad as mine. At least I dont think so, anyway.
Where should I start? I recently bought the phone off ebay. The seller did clearly state the phone's issues and that he couldn't be bothered fixing it, let alone paying over $200 to send it back to Google to be repaired or replaced (from Australia). Call me a sucker for punishment, but I do like dabbling in electronics so I thought I'd give this a go and hopefully will be successful. It wouldn't bother me if it rebooted once every few days then rebooted again normally but this isn't the case. I'll try to describe it's behaviour as precisely as I an and I sincerely hope the collective expertise on this forum will be able to help me successfully resolve this issue. BTW, I've been using a gorgeous Desire since July.
The Nexus one is running Modaco r21, 4.06.00.12_7 radio, 2.6.32.9 kernel, CMR 2.5.1.0.
1. When the phone has been powered down for at least 5 mins, it will power up as normal. If left alone on the bench or very lightly used ie a few minutes, then pwr button sleep, no problem. If I continue 'sleeping' the phone every few minutes while using it it continues to function normally for a few hours. If I don't 'sleep' the phone and use it continuously, then after about 20 mins it goes into a reboot cycle with the static 'X' going on and off every few seconds then ending up with the continuously on "X" with the unlocked padlock underneath, which is unrecoverable until the battery is pulled.
2. Battery reinserted immediately after removal and the reboot cycle continues. I can boot into the white Recovery or Fastboot sreens but when I select an action like Recovery, the boot loops starts again. Battery pulled and reinserted again, boot loop occurs again. Pull battery and leave it out or powered down with battery inserted for 5 mins, reboots normally. Then point '1' above continues.
3. I have Rom Manager, Titanium and Superuser Permissions installed. I received the phone with Eclair installed and after many attempts managed to install the new radio and Modaco R21. Last night I tried doing a back up via Rom Manager since I cant get into the black Recovery screen and now Titanium and SU are force closing.
This is all I can think of right now and will update with more info as they come to light. I've been trying to install setcpu to see if underclocking will help however I have been unsuccessful due to SU force closing. I am an Android and Linux noob but am always willing to learn. I really would like to get more stability in this phone so I can either use it as my primary or back up.
Thanks in advance for all your help.
Edit. I magaed to do a factory reset when it dont momentarily allow me into Recovery mode. Wiped all data and davlic as well.
My first instinct is that the phone has suffered or is suffering from a heat problem of some type.
Do you have the android SDK set up on your computer? You should be able to flash an aftermarket recovery using the "fastboot flash" commands. You could also use the "adb reboot recovery" command to reboot the phone directly into recovery mode.
I'll give your suggestions a try. What fastboot commands should I be entering? I am an absolute virgin with all this.
Sent from my HTC Desire using XDA App
I think this thread should have some good information for you
Thanks for the link, mate. I'll have a read and I'm sure there'll be more Q's soon.
Sent from my HTC Desire using XDA App
Hi again,
I've installed Android SDK and usb drivers. Where do I go from there? I am a complete newbie at this so please be kind.
julian.kueh i was posting to ask how things have been progressing along this matter?
I got the same problem. No matter what I do, I can get into Recovery. It stay in loop with X
I change twice recover and nothing.
Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks
just a little baby sized pump...
This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?
Do you have a link for the method you described about? That would be really helpful!
An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.
And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.
I'm tring to use RSDlite from a virtualbox vm, but its going really, really slow. I'm some 40 minutes in and its only on step 6 - I don't think it will complete before the battery goes dead.
If I cancel it now and do all the fastboot flashing by hand through my host os, will I screw anything up?
vonwhoopass said:
I'm tring to use RSDlite from a virtualbox vm, but its going really, really slow. I'm some 40 minutes in and its only on step 6 - I don't think it will complete before the battery goes dead.
If I cancel it now and do all the fastboot flashing by hand through my host os, will I screw anything up?
Click to expand...
Click to collapse
its never safe to stop a flashing process. Depending on when you stop it you could royally screw your phone up. Certain files can get corrupted that won't allow you to enter fastboot mode anymore (im not aware of exactly which those are but i think there are many). It shouldn't take that long to flash your phone so im not sure what the problem is. If it has been stuck on the same step forever then maybe it has failed or something. You def don't want your phone battery to go dead because there may be no way to charge it again if there is no bootable rom on there. I believe fastboot may still allow your phone to charge but Im not sure if thats true. I know it didn't used to be able to but i think it may now. Personally, i would stop the rsdlite process before i let the phone battery drain. Then hopefully your phone will fully boot from there and i would charge it to 100% before trying to flash it again.
If my memory is correct then step 6 is the system.img file - the main OS of the phone. It is the big file that will not only take the longest but it is also the one that will fail the easiest as it is so big. On an older XP machine it takes 5 minutes or so to transfer/flash that file.
I have had the process hang during the transfer of the system.img file before. One time I had to reboot my computer and I rebooted the phone. This will leave the phone unable to boot but with enough key presses you can get into fastboot still - I don't recommend this!
When it happened a second time I only rebooted the computer, and not the phone. You can start the flashing process again without restarting the phone unless it has crashed. You should be able to manually flash with fastboot starting with the step that that failed.
I did some googling - it looks like VirtualBox has some problems with USB speed in Windows XP as a guest.
I ended up killing the RSD flash, and doing it by hand, which went way, way faster. I was able to flash the whole thing in the time it took to send the first 2 files, which only adds up to 1.7 meg.
For what its worth, I killed the flash during step 6, which is system, you are correct. I think this may have actually saved me since it had the boot and recovery images already.
edit: and it appears the phones do charge in fastboot. I had more charge when it rebooted after the successful flash than I started with.
Good to hear you got it working. And yes, the phone should (slowly) charge when in fastboot.
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
SantiagoEB24 said:
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
Click to expand...
Click to collapse
Flash system.img and boot.img then flash twrp.img and boot into twrp and flash your stock ROM for your device