Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
Related
I'm not sure if this is a soft brick, full brick, or not bricked at all..not getting flashing red light or anything, but i am getting stuck at the white ATT boot screen
I'm not a dev. I was only trying to set my phone up wth root, Adeo ROM and Gingerbread theme but then ran into connectivity issues when i was trying to flash GB to it that i think had something to do with ADB not staying in \Sbin
- see this thread
Now i just did a factory reset and i am stuck in bootloader. Since i'm not familiar and don't want to brick it from here (if it's not already) some knowledgeable help would be GREATLY appreciated as to what do next i'm just a bit nervous to play at this point
UPDATE: I just noticed when i turn my phone landscape i get half (the right half) of the MOtolur login screen...half stays white ATT....weird
Thanks
i am no pro here, but try holding the vol down on boot from battery pull.. then factory reset from menus and delete cache.. then i am pretty sure you will boot fine...
the issue is your cache if i am not mistaken.
I have no idea what i did, but for now i am booting up again!
I tried to select what i thought was Factory Reset from Fast Boot menu. It didn't actually ever boot up from that. but after another battery pull it rebooted normally...very happy to see that!
For now everything looks good...now hopefully my ADB issue is going to be resolved with new driver installations and the flash...
u posted in the wrong froum but this is what u should do
http://forum.xda-developers.com/showthread.php?t=991595
and this is what u do if u brick
http://forum.xda-developers.com/showthread.php?t=991072
I appreciate the reply, and i appologize for posting in the wrong forum
i tried to flash that ROM but it doesn't install...believe it or not i am having a bigger issue than the previous...my phone is not being recognized through the USB bc for some reason ADB keeps getting deleted. Even if i manually add it it still does not allow me to flash anything, the phone acts as though not recgonized, but it is recognized through normal user USB functions..
Again, this is the thread related to that
and despite what the Title reads i assure you it does not seem fixed by anyone who has posted in that forum except one person
Dillsnik said:
I appreciate the reply, and i appologize for posting in the wrong forum
i tried to flash that ROM but it doesn't install...believe it or not i am having a bigger issue than the previous...my phone is not being recognized through the USB bc for some reason ADB keeps getting deleted. Even if i manually add it it still does not allow me to flash anything, the phone acts as though not recgonized, but it is recognized through normal user USB functions..
Again, this is the thread related to that
and despite what the Title reads i assure you it does not seem fixed by anyone who has posted in that forum except one person
Click to expand...
Click to collapse
man if im not mistaken, you can just flash the sbf file with
RSD lite even with offline adb.
trying that now actually...got hung the first time..going again now
Thanks
uhm, mate do you have the proper drivers installed?
yes, except for the adb issue
UPDATE - the SBF flash WORKED! hallelujah! lol
Moved as not android development
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!
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:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
I tried rooting my device using the install-twrp-recovery-xiaomi-mi-a3-guide/ it took a while but I got magidisk working but wifi wasn't connecting, if I turned it on it would turn itself off after a couple of seconds. I tried making a call and this crashed the system and factory resets the device, then the same issue comes up again. I thought I might have flashed the wrong iso. because I used the global version instead of stock_boot_10.3.13.0_mi_a3_eu.iso. I followed the same steps with this instead and had the same issue but on the phone the build number changed to 10.3.12.0 so I tried the same with that boot but it swapped back to 10.3.13.0. recovery mode come up with "no command" and I can access twrp and fast boot but nothing i've tried has let me make calls/ turn on wifi. I didn't make a back up unfortunately, would flashing the stock ROM work? oddly 4g does work and internet from that.
Not sure what to try, feel very out of my depth and feel a bit dumb trying this without having much of a clue what I was doing. Feel like it's not totally ****ed but I've hit a brick wall, thanks in advance for the advice.