Develop Bugs

Bricked EVO?

So this was sort of a 3 part process that I need to detail to see if anyone has any clues on how to help. I tried to search the forums but had no luck coming across anything. Basically here is what I did, as I'm using a Mac I took a back door route.
1. Rooted phone using UnRevoked3. This worked fine I was using it for a day or two but then wanted to install Cyanogenmod so I could use Froyo. I wasn't able to install and it appeared the consensus was that the way unrEVOked works does not allow the proper access to install cyanogenmod. According to theunlockr.com/2010/07/20/how-to-root-the-htc-evo-4g-unrevoked-method/ it appeared that after installing unrevoked one still needed to unlock the NAND as seen here theunlockr.com/2010/07/20/how-to-unlock-nand-on-the-htc-evo-4g/
2. As this process did not work on Mac I scoured the forums and found this process forum.xda-developers.com/showthread.php?t=705113 and went through all the steps. Everything worked fine until the end when I installed the Radio an then the ROM (this was backwards from their instructions, ROM then radio which may have cause the problem). Regardless I ran Radio update, but then didn't reboot and installed Cyanogenmod update linked to from here forum.xda-developers.com/showthread.php?t=729367&highlight=brick
3. Everything appeared to work fine. After installing Cyanogenmod it asked if I wanted to reboot. I said yes, it said updating radio then rebooted. This may have been where I made the true mistake. It gave me a thing with an exclamation point after rebooting. At this point I waited for a little while then tried restarting, I took the battery out and tried to press a button. After this it wouldn't turn on. Am I totally screwed? My guess is that I probably am and feel like a total moron... Please let me know if there is anything worth doing...
Thanks,
Greg

also http portions were left out of links due to the fact that xda won't let me post links as a new member

[fixed] Flashed wrong TWRP, possible hard brick? Please help :'(

