I already snagged another phone so this isn't a dire emergency "HELP!", but I would like to learn all I can from this mistake, and maybe resurrect the phone.
My VZW G2 is badly bricked. It turns on, shows the LG logo, sits for 20 seconds, then reboots and repeats. I can't get into download mode, recovery, and definitely not normal boot. It doesn't say anything about security boot error or fast boot on the screen before rebooting. So far, I haven't been able to get to a point where the pc will recognize it... not showing up in device manager at all (no Unknown devices)
Here are the newb steps I took to get here:
tot flashed back to vs98010b
Rooted,
Backed up stock recovery
Flashed custom recovery (twrp2.6.3.2 > philzcwm6.19.3 > philzcwm6.19.7)
Took vs98011a ota update (yes, intentionally)
Now I'm in a recovery bootloop, no biggie - I wanted to see what the ota puts where.
Pulled what I wanted
- Now the newb mistakes -
Decided I wanted to do the ota, so I flashed the the stock recovery back... while in recovery
Rebooted - LG logo bootloop
I know flashing stock recovery was my big mistake, but I'd like to know why -
1. does something else need fixed to go back to stock recovery?
2. we can't dd the stock recovery while booted in recovery? (didn't even think about this when doing it since you can flash a recovery zip from recovery, but I guess thats different)
3. the stock recovery img must have been corrupted?
4. something else...
I'm counting this as an expensive lesson, so I would like to learn as much as I can from it.
Try this thread http://forum.xda-developers.com/showthread.php?t=2582142
shaungregg said:
Try this thread http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
I did look at that thread but didn't read thru all 38 pages. I'll go ahead and start reading thru it to see if someone in my spot was helped. Key difference between my scenario and that thread is that I have nothing showing up in device manager - I'm not getting the qhsusb_bulk device in device manager which is crucial for that to work.
I'm hoping someone knows how to force it to some other mode besides download mode and recovery since those don't work.
So i saw there was an application update for my lg g2 (d802) so i decited to install it but now my lg is stuck in OTA mode and it wont boot up because of the secure boot error.... I can't access download mode or fastboot or recovery. It is pretty useless now . Please please help my. I really don't know what to do....
FritsPikee said:
So i saw there was an application update for my lg g2 (d802) so i decited to install it but now my lg is stuck in OTA mode and it wont boot up because of the secure boot error.... I can't access download mode or fastboot or recovery. It is pretty useless now . Please please help my. I really don't know what to do....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2582142
26646648 409
Art Vanderlay said:
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
I tried that but it isn't working for me... something is wronge with my sdb files I thing
Can we get some more info model, variant, base band, any mods, and exactly what you've done so far
Art Vanderlay said:
Can we get some more info model, variant, base band, any mods, and exactly what you've done so far
Click to expand...
Click to collapse
I have the LG G2 D802 (international)
I wanted to backup my whole system just in case something would go wrong. So I installed cwm and when I booted my phone in recovery mode it was giving me a 'secure boot error'. But I accidently made a backup with the cwm error (I thought it was still the original recovery but it wasn't) then iI installed twrp 2.7 for lg g2 and that worked just great =). I made my backup. But then there was an software update from android (not google play) so I clicked on the 'install update notification' and my phone turned of and back on. but it booted in twrp instead of the original recovery (duh!) I looked it up on internet and found a command line I had to fill in in the twrp menu (something with 'dd if=/' etc). that fixed the problem but still the update wasn't installed. So I installed my old recovery back (the backup I made but what wasn't the original recovery. I installed the cwm 'secure boot error" recovery back). After I click again on the 'install update notification' my phone went in a bootloop with the 'secure boot error' I fuxed that problem now through this xda thread:
http://forum.xda-developers.com/showthread.php?t=2582142
But now my phone is stuck in fastboot mode, I tried these solutions but none of them helped...
http://uncle-yakuza.jouwweb.nl/lg-g2-fast-boot-menu-fix
http://forum.xda-developers.com/showthread.php?t=2477595
After all the fastboot commands are done an they all said 'OKAY' I rebooted my phone and in still booted in fastboot. \
Thats the whole story, and I again don't know what to do....
I'm in a very peculiar position here, where my LG G2 is stuck as the LG boot logo, but when plugged into my computer I have access to the internal storage. Here's how I got to this situation:
I previously owned a G2 on CM11 that had hardware issues. Before swapping it out due to those issues, I had made a backup using the package listed here, which created a few .img files, including boot.img.
On my new phone, I rooted, installed TWRP, made a backup of stock
Flashed Mahdi Rom
After flashing Mahdi Rom, my phone would immediately boot into fastboot, showing "fastboot started (new line) udc_start"
I did with the procedure listed here to be able to access download mode, and this was successful.
I then followed the procedure here to return to stock, but I got an error in LG FlashTools saying that I had the wrong model number. After a bit of digging around, it seems that this error may have been caused by the Mahdi Rom flash renaming my phone to "G2" instead of "d800".
After troubleshooting this for hours, I took a stab at flashing the boot.img file mentioned earlier through fastboot. Flashing this boot.img is what triggered the predicament I'm in now - I can access the phone's internal storage on my computer via USB, but it's stuck at the LG logo.
At this time, my phone will not ADB, fastboot, or enter recovery; I can only access download mode. When trying to enter recovery, it loads for about 1 second and then I'm kicked out and it goes back to the LG load screen.
Thank you in advance for any and all help
Try here http://forum.xda-developers.com/showthread.php?t=2687768
THANK YOU
MK45A said:
Try here http://forum.xda-developers.com/showthread.php?t=2687768
Click to expand...
Click to collapse
Holy **** it worked! Thank you for linking this, my D800 baby has been resurrected.
Hi all,
I have a UK N910F 32GB Snapdragon Note 4, with a custom Lollipop rom that I've been using with no problems for a few months (http://forum.xda-developers.com/note-4/snapdragon-dev/rom-bob4-devbase-multi-csc-safe-bloat-t3033881). Yesterday the weirdness began - my Note 4 froze randomly in normal use and rebooted. It was then fine for around 5 hours, then froze again, and when it restarted it would continue to freeze on start-up. At that stage I could still boot into recovery (Clockwork Manager custom recovery), so I tried clearing cache and dalvik, which changed nothing. But now I am unable to do even that - it just gets stuck in bootloop and won't even go into recovery.
When I turn it on, it will stay on the Samsung splashscreen for 10 seconds, then reboot and vibrate twice, then go back onto splashscreen, reboots, etc. I need to remove the battery to stop this. The only thing I am able to do is boot into download mode, where the phone works with Odin fine, and I am able to flash successfully with Odin.
So far I have tried reflashing a stock UK 5.0.1 ROM - it initially gave me the ext4 error but I then got the N910F pit file and repartitioned - Odin flashing completed fine, then still got stuck on splashscreen with "Recovery booting...."). I have also tried to flash CWM and TWRP, which both flash fine, but then the phone still won't boot into recovery - I get:
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
and doesn't boot into recovery. I'm pretty sure I'm using the correct TWRP and CWM versions.
I've spent all day trawling XDA and the wider web with no luck. Does anyone have any ideas on how to fix this? I'm hoping it is a softbrick but cannot work out how to get it back. I don't care about losing any data at this stage, just keen to bring my Note 4 back to life!
TL;DR: phone will stay on bootloop when powered on - not caused by failed software install, just started happening randomly. Cannot boot into recovery. Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Markachy said:
Download mode works and can flash with Odin, but all attempted flashes so far haven't helped even when Odin succeeds in flashing.
Click to expand...
Click to collapse
.
Have you tried flashing your variants cf-root file with auto reboot unchecked, let it Pass, remove USB abd battery, wait 30 seconds and reboot? Sounds weird.. i know, but for a while that put many users on 5.0.1 softbricks back to their previous working ROM.
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Markachy said:
I've just done that, it flashed successfully, I took battery and cable out and then rebooted after 30 seconds - it is now booting onto Samsung bootscreen, says:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Then reboots itself, same thing happens, reboots itself - back to a bootloop, but with the above written.
What's the fix for the above? Does it mean the recovery installed is wrong for the Android Rom version I have?
Thanks for your help so far, much appreciated.
Click to expand...
Click to collapse
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
phongpan355 said:
If you can still boot into the download mode and want to boot into the system as normal, using Samsung's Smart Switch tool will work. Search Google for "Samsung Smart Switch" no quotes, install the program then after finished installing, in the application, click MORE at the Smart Switch window, then click Emergency software recovery and initialization, then follow on-screen steps.
Click to expand...
Click to collapse
Just tried that, same issue. When it boots after installation, it says "Recovery booting..." in top left corner, then goes into bootloop. Thanks for the tip though.
Any other ideas out on the grapevine? Or is it time for a return?
I'm having the same issue. Tried stock ANK4, BOB4 and BOC3. Only bootloops and can't reach recovery mode.
Than I tried TWRP 2.8.7.0 and "philz_touch_6.59.0-trlte" but they don't work either.
Don't know what to do now. Never had this issue before on any Samsung device
EDIT: Tried Samsung Smart Switch and it dowloaded PDA: OC3 / CSC: OB6 / PHONE: OC3 (DTM). But my Note bootloops furthermore
Saw 2 other guys with the same Problem and no solution here.
And I found this. This could be the same issue we are facing:
http://forum.xda-developers.com/showthread.php?t=1840030
Hope there is a dev that can make this for our 910F
Hi all
This is now also happening to me...
Have Odind back to stock and it works for about 4 hours,
Then issue starts...
Reboots randomly
Then reboots to blank screen... No recovery
Again uk note 4. 910f
So I was installing twrp and everything went right until it didnt boot to the recovery and from then it keeps booting to lg logo and bootloader warning forever.
I know I can install the stock rom with lg up by I cannot enter download mode since the phone isnt technically turned off. Does anyoene have a solution.
It's my main phone and I literally cannot afford a phone right now.
A way to turn it off would be the solution. Battery was around 70% so it will take a long time to actually have 0%.
Update: I got to the fasboot menu from where I can run fastboot reboot recovery after installing twrp again. Now I have some mounting issues and I cannot flash any zip without entering bootloop. Im trying to use the shut down menu of twrp to try to enter download mode.
2nd Update: solved using lg up with the latest android version.