Database Info

Help! Might be bricked? Confused.

So i bought a htc one xl on craigslist a few months ago. I downloaded an app to check if its rooted and it said it was. Long story short i think i downloaded the wrong rom and i cleared everything from TWRP. I really have no business doing anything like this.. Now im stuck. I can get to the bootloader mode screen but when i got to recovery it takes me to twrp. I hope i didn't screw it up too bad. TWRP says "no os" also.
Any help would be appreciated! Im done with messing with rooting and such i don't want to mess up my phone anymore.
ps: I didn't do a backup.

Download the right Rom to your computer lets make it viper xl to make things easy once done downloaded mount usb storage in twrp drag the Rom over... Factory reset and flash the Rom and you're good

It installed fine and everything but its been at the viper xl loading screen for 10 minutes. Any reason why its doing this?

Do you have hboot 1.14? And did you factory reset

Yes and Yes

You still have the zip on your computer right? So I guess we're going to have to fastboot the boot.img which is very simple I'll give you a quick tutorial in a sec
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"

I extract the fastboot folder right? I did that and its "saying waiting for device".

Install the drivers

Sorry but where do i find those?

Alright i think i did it right it said finish in the command prop. Now what do i do?

1991birdofprey said:
Alright i think i did it right it said finish in the command prop. Now what do i do?
Click to expand...
Click to collapse
If you have adb/fastboot installed, have a copy if the rom on your phone and also the computer for less confusion. On your computer, extract to rom and copy the boot.img INSIDE your adb/fastboot folder.
Enter boot loader on your phone, (white screen 3 skating droids). Make sure it says fast boot usb. Run a simple command like "fastboot devices" and see if something shows up. If so, proceed. If not, restart computer or make sure drivers are installed.
On your computer, right click on the adb folder and choose "open command prompt here" in the cmd window type->
Fastboot flash boot boot.img
Upon success, immediately boot into recovery (twrp) and flash (install) the entire rom.
Profit
Sent from my HTC One XL using Tapatalk 2

Thanks a bunch guys! I thought i lost my phone! Everything worked!

[Q] Razr HD Maxx Boot Loop - Need Help

I have a Razr Maxx HD. I am stuck in a bootloop and cannot recovery with factory firmware. The phone was rooted but the bootloader not unlocked. I could use some help. I have tried many of the things that I have seen on online forums but have not had success.
Here is what led to the problem:
1) I rooted my phone. It rebooted fine.
2) I downloaded a modified framework-res.apk and Root Explorer (File Manager) to my phone.
3) Mounted Root Explorer in r/w mode.
4) Copied and overwrote original /system/framework-res.apk with modified file.
5) Phone rebooted and got stuck in loop.
*USB debug mode was on at time of failure.
Here is what I have tried on a Mac:
1) In Android System Recovery <3e>, I tried "Wipe cache partition" and "Wipe data/factory reset." That did not work.
2) I downloaded the Mac Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can run ADB in my terminal. However, it only shows the device when in "Recovery/Apply update from ADB " mode. When I perform "adb devices" it shows a serial number and "sideload." I use the "adb sideload" command to transfer the firmware .zip file. It reads the following after it is uploaded:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/framework-res.apk", "bunch of numbers")
Installation aborted.
This was after sideloading the package "Blur_Version.9.1.41.XT926.Verizon.en.US.zip." This was the same file I was modifying earlier. I have tried it with the fireware xml.zip files from sbf.droid-developers.org/vanquish/list.php and only got to line 3 before it aborted.
3) Tried to update from microSD card and got same result.
4) I have the original framework-res.apk file; however I don't know how to push it. I cannot get it to recognize the device in ADB outside of the Recovery from ADB sideload option. All other ADB commands return an "error : closed" reply.
5) As far as Fastboot, it reads AP Flastboot Flash Mode (S), Device is LOCKED. Status Code: 0, Battery OK, USB Connected. I got the device ID and tried the online unlock key generator on Motorola.com but it stated my device was not eligible for unlocking at this time, so it remains locked.
Here is what I have tried on a Windows 7 PC:
1) I downloaded the Windows Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can open ADB in cmd line. However, when I perform "adb devices," it does not show a serial number, even in Recovery ADB sideload.
2) I downloaded RSD Lite 5.3.1. Selected one of the extracted sbf.droid-developers.org/vanquish/list.php .xml files. Hit start and nothing happened. "Show Device" did not bring anything up. I am guessing the PC is not detecting the device, but I uploaded the latest Motorola Drivers Package. I even tried the Google USB Driver install in Android SDK.
Can you recommend another course of action or a means of getting one of these methods to work? Please help me unbrick my phone. Thank you in advance for any advice.

