Database Info

[Reference] Stock G1 to Newest CM (5.0.7 Stable)

This is a guide that I created for a friend of mine. Since originally putting it together I have found myself going back to it often as a quick reference guide on how to perform certain procedures. I figured that I may as well share it for others that might find it useful. I will do my best to keep it as up to date as possible.
Gain Root
Koush put together an excellent guide for this here:
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Recovery
Rom Manager to install either clockwork recovery or amon ra recovery
{
"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"
}
Rom Manager
Click to expand...
Click to collapse
Backup
In either recovery you can do a nandroid backup. Do a full backup in case anything goes wrong you can restore phone to its previous state. If you have apps2sd running you will want to select the option that does ext backup as well. Basically its best that every time you have your system working the way you like it to do a nandroid backup so you always have the most recent restore point for your phone.
Alternately, if you simply want to backup applications or system settings individually download MyBackup or Titanium backup You can opt to save application data so that all of your application settings and such are saved as well.
MyBackup
Titanium Backup
Click to expand...
Click to collapse
Flash Radio Update
**NOTE** It has been brought to my attention that it can be unsafe to flash Radio or SPL via recovery (result in brick). Fastboot is much safer. I completed this via recover without any issues. However, I am not responsible if something happens. I will be adding instructions for fastboot shortly. Haven't touched it since I first got my phone way back so need to relearn the procedures. Info HERE**
http://forum.xda-developers.com/showthread.php?t=640535
Download - http://www.mediafire.com/?zgnzmex2mrj
Copy to SD card
In recovery apply zip
Click to expand...
Click to collapse
Flash Danger SPL
**NOTE** It has been brought to my attention that it can be unsafe to flash Radio or SPL via recovery (result in brick). Fastboot is much safer. I completed this via recover without any issues. However, I am not responsible if something happens. I will be adding instructions for fastboot shortly. Haven't touched it since I first got my phone way back so need to relearn the procedures. Info HERE**
http://wiki.cyanogenmod.com/index.php/DangerSPL
Download - http://sapphire-port-dream.googlecode.com/files/spl-signed.zip
Copy to SD card
In recovery apply zip
Click to expand...
Click to collapse
Partition SD
In recovery partition SD
~500 ext
64 swap (only do swap if you intent to use it; read info on swap below before you decide)
*These are my settings. You can adjust as you wish
Click to expand...
Click to collapse
Flash Newest CyanogenMod Rom (5.0.7 Stable)
http://forum.cyanogenmod.com/index....magic-mean-lean-pastry-machine-v507-05252010/
Download - http://www.kanged.net/mirror/download.php?file=update-cm-5.0.7-DS-signed.zip
Download - http://kanged.net/mirror/download.php?file=gapps-ds-ERE36B-signed.zip
Copy all to SD card
If first time installing CM 5.0.7 do a wipe in recovery
In recovery apply update zip
In recovery apply gapps zip (not necessary if already running previous version of 5.0.7)
*Note
Go into settings
Application settings
enable unknown sources and aps2sd
Click to expand...
Click to collapse
Optional Addons Must be completed after every rom flash to retain effects.
Enable Swap
**Note** Each location on a flash memory card can only be written to so many times before it stops working correctly. Since swap will cause the swap partition to be written to frequently, there is a potential issue of wearing out part of a flash memory card. If a card wears out while using swap, your system will malfunction and crash.
Wear leveling is a mechanism that distributes write wear uniformly over the entire memory card by dynamically remapping logical memory blocks to different physical memory blocks over time. This largely alleviates the issue of card wear when using applications such as swap that tend to write to the same memory blocks over and over.
Anecdotal reports on the 'net indicate that most Class 6 microSDHC include hardware wear leveling, while Class 4 and lower cards typically don't. A-Data and Transcend Class 6 cards were specifically cited as having hardware wear leveling. Many people have used these cards for swap without issue. In the end it is your decision on whether you want to take the risk of running swap. Many respected developers here recommend you not use it.
http://forum.cyanogenmod.com/index....swap-partition/page__view__findpost__p__30130
Download - http://dl.dropbox.com/u/5702285/G1/86swapon.txt
Edit 86swapon.txt (default at 30 swappiness)
Copy to SD card
In terminal:
su
mount -o rw,remount /system
cp /sdcard/download/86swapon.txt /system/etc/init.d/86swapon
chown 0:2000 /system/etc/init.d/86swapon
chmod 755 /system/etc/init.d/86swapon
sync
reboot
*Verify by typing "free" in terminal (swap will show values instead of "0")
To disable swap do the following:
su
mount -o remount,rw /system
rm /system/etc/init.d/86swapon
sync
reboot
Click to expand...
Click to collapse
Enable JitFix
http://forum.cyanogenmod.com/index.php?/topic/2910-jit-installeruninstaller-script-507t3-updated/
Download - http://dl.dropbox.com/u/5702285/G1/JIT-Install.zip
Extract JITFIX folder to SDCard
In terminal:
su
sh /sdcard/JITFIX/install
after installation is complete you will be asked if you want to install the fix as well
just type Y and hit enter
the next line will ask where your dalvik-cache is located
Type S for SD card
*verify by typing "dalvikvm -h" in terminal (last line will contain "WITH_JIT")
Click to expand...
Click to collapse
Enable OverClock
http://forum.xda-developers.com/showthread.php?t=679033
Download - http://fromhindsight.com/crap/overclock_update.zip
In recovery apply zip
Download SetCPU
Open and set auto detect.
Set max to no higher than 652800
Min works good at 480000
*These are general settings. You can find a more in-depth conversation about what good settings are at the link above.
SetCPU
Market link above for donate. Free for XDA members here
Click to expand...
Click to collapse
Facebook Account Sync
http://forum.xda-developers.com/showthread.php?t=679572
Facebook from market breaks sync for Market users. Firerat has posted a great patch file for fixing this issue.
Download - http://forum.xda-developers.com/attachment.php?attachmentid=325544&d=1273702838
Copy to SDCard
In terminal:
su
sh /sdcard/fr-patch132.txt fb
Go into Facebook app and edit settings for sync
Click to expand...
Click to collapse

