Database Develop

1-ckick rooting for Google G1 / G2

Hey all!
i have some questions to this app:
http://www.cyrket.com/package/org.zenthought.flashrec
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
1. does it works on T-Mobile D G1 with any FW? or also only with RC29 or RC7?
2. is flashing "HardSPL" or "DangerSPL" a musthave or can i use the original SPL (iam scarry to flah SPL)?
3. when i restore the backup do i have the full original t-mobile D delivery version of my G1?
4. how i restore the original recovery.img
5. if needed, how do i restore the original SPL
6. do i need to flash the Radio manual or do the apk make this
7. is this the right order?
- download apk
- install apk
- download CyanogenMod v4.0.1
- save as update.zip on SD root
- execute apk
- create backup
- flash Cyanogen recovery 1.4
- reboot into the new
- flash CyanogenMod v4.0.1
- Wipe
- boot G1
- download new Radio
- copy Radio as Radio.zip to SD root
- update Radio via Cyanogen recovery 1.4
- done
- boot G1 (now i have a rooted G1 with CyanogenMod v4.0.1)
please correct me if the is anything wrong or if i missed any step!!
iam "noob" with android - but i hope not for a long time

As a N00b you should at least read the Sticky posts, like http://forum.xda-developers.com/showthread.php?t=528334 this one...
It's called:
"Don't Start A New Thread - Dream Questions & Answers Here!"

All questions should be posted in the Q&A Section. I'm not too familiar with the 1-click rooting since it's been out for less than 72hrs so from what I've heard the 1-click root flashes cyan's recovery for you so all you have to do is this:
-Download and flash newest radio
-Download and flash Hard SPL
-Wipe
-Download and flash CM v4.0.1
If you do it in this order I'm 99.99999% sure you won't brick your phone, but once again please post all future question in the Q&A section

dubbeld00 said:
As a N00b you should at least read the Sticky posts, like http://forum.xda-developers.com/showthread.php?t=528334 this one...
It's called:
"Don't Start A New Thread - Dream Questions & Answers Here!"
Click to expand...
Click to collapse
if to correct me, iam not a totaly noob - iam only noob in flashing android i allready flashed two HTC Wizard to a german Windows 6.5 Beta 2 and they works perfectly only a bit slower as with mobile 5.0

bluedragon1982 said:
Hey all!
i have some questions to this app:
http://www.cyrket.com/package/org.zenthought.flashrec
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
1. does it works on T-Mobile D G1 with any FW? or also only with RC29 or RC7?
2. is flashing "HardSPL" or "DangerSPL" a musthave or can i use the original SPL (iam scarry to flah SPL)?
3. when i restore the backup do i have the full original t-mobile D delivery version of my G1?
4. how i restore the original recovery.img
5. if needed, how do i restore the original SPL
6. do i need to flash the Radio manual or do the apk make this
7. is this the right order?
- download apk
- install apk
- download CyanogenMod v4.0.1
- save as update.zip on SD root
- execute apk
- create backup
- flash Cyanogen recovery 1.4
- reboot into the new
- flash CyanogenMod v4.0.1
- Wipe
- boot G1
- download new Radio
- copy Radio as Radio.zip to SD root
- update Radio via Cyanogen recovery 1.4
- done
- boot G1 (now i have a rooted G1 with CyanogenMod v4.0.1)
please correct me if the is anything wrong or if i missed any step!!
iam "noob" with android - but i hope not for a long time
Click to expand...
Click to collapse
Yes, this app worked perfectly for me ( cuz I dun wanna waste my time doing all the porcess of pulling the firmware back to RC29 ). If u have the latest radio, then just execute the .apk, turn off your phone right after doing all the required process from that app ( back up current img then Flash the 1.4 img from Cyanogen I remember ), then go into recovery mode and you have the newest recovery img. (Remember to put the CyanogenModv4.0.1 to your SD first). Then Wipe and Flash the update, and you're done

and it works without flashing SPL????

bluedragon1982 said:
and it works without flashing SPL????
Click to expand...
Click to collapse
ARE you NOT getting IT ..........
YOU need TO ask YOUR questions IN the Q&A section....
THIS is THE development SECTION

dan0zone said:
ARE you NOT getting IT ..........
YOU need TO ask YOUR questions IN the Q&A section....
THIS is THE development SECTION
Click to expand...
Click to collapse
thx for moving
now the next ry to get good anwsers and not so stupid answers like the one form dan0zone

