Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,809,495 Members 37,748 Now Online
XDA Developers Android and Mobile Development Forum

[Q] D405n and D405ds IDs mixed

Tip us?
 
lecterek
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Sep 2014
Default [Q] D405n and D405ds IDs mixed

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
Attached Files
File Type: txt getprop.txt - [Click for QR Code] (12.5 KB, 2 views)
File Type: txt build.prop.txt - [Click for QR Code] (6.5 KB, 4 views)
 
shinobisoft
Old
#2  
shinobisoft's Avatar
Recognized Contributor
Thanks Meter 2,087
Posts: 2,263
Join Date: Feb 2012
Location: Knoxville, TN

 
DONATE TO ME
Quote:
Originally Posted by lecterek View Post
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
I'll send @Quarx a link to this thread.

"The way is known to all but not all know it"
My Devices, Mods, ROMs, and Tools
 
Device: LG Optimus L90 LG-D415 ROOTED, Bootloader.UNLOCKED, TWRP 2.7.1.0, Stock KitKat 4.4.2
Device: LG Optimus L9 LG-P769 ROOTED, Bootloader.LOCKED, CWM 6.0.1.2 ( L9RecoveryInstaller ), Stock JellyBean 4.1.2
Device: LG Optimus T LG-P509 ROOTED, Bootloader.UNLOCKED, CWM 5.0.2.7 Touch, CM10
My Stuff
 
SubliemeSiem
Old
(Last edited by SubliemeSiem; 4th September 2014 at 11:40 AM.)
#3  
SubliemeSiem's Avatar
Member
Thanks Meter 31
Posts: 94
Join Date: Dec 2008
Location: Tilburg, NL
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.
Current phone
Model: LG L90 D405n
Recovery: TWRP
Rom: Quarx' CM11

Old phone: Sony Xperia E C1505 (Sold)
Recovery: TWRP and CWM combo
Rom: CM11 (Unstable nightly)

Old tablet: Asus Nexus 7 2013 (Broken)
Recovery: TWRP
Rom: CM11 (Official)

Samsung Galaxy Tab 3 7.0 (Sold)
Recovery: TWRP
Rom: RocketTab
 
lecterek
Old
#4  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Sep 2014
Quote:
Originally Posted by shinobisoft View Post
I'll send @Quarx a link to this thread.
OK, thx. I hope he could provide some suggestions.
 
lecterek
Old
(Last edited by lecterek; 4th September 2014 at 07:53 PM.)
#5  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Sep 2014
Quote:
Originally Posted by SubliemeSiem View Post
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.
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.
 
SubliemeSiem
Old
#6  
SubliemeSiem's Avatar
Member
Thanks Meter 31
Posts: 94
Join Date: Dec 2008
Location: Tilburg, NL
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.
Current phone
Model: LG L90 D405n
Recovery: TWRP
Rom: Quarx' CM11

Old phone: Sony Xperia E C1505 (Sold)
Recovery: TWRP and CWM combo
Rom: CM11 (Unstable nightly)

Old tablet: Asus Nexus 7 2013 (Broken)
Recovery: TWRP
Rom: CM11 (Official)

Samsung Galaxy Tab 3 7.0 (Sold)
Recovery: TWRP
Rom: RocketTab
 
lecterek
Old
#7  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Sep 2014
Quote:
Originally Posted by SubliemeSiem View Post
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.
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.
 
SubliemeSiem
Old
#8  
SubliemeSiem's Avatar
Member
Thanks Meter 31
Posts: 94
Join Date: Dec 2008
Location: Tilburg, NL
Quote:
Originally Posted by lecterek View Post
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.
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.
Current phone
Model: LG L90 D405n
Recovery: TWRP
Rom: Quarx' CM11

Old phone: Sony Xperia E C1505 (Sold)
Recovery: TWRP and CWM combo
Rom: CM11 (Unstable nightly)

Old tablet: Asus Nexus 7 2013 (Broken)
Recovery: TWRP
Rom: CM11 (Official)

Samsung Galaxy Tab 3 7.0 (Sold)
Recovery: TWRP
Rom: RocketTab

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Flyme OS Finds Its Way to the Google Nexus 5

Flyme OS is a heavily modified Android variantdeveloped by the Meizu team for their MX … more

MultiROM Makes Its Way to the LG G2

Over the last few weeks, we’ve seen quite a fewflagship (and former flagship) devicesget to … more

Jair Player with a Major Update–Here’s What’s New!

Back in May, we talked a bit aboutJair Player, a nice looking music … more