[Q] stuck in boot loop with LG mytouch e739 - Android Q&A, Help & Troubleshooting

I installed cyanogen mod 9 on my lg e739 and it installed great except Google apps were missing. I made a backup restore file before I did anything and I was going to restore back to the stock ROM and when it finished installing it acted like it was going to boot normal cause I saw the LG screen come up but ever since then the lg screen is the only thing that shows when it starts up. I've tried everything that I have read online and nothing has worked. I'm can't get back into clock work recovery nor will the phone start its restore process from holding the back and menu buttons. It will go into s/w upgrading mode, but my computer doesn't recognize it in this mode. If I try starting it normally and then plug in the USB my computer does recognize it although it is not mounted so I can't access the sd card or memory. Is there anything I can do or try and is there any programs or command prompt commands that would automatically mount my phone. ...what should I do? Any ideas I would greatly appreciate cause I'm at a loss right now

This situation is more like a BRICK than a Boot loop.
Sent from My Premium Calculator HD

Related

My htc hero is dead

Hi everyone,
Yesterday I made a Radio update to version 63.18.55.06_6.35.07.08. I made it putting the update.zip (radio rom) file in the SD Card.
All worked fine until the htc hero restarted (after appears the box with the orange arrow). Thereafter the Hero only shows the Hero logo when I turn on.
I tried to init the fastboot pressing home+power and home+back+power buttons (without SD Card and without SIM card) but always the result is the same, the logo appears and nothing happens.
The computer doesn't detects the Hero's USB connection and I can't run adb commands because it raises the "device not found" error.
Someone can help me?
Thanks in advance!
Did you let the screen with the box run its course?
Did the recovery console come back up saying formatting cache?
Have you tryed holding just back+power? ive never heard of using back+home+power
And also, i think your supposed to enter recovery with the sd in.
If that works then in that state is should be found by adb.
But yes, as the poster before me said, it should show the "unpacking" image, and then it should reboot. It should then go straight back into the recovery and the recovery will format the cache. If you tryed to turn it off at any point then, then something is badly mucked up. But it isnt bricked, and probably can be saved. Its only bricked when no logos at all come up on boot. If you managed to get it reconised by adb, you could probs format the cache manualy, though i dont know the command
All the previous steps after the breack are as you say, but after the "unpacking" image, the htc hero restarted and showed the hero logo instead the correct menu.
The problem with the adb is that the computer doesn't recognize the htc hero across usb. When I write the adb command ("adb devices") doesn't displays any device, and I can't run any adb shell for the same reason. How can I run any adb command if the device isn't recognized by the computer?
Have you tryed just taking the battery out, waiting 30 seconds, putting it back in, then booting the phone holding back+power?
And adb is very strange i find... Sometimes it reconises a phone, sometimes it doesnt, for no apparent reason. Have you tryed leaving it on the hero logo for a while then running adb commands?
If he has flashed, wouldnt the USB Debugging setting be reset also, wouldnt this be why he cannot access via adb.
Hi.
I habe exactly the same problem. I have updated radion.
Now ther come only the T-Mobile Logo and that's all.
I can not enter neither Recovery Mode nor fasbtoot does do something.
Any suggestions?
Lado
this problem shud be fixed asap because i think its a threat for all hero modders and owners as our phones get killed at anytime with this process. so guys lets try to find a solution for this problem. cheers
Updated Radio to 63.18.55.06JU_6.35.09.26 and it killed my hero.
first the box with the orange arrow came up and then the whole phone died... now it wont even turn on the screen.
please fix?????????????????
I had the box with the orange arrow yesterday after flashing radio.
The phone isn't dead, I think it's just working.
I kinda paniced also when it happend but I got into recovery eventually.
When you flash a radio it does not actually install that image until your first boot (when you see that phone out the box image).
At this point DO NOT DO ANYTHING WITH THE PHONE just wait and it will install the image and reboot for you. IT CAN TAKE UP TO 10 MINUTES.
If you turn it off or otherwise interrupt this process it can really mess up your phone. however the general rule is so long as you can see the HTC logo when you turn on i.e. it still turns on you can in theory always recover, its just a matter of finding the way that works.