hard spl will not brick your phone. it is needed to flash roms from other regions than yours. hard spl is a good thing to have. also with it you can flash nandroid back ups and you can change your splash screen to further personalize your dream. enough said... go download it. flash it. if you have to wipe, then wipe. if you don't like wiping then you should not have rooted in the first place.

but to use this tool have id need to flash the SPL or works it with the original SPL too? in the manual and one the youtube video- there is no info about a need to flash the SPL.
all i want to know is:
can i just install this app, flash the new radio, run the backup, flash recovery, flash CFW, and iam done or not

yes you can do that. afterwards i would recommend flashing the hard spl.
you do not have to flash it, but it would be a good thing.

david1171 said:
yes you can do that. afterwards i would recommend flashing the hard spl.
you do not have to flash it, but it would be a good thing.
Click to expand...
Click to collapse
thanks, should i flash the radio befor i try to root my G1 with the 1-click rooting? or after i flashed the custom FW?

I used the "1-click root"
I followed all the steps and my phone is working fine, but how can you tell if its rooted?
Also, if it is rooted and I wanted to install the most current cyanogen ROM, do I have to install the new radio and SPL files?
Thanks in adv for putting up with my N00Bness.

what build do you have now? rc33? i would first update the radio. i would not mess with the newer spl as it has been known to brick phones. also did you install cynogen's recovery image? turn phone off then hold power button and home key when you turn it on to put you back into recovery image. it should say cynogen recovery 1.4 on top. it will have a number of options on the bottom nandroid backup, restore nandroid etc. if that cynogen"s recovery image is on the phone its rooted. after you flash the latest radio, i would flash jf 1.51 build then cynogens latest build. i heard the going to cynogens latest build will cause a bootloop if your not coming from another modded build.

kaws666 said:
I followed all the steps and my phone is working fine, but how can you tell if its rooted?
Also, if it is rooted and I wanted to install the most current cyanogen ROM, do I have to install the new radio and SPL files?
Thanks in adv for putting up with my N00Bness.
Click to expand...
Click to collapse
To tell if the phone is rooted, download terminal emulator from the market and type su at the prompt. If the phone is rooted, the prompt should go from a $ to a #. If not, you will get a permission denied error message. If that is the case, probably go the old fashion way of rooting
http://forum.xda-developers.com/showthread.php?t=548924
As far as the SPL and radio, you don't need the danger SPL (haykuro's) but you will need to engineering SPL or hard SPL to install custom ROMs. As far as the radio, you want to latest radio to improve calls, bluetooth, etc.

hi im also new..
i did the 1 click root too. i did the back up, then flashed the 1.4. then the nandroid backup, then wiped the data, then flashed cyanogens 4.0.1. so im pretty sure im rooted.. and everything works too! except myfaves and the native im app.
but whats this about the radio? do i have to update that? i havent messed with the radio at all.. what are the dangers in this? if any?
and i haave no clue what the hell spl is lol

roadrunnerx7 said:
hi im also new..
i did the 1 click root too. i did the back up, then flashed the 1.4. then the nandroid backup, then wiped the data, then flashed cyanogens 4.0.1. so im pretty sure im rooted.. and everything works too! except myfaves and the native im app.
but whats this about the radio? do i have to update that? i havent messed with the radio at all.. what are the dangers in this? if any?
and i haave no clue what the hell spl is lol
Click to expand...
Click to collapse
SPL info:
http://forum.xda-developers.com/showthread.php?t=455860
Radio info:
image file for controlling wireless/radio signal, runs at layer underneath android
Source: http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_overview_and_useful_information
Please guys, try to use the search function...pretty please.

definetly flash the radio, it made my speaker a lot louder!

My current build never changed. Its still CRC1 :/
I just tried the terminal emulator command and typed su and it said permission denied :/
What SPL and radio should I flash after I root of course?

DirectMatrix said:
SPL info:
http://forum.xda-developers.com/showthread.php?t=455860
Radio info:
image file for controlling wireless/radio signal, runs at layer underneath android
Source: http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_overview_and_useful_information
Please guys, try to use the search function...pretty please.
Click to expand...
Click to collapse
thank you!

[ROM][CWM] Honeycomb 3.1 - Touchwiz UX - WIFI - DEODEXED (Updated 7/22/2011)

