[Q] D405n and D405ds IDs mixed - LG Optimus L90

Hello everyone,
my D405n is partially correctly recognized as w7n:
ro.product.board=w7n
ro.build.product=w7n
ro.cm.device=w7n
ro.product.device=w7n
ro.build.product=w7n
ro.cm.device=w7n
However partially incorectly as w7ds:
ro.hardware=w7ds
ro.boot.hardware=w7ds
I have unrooted my L90 using towelroot, unlocked bootloader and install recovery with
[GUIDE] Unlock Bootloader and Flash Custom Recovery L90 D410, D405n, D405 [CWM][TWR] method using file for D405n and flashed ROM from @Quarx. In order to flash the ROM I had to remove hardware=w7 check. Now automatic update works in the sense, that incremental update is downloaded, but due to hardware=w7 check I have to modify the updater script every time. Any idea how to correct ro.hardware and ro.boot.hardware entries? I have attached my build.prop file and output from getprop command, if that could be helpful.
Best regards

lecterek said:
Hello everyone,
my D405n is partially correctly recognized as w7n:
ro.product.board=w7n
ro.build.product=w7n
ro.cm.device=w7n
ro.product.device=w7n
ro.build.product=w7n
ro.cm.device=w7n
However partially incorectly as w7ds:
ro.hardware=w7ds
ro.boot.hardware=w7ds
I have unrooted my L90 using towelroot, unlocked bootloader and install recovery with
[GUIDE] Unlock Bootloader and Flash Custom Recovery L90 D410, D405n, D405 [CWM][TWR] method using file for D405n and flashed ROM from @Quarx. In order to flash the ROM I had to remove hardware=w7 check. Now automatic update works in the sense, that incremental update is downloaded, but due to hardware=w7 check I have to modify the updater script every time. Any idea how to correct ro.hardware and ro.boot.hardware entries? I have attached my build.prop file and output from getprop command, if that could be helpful.
Best regards
Click to expand...
Click to collapse
I'll send @Quarx a link to this thread.

Strange, I have a D405n too, but never had this issue. I wrote a guide explaining the way I unlocked the bootloader here. I used Quarx' latest TWRP, which can be found in his thread and just did a full wipe and flashed CM after that. Seemed to work for me. I would just try reflashing the KDZ again and restarting the unlock process with the newest files available.
EDIT: I just checked my build.prop and my w7n is recognized as a w7. The device is still recognized as the D405n though, so NFC does show up in the menu.

shinobisoft said:
I'll send @Quarx a link to this thread.
Click to expand...
Click to collapse
OK, thx. I hope he could provide some suggestions.

SubliemeSiem said:
Strange, I have a D405n too, but never had this issue. I wrote a guide explaining the way I unlocked the bootloader here. I used Quarx' latest TWRP, which can be found in his thread and just did a full wipe and flashed CM after that. Seemed to work for me. I would just try reflashing the KDZ again and restarting the unlock process with the newest files available.
EDIT: I just checked my build.prop and my w7n is recognized as a w7. The device is still recognized as the D405n though, so NFC does show up in the menu.
Click to expand...
Click to collapse
Is it necessary to flash the KDZ? Flashing/dd aboot.bin again should be sufficient I think. I did it, but situation is the same. I have checked aboot.bin files for D405n linked by people in different posts over xda forum (your link as well) and all the files are identical, so in my opinion there is no newest aboot.bin. Concerning TWRP I have tried latest Quarx version and also this version. No difference concerning w7n and w7ds mismatch.
Yesterday I tried also to flash Quarx' CWM instead of TWRP and surprisingly automatic update worked with no problem with hardware=w7 check. However, output/content of getprop command and build.prop file are unchanged. Strange. Looks like with TWRP hardware=w7 check fails while with CWM everything is OK, which would indicate different getprop output for different recovery.

Might be you guys got the D405n with softwareversion 10a, where my device had 10b.. Seen this before and most users with that combination seem to have issues. Might also be a total coincidence though. I don't know what the difference is, but I do know the Russians that made the aboot.bin files made a seperate one for D405n_10b and for D405_10a. So either the version for D405n combined with 10a is missing or you should be able to use one of those two versions.. But once again, this is pure speculation, I don't know if this can cause these issues.

SubliemeSiem said:
Might be you guys got the D405n with softwareversion 10a, where my device had 10b.. Seen this before and most users with that combination seem to have issues. Might also be a total coincidence though. I don't know what the difference is, but I do know the Russians that made the aboot.bin files made a seperate one for D405n_10b and for D405_10a. So either the version for D405n combined with 10a is missing or you should be able to use one of those two versions.. But once again, this is pure speculation, I don't know if this can cause these issues.
Click to expand...
Click to collapse
Is it OK, to use aboot.bin_D405_10a for D405n? I mean, no soft brick in that case? With stock ROM I had 10b as well.

lecterek said:
Is it OK, to use aboot.bin_D405_10a for D405n? I mean, no soft brick in that case? With stock ROM I had 10b as well.
Click to expand...
Click to collapse
I'm not sure, but even then you should still be able to flash the kdz and start over. It doesn't take that long to go through the entire process, I've done it multiple times already. I don't have these problems, so I can't experiment with these files.

