Database Info

Semi Brick, STUCK ON DOWNLOAD MODE. HELP

Hello everyone, I totally pulled a noob earlier, with all the excitement going around with the official ICS update going around, accidentally I pushed a 19100 ROM into my sgs2 by sprint; and now my device is semi brick, neither Kies, Odin nor SimpleDownloaderTool for SPH-D710 recognizes the device, after downloading the correct drivers into my computer.. now what do I do?

If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.

sgs4g SGH-T959V always reboot into download mode, even after successful oneclick
lumin30 said:
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
Click to expand...
Click to collapse
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.

Pro tip: Open a new thread if you need to ask a question or need help. Don't "hi-jack" other threads. (considering that the original thread is from 2012)
But it's done...
teevoo said:
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
Click to expand...
Click to collapse
Did you follow @lumin30's guide?
teevoo said:
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Click to expand...
Click to collapse
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
teevoo said:
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Click to expand...
Click to collapse
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.

bhundven said:
Did you follow @lumin30's guide?
Click to expand...
Click to collapse
Yes. Oh and I made several posts (not hijack ) regarding this issue elsewhere in the forum but got no response. One thing I forgot to mention in this version is that originally, the download mode on phone was triggered physically somehow. My uncle accidentally dropped the phone in water. He then blew it dry with a strong fan and must have turned it back on too early. Since then the phone's been in download mode.
bhundven said:
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
Click to expand...
Click to collapse
I'm now wondering if there is a program that can do a reset like heimdall/odin without going through the whole reflashing process. Assuming the phone's memory components haven't been physically damage, at least this would mean I can restart the phone to normal mode quickly.
bhundven said:
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
Click to expand...
Click to collapse
Ok, I'll try to find a different computer to do this with, although right now I'm thinking USB is not the case as I have successfully performed the same flash on a different sgs4g and it works just fine (the difference was that phone was never stuck in download mode to begin with). For the problem phone, I have tried a couple of ports and 2 different cables on my Mac. From what you just told me, perhaps the phone's usb port is the culprit.
Thanks for your reply, and thanks for all the programming work you've contributed to this forum :good:

Help pls!!!! 20$ in it!!!

New that would get attention. Is there anyone out there that is dedicated to helping for a lil cabbage? I have this tf101 transformer that i cant seem to get rooted. Why is it so gosh dern hard to root one? I have followed all methods and tryed diff methods. The emulator runs but root is still not acheived. I have not bricked it. Its running ics. Ive rooted phones and tablets since the evo 4g..... this garbage a$$ tablet is without a doubt one of the worst i have ever had the displeasure of owning. Nexus 7,,,samsung note 1,,,note 2,,,,,,note 10.1,,,,,htc first,,,,evo 4g,,,,blackberry tour....AND NONE HAVE EVER BEEN THIS HARD TO ROOT. I wont buy another asus anything.
So,if som1 could explain what im doing wrong thatwould be great...also 20 buck in the paypal acct.....if you can think of it. Ive done it. Next is taking it apart to see what makes it tick

First thing - Does your tablet get seen by your PC in either APX or ADB mode? And did you update the driver using the Naked Drivers?
Last time I rooted I used Wolf's Method 3. Here is what I did:
Plugged in my tablet to my PC via USB (win 7 PC).
After the device was detected, I went to Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://forum.xda-developers.com/showthread.php?t=1998650
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Next, run the following commands (from Wolf's Exploit, Method 3)
Code:
adb push TWRP.blob /sdcard/
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
adb reboot
exit
It will reboot. Once you see the ASUS loading screen, you can continue:
Code:
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)
Now you can install your favorite SuperUser app.
Download a zip flashable SuperUser
ChainsDD SuperUser: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
ClockWorkMod SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Chainfire SuperSU: http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
I like the CWM SuperUser at the moment, but all three will work.
Put these where you can see them from the recovery you flashed. If using TWRP, it needs to be in the /sdcard/ directory or on the microSD card.
Next, reboot to recovery. Hold VOL DOWN and POWER for 12-15 seconds until you see some white text in the upper left of the screen. Release both buttons and tap VOL UP to enter RCK (Recovery).
Once in recovery, tap Install and choose the SuperUser.zip file to install. Once installed, you are rooted.
Another time I rooted, I used EasyFlasher and here is the thread on my rooting guide for that if you are interested: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once again, if you cannot get your tablet detected by ADB or APX, chances are it is a bad USB cable.