Pretty basic release. This is a deodexed version of the touchwiz wifi update.zip available in this thread: http://forum.xda-developers.com/showthread.php?t=1167250
I have not changed anything else in this ROM (though I am now working on a more streamlined touchwiz ROM using this deodexed version)
So no, this ROM is not meant to improve performance or fix any bugs from the stock touchwiz update. A deodexed ROM simply makes it possible/easier for devs to create patches that can address these issues, make themes, etc.
Warning: I am not responsibile for any damage you do to your device from flashing this update. Please be careful and follow the instructions below, and use at your own risk!
md5: 5a6a04a24f7f799b1b122d9e445110b2
Uploaded 7/22/2011: http://www.multiupload.com/WTU98VP2D5
-Fixed WiFi issue (thanks to DocRambone for the fix)
-Fixed /system not being wiped properly during update
Installing:
Download and place somewhere on your /sdcard directory
Boot into CWM
Wipe Dalvik Cache
Wipe /data and /cache (you can skip this if you had flashed the r4-7/19/2011 previously)
Install this zip from sdcard
---
Rooting:
Flash su_busybox_misc-sam_tab_10.1-051511.zip using CWM / Rom Manager: http://droidbasement.com/galaxy/tools/su_busybox_misc-sam_tab_10.1-051511.zip
---
Before reporting any bugs please make sure you have followed these directions. If you are getting a boot loop you most likely missed one of the steps above.
If you are getting the "service temporarily unavailable message" you need to sign into your google account, it should go away after you do that
Have fun themeing and modding!
~Shev
Thanks to:
pershoot - for the update.zip and the rooting zip
mughalgxt - for finding and sharing the stock touchwiz update

Does this mean i am the first...
To try this.....HMMMMM - let me sleep over it.
Oh - what the heck!

is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!

Interesting....very interesting. Might have to give this a look-see...

rvrugg90 said:
is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!
Click to expand...
Click to collapse
No, this update will make it possible to create and use modified versions of the apps + framework resources contained within the touchwiz ROM (i.e create themes, etc)

Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?

Nice work here.

xSunny said:
Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?
Click to expand...
Click to collapse
Are you talking about the special tilt / pan control? Just tested that, still doesnt work, but it may be possible now to patch the problem if someone can find it (in the deodexed resources).

Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom

Yeah i still didnt go back to stock 3g im just hoping somebody can find it in this deoxed rom but lets see

Can you pleaseeeee hook me up with the 3g touchwiz .zip??? IV looked everywhere! My tab is sooo slow with the wifi version but the 3g version, even with errors, was smoking fast! Thanks!
je2345 said:
Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom
Click to expand...
Click to collapse
Sent from the best phone on the planet (SGS2) running the best ROM on the planet (Cognition S2)!

Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz

roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
I don't think it really matters when you flash root bro. Make sure you are using pershoots tools pack though.

roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
The linked root zip is optional, you don't have to flash right after, you can flash it whenever (but dont use any of the other rooting zips available for this tab, the linked one is the only compatible version). Your bootloop is probably caused by not wiping /data+/cache or the davlik cache. Follow the instructions in first post.

daddymatt said:
Can you pleaseeeee hook me up with the 3g touchwiz .zip???
Click to expand...
Click to collapse
Enjoy.
http://www.megaupload.com/?d=XBAH8X7P

Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...

nakedninja42 said:
Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...
Click to expand...
Click to collapse
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.

are you sure thats the 3G version? I went to download it and my pc sees it as exactly the same as the new wifi version... thank you sooo much for it either way! good looking out!!!

SellswordShev said:
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.
Click to expand...
Click to collapse
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?

nakedninja42 said:
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?
Click to expand...
Click to collapse
No if its not working in CWM it wont work if you do it through ROM manager. Redownload and verify the md5 hash from the original post. Boot into CWM recovery, wipe everything mentioned and retry.

My new LGOS (RIL?)

Hello - I tried to search but couldn't really find answers
I got my LGOS some days ago from Ebay.
He used Cyanogenmod but reverted it back to the Stock image "over the settings menu" - whatever that means.
It was still rooted (he said he did it with Gingerbreak) and had Superuser installed. Clockworkmemory is installed, too (I updated it to a newer version with ROMManager now).
It has the 10c firmware - that means unbranded if I understand that right.
I downloaded both RIL tools to figure out which RIL I have - but unfortunately they won't show me my RIL version
"Unknown RIL file found"
Baseband is 1035.21_20110405
Could somebody help me - what should I do next with my device? I think I want to stick with stock for now. Should I do a full revert with NVFlash? Or can I just use it? For the last 2 days I had no crash - it seems to work fine.
I owned a ZTE Blade before and did a lot of flashing (CM7 mostly). Just want to say that I am no total noob - but I am a bit confused with my new smartphone now
Thanks in advance

