Develop Bugs

[SOLVED] Oh shoot, need some help.

I flashed a ROM and now I can't make it past the boot image. I'm not sure why. It's been there for the past few minutes. So I pulled battery and went to bootloader to boot to recovery and retry. Recovery and root is working fine, but somehow it says I have an update package on my SDCard....so now my only two choices are to install or not to install and reboot.
Since I can install an update package, I think it does mean that nothing vital is screwed up. I've just been checkmated.
Now how do I enter recovery? I know I can always install an HTC update package via ADB, but I don't want to lose root and have to reroot and all.
So is there some way I can get into recovery without bootloader?
Thanks
EDIT: It looks like there's some way to boot into recovery using android SDK, but I can't figure it out. Any help?
EDIT2: I don't have a micro SD card reader, so I can't delete the pesky update package (it might be some boot.img I downloaded but never got around to)
Final EDIT+ Solved
For those who didn't understand SDK and ADB, this was a great help:
http://www.youtube.com/watch?v=y6K1XLmafPc
Actually I realized that I could boot into bootloader and then recovery without an SD card. Lawd have mewcy on idiots like me When it started getting into 4ext I popped in my SDcard again and booted right in. Everything should now be fine.
On a side note, I realized I forgot to backup my previous ROM in my haste to see if MIUI Camera worked on certain ICS roms (I got it completely working in blackout, and partially working in NeroXL). I hope to god I'll like XGS, because this was more effort than I'd like to spend on my phone.
I'll leave it to the Mods decision on whether or not to delete this, maybe this info will help others.

No camera on MMB29K?

I just flashed the Factory Image MMB29K (flash-all.bat then reinstalled TWRP and SU manually). Now the camera doesn't work (see attachment below). I did check the MD5 and it matched.
Any help is greatly appreciated.

Very odd. If I do not install TWRP (I have tried both 2.8.7.0 and 2.8.7.2) or SU (Beta 2.52) the camera works fine. Or maybe it's the version of the modified boot image (Chainfire's mdb08i) that's not compatible.

Disregard. Found another thread with a discussion of the same issue. The problem is with the old mdb08i boot image.
In case anyone is experiencing the same issue please see this post:

The way I just rooted 2 5x's was, I unlocked the bootloader, flash-all on the MMB29K update, reinstalled TWRP, and then installed Super SU v2.61. You don't have to use a modified boot, that version of Super SU does the modifying for you. Just make sure to read the directions - I got caught in a boot loop trying to install 2.61 over a modified boot (essentially I did the process backwards the first time.) Recovered, and did both phones just fine. Camera works great.

How is that systemless root - any problems so far? I was feeling lazy so stuck with the old fashioned version - haven't had time to read up on the new method.

The only problem I have had so far (and I had the same problem on system root as systemless) is when I boot into TWRP, it brings up the pattern lock. The problem is, sometimes it doesn't recognise my touch on the pattern, so I can't get it to mount the Data partition. When that happens, I either have to flash whatever I was going to flash using USB-OTG (luckily I bought one of these, and got it the same day the phone arrived) or keep re-booting into system, then back into recovery until I get it to work. Might be able to take the pattern off before I go into recovery, but that'd be a pain - and I think I'd have to re-do fingerprints every time, too.

Danariel - thanks for the reply. I think I'll wait until the next go around of updates before trying out the systemless root. Feeling extremely lazy right now.

Boot loop and factory image restore

Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.

Try the flash all script again with latest firmware and let it boot up completely. It will take a while, once booted, flash TWRP and root if you want.

ntropia said:
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Click to expand...
Click to collapse
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app

androidddaaron said:
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That's an interesting perspective, actually.
I didn't know that you needed a special image for rooted devices.
Although, I would imagine that's always possible to 'un-root' it, and honestly I was hoping that 'fastboot flash -w...' would have removed any trace of the root.
Is that the case?
Either way, where could I find these modified images?
Thanks a bunch!

Solved
I found the solution which, as it happens when nothing seems to be wrong, was fairly trivial.
Basically, the scripts provided with the stock ROM from Google has problems, and this last command fails:
Code:
fastboot update image-bullhead-mmb29p.zip
saying that system.img is missing.
To fix that, you have to manually extract the content of the files and proceed to flash manually userdata, system, etc...
The problem is that if you don't flash also vendor.img, you're in trouble, and the device will not boot.
Some of the guides that I've found were suggesting that you need to do it for the Nexus 9, and I didn't notice when other guides were mentioning it.
Once you flash the vendor.img, the boot loop is gone.
I'll put it here, I hope it can be helpful to somebody.
Thanks to androidddaaron and k.s.deviate for the support!
(I've thanked also used the thank button near the posts, but if there's more to do, let me know)
Now, back to mess up the Project Fi SIM...

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!

Re-Root? Possible partition messup, Lost root now stuck in fastboot

Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.

5k1tz0 said:
Hello, Sorry to bug you guys...I read multiple different fourms/how2s and I guess I'm a little mixed at what i should do. I Have the oneplus 7t (hd1505) with android 11 rooted, and after that I installed NikGapps after I had it rooted, then flashed nethunter. Was in the terminal as root, all was well..I believe It rebooted and would'nt boot to rom so i went and re'did magisk, may have used a different patched magisk? but now is stuck fastboot. Cant get it to boot.
Sorry for the maybes but I had brain surgry and my memories not the best. Everything was going fine so I didn't document things like normal. Anyways, Is there a program that helps with thiss? MSM somthing? or could anyone please point me in to a nice how2 or some quality links to assist? I really apprricate it, normally I'd just test till I get it, but I think I may be at a point where I could really mess it up.
Click to expand...
Click to collapse
If you don't care about data then use msm tools to factory restore. Or you can flash boot image of the rom you were using (unpatched) in fastboot mode itself.

No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.

5k1tz0 said:
No need to keep data, I'd prefer to wipe device and start fresh instead of getting stuck on the concept of A/B partitions. I get the CMD getvar, but I'm not sure if i flashed the lineage OS to one or both...at 1 point i think i was booted in A, now its saying B. I got overeager and downloaded multiple ROMs and not sure which one worked. In the past I usually downloaded a few and the first one to work I used. Not smart...I know. If I wanted to wipe all and start fresh with gaspps and root, where/how should I do that? I can't just fasatboot oem unlock , could I? Would you recommend stock OS? Lineage? Thanks for your help BTW.
Click to expand...
Click to collapse
Go to this thread for MSM Tool download and instructions: Unbrick tool to restore your device to OxygenOS