Database Info

Stuck on red M - Dual Core Logo

Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks

unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good

hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"

Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery

okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?

There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?

llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?

about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...

About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to

i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...

The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.

well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..

The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in

well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)

The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery

http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that

Have u done the lte update?

UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...

Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)

it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

How do I Unbrick? Small twist

Ok so here is the issue. My Nexus S i9020a has a power button that is no longer working. Whenever I put the battery in, it automatically boots up, to reboot I take the battery out and slide back in. I want to bring it back for warranty since my bro got the warranty until 2014 or so. I had previously had a couple of custom ROMs on it. I wanted to flash stock ROM and lock the bootloader.
When I boot into recovery (hold up while I put the battery in), I can't do anything. Even the volume up/down doesn't do anything, and of course pressing the power button doesn't select anything. So I got ROM Manager and found a copy of the stock rom. ROM Manager was supposed to install the rom from the .zip file, which it sort of did. It wiped everything and installed. I left it on while I went to do something. When I came back, the phone is stuck in the bootup animation.
If I was able to do anything in recovery I would just reflash a different ROM and go again.
I have watched some videos, and tried the Oneclick Unbrick, but doesn't work. I've read some other threads here that talked about getting Linux on a USB, or other mod. But I am trying not to go that route, as it seems pretty complicated.
When the phone is in the bootup animation and I connect it to the computer, I hear the sound that Win7 detects new hardware. If I am in the bootloader Win7 does not play any of that sounds.
I remember using adb and I still have the files on my computer from when I unlocked and rooted.
Not sure what should I do now?

also, all of my soft button lights are on during the boot animation. read in one of the threads that different lights on mean different modes. so not sure if this means anything.

hi, I am afraid the bad functioning of power button is responsible of all of these problems,
probably you can send it for warranty as is now
---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------
have you tried already the linux app UnBrickable Resurrector ?
maybe you would be able to install the stock rom via fastboot