[Q] Recovery & Flashboot issues. help is appreciated [SOLVED]

First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?

[Q] Boot Hangs Up on Viewsonic Screen

I ran Cyanogen7 for about two days after rooting, and then the Gtablet froze. When I rebooted, it hangs on the Viewsonic bird screen. I seem unable to turn off, but when I try and reboot with either the pwr + or pwr - button, I'm unable to get anything to happen other than go back to the viewsonic screen with birds. I tried connecting via usb, but can't see the internal SDCARD. Please help, the gtablet is currently only useful as a flashlight using the viewsonic screen. Thx.
nv flash it back to stock rom and try putting rom on again. and clean factory data before new rom boots up or else it will hang.
I'm a novice just knowing enough to be dangerous. How do I NV flash it back to stock ROM when I can't get it to boot and I can access the internal SD with USB?

[Q] DOPO d7020 stuck in loop with mysterious issues

I bought this tablet exactly a year ago, never modified or rooted it, and suddenly a lot of apps started having issues. Went to reinsall a few of them then suddenly the whole OS froze.
Rebooted and the Dopo splash would show, then the android logo showing movement like it is trying to boot but gets stuck there.
Tried going into recovery by holding the power and volume button, that *worked* but when selecting factory reset then it crashed again.
So I repeated the process and now it won't even boot into recovery using the power and volume button!
Tried running the battery dead and restarting, tried using the reset button pinhole. Nothing worked.
I installed adb and fastboot (I use linux) and went through most of the simpler procedures.
adb connects and I can run its shell and view my files that are on the tablets. Ran the command to see its debugging output and noticed that the boot loop was because the filesystem turned everything except userspace to read-only!
Now here is what is real odd.. when I try pushing a file onto the tablet using adb, it instantly becomes corrupted when reading it back.
Like if I make a simple text file called hello.txt with some text in it saying "Hi there!", when I push that file onto the tablet, then read its contents it is gibberish.
This leads me to believe the whole filesystem somehow became corrupted and can no longer write files properly.
There doesn't seem to be a way to run fsck or anything alike and I can not put any files on the tablet because they instantly become garbled.
No use in running fastboot when the tablet no longer can go into the recovery screen either by vol+power pressing or by adb reboot recovery. Both simply just try to boot the tablet normally now, unlike the first time I tried
Assuming I have the factory .img file is there any way I can fix this?
Or does this sound like the hardware got damaged?
I fear the worst at this point.

[Q] HELP: Stuck at splash screen (Soft or Hard brick??)

This is going to be a little long, but I figured the more info the better. I recieved a TF201 from a friend of mine. He already had it rooted and running a custom ROM. It was loaded down with a bunch of stuff so I attempted a factory restore through CWM so I could start over and customize to my liking. Everything went fine (or so I thought) It booted back up to stock interface and still had root intact. I downloaded Astro FM from Play Store just to have a look around and make sure everything was intact. Everything seemed normal but suddenly rebooted and stuck at splash screen. Im able to boot into recovery still so first thing I tried was loading a backup as there were about 6 of them in the list of backups. None of them work, I just get "No files found" error. Next I tried to reload stock ROM with the Install zip from SD option. Also getting no files found error. somehow the SD card has nothing on it anymore even after copying a zip of the stock ROM downloaded from ASUS. The only other thing I can do that I know of is instead of loading recovery, is go into the cold boot menu with the 3 icons in the middle of the screen. By pressing nothing, it says that it is cold-booting Linux. This process just hangs and nothing happens. It does attempt to install MTP device drivers (which were already previously installed) but ends in an error (Failed). Selecting the middle option gives me "Starting Fastboot USB download protocol" but this also hangs and does nothing. Lastly the "Wipe Data" option completes it process and says "Wipe-Data done" but then also hangs and does nothing. At this point Im assuming its Hard Bricked and nothing can be done but I just wanted to see if anyone would be able to help. I have read a lot of similar posts on here but haven't been able to find anything that helps. Most other people with similar problems at least have a way to install from SD but my device wont recognize anything on the card. Does anyone know of anyway to fix this??

Categories

Resources