Database Info

Well I screwed up

Okay, so SOMEHOW I downloaded the crespo factory images and flashed the bootloader and then the radio. The system update wouldn't flash and this is when I realized my horrible mistake. So I downloaded the correct factory images. But now, I have no USB access on the thing. Can't fastboot. Can't adb. Phone boots and charges over usb. I can reboot into the bootloader, but my computer doesn't recognize the phone is even attached. I can reboot into recovery (I still have CWM on there) but what can I do from there? Am I TOTALLY ****ed? Please please please help!.....

I think what I need is a CWM flashable bootloader zip file. Or a complete OTA ROM Update zip file that flashes ROM, radio, and bootloader. Since I have CWM I think either of these will work for me, but I can 't find anything like this for the Nexus S 4G. Can anyone help?

have you checked if your computer recognizes your phone on odin mode? if it does you can prob try this
http://forum.xda-developers.com/showthread.php?t=1575502

JOEOZUNA4U said:
have you checked if your computer recognizes your phone on odin mode? if it does you can prob try this
http://forum.xda-developers.com/showthread.php?t=1575502
Click to expand...
Click to collapse
Unfortunately it doesn't. My computer doesn't recognize this phone at all anymore, not in fastboot or download mode, or even just booted into Android. If someone could PLEASE show me where a CWM flashable file that will flash the bootloader is, or make me one, I'd pay some good $$$ for it. Please help?

You flashed the bootloader & radio with ODIN?

supercluver said:
Unfortunately it doesn't. My computer doesn't recognize this phone at all anymore, not in fastboot or download mode, or even just booted into Android. If someone could PLEASE show me where a CWM flashable file that will flash the bootloader is, or make me one, I'd pay some good $$$ for it. Please help?
Click to expand...
Click to collapse
Give me a sec I will try to make a flashable CWM with just the bootloader. No need for donations

polobunny said:
You flashed the bootloader & radio with ODIN?
Click to expand...
Click to collapse
I flashed the CRESPO bootloader and radio via fastboot. Then when I tried to flash the ROM update via fastboot it gave me an error. This is when I noticed I was using the CRESPO files instead of the CRESPO 4G files.... Now, after rebooting, my computer WILL NOT recognize the phone at all via usb, in any way, fastboot, ODIN, nothing. But otherwise the phone seems fine. It charges over USB. It boots and I can get into recovery (and I still have CWM) so if I could download a file over wifi (which I can, already tried) and then flash said file via CWM that would flash the new bootloader, I'd be good to go.

rasengan82 said:
Give me a sec I will try to make a flashable CWM with just the bootloader. No need for donations
Click to expand...
Click to collapse
Dude THANK YOU.

I don't think that's possible though, to make a CWM flashable bootloader. :|

Here ya go man. Hope this helps.
https://www.dropbox.com/s/0yemj2aybmdda4f/crespo4g_bootloader_rasengan82.zip

polobunny said:
I don't think that's possible though, to make a CWM flashable bootloader. :|
Click to expand...
Click to collapse
I'm pretty sure it is, as a complete OTA zip will flash the radio, bootload, and ROM, at least I think it will....

rasengan82 said:
Here ya go man. Hope this helps.
https://www.dropbox.com/s/0yemj2aybmdda4f/crespo4g_bootloader_rasengan82.zip
Click to expand...
Click to collapse
Here. Just in case you missed from previous page.

rasengan82 said:
Here. Just in case you missed from previous page.
Click to expand...
Click to collapse
THANK YOU! Worked perfectly. Flashed, rebooted to bootloader, and computer recognized the device again. You are a life saver! You sure no donations are necessary???

supercluver said:
THANK YOU! Worked perfectly. Flashed, rebooted to bootloader, and computer recognized the device again. You are a life saver! You sure no donations are necessary???
Click to expand...
Click to collapse
Nah it's alright man. Glad it worked!

NVM RAS is da man!
Can you put the phone into download mode?
1. Unplug USB and pull the battery. then replace the battery.
2. with the volume up and vol down buttons held down. Press and release the power button for about a sec.
If you get the same as the picture below follow the procedure found here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

