Related
hi,
here a kernel, which we want to commit to kernel "msm-linux"
(the kernel should be for: raphael, diamond, blackstone, topaz, rhodium, kovsky) booting via haret
all credits to crazyvirus, alex, acl, jonpry, phh, oliwe, etc ...
BE CAREFUL ! best would be -> make backup before, beucase there a lotof changes and i tested only the blackstone !
changes overview:
1.) new battery algo for better display the VOLUME (for now blackstone is ajusted, the other devices battery devices could be, that we must do finetuning
2.) new USB driver (working also if not connected on boot)
3.) AC / USB charger detection
4.) reboot/shutdown should now work for devices (maybe it reboots - not only shutdown, must do testing on it for diff devices)
TESTING:
please test this kernel:
1.) battery - specially we need testing on battery -> please add the logging data from kernel... -> via kernel logging -> cat /proc/kmsg | grep battlog)
2.) USB
.) connecting USB after rebooting, then try to connect via win adb or linux
.) test mass data storage
.) DON'T click/test wlan hotspot !!! it could be, that you have problems after using it !
3.) AC / USB charger -> change the adapter and look on battery information if it will be changed correct.
4.) reboot/shutdown should now work for devices (maybe it reboots - not only shutdown, must do testing on it for diff devices)
please help on testing, because we want soon to commit this changes.
cu camel
PLS: as you know, this kernel is for multiple sys please add always:
Device: ??
Battery Type: Original or ????
Battery Volume: ???? mAh
############################
attached a new kernel V8
.) try now to fix the boot for kovsky (device think the batt is 70° hot ...)
.) cleanups for battery driver things
.) logging is now different
.) there is a new log option (only in startup.txt boot option like
+ htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
+ htc_battery_smem.fake=1 ( 0 | 1 ) via bit (0 = OFF / 1=ON) (would fake to system, that it is always on USB charger)
+ htc_battery_smem.vol_min=5 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)
here an example of my startup boot option line:
set cmdline "gsensor_axis=-2,-1,3 lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off acpuclock.oc_freq_khz=575000 msmsdcc_fmax=32000000 htc_battery_smem.debug=7 rel_path=AndroidBoot"
EDIT9: kernel v9
.) fixing high temperature on kovsky & rhod (which does on startup autoamtically a shutdown, because android system is thinking the batt is too hot.
:> i made a mistake, which should be now correct. if it would be too hot (> 50°), then i set the temp to 499 = 49,9° -> so watch out if there is a value of 499 on temp
EDIT10: kernel_v10
.) now battery data for blackstone should be fine. (current + volatage, + % + 93% to 100%
.) kovsky adjustment for voltage, temp + current should be now better ...
EDIT11: kernel_v11
.) now battery data for raph should be fine. (current + volatage, + % + 93% to 100%)
EDIT12: kernel_v12
some device had problems with wrong values from battery driver, and then device shutdown by itself ..
-> should be fixed now
EDIT13: kernel_13
sorry, the kernel v12 was very bad, a lot of mistakes ..sorry
.) fixed a lot of things in alog, specially if charging, had wrong values, also fix temperature values, etc...
.) adjusted raph100 (hwboard_id=1)
fixed some errors on wrong values which shutdown the whole system
EDIT14: kernel v14
.) fixed some problems with charger devices
.) added corr for AC adapter if current is higher
.) adjust a lot of things on algo
EDIT15: kernel v15
.) made a stupid bug in autocorrection function (temp was never corrected), so the device shutdown the device if wrong values ..is fixed now
EDIT16: kernel v16
.) add addionally debug prints for kovsky (because no battery init)
.) diamond100-900 adjustments - for diamond100-900 we need a FINAL LONG TEST - see posting #2
EDIT17: kernel v17
.) added support for topa??-1100 vendor=2
.) removed extra debugging prints for kovsky
EDIT18: kernel v18
.) added support for kovsky, new rhod type
.) extreme values checking
.) adjustments for rhod + kovsky current, temp, etc..
.) extra recheck for INCALL
.) rhod: set POWER to HOME KEY (only for rhod)
EDIT19: kernel v19
.) try to write the temperature only once, if value is ok, so the auto shutdown shouldn't happen any more.)
.) adjustment for kovsky device
.) some other small fixes
EDIT 20: kernel v20 (battery driver on chip 2746 - experimental)
.) there is a new log option (only in startup.txt) boot option like
+ htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
+ htc_battery_smem.fake=0 ( 0 | 1 )
+ htc_battery_smem.vol_min=0 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)
+ htc_battery_smem.vol_max=100 ( integer value which will be the maximum value) if it is > then it will correct the volume to this value, so the battery won'T be charged by kernel, and the battery can switch off the charging by itself
.) adjustment on current + voltage for kovsky
.) alex patches: clock wince + kovsky battery support via ds2746 (no idea how it works - short test before a long time test makes sense and would be welcome
EDIT21: kernel v21
.) support for rhod300
.) changed back to calc the kovsky from kernel on normal way
.) removed the wince clock path from Alex (because users reported problems with flickering)
x.....OK
o.....IMPLEMENTED - FINAL TEST IS MISSING
t.....TESTING
n.....not supported
b.....buggy, not working
?.....no info about ..
Code:
BATTERY TYPES__:raph100-1340|raph100-1340|raph300-????|raph500-????|raph800-????|diam100-????|diam500-????|blstone-1350|topa100-1100|topa100-1100|rhod100-????|rhod210-????|rhod300-1500|rhod400-????|rhod500-????|kovsky1-????|
ExTRAINFO______:hwboardid=0_|hwboardid=1_| | | | | | |vendor1 |vendor2 | | |vref=1254 | | | |
---------------:------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|
boot procedure_:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______x_____|______?_____|______?_____|______x_____|
InCall Mic_____:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
InCall Earpice_:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
USB Gadget_____:______?_____|______x_____|______?_____|______?_____|______?_____|______x_____|______?_____|______x_____|______?_____|______?_____|______?_____|______?_____|______x_____|______?_____|______?_____|______?_____|
USB Mass Storag:______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|______n_____|
temperature____:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______b_____|______b_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
voltage________:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
current on AC__:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
current on USB_:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
current on batt:______?_____|______o_____|______?_____|______?_____|______?_____|______t_____|______?_____|______o_____|______t_____|______t_____|______?_____|______?_____|______o_____|______?_____|______?_____|______t_____|
(updated -> 20.10.2010 10:59 GMT+2)
we need for every battery type and device a detail log, so that i can adjust the battery parameter
if you also want that your phone shows the real % volume, then you must log as described..if not -> your own fault
how to log:
at first you must activate logging:
short test:
========
1.) boot
2.) activate logging via:
dmesg >> /sdcard/kovskylog.txt
cat /proc/kmsg >> /sdcard/kovskylog.txt
preconditions: best would be if the phone is 10% -90% (not on 100% !!)
then do:
~2min charging via AC
~2min on battery
~2min charging via USB
################################################## ##
then send me this log file, then i can adjust the basisc...
################################################## ##
after that we can do the long time test:
################################################## ##
long time test: (needs ~10hrs)
(preconditions: best would be if the phone is 0% - 50%)
========
1.) boot
(for this test -> before booting to android -> you should add to startup.txt)
htc_battery_smem.debug=7
htc_battery_smem.vol_min=15
htc_battery_smem.vol_max=90
2.) activate logging via:
dmesg >> /sdcard/kovskylog.txt
cat /proc/kmsg >> /sdcard/devicename_log.txt
then do:
~30min charging via USB
~3min on battery
~3-4hrs charging via AC
after that prepare your device:
-> flight mode ON
-> SYNC data - OFF
-> 3G -> OFF
-> screen always ON
-> screen ~50% brightning
plug out the cable and let device run out of battery
(needs ~6hrs)
then send me the log
################################################## ##
.) there is a new log option (only in startup.txt) boot option like
+ htc_battery_smem.debug=7 ( 0 | 1 | 2 | 4 ) via bit (so 7=all)
+ htc_battery_smem.fake=0 ( 0 | 1 )
+ htc_battery_smem.vol_min=0 ( integer value which will be the minimum value) if it is < then it will correct the volume to this value, so the battery can also run out (if wanted)
here an example of my startup boot option line:
set cmdline "gsensor_axis=-2,-1,3 lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off acpuclock.oc_freq_khz=575000 msmsdcc_fmax=32000000 htc_battery_smem.debug=7 rel_path=AndroidBoot"
1.) full charging of your phone, -> please to be sure, that it is really full -> charge it ~3hrs via AC adapter.
2.) kill all applications
3.) open terminal emulator:
-> then input: su
-> then input: cat /proc/kmsg | grep BATTLOG >> /sdcard/batterylog.txt
or if you want full logging -> then input: cat /proc/kmsg | grep BATT >> /sdcard/batterylog.txt
(for me it is very simple to grep my data for algo fine tuning
4.) switch to AIRPLANE mode
5.) set your device to: SCREEN ALWAYS ON (there are several tools on the market wher you can do that, 30 is not enough
6.) SET DISPLAY BRIGHTNESS to 50%
then plugout the AC Adapter - and let the phone run out o battery (mostly 5-8hrs)
after that please post the log data. which can be found in sdcard -> (called) -> batterylog.txt
PLS: special apps on market
for "STAY ALWAYS ON" -> you can use: "caffein" (from Syntaxa)
for disable "UNLOCK SLIDE SCREEN" -> you can use: or "screemodewidget"
or also "extended control" but cost some bucks ..
wow these changes sound so promising. downloading and soon to be testing. gettting ever so closer to have a fully functional android. =D
keep up the good work devs
Device: Blackstone
Battery Type: Original
Battery Volume: ?
Detects usb conection, but can't use as usb storage...
Detects if is usb or ac charge...
mic, not perfect, have to pull volume down to activate.
i will do more tests
Sorry, my english... portuguese... to english....
change to english or not... nothing change, only japonese keybord
1.) It says permission denied, what I'm doing wrong?
2.) USB connection is detected, but no mass storage detection
3.) AC / USB charger seems to be correct
4.) (only) reboot works
Device: Blackstone
Battery Type: Original
Battery Volume: 1350 mAh ???
Additional: no mic without pressing volume +/-,no speaker on incoming calls (also after pressing +/-)
Blackstone
Original battery
Wifi not working
Incoming call mic only works after you press volume down
ac and usb charging detected properly.
switch from ac - usb - detects usb
switch usb - ac (with a delay after the battery info says unplugged) - detect.
switch usb - ac (quickly) - doesnt detect.
shutdown button reboots the phone to windows.
USB detected on PC.
USB mass storage didn't work.
Teethering detects USB as connected.
Turn on wifi - gets error with this image. with the 17 th build image it works.
Mic is mutted on receving call. We may need some state machine tweks to get it done.(guess)
Any one facing issue with re detecting signal once it is lost?
Enable GPS - battery level suddenly goes down. Disable GPS it comes back. Is it expected.
Device: Blackstone
Battery Type: Original
Battery Volume: 1350 mAh
May sound weird but where to copy these files to test them..I'm a rookie at android..
joveen said:
with the 17 th image it works.
Click to expand...
Click to collapse
Where can I find this file?
battery seems to be almost... fixed... i boot my phone and he says battery volume 42, 8 hours later... i have 14 of volume battery, no wifi, no calls, standby 8 hours with half battery...
in win mobile he says 20%, in android he says volume battery 14, nothing like before.
hi camro ,
i have a blackstone ,with stock ROM 6.1.........
overall FroYo 2.2 with your updated kernel , is running quite smoothly this morning.( lets hope it stays that way!! )
previously ( few days back ,till yesterday) had sound problems ,but change ...cmd line, accordingly to your suggestion , in you "fix for battery "thread (your post 89 )...yesteday morning and sound had been stable ever since.!
i have wifi , no problem.
battery is much better with your fix ....thank you
shutdown ..button ..
reboots the phone..(which is perfect for me )..better than switch off (,as i can get into windows... without taking cover off.. etc.etc..reset button.. )
plse, keep it like that !!!.. ?
but.....
i must add...
that yesterday before i made the relevant kernel changes i also notice
android battling with redetecting signal ..( i have good reception ..3g and gsm in my area..) as joveen in post 8, states "issue with re detecting signal once it is lost?) and after i replaced it with your updated kernels i still had these issues.
i tried replacing ,all old kernels etc etc ..no luck
( so i am convince the updated kernels... dont play a part in it..!!.. ?? )
but ..(and thats, the point i want to make...)
... i noticed every time ,
android... battled to "redetect signal " ..i had "deep sleep issues...???
and if i had constant signal ..i had nothing ..!!!android woke up every time
( just thought i will add it )
thank you.............. camro, alex, acl, jonpry, phh, oliwe..!!!!
good luck
willcor
Regarding redetecting signal -
I tried at a place where the signal levels is not that good.
the battery doesnt seems to be consumed !! .. I doubt if the android is trying to detect the signal. If it had tried the battery consumption would have increased. (Not sure if this is valid.. It is just a guess from my side).
dizzyman said:
battery seems to be almost... fixed... i boot my phone and he says battery volume 42, 8 hours later... i have 14 of volume battery, no wifi, no calls, standby 8 hours with half battery...
in win mobile he says 20%, in android he says volume battery 14, nothing like before.
Click to expand...
Click to collapse
normal, WM is not a hint for correct %vol.
@USER which are testing dlackstone: !!
if you have don't have a blackstone device, then i would need a log from real 100% to 0% - best would be, if you can hold the current stable (like: diplay always on, all other apps closed and sync deactivated), then do logging as it is describe on #1 posting.
joveen said:
Regarding redetecting signal -
I tried at a place where the signal levels is not that good.
the battery doesnt seems to be consumed !! .. I doubt if the android is trying to detect the signal. If it had tried the battery consumption would have increased. (Not sure if this is valid.. It is just a guess from my side).
Click to expand...
Click to collapse
at first, thanks, your previous feedback was great, will try to take a look on different minutes ...
for your last feedback:
redetecting ? what do you mean ? usb or battery ?
please can you explain that more in detail ?
for usb mass storage -> maybe this you must activated somewhere in the phone, for USB, there must be 3 diff models of using... (tethering, usb mass storage, usb debugging, etc..) - but haven't found this - not yet tested
willcor said:
hi camro ,
i have a blackstone ,with stock ROM 6.1.........
overall FroYo 2.2 with your updated kernel , is running quite smoothly this morning.( lets hope it stays that way!! )
previously ( few days back ,till yesterday) had sound problems ,but change ...cmd line, accordingly to your suggestion , in you "fix for battery "thread (your post 89 )...yesteday morning and sound had been stable ever since.!
i have wifi , no problem.
battery is much better with your fix ....thank you
shutdown ..button ..
reboots the phone..(which is perfect for me )..better than switch off (,as i can get into windows... without taking cover off.. etc.etc..reset button.. )
plse, keep it like that !!!.. ?
but.....
i must add...
that yesterday before i made the relevant kernel changes i also notice
android battling with redetecting signal ..( i have good reception ..3g and gsm in my area..) as joveen in post 8, states "issue with re detecting signal once it is lost?) and after i replaced it with your updated kernels i still had these issues.
i tried replacing ,all old kernels etc etc ..no luck
( so i am convince the updated kernels... dont play a part in it..!!.. ?? )
but ..(and thats, the point i want to make...)
... i noticed every time ,
android... battled to "redetect signal " ..i had "deep sleep issues...???
and if i had constant signal ..i had nothing ..!!!android woke up every time
( just thought i will add it )
thank you.............. camro, alex, acl, jonpry, phh, oliwe..!!!!
good luck
willcor
Click to expand...
Click to collapse
thanks for report,
redetection signal on data connection (3g, 3g, e,) - i'm wondering about, normally nothing changed for this part in kernel.
but if see something in the log.
if you can reeproduce this problem, then make catlog + dmesg, maybe we can find the problem. i never seen such problem on my device ...
have you played with the tethering ?
because since i tried it to activate, i can't disable the tethering/hotspot - maybe this is the problem ..
i must backup + delete my data again and then try it again - without tethering or hotspot .
Hi Camro,
I meant "Redetecting the 3g/2g signals once it is lost".
In a place with low signal, the battery should be consumed more. I am not seeing that with my black stone.baterry almost remains same. Seems like android is not trying to redetect the signals once it is lost. Is there some logs/kernal message to see if it is searching for signals.
Where can I find a file image where features wifi, thanks
DON'T click/test wlan hotspot !!! it could be, that you have problems after using it !
joveen said:
Hi Camro,
I meant "Redetecting the 3g/2g signals once it is lost".
In a place with low signal, the battery should be consumed more. I am not seeing that with my black stone.baterry almost remains same. Seems like android is not trying to redetect the signals once it is lost. Is there some logs/kernal message to see if it is searching for signals.
Click to expand...
Click to collapse
catlog -> grep for "ConnectivityService", there you'll should a part of it ....
fori played with hotspot, and i can'T disable it -since now always "ConnectivityService" will try to set some part for wlan hotspot... must remove my data and install my apps again ..
Thanks to denominator77 we now know how to recmod some modules
denominator77 said:
1. FixRecMod.exe your_dll_folder
2. LordPE -> PE Editor -> choose the recmoded dll -> get ImageBase value -> add the value to BaseOfCode and BaseOfData -> Save&OK
Sometimes ImageBase is not properly restored by FixRecMod.exe. If IDA has not identified any imported function, then try the following steps to fix the addresses:
1. Go to .pdata segment
2. There will be a list of "Function start" and "Function end" definitions
3. Take the first "DCD 0xNNNNZZZZ ; Function start"
4. In the most cases ImageBase will be 0xNNNN0000
5. Run LordPE and update ImageBase, BaseOfCode, and BaseOfData
download to fixrecmod
View attachment 487836
Click to expand...
Click to collapse
Link to LordPE
http://www.woodmann.com/collaborative/tools/index.php/LordPE
to get you all starting I did some modules .
http://dl.dropbox.com/u/5011238/Data/SecurityCore.7z
http://dl.dropbox.com/u/5011238/Data/MSXIPKERNEL.7z
http://dl.dropbox.com/u/5011238/Data/Phone.7z
http://dl.dropbox.com/u/5011238/Data/Start.7z
http://dl.dropbox.com/u/5011238/Data/APPPLATFORM.7z
if a file isn't working then use the above steps (quoted)
edit: updated the DL links.
I'm sorry to bumb such an old thread, but please could you try recmodding the SystemInfo exes and dlls from the ShellDogfood package? They are really old, but there is a possibility that they could run on current version of WP. And if they don't run, is there a way to debug them?
Test made on Omnia 7 EU
Lurking around on my webserver inside wp7 (onmia 7 EU), trying to call them with a tool found here http://forum.xda-developers.com/showpost.php?p=9276473&postcount=91
those below are direct exe's on the HDD (that actualy did something worthy)
\windows\uif.exe >> feedback (hidden)
\windows\LTKeypad.exe >> physical buttons test
\windows\LoopbackTest.exe >> physical test of sound
\windows\Cam_FW_update_ui.exe >> Camera ISP Firmware update (real nice find) (watch out for bricking, launched, but not tested)
\windows\AppCheckerShim.exe >> (stopped my music for a secound :/ ?)
\windows\FailedStorageUI.exe >> manager for "There's a storage error" \Long info text here\
-[emergency] : [turn off] (cant backpress, do [Home])
\windows\flightmode.exe >> shortcut for the On/Off of the airplane mode
\windows\GamesUx.exe >> games - collection (direct exe of tile "Games")
\windows\invalidLicenseUxLauncher.exe >> (wont lanch this one, may brick my phone; update: not dangerous)
\windows\OneNoteMobile.exe >> One Note (somehow it closes it self direct after load (navigation fade))
\windows\PhotoEnt.exe >> Pictures #[all/date/favorites] (glitch?, no thumbnails on EVERY pic)
\windows\PhotoEntCapture.exe >> Camera/focus held down 2 sec~
\windows\TestShow.exe >> all-in-one [AmbientLight/Accelerometer/Proximity/Compass/FMRadio]-Tester
-(same as "see > FailedStorageUI.exe > cant backpress", + CANT [HOME]!, do [EXIT] button)
\windows\Version.exe >> (real nice to "see > Cam_FW_update_ui.exe") >>
-(not the "Settings > about", better) >> 'Wi-Fi MAC', PDA: I8700????? ('?' = my id, 5-char),
-and some etc info (BT ver + etc)
\windows\WebSearch.exe >> physical [Search]
\windows\WiFiUXSplash.exe >> direct exe for "Settings > Wi-Fi"
\windows\ZipView.exe >> ZipView.exe %1 (args), zip file viewer
May come more exe's at next WP7 Microsoft update 1
Rename attatchment to xap and ChevronWP7 -it if u want to try em out.
Nice tool
can you do it HTC compatible with arguments and log
to see exe error?
that can help a lot dev.
i have already try all exe with remote execute.
invalidLicenseUxLauncher.exe just show popup message saying invalid license
not dangerous.
xboxmod said:
Nice tool
can you do it HTC compatible with arguments and log
to see exe error?
that can help a lot dev.
i have already try all exe with remote execute.
invalidLicenseUxLauncher.exe just show popup message saying invalid license
not dangerous.
Click to expand...
Click to collapse
Im not the owner of project "NativeCodeTest" you may ask RustyGrom, just having fun crawling my WP7, so sry cant make it HTC compatible =D
Hello people!
I proudly present FunkyROM v2.0 for the Nokia Lumia 900!
But first of all:
I would like to say a huge thank you to everyone who made this rom possible!
Rataplan: Thank you buddy! I've learned so much from you!! Thank you for your friendship!!
-=Barin=-: for giving us the heart of rom-cooking: OsBuilder!
ultrashot: for all your amazing stuff you did for WP7 community!
dewe: for your LumiaDownloader, it's awesome, i didn't have to reboot to ubuntu for everytime flashing the rom!
Heathcliff74: for your WP7 root tools!
Jaxbot: for all your amazing stuff on windowsphonehacker.com!
everyone else i didn't mention by name, but used stuff from!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshots were taken using USB Video Out.
Changelog v2.0:
- included MS os updates 7.10.8860.142 and 7.10.8862.144 --> live tile fix!
- added full CAB update support to cab updates signed by: lordmaxey (me ), ultrashot, XBmod-Yuki, Rataplan, CeesHeim, pdaimatejam, voluptuary
- of course everything else from v1.0
Click to expand...
Click to collapse
Changelog v1.0:
Basic rom: RM-823 2175.2907.8858.13030 - MX Country Variant
Languages: all official languages, set 0809 (eng-GB) as default
Added:
- Full Unlock v4
- Root Manager --> Settings
- XapDeployer --> Settings
- customizable SearchKey --> Settings
- Wmdc
- Bazaar
- Camera Extras
- Flashlight
- KeepWifi Alive
- Program Manager --> Settings
- Screen Capturer
- WP7 RootTools
- WPH Tweaks
- USB Video Out
- Tile World Clock
- Colors Start Menu
- GSensor Switch --> Settings
- "Custom Blue" Theme --> set as default
Removed:
- preinstalled AppHighlights
- preinstalled ESPN
- VolumeLimit
Else:
- modified Internet Explorer Favourites
- modified Phone Info/about
Click to expand...
Click to collapse
Please note, you can only flash this ROM when your Lumia 900 is QUALCOMM.
and you're using this ROM at your OWN RISK.
one last thing: I hope you can enjoy your Lumia 900 device even more with my rom.
Download:
FunkyROM v2.0 for Lumia900 RM-823
Mirror @ 4shared
useful stuff
Dewe's Nokia Lumia Downloader 0.5
I attached the Nokia Lumia Downloader 0.5 for flashing your Lumia 900 easily in Windows.
Thx to dewe for his great work!
How to use USB Video Out:
As it seems to be a little "difficult" to use the usb video out package, here's what you have to do (this is a copy out of the readme file of the package):
You can download the needed files here:
USB-Video-Out.rar
Mirror @4shared
Enabling USB video out on the phone (ON THE PHONE)
- From Start Menu swipe over to the application list and run "USB Video Out"
- Answer Yes to enable USB Video out. This is a toggle.
- When the phone boots up it is in Zune Mode which enables it to sync data with Zune Client software on the PC. You will need to toggle this to Video mode using the above steps to get video out.
- Note: Toggling between Zune mode and Video mode requires the phone to reboot each time.
Setting up driver on the desktop (one time)
- Make sure Zune is not running.
- Your Phone must be flashed with a ROM that has video out bits on it, they must be enabled, and the phone must be on and plugged into your PC to continue. When the phone boots up the default setting is OFF for the video output.
- Start -> Right click on Computer, select Manage
- In "Computer Management" click on the Device Manager
- Under "Other Devices"
- Within the list of drivers Right Click on WM7VIDSTREAM driver, select "Update Driver Software..."
- Choose Browse and point Windows to appropriate driver folder.
- Approve the Unsigned Driver installation.
Starting application
- Launch VidStream.exe.
- This application does support disconnect & reconnecting of the phone's USB cable.
- If a previous instance of VidStream.exe was running with the device connected, you will need to simply unplug and replug the phone's USB cable.
- Press ESC to exit the PC Client application.
Re-enabling MTPz USB sync (Zune Mode)
- Open "USB Video Out"
- Answer Yes to enable MTPz
- The device will reboot to make the changes effective.
Click to expand...
Click to collapse
Update to 8860 and 8862 successful
Hi there,
just a quick information:
I successfully updated to the Microsoft OS Updates 8860 and 8862 via Zune.
Unlock is still ok, also the qualcomm bootloader was not overwritten :good:
The only thing it "killed" so far, is the information of my Custom Rom in settings --> about.
It changed firmware revision number from "FunkyROM v1.0 - xda-developers" back to "2175.2907.8858.13030"
cheers
Will this work with AT&T Nokia Lumia 900?
Hi lordmaxey,
Last week I downloaded this rom 2175.2907.8858.13030 from navifirm then flashed it using the NCS. No problem when flashing it. But my concern is the battery drain. So I decided to go back to 2175.2905.8858.12480 (variant finland). Actually im not sure if my qualcom is unlock. My question is can I use this rom same process to flash it by using NCS? thanks
AW: [Custom ROM] FunkyROM v1.0 - Lumia 900 RM-823 - All official languages
kunalsethi50 said:
Will this work with AT&T Nokia Lumia 900?
Click to expand...
Click to collapse
i'm not sure, because i haven't tested. But probably not.
kookook said:
Hi lordmaxey,
Last week I downloaded this rom 2175.2907.8858.13030 from navifirm then flashed it using the NCS. No problem when flashing it. But my concern is the battery drain. So I decided to go back to 2175.2905.8858.12480 (variant finland). Actually im not sure if my qualcom is unlock. My question is can I use this rom same process to flash it by using NCS? thanks
Click to expand...
Click to collapse
no, you need to have an unlocked bootloader, to flash this rom. You can not flash it using NCS.
However Nokia want to sell her phones or atf boxes? ) Why write that stupid nokia bootloader? I read forums and see peoples buying Atf box for flashing phones.
updated to v2.0
Hi there,
just updated first post to FunkyROM v2.0.
Changelog v2.0:
- included MS os updates 7.10.8860.142 and 7.10.8862.144 --> live tile fix!
- added full CAB update support to cab updates signed by: lordmaxey (me ), ultrashot, XBmod-Yuki, Rataplan, CeesHeim, pdaimatejam, voluptuary
- of course everything else from v1.0
Click to expand...
Click to collapse
Enjoy.
please how to flash it
do I need any other device or just a software
please give me the light
Abd654 said:
please how to flash it
do I need any other device or just a software
please give me the light
Click to expand...
Click to collapse
guys, did you do any searching?? any??
http://forum.xda-developers.com/showpost.php?p=38774062&postcount=12
lordmaxey said:
guys, did you do any searching?? any??
http://forum.xda-developers.com/showpost.php?p=38774062&postcount=12
Click to expand...
Click to collapse
one fast question , i belive not stupid , if i use this rom , i will be able to find some extra apps here or on the internet , or only marketplace and the preinstalled ?
i ask this , because i dont have something like this before ...
Santoman7 said:
one fast question , i belive not stupid , if i use this rom , i will be able to find some extra apps here or on the internet , or only marketplace and the preinstalled ?
i ask this , because i dont have something like this before ...
Click to expand...
Click to collapse
because this rom is fully unlocked, you can install every xap (apps) you can find on the internet or in preinstalled programm bazaar.
lordmaxey said:
guys, did you do any searching?? any??
http://forum.xda-developers.com/showpost.php?p=38774062&postcount=12
Click to expand...
Click to collapse
I find a store which can unlock my phone but hasn't atf box , but another flasher for lumia phones , will it work ok ;
I told this because if i have understand well , i want only the Qualcomm bootloader , so is it possible ;
And finally if i get the bootloader , i then go home and put the rom or rom want the box to get installed ;
Thanx for your time ...
Santoman7 said:
I find a store which can unlock my phone but hasn't atf box , but another flasher for lumia phones , will it work ok ;
I told this because if i have understand well , i want only the Qualcomm bootloader , so is it possible ;
And finally if i get the bootloader , i then go home and put the rom or rom want the box to get installed ;
Thanx for your time ...
Click to expand...
Click to collapse
?
as far as i know, ONLY ATF can replace dload with qualcomm bootloader.
If that store does NOT have an ATF, i think they were lying an cheating to you! be careful!
Yes, once you've got the qualcomm bootloader, you can go home and flash my rom using dewe's Lumia Downloader 0.5.
I recommend you reading this thread: http://forum.xda-developers.com/showthread.php?t=2204994
lordmaxey said:
?
as far as i know, ONLY ATF can replace dload with qualcomm bootloader.
If that store does NOT have an ATF, i think they were lying an cheating to you! be careful!
Yes, once you've got the qualcomm bootloader, you can go home and flash my rom using dewe's Lumia Downloader 0.5.
I recommend you reading this thread: http://forum.xda-developers.com/showthread.php?t=2204994
Click to expand...
Click to collapse
http://gsmserver.com/shop/gsm/cyclone_box.php
this is the box i found ...
Santoman7 said:
http://gsmserver.com/shop/gsm/cyclone_box.php
this is the box i found ...
Click to expand...
Click to collapse
No, this box can not flash qualcomm to you Lumia!!
A Lumia phone is NOT a BB5 phone!!! Totally different!
lordmaxey said:
No, this box can not flash qualcomm to you Lumia!!
A Lumia phone is NOT a BB5 phone!!! Totally different!
Click to expand...
Click to collapse
so , I give up ..... None can help me ... And I don't give so much money to buy a flashing machine for just one phone update .... Will may be another way someday ? Or Its finally this way ?
USB Tether
Guys, apologies if this has been covered before. I'd love to share the internet connection via usb to avoid battery drain with wifi sharing. Do any of the custom ROMs allow/enable this? Seems to have been made possible with some of the Samsung Windows Phones but I find the network performance to be phenomenal on the 900 - even better than the 920 I own (looks like this is nowhere near possible on the newer 920). Was hoping the issue had been cracked on the older hardware/software!
@lordmaxey this ROM is amazing :victory: Thank you very much!
there is posible one problem: IE often crashs (I mean that IE automatically exits ) when I watch some websites that contains lots of pictures It does not happen in the original ROM.
But I'm uploading your ROM again and hard reset my phone. Perhaps the problem will disapear
steviesteve78 said:
Guys, apologies if this has been covered before. I'd love to share the internet connection via usb to avoid battery drain with wifi sharing. Do any of the custom ROMs allow/enable this? Seems to have been made possible with some of the Samsung Windows Phones but I find the network performance to be phenomenal on the 900 - even better than the 920 I own (looks like this is nowhere near possible on the newer 920). Was hoping the issue had been cracked on the older hardware/software!
Click to expand...
Click to collapse
No It isn't possible to share Internet connection via USB in Windows Phone
thangvh said:
No It isn't possible to share Internet connection via USB in Windows Phone
Click to expand...
Click to collapse
Yes it is...
Search for "enable USB Tethering with Windows Phone"
INFO
I sold my P10 Lite, based on Huawei's decision to no longer provide bootloader unlock codes.
For a generic version of this project (ADB-Overlay) have a look at this thread.
The latest build of this project is still available.
---
Hello together,
here is a toolkit for the P10 Lite, it's designed to work primary with root (THE MOST TIME) so be careful what u are doing, specially if u are using the "Explorer". (Deleting the wrong file/folder on root lvl, could bring u in bad trouble!)
-
To all who used already my P9 Lite toolkit, there is currently not all available which u know from the old version, but i'll extend this toolkit in the next days. So, no worries about missing functions, they'll appear in some of the next builds.
-
About the usage,
- For a basic UI-Help just press F1
- If ur device is not detected u can switch off the "Device check" on the "Disclaimer" view (If u own a P10 which is not detected pls share a screenshot of the "adb devices -l" (l = lowercase L) command)
- U can also switch the (su -c) usage off (in the explorer view), BUT! after u performed any action which requires root, the trigger will be automatically switched on. (There is no other option, because my dll know only, use root or don't do so... There is no use root part-wise)
But anyways, i'm NOT responsible for any damage to your device!
Little preview of what u get
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tested Devices
Huawei P10 Lite [WAS-LX1A] [SINGLE-SIM]
Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
XDA:DevDB Information
WAS-Lxx [EU] Toolkit, Tool/Utility for the Huawei P10 Lite
Contributors
k1ll3r8e
Version Information
Status: Stable
Current Stable Version: 0.0.0.5
Stable Release Date: 2018-08-01
Created 2018-03-30
Last Updated 2018-08-15
How-To
[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging (see the screenshot)
(Only in adb mode my toolkit can detect ur device)
3. Make sure that u granted adb access on ur device
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.
U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:WAS-Lxx model:WAS-Lxx device:XXXXXXX
If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.
[Q:02] What does the Lxx Cxxx Bxxx mean?
The Lxx is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.
Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL
More comming soon...
Big THX for some of those "identifier" goes to:
@lost3
@baduncle
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
[Q:04] How can i manually boot into a specific mode?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[fastboot] = N/A
[Q:05] Does the Dual-Sim upgrade survive an OTA?
Yes, the Dual-Sim modification will stay until u flash another oeminfo.
[Q:06] I upgraded to Dual-SIM and there is only one IMEI shown?
That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim or as shown the "0000000000000000".
Changelog
2018-08-01 - 0.0.0.5
* Added a Remote-Desktop
* Added a "partition selector" (recovery [Nougat], recovery_ramdisk [Oreo])
* Added a rooting option for Oreo
* Fixed a few bugs
* Realigned a few container
2018-04-21 - 0.0.0.4
* Added on the Device-Info view the BusyBox check
* Added the Phone control
* Added the Root menu (just waiting for permissions to include a zip)
* Added some features to the Explorer "View" menu (e.g. Sync with Treeview, Layout, Sort)
* Added a Display-Trigger to the "Power-Button" menu
2018-04-10 - 0.0.0.3
* Fixed a crash which appeared during device connection on the Explorer view
* Switched the whole window stuff to my new GlassWindow
* Added a AlphaChannelSlider (left beside the [--] button) for those which don't like transparent windows
* Added a Device-Info view
2018-04-01 - 0.0.0.2
* Fixed the icon bug (Big Icons, List)
* Re-positioned the "View" menu and made 2 of them, one for each view
* Refactored the "Button" layout, that they match now with the rest of the dark theme
* Added a fallback color "#2C2C2C" for those who got maybe the error message that the Glass-Effect couldn't be applied
* Added the "Shell-Tools" menu
* Added the 1st tweak (Pro-Mode)
Bug-Tracker
*FIXED in 0.0.0.2
- Noticed already the missing icons in the "Explorer" (Big Icons + List)
(Bug is already solved and will be fixed in the next version)
Known-Issues
- The "Explorer" "Big Icons" looking a bit ugly, that's because the p/invokes won't give me the "Extra Large" icons... I still work on it, so maybe it's fixed in the next version.
--
Drag 'n' Drop on any Explorer view, from outside the Application won't work until u run everything as Admin... That's a Windows UAC restriction and based on the fact, that we need the right's to create/delete/modify files/folders under Win8++ on the system HDD. (Like ADB pull for export of the oeminfo and custom.bin)
Missing Tweaks from the P9 Lite Toolkit
- As the screenshot shows, i managed to activate the "Double-Tap" menu, but that's all... The Double-Tap it self doesn't work... So there will be no "tweak" for this. - (Additional Info: The Double-Tap works^^ But ONLY on the lock-screen... And ONLY to turn the screen off... What a joke...)
- USB-OTG, is not available because, so far i know, u need a special kernel for it. (Which i can't provide, atm)
- AppTwin, because it should be enabled on any P10 Lite by default
Little - Update (1+2+3+4)
- I added a screenshot of the upcoming release, with integrated "Phone" control. (Currently only Call/Dial works)
- Added another screeny, now (Call/Dial/Add) is possible. Add, needs still interaction on the device side, like which "provider" (Device, Google, etc.) u want to choose. Dial, will insert the number in the default dialer, or it gets captured by any USSD protection. Call, will immediately start a call to the provided number.
- Just tested to send USSD-Codes like "*#06#", but it seems that u really have to type them... Even sending "*#06" and manually type the "#" doesn't work... U have to delete and re-type the whole USSD-Code...
- Added the final look of the "Phone". (At least, Add, Call, Dial, Hang-Up) is now possible.
For those which also use XAML, here are the control-button-geometries i created:
Menu-Button
Code:
<Path Fill="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="2,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,14" RadiusX="1.5" RadiusY="1.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Call-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,9 8,13 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Hang-Up-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,13 13,5 M 5,5 13,13" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Dial-Button
Code:
<Path Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="9,9" RadiusX="8.5" RadiusY="8.5"/>
<EllipseGeometry Center="6,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,14" RadiusX="0.5" RadiusY="0.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Delete-Button
Code:
<Path Data="M 0,7.7 5,2 16,3 16,12 5,13 Z M 8,5 13,10 M 8,10 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
WAS-LX1AC432B204dual
oeminfo
WAS-LX1AC432B206dual
oeminfo
I tested it on my WAS-LX1 C10 DS/ It works.
Perfect
Thank you !
rom issue
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Use only stock ROMs for now, cuz there's no daily driver Customs for P10 Lite yet. Stock Oreo is really good. You can use HwOTA to flash stock ROMs.
nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
k1ll3r8e said:
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
Click to expand...
Click to collapse
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---------- Post added at 12:18 PM ---------- Previous post was at 11:59 AM ----------
k1ll3r8e said:
If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent.
Click to expand...
Click to collapse
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
nsx82 said:
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
Click to expand...
Click to collapse
Heyho,
np
-
Yes, the "Lx1" are always the SS and the "L[1-9]1" are the DS variants. - Btw. u can't see the "real ID" under "Settings -> Info" to see the "real ID" u have to look in the "current" oeminfo.
-
I wrote a tool for this kind of tweaking/exploring, have a look at it, u can get it here
EDIT:
About the issue with the display/animations, it could also be a problem with the HW... I have seen a few forum posts about "factory delivered" broken chips etc.... Maybe there is something else wrong, if it was really from the 1st day u got it.
Regards,
Sebastian
Little Update
Heyho together
-
Here is a little preview of the upcoming update.
* Added a Remote-Desktop (touch, swipe and keyboard are working so far)
* Improved the speed
* Fixed a few minor bugs
Release should be in 2-3 days
Version 0.0.0.5 is online!
Regards,
Sebastian
k1ll3r8e said:
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
Click to expand...
Click to collapse
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
callmeWhiskers said:
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
Click to expand...
Click to collapse
Heyho,
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Regards,
Sebastian
k1ll3r8e said:
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Click to expand...
Click to collapse
Thank you very much for clarifying and shedding some light on this, Sebastian!
From what I've read, reconstructing (files) from checksums doesn't (really/easily) work - though in theory (if enough additional parameters are given, and IMEI/IMSI are kind of short strings) it could be reverse engineered - unless I interpreted my research findings wrong :victory:
I assume it's safe though
Liebe Grüße nach Delmenhorst!
Hi world(first post since android(previous windows mobile member of xda)),
I have P10 lite for almost a year(not rooted for warranty issues).
I wanted to perform a stock firmware backup before I endulge in rooting/custom ROM.
Is that possible with TWRP(with or without rooting), and are there any how-to's?
Sorry for being such a newbie, just like to upgrade to 8.0 and revert back to stock in case of a problem or warranty issues.
Thank you.
Recovery