harley1rocker said:
-snip-
Click to expand...
Click to collapse
If you've 'tried everything', then it's likely Bad drivers or a bad USB cable, I'll assume you've tried my tool, the idcrisis tool, Easyflasher and wolf's method (Described by Fred) above.
If you'd like me to remote desktop you with Teamviewer to make sure your drivers are good I can do that, but if you've really tried everything then it's likely a bad cable.
ToD

To test the cable, simply transfer a file through USB with a known md5 signature, then verify it again after it's been transferred. You can use something like AFV to check the md5 once on the device. The bigger the file the better; the more chances it has to fail.

I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS

harley1rocker said:
I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS
Click to expand...
Click to collapse
Glad you got it sorted.

who got the 20 dollars
Sent from my Transformer TF101 using xda premium

stesteste said:
who got the 20 dollars
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Wasn't me. But I did not respond for the $20, I am just a good guy.

No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.

harley1rocker said:
No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.
Click to expand...
Click to collapse
We're all here to help, it really isn't about $, for me really it's just seeing that someone cares to donate that makes my day.. It's all about the passion of android though As fred will probably tell you.

[Q] I need to return a broken rooted phone, and have a question before I do so...

I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.

SevnSins said:
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.

Lgrootnoob said:
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Click to expand...
Click to collapse
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks

SevnSins said:
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
Click to expand...
Click to collapse
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.

SevnSins said:
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
Click to expand...
Click to collapse
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.

Lgrootnoob said:
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Click to expand...
Click to collapse
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help

SevnSins said:
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
Click to expand...
Click to collapse
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )

Lgrootnoob said:
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Click to expand...
Click to collapse
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.

SevnSins said:
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.

Lgrootnoob said:
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Click to expand...
Click to collapse
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help

SevnSins said:
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
Click to expand...
Click to collapse
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh

Lgrootnoob said:
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Click to expand...
Click to collapse
well... where wasn't a fire, but I got a pretty cool spark. although; it still didn't "kill it" all the way. it's still try to boot up. I just decided to send it in, if they charge me for it, I'll just pay it. my job is taking over my phone bill anyways, so I shouldn't need to worry about it.
thank again for your help :good:

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!

Please Help, Stuck in TWRP.

So this morning i got a notification on my phone about updating android version. In my half asleep state, i click sure, update, and rolled over to go back to sleep. i checked on it in a couple minutes and saw that it just booted into twrp and sat there because i have a custom recovery installed it can't do its normal processes. I reboot the phone, only instead of booting up like normal, it goes to the lg screen as usual and then straight into twrp. my first action was to reflash what i was using before, wich was H830_20A_DeOdexed by lordodin912. it flashed fine, but still didn't boot. then i thought maybe it got further into the update then i thought and i need a 20c rom, so i tried flashing 20c+kernel also by lordodin912. Still nothing. So sine then i have tried flashing a few things both 20a and 20c and none of them seem to be changing my situation as soon as it boots its just goes straight back into twrp.
Anyone have any ideas? this is just getting really frustrating, i would love to know what i messed up and how i can fix it.
edit* TheRealJDTram posted a solution, if anyone has the same problem
TheRealJDTram said:
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
Click to expand...
Click to collapse

konchar said:
So this morning i got a notification on my phone about updating android version. In my half asleep state, i click sure, update, and rolled over to go back to sleep. i checked on it in a couple minutes and saw that it just booted into twrp and sat there because i have a custom recovery installed it can't do its normal processes. I reboot the phone, only instead of booting up like normal, it goes to the lg screen as usual and then straight into twrp. my first action was to reflash what i was using before, wich was H830_20A_DeOdexed by lordodin912. it flashed fine, but still didn't boot. then i thought maybe it got further into the update then i thought and i need a 20c rom, so i tried flashing 20c+kernel also by lordodin912. Still nothing. So sine then i have tried flashing a few things both 20a and 20c and none of them seem to be changing my situation as soon as it boots its just goes straight back into twrp.
Anyone have any ideas? this is just getting really frustrating, i would love to know what i messed up and how i can fix it.
Click to expand...
Click to collapse
i am have the same situation ....quite worry about it.

