LG Rebel 2 (LG L57BL) problem with root, bootloader, and fastboot - Android Q&A, Help & Troubleshooting

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 ?

Related

[Q] Asus Transformer Pad TF103C Tablet - Root? (Intel Bay Trail Z3745, Android 4.4)

Today I got one of the new Asus Trasformer Pad tablets. They just rev'd the line and this one is running Android 4.4.2 and has an Intel Bay Trail Z3745 processor.
This is a very new device: yesterday was the first day this variety of Intel processor was supposed to be available in a tablet, and I had this one on pre-order and it arrived today. Of course, I want to root it.
If anyone knows how I would love it, or pointers to ideas. I rooted my prior Intel Android tablet (an HP Slate 7 1800 "mesquite") with the TwerkMyMoto hack from this thread:
http://forum.xda-developers.com/showthread.php?t=2548742
which has been very helpful. (I find it quite limiting to do development on a non-rooted device, and what I'm working on doesn't run on an emulator). I am very much non-expert at rooting / recovery, and I'm not sure I would make any headway on my own. Depending how much of a limitation lack of root proves to be, if no one has better ideas then I may eventually just start trying things, and if I have any success, certainly I will post back here.
Cheers.
I just got this new tablet and like the performance very much!
I too am interested in rooting it. If anyone has any suggests please post here.
I have tried some generic root methods for x86 tablets, but have not had any luck. The bootloader in locked and when I try to run adb as root, I get an error message "adbd cannot run as root in production builds"
I am a newbie, but if anyone has any suggestions please let me know and I'll give it a try.
Thanks!
bit.perfect said:
I just got this new tablet and like the performance very much!
I too am interested in rooting it. If anyone has any suggests please post here.
I have tried some generic root methods for x86 tablets, but have not had any luck. The bootloader in locked and when I try to run adb as root, I get an error message "adbd cannot run as root in production builds"
I am a newbie, but if anyone has any suggestions please let me know and I'll give it a try.
Thanks!
Click to expand...
Click to collapse
I just picked up one of these today and am also interested in root
Does anyone have any updates?
If anyone has any suggestions please let me know I can test on my device.
It's been two weeks now and I managed to discover some drawbacks. In my case it is closing some applications without any reason. The message displayed says usually that application was suddenly closed or that there was some error etc. I appreciate asus issuing constantly some system updates but they just don't seem to be improving anything so far. Another thing is that I can't connect my HP LJ 1018 printer to USB port. NTFS formatted pendrive also doesn't work... Root access could make this device more useful for me. Anyone... please...
I've got mine 3 days ago and for now I'm satisfied. It would be better if it had an HDMI. I'm waiting for root too. Want to make an swap file to extend RAM memory. I hope someone will make tutorial for us.
Edit: My TF103 died and couldn't come back to life. I'd only had it for 15 days. I returned it and bought a Galaxy Tab 4 instead.
Got one as well
dublinman said:
It's been two weeks now and I managed to discover some drawbacks. In my case it is closing some applications without any reason. The message displayed says usually that application was suddenly closed or that there was some error etc. I appreciate asus issuing constantly some system updates but they just don't seem to be improving anything so far. Another thing is that I can't connect my HP LJ 1018 printer to USB port. NTFS formatted pendrive also doesn't work... Root access could make this device more useful for me. Anyone... please...
Click to expand...
Click to collapse
I picked one of these up before the weekend, and now its become my weekend. Here is what I've managed to figure out:
ASUS Transformer Pad MG10/TF103C
Enable the Developer menu:
Settings -> About -> Software information -> Tap Build number numerous times
Settings -> About -> Software information -> Tap Android version numerous times get a Kitkat animation (Easter egg, nothing helpful)
Using adb reboot bootloader, I have learned this about the bootloader:
DROIDBOOT bootloader
Version 2.0
and everything else you can make out in the picture. Sorry, the size restrictions were getting me.
Update.zip from ASUS
I'm not an Android developer, so forgive me if this question is a facepalmer. Asus has an update.zip for this new model, but its like the guy that updates their website was in a hurry for the weekend so half of the fields aren't filled in. I have determined which update.zip would apply to my particular device, and when I extract everything there is a boot.img, fastboot.img, recovery.img, etc
Can you build a root update package from this or is it not that simple? Currently, there isn't anything out as far as a unlocking package from ASUS or anyone else.
Am I on the right path or am I pissing in the wind?
Nebtastic said:
Can you build a root update package from this or is it not that simple? Currently, there isn't anything out as far as a unlocking package from ASUS or anyone else.
Am I on the right path or am I pissing in the wind?
Click to expand...
Click to collapse
You're on the right track. To get root via a flashable zip, you either need a custom recovery (to flash unsigned zips), or a way to sign the zip to make it look official to the device.
Usually once a custom recovery is available, custom roms follow pretty quickly.
Hello
i wan't any thing do Root for Asus TF103C.
-why there is nothing do Root for the tablet? (Is this for strong security of the tablet?)
Pleeeeaaaassssseee we want Root for this best tablet on Earth:highfive::silly:.
Developer are welcome
I'm also looking forward to have a root!.
I have tried all programs available, none works
Developer are welcome to root Asus TF103
Asus Support
{
"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"
}
Ok, I figured this would be a fruitless journey, but since they released bootloader unlock tools for the last Transformers I thought I would give them a shot.
Asus support says there is no unlocked bootloader. So at this time, there is no support from manufacturer to unlock bootloader or root this device. It looks like to root this device someone is just going to have to hack it.
I have used adb to install busybox and framaroot, but neither were successful. The applications show up in the collection, but when you execute them they fail and close because they cannot attain root access.
I just got this tablet a few days ago, and I love it!! I also long for root/unlockbootloader on this amazing device, I've also tried most rooting methods and without success. But I did discover that they have released the source for its kernel. what is the point of that if they are going to lock the bootloader? :c sorry I am new to this and I dont understand
(cant attach link to kernel yet, sorry!)
upupupupupupupupup
I just picked this a week ago...
cocopwr said:
I just got this tablet a few days ago, and I love it!! I also long for root/unlockbootloader on this amazing device, I've also tried most rooting methods and without success. But I did discover that they have released the source for its kernel. what is the point of that if they are going to lock the bootloader? :c sorry I am new to this and I dont understand
(cant attach link to kernel yet, sorry!)
Click to expand...
Click to collapse
I like this tablet, I use it in my office instead of my issued laptop. The best thing about it is its versatility and quick responsiveness, but it has applications I have no use for as well. If this device can be rooted it would be an added benefit to those of us using it. So, if anyone has the time and the patience I am sure it would be greatly appreciated. Thanks
only if we could obtain temp root :c intel's security seems very tough this time... due to vulernabilities in the past platforms they don't want to unlock the bootloader it seems.
Sent from my K010 using XDA
In case it helps I managed to get this device in fastboot mode and booted in safe mode (did not know that existed).
How to get device into Fastboot mode.
1. Press and hold the Volume + button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume + button.
Device should load the bootloader.
How to boot device into Safe Mode.
1. Press and hold the Volume - button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume - button.
Device should boot into safe mode.
I too am still looking for root method.
bit.perfect said:
In case it helps I managed to get this device in fastboot mode and booted in safe mode (did not know that existed).
How to get device into Fastboot mode.
1. Press and hold the Volume + button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume + button.
Device should load the bootloader.
How to boot device into Safe Mode.
1. Press and hold the Volume - button and power button (while device is on).
2. When screen turns black release the power button, but remain holding the Volume - button.
Device should boot into safe mode.
I too am still looking for root method.
Click to expand...
Click to collapse
This app works for me : asuszenfoneblog app ->rootzenfone-144r
I found the safe mode and the recovery well enough, and I am extremely pleased with this device having traded in my fly tf300t to get it(keyboard nightmare!). It is quick, attractive, and hard to stump.. except for that achilles heel.. For some reason, this guy doesnt enjoi transforming so much. Also, ive caught him in bootloop and having to reboot from recovery. It is an intermittent issue and there seems to some kind of formula to doing all of this smoothly EVERY time. I am interested to hear of issues anybody else is having and if any of you are balding because of the keyboard issue with the previous transformer.. .. and asking for a referal to a good therapist if there are similar issues with this guy..
Sent from my K010 using XDA Free mobile app