Thanks for this guide!

What's this for?
echo 255 >/sys/class/leds/blue/brightness;

yokonunz said:
What's this for?
echo 255 >/sys/class/leds/blue/brightness;
Click to expand...
Click to collapse
Led will turn blue after settings swap on startup. (Will be reset later in the startup process)

Enable Facebook Sync
To enable Facebook sync use firerats script: http://forum.xda-developers.com/showthread.php?t=679572
su
sh /sdcard/fr-patch132.txt fb
Click to expand...
Click to collapse

fonzie123 said:
Led will turn blue after settings swap on startup. (Will be reset later in the startup process)
Click to expand...
Click to collapse
As Fonzie stated, it makes your led turn blue during startup. This lets you know that the script file is being run. You can safely remove that section if you do not need to notification. I just like having it there.

fonzie123 said:
To enable Facebook sync use firerats script: http://forum.xda-developers.com/showthread.php?t=679572
Click to expand...
Click to collapse
Thanks for that. I'll add it to the guide.

Should be on Cyanogenmod wiki where it belongs

xaueious said:
Should be on Cyanogenmod wiki where it belongs
Click to expand...
Click to collapse
I can throw it on there as well, but I think it belongs here as much as it does there. xda-dev forums are here to help all, and have a much larger user base. A large number of g1 users here use cyanogen. And besides a lot of this can be used for other roms as well. It's simply a quick reference guide to help people out.

To be safe, if you already have the newest radio 2.22.23.02, I say DOWNGRADE to 26i. That way when you're flashing the Danger SPL you decrease your chance of getting a brick.
I know thins because I accidentally bricked my friends G1 because he had the newest radio(2.22.23.02) when I flashed Danger over it..
I wouldn't know how to write out the steps so if you kindly would.
And if you already have 26i whoopy dooo for you less work.

AustinAce said:
To be safe, if you already have the newest radio 2.22.23.02, I say DOWNGRADE to 26i. That way when you're flashing the Danger SPL you decrease your chance of getting a brick.
I know thins because I accidentally bricked my friends G1 because he had the newest radio(2.22.23.02) when I flashed Danger over it..
I wouldn't know how to write out the steps so if you kindly would.
And if you already have 26i whoopy dooo for you less work.
Click to expand...
Click to collapse
That advice is false.
What does prevent accidents when flashing radio is flashing in fastboot

xaueious said:
That advice is false.
What does prevent accidents when flashing radio is flashing in fastboot
Click to expand...
Click to collapse
I'm talking about the SPL. When I flashed Danger over 2.22.23.02 I bricked my friends phone.

What xaueious means is that flashing a radio or SPL through recovery has been proven dangerous. We don't fully understand why, but we do know that you run close to 0 risk if you flash through fastboot instead. Danger has been shown running on old 1.x radio's before, only if they are flashed through fastboot.

mejorguille said:
What xaueious means is that flashing a radio or SPL through recovery has been proven dangerous. We don't fully understand why, but we do know that you run close to 0 risk if you flash through fastboot instead. Danger has been shown running on old 1.x radio's before, only if they are flashed through fastboot.
Click to expand...
Click to collapse
Oh hahaha alright I get it thanks for clearing that up for me.

Sorry! Process System is not responding
i don't know what i have done to the phone. since i flash cm5-t5, i get warning "Sorry! Process System is not responding" everytime I reboot the photo and then unlock it. I did try to wipe and flash back to cm5-t4, i still get the same warning.

xaueious said:
That advice is false.
What does prevent accidents when flashing radio is flashing in fastboot
Click to expand...
Click to collapse
Thanks for the info Xaueious. I looked more into this and found the following:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
I will be updating my reference guide here shortly to reflect this information.

Great guide i just placed it in the bible

Royalknight6190 said:
Great guide i just placed it in the bible
Click to expand...
Click to collapse
Thanks Royalknight. I figured some people could get some use out of it. And it helps me update my procedures as people kindly let me know of better ways to do things.

sagementor said:
i don't know what i have done to the phone. since i flash cm5-t5, i get warning "Sorry! Process System is not responding" everytime I reboot the photo and then unlock it. I did try to wipe and flash back to cm5-t4, i still get the same warning.
Click to expand...
Click to collapse
So you had test 4 running good, and flashed test 5 over it correct? No other changes? Upon booting up when you attempt to unlock you get the above error message?

i don't remember. i can eliminate the problem by swipping the ext partition. however after i add back some apps, the problem appears again.

[Guide][CM7 2.3.5][ROM][BackLight Fix for CM7] CM7 and MIUI port from Defy