..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.

mentose457 said:
..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.
Click to expand...
Click to collapse
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?

rmp2737 said:
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?
Click to expand...
Click to collapse
Is this the case in both windowz and osx?
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 06:00 PM ---------- Previous post was at 05:31 PM ----------
I cant find the article bout using a stock update zip. Though you could flash the latest ota update. It would eliminate any chance of you unlocking the bootloader and possibly obtaining root.

mentose457 said:
Is this the case in both windowz and osx?
Click to expand...
Click to collapse
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
mentose457 said:
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Click to expand...
Click to collapse
Thanks. Let me know if you find it.

If you could get your phone to be recognized in adb all of your problems could be solved. You could even unlock your bootloader without being able to get into the os. If I were you id continue to try to get my computer to communicate with my phone.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
rmp2737 said:
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
Thanks. Let me know if you find it.
Click to expand...
Click to collapse
is the "apply update from adb" part of the stock recovery? Ive never encountered it.
---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.

mentose457 said:
Is the "apply update from adb" part of the stock recovery? Ive never encountered it.
Click to expand...
Click to collapse
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.

rmp2737 said:
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.
Click to expand...
Click to collapse
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
mentose457 said:
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.
Click to expand...
Click to collapse
Have you tried this ^^^
---------- Post added at 07:34 AM ---------- Previous post was at 07:17 AM ----------
What method did you use to fastboot?

mentose457 said:
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
Click to expand...
Click to collapse
I tried it a few times with RSD Lite different file versions. They did not work. Perhaps the permissions for the folder were not reverted and this is a problem?
I have tried to connect to with ADB during the bootloop and in the recovery mode menu. It did not work.
As for fast boot, I am using the AP Flastboot Flash Mode as part of stock recovery.
Thank you for your help so far. I am lost at this point, since it seems all the typical methods are not working.

I am suspect that performing the factory reset disabled USB Debugging Mode and that is why ADB won't work. If so, I think I am stuck because it's Catch 22. I can't push the files with ADB, I cannot flash the system.img file because it is too big, I cannot flash the system.img file with RSD Lite (for what I can only assume is a permission error), I cannot erase the system.img to clear it before I flash over it because the bootloader is locked, and I can't unlock the bootloader because the exploit requires you to use ADB commands. Unless, I am missing something.

Screwed [Solved]

Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....

DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt

_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!

When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..

DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?

lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot

DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.

We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh

berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!

lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?

berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh

lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.

I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?

Look in Device Manager on your PC and check that the Asus ADB interface drivers are there

Wow what a difference DATA2SD and ROM2SD make!

lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh

DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working

lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW

lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?

lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...

[Q&A] **TWRP** custom recovery for IDOL3 6045

Q&A for **TWRP** custom recovery for IDOL3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for **TWRP** custom recovery for IDOL3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

stuck on twrp bootloop
stuck on twrp boot loop. any suggestions? i followed instructions as posted, but when rebooted into twrp and tried to reboot system, i keep going back to twrp. thanks

Heyy
I have the same problem,, although i did a backup and then a deleted everything cause it was looping,,, how do i fix everything to the original condition,, i won't be doing this again,, my model is an i version.. Although mine is not booting into twrp ,, just the original..

Restoring my backup does not work

I tryed everything,, i know not to do this anymore I think it's broke forever.

If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...

Where is the system image?
neilownz said:
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Click to expand...
Click to collapse
---------- Post added at 12:30 AM ---------- Previous post was at 12:20 AM ----------
im in tears (

I believe there's a link in the thread about ota updates after rooting.
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745

Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
Click to expand...
Click to collapse
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...

TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
Click to expand...
Click to collapse
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.

I can't even get into TWRP mode now it reboots too fast now..
maigre said:
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
Click to expand...
Click to collapse

You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).

