[Q] Stuck in download mode and broken Volume Buttons - Galaxy S II Q&A, Help & Troubleshooting

Hello there experts,
The volume buttons of my S2 don't work at all. I bought it 2nd handed and the seller told me this beforehand. It seems they were broken in the process of replacing the screen, God knows who made such mistake.
I installed cyanogenmod with CM installer, as it does the job almost automatically without the need to go to the Download mode.
Once everything was installed and set up I thought, well let's try to remove that yellow triangle image...
After installing Triangle Away, it brought me to the download mode. I knew it was risky but I thought the phone would restart normally.
If I remove the battery, it'd always go back to download mode, and there is no way to start the phone normally.
as I'm unable to either press VOL up / down, i'm stuck in the download mode.
The only solution that comes to mind is disassembling the phonem, play with the volume buttons and see what's happening there, and try to fix it (if there's even a possible fix)
Does that look like it could be fixed? or it would need to replace and solder something else?
also, is there a way to get rid from the DL mode with some USB method on the PC? also flashing the phone as it is right now is impossible I guess.

this is what I found in the volume parts,
it's the first time I dare to disassemble a device like this. I have no clue about this kind of stuff;
{
"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"
}

Try ADB Fastboot commands. Maybe it detects S2 in Download Mode. But not sure about that. First of all,
Download Samsung USB Drivers.
Download Minimal ADB & Fastboot
Connect USB Cable
Open that command line tool
Issue command 'adb devices' or 'fastboot devices'. If it detects your phone, your IMEI will be shown. Then try,
ADB Fastboot Reboot System
If all good, your S2 will be rebooted.(presuming that you're Rooted). If it doesn't you have to repair those keys or try to press them by some sort of sharp thing but easy you go, otherwise you will be damaging your phone. I recommend you ti get them repaired

syedbilal093 said:
Try ADB Fastboot commands. Maybe it detects S2 in Download Mode. But not sure about that. First of all,
Downliad Samsung USB Drivers.
Download Minimal ADB & Fastboot
Connect USB Cable
Open that command line tool
Issue command 'adb devices' or 'fastboot devices'. If it detects your phone, your IMEI will be shown. Then try,
ADB Fastboot Reboot System
If all good, your S2 will be rebooted.(presuming that you're Rooted). If it doesn't you have to repair those keys or try to press them by some sort of sharp thing but easy you go, otherwise you will be damaging your phone. I recommend you ti get them repaired
Click to expand...
Click to collapse
Thanks for your help.
Yes I was root, the solution you gave looks like it could have worked to get rid from the download mode.
Anyways, the flex that connects the buttons internally was broken, maybe this was a good thing that had to happen to get it repaired, as sooner or later I'd have to do that.
Finally I found a guy who is a beast at these things and he had lots of parts of S2's, so he repaired it in about 10 minutes.
Now I have a fully functional S2. It's still a good device in my opinion.
I bought it 2nd handed for a lower price that any chinese phone, good cam and speakers... makes me wonder if we should get ex-flagship devices instead of newer chinese cheap phones. I paid only 55euros for this phone, I know it's usually more expensive. After using a chinese android phone, my experience is much better with the S2.
So far I'm using cyanogenmod11 as my first rom. I know this question can be dumb and repetitive, but could you tell me what are the best roms/rom in your honest opinion? As usually, the smoothest running and more lasting battery are the most demanding needs.
Thanks again man!

Thats good to hear that. Yeah chinese phones are not good at all. Samsung S2 is a demanding phone still. I am also using S2.
As you asked about ROMs, personally i haven't rooted my S2. But in my opinion, i am listing three links about Top Custom ROMs. Visit them you'll find something for your S2.
http://www.cnet.com/how-to/best-custom-roms-for-the-samsung-galaxy-s2/
http://androidcure.com/best-kitkat-roms-samsung-galaxy-s-ii-i9100/
http://www.androidpit.com/best-5-custom-roms-for-the-galaxy-s2
Visit CNET first. In my honest opinion, stock Rom is the best ROM if we talk about stability,smoothness & performance. . Visit them you'll be able to find a ONE for your's.

syedbilal093 said:
Thats good to hear that. Yeah chinese phones are not good at all. Samsung S2 is a demanding phone still. I am also using S2.
As you asked about ROMs, personally i haven't rooted my S2. But in my opinion, i am listing three links about Top Custom ROMs. Visit them you'll find something for your S2.
http://www.cnet.com/how-to/best-custom-roms-for-the-samsung-galaxy-s2/
http://androidcure.com/best-kitkat-roms-samsung-galaxy-s-ii-i9100/
http://www.androidpit.com/best-5-custom-roms-for-the-galaxy-s2
Visit CNET first. In my honest opinion, stock Rom is the best ROM if we talk about stability,smoothness & performance. . Visit them you'll be able to find a ONE for your's.
Click to expand...
Click to collapse
I'm not sure about the s2 but in other devices, the stock updated roms+root access have always been the best configuration. Thing is I don't like TouchWhiz much.
Thanks for the info man. I'll check that out.
Enviado desde mi M9Pro mediante Tapatalk

Yeah check them out. No problem man. ! I also dont like TouchWiz. I like HTC Sense.:thumbup:

Related

Mobile phone for help

我的手机amaze,已经官方解锁了,super-cid写入失败,从新写入系统时,失败了。可是电脑端显示成功,我重启手机,手机开不开机,也进不去HBOOT,屏幕只能显示四角各有个感叹号,中间一个灰色的'HTC'的字样,怎么办求解!知道答案的请发 Edited by Moderator.
——————我是一个中国学生!翻译不好请见谅!—————————————————————————————————————————
My mobile phone amaze, have unlock, super-cid write failure, from the new writing system, failed. But the computer terminal display success, I restart mobile phone, mobile phone to open the boot, cannot also go in the HBOOT, the screen shows only four corners of an exclamation point, the middle of a grey 'HTC'', how to do to solve! Know the answer please Edited by Moderator. Mr. lu! Thank you very much.
boxboooon said:
我的手机amaze,已经官方解锁了,super-cid写入失败,从新写入系统时,失败了。可是电脑端显示成功,我重启手机,手机开不开机,也进不去HBOOT,屏幕只能显示四角各有个感叹号,中间一个灰色的'HTC'的字样,怎么办求解!知道答案的请发 [email protected] 卢先生!谢谢你们!
——————我是一个中国学生!翻译不好请见谅!—————————————————————————————————————————
My mobile phone amaze, have unlock, super-cid write failure, from the new writing system, failed. But the computer terminal display success, I restart mobile phone, mobile phone to open the boot, cannot also go in the HBOOT, the screen shows only four corners of an exclamation point, the middle of a grey 'HTC'', how to do to solve! Know the answer please [email protected] Mr. lu! Thank you very much.
Click to expand...
Click to collapse
当你用4个惊叹号宏达屏幕上,尝试做此命令
fastboot devices
然后让我们知道,如果你看到什么
___________________________________
When you are on the HTC screen with 4 exclamation marks, try to do this command
fastboot devices
and then let us know if you see anything
Sorry if the chinese is bad, I'm using google translate
Keylogger_0 said:
当你用4个惊叹号宏达屏幕上,尝试做此命令
fastboot devices
然后让我们知道,如果你看到什么
___________________________________
When you are on the HTC screen with 4 exclamation marks, try to do this command
fastboot devices
and then let us know if you see anything
Sorry if the chinese is bad, I'm using google translate
Click to expand...
Click to collapse
Unable to access FastBoot,Only one interface
boxboooon said:
Unable to access FastBoot,Only one interface
Click to expand...
Click to collapse
Did you plug in usb cable? Do you have fastboot drivers installed on the computer?
Keylogger_0 said:
Did you plug in usb cable? Do you have fastboot drivers installed on the computer?
Click to expand...
Click to collapse
I don't have this mode drive, only HTC sync. Oh, God, my mobile phone is dying! Can only send HTC to repair? Though I know I repaired the possibility is very small, but I am very grateful to you Keylogger_0! Thank you. Thank you XDA!
谢谢Keylogger_0!祝你健康快乐~
boxboooon said:
I don't have this mode drive, only HTC sync. Oh, God, my mobile phone is dying! Can only send HTC to repair? Though I know I repaired the possibility is very small, but I am very grateful to you Keylogger_0! Thank you. Thank you XDA!
谢谢Keylogger_0!祝你健康快乐~
Click to expand...
Click to collapse
You don't need to send to HTC for repair. More likely than not, we can fix it. If not, then yes, you send to HTC.
Okay, I can't read chinese, which makes things difficult.. but all the answers will require the user to be able to read some english anyways, so...
First: What did you do before the issue happened? Did you try to install the RUU? Were you going for s-off? What EXACTLY did you do before the issue.
Second: What happens when you turn on the phone while holding the down volume button? The feedback I see from people having this issue, it seems most are able to access the bootloader..
Third: Did you google "4 exclaimation marks htc"? There are a LOT of answers out there that may help you, and I have yet to find anything that says your device is bricked..
As this is the first time I have seen someone have your issue the most important question is "WHAT DID YOU DO BEFORE ISSUE".. so we can make sure people do NOT do that! The community can probably help if you can work around the language barrier a bit.
Silentbtdeadly said:
Okay, I can't read chinese, which makes things difficult.. but all the answers will require the user to be able to read some english anyways, so...
First: What did you do before the issue happened? Did you try to install the RUU? Were you going for s-off? What EXACTLY did you do before the issue.
Second: What happens when you turn on the phone while holding the down volume button? The feedback I see from people having this issue, it seems most are able to access the bootloader..
Third: Did you google "4 exclaimation marks htc"? There are a LOT of answers out there that may help you, and I have yet to find anything that says your device is bricked..
As this is the first time I have seen someone have your issue the most important question is "WHAT DID YOU DO BEFORE ISSUE".. so we can make sure people do NOT do that! The community can probably help if you can work around the language barrier a bit.
Click to expand...
Click to collapse
1:问题发生前,我在试图写入“super-cid” 但是写入失败,原因是没有s-off。在这时,手机的情况是:官方解锁,没有s-off。
2:打开手机,按住下音量按钮时,就是图上的那样,无法进入hboot
提醒别人不要用线刷的方法将官方的zip解锁包第二次刷入官方解锁的手机了!因为这样做会使字库里的数据被擦掉却没有再次写入!
我是学生,现在开学了,回复很慢见谅~
1: problems before they occur, I was trying to write " super-cid " but write failed, because there is no s-off. At this time, the mobile phone is: unlock, no s-off.
2: open mobile phone, press and hold the volume buttons, is a map of it, can not enter the HBOOTRemind the others do not use wire brush method will be the official zip unlock the package second brush into the official unlocked mobile phone! Because it will make in the font data erased but not write again!I am a student, school now, the reply is very slow. ~
boxboooon said:
1:问题发生前,我在试图写入“super-cid” 但是写入失败,原因是没有s-off。在这时,手机的情况是:官方解锁,没有s-off。
2:打开手机,按住下音量按钮时,就是图上的那样,无法进入hboot
提醒别人不要用线刷的方法将官方的zip解锁包第二次刷入官方解锁的手机了!因为这样做会使字库里的数据被擦掉却没有再次写入!
我是学生,现在开学了,回复很慢见谅~
1: problems before they occur, I was trying to write " super-cid " but write failed, because there is no s-off. At this time, the mobile phone is: unlock, no s-off.
2: open mobile phone, press and hold the volume buttons, is a map of it, can not enter the HBOOTRemind the others do not use wire brush method will be the official zip unlock the package second brush into the official unlocked mobile phone! Because it will make in the font data erased but not write again!I am a student, school now, the reply is very slow. ~
Click to expand...
Click to collapse
Download this attachment, extract it to desktop, and then run Vars.bat file and attach the file DIAGNOSTIC.LOG when its done
Don't forget to attach the file 'DIAGNOSTIC.LOG' which will look like this:
{
"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"
}
_______________________________________
下载这个附件,解压缩到桌面,然后运行Vars.bat文件和附加文件DIAGNOSTIC.LOG时
不要忘记附加文件“DIAGNOSTIC.LOG”这看起来像这样:
Edit: English was included. Thread open.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice
Sent from my HTC One X, using XDA Premium
http://forum.xda-developers.com/announcement.php?a=81
I'm still willing to help, especially when someone has a unique problem.. I think it would be helpful to know what he did before the issue happened, that would help more in troubleshooting or keeping the issue happening for others. This is the first time I've seen someone with this issue.
Sent from my HTC_Amaze_4G using xda app-developers app

[Q] Bootloop, can't fix?

Last year i tried to disassembly the phone to fix a probably broken audio conector, then i decided to flash a new rom; since then, i'm facing bootloop. I tried to enter into recovery and simply doesn't go there. Download Mode works just fine, so i decided to flash a new stock rom and a TWRM (latest) and the system almost worked. I could enter Recovery Mode, but when i was about to try a factory reset, the touch stopped working. So i rebooted again, then a white screen (that first one that appears, with AT&T logo on it) appeared my phone rebooted.
I flashed a stock recovery but didn't had any sucess either...
Now i'm with a galaxy note 3 (n900) and my phone is in the shelter, completely useless.
Try an emergency recovery with kies.
440bro said:
Try an emergency recovery with kies.
Click to expand...
Click to collapse
Thanks for answering, but it was no use for me.
I can only enter download mode now and my device didn't shown on that list.
Thanks, though.
You only need to be in download mode for kies to work.
Don't use kies 3 that the note 3 uses. Use the original one. Make sure it's up to date. Reinstall the i717 drivers from Samsung. Put phone on download mode and plug into pc. Open kies and click "emergency firmware recovery" type in all caps SGH-I717. Then type in serial number and let it do it's thing!
440bro said:
You only need to be in download mode for kies to work.
Don't use kies 3 that the note 3 uses. Use the original one. Make sure it's up to date. Reinstall the i717 drivers from Samsung. Put phone on download mode and plug into pc. Open kies and click "emergency firmware recovery" type in all caps SHG-I717. Then type in serial number and let it do it's thing!
Click to expand...
Click to collapse
{
"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's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.[/QUOTE]
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
440bro said:
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
Click to expand...
Click to collapse
Firmware upgrade is what you want. The only problem I had was Kies didn't like my serial number. Luckily my wife has a OG Note and I used her sn with no problems Good luck!
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also said:
440bro said:
Here's a screenshot of what it looks like when i do EXACTLY as you told me to.
Also, it's a recently formatted computer, so isn't any driver conflict or thinks like that.
Click to expand...
Click to collapse
Try clicking "Firmware upgrade and initialisation" instead of "emergency recovery". I might of told you wrong. I apologize. It's been awhile since I've needed to fix my i717. I moved on to note 3.
Click to expand...
Click to collapse
Just did that and still the same problem.
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Agoattamer said:
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Click to expand...
Click to collapse
Whoops! Good eye!!
i am also having same issue .. kies says SGH-I717 not support initializing
Agoattamer said:
Type in SGH-I717 not SHG-I717. Hopefully you caught that typo.
Click to expand...
Click to collapse
Unfortunately, it wasn't the case. I double check it before installing.
Maybe it's soft bricked.
Using odin to get you into download mode (not recovery), and flash a stock .tar file to get up and running again. Unless you have a hardware issue inside the phone.
If you want a decent tutorial on doing this, YouTube search "unbrick i717 odin" and the first video listed (for me anyway) is a video by Qbking77 on how to do this step by step. He gives links to odin files and .tar stock files for the i717.

Lenovo Tab 2 A8-50F Root/Recovery ??

hi all i have purchased the Lenovo Tab 2 A8-50F and i have tried everything to root it and cant find a custom recovery for it anywhere..
EDIT::: finally got it rooted with twrp go here for a full guide on how http://forum.xda-developers.com/android/development/root-twrp-lenovo-tab-2-a8-50f-mt8161-t3226130 enjoy
can anyone shed any light on the subject..
SPECS:
MODEL: Lenovo Tab 2 A8-50F
CPU: MT8161 QC 1.3ghz 64Bit
DISPLAY: 8inch 1280*800 IPS
MEMORY: LP-DDR3 1GB
STORAGE: 16GB
OS: Android 5.0.2
thanks in advance..
EDIT: i have found the source code here http://support.lenovo.com/us/en/products/tablets/a-series/a8-50-2/downloads/DS102968
if anyone is intrested in jumping on the boat with me and trying to get this rooted let me know..
UPDATE::::
here is how to unlock the bootloader>>> THIS WILL WIPE THE DEVICE TO FACTORY SETTINGS
first enable usb debugging and make sure oem unlock feature is enabled in developer options.
download the minimal adb (attached)... Extract to desktop or wherever and then run MINADB.exe
in the terminal type adb reboot bootloader you will be rebooted to a black screen which says Fastboot Mode....
now in the terminal type fastboot oem unlock
press the up volume button when asked and WAIT
when its done it will show a menu of boot modes dont do nothing and in the terminal just type fastboot reboot
bootloader is now unlocked.. i am still working on rooting i am trying to find a way to dump the recovery and boot partitions but its proving extra difficult due to permission problems..
I'm in the same boat. I tried everything. I don't think there's a method available for this device yet.
well i am working on it i have done alot of work on new devices and manually figured a root method out.. firstly i need to try and find the source code for our tablet then i can try to get an unsecure boot image then other things will follow on from it..
I believe the source code is on lenovo's website. Idk if that's what you're looking for. http://support.lenovo.com/us/en/pro...,_tablet,_workstation_and_thinkserver_support
DeeJay1 said:
I believe the source code is on lenovo's website. Idk if that's what you're looking for. http://support.lenovo.com/us/en/pro...,_tablet,_workstation_and_thinkserver_support
Click to expand...
Click to collapse
exactly what i am looking for
Awesome! Glad to be of assistance. You said you found a manual root method?
DeeJay1 said:
Awesome! Glad to be of assistance. You said you found a manual root method?
Click to expand...
Click to collapse
yes for other devices.. and i am hoping to find a way on this device but first i need a way to get a custom recovery working on it.. mtk droid tools is a handy place to start and its the best i had it wont root it but it sent me here http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 which happens to be an intresting read..
I too read up on that forum, but I'm not that well versed in Android development lol
lol... well its not so straight forward being that our tablet has a mediatek 64BIT processor.. when i owned the htc desire 510 (uk) it was the first phone with 64bit architecture but i was part of the community that managed to get it rooted after some gruelling hard work.. bad news is that this tablet will probably take quite some time crack.. :/ but i am working on it and i will post any progress on rooting it here..
Inside 4ndroid said:
yes for other devices.. and i am hoping to find a way on this device but first i need a way to get a custom recovery working on it.. mtk droid tools is a handy place to start and its the best i had it wont root it but it sent me here http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 which happens to be an intresting read..
Click to expand...
Click to collapse
Inside 4ndroid said:
lol... well its not so straight forward being that our tablet has a mediatek 64BIT processor.. when i owned the htc desire 510 (uk) it was the first phone with 64bit architecture but i was part of the community that managed to get it rooted after some gruelling hard work.. bad news is that this tablet will probably take quite some time crack.. :/ but i am working on it and i will post any progress on rooting it here..
Click to expand...
Click to collapse
I figured the same. Good luck to you, I'll be looking around for any solution, and let me know if I can assist you with anything.
What is this
I ran into this menu on my tablet. Chinese? Lol
{
"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"
}
It's a factory test mode, tnx to google translate
I'm not able to create the scatter file...
Any luck with this? so frustrating cant get it rooted, cheers
Same here. I have only had my Tab 2 A8-50F for about a week. I am really liking this tablet. For the price it preforms rather well. Only thing keeping me from making a solid decision to keep it is the lack of Root. If I can't root it I might have to start looking for another device
what is so special about this tablet that it wouldnt be able to be rooted? geez.
I am working on a root but its taking longer than normal being the device has 64bit architecture and our chipset is unsupported across most mediatech tools out there oh and the fact it runs lollipop... Instead of thinking there is something special about it try an help yourselves by testing what is already out there and remember most root tools get updated often so keep an eye on them an keep trying until I can come up with something... I am working on it but these things take time when you have a full time job and 2 children t look after... Happy testing an if you find anything you think may help post it here or pm me... ???
Just got this tablet today, updated it from 5.0.2 to 5.1.0
Good device although the latest OTA (Aug 15) has some UI issues/bugs:
Squashes apps in landscape (most evident with Material Design apps like Play Books, Drive)
Completely breaks Lollipops notification bar coloring, just remains Black or changes to White (Google Translate is a good example)
Strangely the Chromecast icon now shows up permanently in any app that has support, never did this before.
Also, I didn't notice before whilst on 5.0.2 but 5.1.0 now has a "OEM unlocking - Allow the bootloader to be unlocked" toggle in the Developer options menu, is this any use?
Deleted
n/m
ok so i have bricked my device hahaha although i have found out how to get it into preloader mode and it shows in device manager as an MT65xx preloader so if someone could follow this guide and backup there boot and recovery images i would be very gratefull and by providing the rom dump i can get mine unbricked and also get root easily..
could someone please do this for me out of good spirit and to help get root who ever follows the guide successfully at the link below and can provide the files i need will get full credit when it comes to releasing root and recovery..
(you must unclip the back off the tablet and remove a metal plate to unplug the battery befopre putting it into preloader/meta mode..
LINK : http://forum.xda-developers.com/showthread.php?t=2540400
thanks

LG Rebel 2 (LG L57BL) problem with root, bootloader, and fastboot

I cannot seem to get this phone into the bootloader, download mode, or fastboot mode. I also can't get any rooting programs to work.
I have an LG Rebel 2 L57BL Tracfone that I've read is a variant of an LG K4 2017 LTE.
I have tried like every combination of buttons to get into fastboot but can only get into Recovery Mode. Using sudo adb reboot bootloader or sudo adb reboot-bootloader does not work, it just reboots the phone. I have managed to get the phone to boot into safe mode as well while messing with different buttons combinations and times.
I am just trying to get this phone rooted but I'm having a hell of a time. I am running Linux and Windows. Does anybody have any idea how to get into fastboot mode or how to root this device? It would be awesome, Thanks
{
"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"
}
Knuxyl said:
I cannot seem to get this phone into the bootloader, download mode, or fastboot mode. I also can't get any rooting programs to work.
I have an LG Rebel 2 L57BL Tracfone that I've read is a variant of an LG K4 2017 LTE.
I have tried like every combination of buttons to get into fastboot but can only get into Recovery Mode. Using sudo adb reboot bootloader or sudo adb reboot-bootloader does not work, it just reboots the phone. I have managed to get the phone to boot into safe mode as well while messing with different buttons combinations and times.
I am just trying to get this phone rooted but I'm having a hell of a time. I am running Linux and Windows. Does anybody have any idea how to get into fastboot mode or how to root this device? It would be awesome, Thanks
Click to expand...
Click to collapse
Aaaaah.Unlock your bootloader First?
Sent from my Nexus 6P using Tapatalk
Knuxyl said:
I cannot seem to get this phone into the bootloader, download mode, or fastboot mode. I also can't get any rooting programs to work.
I have an LG Rebel 2 L57BL Tracfone that I've read is a variant of an LG K4 2017 LTE.
I have tried like every combination of buttons to get into fastboot but can only get into Recovery Mode. Using sudo adb reboot bootloader or sudo adb reboot-bootloader does not work, it just reboots the phone. I have managed to get the phone to boot into safe mode as well while messing with different buttons combinations and times.
I am just trying to get this phone rooted but I'm having a hell of a time. I am running Linux and Windows. Does anybody have any idea how to get into fastboot mode or how to root this device? It would be awesome, Thanks
Click to expand...
Click to collapse
Hey, try removing the battery, pressing the vol+ button & plugging it into PC, then you should see a little screen show up about having no battery to charge,
So while still holding the vol+ button on the device, with it still plugged into the PC, insert your battery back into the phone, don't take ur finger off the vol+ button until after you are in the Download Mode (at least my rebel 1 thru TracFone does it just fine)
Similar problem
What apps did you use to root? I have lg rebel 2. Also will I still have the same rom so the stock can be backed up or will rooting it alter the rom
OP, did you find anything new about rooting this phone as I have the same exact problem and I need a root
I have the 58vl (cdma variant) and from the research I've done tonight it looks like the only hope is porting twrp from a similar msm8909 device but using our kernel as well as modifying the partition layout. I've done this with similar low end devices with success, with that being said there has also been a few bricks in the wall as well. I suppose this phone qualifies as cheap enough to mess with, with little to lose. I can probably provide a recovery.img for the l58vl model, but gsm users should use at their own risk. I'll of course test the recovery.img on my device before releasing publicly. Really the only real reason I need this is for disabling anything lower than 4g because the tf Verizon network does not seem to allow roaming any at all unless it is 4g/lte.. I can have 3 bars on 3g and have no sms/voice/data, however in that exact same spot if I manage to skip the 3g network and hook onto lte with only one bar I've got service. With gsm variants the phone service menu / engineer mode probably works? But with cdma it doesn't and i need to provide a build.prop mod on order to disable the cellular radio on any technology older than 4g.. Otherwise I'd not really even need root myself with this device.
linuxsociety said:
I have the 58vl (cdma variant) and from the research I've done tonight it looks like the only hope is porting twrp from a similar msm8909 device but using our kernel as well as modifying the partition layout. I've done this with similar low end devices with success, with that being said there has also been a few bricks in the wall as well. I suppose this phone qualifies as cheap enough to mess with, with little to lose. I can probably provide a recovery.img for the l58vl model, but gsm users should use at their own risk. I'll of course test the recovery.img on my device before releasing publicly. Really the only real reason I need this is for disabling anything lower than 4g because the tf Verizon network does not seem to allow roaming any at all unless it is 4g/lte.. I can have 3 bars on 3g and have no sms/voice/data, however in that exact same spot if I manage to skip the 3g network and hook onto lte with only one bar I've got service. With gsm variants the phone service menu / engineer mode probably works? But with cdma it doesn't and i need to provide a build.prop mod on order to disable the cellular radio on any technology older than 4g.. Otherwise I'd not really even need root myself with this device.
Click to expand...
Click to collapse
hey did u managed to create an image of twrp?
I'm having trouble rooting my lgl57bl.can someone help me plz.
LilAnt530 said:
Hey, try removing the battery, pressing the vol+ button & plugging it into PC, then you should see a little screen show up about having no battery to charge,
So while still holding the vol+ button on the device, with it still plugged into the PC, insert your battery back into the phone, don't take ur finger off the vol+ button until after you are in the Download Mode (at least my rebel 1 thru TracFone does it just fine)
Click to expand...
Click to collapse
Can I see a video of this by chance ?
You're sure just holding some of the buttons from powered off isn't enough ?

I can't flash recovery with Fastboot

Before going any further, i reverted back to stock yesterday via LGUP to fix some issues i had with the phone on custom roms that caused system crashes. Bootloader is unlocked, i get the prompt that bootloader is unlocked and it isn't safe when the device is booting and OEM unlock is enabled in developer settings.
I'm trying to re-flash TWRP since reverting to stock via. LGUP reverts recovery back to stock. I have issues sending commands via. Fastboot which is making me unable to flash the recovery rom.
Fastboot devices detects my H930, and a few commands works like fastboot reboot bootloader. It's only when it reaches the step to sending the image that the device either freezes for hours or gives an random error like failed command, or too many links.
{
"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've tried multiple ports and usb cables on multiple operating systems "Windows 10 and Arch Linux" on multiple computers my old laptop and my desktop PC with the latest drivers.
I have the latest LG Mobile drivers, i have also tried Driver booster which worked for some but not me
I have the latest SDK platform tools from developer.android.com r31.0.2 (ADB/Fastboot), I've also tried 1.6_r1 and 1.43 with no success.
I'm on a Pre-July 2018 Android security patch on Oreo for LG V30 H930
And I'm using the latest TWRP Joan that i used before reverting to stock (TWRP-JOAN-3312_2020-02-23)
I've followed all troubleshoot options under section 7 at WTF V30 Root Guide other than buying a USB 2.0 hub which seems ridiculous
I have no more options, It's not like i haven't done this before so I'm sure that I'm doing it correctly
Sounds to me like a communication error, which is either a cable or USB issue. As you know, some computers simply don't work well with this process, and fail to unlock bootloaders and/or flash things. I know you feel like you've tried everything, but you may just need to try other cables and most likely computers. There's really no other solution to that problem beyond that.
Also, age of the computer doesn't make as much of a difference, from what I've seen. Just because it's "old" doesn't mean it should work, necessarily. Maybe it's not a chipset that works, and there's no way to fix that externally. Admittedly, older machines seem to work better, but maybe yours is just not "old enough" or something. Do you have the machine that you originally did the BL unlock with, successfully? That might be a good place to start...
Again, I hear you, and you seem experienced... but you just might need to keep trying.
Also, make sure your twrp.img is correct and not corrupted in some way. Can't hurt to check.
I wonder if you can do a fastboot boot twrp.img, and then use TWRP there to perform the flash to the recovery partition? Just thinking aloud...
schwinn8 said:
Sounds to me like a communication error, which is either a cable or USB issue. As you know, some computers simply don't work well with this process, and fail to unlock bootloaders and/or flash things. I know you feel like you've tried everything, but you may just need to try other cables and most likely computers. There's really no other solution to that problem beyond that.
Also, age of the computer doesn't make as much of a difference, from what I've seen. Just because it's "old" doesn't mean it should work, necessarily. Maybe it's not a chipset that works, and there's no way to fix that externally. Admittedly, older machines seem to work better, but maybe yours is just not "old enough" or something. Do you have the machine that you originally did the BL unlock with, successfully? That might be a good place to start...
Again, I hear you, and you seem experienced... but you just might need to keep trying.
Also, make sure your twrp.img is correct and not corrupted in some way. Can't hurt to check.
I wonder if you can do a fastboot boot twrp.img, and then use TWRP there to perform the flash to the recovery partition? Just thinking aloud...
Click to expand...
Click to collapse
My reasoning for why my old laptop might have worked is because of the older USB ports on it, since it's from the early 2010, but it didn't work.
I'm unable to send anything to my device via. fastboot which includes trying to boot into the TWRP image. I have tried multiple versions of the TWRP image and they worked prior to reverting to stock so i don't expect the image file to be the issue.
Do keep in mind that all of my issues are related to fastboot and not adb or the device itself since i've flashed multiple custom roms on it before, i just didn't expect that reverting to stock would make me unable to flash TWRP back on it.
I've tried the original cable, all of my VR charging cables which are also USB-C on multiple ports on both machines and in both operating systems. At least the phone is not unusable, but i miss Pixel Experience.
When I suggested checking the image files, I mean be sure you're getting a ZIPped image that you are extracting, or be sure that the hashes match. Zip does internal hashing to some extent, so it can prevent corruption, but outside of that it's a good idea to check the hash. But, I do agree, that's not likely the issue.
Again, you may just need to try different, older machines. You mention you have two - a new and old. That's fine, but not all "old" machines work either.
You may also try going into safemode or something - sometimes firewalls, virus scanners, etc get in the way. I haven't experienced that personally on this application, but I have seen such things happen recently with other software.
Beyond that, I don't have any other ideas to offer, sorry.
em.. if you can issue fastboot reboot bootloader, I don't think this is connection issue. are you able to get to the download mode? if so, try to refurbish your kdz again, and then restart over

Categories

Resources