i flashed a CM nightly build.. which is out nof the norm for me kuz i usually stick with #euroskank and i lost all USB capabilities too. everything else works perfectly, charges fine and all..
i flashed the above zip and it gives me temp access via USB but if my phone goes to sleep or if i reboot im back to square 1 and have to re flash... dunno wtf i did but damn this sucks

kalico17 said:
i flashed a CM nightly build.. which is out nof the norm for me kuz i usually stick with #euroskank and i lost all USB capabilities too. everything else works perfectly, charges fine and all..
i flashed the above zip and it gives me temp access via USB but if my phone goes to sleep or if i reboot im back to square 1 and have to re flash... dunno wtf i did but damn this sucks
Click to expand...
Click to collapse
Did you ever get this resolved? I did something VERY similar when I first started modding on this phone, and experienced VERY similar issues. I have an AWESOME fix, even though it leaves the download screen looking like the oem unlock screen if you put oem lock back on (otherwise it looks normal, and who the heck would do that is beyond me - I only found it when I originally took it back to COMPLETE stock), but it functions fine, and this will take you back to gb, but it seems like the 'fixall' for this phone, and you can always reroot, reflash cwm via fastboot, etc, after using it.
Let me know.
Peace..
~WickiD~

DONT POST IN THE DEVELOPMENT THREAD UNLESS YOU'RE RELEASING A ROM KERNEL OR RECOVERYY!!!
this needs to be moved to Q&A or General...
BIGGEST PET PEEVE!!!!!!!!!

[Q] Infuse stuck on boot screen

Background: Trying to update my stock infuse to Jelly Bean. Looked into what was needed via hours of research. Used SuperOneClick to root phone (Success), installed ESFile Manager to help install mod 3e recovery (success), used ROM Manager to flash CWM (Success).
Upon testing the CWM by booting into recovery, this boot screen issue started.
- I've tried hard resetting, (no success, won't go past the Samsung screen).
- I'm currently using Odin to restore stock firmware, but it's been about 25 minutes so it's probably not working.
- I can only get to Samsung screen and download mode, that's it!
I need my phone and I need to get some sleep. what am I missing? Much appreciated
thanks

here's a shot of Odin right now. It's stuck on "setup connection"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Here is what I used to Un-boot loop my phone worked like a charm, the instructions we're a little un-clear but if you read through it, a few times, it's really rather easy. You need to download Java (Jave Runtime Enviorment, also known as JRE I used OpenJDK Java 7) on your computer, download the Heimdall one click packages, put your phone in download mode:
-Pull the battery out and make sure the phone is NOT connected by a usb cable.
-Put the battery back in!
-Hold vol up+Vol down. DO NOT PRESS POWER.
-Plug in the USB cable.
Open the downloaded heimdall one click with java (in Ubuntu Context menu Windowz is likely the same) and it will return your phone back to stock which is where you want to start for I believe almost all the JB ROMs. If you search around Quickster made some other One click packages to get you rooted and CWM installed as well as Kernels and other stuff. These things work great and to me are a million times easier than every other method.Good luck and if there's any other help I can provide I'll do my best

dginsd said:
Here is what I used to Un-boot loop my phone worked like a charm, the instructions we're a little un-clear but if you read through it, a few times, it's really rather easy. You need to download Java (Jave Runtime Enviorment, also known as JRE I used OpenJDK Java 7) on your computer, download the Heimdall one click packages, put your phone in download mode:
-Pull the battery out and make sure the phone is NOT connected by a usb cable.
-Put the battery back in!
-Hold vol up+Vol down. DO NOT PRESS POWER.
-Plug in the USB cable.
Open the downloaded heimdall one click with java (in Ubuntu Context menu Windowz is likely the same) and it will return your phone back to stock which is where you want to start for I believe almost all the JB ROMs. If you search around Quickster made some other One click packages to get you rooted and CWM installed as well as Kernels and other stuff. These things work great and to me are a million times easier than every other method.Good luck and if there's any other help I can provide I'll do my best
Click to expand...
Click to collapse
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed

mendozer said:
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed
Click to expand...
Click to collapse
Perhaps try to use the Heimdall "back to stock" while in that Emergency mode. The Heimdall program will also tell you if it recognizes a phone attached in download mode, and if it will recognize the phone and flash you back to stock, you can also have it put you back on stock bootloaders which sounds like your problem (though flashing bootloaders is dangerious but in your case may be nessessary). Maybe PM Quickster see if he recommends trying to flash with Heimdall on that mode you've entered, I might also try using an alternate USB cable if you haven't already.