Related

Error message when trying to update with LG Updater

Hi everyone!
First of all, sorry if this as been asked, tonight my Google skills didn't help me find an answer.
A friend of mine owns a LG Optimus 2X (P990) bought from Fido in Canada. Currently she's on Gingerbread and would like to update to ICS (which is the latest stock rom available from what I read)
She wouldn't get the software update OTA so she tried downloading the LG Updater software from LG directly. The software detects the phone and says an update is available.
At some point, a popup appear suggesting to make a backup. So far, everything is fine. Once the backup is done and she click the "Start upgrade" button, she gets this error message : "An Unsupported operation has been attempted"
Anyone ever seen this before? Is there a way to upgrade her phone without using the LG software?
Since it's not my own phone, I would prefer not rooting it.
If rooting is really the only solution? What would be a good guide to read to do the update? (I did read a few sticky posts... 1 is the all in one tool kit... it explains each feature, but is not really a guide and I still have some questions unanswered after reading it. The other guide I read, the download links are broken)
Thank you
BigBlarg said:
Hi everyone!
First of all, sorry if this as been asked, tonight my Google skills didn't help me find an answer.
A friend of mine owns a LG Optimus 2X (P990) bought from Fido in Canada. Currently she's on Gingerbread and would like to update to ICS (which is the latest stock rom available from what I read)
She wouldn't get the software update OTA so she tried downloading the LG Updater software from LG directly. The software detects the phone and says an update is available.
At some point, a popup appear suggesting to make a backup. So far, everything is fine. Once the backup is done and she click the "Start upgrade" button, she gets this error message : "An Unsupported operation has been attempted"
Anyone ever seen this before? Is there a way to upgrade her phone without using the LG software?
Since it's not my own phone, I would prefer not rooting it.
If rooting is really the only solution? What would be a good guide to read to do the update? (I did read a few sticky posts... 1 is the all in one tool kit... it explains each feature, but is not really a guide and I still have some questions unanswered after reading it. The other guide I read, the download links are broken)
Thank you
Click to expand...
Click to collapse
i want ICS too on my phone, and use LG tool several times but unsuccessfully, it is like that not working or i dont know...
you can use AIO tool, it is too easy to work with it, just follow instruction and install correct bootloader and thats it.
sejo789 said:
i want ICS too on my phone, and use LG tool several times but unsuccessfully, it is like that not working or i dont know...
you can use AIO tool, it is too easy to work with it, just follow instruction and install correct bootloader and thats it.
Click to expand...
Click to collapse
What would be the right steps?
Use option #4 to repartition the device for ICS and then option #7 to flash the ICS stock rom?
here, in this link is explaination how to root and install ROM:
http://forum.xda-developers.com/showpost.php?p=43869967&postcount=667
i work what it say in that post, and succes
sejo789 said:
here, in this link is explaination how to root and install ROM:
http://forum.xda-developers.com/showpost.php?p=43869967&postcount=667
i work what it say in that post, and succes
Click to expand...
Click to collapse
Thank you, I'll give it a try tonight
Alright, that didn't help at all.
First of all, I wanted to flash a stock ROM... the guide tells us to install CWM and we got stuck at the part where we have to flash the ROM because it would seem CWM won't take the KDZ (or bin/fls) files.
Now we can go to the SW Upgrade mode without the battery, but the smartflash utility time out after 3 minutes and end on an error.
We can also go to CWM with the battery... but with no apparent way to flash a stock rom.
We're stuck at the moment.
Edit : So in the end we flashed only the BIN file instead of both BIN and FLS. No more errors and the phone rebooted correctly under ICS! Yay!
BigBlarg said:
Edit : So in the end we flashed only the BIN file instead of both BIN and FLS. No more errors and the phone rebooted correctly under ICS! Yay!
Click to expand...
Click to collapse
so, problem is solved? or still have some problmes?
sejo789 said:
so, problem is solved? or still have some problmes?
Click to expand...
Click to collapse
It's fixed! We didn't flash the FLS file (which would be the baseband?) but the phone still booted properly and connected properly to the cell phone provider.

[Q] Your opinion please for a M/B transplant.