I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?

datkevjames said:
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
Click to expand...
Click to collapse
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
maigre said:
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
Click to expand...
Click to collapse
If you can execute fastboot commands, your already in bootloader.

famewolf said:
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
If you can execute fastboot commands, your already in bootloader.
Click to expand...
Click to collapse
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.

twrp bootloop
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.

datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
Click to expand...
Click to collapse
There are no install-script and install-binary example files to use to build a signed update.zip because there are no rom's available....maybe someone could build something using the spanish rom just posted but I don't read spanish and they seem to have built it for a 6045Y which isn't gonna help 6045i or 6045K users. If you were running twrp it wouldn't be an issue as twrp allows adb access....stock recovery doesn't..it also doesn't support rebooting to bootloader....if your bootup was "freezing" as a normal build.prop issue would then you should STILL be able to do an "adb reboot bootloader" or an "adb shell" and look around.

datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
.
Click to expand...
Click to collapse
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
---------- Post added at 10:58 AM ---------- Previous post was at 10:50 AM ----------
faresbreech said:
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
Click to expand...
Click to collapse
if you have a problem then:
1- you have to tell what did you do before it happen.
anyway if you can go to TWRP, you can download system Image backup from @famewolf thread HERE, copy it to your sd card and then proceed with restore menu from TWRP. And just check the "system" .

First I rooted phone, then verified through root checker that I was truly rooted. After that I proceeded to flash twrp. Once twrp was flashed, I went to recovery to make a full backup. There I first chose read only and then backed up, but realized that I was limited on performing different actions so I reflashed twrp and this time I chose for twrp to fully work and again preformed another backup. It was when I rebooted system after the second backup when I started looping back to twrp.
I was wondering if maybe there is a terminal command I can execute through twrp to fix this like the LG G2 has. I had a problem like this before on my G2 but after executing the terminal command it would get fixed. Thanks
Sent from my Z987 using XDA Free mobile app