kugcsq said:
i am have the same situation ....quite worry about it.
Click to expand...
Click to collapse
Same here as well. I've reverted back to using my PRIV until we can figure this out.

Wouldn't lgup help?
Sent from my LG-H830 using XDA-Developers Legacy app

And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.

TheRealJDTram said:
Same here as well. I've reverted back to using my PRIV until we can figure this out.
Click to expand...
Click to collapse
PRIV?

konchar said:
PRIV?
Click to expand...
Click to collapse
BlackBerry PRIV. My previous phone.

TheRealJDTram said:
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
Click to expand...
Click to collapse
thanks for your help, where do i run these? i used minimal_adb_fastboot before for adb commands, but it is telling me that dd is not recognized as a command. im using that im using the commands in the wrong place, can you elaborate on how to input it?

konchar said:
thanks for your help, where do i run these? i used minimal_adb_fastboot before for adb commands, but it is telling me that dd is not recognized as a command. im using that im using the commands in the wrong place, can you elaborate on how to input it?
Click to expand...
Click to collapse
With your phone booted into twrp, connect to computer, run ADB devices. Verify that your device is detected. If it is, run "ADB shell". You'll be brought to a Linux prompt. Mine had some odd characters at the prompt, looked corrupt, but it worked anyways. Paste the two commands that are listed into that prompt one at a time and pressing enter after each. It should execute them on your phone. If you can't get that to work and you feel you could type the commands out using the on screen keyboard, you can select advanced in TWRP and launch Terminal.

TheRealJDTram said:
With your phone booted into twrp, connect to computer, run ADB devices. Verify that your device is detected. If it is, run "ADB shell". You'll be brought to a Linux prompt. Mine had some odd characters at the prompt, looked corrupt, but it worked anyways. Paste the two commands that are listed into that prompt one at a time and pressing enter after each. It should execute them on your phone. If you can't get that to work and you feel you could type the commands out using the on screen keyboard, you can select advanced in TWRP and launch Terminal.
Click to expand...
Click to collapse
you are awesome. that did the trick. bootlooped a few times, and then went on to setting up android. thanks alot for your help.

konchar said:
you are awesome. that did the trick. bootlooped a few times, and then went on to setting up android. thanks alot for your help.
Click to expand...
Click to collapse
No problem. I had the issue as well and just started trying everything I could find on here.

TheRealJDTram said:
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
Click to expand...
Click to collapse
i wish i could see this early. i spent a whole night to fix it.
Finally i use this way:
Here is how you should do it:
1. Download LG bridge on your computer.
2. Switch off your Device, pull out your battery.
3. Attach your USB Cable from desktop to mobile
4. Hold volume up button, and put your battery while holding it. It should switch on itself if the USB is attached and you are holding volume up before putting in battery.
5. Once its on Bootloader, flash firmware recovery from LG Bridge.

Please help! I too was stuck in the TWRP, tried those two commands but now I'm getting red triangle and "Device Corrup, Cannot boot" error.
Tried to firmware repair with LG Bridge (entered Download Mode) but it cannot find any phone, even if it shows up on my PC as a serial LG COM port.
LG G5 H850 - Unlocked BL - was running Fullmics v1.5

Same happened to me, except I didn't get a prompt. I was playing chess and it said something about shutting down to update.
The commands worked.
If you have TWRP you can go Advanced > Terminal and just type it in there. !!!Make sure you double-triple check the spelling, typos will effff your shhht up!!!

Same exact thing happened to me, stuck looping back into TWRP. Used UPPERCUT to start LGUP (phone was being ID'd as an h1 instead of h830). Went from broken 20c to the 20a kdz file. Of course, lost everything on the internal storage and root and TWRP but just ran the easyrecowvery auto script and regained TWRP. Flashed 20c back on top and the NSS5.5 kernel package and am finally back where I was before the whole debacle. I'll wait and see if Autoprime preps a tested flashable version, maybe try again then.
BTW, I think the 20a deodex by lordodin912 is partial; it requires the complete 20a to be flashed first as a backbone. I don't think it's bootable by itself.