Hi, recently i managed to brick my Korean F340L G Flex so bad. I've tried almost everything software wise.
-The solution:
I'm planning to change the logic board from a Sprint LS995 model. I think it will work ok. Of course I'll have to some how get an unlock code in order to use it in Greece where I live.
I've seen in ebay some users providing for a small amount of money this code.
So, what do you think. Will it work as I'm thinking? Any comments, suggestions, guides welcome. Thanks
Here is a short story:
"Hello, to all, I'd like to share my experience and problem with my LG G Flex, as a last hope to find a solution to unbrick it.
I know that the talk here is about G2's, but I saw many users reviving their Flexes with OP's method.
So here is what I did in steps:
1)I rooted my Lg g flex F340L
2)New OTA, downloaded, but failed to install after reboot. The message was no OTAs for rooted devises
3)Tried to unroot, but with no success. Still no installation of OTA.
4)Found, and flashed the stock F340L rom , (had an EFS backup), from another user here(.tot file), with LGFlashTool.
5)SIM card was not recognized any more (Greece, Vodafone), so no calls. Did all the updates, but no SIM, still.
6)Hard reset, still no SIM.
7)Decided to flash stock F340K kdz rom, and install CWR. All good, SIM detected, OTA downloaded, but after reboot stuck at CWM nenu. Whatever I do just CWM.
8)No download mode, or usb support, just an LG FLEX unknown device. Got some drivers only to be seen as lenovo ADB device.
9)I found the test point on the motherboard and short circuit it. Got a qhsusb_bulk(qualcomm 9008) under COM ports, but not on a specific port.
10) No flash capability, and no partitions to try and flash the 10 or so, images. Ubundu, no luck with the partition detection either.
11)After many reboots and button long presses the CRW came back...again
Well as I can see, there is not so much support for the korean variants and I might have destroyed my phone. So, I need your advise in changing the motherboard. I found M/B's from AT&T and Sprint variants, to install to my F340L. I think it will work. After I will purchase an unlock code from lets say ebay to unlock it to all GSM networks ( I live in Greece).
What is CRW or CWR?
Are you referring to CWM? The recovery?
If you can boot into cwm your phone has a chance to be saved no need to change the mb.
By the way sprint doesnt give out unlock codes like att. There is an specific process to sim unlock sprints variant.
Alex_XV6700 said:
What is CRW or CWR?
Are you referring to CWM? The recovery?
If you can boot into cwm your phone has a chance to be saved no need to change the mb.
By the way sprint doesnt give out unlock codes like att. There is an specific process to sim unlock sprints variant.
Click to expand...
Click to collapse
Yes sorry, CWM I was refering to. Well, since I have no other option at the moment. I'll try to find that specific process you've mentioned when I get the board(help or hint welcome)
As, for the M/B change, no system partitions are recognized in order to flash individual .images to unlock them.
If you can access CWM you dont need to flash the .img files for your phone. Instead you could flash a stock zip through adb sideload or flash twrp through sideload too. Twrp allows MTP use so someone using an F340K can help you with a stock backup and you can unbrick instead of changing board.
Alex_XV6700 said:
If you can access CWM you dont need to flash the .img files for your phone. Instead you could flash a stock zip through adb sideload or flash twrp through sideload too. Twrp allows MTP use so someone using an F340K can help you with a stock backup and you can unbrick instead of changing board.
Click to expand...
Click to collapse
The only stock image I have is in .TOT file for the L variant. I also have stock .kdz file for the K variant. I can sideload to /sdcard/0/ directory only, if that helps. I'll try to find twrp.zip and try it. But the main problem is to find stock rom in .zip format.
I've managed to install twrp 2.8.0.0...
N3M3SYS said:
I've managed to install twrp 2.8.0.0...
Click to expand...
Click to collapse
Ok
now you could try to flash this rom.
let me know how it goes.
Alex_XV6700 said:
Ok
now you could try to flash this rom.
let me know how it goes.
Click to expand...
Click to collapse
Thnx for the link, but this rom says is for F340K, I have a F340L. In addition the download link is not working...
N3M3SYS said:
Thnx for the link, but this rom says is for F340K, I have a F340L. In addition the download link is not working...
Click to expand...
Click to collapse
Ok, this will take time friend.
I will try to make you a flashable zip of stock F340L KK.
Maybe it will take me some 4 or 5 hrs.
Alex_XV6700 said:
Ok, this will take time friend.
I will try to make you a flashable zip of stock F340L KK.
Maybe it will take me some 4 or 5 hrs.
Click to expand...
Click to collapse
That would be a miracle for me, I'll be waiting!

[Q&A] Bootstack (KK and L) for L90