I've had a horrible run of luck these past couple weeks.. Deep 2nd degree burns, two broken s6 edges from sliding off surface, and a drop all at short Heights, even with case on.. So now that I was laid up in bed recovering from work accident I decided to get my tmobile p607t I just picked up and my edge all sorted out.. This is what I did:
Downgraded from 4.4.4 to 4.4.2
Towelroot and supersu
Installed titanium backup
Decided to install custom rom and make nandroid backup
Installed flashify
Erroneously installed twrp for nexus 6 (it's a real ****ty mistake I wasn't paying enough attention, probably pain killers had something to do with it and didn't realize that for all the mentions of the note in the article that they were actually linking to nexus 6 twrp)
Flashed twrp with flashify, reboot, and would only boot into download mode
Booted into odin tried flashing the same stock 4.4.2 knowing it probably wouldn't fix problem, errored out, unsuccessful
Read something about flashing twrp with odin so tried that, it didn't work, heard cwm may work with odin, Unplugged tablet from pc, power cycled, started up with black screen.
Found out it was on by plugging back into pc and odin showed "Added"
Power cycle odin shows removed and added again.
Installed adb/fastboot and drivers via installer (win7 x64)
Just so see what was going on with tab figured I would try to flash stock again to see what error was, so I would be able to mention it in this post, says no pit partition and screen is still black..
This is the point where I decided to post, during all that I did read a lot and did try searching around for something model specific, but am really concerned about doing anything else without advice.. Not really sure if it's even fixable, but hoping that because odin still sees it, maybe it's not a lost cause.. Even if it is just pointing me in the right direction it'd be helpful. I'd be willing to donate to xda's server costs if it takes really in depth help, I've benefited a lot from the site over many years and never really had to post before because I've never had any real issues, usually much more thorough with reading things. Thanks in advance.
I have family coming over so will more than likely be back to working on it tonight..
Edit:
Jesus in doing a horrible job at life.. Posted in wrong sub.. Should be in note 10.1 2014 forum, please move to correct forum.. Sorry
Edited to add:
It's fixed, I located pit partition file, loaded that and stock rom in odin, attempted to flash but it failed, power cycled and download mode appeared on tablet, without error and odin automatically began flashing, everything is back to normal..

defcomexperiment said:
I've had a horrible run of luck these past couple weeks.. Deep 2nd degree burns, two broken s6 edges from sliding off surface, and a drop all at short Heights, even with case on.. So now that I was laid up in bed recovering from work accident I decided to get my tmobile p607t I just picked up and my edge all sorted out.. This is what I did:
Downgraded from 4.4.4 to 4.4.2
Towelroot and supersu
Installed titanium backup
Decided to install custom rom and make nandroid backup
Installed flashify
Erroneously installed twrp for nexus 6 (it's a real ****ty mistake I wasn't paying enough attention, probably pain killers had something to do with it and didn't realize that for all the mentions of the note in the article that they were actually linking to nexus 6 twrp)
Flashed twrp with flashify, reboot, and would only boot into download mode
Booted into odin tried flashing the same stock 4.4.2 knowing it probably wouldn't fix problem, errored out, unsuccessful
Read something about flashing twrp with odin so tried that, it didn't work, heard cwm may work with odin, Unplugged tablet from pc, power cycled, started up with black screen.
Found out it was on by plugging back into pc and odin showed "Added"
Power cycle odin shows removed and added again.
Installed adb/fastboot and drivers via installer (win7 x64)
Just so see what was going on with tab figured I would try to flash stock again to see what error was, so I would be able to mention it in this post, says no pit partition and screen is still black..
This is the point where I decided to post, during all that I did read a lot and did try searching around for something model specific, but am really concerned about doing anything else without advice.. Not really sure if it's even fixable, but hoping that because odin still sees it, maybe it's not a lost cause.. Even if it is just pointing me in the right direction it'd be helpful. I'd be willing to donate to xda's server costs if it takes really in depth help, I've benefited a lot from the site over many years and never really had to post before because I've never had any real issues, usually much more thorough with reading things. Thanks in advance.
I have family coming over so will more than likely be back to working on it tonight..
Edit:
Jesus in doing a horrible job at life.. Posted in wrong sub.. Should be in note 10.1 2014 forum, please move to correct forum.. Sorry
Edited to add:
It's fixed, I located pit partition file, loaded that and stock rom in odin, attempted to flash but it failed, power cycled and download mode appeared on tablet, without error and odin automatically began flashing, everything is back to normal..
Click to expand...
Click to collapse
Really unlucky but in my country we use to say good end everything good. I hope to have better days from now on.
Sent from my GT-N7100

Thank you, yes things are starting to look much better. Burn is healed, my devices are working as they should..

Soft Bricked LG G3, trying to get LineageOS on it. (Success!)

I was needing a new phone and saw a Linus Tech Tips video where he took an LG G3 and put LineageOS on it. So I thought I'd try it out for myself following his guidelines at https://linustechtips.com/main/topic/1058206-lg-g3-lineageos-tutorial/
I bought an LG G3 D851 (T-Mobile version) off EBay for this. It's my first Android phone (yes, experimenting on my first Android Phone), I've always used Windows phones. This is what I've done to the LG G3 so far:
I reverted back to KitKat. Everything seemed to have gone just fine.
Then I downloaded the the Full Purple Drake Root and ran that after I figured out that .gz files are a compressed file and that can be decompressed. Everything seemed to have worked fine.
Then I downloaded the TWRP app on the phone and tried to backup the recovery via the TWRP app, which I'm not sure if it worked correctly. But anyhow.
Now that I'm writing this I see I missed this step:
number seven: Select the TWRP file we copied over earlier in the app, flash it to recovery, and then reboot to recovery
Click to expand...
Click to collapse
I guess I just didn't understand what was meant by flashing it over and has just copied it to the phone's memory which I later wiped.
Well then I went into TWRP recovery and tried to do a recovery backup, which it seemed to do just fine. I rebooted and tried copying it over to the computer, which seems to not have worked. I just have an empty folder on my computer as we speak.
Then back in the TWRP recovery, I selected Wipe>Advanced Wipe, and select Dalvik, Cache, Data, Internal Storage, and System – then swipe to wipe.
Then I downloaded the latest version and nightly of LineageOS zip file and the Opengapps zip file but then had a hard time figuring how to get them to the phone.
I figured out that I could stick them on an SD card and slip it into the LG G3 that I'm working on and could see the files from the TWRP recovery menu.
So I tried to install the LIneageOS zip file several times and it didn't work. I'm guessing it's because I forgot to flash a certain file to TWRP recovery and am not sure how to do that, especially now with the phone only booting into recovery mode with the TWRP menu since it's wiped clean and will just display the LG logo and turn the LED different colors if I try to normal boot the phone.
Well I still want to try to fix the phone and go for LineageOS. I spent nearly all night working on it so I may give it a rest for a few days. But any help or pointers would be greatly appreciated.

Now that I think about it, I didn't do what I mentioned ok #4 above about flashing the TWRP recovery because TWRP recovery was installed with the full Purple Drake root. However, the Linus Tech Tips instructions point to them rooting the phone with the lite version of Purple Drake (root only) and then flashing the newest version of TWRP recovery. So I wonder if my problem has to do with my having the latest version of TWRP recovery on my phone.

Ok. So I think I'm making progress, although that's just a feeling I have since I'm not suite what I'm really doing.
Anyhow the error code was something like "Unknown Error, Error Executing Updater Binary in Zip, Zip is for LG G3 D851, this phone is...(blank)". So I found an article in DroidThunder.com talking about this very problem. It suggested unzipping the rom on my computer and looking for the updater-script file and erasing some lines that apparently only have to do with verification. Then re-zip and retry.
Now I'm getting a "No MD5 file" message followed by an "Error flashing zip" message.
Edit: After reading this I take it I have an older version of TWRP, that is, v2.7.1.0, whereas the newet versio (for this phone?) is apparently 3.3.1-0. That seems to have an effect on this. I wonder if it's possibly to flash a newer version of TWRP onto this bricked phone. Anyhow, I'll have to look into that later. It's time to call it a day.

So recently I've been focusing on these two threads:
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851! by Omar-Avelar
And:
[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery by l33tlinuxh4x0r
But I can't get either of them to work. I guess the only other thing would be to try to find a ROM, preferably the original KitKat that came with the phone, and hope and pray that I can get TWRP recovery v2.7 to install it.
I have the original as a tot file. But as far as I understand, I need a zip file that's set up for TWRP recovery.
Anyhow, trying to get this phone running hasn't been easy and has made other problems. Now every time I turn on my Surface 3 I have to go through BitLocker authentication. Hopefully turning bcd Test Signing off will stop that. But I'm getting to the point that I'm feeling like giving up.

Well that's it. Last night I found a zip file for the original Marshmallow ROM for my G3. I got it onto the SD card, went into TWRP recovery, saw it install, restarted and...
Now it's hard bricked. I cannot even get into TWRP recovery. The screen won't show a thing. I tried several times to get it into any mode possible, normal boot, TWRP recovery boot, download mode, and that jumping the pins trick, and I can't get it to where I can do something with the phone.
So I'm giving up on all this rooting, custom recoveries and custom ROM stuff. It all seems like a good idea, and I'd love to be a part of it all. But I take it this isn't for me. So I give up.
Thanks to all who have worked on this and have made the helpful forums about these phones! Maybe if I were more competent I would have figured it out.

Well, I said I was giving up. But maybe not. I did give up trying to recover the phone from being bricked and sent it out to a JTAG shop. For about $40 the phone is supposedly fixed and on it's way back.
But when it's back, do I just leave it alone this time, or should I try to get Lineage OS back on it again? Well, this is something that I haven't made my mind up yet. I see where I had made several mistakes when I first tried to get LineageOS on it. Maybe I know enough now that it won't happen again. But at the same time there's no guarantee that I won't me it up again, and have to pay some $40 again to have it unbricked.

SUCCESS!!!
So I got my phone back with stock Marshmallow working. Then I carefully went through every step on the Linus Tech Tips site, including installing the latest version of TWRP, and the next thing I know I'm running LineageOS 16 on my phone!
This is great! It's my first Android Phone and I've got it setup just about perfect! The only thing I kind of miss is Wi-Fi calling. But that didn't work so well on the Alcatel Window's phones I had anyway. But I got all the apps and most of the music I need installed and am ready to go! I also have two batteries, and the original isn't too bad, so I might carry that around as a backup until I'm sure how much battery I'll be using.
I'll be coming back and thanking all the ones who's posts and work have helped me individually. But if you read this and are one of those who have worked on TWRP, LineageOS and anything else that has helped me, Thank You!

Trouble Booting into TWRP/Flashing magisk. Tried almost everything.

Okay, so I'm having a real b**** of a time getting root or even TWRP on my Moto G Fast (Boost mobile) and I really don't understand what it is I'm doing wrong. I've carefully gone through pretty much every thread available on XDA (and basically everywhere else) pertaining to getting root/TWRP on this device and from what I've gathered its been a pretty simple process for most other people with this device but for some reason nothing has worked for me. I should also note that my phone has had the most recent OTA update, which I was led to believe would make things easier but apparently not lol. So far the only thing that's gone off without a single hitch was unlocking the bootloader. Beyond that nothing I've tried has seen much success.
I was able to flash TWRP and get it to boot a couple times, but only from the fastbootd menu and even when I was able to boot TWRP and attempt flashing Magisk it failed every time (far to quickly for me to even read the red text in the log) and would immediately reboot TWRP, taking me back to the recovery lock screen. I'm also not used to having two different bootloaders on a phone so I'm still not quite sure which one I'm supposed to use for flashing (although fastbootd has so far been the only one I've achieved any success with) and the stock recovery has been a dead end at least 50% of the time I was able to get to it (I just get the dead Andy with the "no command" dialog and the hard buttons do nothing) So I eventually gave up flashing the Magisk zip and decided to try patching the boot.img instead. I used fastboot to flash the patched img to both the boot_a and boot_b partition, which seemed to work at first, until I realized I had no mobile signal and my touch screen was unresponsive. I just spent the last hour or so unbricking it with Lenovo's Rescue & Smart Assistant. I've read plenty of threads where these same exact issues happened to others but I've yet to find any kind of effective work-around or an explanation as to why its happening.
Even when I was able to get TWRP to boot it never seemed to survive a reboot. I'd have to flash it again every time in order to get into it. It's also been quite a while since I've rooted a phone so I'm still pretty new to treble enabled devices and their surplus of confusing partitions, a few of which I wasn't even able to mount/unmount in TWRP, which was a bug I thought was fixed a while ago, but to my knowledge I have the most recent version and I'm still getting these same bugs
Basically at this point I'm at a loss for ideas so any and all advice or suggestions would be much appreciated. I apologize if this post just sounds like a long winded complaint or I didn't provide enough info for anyone to work with (I'm running late for work and I'm mentally exhausted lol) but hopefully someone on here can provide me with some answers. I'll try to post more specific info and maybe some logs after work but until then godspeed.

AMShiech said:
Okay, so I'm having a real b**** of a time getting root or even TWRP on my Moto G Fast (Boost mobile) and I really don't understand what it is I'm doing wrong. I've carefully gone through pretty much every thread available on XDA (and basically everywhere else) pertaining to getting root/TWRP on this device and from what I've gathered its been a pretty simple process for most other people with this device but for some reason nothing has worked for me. I should also note that my phone has had the most recent OTA update, which I was led to believe would make things easier but apparently not lol. So far the only thing that's gone off without a single hitch was unlocking the bootloader. Beyond that nothing I've tried has seen much success.
I was able to flash TWRP and get it to boot a couple times, but only from the fastbootd menu and even when I was able to boot TWRP and attempt flashing Magisk it failed every time (far to quickly for me to even read the red text in the log) and would immediately reboot TWRP, taking me back to the recovery lock screen. I'm also not used to having two different bootloaders on a phone so I'm still not quite sure which one I'm supposed to use for flashing (although fastbootd has so far been the only one I've achieved any success with) and the stock recovery has been a dead end at least 50% of the time I was able to get to it (I just get the dead Andy with the "no command" dialog and the hard buttons do nothing) So I eventually gave up flashing the Magisk zip and decided to try patching the boot.img instead. I used fastboot to flash the patched img to both the boot_a and boot_b partition, which seemed to work at first, until I realized I had no mobile signal and my touch screen was unresponsive. I just spent the last hour or so unbricking it with Lenovo's Rescue & Smart Assistant. I've read plenty of threads where these same exact issues happened to others but I've yet to find any kind of effective work-around or an explanation as to why its happening.
Even when I was able to get TWRP to boot it never seemed to survive a reboot. I'd have to flash it again every time in order to get into it. It's also been quite a while since I've rooted a phone so I'm still pretty new to treble enabled devices and their surplus of confusing partitions, a few of which I wasn't even able to mount/unmount in TWRP, which was a bug I thought was fixed a while ago, but to my knowledge I have the most recent version and I'm still getting these same bugs
Basically at this point I'm at a loss for ideas so any and all advice or suggestions would be much appreciated. I apologize if this post just sounds like a long winded complaint or I didn't provide enough info for anyone to work with (I'm running late for work and I'm mentally exhausted lol) but hopefully someone on here can provide me with some answers. I'll try to post more specific info and maybe some logs after work but until then godspeed.
Click to expand...
Click to collapse
You saw my thread
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
You saw my thread
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah I tried following exactly that procedure and it bricked.

Dude. I have this phone. Same Carrier.
I know, it can be a pain in the ass. I've been on medical leave for 3 years though and needed a project to work on so I've been coming up with my own methodologies to fix this process...
Like, I've got a script that should de-brick your phone back to stock no matter what, and then we can move forward.
Are you on discord? This is going to be a bit too slow. I can just create us a channel or something though.

Lanlost said:
Dude. I have this phone. Same Carrier.
I know, it can be a pain in the ass. I've been on medical leave for 3 years though and needed a project to work on so I've been coming up with my own methodologies to fix this process...
Like, I've got a script that should de-brick your phone back to stock no matter what, and then we can move forward.
Are you on discord? This is going to be a bit too slow. I can just create us a channel or something though.
Click to expand...
Click to collapse
I appreciate the reply man, and sorry for the late response (I only get one day off a week), but I fortunately got it figured out finally. My main issue was that this is the first A/B treble enabled phone I've ever tinkered with, and most everything I read claimed I had to boot to fastbootd in order to flash twrp but that never seemed to work.
My computer would recognize the phone as a fastboot device while in fastbootd but that's about it. Everytime I tried to flash in fastbootd the output either claimed there was 'no such file' or it appeared to work, but when I tried booting to recovery I still got stock recovery. I was finally able to get TWRP to stick by just booting it initially from the normal bootloader and using TWRP to flash itself to the recovery partition.
Then I was able to install magisk in TWRP by formatting data and flashing v21 instead of the latest version (Everytime I tried flashing v22 from TWRP it failed). Then after booting system, going through setup, and installing magisk manager I found Id successfully achieved root and was able to update to magisk v22 via MM without bricking.
After all that trouble I'm a little nervous to try a custom ROM cuz stock with root is basically perfect so far. Now the only thing I'm struggling with is figuring out how to set selinux to permissive so I can install BusyBox to xbin.

Stuck on Boot Animation after Update :(

Hi, I'd like to start off by saying I'm new here, and have went over all the newbie threads as best as I can. I appreciate how welcoming this forum is, I never took that much of a deep look at it besides looking at threads in the past for multiple things. Still very new to all this stuff in general. Due to being stuck rn, I cannot provide a proper signature, apologies.
Couple Days Ago- Unlocked bootloader on my Oneplus 7 Pro using adb, flashed TWRP for the then current version for the 7 Pro Guacamole referenced from the post here, then sideloaded Lineage through TWRP. Started using the device and it seemed to have went well and like a pretty average install as far as I can tell.
Note- I'm not sure if I installed TWRP properly, as I was able to boot into TWRP through power button and volume up, but I remember also accidentally booting into the Lineage Recovery at some point after my phone was already rooted after the next step, but idk honestly. I note this bc I seen that there might be another step to permanently install twrp once inside after flashing, but not sure, apologies. My lack of knowledge feels inexcusable with how abundant it is here.
I rooted the device soon after with magisk, which I installed the zip (which was simply placed in main directory) through TWRP, then finished the install in the OS and that seemed to be good. Mention I didn't actually know that the device was rooted after the first time, dumb ik, but I did this maybe 3 times before realizing that the device was indeed already rooted and I did it extra times.
Today I got the notification for a Lineage OS update in the OS. Because I know it's coming, yeah, ik how stupid this was to not make backups beforehand as I already have a good bit on there I don't wish to lose, although I have MEGA for all my super important stuff like my password database, etc. Needless to say, I have learned my lesson. Nonetheless, I downloaded the update and pressed the install button. It said installed and would need a reboot, so I did. Then it got stuck in the boot animation for 1.5+ hours.
Force shutting it off and into fastboot, I could boot into the updated lineage recovery, but no TWRP. I have tried reflashing the previous version of the lineage recovery and it did not make a difference. I also tried flashing the next newest version of TWRP for the 7 Pro running guacamole, but then I couldn't get any further than the bootloader.
I ended up reflashing the up to date version of the lineage recovery and it sat doing nothing for a while, so it's off now. I presume that Nebrassy and other devs for TWRP are working on a version for the new update, but idk how long that takes, not complaining though. (mad respect for all who make lineage, twrp and all this possible) (not to mention I don't even know the root of the problem)
Any thoughts or help would be much appreciated, and feel free to ask questions. I would preferably not have to wipe it all and restart, so I'm looking for solutions, although I'm willing to accept this might be for nothing and take the L. Lastly sorry if I have done anything "wrong" in this thread, lmk if I can do anything better, I appreciate it.