Related
Been having a lot of trouble flashing new roms. Curently running tazz froyo v1.0. Have been able to root, flash many different types of roms (2.1, froyo etc)
But lately been wanting to try out Nonsensikal v4.6 but for some reason cannot get it to load. It'll either get stuck onthe white screen or if it does make it past the boot freezes during the boot animation and will remain stuck for a long time. Have let it go for 30-40 minutes. Batt pull, both wipes reflash and same thing.
So it has to be corrupted downloads. Tried on different computers, same results. Reformatted my card (was already no partitions, fat32 for froyo).
I would like to figure this out as i really want to try nonsensikal ( ran v 3.4 and loved it)
Any ideas? Battery is always fully charged when flashing. Sd card is good.
Maybe it's a computer issue?
Appreciate any responses.
Thannks
Stephen,
Thanks for the input. No setcpu for me anymore. Its only phone but never activated. I can flash other roms. It's just certain ones won't finish booting.
I'll have to verify the md5s and focus on the corrupted download issue.
Thanks again.
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
You did wipe. My mistake.
bftb0 said:
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
Click to expand...
Click to collapse
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Jp50 said:
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Click to expand...
Click to collapse
Let me know if you have tried booting it without the SD card in the phone (the first time you try booting it). If you already said you did that and I missed it, then my apologies.
Some dev ROMs (not all of them) have "USB debugging" enabled in their boot scripts (some don't), so you can sometimes detect what the problem is using logcat. Maybe you do the "wipe-flash-boot without SD card" experiment and at the same time do this:
- Turn phone off
- Plug it in to the PC and bring up a command window
- in the PC, enter the command
Code:
adb wait-for-device logcat > logcat_boot.txt
The command prompt will not return - it will just sit there, waiting for the phone to start up. So, then:
- boot the phone.
Let the phone sit, even if you think it is going in to a boot loop. The "adb" command will also just sit there until you interrupt it. Wait for 10 minutes if necessary.
Hit Ctrl-C in the PC Command window. You should see the command prompt return.
If the phone booted successfully, then you can just delete the "logcat_boot.txt" file.
If the "logcat_boot.txt" file is zero length, that means that the dev did not enable the "adbd" service on bootup, so this particular technique is of no value.
If the phone went into a bootloop and you have a big "logcat_boot.txt" file, I will probably suggest you post it up to a pastebin somewhere (e.g. http://pastebin.com/ ) so we can look at it.
bftb0
ran the logcat test and it returned nothing. phone still won't boot nonsensikal. just freezes on the white screen. battery pull, reboot now its in boot loop city.
i think i've wasted enough time on this rom. I'm running cyanogen Tazz v2.0 and I was able to flash it over v 1.0 with no issues (other than the camera).
I guess nonsensikal rom doesn't like my phone. the dev was a lot of help, but i think the issue is my phone is just ****ed. I can't overclock anything over 604 without it freezing.
Time to move on and get back to having a real life and not obsessing over a phones interface. tazz's rom is more than good enough and I just have to move on. The amount of time I wasted on this is just silly. This phone took over my life and I have to lick my wounds and admit defeat.
thanks for all your help everyone. not all phones are created equal.
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
GOT IT!!!!!!!!!!!!!!!!!!
plymouthrock99 said:
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
Click to expand...
Click to collapse
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee! pdanet.co
plymouthrock99 said:
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee!
Click to expand...
Click to collapse
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
I have one as well and was able to root it with the latest bin4ry tool! Hopefully Blu will enhance their customer support as they gain more popularity and release some source code or dev tools for the phone. Or at least, since it's rooted, the device can eventually gain support from any devs.
Kah,
Can you post root instructions for us, please?
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Any Information posted in this thread is Great!
I don't mind taking this off track of what the original thread. I like it that it is progressing the way it is, helps me out with other questions and anyone else that starts off with my problem probably wants additional information on what else could be done with these phones.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Average
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
plymouthrock99 said:
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
Click to expand...
Click to collapse
Try using Mounts2SD..
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
j21blackjack said:
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
Click to expand...
Click to collapse
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
kah1593 said:
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
Click to expand...
Click to collapse
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
j21blackjack said:
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
Click to expand...
Click to collapse
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
kah1593 said:
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
Click to expand...
Click to collapse
Hold volume up and power until it turns on. As soon as the screen changes to green, I let go of the power button and keep holding the volume up button until it's in recovery mode. It seems the power button release has to be timed right or else it just sits on the green screen, or powers off again. It takes a couple of tries for me. I probably did 10 factory resets last night before finally getting it rooted, lol. The built in recovery has an option to flash from external storage, kind of makes me wonder how easy this phone would be to get CWM working. Of course, the real problem is getting developers to write the custom ROMs for it. The only thing this $230 phone is missing from its $600 cousins is 4G LTE, but on Tmobile it doesn't even matter right now. It's still blazing fast even on stock with no overclock, I can't imagine how much more awesome it would be with a custom rom.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Can anyone post a link of where I'll find the proper drivers? It just shows BLU with an exclamation in my Device Manager. The PDANET trick did not work as it won't detect the device. - and if I can get this working, I'll post an actual tutorial for it.
If anyone could post an update.zip of the original rom that would be fantastic. - and clockwork 6 will run on our devices with some work. but right now, mine is a brick, it still has recovery but the stock rom is effed.
I'm in the same situation. I deleted my contacts.apk in hopes of replacing it with a stock version, now it's stuck in a boot loop, and factory reset doesn't help.
Alright guys, I hit the jackpot. I have CM 10.1 working on my Quattro 4.5. It all began when I read somewhere on the xda forums that the Quattro 4.5 and k-touch v9 are essential the same phone. I said before, my phone was bricked so I figured I do some more research and see what I could do. Turns out that person as right. I found a website ( http://www.needrom.com/phone-roms/k-touch/k-touch-v9/ ) that has 3 roms for the v9, CM 10.1, MIUI 3.4.5, and CM 10, and instructions to install them. I decided to take a leap of faith and follow the directions given for CM 10.1. The installation directions for custom recovery CWM 6.0.1.1 worked perfectly - only problem is after you've installed the recovery, the menus are in Chinese.
Once again, My phone was bricked and essentially completely erased. If your phone isn't bricked, it should be fine as long as you do a factory reset before. I would suggest doing this before installing the CWM recovery because I have no clue how to do the reset using the Chinese menu.
I downloaded the CM 10.1 rom from the website above and gapps for 4.2.2 as well (you can find this with google). If you're using one of the other roms, obviously make sure you're using the proper gapps version.
ADB works while in recovery so use this to push the zips to the phone. I say this because I've discovered the sd card directory changes depending if your phone is bricked or not (i.e. /emmc vs /sdcard).
Flash the rom zip, then gapps - select the 2nd option in the main menu then in the following menu, the 4th option. This should lead you to the directory containing your zip files. Choose the appropriate one, and let the CWM work its magic. ( also from messing around I can also tell you the first option in the main menu is to reboot)
Once you've reboot, everything should work perfectly - WIFI, bluetooth, brightness, camera, video recording, audio, microphone, not a single problem except the volume being much louder than before. It's amazing. I have straighttalk's $30 plan, so I'm still stuck with a dumbphone until I bump up to the unlimited everything at the end of the cycle, so I can't test the phone radio, but I would expect it to work considering everything else does as well. Let me know if I left something out. I would test the other roms, but I'm so happy and content with my phone working again, I don't want to go through the effort just yet.
I found a way to create an English recovery that works from the Chinese version. Just replace the recovery.img provided with this one. Here's the link: https://www.dropbox.com/s/5y6r9gvspvouhbo/recovery.img I don't think this should cause any issues because it hasn't for me, but remember you are using this at your own risk. Though if an issue does arise, I'll try my best to help.
Install with English Recovery?
Did you install with the English recovery, because I am stuck at CM10.1 boot screen installing with the English recovery.
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh: