Database Info

[Q] To flash or not to flash

Ok so seeing as the Lollipop is rolling out today for the 2012 N7 and moto x, and I just read a post that it's being batch pushed to our great N5.
I am wondering if I should flash stock 4.4.4 and hit the check now button intill it comes or if I should wait for a custom build of Lollipop.
If I do go stock for the time being, can someone point me to a flashable stock image... And when 5 hits my phone i will up load an image for you guys...
Any way what would you do?

Form your own opinion

Well Where can I find a flashable stock image of 4.4.4

1. Google has already explained how OTA works. It starts at 1 percent of all devices and gradually climbs. If you don't get it the first batch on OTA, clicking Check now doesn't do a single thing, you don't lose your place in line or get another chance. It's a one time thing.
2. Because of #1 ... I'd wait for the factory image and flash that after backing up all your data.

technically, source is not up for the n5, and neither is the android 5.0 stock image for the n5. and @dicecuber is right, its up to you to decide, not us. me.. i flashed a aosp build with the older n5 binaries.

If you want stock use a toolkit. Better yet use google.

kitila said:
If you want stock use a toolkit. Better yet use google.
Click to expand...
Click to collapse
never ever tell someone who has no idea what they are doing to use a root toolkit. that is the absolutely worse piece of advice.

Going off of what the OP is saying, does anyone think that the image will be able to be dirty flashed over the latest Developer Preview?

Ramocity said:
Going off of what the OP is saying, does anyone think that the image will be able to be dirty flashed over the latest Developer Preview?
Click to expand...
Click to collapse
some ppl that tried, had issue. but i dirty flashed aosp lollipop over kitkat without issue.

[Bootloader][d800][JB/KK/LP][2015.07.29] Flash JB/KK/LP Bootloader