[Q] Stuck in download mode and broken Volume Buttons

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:

[Q] Soft Bricked?

Alright. My current phone I was using broke (screen cracked) and I decided to use my old phone, the Droid Razr to get me by until I get a new phone. My Razr was previously rooted on JB when I left it a few years back. It works fine, except it was running slow. It had bootstrap and Safestrap installed. I'm pretty sure at the original time of getting JB on the razr, you had to use bootstrap first and then switch to Safestrap since its safer? However, I forgot this at the time. I wanted to try clearing the cache on the phone to see if it sped it up. However, I guess I uninstalled safestrap and switched it to bootstrap because i used the bootstrap recovery out of ignorance. When I turn on the phone, I get the "Encryption Unsuccessful" message.
I've tried doing the format option it gives but it just restarts the same every time. I've done some researching and it appears I've soft bricked it. I've been reading that the only way to fix it is by using fastboot to wipe the phone to factory settings. I have all the necessary files to do so. I've been working on this for about two days now. However, fastboot does not seem to recognize my phone. I have the drivers installed. When I plug it in normally when it is not in fastboot mode, my PC shows the XT912 under hardware plugged in via USB. But when I put it in fastboot mode, it does not recognize it and it isn't shown in my ADB devices list. What do I do here? I really need this phone to work and I am willing to do whatever it takes to it. I don't care if I have to wipe it/lose root any of that. Please help me. Im not one to make threads of issues that others have but no one elses thread has helped me.
MeltingHolster said:
Alright. My current phone I was using broke (screen cracked) and I decided to use my old phone, the Droid Razr to get me by until I get a new phone. My Razr was previously rooted on JB when I left it a few years back. It works fine, except it was running slow. It had bootstrap and Safestrap installed. I'm pretty sure at the original time of getting JB on the razr, you had to use bootstrap first and then switch to Safestrap since its safer? However, I forgot this at the time. I wanted to try clearing the cache on the phone to see if it sped it up. However, I guess I uninstalled safestrap and switched it to bootstrap because i used the bootstrap recovery out of ignorance. When I turn on the phone, I get the "Encryption Unsuccessful" message.
I've tried doing the format option it gives but it just restarts the same every time. I've done some researching and it appears I've soft bricked it. I've been reading that the only way to fix it is by using fastboot to wipe the phone to factory settings. I have all the necessary files to do so. I've been working on this for about two days now. However, fastboot does not seem to recognize my phone. I have the drivers installed. When I plug it in normally when it is not in fastboot mode, my PC shows the XT912 under hardware plugged in via USB. But when I put it in fastboot mode, it does not recognize it and it isn't shown in my ADB devices list. What do I do here? I really need this phone to work and I am willing to do whatever it takes to it. I don't care if I have to wipe it/lose root any of that. Please help me. Im not one to make threads of issues that others have but no one elses thread has helped me.
Click to expand...
Click to collapse
Windows 7? 8? 10?
Did you tried all usb ports?
Uninstall all moto drivers,reboot computer,install them again.
Here are the newest moto drivers
http://forum.xda-developers.com/showthread.php?p=59139823
Sent from my Razr XT910
Thanks for the quick reply. I'm using Windows 8.1. I did what you asked, and when I turned my phone on after re-installing the drivers, it installed the device normally. It shows this in device manager.
{
"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 still wont recognize it in ADB.
MeltingHolster said:
Thanks for the quick reply. I'm using Windows 8.1. I did what you asked, and when I turned my phone on after re-installing the drivers, it installed the device normally. It shows this in device manager.
It still wont recognize it in ADB.
Click to expand...
Click to collapse
That's a common problem with Windows 8,on Windows 7 everything is ok
Sent from my Razr XT910
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
MeltingHolster said:
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
Click to expand...
Click to collapse
You can fix it with Windows 7
Sent from my Razr XT910
MeltingHolster said:
So that means i cant fix it?
Sent from my SM-T217S using XDA Free mobile app
Click to expand...
Click to collapse
What is on AP Fastboot screen, complete text?
sd_shadow said:
What is on AP Fastboot screen, complete text?
Click to expand...
Click to collapse
It says AP Fastboot Flash Mode (S)
0A.77
eMMC Info: Size 16GB
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected

Bricked trying to magisk 11

I got the Motorola update to android 11 and successfully installed it. When I tried to install magisk after patching my boot.img, I think I've hard bricked the phone.
I'm unable to turn on the screen.. tried just the power button, vol- and power, vol+ and power.. no dice.
anyone know of other things I can try to get in to fastboot and reset the device? or is it a lost cause?
I flashed the patched boot.img from fastboot. when the phone screen was stuck at the motorola logo. I went back to fastboot and flashed the stock boot.img. It boot looped a couple of time and now it won't turn on at all.
Using the rescue tool is of no help because the tool requires the device to boot into fastboot
Help!
Try this. Hopefully you can get to the bootloader. If yes, continue with my suggestion below.
I guess you go up to android 11 via OTA. In this case, you need to download the android 11 firmware matching your phone, then extract the boot.img which you will flash back to your device. Hopefully, you can reboot to your phone as normal.
When patching the boot.img using the latest magisk, remember not to change the patched file name given by magisk. Just keep it as is as provided by magisk. To be safe, you should test a single boot with the patched image before flashing it.
Hope that'll help.
tinbilly said:
Try this. Hopefully you can get to the bootloader. If yes, continue with my suggestion below.
I guess you go up to android 11 via OTA. In this case, you need to download the android 11 firmware matching your phone, then extract the boot.img which you will flash back to your device. Hopefully, you can reboot to your phone as normal.
When patching the boot.img using the latest magisk, remember not to change the patched file name given by magisk. Just keep it as is as provided by magisk. To be safe, you should test a single boot with the patched image before flashing it.
Hope that'll help.
Click to expand...
Click to collapse
Thanks.. I cannot get the phone to power on at all.. so, no bootloader/fastboot. Tried power cycle while plugged in.. didn't change anything. Will keep trying.. Strangely, the rescue software's 3rd option is "power-off mode", but that option also asks me to be in fastboot.
smvsmv said:
Thanks.. I cannot get the phone to power on at all.. so, no bootloader/fastboot. Tried power cycle while plugged in.. didn't change anything. Will keep trying.. Strangely, the rescue software's 3rd option is "power-off mode", but that option also asks me to be in fastboot.
Click to expand...
Click to collapse
is it listed in Device manager like this?
Is my device in EDL Mode?
sd_shadow said:
is it listed in Device manager like this?
Is my device in EDL Mode?
Click to expand...
Click to collapse
No. I tried reinstalling the Qualcomm usb drivers. That didn't help either. Possibly that's why the rescue tool is unable to help with the power off option. Any other ideas? What ever happened, it has to do with the boot.img.
I wish phones had a reset hardware button.
Are you sure the phone is fully charged? Did you try plugging in the power for several hours?
Did your try https://support.lenovo.com/vn/en/downloads/ds101291-rescue-and-smart-assistant-lmsa?
tinbilly said:
Did your try https://support.lenovo.com/vn/en/downloads/ds101291-rescue-and-smart-assistant-lmsa?
Click to expand...
Click to collapse
Yes, that's the rescue tool that I've been referencing. Also, the phone had full charge when I screwed it up. Will try plugging it again.
smvsmv said:
No. I tried reinstalling the Qualcomm usb drivers. That didn't help either. Possibly that's why the rescue tool is unable to help with the power off option. Any other ideas? What ever happened, it has to do with the boot.img.
I wish phones had a reset hardware button.
Click to expand...
Click to collapse
How is it listed in Device Manager?
sd_shadow said:
How is it listed in Device Manager?
Click to expand...
Click to collapse
It's not at all listed.. there are no "other devices" and it's not listed under ports either
{
"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"
}
smvsmv said:
It's not at all listed.. there are no "other devices" and it's not listed under ports either
View attachment 5311913
Click to expand...
Click to collapse
If windows is making the device connected sound will connecting to USB, it's there somewhere.
Otherwise, it's not fixable because there is no device to send commands to.
sd_shadow said:
If windows is making the device connected sound will connecting to USB, it's there somewhere.
Otherwise, it's not fixable because there is no device to send commands to.
Click to expand...
Click to collapse
Yep.. that's what I'm afraid it is. Unless the device decides to boot to something, I'm guessing it's done. Thanks for your help!
Did you try Motorola Moto G 3rd Generation Troubleshooting or Moto G Power: Black Screen or Screen Won't Turn On? 6 Easy Fixes!?
tinbilly said:
Did you try Motorola Moto G 3rd Generation Troubleshooting or Moto G Power: Black Screen or Screen Won't Turn On? 6 Easy Fixes!?
Click to expand...
Click to collapse
yeah.. been googling and this was the first video that I came across. didn't help though.
EDIT - ignore the below. Just remembered that is a snapdragon and not Mediatek.
When I leave the phone connected to my windows 10 laptop, the device shows up occasionally under networks. Double clicking the device pulls up the properties.
Looks like there's still some "life" on my phone. Anyone have ideas on how to get into it?
smvsmv said:
EDIT - ignore the below. Just remembered that is a snapdragon and not Mediatek.
When I leave the phone connected to my windows 10 laptop, the device shows up occasionally under networks. Double clicking the device pulls up the properties.
Looks like there's still some "life" on my phone. Anyone have ideas on how to get into it?
View attachment 5314927
Click to expand...
Click to collapse
do you what Model # you have?
sd_shadow said:
do you what Model # you have?
Click to expand...
Click to collapse
Not sure.. but before upgrade, the rescue tool downloaded the file SOFIA_RETAIL_QPMS30.80_63_6_8_5_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml Not sure if that shows model
smvsmv said:
Not sure.. but before upgrade, the rescue tool downloaded the file SOFIA_RETAIL_QPMS30.80_63_6_8_5_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml Not sure if that shows model
Click to expand...
Click to collapse
open that folder, does it have a
preloader.bin file?
sd_shadow said:
open that folder, does it have a
preloader.bin file?
Click to expand...
Click to collapse
No. these are only 4 bin files
The info file has the below. Couldn't find anything that status with a XT
BUILD REQUEST INFO:
SW Version: sofia_retail-user 10 QPMS30.80-63-6-8-5 a1e5d release-keysM6125_39.36.03.39R
Modem Version: M6125_39.36.03.39R
FSG Version: FSG-6125-03.87
MBM Version: MBM-3.0-sofia_retail-37f1d8316-201231
Build Fingerprint: motorola/sofia_retail/sofia:10/QPMS30.80-63-6-8-5/a1e5d:user/release-keys

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