Possible fix: Remove all drivers and reinstall via Nexus root toolkit. Go to adb and flash TWRP, or CWM Touch Recovery (make sure it's touch-enabled), then flash a new rom.
Permanent fix: As far as I can remember (I also had this issue about 6 months ago) samsung will still recognize the warranty even when your bootloader is unlocked, at least in my place. The issue you're returning with is a hardware issue, not a software issue. So tell them to just replace the power button and you'll do the rest. As long as the samsung warranty sticker on top of the screw is in-tact, you're good to go. Again, this is my experience in a samsung service center near my place. I don't know how they deal with things elsewhere.

if this can help, I read in forums that also in Italy samsung support fixes nexus s in warranty even with unlocked bootloader, this is not a direct experience though

So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?

eugene188 said:
So I have tried the wugfresh Nexus Root Toolkit and tried installing different drivers. None of them can detect the phone when it is in the bootloader, windows only makes a sound when the phone is trying to boot up.
I've tried the "Flash Stock + Unroot" button but as soon as it tries checking the fastboot it cannot detect anything. The mini description says all it needs it to have the phone in the bootloader, but I can't get it to do anything else.
I have tried the guide at DroidViews (can't post links yet), but in the command prompt, fastboot just keeps waiting for the device again, windows does not detect the phone unless it starts to boot and enters the bootloop.
what do I do now?
Click to expand...
Click to collapse
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.

ej8989 said:
Remove all android/samsung drivers and install PDAnet drivers. PDAnet detects the phone even on bootloader.
Click to expand...
Click to collapse
I just tried the PDAnet, I choose the Samsung drivers, then once it pops up with the screen to ask me to connect the phone then I'm stuck. Whether I put the battery in and let it bootloop or hold vol+ and put the battery in, it doesn't get past the screen. Only thing I could do was "skip USB" which still installed PDAnet but possibly without USB support and just bluetooth support.
I even tried it on my brother's laptop which is still in a relatively clean OEM state but the got stuck at the same place.

Need help getting to stock recovery

Need help...
Was messing the around with the screen density in the buildprop.. after reboot, "systemui keeps FCing" making it unusable and I cant do anything. Attempting to do a hard button combo to go into stock recovery but cant seems to get it to work.. Googleing tells me to, hold volume down and power till the LG logo, release power and rehold again.. it just reboots again.. holding all 3 brings me to a korean menu that I cant read.. holding up and power brings me to a recovery menu that I think only the service centre can use, there's no option in there, only asking me to reboot.
Any kind souls please....

scpion said:
Need help...
Was messing the around with the screen density in the buildprop.. after reboot, "systemui keeps FCing" making it unusable and I cant do anything. Attempting to do a hard button combo to go into stock recovery but cant seems to get it to work.. Googleing tells me to, hold volume down and power till the LG logo, release power and rehold again.. it just reboots again.. holding all 3 brings me to a korean menu that I cant read.. holding up and power brings me to a recovery menu that I think only the service centre can use, there's no option in there, only asking me to reboot.
Any kind souls please....
Click to expand...
Click to collapse
I've been trying to get into my stock recovery for some time now trying all sorts of button combos but to no avail. Previously I had the g2 and when it updated from jellybean to kitkat, the combo for entering stock recovery changed however, this new combo doesn't seem to work on the G Pro 2 either
You should be able to revive your device back to stock using the LG pc Suite however, after tampering with the system, it is often necessary to perform a factory reset after the pc suite has done it's work which will need you to enter stock recovery.
If you are completely stuck, I would suggest restoring your device using the pc suit and, all being well, your device will boot sufficiently for you to perform a reset through the phone settings menu. If you are really lucky, it may boot properly and you may not need to perform any reset however, it would still probably be a good idea to do so.

bobsie41 said:
I've been trying to get into my stock recovery for some time now trying all sorts of button combos but to no avail. Previously I had the g2 and when it updated from jellybean to kitkat, the combo for entering stock recovery changed however, this new combo doesn't seem to work on the G Pro 2 either
You should be able to revive your device back to stock using the LG pc Suite however, after tampering with the system, it is often necessary to perform a factory reset after the pc suite has done it's work which will need you to enter stock recovery.
If you are completely stuck, I would suggest restoring your device using the pc suit and, all being well, your device will boot sufficiently for you to perform a reset through the phone settings menu. If you are really lucky, it may boot properly and you may not need to perform any reset however, it would still probably be a good idea to do so.
Click to expand...
Click to collapse
I cant use the LG Suite... the screen doesnt allow me to choose the connection type.. It just FC constantly.. I am screwed..:crying::crying:

scpion said:
I cant use the LG Suite... the screen doesnt allow me to choose the connection type.. It just FC constantly.. I am screwed..:crying::crying:
Click to expand...
Click to collapse
Think the only option is to send it in officially and say I dun know what happened......

Help
Has anybody found the way to hard-reset D838 from a bootloop? I really cant reach the recovery mode

manas.neo said:
Has anybody found the way to hard-reset D838 from a bootloop? I really cant reach the recovery mode
Click to expand...
Click to collapse
I had tried everything.. Even adb command to reboot into recovery. It just brings me to a broken Android with red triangle. I am starting to think there is no stock recovery built in that is accessible to users..

I am now at the service centre. Well the guy can detect that its rooted.. voids warranty.... But will try to see if he can help to reflash the firmware.. If not have to change hardware and will be chargeable....... Fingers crossed. He did say users are not able to access the recovery..
Guys.. Until there's custom recovery, pls dun mess with it.....

That is really bad. I am stuck at bootloop and unable to reach the recovery mode. I wonder how entire web just talks about a hardreset process that doesnt even work
scpion said:
I had tried everything.. Even adb command to reboot into recovery. It just brings me to a broken Android with red triangle. I am starting to think there is no stock recovery built in that is accessible to users..
Click to expand...
Click to collapse

manas.neo said:
That is really bad. I am stuck at bootloop and unable to reach the recovery mode. I wonder how entire web just talks about a hardreset process that doesnt even work
Click to expand...
Click to collapse
I know.. I was desperate too... There's 2 versions, the other model is f350 or something.. Anyway at the service he did flash the phone again for me foc. BUT! He stamp a big NO WARRANTY as well... Goodbye to my balance 10 months warranty.. Buy hey.. I am grateful that I have my phone working again..I think.
I confirm with him again.. Yes, there is no stock recovery users can access....

scpion said:
I know.. I was desperate too... There's 2 versions, the other model is f350 or something.. Anyway at the service he did flash the phone again for me foc. BUT! He stamp a big NO WARRANTY as well... Goodbye to my balance 10 months warranty.. Buy hey.. I am grateful that I have my phone working again..I think.
I confirm with him again.. Yes, there is no stock recovery users can access....
Click to expand...
Click to collapse
Glad you were able to get your phone back. I have some positive news. I am trying out a recovery method as we speak. Using the LG Software update & USB driver tool I found the option for a update recovery. So I gave the IMEI and it prompted for a connection to the device which wasnt there as the phone is stuck in a boot loop. So I thought if it is going to restore the firmware from PC ( and not OTA) then it at some point of time will take the phone to download mode. So I just put the phone in download mode and VOILA it recognised the connection. And right now it is downloading the recovery firmware. The firmware being downloaded is around 1.5GB which is exactly what size I expected it to be. I have my fingers crossed. Just hope it goes through fine.

manas.neo said:
Glad you were able to get your phone back. I have some positive news. I am trying out a recovery method as we speak. Using the LG Software update & USB driver tool I found the option for a update recovery. So I gave the IMEI and it prompted for a connection to the device which wasnt there as the phone is stuck in a boot loop. So I thought if it is going to restore the firmware from PC ( and not OTA) then it at some point of time will take the phone to download mode. So I just put the phone in download mode and VOILA it recognised the connection. And right now it is downloading the recovery firmware. The firmware being downloaded is around 1.5GB which is exactly what size I expected it to be. I have my fingers crossed. Just hope it goes through fine.
Click to expand...
Click to collapse
As I mentioned in an earliar post on this thread, you can usually get the device into a booting state using the lg pc suite. You will probably have to perform a factory reset but, hopefully, after using the tool, you can access the software factory reset in the settings menu. From past experience with other lg devices, it can often help if you run the recovery more than once in the pc suite.

bobsie41 said:
As I mentioned in an earliar post on this thread, you can usually get the device into a booting state using the lg pc suite. You will probably have to perform a factory reset but, hopefully, after using the tool, you can access the software factory reset in the settings menu. From past experience with other lg devices, it can often help if you run the recovery more than once in the pc suite.
Click to expand...
Click to collapse
Hi Bob,
Yes I think the same option is there in the LG PC Suite as well. But unless you do what I have tried to do it wont recognise a device that has not booted yet. Devices soft-bricked or bootlooping wont be recognised by the PC suite for recovery. But thanks for the tip. I'd keep that in mind and see if it'd need another factory reset after recovery. But it seems like it will be a hard reset done by the recovery happening right now

manas.neo said:
Hi Bob,
Yes I think the same option is there in the LG PC Suite as well. But unless you do what I have tried to do it wont recognise a device that has not booted yet. Devices soft-bricked or bootlooping wont be recognised by the PC suite for recovery. But thanks for the tip. I'd keep that in mind and see if it'd need another factory reset after recovery. But it seems like it will be a hard reset done by the recovery happening right now
Click to expand...
Click to collapse
Good luck. If no joy just try the pc suit. I'm fairly sure I had a success on my old g2 with a similar problem to yours. Can't remember exactly what I did but I kept trying things and eventually the pc suit recognised and sorted my device. Perhaps try to adb reboot recovery with the pc suit on screen??

PC suite and the software update thing didn't work for me. It just refuse to recognize my device. Hope things work out for u!

bobsie41 said:
Good luck. If no joy just try the pc suit. I'm fairly sure I had a success on my old g2 with a similar problem to yours. Can't remember exactly what I did but I kept trying things and eventually the pc suit recognised and sorted my device. Perhaps try to adb reboot recovery with the pc suit on screen??
Click to expand...
Click to collapse
Thanks. I was able to revive my phone. No loss of apps and data. Just the root was lost. Can you tell me what issues you have witnessed after such a recovery that made you to do a factory reset? The phone looks fine at the moment but wonder if it'd end up in a boot loop again.

manas.neo said:
Thanks. I was able to revive my phone. No loss of apps and data. Just the root was lost. Can you tell me what issues you have witnessed after such a recovery that made you to do a factory reset? The phone looks fine at the moment but wonder if it'd end up in a boot loop again.
Click to expand...
Click to collapse
You shouldn't have a problem. I just like to have a clean start and to make sure that there are no alien files left from my previous tampering.

bobsie41 said:
You shouldn't have a problem. I just like to have a clean start and to make sure that there are no alien files left from my previous tampering.
Click to expand...
Click to collapse
It went all smooth. I'd like to shout out to all LG G Pro 2 users to make a note of this method and try it whenever they soft-brick their phones.

service
scpion said:
I know.. I was desperate too... There's 2 versions, the other model is f350 or something.. Anyway at the service he did flash the phone again for me foc. BUT! He stamp a big NO WARRANTY as well... Goodbye to my balance 10 months warranty.. Buy hey.. I am grateful that I have my phone working again..I think.
I confirm with him again.. Yes, there is no stock recovery users can access....
Click to expand...
Click to collapse
Hi there,
I am in the same situation, I can not do the factory reset in any way was mentioned here (pc suite, lg update) in the forum, because there is no connection between the pc and the mobile.
Where you from anyway and which mobile service did you take your phone, how much was the service cost?
THX

david_csaba said:
Hi there,
I am in the same situation, I can not do the factory reset in any way was mentioned here (pc suite, lg update) in the forum, because there is no connection between the pc and the mobile.
Where you from anyway and which mobile service did you take your phone, how much was the service cost?
THX
Click to expand...
Click to collapse
Did you try this:
VOL DOWN + POWER
when LG logo appears release booth keys and wait 2 sec then
VOL DOWN + VOL UP
you should get factory reset screen

[Q] huawei g300 (u8815) not responding to anything after freezing & rebooting..

so, i have a huawei g300 it was constantly freezing and restarting so i rooted, unlocked bootloader and also zeroed my imei so i could downgrade to gb. after successfully downgrading it started acting up again like before, so i upgraded back to a non branded ics firmware. after awhile it started acting up again after a couple of restarts it never came back on again, it doesn't respond to anything at all recovery mode nothing. but all the lights on the phone flash for a second when i insert the battery and sometimes when i connect the phone to the pc it says unknown device. am no noob so i have tried almost all the known tricks. fastboot, recovery, cwm all that stuff they don't work. even opened the phone and took out the small battery to erase the bios(whatever it's called) memory.

so no one here can help me? cmon someone! anybody!

Hard wipe, or custom kernel
Sent from my HUAWEI Y210-0100

KkdGab said:
Hard wipe, or custom kernel
Sent from my HUAWEI Y210-0100
Click to expand...
Click to collapse
how do i hard wipe? is it the same as factory data reset in recovery menu? my phone doesn't turn on at all... when i insert the battery all the keys and charging led flashes for a sec that's all i get from this phone. i noticed when i insert the usb cable into the pc i get the unkown device message. makes me wonder what state it's in wether (bootloader mode or something else) and Softwares that operate in bootloader mode cant find the phone either. am really confused, never experienced such a brick before. or maybe it''s a hardware problem cos all evidence points to that.