Easily Switch Between JB/KK/LP Bootloader
!! d800 ONLY !!
Make sure you flash the right model!​
With the advent of BUMP, we can now use the KK bootloader. A lot of projects preserved the old JB bootloader, since that was needed due to loki. This is the easy way to update your JB bootloader to the new KK bootloader.
Inspired by @dorimanx who did this for the d802. I followed suit and made this for the d800.
What this is:
As it simply says, it upgrades (or downgrades) the bootloader. This includes several other small partitions, in addition to aboot and sbl1.
Sources:
10d & 20c - Extracted from TOT file
20y & 30f - I started with 20d, then did FOTA to 20y and extracted the partitions. Then I did FOTA to 30f and again extracted the partitions.
What this is NOT:
This does not touch your boot, recovery, or modem/radio partitions. You must make sure those are compatible BEFORE flashing this.
WARNING: You can easily brick your phone if you mess this up! This is for d800 ONLY!!! Also, you must have BUMPed boot and recovery images already on your phone to use KK bootloader or you will get fastboot error (or it just won't boot). JB supports BUMP images and LOKI images. KK only supports BUMP.
Lollipop Information:
Special LOLLIPOP WARNING: At this time, the Lollipop BL is not exploitable. Therefore, if you flash Stock LP BL, you will probably brick, or at a minimum, you will lose access to recovery.
To use a BUMPED lollipop ROM, you should install the Lollipop Bump bootstack on my site. It is all of the 30f Lollipop partitions, with a 20y aboot (so bump will work).
Download:
Did you read the warning above? If not, DO NOT DOWNLOAD.
Did you read it twice? If not, DO NOT DOWNLOAD.
Do you understand everything it says? If not, DO NOT DOWNLOAD.
Do you know how to recover if you mess your phone up? If not, DO NOT DOWNLOAD.
I do not want any posts saying "HALP I MESSED THIS UP."
Which bootloader am I currently on?
The only sure way to know is to flash one, or know which one you flashed last.
You can get an idea of your bl when you use the button combo to enter recovery (VolDwn+Pwr, release and repress when LG logo comes up, hold until menu comes up) the screen looks different. On JB the phone asks you to repeatedly press power for factory reset. On KK the phone has you use the volume rocker to pick different menu options.
Download:
https://www.gregtwallace.com/lg-g2/d800_d801-bootloaders/
Again, thanks to @dorimanx.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal

Update 2015.07.29
-Version 1.1 does NOT flash misc partition.
+Misc contains things like MAC addresses and doesn't need to be flashed.
Update 2015.05.12
I have added the 20y KK bootloader, which appears to be different than the originally posted 20c. Both are now posted.
Additionally, I added the LP 30f bootloader. WARNING: This bootloader is not (yet?) exploitable! Flashing it will likely brick your device, or at the very least it will break your recovery. You have been warned!

Reserved2
Reserved2

Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader

raulx222 said:
Cool thing! And nice work! I was just looking around to learn more stuff about bootloaders ..did dorimanx made a thread for d802?
Your awesome version of TWRP is bumped, dorimanxs kernel is bumped too thats all i need to switch on kk bootloader
Click to expand...
Click to collapse
No he didn't, but he posted the d802 version under his kernel thread, which is linked in my signature.

Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.

You, sir, are a badass. Thank you for this
Sent from my LG-D800 using XDA Free mobile app

Formhault said:
Great initiative, @blastagator!
Now... On to the actual bootloader... stuff.
EDIT : Nevermind. Just noticed that this is for the D800 only... and I have a D802, lol.
Click to expand...
Click to collapse
As stated in the OP, dorimanx made exactly the same zip for the d802 to update the bootloader and the other necessary partitions.
You'll just need a bumped recovery + bumped kernel.
Just in case you would like to upgrade to KK bootloader
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader

Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.

Voltaine said:
I'm just waiting for render to release bumped R26 and the first thing I'll do is update the bootloader
Click to expand...
Click to collapse
Me too, I guess :silly:

idoluvizsick said:
Could someone please be kind enough to make one for vs980? I tried making one myself by picking the same exact files off of vs980 kdz but it didn't work.
Click to expand...
Click to collapse
I used this: http://forum.xda-developers.com/showthread.php?t=2600575
Extract the partitions out of the stock tot, then just use a simple flash script. Again, if you don't know what you're doing - it is VERY easy to mess up and DIFFICULT to recover from.

Noticing this says bumped boot and recovery required in the op. Was wondering even if I'm on stock everything, boot included, do I still need to be bumped. I would say yes on the recovery due to the nature of how autorec worked. But what about boot, since it is bone stock? Thanks for the info. Thanks for your work on this phone.

Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?

buffal0b1ll said:
Yikes I tried this with 12/5 AICP 5.0 drgravy d800, Render5, and blastagators bumped TWRP 2.8.2.0.
Installed the KK-20C bootloader, the device spent a long time on on the LG logo with a few vibrates, then it blackscreened. While blackscreened plugging into PC started charging and gave me access to Internal Storage. Tried a power off and back on again with same result.
Luckily, manually going into TWRP and flashing the JB-10D bootloader got things back to normal.
EDIT: Just dawned on me that I had the dr87 Working Rotation JB Baseband installed. Perhaps I should have tried with the KK Baseband?
Click to expand...
Click to collapse
I don't think it works with JB based kernels.

sr20ryda said:
I don't think it works with JB based kernels.
Click to expand...
Click to collapse
I used Render 5 which is a L Kernel. Is this JB based?

buffal0b1ll said:
I used Render 5 which is a L Kernel. Is this JB based?
Click to expand...
Click to collapse
Yes. All the LP builds have JB based kernels AFAIK.

sr20ryda said:
Yes.
Click to expand...
Click to collapse
Is there a bumped kernel that d800 can use on L with KK bootloader then?

I don't believe so.

It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart

siggey said:
It works only with dorimanx on stock based rom, no cm aosp aicp et
_____________________________Write less read more and be smart
Click to expand...
Click to collapse
After reading ALOT of info heres where i am. I think our good guy render is trying to get his kernel working bumped for KK bootloader and lollipop builds.. heres where i got sad.
It seems recently there is ALOT of dev arguements on the nature of opensource bump so much so that the the orginators have actually closed down and stopped development on the project. lets not go any further with that disucssion, there are other threads for that if you care to read.
So basically i dont have a build environment right now to try to bump any kernels using the instructions and I'm not sure what to think right now considering what i HAVE read. I actually stay away from posting alot of things on XDA that i do on my own, because of this very nature i have seen pop up to many times to count. So to summerize:
Dont have a build environment where i am right now to try...even when i get home im not sure how i will feel since i do respect the codefire guys but understand why someone would have done what they did. If i am successful getting someone elses work say renders kernel, to finally boot ill let him know but im sure render will figure it before i even do that :highfive:

Second hand nexus 5 Q?

I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?

Help?
Sent from my Nexus 5 using XDA Free mobile app

I think nobody wants help a KILLER

HIGKILLER said:
I bought this nexus 5 from a previous user, noticed bootloader unlocked, diferente kernel(althought i flashed another already), but something caught my eye, im not sure if i have the stock rom, as i get an update of 16mb and fails.
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.

Yaz75 said:
It is not stock. Unlocked bootloader is fine, everything else is a no-go. The different kernel is the glaring problem, you can not apply an OTA with that non-stock kernel. The first, most complete, easiest option is to flash the latest factory image. Seeing as this is a new phone to you, I can't imagine that you have a ton of personal info to save. For me personally, I'd flash the image just so I know that I'm starting with a fresh clean slate. Then you can read up and root/mod how you'd prefer.
Click to expand...
Click to collapse
I have experience with custom roms all that, i did flash this kernel, but the room, is what bothers me. and thank you, i was kinda sure this wasent stock rom! Thank you

HIGKILLER said:
"devcheck app"
Under system = Codename: Hammerhead
5.1.1
Build: LMY48I
Is this stock?
Click to expand...
Click to collapse
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.

Wakamatsu said:
Not enough information from this to say. The custom kernel you installed is enough to prevent OTA updating.
Click to expand...
Click to collapse
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?

HIGKILLER said:
i can never find a decent post, how can i be sure this is stock rom, without having to flash the stock one?
Click to expand...
Click to collapse
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.

Wakamatsu said:
It would be easy to say if the build didn't match a legit N5 image. If the build info in build.prop isn't informative, look for apps/features that shouldn't be in a stock image, eg. AOSP apps replacing the Google versions. Unfortunately, you do have to have some familiarity with stock Google to be able to spot something that's out of place.
Click to expand...
Click to collapse
thank you sir

[US996] 100% Stock deODEXd ROM

Do you have a US996, and want to be able to start modding/theming the ROM? FINE! HERE! Lol...
Please know, this is 100% stock, including kernel. Also, I do not own a US996 (but I do own the H918). This ROM has already been tested (thanks @monsieurtalbot !)
No changes on the ROM. SuperSU gets flashed alongside the ROM. Oh, and setenforce=0 is set via init.qcom.post-boot
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently, RC8, 3.0.2-0, and 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it could also be that you are on an old TWRP build. . You have been warned.
This is for the Factory Unlocked US Cellular. Untested on the other US996.
Here we have the base NRD90M ROM from LG. The only difference from this, and what came on your phone is, that it is not ODEXd anywhere. DeODEXing basically bundles all parts of an APK together which saves space, allows for modification of the APK (like for System UI and stuff), and ever so slightly increases performance (by the littlest amount possible). This is ONLY for the US996.
Also, no need to wipe, as /system is fully removed (your apps and settings will stay since that is in /data). Since we only have 1 base from LG, ROMs don't need to be wiped, even if coming from ODEX.
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for inspiring me to learn to do it. Also, he supplied the stock System.img, boot.img, and sources for a custom kernel!/RealMVP

SUPER happy to say I am using this currently and it is flawless. Fantastic base for our custom unlocked US996 community.
No more systemless root. This is a full root and I was finally able to delete the stupid boot sounds.
Thx for letting me be the test dummy.
Just so everyone knows I dirty flashed in TWRP from stock and I have had 0 issues. I am a heavy power user.
Everything is working as it should be.
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Super excited for some custom roms. =)
---------- Post added at 10:53 PM ---------- Previous post was at 10:39 PM ----------
Moving this conversation over from the H918 thread...
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3