Q&A for Bootstack (KK and L) for L90
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 Bootstack (KK and L) for L90. 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!
what can we do with bootstack ?
leandro_sousa said:
what can we do with bootstack ?
Click to expand...
Click to collapse
Bootstack is a bunch of files deep inside the phone. They are responsible for turning device ON and OFF, having SIM card support or download mode for flashing .kdz systems.
If you want to use stock KitKat or any customROM (KK or L) you need KitKat bootstack.
If you want to use stock Lollipop you need Lollipop bootstack.
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
grey heron said:
Hi,
At the moment I'm running stock lollipop on a d405N. The Phone is also rooted, and i've unlocked bootloader and flashed TWRP 2.8.6.0.
After flashing your KK bootstack, can I immediately flash a custom Lollipop rom and Gapps, and if so will my waveband work?????
Click to expand...
Click to collapse
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Xemidra said:
Yes. That's exactly for what bootstacks are made for.
If you will have any problems after using those files, let me know.
Also I would appreciate information if it worked so I could mark it as stable.
Click to expand...
Click to collapse
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
grey heron said:
Thanks for your quick reply,
I see i made an error, it should be baseband not waveband
A few more questions though, before flashing your bootstack should I do a clean wipe?
Also, captivate king says: quote: Flash this after flashing my ROM, and you should be good to go, does the order in which I flash matter or not????
Thanks in advance,
Click to expand...
Click to collapse
I figured out that you meant baseband
It's not necessary to do a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Xemidra said:
I figured out that you meant baseband
It's not necessary to a wipe. Changing bootstack does not affect /system, /data and /cache partitions, but if you'll have problems with your customROM you should of course start with a wipe.
There is no order in which you should flash your bootstack and ROM. I firstly flashed bootstack (while being on stock Lollipop) and restarted my phone to see if it worked. I had no SIM support so I knew that my flash was successful. Then I flashed CM.
One more important thing is that you cannot restart you phone if flashing bootstack fail. Also it's recommended to flash bootstack before you boot your customROM for the first time to eliminate any possible bugs caused by wrong baseband file.
If you have any more questions feel free to ask them.
Click to expand...
Click to collapse
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
grey heron said:
Hi again,
both bootstacks for D405N worked for me, no more problems with baseband and wifi, :good:so thanks again.
I was just wondering, why all the files in the bootstack? Wouldn't just changing the modem be sufficient? I know i'm showing my ignorance, but just when I think I've figured things out, I get back to square one
Click to expand...
Click to collapse
It's for compatibility reasons. To make sure that everything is working fine I changed all files. It's less secure but more effective.
Hi Xemidra and everyone else.
I have used this for about 12-14 times now, going from stock LP to custom ROM and back, and as far as I Know it's working without any problems.
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Is it something that a ROM chef could do?? Or is this a CM thing???
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil??? Anybody know more about this??? I've tried searching for this article again, but couldn't find it. I use google, anybody know a better search engine for these type of querries?
grey heron said:
It's a great timesaver, but wouldn't it be better that ROMs have LP as a base instead of KK, so that using bootstacks or other or reflashing KK wouldn't be needed?
Click to expand...
Click to collapse
Yes, it would be. You need to contact you ROM developer about this. I can't do anything about that.
Which bootstacks did you use ?
Another thought, the modem file used. I've read somewhere that its not just the variant, but that different regions, countries etc. can have different (optimal) modem files, ie what would work great for me in Holland, might be unacceptable for someone in say Brazil???
Click to expand...
Click to collapse
Maybe. I haven't head anything about that. No one complaint about quality of calls etc. I believe that different bootstacks for different variants are enough. Countrys from which I use the .kdz file to create bootstack are random.
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
http://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917
---------- Post added at 11:45 AM ---------- Previous post was at 11:28 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
i have D410_v20A stock rom rooted
what file can i use to first unlock my bootloader can i use D410_v20b_patched_aboot
no one helped me on this
my question is can i use any D410 hacked aboot to unlock my bootloader or what
please help i want to start try some new roms
Hi,
Am on a d405N myself, but I would stick to the same version aboot as your firmware: D410 v20a fw >>>> D410_v20a_patched_aboot. Stick with what works.
I wouldn't use just any aboot version. It might work, but why take the chance?
If you can't find the D410_v20a_patched_aboot, consider upgrading your fw to v20b first. Firmware is a bit easier to find.
It would be even better to flash a d410 v10 kdz, aand use a d410 v10 aboot. This way you wouldn't have to worry about using bootstacks.
Hope this helps, and stop spamming.
Odd Report
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
dnuuk said:
I'm here to thank you so much for putting all this information togetther, although it's possitive... my report should be a little odd, I want to report that BOOTSTACK_v1.4_D405N-10F helped me get my D400HN's (yes, D400HN) sim card running with Temasek's CM12... just in case someone is looking for an answer like this...
Thanks a lot!
Click to expand...
Click to collapse
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Xemidra said:
Your phone will from now present itself as D405n.
Because you seem like a nice guy I made a bootstack especially for you and you variant (D400hn).
It's not tested and it may be faulty. If you want to go ahead and download it. From what I read your variant has an unlocked bootloader so I included the stock one.
Click to expand...
Click to collapse
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
dnuuk said:
Awww! How nice and kind of you!!
I'll download it right away and give it a try tonight as soon as I get home... just a quick question... should I just flash it over the custom ROM I'm already using? or should I do a clean flash? If it's of any use, Im running CM12 Temasek Build.
Anyway, thanks a zillion for being so kind and dedicated, as well as for the patient for noob users like me :silly:
Hope you're well
Click to expand...
Click to collapse
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Xemidra said:
It shouldn't have any impact on your ROM but if you'll have any trouble then do the wipe.
Let me know if it worked for you.
Click to expand...
Click to collapse
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
dnuuk said:
Well bad news... couldn't wait to get home and flashed it already dear @Xemidra, as soon as boot starts i get a nasty error that says Error: Boot certification verify, secure booting error. Cause: boot certification verify (and about 6 times de number "520")... And it turns off automatically three seconds after showing that screen, if I try Vol Down + Power, release and push the same combination again (as trying to get in Recovery Mode, TWRP in my case) the numbers changed to a 4 digit number (something like 5340 or so), tried three more times to enter recovery mode and I get the factory reset confirmation but as soon as I accept on YES the phone turns off completely and won't turn back or respond (unless I take the battery off and put it back on)
Any ideas on how to come back to life? KDZ? I had a lot of issues with KDZ before, couldn't get the LG software to recognize my phone at all
Any suggestion would be greatly appreciated, thanks
Click to expand...
Click to collapse
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
dnuuk said:
I can get to Download mode, but it only says ROOTED (In red) and an user number i.e. USER B47, but LG Flash Tool won't recognize the phone (the drivers are fine, the computer does recognize the phone, not LG Flash tool 2014
Any aditional ideas or should I just forget I had a phone?
Click to expand...
Click to collapse
Try to use LG Mobile Support Tool ? It always worked for me. Make sure you really have all the drivers installed.
It will flash the original .kdz meant for your phone.
Sorry for all the trouble I guess that the bootloader was locked ? or it needed to be unlocked using oem-unlocked feature.

