Related
I'm on the stock JF6
and i have a build 1008 phone..
I can't seem to access download or recovery mode using the 3 buttons
anything I can do? My friend had flashed this random chinese I9000 ROM onto my captivate, so I flashed it back to stock using ODIN
recoverymode/download mode was fine on his ROM though
thoughts? cheers
and I can't return the phone as I live overseas!
Use ADB to get into download/recovery modes
And read the q&a sticky for more info and links.
Sent from my SAMSUNG-SGH-I897 using XDA App
avgjoegeek said:
Use ADB to get into download/recovery modes
And read the q&a sticky for more info and links.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
i'm using droid explorer
it has the same adb commands, but when I tell it to either reboot into recovery/download mode
it popups up on my PC screen and says are you sure, click "yes"
then nothing happens
or
it says "reboot operation not permitted"
bump
need urgent help pleaes
Do a search in the Development section for designgears' 3 button fix.
Hope that helps.
------
Axura 2.5CE
Samsung Galaxy S w/ AT&T
Mr.Pie[OCN] said:
i'm using droid explorer
it has the same adb commands, but when I tell it to either reboot into recovery/download mode
it popups up on my PC screen and says are you sure, click "yes"
then nothing happens
or
it says "reboot operation not permitted"
Click to expand...
Click to collapse
Learn to use the real ADB from the SDK.
Also, if your phone is not rooted, the reboot command does not work.
http://forum.xda-developers.com/showthread.php?t=812434
fixed
nvm
thanks all
do u know what i did was use a different usb cable dont use the one that comes with the phone. i used a different cable and download/recovery mode comes up. hope this helped
For those who need to know....
If you have a 1008 build (like me). Most of the time the buttons on the phone will not work. (Most meaning if your running certain custom ROMs the functionality returns until you go back to stock.)
I end up having to use ADB to reboot my phone into download or recovery in between flashing back to stock and going onto the new ROM because the buttons never work when I want them too, and it's become almost second nature to me
In order for ADB commands to work - you do NOT need your phone Rooted (otherwise I'd have been fubard a long time ago). You do need USB Debugging turned on or the commands won't work.
Also.. you only need Root/SU if you plan on using ADB shell commands and wish to play within the phone itself. Def not suggested for those who never have played with a shell before.
If you're going to be flashing different roms then next time you go back to stock use this one:
http://forum.xda-developers.com/showthread.php?t=818439
I've used it on my 1008 captivate probably 100 times so I know it works
avgjoegeek said:
In order for ADB commands to work - you do NOT need your phone Rooted (otherwise I'd have been fubard a long time ago). You do need USB Debugging turned on or the commands won't work.
Also.. you only need Root/SU if you plan on using ADB shell commands and wish to play within the phone itself. Def not suggested for those who never have played with a shell before.
Click to expand...
Click to collapse
Oops. I had totally forgotten that was for the shell on the phone cause thats how Ive been doing it lately when I flash. Thanks for correcting everyone
Sent from my Captivate
abhele said:
do u know what i did was use a different usb cable dont use the one that comes with the phone. i used a different cable and download/recovery mode comes up. hope this helped
Click to expand...
Click to collapse
Wrong the one that came with the phone will work for download mode everytime. it is the other 3rd party usb cords that do not work sometimes.
I have a 1008 batch phone and have never had a single problem flashing ROMs.
I've got a Nexus S that got screwed up from the 2.3.6 OTA. It can go into fastboot mode and recovery mode but it will not boot into Android. When you try to unlock the bootloader you get the unlock screen, can select yes but when you press power the device just hangs. If you go into download mode you get a screen about unlocking the bootloader. Odin detects the device, retrieves the pit, sends the image you want to flash to the phone and the phone says image verified. Then it just does nothing. Odin just sits there and there is no other feedback on the device. It looks like if the bootloader is locked you cannot flash with Odin either. Or at least if the device goes into the strange unlock bootloader screen instead of the true download mode screen Odin flashes fail. I have searched and searched and cannot find a resolution to this problem. Has anyone figured out why some devices hang when you try to unlock the bootloader and has anyone found a way to work around this problem. I am trying to help a guy out and don't want to give him back his phone telling him there is simply nothing I can do for him. He has a TMO device in Thailand. Samsung service here will only service phones sold in Thailand through authorized channels. Since it has a TMO model number they won't touch it.
push clockwork with fastboot
tylerwatt12 said:
push clockwork with fastboot
Click to expand...
Click to collapse
Can't. Clockwork recovery image is sent to the phone. Then it says failed because bootloader lockaed, use "fastboot oem unlock" to unlock the bootloader. And on the phone it says something like Flash FailedState LOCKEDbootloader.
Without being to unlock the bootloader no image can be flashed. I even tried a stock boot image just for a test and it was rejected in the same manner. With the bootloader being locked down it won't let me flash anything. I would need a stock signed rom with android-info.txt and android-product.txt files. I have yet to find one. I think that would flash the phone.
Odin is a no go also. The images are pushed to the phone, the phone verifies the images and then doesn't flash them due to the bootloader being locked. And in download mode I don't get the shovel guy I get a screen telling me to unlock the bootloader but I am connecting in the manner that Odin can see and talk to the phone. The phone just refuses to flash the images once they are downloaded to it.
same for my nexus s,how to solve it?thx
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
splinter701 said:
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
Click to expand...
Click to collapse
Do you mean getting stuck when you try to unlock the bootloader (fastboot oem unlock) or can you not even get into the bootloader at all.
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
maybe try on another pc?
splinter701 said:
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
Click to expand...
Click to collapse
Reinstall drivers?
Sent from my Nexus S 4G using xda premium
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Sent from my Nexus S using xda premium
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
splinter701 said:
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
Click to expand...
Click to collapse
=] your most welcome sir
Sent from my Nexus S using xda premium
YourMainDude said:
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
link
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I tried this but it still requires bootloader to be unlocked so it didn't work. My problem is similar to OP's. My phone appears to offer the bootloader unlock option, but selecting 'yes' to unlock fails to actually unlock. So nothing else works to restore the ROM. Though the phone does accept commands from adb just fine.
Anyway, I'm just posting this in case anyone else has the the same issue w/ bootloader not unlocking.
I have spent weeks trying to fix my phone and im really fustrated!
i started with rooting my phone with the ice cream sandwhich rom,
everything was okay for a few days and then my middle menu button
stopped working programs keep crashing wireless doesnt work properly
ect basically my phone is very hard to use!
so i researched over weeks for what to do downloaded a stock rom and tried
to put my phone in to download mode, didnt work
i bought the clockwork apps but i get an error saying phone is not rooted
although obviously it is as i have the custom os on it
please somone help me before i throw my phone at a wall
What model do you own? Ive got atat's version, and can probably help you out of your situation.
Sent from my SGH-I777 using xda premium
hannah_jane_johnson89 said:
I have spent weeks trying to fix my phone and im really fustrated!
i started with rooting my phone with the ice cream sandwhich rom,
everything was okay for a few days and then my middle menu button
stopped working programs keep crashing wireless doesnt work properly
ect basically my phone is very hard to use!
so i researched over weeks for what to do downloaded a stock rom and tried
to put my phone in to download mode, didnt work
i bought the clockwork apps but i get an error saying phone is not rooted
although obviously it is as i have the custom os on it
please somone help me before i throw my phone at a wall
Click to expand...
Click to collapse
You need to try to put your phone into download mode with adb. Download Android-sdk and get the the gingerbread stock odin for your phone. Take the Android -sdk and put in on the root of your hard drive on your computer. The go to the start menu on you computer and type cmd if you are using window. Which I assume you are. Ok in the command type cd\android-sdk\tools. Now have your phone on and plugged up to your usb. Then type adb devices to make sure the device is there. Also you will need to install the Samsung driver for your phone before you use cmd. Ok sorry I forgot that. Now after you adb devices and you see your phone . Type adb reboot download. Your phone should now reboot into download mode. Open up odin and run it.
Sent from my SPH-D710 using Tapatalk 2
Plug your phone into your computer, press Power,Volume up and Volume down all at the same time for 10-12 seconds, then you SHOULD be in download mode, as long as your phone is functioning at the moment you shouldn't need all those files, although they are quite helpful in the end as you can use adb for lots of things. Hope this helped.
Sent from my SGH-I777 using Tapatalk 2
So when I was trying to unlock my phone via my fingerprint, i didn't have my finger on there correctly 1 to many times and locked my phone. I couldn't remember my passcode and had to log into it via my google account. It then restarted and now won't boot. Gives me the "custom binary blocked by FRP lock" Tried flashing the root tar file and TWRP tar file with no luck. Don't know what to do as I have never came across this before. Any help is appreciated. Phone is rooted but stock.
They holding volume up, home and power when the phone is off. Should get you into recovery. Then do a factor reset. Not sure if this will work though.
Sent from my SM-N920P using Tapatalk
CBRRider said:
So when I was trying to unlock my phone via my fingerprint, i didn't have my finger on there correctly 1 to many times and locked my phone. I couldn't remember my passcode and had to log into it via my google account. It then restarted and now won't boot. Gives me the "custom binary blocked by FRP lock" Tried flashing the root tar file and TWRP tar file with no luck. Don't know what to do as I have never came across this before. Any help is appreciated. Phone is rooted but stock.
Click to expand...
Click to collapse
The phone is rooted so flashing the tar file for root or TWRP is useless because its already rooted. The problem is you locked the phone with your fingerprint. Did you make a backup? You can restore that and you should be good beause it resets the device completely. However, if you did not, then flash the stock tar file in Odin and you'll be good to go. You can find the stock tar file here...http://forum.xda-developers.com/showpost.php?p=62536311&postcount=1
I can confirm it works. You will just have to reroot because it returns the phone to stock out the box.
Due to FRP (Factory Reset Protection) by Google, You won't be able to flash any custom files to phone, it'll always fail, To be able to flash any custom files, You have to enable "allow OEM unlocking" from developer menu, which will disable the FRP lock, But this is not possible in your case since you can't access the menu, But since you're rooted, i assume that you enabled "USB Debugging", So now connect the phone to PC and run CMD and try the following commands one by one,
adb devices # this should list your device
adb shell
su
cd data/system
ls #this will list all files in that dorectory
rm *.key #to delete all .key files which contains the lock
and you're done.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
Due to FRP (Factory Reset Protection) by Google, You won't be able to flash any custom files to phone, it'll always fail, To be able to flash any custom files, You have to enable "allow OEM unlocking" from developer menu, which will disable the FRP lock, But this is not possible in your case since you can't access the menu, But since you're rooted, i assume that you enabled "USB Debugging", So now connect the phone to PC and run CMD and try the following commands one by one,
adb devices # this should list your device
adb shell
su
cd data/system
ls #this will list all files in that dorectory
rm *.key #to delete all .key files which contains the lock
and you're done.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
How does one use ADB when its stuck like this?
hshah said:
How does one use ADB when its stuck like this?
Click to expand...
Click to collapse
He just said his phone is rooted, And i assumed that USB Debugging is enabled, So if you have the same case, You can connect your phone to PC and start using ADB as normal, Then you can follow my guide to get rid of any kind of screen security there, Simple like that.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
He just said his phone is rooted, And i assumed that USB Debugging is enabled, So if you have the same case, You can connect your phone to PC and start using ADB as normal, Then you can follow my guide to get rid of any kind of screen security there, Simple like that.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
If your phone doesn't boot to system, Then you can't use my method, My method was all about saving the data on the phone, And if the data wasn't important to you, you can always flash the stock FW for your phone, Or even wipe the phone from recovery, And i can see you had no option since system doesn't boot up.
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
If your phone doesn't boot to system, Then you can't use my method, My method was all about saving the data on the phone, And if the data wasn't important to you, you can always flash the stock FW for your phone, Or even wipe the phone from recovery, And i can see you had no option since system doesn't boot up.
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
Interestingly I have just recovered it by flashing stock through ODIN and all I lost was root and Xposed. All my data etc is still there! :highfive:
hshah said:
Interestingly I have just recovered it by flashing stock through ODIN and all I lost was root and Xposed. All my data etc is still there! :highfive:
Click to expand...
Click to collapse
Good for you, And that's because you've flashed an One-Package FW (AP only) which is simillar or newer than the one you had, In that case all your of your settings and data will be still there, And that applicable also for the screen security, Which you'll notice it being there if you had one before your phone got stucked at boot screen, Now i see what your problem was, Before now i thought it was about security. :highfive:
Sent from my iPhone 6 using Tapatalk.
mirosaw2 said:
Good for you, And that's because you've flashed an One-Package FW (AP only) which is simillar or newer than the one you had, In that case all your of your settings and data will be still there, And that applicable also for the screen security, Which you'll notice it being there if you had one before your phone got stucked at boot screen, Now i see what your problem was, Before now i thought it was about security. :hoghfive:
Sent from my iPhone 6 using Tapatalk.
Click to expand...
Click to collapse
I actually didn't have any screen security. I know I had turned on OEM and USB Debugging, so not sure how OEM got turned off.
Anyways glad its sorted! Just finished re-rooting and I am back up and running!
odin flash fails
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
mevj said:
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
Click to expand...
Click to collapse
You need to flash stock ROM, not custom ROM.
hshah said:
You need to flash stock ROM, not custom ROM.
Click to expand...
Click to collapse
where can i find this stock rom
mevj said:
Hey ..
I have a sprint note 5..I was trying to root my phone but somehow the instructions I was following didn't have anything about developer options and lock off from setting..
Now after I restarted I cannot boot up my device .and get the
Frp lock error .
I tried refreshing custom rom through odin, but it keeps failing..
Please help.
Click to expand...
Click to collapse
I have the exact same problem and tried flashing a stock rom but it fails as well.
did you have any luck??
mine is stuck too i turned off oem unlock and resarted phone now it wont boot i tried odin to stock oi6 but i did ota to oj6 which i see isnt released yet, so does anyone know if and when they are going to release OJ6 FW? and does anyone know how to fix this problem
How did you do it?
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
How do you get it to flash via odin? I keep trying and get a failure of the lock. Is there a specific method you did that i am not doing right?
Please help if you can. I don't want to have to go to warranty and pay a hefty fee.
I too am suck in FRP lock. I also can't get into TWRP or can't flash it on the phone.
I would really appreciate it.
psychokrod said:
How do you get it to flash via odin? I keep trying and get a failure of the lock. Is there a specific method you did that i am not doing right?
Please help if you can. I don't want to have to go to warranty and pay a hefty fee.
I too am suck in FRP lock. I also can't get into TWRP or can't flash it on the phone.
I would really appreciate it.
Click to expand...
Click to collapse
Try flashing this one in Odin http://forum.xda-developers.com/showthread.php?t=3273483
hshah said:
I connected the phone to the PC whilst it was in Download Mode (that is the only mode I can boot into and it wouldn't see it).
Too late now anyway, as I've just flashed stock through ODIN
Click to expand...
Click to collapse
Did THE stock flash worked for you? cause i can only boot in download mode also. I didnt know about this lock.... Is it so i have to walt for 3 days to use my phone?
liobeir said:
Did THE stock flash worked for you? cause i can only boot in download mode also. I didnt know about this lock.... Is it so i have to walt for 3 days to use my phone?
Click to expand...
Click to collapse
Yes it did. Download the stock firmware from Sam Mobile and just flash it through ODIN whilst in Download mode. It kept all my apps and settings too.
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.