I am used to installing a custom recovery, wiping the whole phone, and installing the ROM i want, and then being happy.
I got my v10 used and I did a factory reset after turning it on, but is there no way to plug it in to your computer and have the lastest update from LG written to it?
Android 6.0.1 came out 18 days ago and it's hard to know how long it will be until VZW pushes it OTA.
Related
I have Koodo P500H phone that came with Froyo (V10V ROM) installed on it. In July-August, I upgraded it to Gingerbread V20C stock rom using KDZ updater, rooted it, and flashed CWM Recovery on it. Earlier this week, Koodo also released their Gingerbread stock rom (V20A) and I thought of upgrading to it so that I can see what's modified in that rom. So, once again I used KDZ updater to flash the V20A ROM but didn't perform UNROOT / Factory Reset action before going ahead with the update. As a result, the ROM was flashed but I couldn't pass beyond the ANDROID logo.
Then, I thought of going back to V20C ROM and to my surprise this time Phone booted fine and it was back to the same state as it was to begin with. Next, I performed the Factory Reset (i.e. the phone appears as it was after V20C upgrade - no root and my applications) and made one more attempt to flash the V20A ROM. But, once again the result was same, i.e. couldn't go beyond the Android logo on Hard Reset after finishing the update procedure.
Then, I thought of checking what happens if I go back to V20C ROM and to my surprise this time Phone boots completely and all works fine. Next, I tried to flash the V10V ROM (that this phone came with) and again couldn't go beyond the Android logo.
Therefore, my problem is whenever I am flashing a ROM that is other than V20C my phone stays at Android logo, and works fine if I go back to V20C rom.
Please guide me what it is that I am missing or doing wrong here.
Thanks.
mdwivedi said:
I have Koodo P500H phone that came with Froyo (V10V ROM) installed on it. In July-August, I upgraded it to Gingerbread V20C stock rom using KDZ updater, rooted it, and flashed CWM Recovery on it. Earlier this week, Koodo also released their Gingerbread stock rom (V20A) and I thought of upgrading to it so that I can see what's modified in that rom. So, once again I used KDZ updater to flash the V20A ROM but didn't perform UNROOT / Factory Reset action before going ahead with the update. As a result, the ROM was flashed but I couldn't pass beyond the ANDROID logo.
Then, I thought of going back to V20C ROM and to my surprise this time Phone booted fine and it was back to the same state as it was to begin with. Next, I performed the Factory Reset (i.e. the phone appears as it was after V20C upgrade - no root and my applications) and made one more attempt to flash the V20A ROM. But, once again the result was same, i.e. couldn't go beyond the Android logo on Hard Reset after finishing the update procedure.
Then, I thought of checking what happens if I go back to V20C ROM and to my surprise this time Phone boots completely and all works fine. Next, I tried to flash the V10V ROM (that this phone came with) and again couldn't go beyond the Android logo.
Therefore, my problem is whenever I am flashing a ROM that is other than V20C my phone stays at Android logo, and works fine if I go back to V20C rom.
Please guide me what it is that I am missing or doing wrong here.
Thanks.
Click to expand...
Click to collapse
If a factory reset not work... remove the battery and try again... it can take several times to work...
Thanks FPChaim for your response. I had already tried that numerous time.
Anyways, I found a solution for that and it was different Hard Reset key combination (Home + Volume Down + Power) which works after flashing Koodo's ROM. However, with other ROMs (V20C and V20G) it was (Menu + Volume Down + Power) combination that would work.
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
dsteinschneider said:
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
Click to expand...
Click to collapse
If you're looking for a newer phone that lets you unlock the bootloader, you might want to check out last year's Nexus 6 or the newer Moto X Pure Edition. The Nexus 6P from Huawei also looks nice and I'm keeping an eye on it as my next potential phone. The Nexus 5x from LG should also have a boo that can be unlocked.
-----------
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
I'm thinking that you're probably getting confused with needing to flash Beanstown106’s modified MJ9 firmware (which doesn't return the phone to stock or contain the 4.3 bootloader). See one of my previous posts ( http://forum.xda-developers.com/showthread.php?p=58541771 ), which discusses a similar issue and has a link on how to flash the stock recovery back onto the phone if you'd like to try that rather than restoring the phone back to stock 4.1.2.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
I usually remove my Sim card when restoring to stock 4.1.2... just to ensure I don't accidentally take an OTA update before I get it rooted again. (You can skip the initial phone Setup screen with the method in this YouTube video - https://youtu.be/qekEpn1Bufc ). It says it's for the S3 but works on the Note II as well. Once you get back into the phone and enable USB debugging in Developer options, you should be able to run Casual again. The phone doesn't have to be activated or on wifi to do this.
Once Casual is successful, it's safe to put the Sim card back in because I don't believe an OTA can install successfully with a custom recovery installed.
Good luck.
mattnmag said:
I
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
Click to expand...
Click to collapse
All the ROM's and tools are from threads here so pretty sure I'm using Bean's modified MJ9. I was on Beans 4.3 for over a year before I went to the Alliance ROM.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
Click to expand...
Click to collapse
4.1.2 sounds like a better idea - I have that also.
Thanks your advice here is just what I was looking for in my effort to get this phone running again.
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
dsteinschneider said:
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
Click to expand...
Click to collapse
I don't know if a USB jig would help the computer recognize the phone again.
Since you tried 3 different computers and still couldn't get it recognized... I'm wondering if something got fubared when you Odin flashed the VRLJB stock Rom. So when you go to Device Manager in the computer, the computer doesn't even show anything connected at all?
I don't know that it would be worth the time, but (on the computer that last worked for your phone), you could try uninstalling the Samsung Drivers, and then use a program like DevManView to totally uninstall all Android related drivers. Restart the computer afterwards and then reinstall the Samsung USB Drivers (from here: http://www.samsung.com/us/support/owners/product/SCH-I605) . Then connect your phone back to the computer in Download Mode to see if it will reinstall the drivers and recognize it.
If the computer still doesn't recognize the phone after all that, then I'm out of ideas.
I'll try the devmanview driver cleanup (love nirsoft utils!) and install the driver in your link on the orginal pc which I use for flashing ROMs. If that doesn't work I'm going to look into sending it out to a JTag guy although they claim if you can get into download mode after they perform their magic that they were successful.
Went with the LG G4 which I'm very happy with. As far as getting the Note 2 running again I've been thinking l might buy a used Verizon Galaxy Note 2 motherboard on ebay rather than sinking a lot of time into trying to... should I say "unbrick" it.
If you ran casual first, it will not connect to the samsung driver, until you uninstall the USB services from the device manager, and then run find new hardware.
But maybe this will not help considering you already tried 3 machines?
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
dsteinschneider said:
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
Click to expand...
Click to collapse
Right, it was in the Adam Antler video, for casual. Once you use the casual on USB, the samsung driver will not work until you uninstall and reinstall USB system.
I can get almost 3 days out of a phone battery with little or no use. The one I am using could make it a day and 1/2, but I charge that one every night because I do not need and down time just in case.
I am using the nightly build, 12.1-20151222 12/22/15, I am not sure how the other builds are, or even the stable build for that matter?
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
So it has been a VERY, VERY, long time since I attempted to root a device. I admit, that I completely forgot most of what I knew from back in the day rooting like the Motorola OG Droid. Here's the deal. I tried rooting a USC XT1526 and I had no idea what I was doing. I followed the steps through and managed to install TWRP and SU. So I assume I got full root. Well The issue started after I got an UPDATE AVAILABLE message and tried to go through with the OTA Update. When it got to the point of installing the OTA Update, my device turned off like normal but instead of updating, it booted into TWRP recovery. It didn't update at all and when I booted my phone normally, it kept trying to update so my phone turn off (loop) every time it tried to install the update. I did a factory reset and it stopped rebooting. I later tried to flash back to fully stock but I believe I might have downloaded the wrong file because I now have a device with no WiFi. Can someone please help me.
Hi guys hopefully someone can give some guidance on my issue.
I loaded a rom (pixel experience (android 10)) apart from stock for first time since I bought v30 about a year ago. Found it to be somewhat unstable, so went back to stock rom (android 9). Phone now boots to LG logo with startup tune, and just sits there on that screen for at least 1 minute longer than it did previously. Did a a complete wipe between flashes, went back to pixel experience to see if it went back to normal "boot speed", Phone bootup speeds went back to normal on that. Now back on stock again, and it's same thing with long boot time. Phone boots up fine eventually but it is quite painful to deal with now and regretting trying something different with zero payoff.
Any ideas?
Many have found flashing back to Nougat KDZ, then flashing to Pie KDZ (your bootloader will remain unlocked during both flashes), then re-installing TWRP, and re-rooting erases some of the changes you describe. See this post for reinstalling all that stuff, after you flash Nougat, then Pie KDZ.
INSTALL or REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Can't guarantee it, but going back to Nougat temporarily flushes a lot of stuff out of the system.
Which variant do you have?
GetRekt_ said:
Hi guys hopefully someone can give some guidance on my issue.
I loaded a rom (pixel experience (android 10)) apart from stock for first time since I bought v30 about a year ago. Found it to be somewhat unstable, so went back to stock rom (android 9). Phone now boots to LG logo with startup tune, and just sits there on that screen for at least 1 minute longer than it did previously. Did a a complete wipe between flashes, went back to pixel experience to see if it went back to normal "boot speed", Phone bootup speeds went back to normal on that. Now back on stock again, and it's same thing with long boot time. Phone boots up fine eventually but it is quite painful to deal with now and regretting trying something different with zero payoff.
Any ideas?
Click to expand...
Click to collapse
Yep, exactly this. After many hours yesterday of troubleshooting and trying different stuff, what I did in end was downgrade to first oreo release and OTA'd my way backup, all back to normal now.
Phew, glad it's not something I have to live with.
ChazzMatt said:
Many have found flashing back to Nougat KDZ, then flashing to Pie KDZ (your bootloader will remain unlocked during both flashes), then re-installing TWRP, and re-rooting erases some of the changes you describe. See this post for reinstalling all that stuff, after you flash Nougat, then Pie KDZ.
INSTALL or REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285
Can't guarantee it, but going back to Nougat temporarily flushes a lot of stuff out of the system.
Which variant do you have?
Click to expand...
Click to collapse