mendozer said:
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed
Click to expand...
Click to collapse
The computer icon with a yellow hazard triangle in between them is a form of download. Use Heimdall after making sure you have the correct JRE and drivers.
Sent from my SGH-I997 using xda premium

psal217050 said:
The computer icon with a yellow hazard triangle in between them is a form of download. Use Heimdall after making sure you have the correct JRE and drivers.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I have the stock firmware from Samsung. that includes the drivers I presume? the md5 file

holy smokes I'm so relieved it worked!
So, I used Heimdall's froyo Uck3 firmware or whatever since that's what was in the package. I still want Jelly bean. I have the JB folder with what I suppose I need (think it was from android geeks). However, since this was painless, is there a Heimdall one click for JB?

mendozer said:
holy smokes I'm so relieved it worked!
So, I used Heimdall's froyo Uck3 firmware or whatever since that's what was in the package. I still want Jelly bean. I have the JB folder with what I suppose I need (think it was from android geeks). However, since this was painless, is there a Heimdall one click for JB?
Click to expand...
Click to collapse
I haven't seen a Heimdall for JB, or any custom ROM I think because it requires a special PIT file to make. I used this ROM http://forum.xda-developers.com/showthread.php?t=1776129 To flash It though you have to be on the Gingerbread bootloaders, and the instructions for flashing it want you to even flash CM9 ICS, before you flash the final JB ROM. Basically follow the instructions thoroughly or you'll end up in a boot loop ( Not that that's a big deal, now that you have a quick easy way out)

meanhs sal
darn, I'll have to see if JB is really worth it to take the chance again. I also noticed that froyo version from the Heimdall is quirky with some apps. I turn the phone on and several apps just close on me. I get the buzz of death (the one and three) as i like to call it

I'm pretty sure there's Gingerbread version of the Heimdall one click, I'd flash that as almost all the newer Roms are going to require you at least have upgraded to the Gingerbread bootloaders.

NO BOOT: Stuck at "Samsung Galaxy Note 10.1" Splash Screen

Hi All,
I've gone through all the different threads but I am going nowhere so I have decided to start a new one and track steps I have done so far. I have a Samsung Galaxy Note 10.1 Wifi-Only (GT-N8010) and it just stays stuck on the "Samsung Galaxy Note 10.1" Splash Screen.
Premise
#1: My tablet is not rooted.
#2. I am no longer interested in recovering any files in it. I just want it working again.
#3. I cannot access Recovery mode
#4. Fashed with Stock Rom from Sammobile using Odin (v3.10.7, v3.07, and v1.85): Says "PASS", restarts then > same issue. Attempted to go to Recovery using Power+Up Button on Splash screen> Still can't go to Recovery, can still access Download mode.
Any help would be greatly appreciated.

Can you access recovery?

Just flash stock 8010 rom via Odin .

JJEgan said:
Just flash stock 8010 rom via Odin .
Click to expand...
Click to collapse
I have looked everywhere but I can't seem to get a stock rom. I'll look further..is there any specific options that I might need to check/uncheck e.g F.Reset etc?

DroidTwe4kz said:
Can you access recovery?
Click to expand...
Click to collapse
No. I can access download but not recovery mode...

Update
Currently downloading stock firmware from SAMMOBILE
Model GT-N8010
Model name GALAXY Note 10.1
Country Australia
Version Android 4.1.2
Changelist 805288
Build date Wed, 20 Nov 2013 07:29:39 +0000
Product code XSA
PDA N8010XXUCMK2
CSC N8010XSACNA2

Marcel41 said:
Currently downloading stock firmware from SAMMOBILE
Model GT-N8010
Model name GALAXY Note 10.1
Country Australia
Version Android 4.1.2
Changelist 805288
Build date Wed, 20 Nov 2013 07:29:39 +0000
Product code XSA
PDA N8010XXUCMK2
CSC N8010XSACNA2
Click to expand...
Click to collapse
Flash it via Odin.

DroidTwe4kz said:
Flash it via Odin.
Click to expand...
Click to collapse
Still no Go. It says PASS, it restarts then same issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Comment boots un gas

Marcel41 said:
Still no Go. It says PASS, it restarts then same issue.
Click to expand...
Click to collapse
Uncheck auto reboot in Odin. Reboot manually into recovery mode and boot system

DroidTwe4kz said:
Uncheck auto reboot in Odin. Reboot manually into recovery mode and boot system
Click to expand...
Click to collapse
Yesterday, my stock, unrooted 8013 rebooted itself from sleep mode and I found it stuck at the splash screen when I went to pick it back up after a long conference call. I also can only get into download mode since Kies doesn't recognize my tablet. I found the only 8013 ROM on Sammobile and flashing it with Odin did nothing. I then downloaded the PIT file for the 8013 from a thread in this forum and retried with Odin, repartitioning and reflashing the ROM. I'm still stuck at the splash screen and only able to download. (I ran Odin again with your suggestion of turning Auto-Reboot off, didn't make a difference.) I'm seeing many users with the first gen notes experiencing this issue. Although I'm not seeing any errors when using Odin, do we have defective NAND memory? This problem seems to be increasing as our tablets age. Anyone have any other suggestions of potential fixes?

Well, I found a copy of official KK 4.4.2 and flashed it, since I had that version on my tablet and bootloaders supposedly don't work with earlier versions. Unfortunately, it didn't help. Installing other recoveries haven't worked. I still can't get into recovery mode, only download mode. Tomorrow, I'll try Nand Erase. I keep reading posts in various forums. It seems this is a common problem, even for stock, unrooted tablets. Some are saying Samsung is saying it's hardware related. I have a battery saver program that has a different battery icon when charging. My tablet can still see data because it switches to the 3rd party battery icon a few seconds after I put the tablet on charge. I'm hoping that if I have a file that's been corrupted in the cache or bootloader and can't be written to that Nand Erase will delete it and then be able to re-partition and properly flash a standard ROM. I've got a headache from reading so many posts that I'm quitting for the night. Samsung should make various standard ROMs available even for products at end of life. They overcharge and don't support their hardware very well. It's frustrating trying to find official ROMs for various models.

DroidTwe4kz said:
Uncheck auto reboot in Odin. Reboot manually into recovery mode and boot system
Click to expand...
Click to collapse
Same thing.. I restarted manually holding POWER+VOLUME UP. When the Samsung Galaxy Note screen appears, I release the power button while holding VOLUME UP. It blinks but goes back to the Samsung Galaxy Note 10.1 screen.

Marcel41 said:
Same thing.. I restarted manually holding POWER+VOLUME UP. When the Samsung Galaxy Note screen appears, I release the power button while holding VOLUME UP. It blinks but goes back to the Samsung Galaxy Note 10.1 screen.
Click to expand...
Click to collapse
Did you already try to flash PhilZ kernel or recovery?

DroidTwe4kz said:
Did you already try to flash PhilZ kernel or recovery?
Click to expand...
Click to collapse
I tried installing both recoveries, inluding PhilZ's, which were included in the official KK 4.4.2 ROM zip from XDA forums. Didn't work. There are far more dicussions of this issue--soft brick with no access to recovery mode on all Samsung devices--on other forums. I think those who are speculating that a corrupted cache file or partition file has become read only and is preventing successful flashing are right. Without access to recovery, we're totally stuck. There are some suggesting that those of us with non-removable batteries carefully access our batteries, remove the cables (plugins, not soldered) for 12 seconds and see if we can then boot into recovery mode. That's the easy fix for Samsung phones with removable batteries. This weekend, I'm going to remove the back of my Note 10.1 and unplug the battery connectors for 12 seconds and then see if I can boot into recovery. I've asked a senior member with experience with Odin Nand Erase some questions and may go that route if the battery disconnect doesn't work to get me into recovery. If Odin can still write to the Note after Nand Erase and rewrite the Pit file an official ROM that may be the only way to get rid of the corrupted file that's become read only.

mke1973 said:
I tried installing both recoveries, inluding PhilZ's, which were included in the official KK 4.4.2 ROM zip from XDA forums. Didn't work. There are far more dicussions of this issue--soft brick with no access to recovery mode on all Samsung devices--on other forums. I think those who are speculating that a corrupted cache file or partition file has become read only and is preventing successful flashing are right. Without access to recovery, we're totally stuck. There are some suggesting that those of us with non-removable batteries carefully access our batteries, remove the cables (plugins, not soldered) for 12 seconds and see if we can then boot into recovery mode. That's the easy fix for Samsung phones with removable batteries. This weekend, I'm going to remove the back of my Note 10.1 and unplug the battery connectors for 12 seconds and then see if I can boot into recovery. I've asked a senior member with experience with Odin Nand Erase some questions and may go that route if the battery disconnect doesn't work to get me into recovery. If Odin can still write to the Note after Nand Erase and rewrite the Pit file an official ROM that may be the only way to get rid of the corrupted file that's become read only.
Click to expand...
Click to collapse
I think that you wiped /boot partition and then rebooted your phone. That's what causing that you can't access recovery

DroidTwe4kz said:
I think that you wiped /boot partition and then rebooted your phone. That's what causing that you can't access recovery
Click to expand...
Click to collapse
No, i,m till soft=bricked and boot to the splash logo. what most people don't understand who haven't experienced this is not being able to get to recovery to wipe cache seems to cause Odin to be unable to flash anything even though it doesn't give error messages. Those with phones that have removable batteries are generally able to remove their batteries and then get to recovery and wipe cache. Doing that, they are able to flash ROMs. This has led many to speculate that a file or files have become corrupted and read only, preventing successful flashing. This is a long standing issue with most Samsung devices.

mke1973 said:
No, i,m till soft=bricked and boot to the splash logo. what most people don't understand who haven't experienced this is not being able to get to recovery to wipe cache seems to cause Odin to be unable to flash anything even though it doesn't give error messages. Those with phones that have removable batteries are generally able to remove their batteries and then get to recovery and wipe cache. Doing that, they are able to flash ROMs. This has led many to speculate that a file or files have become corrupted and read only, preventing successful flashing. This is a long standing issue with most Samsung devices.
Click to expand...
Click to collapse
Maybe you can disassemble your device and remove battery manually.

DroidTwe4kz said:
Maybe you can disassemble your device and remove battery manually.
Click to expand...
Click to collapse
I won't need to completely remove the battery, just unplug the connector cables. If the battery disconnect doesn't work, then I may try Nand Erase--apparently, Odin can flash Pit files and ROMs after it does Nand Erase. If none of this works, then my Nand memory is totally corrupted and unrepairable. What surprises me is how often this happens on totally stock Samsung devices. Samsung's Nand may be inferior and easily corrupted.
---------- Post added at 11:28 AM ---------- Previous post was at 10:57 AM ----------
I looked at the iFixit teardown of the Note 10.1 just to see if the Nand chip is soldered. Its not, it's plugged in and the board is screwed down and easy to remove. Replacement Nand (Samsung KLMAG2GE4A NAND flash memory) costs $25 USD. Should battery disconnect or Nand Erase not work, I'll replace the Nand chip.

mke1973 said:
I won't need to completely remove the battery, just unplug the connector cables. If the battery disconnect doesn't work, then I may try Nand Erase--apparently, Odin can flash Pit files and ROMs after it does Nand Erase. If none of this works, then my Nand memory is totally corrupted and unrepairable. What surprises me is how often this happens on totally stock Samsung devices. Samsung's Nand may be inferior and easily corrupted.
---------- Post added at 11:28 AM ---------- Previous post was at 10:57 AM ----------
I looked at the iFixit teardown of the Note 10.1 just to see if the Nand chip is soldered. Its not, it's plugged in and the board is screwed down and easy to remove. Replacement Nand (Samsung KLMAG2GE4A NAND flash memory) costs $25 USD. Should battery disconnect or Nand Erase not work, I'll replace the Nand chip.
Click to expand...
Click to collapse
Try disconnecting cables on the battery. It will hopefully fix the problem. I own Note 10.1 and I haven't ever had this kind of problem before. Every time when I get into bootloop, I used PhilZ recovery and that fixed my problem.

PLEASE HELP! Attempted to root, now stuck on boot screen. Verification fail/mismatch

I'm brand new to LG devices & was using this threads instructions
http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526
I tried rooting using a TOT file in LG UP. However, when I opened lgup it said I needed to download the driver for it to work. But I had downloaded the h830 DLL and the mobile drivers, and the program launched and saw my device so I just continued.
After it opened, I just selected the TOT file and started, it finished, and now I can't get past the boot screen. There's red language at the upper left saying 680,730,780 boot verification fail, 830-cause mismatch_sig_len, 880,930
Ive read and downloaded things for hours now trying to figure out how to get it back to stock. I've downloaded the 4.9gb tot file that's linked in that thread for going back to stock, but all I can find is people saying use lgup to flash the file.
My question is, how do I accomplish that if I can't get past this screen? I can't get it back in the bootloader. I can't get it to be recognized by the pc. And lgup still says it needs the driver when I open it, and it doesn't see the phone either. Please help. I've had this phone all of 1 day.
BTW, I uninstalled lgup and the driver and DLL, rebooted, then reinstalled the DLL and driver first, before reinstalled lgup and it still says it needs the driver.

Anyone?
I never used adb to unlock the bootloader before trying to flash. I thought I only had to check oem unlock and USB debugging in developer options because I was trying to use iroot first.
My main problem is my phone starts up but doesn't get past the LG logo. It shows the boot verification error, mismatch_sig_len then immediately reboots and does it again. How do I reflash the stock TOT file in this state?
Is it just a driver issue, and my phone should be seen by lgup even in this bootloop? Or do I have to get it back into bootloader? If so, how?
Please don't disregard if I sound like a total idiot. I do have experience flashing with galaxy devices. I just didn't do enough research before I tried this one.

Have a look at LG Flash.

im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.

konchar said:
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
Click to expand...
Click to collapse
Please browse the thread and/or the guides section first. It's there. Being self-sufficient never hurt anyone.

konchar said:
im stuck in pretty much the same spot as you. you can press up during that boot loop to go back to download mode, but when i run LGUP again with the "stock" version, there is an error a few seconds in. that says error code 0x81000402 tot antirollback version is smaller than device version. Thats all i got for today, hopefully some one will be able to help us out.
as for lg flash, i found the program but im not sure what to do with it, do you have any instruction, or directions for how to use it?
one thing i noticed, was i was doing all fo this with lg up version 1.11, not 1.14. that might have caused our problems, check to see wich version you used. but in the end i downloaded lg bridge and simply had it update my phone. it could read my phone when it was in download mode, that you get to by pressing the up volume button. ended up without root, but it was no longer in a bootloop.
Click to expand...
Click to collapse
Thank you for this post. Just knowing that someone who had the same issue as me was able to get the phone back to stock successfully made me not so anxious.
My main issue the other night when I was trying to fix the phone, was I couldn't get it back into download mode. I had the phone connected to the computer, and was disconnecting the battery and connecting it again while holding volume up, with the cable always connected. Tonight, I just help volume up while plugging in the cable instead, and was able to get it into download mode.
I then ran into the same anti rollback issue. But I'm now using LG Bridge to go back to stock.
I think what we need to do to get root, is enable USB debugging and check oem unlock. Then use the sdk tools with the command prompt window... Adb reboot bootloader>Fastboot oem unlock, then try flashing the root tot file with latest version of lgup.
As long as I know I can get back to stock, I won't be so scared about attempting the root again. Lol.
TH4N1X said:
Please browse the thread and/or the guides section first. It's there. Being self-sufficient never hurt anyone.
Click to expand...
Click to collapse
Come on man. Some of us have spent hours searching what to do, and are running into unforseen issues and just need a little guidance. I'm all for searching threads to get your information, but when your hours or days in and running into walls, regardless of the reason... It's ok to ask for help. Not everyone has the same knowledge and skill level with this stuff. I've only ever used Odin to flash stuff to galaxy phones before... All this LG stuff is brand new to me.

Ok relax, in order to have your device recognized by your pc you must now put it in d/l mode (with power off, hold volume down and power until d/l mode starts) then run LG UP and try to downgrade. If that gives you the all to well known anti-rollback error then you need to download the hacked version of lg up (forget what it's called but it's in one of the rooting threads) and then downgrade. I struggled with the same thing a while back. My memory just isn't so good but I'm confident you'll figure it out.

@SaintCity86
autoprime said:
Repacked LG's original installer with @ieatacid's patched EXE.
Should make installing it all even easier... no more EXE switch.. just install and use (hopefully).
I made sure to add ieatacid's name, paypal and this thread in the Setup EXE.. this way ieatacid's name will always be attached to the LG Flash install rather than the loose LGFlash.exe getting passed around like the old megalock.dll.
Added LGUP and LG Flash directions and downloads to my All-in-One G5 Thread here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MD5 (Setup_LGFlashTool_2.0.1.6-ieatacid.zip) = 7e2a5a6c74ac3d54a707c7fcde831655
MD5 (Setup_LGFlashTool_2.0.1.6.exe) = 6d0f8a4ad4bc01157a9c7c16f3a7c574
Download Setup_LGFlashTool_2.0.1.6-ieatacid.zip
Click to expand...
Click to collapse
Second page, 7th post on it (17th in total). It's also stickied in the Guides, News, & Discussion section.
http://forum.xda-developers.com/showpost.php?p=66683763&postcount=17
You can also try different versions of LG UP and if it fails go for the LG Flash. You can find software to flash here: http://lg-firmwares.com/lg-h830sv-firmwares/. Only flash KDZs from the TMO region. If you succeed in going back to stock, you can get recovery and root by using the Dirty COW exploit.
One more thing:
SaintCity86 said:
Tonight, I just help volume up while plugging in the cable instead, and was able to get it into download mode.
Click to expand...
Click to collapse
That's how you actually get into download mode. Battery pulling is for getting out of it.

So I managed to get it back to stock by using LGBridge and updating. And I've been using the 3 step guide in this thread:
https://forum.xda-developers.com/tm...p-step-guides-rooting-t-mobile-lg-g5-t3388272
All seemed to be going fine, but when I put my phone is is debugging and checked oem unlock then plugged it into my laptop (64bit windows 7), it failed to install 2 parts of the initial driver. MTP and another one I can't remember. But it is recognized by the computer when it's on.
However, when I boot into fastboot, it's only showing up as an android device with no driver. And I can't figure out which driver to get for the life of me. Idk if I'm running into issues because it's a 64bit system or what. Do you Have any suggestions where I can look to get this resolved?
TH4N1X said:
That's how you actually get into download mode. Battery pulling is for getting out of it.
Click to expand...
Click to collapse
Yeah I'm aware. It's the same for Samsung galaxy devices which I've developed on for years....my issue was I had the phone plugged into the computer and was pulling the battery to turn it off and just plugging the battery back in holding vol up, with the cord still plugged in. I didn't realize there was a difference. I thought I just couldn't get into download mode.

djerick3 said:
Ok relax, in order to have your device recognized by your pc you must now put it in d/l mode (with power off, hold volume down and power until d/l mode starts) then run LG UP and try to downgrade. If that gives you the all to well known anti-rollback error then you need to download the hacked version of lg up (forget what it's called but it's in one of the rooting threads) and then downgrade. I struggled with the same thing a while back. My memory just isn't so good but I'm confident you'll figure it out.
Click to expand...
Click to collapse
UPPERCUT ?? thats the one your looking for

bassmek2 said:
UPPERCUT ?? thats the one your looking for
Click to expand...
Click to collapse
Yup that's it

get into download mode open device manager look for device with explanation mark right click and search for driver or u can show it where the driver is look for the folder where driver installed should be an lg folder C:\Program Files (x86)\LG Electronics\LG Mobile Driver if you don't have that folder then you haven't installed driver package download uppercut and get your kdz file I've had a few problems with a couple of kdz files I've downloaded they wouldn't install i think the file you need is H83020a_00_1107.kdz make sure when u go to flash that you have it in upgrade mode or else it will give you an error

SaintCity86 said:
Anyone?
It shows the boot verification error, mismatch_sig_len then immediately reboots and does it again.
Click to expand...
Click to collapse
Good day!
How did you solve your problem?
I have same trouble with my LG H830. When i try to boot in DL mode, appears small icon Dowload Mode and the phone restarting again with error:
[870] Boot verification fail!!
[920] cause : MISMATCH_SIG_LEN
How did you boot to download mode?
Thanks.

Galaxy S6 0mb TWRP / no OS! Help wanted, i do not want an brick

I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU

go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.

HowJesNo said:
go to download mode and flash stock firmware with ODIN. than flash twrp, enter recovery (twrp) before system. and boot to stock.
than try again.
Click to expand...
Click to collapse
Hi!
I got stock firmware from Updato and then began to flash with Odin and it seemed that it would work since it was actually doing something at first (while trying to flash ROM's Odin crashes) but then it gave an error and stopped :\ Here is an picture of Odin's log.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I guess you had better restore factory image, make sure the system comes back. then flash updated version OS.
You can trying to use ODIN to do that. or using fastboot flash .....
https://gs6.gadgethacks.com/how-to/unroot-restore-samsung-galaxy-s6-back-stock-0162155/
Hope to it is helpful.
DARKKi said:
I have Galaxy S6 and when i tried to install new ROM via usb-otg stick something strange happened and now my whole phone is unusable.
TWRP just says 0mb for internal storage and i cannot install anything since i cannot mount anything. I have looked pretty much all the "fixes" but nothing has helped so far :\ I have tried to format, wipe, change partition type, install, etc. And nothing has helped me so far. So if there are any ideas left please help :]
I think i still have root and when entering TWRP it does not ask password since i have done dm-verify long time ago.
Here is video showing some of the things: https://youtu.be/wXVVRBmRROU
Click to expand...
Click to collapse

Okay, i have new problem. After i tried to flash with odin now i got only one place i can boot into and it looks like this:
I downloaded Smart Switch and entered emergency recovery but i was met with this screen and i have no idea from where to get the code.

in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.

HowJesNo said:
in smart switch emergency upgrade and initialization, if will ask model and S/N.
model is SM-G920F and S/N in on the back of the phone. all caps.
Click to expand...
Click to collapse
Smart Switch did not even have that option but i tried it with Kies and got this

smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.

HowJesNo said:
smart switch should have same option. I found googling that in never versions that option was not functional due to Samsung not wanting people to debrand their phone. so older version is needed.
just got mine in a similar bootloop.
can u get into download mode?
If phone can't turn off do this:
- hold volume down + power, (that is reboot)
- as the screen goes black move finger to volume up + home key.
that should get you to download mode. now use odin to flash stock firmware.
Click to expand...
Click to collapse
I tried that before and i tried it now again and same result:

is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9

The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.

HowJesNo said:
is that firmware higher version than one previously installed?? i had that issue once!
G920FXXE5EQJ1........ try with any other with higher number. UK (BTU) is G920FXXU6ERC9
Click to expand...
Click to collapse
Hi! I got the Model name but for some reason i cannot find S/N in the box or anywhere else
vindau said:
The problem is hidden.img file.
Search in google "galaxy s6 hidden.img fail" and solved.
Click to expand...
Click to collapse
Thanks a lot for this! I was able to install stock rom.
---
But then trouble started again. Boot screen came up and then text and mount problems like "failed to mount efs (no such file or directory)" :crying:
Here is the video about it, anything i could do now? I installed TWRP and it still says internal storage 0mb and formatting has no effect.
Video - https://youtu.be/OBfhTRWUZeU

I got little progress. I found the S/N from back of the phone with torch which i could not see without (Thanks for Augustin @ XDA Discord for this!) and then i tried to use Smart Switch but it does not recognize the phone and only option is "Emergency Firmware Recovery" and it needs some recovery code.
Then i tried Kies and it does not detect the device either and i tried the option "Firmware Upgrade and Initialization" and typed out model and S/N and after that it said "SM-G920F" does not support initializing"
So anyone knows what i could do now? Seems like i am running out of options here
Augustin also said that i should try pit but i have never used that feature in Odin so help with that would be awesome if it can remedy this situation somehow

You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459

allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! I will begin investigating and learning!
Hopefully this would solve this damn problem
And thanks a lot for this info!

allensd.cordero said:
You need the .pit file according to your csc. Found it here: https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
Click to expand...
Click to collapse
Thanks a lot! Finally using pit got the partitions right and phone is working like a charm now! :]

This might be a bit late but I am also currently in the same situation with my S6. Somewhere in the thread it said something about pit files but I don't really understand what to do. For reference, my issue is the exact same as OP's with the unmountable partitions and unbootable system. Would someone be kind enough to help out? My device is a SM-G920F from Vodafone (UK)