If it's working and you're happy with it, then don't worry about it.

Hehe thanks - and sorry for not making myself clear enough.
I want to stick with stock because it seems everything is working here. Maybe "stick" isn't the best word - "keep" would be better. I thought of a nandroid backup and then to try out CM7
It bothers me a little that no RIL version is shown - this works normally, doesn't it?

It works by comparing the MD5 of your lge-ril.so file against a list of known ones.
Whatever you have just hasn't been entered into it's database.

Rusty! said:
It works by comparing the MD5 of your lge-ril.so file against a list of known ones.
Whatever you have just hasn't been entered into it's database.
Click to expand...
Click to collapse
How can I do that?

tonydl said:
How can I do that?
Click to expand...
Click to collapse
You should mail to [email protected], the dev of LG GetRIL and see that with him.
Sent from my Optimus 2X using XDA App

Striatum_bdr said:
You should mail to sibbor, the dev of LG GetRIL and see that with him.
Click to expand...
Click to collapse
Agreed, send me an e-mail

Okay, I sent you the email. Thanks
I am still a bit unsure about the way the pre-owner restored the ROM and rooted it.
First - does this apply to the LG 2x, too?
http://forum.xda-developers.com/showthread.php?t=1108201
It is strongly recommended that you flash clockwork recovery via NVFlash. If for some reason this or a future nightly build causes your phone to not boot up, you will not be able to boot into recovery unless you have it flashed via NVFlash.
To clear up some confusion, if you flashed your recovery via ROM Manager, you didn't actually flash a recovery. It is what we call a fakeflash, you should still probably flash with NVFlash.
Click to expand...
Click to collapse
Second: Is it correct how he restored the stock rom? He went to "Settings - Privacy - factory data reset" - but had installed CM7 before.

No it doesn't apply to the O2X, ROM Manager flashes properly.
If he did a factory reset, then it's not on stock ROM, just a blank CM7.

Rusty! said:
No it doesn't apply to the O2X, ROM Manager flashes properly.
If he did a factory reset, then it's not on stock ROM, just a blank CM7.
Click to expand...
Click to collapse
I mailed him again - now he clarified it
He reinstalled the ROM with NVFlash a while before he was on CM7 and then deleted all his data via the menu. This explains some remaining stuff & pictures on the internal SD card hehe.
Then it is okay - I just wanted to make sure that he did everything "correctly".
Thank you very mich Rusty for your patience with my noob questions

I had a similar problem when I Installed a 622 baseband, then stock froyo, then cyanogen.
Then I guess I installed the 622 RIL from GB instead of the froyo one and the result was an unknown baseband (in LG GetRIL app), locked sim and no phone network.
Going back to the froyo 622 RIL solved everything.

[Q] [S.O.S.] A rare MILESTONE brick situation!

Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.

some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...

Sir, I have tried so, somehow, I did not have lucks other had.

roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.

..... my bad

I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me

skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.

By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.

So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?

zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.

Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet

zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.

same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App

guys same problem here, help us

[Q] (Q) Problem with Carbon and Mahdi Rom

I 've tried both roms (clean install) but only the front camera is working (model d405n)
I 've tried with CWM and TWR but with the same result.
Is there any fix for that?

No idea... Have you done a full wipe?
(If you realy want, you can restore everything with kdz en start all over again?)

We have one guy on polish forum with the same issue. Strange thing, as if there is more than one d405 variant.

Yes i did a full wipe.
I restore with kdz, root again, full wipe, install rom, and the problem still exist

is there any kernel i can use?

I use the latest CarbonROM (CARBON-KK-UNOFFICIAL-20141004-1556) for my D405n and front camera works. Are you sure you flashed the correct bootloader image (boot.img)?

i can not find a link for that build. Can you please post a link here?

I use this boot
L90_D405n_v10b_aboot.zip
from
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690

giannis_25 said:
I use this boot
L90_D405n_v10b_aboot.zip
from
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
Click to expand...
Click to collapse
I haven't seen anybody got fix for that yet and it may me a little problem since most users don't experience this bug whilist having the same phone version. Maybe some dev might look into it and tell you at least what it is caused by