Problem when tried to update from CM13 20160502 to 20160506, my phone "dosnt work".

Problem when tried to update from CM13 20160502 to 20160506, my phone "dosnt work".
Hello guys,
Well, i was using CM13 for a long time without problem, but yesterday i tried to update to 06 may 2016, and when i clicked in "update" option, it restarted and the screen started to flash, i waited for about 10 minutes and it didnt changed, so i removed the batery and tried to start again, and it just loop in start screen forever, done a factory reset, and it worked, well, it was on, but a lot of problem started, i couldnt open de SD card (once i selected to use sdcard as internal, the worst choice of my life), the keyboard is not working.. i cant use my phone :/
I can start my phone, but cant access the SDCard and cant use the keyboard..
I really dont want to reflash a stock rom and TRY to root it (the last time it took me 4 days to root it, and i really dont remember how i did it, because none of the methods i found worked, just one from a russian forum worked to me using the lg stock rom 5.0.2), i'm about 2 hours searching for a pre-rooted 5.0.2 android rom for lg l90 d410hn, but cant find either :/
Can some one please save me ? I really LOVE CM rom and dont want to get back to stock rom, and i really need my phone working again :crying:
Thanks in advance!
Have a nice day.
Apparently i cant open it in download mode too.. if i press volume up + power, it just starts normally, without entering download mode :/
roxloljapa said:
Hello guys,
Well, i was using CM13 for a long time without problem, but yesterday i tried to update to 06 may 2016, and when i clicked in "update" option, it restarted and the screen started to flash, i waited for about 10 minutes and it didnt changed, so i removed the batery and tried to start again, and it just loop in start screen forever, done a factory reset, and it worked, well, it was on, but a lot of problem started, i couldnt open de SD card (once i selected to use sdcard as internal, the worst choice of my life), the keyboard is not working.. i cant use my phone :/
I can start my phone, but cant access the SDCard and cant use the keyboard..
I really dont want to reflash a stock rom and TRY to root it (the last time it took me 4 days to root it, and i really dont remember how i did it, because none of the methods i found worked, just one from a russian forum worked to me using the lg stock rom 5.0.2), i'm about 2 hours searching for a pre-rooted 5.0.2 android rom for lg l90 d410hn, but cant find either :/
Can some one please save me ? I really LOVE CM rom and dont want to get back to stock rom, and i really need my phone working again :crying:
Thanks in advance!
Have a nice day.
Apparently i cant open it in download mode too.. if i press volume up + power, it just starts normally, without entering download mode :/
Click to expand...
Click to collapse
ok so if you have sd card adapter for your laptop or pc you can easily download partition tool and fix your sd card(there is a lots of videos on youtube on how to do that) to fix your keyboard go to play store go to =my apps= in and go to any google app that you hace installe for example chrom browser then scroll all the way down and you will see =Google.inc click on =more= and then click on =all apps= and you should be presented with all of the google apps.. scrool down untill you see google keyboard BTW(if your AOSP keyboard is constantly fc go into settings apps and disable the keyboard) install the google keyboard and you are redy to go (AOSP keyboard is the same keyboard as the google one but this one you can change the height of it in the keyboard settings =GOOD LUCK=
lgl90 said:
ok so if you have sd card adapter for your laptop or pc you can easily download partition tool and fix your sd card(there is a lots of videos on youtube on how to do that) to fix your keyboard go to play store go to =my apps= in and go to any google app that you hace installe for example chrom browser then scroll all the way down and you will see =Google.inc click on =more= and then click on =all apps= and you should be presented with all of the google apps.. scrool down untill you see google keyboard BTW(if your AOSP keyboard is constantly fc go into settings apps and disable the keyboard) install the google keyboard and you are redy to go (AOSP keyboard is the same keyboard as the google one but this one you can change the height of it in the keyboard settings =GOOD LUCK=
Click to expand...
Click to collapse
REALLY thanks man, this should really have done with my problem, but.. i bricked it when i tried to factory reset, well, i did the [GUIDE] unbrick... and its on again, but with android 4.4.2.
In the lg-phone-firmware theres 3 v20 version, v20a, v20b and v20c, wich one of them i can root with the one click root method ? Or how could i root it in the v20c version ? The last time i rooted mine with pure luck, using a russian forum (that i dont remember the name...).
If you know, or any one, i would really appreciate the help!
Thanks again my friend, if i werent soo anxious, you would have saved me hahah
Her is the link for the root(I AM NOT RESPONSIBLE IF SOMETHING HAPPENTS TO YOUR DEVICE) http://forum.xda-developers.com/lg-l90/general/root-lg-optimus-l90-44-2-5-0-2-android-t3110257
You can also root any L90 Lollipop version, including 20c, with KingRoot. Download it from XDA.
lgl90 said:
Her is the link for the root(I AM NOT RESPONSIBLE IF SOMETHING HAPPENTS TO YOUR DEVICE) http://forum.xda-developers.com/lg-l90/general/root-lg-optimus-l90-44-2-5-0-2-android-t3110257
Click to expand...
Click to collapse
Tried this one, didnt work :/
lfom said:
You can also root any L90 Lollipop version, including 20c, with KingRoot. Download it from XDA.
Click to expand...
Click to collapse
Thanks man! This one works! hahaha
But i think i'm a idiot, tried to unlock bootloader using v20b version (because i didnt found the v20c :/), tried to install CM13, and got error something 7, well, bricked again hahahaha
I done the process to recover from hard bricked, and i'm with v20c LG stock rom again. I'm searching for one v20c aboot, if someone have it, i would appreciate it
Thanks guys, you're awesome!
roxloljapa said:
Tried this one, didnt work :/
Thanks man! This one works! hahaha
But i think i'm a idiot, tried to unlock bootloader using v20b version (because i didnt found the v20c :/), tried to install CM13, and got error something 7, well, bricked again hahahaha
I done the process to recover from hard bricked, and i'm with v20c LG stock rom again. I'm searching for one v20c aboot, if someone have it, i would appreciate it
Thanks guys, you're awesome!
Click to expand...
Click to collapse
if you have v20c now you can pool aboot using adb do i t at your own risk
lgl90 said:
if you have v20c now you can pool aboot using adb do i t at your own risk
Click to expand...
Click to collapse
Could you please send me the link you used to do it ? I tried using aboot.img from v20b, i found the v20a and v20b img, but not the v20c :/
Thanks
I would like to send.you the link but im having my lg l90 d415 hardbricked for 2years ... Just google it how to do it...
lgl90 said:
I would like to send.you the link but im having my lg l90 d415 hardbricked for 2years ... Just google it how to do it...
Click to expand...
Click to collapse
I think i'm an idiot,i really cant find a LG L90 D410hn V20c aboot.img :/
If i go back to v20b or v20a, is there any problem ? I want to go back to CM13..
If someone have the v20c bootloader img, please share here :crying:
roxloljapa said:
I think i'm an idiot,i really cant find a LG L90 D410hn V20c aboot.img :/
If i go back to v20b or v20a, is there any problem ? I want to go back to CM13..
If someone have the v20c bootloader img, please share here :crying:
Click to expand...
Click to collapse
There's full 20c bootstack AFAIK, you can use any other aboot to flash TWRP then flash bootstack.
lfom said:
There's full 20c bootstack AFAIK, you can use any other aboot to flash TWRP then flash bootstack.
Click to expand...
Click to collapse
I'm still learning about those things, soo, bootstack is something new to me, and seaching for lg l90 d410 v20c bootstack, found this one http://forum.xda-developers.com/lg-...k-kk-l-l90-t3118632/post63292272#post63292272, could you please see if is it ? Basically i need to enter TWRP, and then flash this .zip file ? I didnt found the aboot.img to v20c :/
Thanks my friend
roxloljapa said:
I'm still learning about those things, soo, bootstack is something new to me, and seaching for lg l90 d410 v20c bootstack, found this one http://forum.xda-developers.com/lg-...-kk-l-l90-t3118632/post63292272#post63292272, could you please see if is it ? Basically i need to enter TWRP, and then flash this .zip file ? I didnt found the aboot.img to v20c :/
Thanks my friend
Click to expand...
Click to collapse
D410hn is different than D410, hn variant is dual SIM and has NFC, its bootstack may have problems with D410. I suggest that you use latest bootstack for your model.
lfom said:
D410hn is different than D410, hn variant is dual SIM and has NFC, its bootstack may have problems with D410. I suggest that you use latest bootstack for your model.
Click to expand...
Click to collapse
Oh i'm sorry, i think i didnt specified it, mine is the D410hn version, soo this one is the right one ?
And i just need to install the .zip file using TWRP and then install CM13 ?
Thanks again
roxloljapa said:
Oh i'm sorry, i think i didnt specified it, mine is the D410hn version, soo this one is the right one ?
And i just need to install the .zip file using TWRP and then install CM13 ?
Thanks again
Click to expand...
Click to collapse
Yes, correct.
lfom said:
Yes, correct.
Click to expand...
Click to collapse
Tried that, well, same problem, error 7 when i try to install CM13.zip :/
I think it bricked my phone again..
What i did :
Rooted with Kingoroot
Unlocked bootloader using the aboot_unlocked.bin inside the .zip from the other topic
Flashed the .zip from the other topic
Tried to flash CM13.zip and got error 7
Now my phone just shows the LG logo and dont starts :/
roxloljapa said:
Tried that, well, same problem, error 7 when i try to install CM13.zip :/
I think it bricked my phone again..
What i did :
Rooted with Kingoroot
Unlocked bootloader using the aboot_unlocked.bin inside the .zip from the other topic
Flashed the .zip from the other topic
Tried to flash CM13.zip and got error 7
Now my phone just shows the LG logo and dont starts :/
Click to expand...
Click to collapse
Which TWRP did you use? Try another version, shoxxy's version may cause error 7 with some devices.
Also if you are still on an old version of KitKat you may need to flash the full bootstack to update modem partitions as well.
lfom said:
Which TWRP did you use? Try another version, shoxxy's version may cause error 7 with some devices.
Also if you are still on an old version of KitKat you may need to flash the full bootstack to update modem partitions as well.
Click to expand...
Click to collapse
Yep, i tried with the shoxxy version (http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150)
Do you know any version that is not having this problem ?
Thanks for your reply, i'll unbrick my phone again lol
roxloljapa said:
Yep, i tried with the shoxxy version (http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150)
Do you know any version that is not having this problem ?
Thanks for your reply, i'll unbrick my phone again lol
Click to expand...
Click to collapse
Your phone's system partition is empty, that's why it's stuck with LG logo. Simply copy the other (installable) TWRP zip and flash it with current TWRP and it should work. (Reboot afterwards, of course)
I have used the DatkBlue version from the same thread you linked, not sure if it will work for you. There is another version by GrinningFerret IIRIC.
There is also a workaround where you edit the ROM zip to bypass error 7, search forum.
Again, no need to revert to stock now. Good luck.
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Reading your first post, it seems that you micros may be bad. Are you using another one or at least tested that one for hardware errors?
---------- Post added at 11:03 PM ---------- Previous post was at 10:51 PM ----------
Actually the other TWRP version was built by SlimShaddy:
TWRP-3.0.2.0-w7-05-04-2016.img | by SlimShady's for Optimus L90
https://www.androidfilehost.com/?fid=24459283995313433
It's in IMG format, so I think you can't flash it directly in TWRP.
lfom said:
Your phone's system partition is empty, that's why it's stuck with LG logo. Simply copy the other (installable) TWRP zip and flash it with current TWRP and it should work. (Reboot afterwards, of course)
I have used the DatkBlue version from the same thread you linked, not sure if it will work for you. There is another version by GrinningFerret IIRIC.
There is also a workaround where you edit the ROM zip to bypass error 7, search forum.
Again, no need to revert to stock now. Good luck.
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Reading your first post, it seems that you micros may be bad. Are you using another one or at least tested that one for hardware errors?
---------- Post added at 11:03 PM ---------- Previous post was at 10:51 PM ----------
Actually the other TWRP version was built by SlimShaddy:
TWRP-3.0.2.0-w7-05-04-2016.img | by SlimShady's for Optimus L90
https://www.androidfilehost.com/?fid=24459283995313433
It's in IMG format, so I think you can't flash it directly in TWRP.
Click to expand...
Click to collapse
I LOVE YOU MAN!! HAHAHAH
You saved me, really lol
Unbriking the phone, disasemble it, etc, is really boring.. lol
My phone is running CM13 right now, thanks man and everyone that helped

Updating BTV-DL09 to new, unapproved, firmware

Hi all!
First a warning: I tell you how what I done, applying this on different model is possible but require some knowledge... don't try if you are not enough experienced.
My BTV-DL09 had a C100B303 firmware (unlocked, rooted with SuperSu 2.82) and I wanted to upgrade to last version, B310, downloaded with Firmware Finder for Huawei.
But this formware is not yet approved for my device! So i searched a way to update the firmware and found HuRUpdater.
Here the step-by-step tutorial:
1) download version B310
2) rename files (required by HuRUpdater):
- update_data_full_public.zip -> update_data_public.zip
- update_full_BTV-DL09_hw_eu.zip -> update_all_hw.zip
3) download HuRUpdater, I used version 0.3 if a new is available read what's changed.
4) (optional) download custom recovery (in this case the Greatslon TWRP for EMUI 5) and rename it "recovery.img"
5) copy all files to SD, in a subfolder (don't use "dload")
6) install, if not already present, the custom recovery
7) boot to the recovery and install "HuRUpdater_0.3.zip"
8) follow on-screen instructions than reboot!
At this point the Mediapad was working BUT
A) without root
B) with a "half" lock: the bootloader says it's unlocked but refused to flash or boot a custom recovery.
Problem B: I had to re-unlock the booloader with command
fastboot oem unlock 12345678901234567980
I accepted that my data will be erased (I have a backup, you too???) and the Mediapad rebooted.
I was lucky because the data was not erased and the bootloader now was fully unlocked. I'm not sure if this works for all of you so backup your data before. (***)
Problem A: not the custom recovery is booting so I flashed Magisk 15.3 (I had this version on other devices and don't wanted to do more testing for that day). It installed correctly, rebooted and
that's all folks!
(***) Here the enlightenment: https://forum.xda-developers.com/showpost.php?p=78194270&postcount=1029 from @zxz0O0
In short: flash also the custom recovery!
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
thew-tab said:
I have a M3 that can only boot up to twrp. I am trying to fix this tablet, since the previous owner accidentally erased the system partition, and it will not load. I did a search using the firmware finder, but wasn't sure I did it right, alot of versions came up. I do not know what software version was on it, before it got messed up. All I know is that it was bought less than two months ago. I was hoping someone could post a direct link to the firmware that I could use to get this tablet up and running again. the original owner lives in the US, as do I. Any help will be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
Hello. I messed up my M3 trying to update and now Bluetooth does not work.
My firmware shows in Settings as "testkeys", so I don't really now what firmware is, probably B302 since security patch is from November 2017.
I am trying to flash full firmware again and do a full wipe. I tried to do it via TWRP and eRecovery too, but both methods fail.
I also tried the method the OP mentioned with no luck either (maybe because mine is the WiFi-only European version).
What should I do? How do I go back to stock? I don't care if I lose my data or if I have to relock bootloader again, I just want my M3 to work properly again!
sergio_sant said:
Hello. I messed up my M3 trying to update
Click to expand...
Click to collapse
Exact model?
Exact firmware that you have?
nicolap8 said:
Exact model?
Exact firmware that you have?
Click to expand...
Click to collapse
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
sergio_sant said:
Model is BTV-W09C100B006 according to oeminfo.img, so I guess firmware must be B006?
In Settings it shows up like the screenshot attached:
Click to expand...
Click to collapse
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
nicolap8 said:
Ahi, ahi... you are unable to discriminate what is the device model (BTV-W09) from the firmware version (BTV-W09C100B006). So you are not enough experienced nor skilled... Search someone that can help you offline!
Click to expand...
Click to collapse
I may be not enough experienced nor skilled but I've been unlocking, rooting and changing roms to my phones since Android 2.1 era, that was many years ago as you know.
I know that the model is BTV-W09, I just said that OEMINFO says BTV-W09C100B006 when searching "btv" with an hex-editor following YOUR instructions from your earlier post.
Anyway, thanks for nothing, I finally found a solution by myself writing the required images one by one trough ADB.
Have a nice day.
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen, and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
nicolap8 said:
First you need to know the exact model. One method can be this:
0) insert an SD card
1) boot the TWRP
2) open the terminal
3) execute the command:
Code:
dd if=/dev/block/bootdevice/by-name/oeminfo of=/external_sd/oeminfo.img
this will copy the OEMINFO partition to the SD card.
4) open the oeminfo.img file with a hex editor and search for "BTV", do not stop to the first occurrence: there are some and you will find the exact firmware code that was installed.
5) search a FULL firmware with FW finder than flash it!
Nicola
Click to expand...
Click to collapse
thew-tab said:
I had to have messed up something quite well, I ran the updater, everything seemed to go fine, but when I rebooted, it wont go off the Huawei MediaPad android screen,
Click to expand...
Click to collapse
Explain better, which screen?
and I can not get it back into TWRP , or get it to do anything else, any help would be greatly appreciated.
Click to expand...
Click to collapse
Reread first post.
It is the initial boot screen
nicolap8 said:
Explain better, which screen?
Reread first post.
Click to expand...
Click to collapse
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Model number is BTV-W09
Do not know the original firmware, but I apparently read the model number wrong when I looked it up. I used BTV-DL09. TWRP said install was a success ( I used the HuRUupdater thru TWRP) The files used was the full OTA , the update_full_BTV-DL09_dialcu_cn.zip, as well as the update_data_full_public.zip. I changed the file name to the names that were needed to run HuRUpdater. So my question is does anyone know how to fix my mistake?
I was able to get it into fastboot mode, but it said the phone was locked, and was not picked up by my computer.
nicolap8 said:
Model?
Firmware previously on tablet?
Firmware that you installed?
Which files you used?
The update procedure was successfully or there was some message?
Click to expand...
Click to collapse
thew-tab said:
Model number is BTV-W09
I used BTV-DL09. TWRP said install was a success
Click to expand...
Click to collapse
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode, the computer does not recognize the tablet? . Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
nicolap8 said:
NEVER install the software for one model on a different hardware. NEVER!
What TWRP says it's not important: it only wrote some files on a disk but it's not of interest what is inside these files.
You have to flash an appropriate firmware, no other options.
Click to expand...
Click to collapse
thew-tab said:
how can I flash the the firmware, if I no longer have TWRP, or when I can get into flashboot mode. Here is a probably stupid question: do I look for BTV-W09, which is the model of MY tablet?
Click to expand...
Click to collapse
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
nicolap8 said:
You have to unpack the firmware and flash the partition images with flashboot.
Search the forum for "Huawei Update Extractor".
Click to expand...
Click to collapse
thew-tab said:
which of these are the partition images? Second stupid question, I tried to get in to fastboot, but the computer would not recognize the tablet
Click to expand...
Click to collapse
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
What about if I can't get the computer to recognize the tablet in fastboot mode?
nicolap8 said:
All of this are partition images!
The problem is that you have to write all relevant partitions that was written from bad firmware!
Often boot.img is enough to have TWRP working.
Click to expand...
Click to collapse
This is the screen I see when I am in flashboot mode
thew-tab said:
What about if I can't get the computer to recognize the tablet in fastboot mode?
Click to expand...
Click to collapse

Categories

Resources