monsieurtalbot said:
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Click to expand...
Click to collapse
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP

Tilde88 said:
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP
Click to expand...
Click to collapse
There's another US996 for US Cellular - as we all know - so as things get released possibly for that model (which holds the same model number for whatever reason) and this thread ages - it might not be a terrible idea to exclusively specify so some poor soul down the road doesn't flash this to the wrong device... :highfive:

monsieurtalbot said:
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3
Click to expand...
Click to collapse
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess

Tilde88 said:
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess
Click to expand...
Click to collapse
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.

AlkaliV2 said:
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.
Click to expand...
Click to collapse
It would have to be later tonight, getting ready for work now. You can just double click the zip on your pc. If it opens without an error, you are good to go.

Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?

I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->

Mentalmuso said:
I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->
Click to expand...
Click to collapse
I honestly am not sure, but I did this just to be safe. As it turns out, FM is not included in the US996 ROM or kernel. I don't know of any other discrepancies, but that was enough for me.
IMO the H918 is the way to go, and just Unlock it from Tmobile. But that's just my opinion.

papashex said:
Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?
Click to expand...
Click to collapse
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:

You're right, no point. It's early in the game, hopefully there will be a .tot or .kdz (lg equivalent of ruu) for the eventual 7.1 update.
Thanks for your efforts to date.