DallasCZ said:
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
Click to expand...
Click to collapse
I tried spamming 'adb reboot-bootloader' as fast as possible, but apparently I didn't authorize my computer. ADB gives me this: error: device unauthorized. Please check the confirmation dialog on your device. ffs. Now what? I do appreciate all help. I am savvy enough to try to solve this on my own but any helpful advice would be awesome.

Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )

Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )
Everything you need to root your LG Stylo 2 Plus running on Android 7.0 is packed into Stylo2.zip for convenience
If the link ever goes down send me a private message, I'll have a few backups of this laying around.
This method works on MetroPCS (LGMS550) and T-Mobile (LGK550) phone models.
Stylo2.zip​(35.6mb)
VirusTotal Scan
Click to read the guide​
Before doing anything, on your computer you need to extract Stylo2.zip to your Desktop, and install:
minimal_adb_fastboot_v1.4.1_setup.exe (Install this into the Stylo2 folder)
PhoneDrivers.exe
1. Enable Developer Options on your phone, and navigate to the Developer Options page.
Enable OEM unlock
Enable USB debugging
Enable File Transfer
Place no-verify-opt-encrypt-5.1.zip and SuperSU.zip onto your external sd card.
2. After placing the two zip files into the root of your sd card
Enable Charging mode
Authorize your computer for USB debugging
3. Launch MAF32.exe from the Stylo2 folder
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2>
5.Boot into the bootloader by typing
adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2>
6. Next you will be unlocking the bootloader
(This will erase everything on the Internal Storage)
In the PowerShell window you will need to type:
fastboot oem unlock
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2> fastboot oem unlock
...
(bootloader) Erasing userdata and cache
OKAY [ 12.386s]
finished. total time: 12.389s
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2>
Your data should now begin to wipe.
7. Once finished with the data wipe, you will need to flash the recovery.img to your device.
In the PowerShell window you will need to type:
fastboot flash recovery recovery.img
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> fastboot flash recovery recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (15588 KB)...
OKAY [ 0.508s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.918s
PS C:\Users\Hyperion\Desktop\Stylo2>
This is where it can get tricky.
8. Turn your phone off.
Unplug your USB cable
Take out your battery
Put your battery back in
Read next step before turning your phone back on
9. You will now need to boot into TWRP, which isn't the most fun thing to do.
(This process begins after the screen prompt that says your phone can't be authorized has already came up.[if it pops up at all])
Get comfortable with this process before attempting it.
Hold Vol Down + Power (Don't let go)
Once you see the LG Logo let go of the power button briefly
Press the power button while still holding Vol Down
Don't let go until a white Factory Reset screen comes up.
Select Yes, then on the next screen select Yes again
(This should boot you into the flashed TWRP Recovery Image)
If you do not boot into TWRP, repeat Process 1-8 until success
(excluding unlocking your bootloader, once unlocked it does not need to be unlocked again.)
10. Assuming you are in the TWRP menu, you will need to wipe the device again.
Navigate to WIPE in the top right
Follow on screen instructions to wipe the device
Click Reboot, and choose Recovery
It wouldn't be a bad idea to make a Backup at this point
11. Once back at the TWRP menu again, you will need to start flashing .zip files.
Click Install
Click Select Storage in the bottom left
Select no-very-opt-encrypt-5.2.zip
Swype to confirm Flash
Press back until at the TWRP main menu again
Click Install
Select SuperSu.zip
Swype to confirm Flash
Some people have had better luck flashing no-very-opt-encrypt after flashing supersu. (I can not confirm this)
12. Reboot to system, let the thing boot loop a couple times at the MetroPCS screen
Cross your fingers until your phone boots up
Download a Root Checker
Check your root access.
If all went well your MS550/K550 running Android 7.0 Nougat should be rooted
I hope it went well xD
-Mike​
Thanks to:
Danielhammons1/Reemitch (For notifying me about a missing step between steps 4 and 5)

I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).

i am stuck at fastboot oem unlock it doesnt do anything will you please contact me at [email protected]

wellsweb said:
I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).
Click to expand...
Click to collapse
I believe between number 4 and 5, so at 4.5 you must enter the command "adb reboot bootloader" in order to enter fastboot mode.

some help please, stuck on step 4
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks

cruba001 said:
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks
Click to expand...
Click to collapse
That was completely my bad! I forgot I had setup adb and fastboot differently than in this guide, I updated the above post to reflect what you should actually be doing xD Thanks for catching that!~

Can i do this even though im an update behind?

Th3Joker2496 said:
Can i do this even though im an update behind?
Click to expand...
Click to collapse
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.

Dark Bulbasaur said:
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.
Click to expand...
Click to collapse
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'

Please help me lower fw lg stylo 2 plus ms550. thank you
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
Please help me unlock my bootload. ms550

Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.

Dark Bulbasaur said:
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.
Click to expand...
Click to collapse
im so lost bro you have skype?

I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?

Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE

BlackGTNinja said:
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE
Click to expand...
Click to collapse
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase

Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
Reflash TWRP on CMD and remove the battery and run twrp like in the instructions. Afterwards go to wipe, select format in TWRP and type "yes" (after you type "yes" the storage will be wiped. Nothing in internal storage.) and reboot to TWRP (make sure you got a sd card or computer to install rom). After the format, install rom. I don't know how to root on stock. Running LOS 64bit 7.1.2 on my Stylo 2 Plus.

Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
It was the Android Fastboot drivers was not configured right,I had to go to Device Mangager and Manually update drivers to Bootloader interface
http://visualgdb.com/KB/usbdebug-manual/

I hv searched for many websites and they said you should unlock bootloader to go further.
But on lg stylo 2 plus bootloader can't be unlocked it is not available on website .
Can anyone suggest me what i should do to forcefully unlock my bootloader.

xpurge1 said:
I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?
Click to expand...
Click to collapse
no you're not. just go into twrp, format data, mount the device, move the folders, and try flashing SuperSU BEFORE no verity.

I can't seem to flash the recovery. OEM is unlocked and everything else is correct but when i go to the step to flash, it tells me it cant be flashed.