This thread is outdate.New thread is here: http://forum.xda-developers.com/showthread.php?t=1239778
======================================================================================================
[Real DEV][ROM][Port][Updated: 19-Aug-2011]GB MIUI for Milestone2 All-in-one update.zip Thanks to r2beta0 !
Now dangpzanco has set up a project base on MIUI/CM7 on github, anyone who interst in it can contact with him or come here !.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you have any problem in using CM7/MIUI, before question, you may take a look at this thread.
Im not a DEV, so any tutorial and help is very welcomed. If someone can develop for it, that would be very thankful !
Any defy CM7 based/cooked/moded ROM include MIUI can use this method to boot.
Thanks to dangpzanco and r2beta0 for their great effort. And walter79 for the great idea.
Known compatible kernels：
It seems only 2.6.32.9-********[email protected]**lnxdroid**#* series kernels are supported.
2.2.2-CH include 2.10.0 / 2.6.0 / 2.5.0
2.2.1-CH 1.10.0 / 0.24.0
Known incompatible kernels：
2.3.4-CH leak
2.2.2-UK/DE,AT,CH/Argentina/HongKong/Italy
2.2.1-Mexico
2.2-Brazil/France/UK/Australia
Unknown kernels:
2.2.2-France
2.2.1-Argentina
2.2-Argentina/DE, AT, CH
This is my nandroid backup with some fix but not all, you could choose one or not.
[Recommend!]1. Based on MIUI 1.8.12 moded by Wajk, download: http://www.megaupload.com/?d=1RF2A3JC
2. Based on a cooked CM7 ROM(thanks to VIPFXY): http://www.megaupload.com/?d=NOWVXJAK
3. Based on cm7-110813-2132-NIGHTLY-Jordan.zip http://www.megaupload.com/?d=17RERZSM
Patch for CM7/MIUI ( It should work on all defy CM7/MIUI based/cooked/moded ROM ):
This patch fix the following：
1.GSM problem, you may still need to use baseband switcher to change your baseband (If you still have no signal, take a look at this,theoretically it 100% works! http://forum.xda-developers.com/showthread.php?t=1182050 )
Thanks to i7ovehope and dangpzanco
2.Keyboard mapping issue ( except ALT-LOCK, however you can double press ALT instead ) Thanks to 19900828xy
3.fix CWM issues related to /data Thanks to r2beta0
4.When you are charing, you will have your LED turn yellow to tell you, instead of nothing (Charger light still not work)
5. Gravity-sensor/light-sensor are working again Thanks to walter79 and dangpzanco
6. GPS should works
7. compass should works
And the patch does NOT include the following fix, you will need to do it yourself：
[Both CM7 and MIUI]0. Keyboard backlight fix ( Thanks to r2beta0 for fixing. Thanks to nanox_06 from grupoandroid.com. Thanks to layoroa and Motodoido and julianlatasa for telling me ):
Make sure you have apply fix_for_cm7_miui.zip from my attachment ! AND, if you have tried the earlier method （replacing framework-res.apk ), you SHOULD restore the original apk before trying this method !
[CM7]open setting>CM setting>Displayer Setting>(on)Automatic brightness>Advance mode>(on) custom>Edit other levels...
[MIUI]open setting>Displayer Setting>(on)Automatic brightness>Advance mode>(on) custom>Edit other levels...
[Wajk/r2beta0`s MIUI]r2beta0 has uploaded a moded framework-res.apk in #203, you can download it from there and replace the one under /system/framework/ . Don`t forget to set the permission to rw-r--r--. Reboot and Done !
then you will see a mass of squares. Find keyboard row and change the first 2 value from 0 to 255. Save setting. OK, done! Pull out your keyboard and you will find backlight work again.(Be sure you are in dark environment)
Tips: After turning off automatic brightness, your backlight will still work.
{
"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"
}
1. camera upside down ( Thanks to walter79 )
comment the line:
ro.media.capture.flip=horizontalandvertical
in /system/build.prop, make sure it is
#ro.media.capture.flip=horizontalandvertical
2. The camera noise after system booting, which exist in MIUI moded by Wajk
freeze talk.apk under /system/app
if you still need to use gtalk, try to install it from apk (not test if this will bring back the noise )
3. Stock soft-keyboard too small
Use 3rd-party keyboard app to replace it
4. Phone version shows MB525
Edit the line:
ro.product.model=MB525
in /system/build.prop to
ro.product.model=A953 //or anything you want
5. The default baseband of my nandroid backup is CH2.6.0/2.5.0
If you have no signal, please use baseband switcher to change to a suitable one or take a look at this (theoretically 100% works ) http://forum.xda-developers.com/showthread.php?t=1182050
6. If you think your flash light is a little dim compared to before. (Thanks to walter79 and below is what he said )
Be careful with that. Chinese pepole killed it with fixed-sbf for Europe Defy and in past europe people killed led with china fixed-sbf. It is related to devtree. But if your flashlight works more than 2x then you can edit your build.prop and del this:
- ro.media.capture.flashIntensity=41
- ro.media.capture.torchIntensity=25
7. SD card can NOT be mounted in recovery
In recovery, open advance, select start adbd and then kill adbd. Go back to try, and you should find your sd card has been mounted correctly. Next time if the issue appears again, just re-do it again.
8. If you have USB connection problem. Thanks to r2beta0
[MIUI] Please go to #211 for framework-res.apk. Replace the one under /system/framework/ with it.
[CM7] This is the manual solution r2beta0 post in #213
You must download apk_manager and use it to decompile framework-res.apk. Then you edit bools.xml that is inside res/values folder. The variable you must change is called config_enableUsbModeSelection, it is a user friendly name. Change from false to true. Then you use apk_manager to recompile it but don't sign. Set compression to zero.
The known issues which can NOT be solved till now:
1.Video hardware decoding is dead mostly, only .mp4 survival (need someone to fix that soon!)
[DEV] I upload these 2 patch which is used to port rmvb/mkv HW Decoding to froyo. It should help with porting HW to CM7/MIUI.
[MultiUpload] http://www.multiupload.com/JYNSW5VILR
[MegaUpload] http://www.megaupload.com/?d=A9OC25CT
[WithProxy][MegaUpload] http://174.140.154.13/?d=A9OC25CT
[Hotfile] http://hotfile.com/dl/127190044/59fde10/milestone2_RmvbMKV.7z.html
2.ALT-LOCK not working ( double press ALT instead )
3.USB mass storage mode issue ( except MIUI moded by Wajk )
You will find that you can NOT mount your SD card to PC.
Softwate Solution[Recommend]: Install Protocol-X Dual Mount SD Widget, you can download it from Android Market.
Manual Solution: Every time you connect to PC. Make sure connection manager appears in your notification bar, if not, enable/disable USB debug. Once it shows, first choose NONE, and then choose USB mass storage. By all this, you will see your SD card mounted in PC.
4. Charger light still not work
Seems lights.jordan.so under /system/lib/hw is related to it in some way. I replace it with the one from new leaked GB, then the LED became the charger light
Tutorial:
1. reboot to CWM and then restore nandroid backup (if you want to flash defy_cm7/miui.zip, make sure your CWM is 3.0+)
2. enable bootloader mode, flash fixed sbf via RSD ( fixed sbf is in firmware.7z )
3. Its recommend to make double wipes in stock recovery
4. reboot
5. CM7/Miui running.
[DEV]CH 2.2.2 (2.10.0) Download (The one who has downloaded it earlier should redownload it again for the correct SBF )
If anyone need to download any other CH ROMs but cannt find them, you can send me a PM
http://u.115.com/file/clsmsk69 PASSWORD: bbs.dkdiy.net
Defy CM7 Download http://defycm7.tanguy.tk/ //RC1 and nightly build are all OK
[Defy][DEV][ROM] CyanogenMod 7 (Android 2.3.4) By Quarx
[Fixed]CWM3.0 Download http://forum.xda-developers.com/showthread.php?t=1196590
Fixed sbf of CH 2.2.2(2.10.0) please download it from attachment below:

Great!
Everything is working?
Sent from my Milestone 2 with GingerBread

Oh that sound great.
My phone is bootlooping right now I could test anything before flashing a working ROM
Gsm radio not working is expected, need custom fixes for cm7.
Just try to fix the led/lights

Good lord, this week is beeing the best for the milestone 2 community! Thanks for your efforts guys!

If rom is booting, we can easily get logcats to fix all the problems

inheme said:
Good lord, this week is beeing the best for the milestone 2 community! Thanks for your efforts guys!
Click to expand...
Click to collapse
I concur. Thanks guys for all your efforts!
Sent from Motorola Milestone 2

will5 said:
If rom in booting, we can easily get logcats to fix all the problems
Click to expand...
Click to collapse
It did boot! Now I am runing CM7.

inheme said:
Good lord, this week is beeing the best for the milestone 2 community! Thanks for your efforts guys!
Click to expand...
Click to collapse
+1 / Like
Sent from Motorola Milestone 2 @ GB

Exciting! Cant wait for a decent workable version.

Endless7 said:
It did boot! Now I am runing CM7.
Click to expand...
Click to collapse
Have you tried all the baseband fixes we have? chinese fix, defy baseband changer, milestone 2 baseband app...
Anyway, if none of them work, maybe baseband needs to be adapted to cm7.

yea like this one http://forum.xda-developers.com/showthread.php?t=1182050

will5 said:
Have you tried all the baseband fixes we have? chinese fix, defy baseband changer, milestone 2 baseband app...
Anyway, if none of them work, maybe baseband needs to be adapted to cm7.
Click to expand...
Click to collapse
The biggest porblem: I cannot connect my SD card to PC !

Maybe you can push the files via ADB to your SDCard/Internal memory?

U should get a microSD usb reader. I have one, maybe I could test stuff out for u.

Or you can use a sd card reader
Lets wait for experienced people, I think sd is not working just because it behaves differently than defy storage, it wont be hard to fix it.

I have no minisdcard reader and now time here is 0:30 am, so it`s impossible to buy one.

jambo89liam said:
U should get a microSD usb reader. I have one, maybe I could test stuff out for u.
Click to expand...
Click to collapse
USB debug is now dead
I have upload the files needed. You all could have a try !

You can try USB storage from CWM.

will5 said:
You can try USB storage from CWM.
Click to expand...
Click to collapse
OK , will have a try

Which cm did u download, ive downloaded the latest nightly build. "cm7-110518-0722-NIGHTLY-Jordan"
Im on Gingerbread at the moment, do i need to go back to froyo before flashing?

[Q] Need help with rooting ZTE N5 Grand Memo

Hello :laugh:,
I have an ZTE Grand Memo V9815 N5 Flagship Phone APQ8064 Quad Core 2G 16G Android 4.1.2 5.7inch from China, and i was wandering if anyone allready has found something to Root this device.
I have tried the standard superoneclick, but thats not working and crashes when in progress.:silly:
I want to root it, cause i need Google play on it. I have installed Google Services/Google Framework, and i can setup an account in Google Play, but after the account stuff Google Framework/Google Services/Youtube service/Google Play crashes constantly
So i contacted ZTE for support, but there is no Rom, or any update for this phone.
I googled some, and at some websites they wrote to Root the device, so its not crashing anymore.
Please help me to get Root on my phone, so i can install Google Play Store.
Thanks in Advance !!

Same problem
Hello Reppo,
I have the same problem. I am not able to root this fantastic phone ... I need to install Google Play on ti .. :crying:
Please advise me if you will find the rooting procedure for ZTE N5 Grand Memo.
Ciao!
Alfredo

alphredo said:
Hello Reppo,
I have the same problem. I am not able to root this fantastic phone ... I need to install Google Play on ti .. :crying:
Please advise me if you will find the rooting procedure for ZTE N5 Grand Memo.
Ciao!
Alfredo
Click to expand...
Click to collapse
I've root Grand memo. What's your specific problems? Did you install unofficial recovery and ADB drive?

HI 123sharon456,
I have no idea how to do it.
I just need procedure and also advice about where to find all the requested files.
Can you give me some advice?
Thanks!
123sharon456 said:
I've root Grand memo. What's your specific problems? Did you install unofficial recovery and ADB drive?
Click to expand...
Click to collapse

alphredo said:
HI 123sharon456,
I have no idea how to do it.
I just need procedure and also advice about where to find all the requested files.
Can you give me some advice?
Thanks!
Click to expand...
Click to collapse
1. Install driver
{
"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"
}
Check your device manager. If it looks like the image follows, it means your ADB driver does not been installed successful.
This is the successful status.
If you can't install ADB driver by automatic installation. You can install ZTE Join Me(mobile phone manager software), it will intall ADB.
2. Recovery
Extract it into any directory.
Click flashrecovery.cmd (antepenultimate) to this interface:
It will run automatically and reboot your phone. If not, reboot your phone and computer, then try again.
If everything is fine, try to enter the recovery.
Shutdown the phone, pressing on volume key by right hand + pressing on power key by left hand. When you see the screen light up and feel the vibration, release the power button. KEEP PRESS ON VOLUME KEY until you see the recovery interface.
-upgrade your system from SD card
-use slideload to upgrade your system
-wipe out data/restore the factory data
-wipe out cache
-backup and restore
-mount and storage
-advanced options
-shutdown
Choose
-wipe out data/restore the factory data
-wipe out cache
and
-upgrade your system from SD card (copy this ROOT ROM in your SD card, and choose it in this step http://dl.xda-developers.com/attach...832b60d/5192289d/1/9/6/1/1/6/8/rootforN52.zip)
LOOK LUCK

123sharon456 said:
1. Install driver
Check your device manager. If it looks like the image follows, it means your ADB driver does not been installed successful.
This is the successful status.
If you can't install ADB driver by automatic installation. You can install ZTE Join Me(mobile phone manager software), it will intall ADB.
2. Recovery
Extract it into any directory.
Click flashrecovery.cmd (antepenultimate) to this interface:
It will run automatically and reboot your phone. If not, reboot your phone and computer, then try again.
If everything is fine, try to enter the recovery.
Shutdown the phone, pressing on volume key by right hand + pressing on power key by left hand. When you see the screen light up and feel the vibration, release the power button. KEEP PRESS ON VOLUME KEY until you see the recovery interface.
-upgrade your system from SD card
-use slideload to upgrade your system
-wipe out data/restore the factory data
-wipe out cache
-backup and restore
-mount and storage
-advanced options
-shutdown
Choose
-wipe out data/restore the factory data
-wipe out cache
and
-upgrade your system from SD card (copy this ROOT ROM in your SD card, and choose it in this step http://dl.xda-developers.com/attach...832b60d/5192289d/1/9/6/1/1/6/8/rootforN52.zip)
LOOK LUCK
Click to expand...
Click to collapse
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not

Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
Dear Sharon,
The link is broken for the RootforN52
Can you please put a good link on it ?

shrewd supllice
Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
Im stucked at the Flashrecovery thing.
How do i open this adb folder, cause i dont have that one.
I have the ZTE Joinme installed, and now what?
Where do i find these recovery files, which i need to extract.
Please help me out, im kinda noobie in this stuff

Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
where can i download unofficial recovery for grand memo

visarya said:
where can i download unofficial recovery for grand memo
Click to expand...
Click to collapse
you can find it here:
needrom.com/mobile/zte-n5/[/url]
I cant set the full link cause i did not more then 10 posts

Good!
took weeks breaking my head up late at night from surfing the net to find some way to rooting this stunning smartphone. But I've been stuck due to no knowledge of ADB commands and of course having no Chinese idea, since supposedly there's an app that automatically Root the phone, but I can not make it work.
Having my disability, I share with you all the information and resources I've got to give you hope someone knows the correct usage.
And it is a shame that a HIGH terminal does not remove all power performance not ROOT and therefore can not set you GAPPS
Web Recovery 4.2.2 ROM and instructions: w w w needrom com/mobile/zte-n5/ (Requires registration, but I am uploading files to my Dropbox so it is not necessary)
* Chinese Subforum: w w w zhongxingfans com/forum-560-1.html (Registration is required, I can spend my MP user you're needed)
* Chinese Tutorial on previous subforum: w w w zhongxingfans com/thread-51487-1-1.html
* Other Chinese Subforum: w w w popfen com/forum.php?mod=forumdisplay&fid=65&filter=typeid&typeid=167 (Same as above, I have also user)
*Another one: www gaojiquan com/forum-ZTEN5-1.html (I'm not registered, I think)
* DropBox folder with everything I've coseguido, even assuming the mobile program that automatically Root: w w w dropbox com/sh/ap64zaexa5sa8op/we9TXWX
* Future tutorials: h t tp : // es.ready2root.com/info/grand-memo-n5 (Now is empty)
[/ LIST]
Hope you have better luck than me, and if they have some known to speak Chinese would be helpful to us.
NOTE: These is a google traducction from a another post from a spanish forum, if you have problems with the links, you can go to the original post here: www . htcmania . com/showthread.php?t=664705

Found this on a chinese website, its not for root, but for better performance of the ZTE N5 :laugh:
Just translate the page with Google Chrome standard translator, and you will understand.
(im still not able to set full links )
link for website:
h t t p ://sjbbs. zol .com.cn/164/642_1635239 .html
link for download:
h t t p://devicedownload .zte. com.cn/cn/UpLoadFiles/product/0/242/soft/2013052815114637 .zip
Im still having the issue that i cannot install GOOGLE PLAY, anyone here that solved that problem???
I appreciate your help
Greets,
Reppo1911

How did you install cwm on zte v9815 please?

CCR
Reppo1911 said:
Thanks A lot,
Im gonna try this, and will tell here about if it worked or not
Click to expand...
Click to collapse
Hello,
Is there some lock in EU phones whereas at the end of the aforementioned process the phone does shutdown and remains, the terminal is waiting for device..., rebooting in system recovery cwm is still missing and every sideload fails, any clue? People on the River would be Happy to give from a remote location.
hxxp://postimg.org/image/42tvojjvh/
ps: all I obtain is this->hxxp://postimg.org/image/blbyq6khf/332da320/
Freedom and Democracy shouldn't mean being jailed within some digital cell while paying for acquiring it: Amendments.

Can anyone give detailed directions?
I just got the device. I tried installing a google play store apk (tried a few different versions) all installed but none work.
How can I install the play store? Do I have to root the device? If so, are there detailed (English) instructions somewhere?

Someone knows if the Mobileuncle MTK Tools can root zte v5? I need to find a" one-click" app...

Partial success
I have installed the rom from needrom for the N5 android v 4.2.2. Took a while to flash the recovery, which is in chainese (driver issues). But still have serious connections issues:
The 3G network disconnects on restart and takes forever to reconnect. Wifi doesn't work! Built in keyboard is awful and also... chainese!
But it is rooted and has the google apps.
Does any one recommend a better combination of recovery and rom?
This is my wife's phone and she is having a lot of trouble with it.

Monsanto
yanay zimran said:
I have installed the rom from needrom for the N5 android v 4.2.2. Took a while to flash the recovery, which is in chainese (driver issues). But still have serious connections issues:
The 3G network disconnects on restart and takes forever to reconnect. Wifi doesn't work! Built in keyboard is awful and also... chainese!
But it is rooted and has the google apps.
Does any one recommend a better combination of recovery and rom?
This is my wife's phone and she is having a lot of trouble with it.
Click to expand...
Click to collapse
How do you flash a Custom rom we cannot even install cwm?
I wrote the Valorous Chinese told me to ask somebody elsee hence I sorry under God shall wish China a Genuine Bankruptcy for denying us Private Property, Communism is a mental disease our Lord should Treat. hxxp://en.wikipedia.org/wiki/Orange,_Vaucluse

How to?
JPWK said:
How do you flash a Custom rom we cannot even install cwm?
I wrote the Valorous Chinese told me to ask somebody elsee hence I sorry under God shall wish China a Genuine Bankruptcy for denying us Private Property, Communism is a mental disease our Lord should Treat. hxxp://en.wikipedia.org/wiki/Orange,_Vaucluse
Click to expand...
Click to collapse
I Followed downloaded the files from the dropbox posted upper in this thread. and followd the instructions in the previous page. Pay special attention to installing the driver for the divice. As soon as it reboots into bootloader it requires another driver.
Also if you must not restart the phone before flashing the rom otherwise it won't last.

perfect aarmewdd um in slack
yanay zimran said:
I Followed downloaded the files from the dropbox posted upper in this thread. and followd the instructions in the previous page. Pay special attention to installing the driver for the divice. As soon as it reboots into bootloader it requires another driver.
Also if you must not restart the phone before flashing the rom otherwise it won't last.
Click to expand...
Click to collapse
I am very Confident Folks bould ask ya about this driver thus they can rush downloading it like gold diggers to the root Saint Cloud very much
postimg.org/image/n6bj2rgyd/

[ Q&A Troubleshooting ] Dirty Unicorns 4.4.4 [Falcon]

[SIZE=+2]This thread has been created
for
• Questions • Answers • Troubleshooting •[/SIZE]​
[SIZE=+2]Dealing with ► Dirty Unicorns ◄ ► Moto G Falcon ◄[/SIZE]
[SIZE=+2]Please feel free to share issues, questions and offer help[/SIZE]
{
"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"
}
[SIZE="+2"]
>> [ROM] [OFFICIAL] Thread: >> Link Here <<[/SIZE]
.
[SIZE=+2]Please Do not clutter the Development thread with non related development chatter[/SIZE]
[SIZE=+2]
Please read the OP in dev thread carefully, it has some very important info in it.[/SIZE]
​
[SIZE="+1"]Please keep discussion focused, on the topic described in the OP[/SIZE]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​

[SIZE=+3]
Please provide ► exact Version and Date ◄ of ROM
Please provide ► exact Version and Date ◄ of Recovery
Please provide ► exact Version and Date ◄ of Kernel
[/SIZE]​
Repost:::
[SIZE="+2"]How to report bugs, the proper way ![/SIZE]
http://therealmofu.com/wp/?p=644
Credit:: by TheRealMofu
Credits:
Indirect for his guide
FuzzyMeep Two for his Windows Logcat Tool
[SIZE="+2"]
Connecting your device through adb on Windows/Ubuntu:[/SIZE]​
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼
[SIZE="+1"]Windows:[/SIZE]
On your PC you need to be logged in as an administrator for doin this and make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
Open the Windows command prompt, which you also can open through pressing Win + R on your keyboard
Now type:
Code:
cmd
Now change into the folder you installed adb, for example:
cd c:\adb
Now were we are in the correct folder, type:
Code:
adb
Now you see a lot of commands appering, and when done, type:
Code:
adb devices
and your phone (Device-ID) should be listed in there, that’s it
[SIZE="+1"]Ubuntu:[/SIZE]
Make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
In terminal type:
Code:
cd (TOOLS_PATH)/android-tools
Then issue the following:
Code:
./adb devices
That’s it
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
[SIZE="+2"]These are the options for reporting a bug:[/SIZE]​
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼
[SIZE="+1"]Section 1 | Logcat:[/SIZE]
This log should almost always be included just because it provides more info than just saying something doesn’t work. It will essentially tell you which apps are crashing and why and it also gives output of what they’re doing. (Your system is running through apps, the dialer, wireless radio’s, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don’t feel like writing a ‘how to use adb’ tutorial for everyone’s phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to
http://pastebin.com/
http://logcat.us/
http://paste.ubuntu.com/
and provide the link in the thread/post.
It’s really that simple!
For Windows users i found an self explaining noob friendly program called Windows Logcat tool 4.0
[SIZE="+1"]Section 2 | Dmesg:[/SIZE]
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go “OH F***” when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like “What driver is the kernel loading {or not loading for that matter}” and similar things. This is linux, so kernel output is important if a hardware aspect isn’t working right.
How to get a dmesg:
This is simple as well, no matter what operating system you’re on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
[SIZE="+1"]Section 3 | last_kmsg:[/SIZE]
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what’s going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can’t. It doesn’t mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it’s trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
[SIZE="+2"]Here is another great instruction tutorial link:[/SIZE]
[SIZE="+2"][WIN][TUTORIAL]HOW TO USE ADB,DDMS AND TAKE A LOGCAT {pictorial explanation} [/SIZE]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​

It's been noticed that sometimes during the install of this it will take a long time to flash.
Just be aware of this known issue
It happens during the format /system of the device
it happens even on the current newest TWRP 2.8.0.1 or twrp-2.8.0.1-xt1032.zip
and sometimes it even happens if you have manually formatted /system in advanced mode
Normal install time ranges from :30 seconds to 1:00 Minute
longer times have ranged with older TWRP recoveries or CWM or Phil's anywhere from 3:00 minutes to 10:00 Minutes
TeamMex has reported that is is most likely an updater-binary issue
reversegear has tested and posted a workaround for those wishing to mod their copy of the ROM
or you can choose to wait out the extra time needed to install this awesome ROM.

one more to hold

Just wanted to say THANK YOU @hhp_211 for creating this thread so that the development thread could possibly level out and get back to where it original was headed

I get the first question. I finally decided to try this out. I'm using the latest official version of CWM; 6.0.4.7 touch. I can report that it did take maybe 5 min to flash the ROM from start to finish. After the first boot, i rebooted to recovery and I then flashed the GAPPs, DU_TBO_GAPPS. I noticed that upon reboot, and signing into my Google account, that the ROM didn't automagically start downloading all my apps from the play store. Is there a setting that I needed to have set?
I went ahead and restored my backup for the time being. The ROM looked nice and smooth.
Thank you.
Sent from my XT1034 using Tapatalk

alfick3 said:
I get the first question. I finally decided to try this out. I'm using the latest official version of CWM; 6.0.4.7 touch. I can report that it did take maybe 5 min to flash the ROM from start to finish. After the first boot, i rebooted to recovery and I then flashed the GAPPs, DU_TBO_GAPPS. I noticed that upon reboot, and signing into my Google account, that the ROM didn't automagically start downloading all my apps from the play store. Is there a setting that I needed to have set?
I went ahead and restored my backup for the time being. The ROM looked nice and smooth.
Thank you.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I believe that is a modded apk to be that way
to change go to
Play Store::Settings::Auto-update apps::
and choose your preferred method

@hhp_211, thanks. I didn't think about going into the play store and looking at the settings. I'm used to other GAPPs packages where it just automatically installs my apps from previous ROMs or phones.
Sent from my XT1034 using Tapatalk

I re-installed today, after flashing the latest TWRP (2.8.0.1). I wiped system, data, cache and dalvik cache. I did not wipe my internal SD card. This time I flashed the ROM, then flashed the GAPPs right away instead of booting into the ROM first. Upon reboot, it asked me to sign into my Google account, and then automagically started to download my apps. So far, so good; although it's constantly giving me a "Unfortunately, OmniSwitch has stopped". After all my apps have downloaded, I'll do a reboot and see.

Is it possible to have FM radio app? Zip? Or it is completely unsupported? I'd rather not to buy a third party app.
Thanks in advance

i have a problem with the BACK soft button in landscape, whenever i press it (and in landscape) it goes to "google now"
i dont know what causes this issue right now (it may be the Recents bttn ... i use inverted bttns)
The problem seems to be that the part avobe of the "home" button black part is for some reason usable??
its kind of wierd but right now i cant go "Back" in landscape because it goes to google now !
im on dirty 8.0 the last one Stock

Mao_anguita said:
i have a problem with the BACK soft button in landscape, whenever i press it (and in landscape) it goes to "google now"
i dont know what causes this issue right now (it may be the Recents bttn ... i use inverted bttns)
The problem seems to be that the part avobe of the "home" button black part is for some reason usable??
its kind of wierd but right now i cant go "Back" in landscape because it goes to google now !
im on dirty 8.0 the last one Stock
Click to expand...
Click to collapse
I'd say grab a Logcat
Maybe also include some screenshots of your layout in landscape
I'm still on the test 8.0 and back works OK,, but i also don't use Google now
.

[ROM][5.1.1_r12][p6200/p6210/t869](27Sep2015OmniROM-Homemade

{
"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"
}
This is an experimental build of the open ROM Omni5.1 for our Samsung GalaxyTab Plus.
Get the media patch for the 20150819 build in the 7.7 thread.
Detail can be found in 7.7 thread
Before you post, read the 7.7 thread first!
*** Post with no detail will be ignored ***
Know issues:
Now is in an early stage. Read carefully before flashing.
1. Wifi direct not fully working
2. May be more....
Downloads: :highfive:
AFH: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=28293
d-h.st: http://d-h.st/users/danielhk/?fld_id=44273#files
mirror: 百度网盘
Use the latest Delta gapps: http://forum.xda-developers.com/showthread.php?t=2997368
** Latest TWRP (2.8.6.x or above) is required.
Omni is not rooted. To root, flash the latest SuperSU-24x.zip in recovery.
Credits: :good:
** The OmniROM team who have such a good idea and their hardworks
** All those who donate to me. Giving me the resources to upgrade my PC and accessories!
** All those who help our cool tab's developments!
Donations:

OMG.i'm such an idiot.roll out and i saw the twpr 2.8.6.0.I wasn' t see that before.flashing succes.Every thing work smoth and fast.
Main problem until now:
1.Brightness slide broke->soluion is download this app and disable "Automatic Brightness" https://play.google.com/store/apps/details?id=net.ailuro.android.settings.screen.brightness
2.Wifi passw clear LOL ~
3.Setting interface xxx
4.Unable to use Simcard
5.HW video notwork.BUT- you can try UC Browser for online video(Fb,youtube,...) like an option https://play.google.com/store/apps/details?id=com.UCMobile.intl .Not done yet,you need to restore the flash cache from 4.4 in titanium backup from the link below,other wise ,it don't work.
6.Can't upload file!
7.I don't see any problem left with reboot.app and system.I'm a BIG dump dump when forget to check update twpr ...what a shame (='.'=)
*.Root: http://download.chainfire.eu/supersu

Trung Gs said:
In TWPR ,after wipe,Omni(27mar2015) p6200 build and gapps5.1 is flashing succes.But,when i reboot system,the screen is black and my tab can't boot into homescreen.I try again with only rom,it still the same problem.It 's hard to say when i have try every way i know. what a shame ≧﹏≦. I hope u can't find out what problem with this build from other people too or the error come from my mistake.
Click to expand...
Click to collapse
Guess might be your tab............works for me. just perform a wipe, reboot the back into recovery and wipe once more.
Install rom, wipe and install rom again.
Reboot and see if it works for you. (can flash gapps later and super su if u need)

Can't access download link
Its weird! AFH says I dont have access to file, Dev-Host just direct me to their homepage, and mirror link is in chinese so I dont have any idea what buttons to hit. Is it just me? Anyone here who can guide me how to download the file?

omike123 said:
Its weird! AFH says I dont have access to file, Dev-Host just direct me to their homepage, and mirror link is in chinese so I dont have any idea what buttons to hit. Is it just me? Anyone here who can guide me how to download the file?
Click to expand...
Click to collapse
Edit 1:
Downloading now! Using google chrome I was able to translate mirror link page to English.
Edit 2:
Successfully flash the Rom via TWRP 2.8.6.0
As mentioned in the OP
- quicksettings pulldown can only be pulled once.
- adjusting brightness slider do nothing
- torch is working
- system apps seems to load faster than cm12.
One thing that caught up my attention is that simcard is not recognized. Have to goto settings/about tablet and found out that baseband version is unknown. Shame cause I really think this rom is more fluid compare to cm12.
I was unable to test user's app due to simcard unavailability, hence 3G as well, as I heavily dependent on it.
Also noticed that 1st & 2nd boot is ok but on 3rd boot is only showing blank screen ( omni bootlogo not showing ) have to longpress power button a couple of times until omni bootscreen appears.. P6200 user here.

Thanks again to this ROM, pretty much stable , no soft reboots. Battery is good, Minor issues i could see.
Video playback is still an issue i believe, even in YouTube.
Thanks again

If this rom could see the daylight I will really love it. It's much better than cm12 . Aside the baseband issue in p6200 really would have preferred this .
Sent from my GT-P6200 using xda Forums PRO

Have just installed latest version 20150518. Installation process without any problem. System is running stable.:good:
But SIM-card is not found. Tried several times.
It's no problem with CM12.1 rom. So I'm back to CM12.1.

uli-hh said:
Have just installed latest version 20150518. Installation process without any problem. System is running stable.:good:
But SIM-card is not found. Tried several times.
It's no problem with CM12.1 rom. So I'm back to CM12.1.
Click to expand...
Click to collapse
So unknown baseband issue has'nt been fix yet?

omike123 said:
So unknown baseband issue has'nt been fix yet?
Click to expand...
Click to collapse
That's what it shows in settings/about phone

uli-hh said:
That's what it shows in settings/about phone
Click to expand...
Click to collapse
Well I guess I'll just have to wait for the next release. I'm sure @daniel_hk would fix this in future updates.

omike123 said:
Well I guess I'll just have to wait for the next release. I'm sure @daniel_hk would fix this in future updates.
Click to expand...
Click to collapse
I don't have problem showing the baseband with or without a sim card. Don't know why some p6200 can't. It's the same modem chip and I'm using the same lib for both too.
Clean flash, Wait for a few minutes, etc.
Can anyone confirm that?
If really can't, in a terminal emulator type:
su (already rooted of course)
rild
see if any error message

here is the result:
WARNING: linker: libsec-ril.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
rm: /data/misc/radio/dlink: permission denied
it is also showing invalid IMEI and unknown baseband version.

PugeAko said:
here is the result:
WARNING: linker: libsec-ril.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
rm: /data/misc/radio/dlink: permission denied
it is also showing invalid IMEI and unknown baseband version.
Click to expand...
Click to collapse
The first one is just a warning because of the only old blob we have.
The second line means the daemon is not start. I'll look into it but I need someone with a p6200 to test for me.

daniel_hk said:
The first one is just a warning because of the only old blob we have.
The second line means the daemon is not start. I'll look into it but I need someone with a p6200 to test for me.
Click to expand...
Click to collapse
Willing to do that.

edwin270 said:
Willing to do that.
Click to expand...
Click to collapse
I think I found the reason. There is a file missing. View attachment libsecril-client.zip
unzip the above zip will get the file libsecril-client.so. Copy the file to /system/lib with a root browser (eg. ES FileExplorer) will do.
Hoping it work for t869 too. t869 owners are welcome to test too.
Good luck!
PS. Will include it in the next build

daniel_hk said:
I think I found the reason. There is a file missing. View attachment 3324813
unzip the above zip will get the file libsecril-client.so. Copy the file to /system/lib with a root browser (eg. ES FileExplorer) will do.
Hoping it work for t869 too. t869 owners are welcome to test too.
Good luck!
Click to expand...
Click to collapse
Was about to try that and alert you. Compared the lib folder for cm12.1 to that of omni and Realized the same missing libsecril-client.so and a couple of others. Looks like you got to it first. Anyway thinking of creating a flashable package for it. [emoji4] [emoji4] [emoji4]

OTG -Wifi???
@daniel_hk This may be stupid but i have to ask u.Does this kernel support USB Wifi with OTG?

Tried the lib files provided and a couple of others from cm12.1...................same old. Installed CM12.1 again and tried the rild check and got the same error as mentioned by PugeAko , though baseband is working with that rom.
Will be pulling the lib from stock MF1 rom for our dear p6200 soon, to see what comes of it.
Will post my findings soon.
Edit:
Checked radio directory in cm12.1 vrs OMni and some files are missing in Omni. Pulled that from cm12.1 but this constant black screen booting of Omni is making me frustrated at the moment. Too much black screen. Trying to see if I can get a boot.
Edit2:
Giving up. Don't know what it is but cannot endure this constant black screen any longer and time is not a luxury that I can afford now, its preventing me from helping figure out how to fix this baseband issue. Going back to the buggy cm12.1 rom. This rom is promising though.

Trung Gs said:
@daniel_hk This may be stupid but i have to ask u.Does this kernel support USB Wifi with OTG?
Click to expand...
Click to collapse
Each USB Wifi probably have different chips which requires drives supplied by the manufacture. For it to work, it requires HAL drivers/firmwares too. Normally there is a CD or place to download. Window might have some driver for a few chips. Linux (Android) would be another story.
Normally, a kernel would only have the drivers for the on board chips.
edwin270 said:
Tried the lib files provided and a couple of others from cm12.1...................same old. Installed CM12.1 again and tried the rild check and got the same error as mentioned by PugeAko , though baseband is working with that rom.
Will be pulling the lib from stock MF1 rom for our dear p6200 soon, to see what comes of it.
Will post my findings soon.
Edit:
Checked radio directory in cm12.1 vrs OMni and some files are missing in Omni. Pulled that from cm12.1 but this constant black screen booting of Omni is making me frustrated at the moment. Too much black screen. Trying to see if I can get a boot.
Edit2:
Giving up. Don't know what it is but cannot endure this constant black screen any longer and time is not a luxury that I can afford now, its preventing me from helping figure out how to fix this baseband issue. Going back to the buggy cm12.1 rom. This rom is promising though.
Click to expand...
Click to collapse
cm12.1 is probably the wrong place to try. Omin for p6800 would be the wiser choice.
Anyway, I will try to get it work on the next build.