Can this ROM be flashed on a sprint 997 that was unlocked and rooted using the dirty Santa method?
The reason I'm asking is because that process seems to change my phone to an unlocked 996 and I want to start fresh with a stock ROM.

Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....

bryancotton84 said:
Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....
Click to expand...
Click to collapse
It detects your model from build.prop I believe.
Can you change your model in your build.prop and retry?

Would anyone be willing on trying out a custom kernel? FM might be working. Plus other things and stuff .
I don't have a US996, so I can't test it. So be sure to have a stock boot.img and your stock /system/lib/modules folder. If this fails, you can simply flash your stock boot.img right within twrp, and then push the modules folder into /system/lib/modules. Or you can reflash the ROM.

i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed

Get Ur Noob On said:
i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed
Click to expand...
Click to collapse
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here

Tilde88 said:
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here
Click to expand...
Click to collapse
basically until the phone actually boots into the os it looks like a messed up tv showing only static colors and you cant see anything, what you do is you wait until it boots into the os and shut the screen off then hold your finger over the front camera and it fixes it and everything is normal.

Tilde88 said:
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:
Click to expand...
Click to collapse
Any chance you could do it, If it's not too much trouble? I'd like to install it on my F800L, if I can, and I seem to be having issues with the current deodex'd version.
If I'm honest, I have no idea if it will make any difference whatsoever, and the issue could be something completely unrelated (ihavenoideawhatimdoing), but I'd just like to try it, anyway. I got an odex'd H918 working, so It has me wondering if it makes any difference?

[Dec-24-2016] H850 20A DeOdexed

Your warranty is now void, don't blame me if your phone blows up blahblahblah.
Only system and kernel are being flashed, no Modem, BL, etc. You should update to 20A before using.
Have not tested this myself, due to not owning the H850. edit: flashed it on T-Mobile 830 for fun with 830 boot, no surprise, didn't work.
Decided to post anyway. If your going to use it, BACKUP, BACKUP, BACKUP
Based off of 20A Complete zip from @autoprime. Only things touched are bootanimation (pixel black) and renamed recovery-from-boot.bak. It's also been zip-aligned.
Flash in recovery, profit??
SuperSu and Busybox included. Only /system is wiped, data left alone.
Can dirty flash over current 20A if you like.
Any errors, etc, would most likely be related to deodexing as all files are stock.- Again, haven't tested this one myself
Link: H850_20A_DeOdexed
MD5: bb58ff90c21bbc09b4d0f1c132fa91b3
If anyone would like to use this as a base, Great! Would appreciate some credit. [emoji3]
Enjoy.
Optional: Adjust Screen Color , Fluence HD Patch
Credits: @autoprime for stock zip. @Chainfire for supersu. @SuperR. for the kitchen. @Tilde88 for pointing me in the right direction. @PlayerZ_ZawZaw for bootanimation. @jcadduono for TWRP.
It's people like them that make Android great!
Finally, thanks to Google/LG & XDA.
...whew.

Reserved

lordodin912 said:
Your warranty is now void, don't blame me if your phone blows up blahblahblah.
Have not tested this myself, due to not owning the H850.
Decided to post anyway. If your going to use it, BACKUP, BACKUP, BACKUP
Based off of 20A Complete zip from @autoprime. Only things touched are bootanimation (pixel black) and renamed recovery-from-boot.bak. It's also been zip-aligned.
Flash in recovery, profit??
SuperSu and Busybox included. Only /system is wiped, data left alone.
Can dirty flash over current 20A if you like.
Any errors, etc, would most likely be related to deodexing as all files are stock.- Again, haven't tested this one myself
Link: Uploading...
MD5: bb58ff90c21bbc09b4d0f1c132fa91b3
If anyone would like to use this as a base, Great! Would appreciate some credit. [emoji3]
Enjoy.
Optional: Adjust Screen Color , Fluence HD Patch
Credits: @autoprime for stock zip. @Chainfire for supersu. @SuperR. for the kitchen. @Tilde88 for pointing me in the right direction. @PlayerZ_ZawZaw for bootanimation. @jcadduono for TWRP.
It's people like them that make Android great!
Click to expand...
Click to collapse
Um, so why post something for others that you haven't even tested for yourself ? Seems a bit dubious? No?
---------- Post added at 06:58 AM ---------- Previous post was at 06:56 AM ----------
Anarchist77 said:
Um, so why post something for others that you haven't even tested for yourself ? Seems a bit dubious? No?
Click to expand...
Click to collapse
Edit... At least have an H850 tester first?
Regardless, thanks for another option for a ROM. Hopefully something good 😊

^Better than not sharing at all, eh? ; ) Not a dev myself, just learning. Enjoy

lordodin912 said:
^Better than not sharing at all, eh? ; ) Not a dev myself, just learning. Enjoy
Click to expand...
Click to collapse
Hey, all good. No offence meant.

Anarchist77 said:
Hey, all good. No offence meant.
Click to expand...
Click to collapse
Let me know if you end up trying it. I'll update OP and give you credit.

Right on! So this should work well with FluenceHD, potentially trying to bring myself to update to Nougat, but man Xposed has some pretty clutch tools, and reverting back to marshmallow I'm reading is a few more steps than I would like to take in a given night, you know if I decide that no ads on YouTube and background playback is worth giving up...
Still thank you for uploading and I will report back if I decide to pause Xposed in my day to day

Pphish20 said:
Right on! So this should work well with FluenceHD, potentially trying to bring myself to update to Nougat, but man Xposed has some pretty clutch tools, and reverting back to marshmallow I'm reading is a few more steps than I would like to take in a given night, you know if I decide that no ads on YouTube and background playback is worth giving up...
Still thank you for uploading and I will report back if I decide to pause Xposed in my day to day
Click to expand...
Click to collapse
It'd be nice if you could dual boot it alongside MM (wishful thinking). Don't think the kernel would boot on the old bootloader....maybe someone with more knowledge can help, or a daredevil could just try to flash it. The older MM modem should still work though, maybe. Shouldn't hurt? if your flashing in dual boot or just through TWRP normally because there's no modem, BL etc being flashed just system&boot.
Now with my old S4 there was no problem running an older BL with newer kernels, but this phone....idk.

Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation

Pphish20 said:
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation
Click to expand...
Click to collapse
Hmmm I removed the assert from updater script already....maybe TWRP needs to be updated??
Just finished DeOdexing 20B so I hope this is working.....

lordodin912 said:
Hmmm I removed the assert from updater script already....maybe TWRP needs to be updated??
Just finished DeOdexing 20B so I hope this is working.....
Click to expand...
Click to collapse
Im using 3.0.2-1
I'll get you a log soon and will gladly test 20b whenever that's uploaded

Going to try to flash this 20A myself soon, with a replaced 830 boot.img and see what happens......

Pphish20 said:
Im using 3.0.2-1
I'll get you a log soon and will gladly test 20b whenever that's uploaded
Click to expand...
Click to collapse
Ok, just downloaded 850 20A checked MD5, then replaced boot.img with 830. Flashed fine, no problems. Wouldn't boot though....no surprise really.
Have you checked the md5? could be a bad download, it is mega after all. Can't think of another reason why it would flash here but not on yours....

lordodin912 said:
Ok, just downloaded 850 20A checked MD5, then replaced boot.img with 830. Flashed fine, no problems. Wouldn't boot though....no surprise really.
Have you checked the md5? could be a bad download, it is mega after all. Can't think of another reason why it would flash here but not on yours....
p.s. 20B has finished uploading....making thread soon.
Click to expand...
Click to collapse
Yeah md5 is good... I'll send you a TWRP log later or possibly just forget about it if 20b works
Thanks again!

Delete