Related
I know this has been posted but since it was long ago and *nobody replied*, here it is:
There are no FULL rom for the 4.0US. Of course you can use the bootloaders from the international version and the factory image that has been posted here, but both don't go without issues. The only stock image we have is the kernel from package2.3.5.
So to fix those issues, I am asking if one of you with stock rom could be so kind as to post a factory.rfs file and (this is including everybody) the other files (sbl, param, boot etc)
I don't think it matters if it is rooted or not (factory.rfs), I am looking at something that is *fully* functional. I'll provide you with tutorials, just ask for it
Thank you!
I'll be happy to post it but where do I look for the files so I can post it. And fyi I am running root stock atm
Sent from my YP-G70 using xda premium
Ben456 said:
I know this has been posted but since it was long ago and *nobody replied*, here it is:
There are no FULL rom for the 4.0US. Of course you can use the bootloaders from the international version and the factory image that has been posted here, but both don't go without issues. The only stock image we have is the kernel from package2.3.5.
So to fix those issues, I am asking if one of you with stock rom could be so kind as to post a factory.rfs file and (this is including everybody) the other files (sbl, param, boot etc)
I don't think it matters if it is rooted or not (factory.rfs), I am looking at something that is *fully* functional. I'll provide you with tutorials, just ask for it
Thank you!
Click to expand...
Click to collapse
You have a US YP-G1 no? You can make a dump of your partitions to make a recovery solution!
Ok, first, I was wrong, you have to be rooted. Then, either from adb from your computer or from a terminal emulator in your device, you have to type:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
No personal data is on this backup. This file can be flashed with heimdall so you can stop there or if you have linux, you can make a tar+md5 file to flash wth odin:
tar -H ustar -c factoryfs.rfs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
if you don't have linux, just post factoryfs.rfs and i'll make it to a tar file.
Note: There may be other ways to do a an image without being rooted, I'll check if you are not rooted.
A HUGE THANKS!!
You have a US YP-G1 no? You can make a dump of your partitions to make a recovery solution!
Click to expand...
Click to collapse
No I can't since I have flashed my device with package2.3.5.tar that was posted here some time ago, which is the only working image we have to date, but there are some issues with this. I also can't post my boot loaders since I have flashed them with the international version. They work, but I can't enter recovery mode or download mode without a jig or access to an adb shell. All those flashes were made in the process of unbricking my device.
Hi Ben,
I had made a backup of my ROM before trying to install Steve's kernel. I used the same 'dd' command you mention in your instructions. The kernel install went OK, but when I ran CWM backup, I got into a boot loop and had to restore to the package_us2.3.5.tar.md5 that's been circulated around. This was a few weeks ago.
I've tried using the steps to run tar and md5sum on two separate Linux installs using my backup and have created what appears to be a valid .tar.md5 file, according to ODIN. But when I try to flash the .tar.md5 file, it passes MD5 checksum OK, ODIN reports NAND write start, but then fails immediately and I'm left with having to reflash package_us2.3.5.tar.md5 to get it to work again. Looking at my factory.rfs binary and comparing it to the factory.rfs in package_us2.3.5.tar.md5 seems to indicate that it's mostly similar, but there are binary differences. Headers look similar though.
So I'm not sure what I've done wrong in either (a) creating the backup image, or (b) creating the .tar.md5 file, or (c) flashing the .tar.md5 file. But the net result is that it won't flash successfully. So I don't think sharing my factory.rfs as it is will help you.
Here are some tips that my help troubleshoot issues.
1. The MD5 sum part is not neccessary, you can just put the factoryfs.rfs in a tarball and flash it.
2. You can loop mount a factoryfs.rfs in linux by creating an empty dir and running "mount -o loop -t auto factoryfs.rfs empty_dir"
3. It should be possible to reverse the dd command to restore the partition. ie "dd if=/sdcard/factoryfs.rfs of=/dev/block/stl9 bs=4096" (if I were going to do this I would use adb in recovery mode and root is required )
4. If you have a CWM backup, you should be able to to pull files out of the backup if you need to restore files manually. Files should be located on external sdcard in "clockworkmod/backup/"somedatestuff"/system.rfs.tar
It seems to me that what Ben456 wrote up there should have worked. Hope this helps.
I just learned how to dump my factoryfs.rfs file. This is dumped from my brand new Samsung Galaxy Player 4.0 (YP-G1CWY/XAA) right after I opened it from the box. It should be 100% clean.
I uploaded it here. Let me know if it works.
http://www.sendspace.com/file/6fzfdg
Here is the recovery rom I just uploaded. I really hope this works.
http://www.sendspace.com/file/1y2ogi
I created a thread for it here.
Hi everyone,
I made this guide for users of a Galaxy Player 4.0 USA or INTL who want to get backups of every partition in case they completely brick their device. This will be very useful if you have somehow screwed up your partitions beyond just /system, which is what most ROMs only include. It even backs up /efs, which contains the serial numbers unique to every player and other things that even complete restore ROMs and nandroid backups don't include. It's also good to just have a backup of your partitions stored somewhere safe, because you never know when you might need them. Also, if you're reverting from CM7 (the second release or later) you will need to use this with a PIT file because CM7 uses MTD partitions. Basically, flashing this backup will allow you to completely return to how your device was before, including all your personal data and apps. Hopefully soon we'll begin to have less "bricked my player help" threads clogging up the General (and sometimes Dev) sections. Enjoy
This backup does not back up bootloaders, which can increase your chances of a hard-brick and are almost never needed. Also, this is for the YP-G1 / Player 4.0 USA or INTL only, not for 5.0 users.
Disclaimer: I am not responsible for your device if anything happens blah blah blah
*Pre-requisites*
- Rooted device or ROM
- Busybox (Most rooted ROMs have this, but you can still download Busybox Installer from the Play Store and update to the latest busybox version just to make sure)
- ADB properly set up
- Some space on your internal SD card (about 1-2 GBs should be fine)
- Player set to "USB Debugging Mode" found in Settings
Alright, let's begin. First we will need to make a dump of every partition on the device. However, dumping the PIT is not needed because Adamoutler has a thread with a master list of PITs. Open a Command Prompt (or Terminal if you're using Linux), make sure your device is connected and type:
Code:
adb remount
adb shell
su
Now, to back up EFS:
Code:
dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096
PARAM
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
KERNEL
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
SYSTEM
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
DBDATA
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
CACHE
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
DATA (Optional if you want your apps)
Code:
tar -czvf /sdcard/data.tar.gz /data
You can exit out of the current window and open a new one once all the processes above are completed.
Now to pull all of the backups to your computer:
Code:
adb remount
adb pull /sdcard/efs.rfs
adb pull /sdcard/param.lfs
adb pull /sdcard/zImage
adb pull /sdcard/factoryfs.rfs
adb pull /sdcard/dbdata.rfs
adb pull /sdcard/cache.rfs
adb pull /sdcard/data.tar.gz
I recommend keeping these files in a safe place on your hard drive for when you need to use them. Feel free to delete them from your player now to save space.
How to Flash
First grab the correct PIT for your device here
For Heimdall, just load the PIT, click "Re-Partition", and select the correct files for each partition. Then click flash.
For ODIN, you have to tar the files together first.
Using Cygwin or Terminal, browse to the directory where all your backup files are. Then, type in:
Code:
tar -H ustar -c efs.rfs param.lfs zImage factoryfs.rfs dbdata.rfs cache.rfs > backup_package.tar
Now load the PIT, click "Re-Partition", and under the PDA section browse to your backup_package.tar (or whatever you named it to). Click flash.
After it is done flashing, here's how to restore your apps. Open Terminal or Command Prompt to the directory of data.tar.gz on your computer:
Code:
adb remount
adb push data.tar.gz /sdcard/
adb shell su -c "tar -zxvf /sdcard/data.tar.gz"
And you're done! If all goes well you should have completely restored your device, with a perfectly safe method and no bootloaders! I hope that this will be helpful to people.
Reserved for future use....
I did this, and i believe that AdamOutlers .pit is what messed up my device. Can you please give me a copy of your or another copy?
Tcollins412 said:
I did this, and i believe that AdamOutlers .pit is what messed up my device. Can you please give me a copy of your or another copy?
Click to expand...
Click to collapse
AdamOutler's pit is not messed up... I used it to repartition my player and it worked perfectly with the right partitions.
Sent using Tapatalk
when i tried it, it messed up my player. do you know how i could fix it?
Hey klin1344, not sure if you still watch this thread, but I was wondering if anyone has had success using heimdall 1.3.2 with the 4.0? I see it says it broke compatibility with some devices.
iJimaniac said:
Hey klin1344, not sure if you still watch this thread, but I was wondering if anyone has had success using heimdall 1.3.2 with the 4.0? I see it says it broke compatibility with some devices.
Click to expand...
Click to collapse
No problem for me
i wanted to use this method to backup my /efs (like daniel advicd me to do ) but i cant seem to do it. It says Can't open 'sdcard/efs.rfs': Read only file system
pls answer
crancpiti said:
i wanted to use this method to backup my /efs (like daniel advicd me to do ) but i cant seem to do it. It says Can't open 'sdcard/efs.rfs': Read only file system
pls answer
Click to expand...
Click to collapse
You have to be rooted to do this.
Sent from my A500 using xda app-developers app
klin1344 said:
You have to be rooted to do this.
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
i think either i hadnt BuSY box installed(my device was rooted before) or it was bcause i connected my device to the PC / i mounted my sdcards
now i have a efs.rfs file and that should do it i hope
thanks . i have problem with heimdall to download my wifi 4 int PIt file
is there any ADB command for downloading pit file from device?
aminking2005 said:
thanks . i have problem with heimdall to download my wifi 4 int PIt file
is there any ADB command for downloading pit file from device?
Click to expand...
Click to collapse
I do remember that there is the dd command from the adb shell in order to get your pit, but it's not the recommended way to get it.
You can download the pit files right here:
http://forum.xda-developers.com/showthread.php?t=1531850
zaclimon said:
I do remember that there is the dd command from the adb shell in order to get your pit, but it's not the recommended way to get it.
You can download the pit files right here:
http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
most pit file are represented for wifi4 8GB . but mine is 16GB.
so im not sure about pit files in forum.
if i install a custom rom and it faild can i recover my yp-g1 by having above backups?
aminking2005 said:
most pit file are represented for wifi4 8GB . but mine is 16GB.
so im not sure about pit files in forum.
if i install a custom rom and it faild can i recover my yp-g1 by having above backups?
Click to expand...
Click to collapse
Sorry for the long reply time, and yeah you should be able to restore with those backups.
Envoyé de mon Nexus 4 en utilisant Tapatalk
Flashing is never 100% safe, use at your own risk.
Backup before flashing!
Make sure your battery is charged!
For US version (YP-GI1CB) use the ROMs from alice90's thread
You might want to use sha1sum or md5sums to check download integrity, and 7zip to unpack archives.
Archive password is: xda-devs
These ROMs can be flashed using Odin3. If you want to use Heimdall (v1.3.2 reported not working with SGP4.2, use v1.3.1) you will need to extract the .img files from the archives. Use stock ROMs if you want to revert back to original state.
/!\ These ROMs are for YP-GI1CW/XEF. If you have another YP-GI1CW model you need to backup your wifi files before flashing and restore them later. You can refer to Backup /system/etc/wifi or Flash kernel (not recommended) or read the procedure in the HOWTO below.
ROOTED ROM
Description: this is the stock ROM with only 1 file added, /system/bin/su which was taken from TinySU (Note: doesn't spawn any popup when giving root through Superuser.apk)
SHA1: 2e27472345a40a8bfd4cba7f13bc1846ceba2800
MD5: 73288ed29eb8c4711b34e682a39682f3
STOCK ROM
Description: stock ROM, flash this if you want to revert back to out-of-the-box state
SHA1: 70eb347c5d8c0c877e7d069d30ac54bd1673d41a
MD5: 71a9880e88e6f513b4e9665542cbeaa3
STOCK KERNEL
Description: don't flash this unless you really need it; your bootlogo will be forever replaced by SGS2 logo, and your device will be watermarked, which will void your warranty
SHA1: 1bc402d990963c973957ef71e80e1a6dede4d1ae
MD5: 5b6be70d941c31aadfdb8d4a11db2800
Greets: Rebellos alice90 Baruch6132 zaclimon Entropy512 baladev helicopter88 ChrisFR and all the people from #xda-devs that supported me
HOW TO USE
Before anything you will have to install Samsung drivers, either with Kies from Samsung website, or using zadig (recommended)
I. Backup /system
Many different YP-GI1CW models exist with different letters at the end; I dumped these ROMs using YP-GI1CW/XEF and hence, if you have the same model but different letters at the end, you will probably not be able to use wifi after flashing. The workaround for this is to backup your original wifi files before flashing, and restore them later. If you own the very same model (YP-GI1CW/XEF) this step may be skipped, but it's safe to do it anyway:
- download & install AndroidSDK. It's a huge package with many tools, such as ADB (there's probably a light, stand-alone ADB somewhere; post if you have some info about this)
- unplug device from USB then put your device in USB debugging mode (Settings > Applications > Development > USB Debugging) then re-plug device.
- change active directory to where you installed AndroidSDK or ADB, on a windows system I would press Win+R then type cmd to open a console, and then in the console:
Code:
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
- make sure your device is detected
Code:
adb devices
Should show your device serial number and status. If you don't see them, check if: you have the correct drivers / USB Debugging is enabled / USB cable properly connected
- backup your /system directory
Code:
mkdir sysbkup
cd sysbkup
..\adb pull /system
You will probably get some errors and that's normal, as you can't pull all files without root. Make sure the files are actually copied on your computer (with my device it's approx. 473MB).
- keep track of the original file permissions so you can restore them later
Code:
adb shell
$ ls -l /system/etc/wifi
-rw-r--r-- root root 274168 2012-03-17 10:05 firmware.bin
drwxr-xr-x root root 2012-03-17 10:05 softap
-rw-r--r-- root root 16295 2012-03-17 10:05 tiwlan.ini
-rw-r--r-- root root 16986 2012-03-17 10:05 tiwlan_cert.ini
-rw-r--r-- root root 883428 2012-03-17 10:05 tiwlan_drv.ko
-rw-r--r-- root root 16985 2012-03-17 10:05 tiwlan_plt.ini
-rw-r--r-- root root 1012 2012-03-17 10:05 wifi.conf
-rw-r--r-- root root 134 2012-03-17 10:05 wpa_supplicant.conf
$ ls -l /system/etc/wifi/softap
-rw-r--r-- root root 262356 2012-03-17 10:05 ap_firmware.bin
-rw-r--r-- root root 652 2012-03-17 10:05 hostapd.conf
-rw-r--r-- root root 954932 2012-03-17 10:05 tiap_drv.ko
-rw-r--r-- root root 22424 2012-03-17 10:05 tiwlan_ap.ini
Save what you see in some TXT file for later reference (will be needed in section III).
II. Flashing with Odin3 on Windows
1. Make sure the ROM you intend to flash was made exclusively for your device
2. Double-check (for Samsung Galaxy Player 4.2: open your device's cover, lift the battery; the model appears behind it)
3. Download & run Odin3 (tested v1.85 and v3.04 so far, both worked fine), click PDA and choose the .tar (or .tar.md5) file you want to flash (most likely, the "Rooted factoryfs" ROM).
4. Put your device in download-mode:
- unplug USB cable
- shut your device down (remove and reseat battery if its stuck somehow)
- press HOME (physical button bottom center), keep it pressed
- press VolumeDown, keep it pressed
- press Power, keep it pressed
- wait until the download-mode confirmation screen shows up
- release VolumeDown first, then the rest of buttons
- connect your PC to your device using USB cable
- press VolumeUp one to finally make your device turn into download-mode
=> this should make Odin3 react, and tell you "Added" in the bottom-left window, while adding something like <COM#> in the first box
Be careful: some user report having troubles with USB3 ports. I would recommend properly powered USB2 ports only. Avoid USB hubs, avoid USB1 and USB3.
5. Make sure to UNCHECK repartition. You can also uncheck the "F Reset Time" and "Auto reboot" but they're harmless. The only box that needs to be checked is PDA, along with the ROM file you're about to flash.
6. To flash your device, click start, the process should take less than 2 minutes.
If Odin3 stops at "Setup connection" this means the device has timed out (happened to me all the time); just retry and click "Start" faster after plugging USB
III. If Wifi doesn't work, restore wifi files saved in section I
Go to your ADB folder in console (refer to secion I), just under the directory containing backup
Code:
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Copy the the files you need on /sdcard/
Code:
adb push sysbkup/etc/wifi /sdcard/wifibkup
Then open a shell on your device, replace wifi files and set permissions (Note: I use 644 and 755 because that's what I had in section I, you should replace them with the permissions you had)
Code:
adb shell
$ su
# mount -o remount,rw /system /system
# cd /sdcard/wifibkup
# for i in *; do dd if=$i of=/system/etc/wifi/$i; done
# cd softap
# for i in *; do dd if=$i of=/system/etc/wifi/softap/$i; done
# cd /system/etc/wifi
# chown root.root *
# chmod 644 *
# chmod 755 softap
# cd softap
# chown root.root *
# chmod 644 *
# sync
Reboot, and you're done!
bluk
[EDIT: the following method does only work on Android 4.0 and above, I keep it here for reference only]
Many solutions exist for backup, I read many times about Titanium backup doing excellent job as well as ClockworkMod but they both need root IIRC. BackMeUp claims to perform backups without root on Android 2.1 and more, no idea to which degree this is true.
Without root, it's possible to make backups using ADB (Android Debug Bridge) which basically is the swissknife for Android devices; it gives you a linux shell on your device, backup/restore ability and more.
1. Download & install AndroidSDK. It's a huge package with many tools (such as ADB); there's probably a stand-alone ADB somewhere if you don't want to go the AndroidSDK way.
2. Unplug device from USB then put your device in USB debugging mode (Settings > Applications > Development > USB Debugging) then re-plug device.
3. Now it's time to create a backup file which I will call C:\MyBackup for the sake of example.
- open a shell
press Win+R and type in cmd
- change active directory to where you installed AndroidSDK or ADB, on my system I type
Code:
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
- at this point, if you need to CREATE backup file, type:
Code:
adb backup -apk -shared -all -f C:\MyBackup
- but instead, if you need to RESTORE a previously created backup, type:
Code:
adb restore C:\MyBackup
zebluk said:
Flashing is never 100% safe, use at your own risk.
Backup before flashing!
A version for US devices (YP-GI1CB) is about to be made, just be patient folks, should be a matter of days!
These ROMs can be flashed using Odin3. If you want to use Heimdall you will need to extract the .img files from the archives. Use stock ROMs if you want to revert back to original state.
Stock factoryfs
Stock kernel (the original logo will be lost, and your device will be watermarked)
Rooted factoryfs
The rooted ROM is minimal. It just adds /system/bin/su to the stock factoryfs and nothing more. That should be enough for anything tho
This version of su (TinySU) doesn't spawn any popup when giving root thru Superuser.apk, feel free to replace it with the version you like.
Greets: Rebellos alice90 Baruch6132 zaclimon Entropy512 helicopter88 ChrisFR and all the people from #xda-devs that supported me
Click to expand...
Click to collapse
Congrats on this!! Now the 4.2 users can finally get their players rooted.
zebluk said:
Flashing is never 100% safe, use at your own risk.
Backup before flashing!
For US version (YP-GI1CB) go HERE
These ROMs can be flashed using Odin3. If you want to use Heimdall you will need to extract the .img files from the archives. Use stock ROMs if you want to revert back to original state.
Stock factoryfs
Stock kernel (the original logo will be lost, and your device will be watermarked)
Rooted factoryfs
The rooted ROM is minimal. It just adds /system/bin/su to the stock factoryfs and nothing more. That should be enough for anything tho
This version of su (TinySU) doesn't spawn any popup when giving root thru Superuser.apk, feel free to replace it with the version you like.
Greets: Rebellos alice90 Baruch6132 zaclimon Entropy512 baladev helicopter88 ChrisFR and all the people from #xda-devs that supported me
Click to expand...
Click to collapse
Is there a step-by-step procedure to do this for complete noobs like me? I don't know how to backup and root since it is my first Android device and I just don't want to brick it if I miss a step. Thank you very much for this.
Would appreciate a full guide as well. Though it seems pretty straightforward, I wouldn't want to make an elementary mistake or one specific to this device.
Also, I'm curious whether full functionality will be present in translating over to a different launcher.
Thanks a ton for the great work to all involved (and great timing in getting it out a week after I got my hands on the 4.2)!
Sent from my YP-GI1 using xda premium
Ok, added a HOWTO for Windows users, I hope that helps.
@Consumers: I'm not sure what do you mean by "translating over to a different launcher", maybe you're talking about CWM? Anyway unless you hardbrick your device, you should be able to restore it to stock (even from the exclamation mark screen which is in fact another download-mode), just be safe and do backups when you're in doubt!
For now I don't plan on doing other updates. Now the stock ROM is dumped & rooted, I'll let the modders take it from here, if they feel like it
bluk
zebluk said:
Ok, added a HOWTO for Windows users, I hope that helps.
@Consumers: I'm not sure what do you mean by "translating over to a different launcher", maybe you're talking about CWM? Anyway unless you hardbrick your device, you should be able to restore it to stock (even from the exclamation mark screen which is in fact another download-mode), just be safe and do backups when you're in doubt!
For now I don't plan on doing other updates. Now the stock ROM is dumped & rooted, I'll let the modders take it from here, if they feel like it
bluk
Click to expand...
Click to collapse
Thanks for the how to. However, the link to the rooted factoryfs is down. Could you please reupload it? Maybe with another file hosting site like Mediafire or through torrent maybe? Thank you very much.
galaxyplayer4.2 said:
Thanks for the how to. However, the link to the rooted factoryfs is down. Could you please reupload it? Maybe with another file hosting site like Mediafire or through torrent maybe? Thank you very much.
Click to expand...
Click to collapse
Thanks for notifying me; reuploading
bluk
Odin seems to flash successfully, but after restarting, root-only programs like Root Browser and ROM Browser still say that it appears that I'm not rooted. I tried flashing twice, both with no problems, and still nothing. Any ideas?
EDIT: Never mind! SuperSU simply wasn't granting access or prompting me to grant access to the apps. Thank you very much for your work, zebluk! Very helpful guide too.
Consumers said:
Odin seems to flash successfully, but after restarting, root-only programs like Root Browser and ROM Browser still say that it appears that I'm not rooted. I tried flashing twice, both with no problems, and still nothing. Any ideas?
Click to expand...
Click to collapse
Install Superuser I didn't include it to keep changes minimal.
Make sure you have rooted device issuing "adb shell" at prompt, then type "su". If you see sharp sign "#" you have root.
bluk
EDIT: looks like you got it at the very same time I was answering enjoy
Hi guys, just a litte thing: the mentioned backup process (adb) doesnt work on Android 2.3.6. Think its 4.0 above ...
Nevertheless, great we got root now
joeblack_2k2 said:
Hi guys, just a litte thing: the mentioned backup process (adb) doesnt work on Android 2.3.6. Think its 4.0 above ...
Nevertheless, great we got root now
Click to expand...
Click to collapse
Thanks for pointing that out, unfortunately seems there are no decent ways of backing up unrooted on GB, I'll investigate when I have time.
bluk
Root, but no wifi =(
First I want to mention that you made a great job!!!!
I'm from germany but the shop sold me a US-Version device (yp-gi1CB). I flashed the CB rooted firmware but i have no wifi. then i flasehd the cw firmware, same problem. Hope there is a solution :/
thanks!
Nouri92 said:
First I want to mention that you made a great job!!!!
I'm from germany but the shop sold me a US-Version device (yp-gi1CB). I flashed the CB rooted firmware but i have no wifi. then i flasehd the cw firmware, same problem. Hope there is a solution :/
thanks!
Click to expand...
Click to collapse
yes i have the same problem i root my device and i have no wifi
Kendos007 said:
yes i have the same problem i root my device and i have no wifi
Click to expand...
Click to collapse
Look at this thread http://forum.xda-developers.com/showthread.php?t=1715461&page=50 untill now the simplest solution is to flash another kernel, but im waiting for a another solution you can read that thread, the problem begans 1 page before..(page 49)
As I posted before I had the same problem when rooting, no WLAN.
But I've got it working again.
Before rooting I did a backup op my /System dir. And because there is a problem with de wifi driver, I restored the files in /etc/wifi from my backup.
After a reboot everything worked fine.
I attached the wifi folder so you guys can restore it. Hope it helps.
If you need any help, let me know.
kiteman76 said:
As I posted before I had the same problem when rooting, no WLAN.
But I've got it working again.
Before rooting I did a backup op my /System dir. And because there is a problem with de wifi driver, I restored the files in /etc/wifi from my backup.
After a reboot everything worked fine.
I attached the wifi folder so you guys can restore it. Hope it helps.
If you need any help, let me know.
Click to expand...
Click to collapse
Thanks man I have wifi again
kiteman76 said:
As I posted before I had the same problem when rooting, no WLAN.
But I've got it working again.
Before rooting I did a backup op my /System dir. And because there is a problem with de wifi driver, I restored the files in /etc/wifi from my backup.
After a reboot everything worked fine.
I attached the wifi folder so you guys can restore it. Hope it helps.
If you need any help, let me know.
Click to expand...
Click to collapse
Hello~ I copied your wifi folder to system/etc/wifi.. and replaced it, but still don't have wifi after reboot. :crying: Any important process I missed?
lng325 said:
Hello~ I copied your wifi folder to system/etc/wifi.. and replaced it, but still don't have wifi after reboot. :crying: Any important process I missed?
Click to expand...
Click to collapse
Hey! Not sure about your device model, can you confirm it is YP-GI1CW ? Btw, the permissions for the wifi and wifi/softap files should be 644, and 755 for the softap directory. Here's my output:
Code:
# ls -l /system/etc/wifi
-rw-r--r-- root root 274168 2012-03-17 10:05 firmware.bin
drwxr-xr-x root root 2012-03-17 10:05 softap
-rw-r--r-- root root 16295 2012-03-17 10:05 tiwlan.ini
-rw-r--r-- root root 16986 2012-03-17 10:05 tiwlan_cert.ini
-rw-r--r-- root root 883428 2012-03-17 10:05 tiwlan_drv.ko
-rw-r--r-- root root 16985 2012-03-17 10:05 tiwlan_plt.ini
-rw-r--r-- root root 1012 2012-03-17 10:05 wifi.conf
-rw-r--r-- root root 134 2012-03-17 10:05 wpa_supplicant.conf
# ls -l /system/etc/wifi/softap
-rw-r--r-- root root 262356 2012-03-17 10:05 ap_firmware.bin
-rw-r--r-- root root 652 2012-03-17 10:05 hostapd.conf
-rw-r--r-- root root 954932 2012-03-17 10:05 tiap_drv.ko
-rw-r--r-- root root 22424 2012-03-17 10:05 tiwlan_ap.ini
Also, some report flashing the stock kernel solved the problem, but this has some drawbacks (logo lost, warranty voided, device watermarked).
If you solve your problem please report what worked for you
bluk
EDIT: just in case, here are the MD5s
Code:
4fc219f6c48380e5df3c4229d3dfec32 firmware.bin
7525a9d0f212cba5ef4ea78860a9285b tiwlan_cert.ini
4457eadff2e6a0e91c1778c794f2ee21 tiwlan_drv.ko
8bd66fa950e4ecff2b34b4063beb44ef tiwlan.ini
c5d6fcfc2ad06b81db3dc3a5f6e7d98c tiwlan_plt.ini
0db52ef0a3e4941874f7de054abd9fc9 wifi.conf
bbb0cc9dac7a8d03ea4d6d477e49a0ee wpa_supplicant.conf
0e82efa50d450915b200a93246190d08 softap/ap_firmware.bin
880f7954eeb2a01d49295f1bd45e8c31 softap/hostapd.conf
ccfcb7e4d27276b0e3791025b2990e26 softap/tiap_drv.ko
214b2320c13c2242db05c40dbe3944d5 softap/tiwlan_ap.ini
zebluk said:
Hey! Not sure about your device model, can you confirm it is YP-GI1CW ? Btw, the permissions for the wifi and wifi/softap files should be 644, and 755 for the softap directory. Here's my output:
Code:
# ls -l /system/etc/wifi
-rw-r--r-- root root 274168 2012-03-17 10:05 firmware.bin
drwxr-xr-x root root 2012-03-17 10:05 softap
-rw-r--r-- root root 16295 2012-03-17 10:05 tiwlan.ini
-rw-r--r-- root root 16986 2012-03-17 10:05 tiwlan_cert.ini
-rw-r--r-- root root 883428 2012-03-17 10:05 tiwlan_drv.ko
-rw-r--r-- root root 16985 2012-03-17 10:05 tiwlan_plt.ini
-rw-r--r-- root root 1012 2012-03-17 10:05 wifi.conf
-rw-r--r-- root root 134 2012-03-17 10:05 wpa_supplicant.conf
# ls -l /system/etc/wifi/softap
-rw-r--r-- root root 262356 2012-03-17 10:05 ap_firmware.bin
-rw-r--r-- root root 652 2012-03-17 10:05 hostapd.conf
-rw-r--r-- root root 954932 2012-03-17 10:05 tiap_drv.ko
-rw-r--r-- root root 22424 2012-03-17 10:05 tiwlan_ap.ini
Also, some report flashing the stock kernel solved the problem, but this has some drawbacks (logo lost, warranty voided, device watermarked).
If you solve your problem please report what worked for you
bluk
EDIT: just in case, here are the MD5s
Code:
4fc219f6c48380e5df3c4229d3dfec32 firmware.bin
7525a9d0f212cba5ef4ea78860a9285b tiwlan_cert.ini
4457eadff2e6a0e91c1778c794f2ee21 tiwlan_drv.ko
8bd66fa950e4ecff2b34b4063beb44ef tiwlan.ini
c5d6fcfc2ad06b81db3dc3a5f6e7d98c tiwlan_plt.ini
0db52ef0a3e4941874f7de054abd9fc9 wifi.conf
bbb0cc9dac7a8d03ea4d6d477e49a0ee wpa_supplicant.conf
0e82efa50d450915b200a93246190d08 softap/ap_firmware.bin
880f7954eeb2a01d49295f1bd45e8c31 softap/hostapd.conf
ccfcb7e4d27276b0e3791025b2990e26 softap/tiap_drv.ko
214b2320c13c2242db05c40dbe3944d5 softap/tiwlan_ap.ini
Click to expand...
Click to collapse
I sure my device is CW verison, I bought it in Hong [email protected]@ I try to change the permissions on files, still dont work. The only method for me is flash back to Hong Kong Stock Rom ( no root).
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
I finally got my wifi back!!! after I said, the only method is flash back the Hong Kong stock rom.. I suddenly think why I don't extract wifi folders from Hong Kong Stock Rom? So I do it and get work!!!!!!! thanks all ~~
Maybe drivers are different on different country although our versions are same( YP-GI1CW)?????.. btw, I found the details code of my device : YP-GI1CW/XSH<<?
My version is YP-GI1CW/XEF ... probably the cause of problem, I'll mention that in OP thanks; and good job fixing your wifi!
bluk
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Thanks to an anonymous donor we now have the ZV6 TOT. I have broken down the TOT and also uploaded the individual partitions which can be flashed if rooted. Speaking of root... ZV6 blocks Stump Root. If you wish to use ZV6 and have root you must install Bump'd TWRP while on ZV4 then manually flash the ZV6 boot/modem/system partitions... OR you may be able to root on ZV4 then take the official ZV6 OTA update and keep root -- the OTA has NOT been pushed yet so it is too early to say for sure. Remember to NEVER take an OTA if you have modified your SYSTEM partition at all (xposed/tethermod/etc) OR if you have TWRP installed.
Changelog:
Google Security Patches
Qualcomm Security Patch
International Voice over WI-FI
Improve unlock algorithm when phone is in the pocket
Enhancements to the LG Home (Sluggish UI fix)
Enhancement to the compass application
Enhancement to the Auxiliary cable recognition.
Mobilize Device Content Caching - An application caches HTTP web and app data on the device (not the Network), making the retrieval of data faster and saving bandwidth on the network
--TOT (*.zip) can be downloaded *HERE*
Flash this TOT using the same method as ZV4. You will need to select "Board DL" in LG Flash, otherwise you will get stuck. After the TOT flashes it will reboot your phone into the "MiniOS".. unplug the USB cable and press and hold the power button on the phone then press on the "Normal Boot" option on your phones screen. You are now on stock ZV6. Remember... there is no root for ZV6 so do not flash ZV6 TOT unless you don't mind being without root.
--Individual ZV6 partitions to flash manually can be downloaded *HERE*
I am removing the system.img from Codefire but thanks to @budeone system.img has been mirrored HERE. Feel free to make more mirrors of system...
The bootloader does NOT need to be updated in order to use the ZV6 boot/modem/system images. It's completely optional to flash the bootloader files (aboot, sbl1, dbi, laf, factory, tz, rpm). To flash the boot, modem and system partitions manually someone can make some new flashable *.zips containing the partitions... OR you can use my "flash2" *.zips which can be found under the How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img section in my *[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually* thread. You simply stick any loose system.img and/or boot.img and/or modem.img on your internal sdcard and flash my premade flashable zips in TWRP to install them.
--ZV4-to-ZV6 OTA Update Zip can be downloaded *HERE*
You must have a stock recovery and stock system partition for this to work. Being rooted may be OK but if you've edited or removed apks or other files or edited the build.prop then OTA zip may fail the integrity check. Root may not stick thru OTA.. until someone confirms one way or the othe the risk is yours.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename zip file into update.zip
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Alternate Directions to skip using ADB (must have root):
1. Stick OTA zip file in the /cache directory
2. Power off and boot into stock recovery (vol down + power)
3. Select the Update from cache option... then select the update zip you placed in /cache
As mentioned above.. ZV6 blocks Stump Root. Bump is not blocked.. so as long as you have root with ZV4 you can manually update to ZV6 and keep Bump'd TWRP or flash any Bump'd kernel or rom. No anti-rollback has been added to this update either.. so downgrading to ZV4 works!
Click to expand...
Click to collapse
Autoprime. Thank you for your work. +1
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Well, took me a bit to get back up and running... but yeah, not seeing much of a difference in this versus ZV4. (Well, except losing root since I'm impatient and flashed the TOT.)
Interesting any major changes or is it a security update
autoprime said:
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Click to expand...
Click to collapse
I'll mirror when I get home from work today. Thanks man!
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Warboy said:
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Click to expand...
Click to collapse
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
engine95 said:
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Click to expand...
Click to collapse
No issues downgrading. There'd be giant red letters everywhere otherwise. But I have now added a mention in the OP that specifies downgrading is still an option. :good:
ZV6 upgrade went just fine, as you stated. No problems using flash2 stuff and let TWRP save the root. It seems to upgrade the Home launcher as well as the contacts database. It also upgrades the Sprint data-sharing activity. In other words, ZVF6 works fine, but is not a big update.
Flashable zip should be up tonight. Tomorrow at latest.
http://forum.xda-developers.com/showthread.php?p=56937777
I have a working compass!
I flashed the modem.img first with no apparent change, then the system.img... Shazammm! After calibration, the compass seems to be accurate. This was the big flaw for me on an otherwise lovely device and now it seems to be working. Now I can look forward to a Lollipop update.
I pray it fixes the bluetooth. I have a Chrysler U Connect system and my G3 or a G3 Vigor for my girlfriend will not stay paired to the unit.
After unzipping the system.img zip, it's named "14-system.img".
I plan on using the "flash2" process of upgrading.
Do I need to rename "14-system.img" to just "system.img" for the flash2 procedure to work?
Thank you
EDIT: I went back and re-read Auto's manual update procedure and can confirm, yes, I do need to rename "14-system.img" to "system.img"
autoprime said:
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
Click to expand...
Click to collapse
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Warboy said:
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Click to expand...
Click to collapse
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
autoprime said:
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
Click to expand...
Click to collapse
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Warboy said:
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Click to expand...
Click to collapse
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
autoprime said:
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
Click to expand...
Click to collapse
Should it be Flash2 not flash2
thznutz87 said:
Should it be Flash2 not flash2
Click to expand...
Click to collapse
I tried having a capital F and that didn't change anything.
system.7z
https://mega.co.nz/#!G0onwR5T!QV-NZ2hpAIllAX9tKCNBDkGLyE7AWD241Stws-c6y18
NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I have created this flashable zip myself and tried this on QMobile Z8 only. It's similar to Wiko Ridge 4G and Blu Life One (2015) in hardware specifications.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing.
NOTE-2:
This flashable zip flashes SYSTEM and BOOT partitions only. If you face ROM abnormal behavior like signals issue, charging problem, device heat up etc. you may flash other partitions as explained here.
Read here more about partitions.
REQUIREMENTS
To flash zip, CUSTOM RECOVERY must be installed. If you don't have one, get here.
If your device is bricked and doesn't boot, try flashing factory firmware as explained here. Even if Download Mode isn't accessible, get official support for your device and pray for it.
STEPS
Download QMobile Z8 Stock ROM Lollipop 5.0.2 Rooted flashable unsigned zip and place it on SD Card or Internal Memory (if you don't going to wipe it).
Reboot into Recovery.
Install ROM zip.
Wipe DALVIK-CACHE, CACHE & DATA.
Reboot. Ignore "No OS Installed" warning (if it comes).
Enjoy!
Thanks for Your Post
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
sadiq1 said:
I have Qmobile z8 , i updated the firmware of Wiko Ridge 4g on my phone few days before.
So my current OS is Ridge 4g , now as i have tried to install your custom rom you mentioned in this thread
it goes normally about 25 percent in progress bar then suddenly progress bar completed as it goes completed , there is no error but in bottom its written Done. then i clear cache and then restart the phone , but it stuck on Wicko logo then restart and this continues. It seems installation did not go completed ,,,, Any solution ?
Click to expand...
Click to collapse
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
sadiq1 said:
What is dd , can you please explain what to do in some detail , i am not so much familiar with android
Click to expand...
Click to collapse
dd is a command on UNIX-like operating systems including Linux and Android to copy / dump data. https://www.computerhope.com/unix/dd.htm
Put both img files on internal sd card. Boot in recovery and run these commands from built-in terminal or adb shell:
Code:
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
Make sure "/dev/block/mmcblk0p23" and "/dev/block/mmcblk0p24" are correct partitions to flash or you may overwrite wrong partitions.
Don't forget to make a backup before making experiments.
mirfatif said:
Flashable zip contains just system.img and boot.img. Extract both files and flash using dd.
Click to expand...
Click to collapse
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
x.ak**** said:
This method of creating a .img using DD is quite difficult so consider doing this instead:
download mode in noir z8
turn off your phone
press*volume +,vol -*and*power button*for 5 second then download mode mn aa jae ga
Firmware to be downloaded from here
http://de.wikomobile.com/maj.php?telephone=549
Rest info is in the pics attached below serial wise
Hit the thumbs up to support me and reply if you need further assistance
Click to expand...
Click to collapse
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
mirfatif said:
That's for flashing stock firmware. https://forum.xda-developers.com/android/help/factory-firmware-qmobile-z8-wiko-ridge-t3586572
Mine flashable image is a bit modified, rooted, bloats removed etc. But yes flashers are easy to use and risk-free.
Click to expand...
Click to collapse
Exactly that's why I prefer them and recommend them.
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------
mirfAtif
where can i write this command
cd /sdcard
dd if=boot.img of=/dev/block/mmcblk0p23
dd if=system.img of=/dev/block/mmcblk0p24
I have TWRP this is a GUI program , where can i write command there?
---------- Post added at 06:35 PM ---------- Previous post was at 05:44 PM ----------
I found the terminal to write the command
Let me know where should i keep the files after unzip them
---------- Post added at 06:46 PM ---------- Previous post was at 06:35 PM ----------
Sorry mirfatif
You told me every thing in ur first post , i didnt read it properly,
Thanks ,
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
sadiq1 said:
Just let me know is there any way to find out which partition is for System and which is for Boot on my phone
Click to expand...
Click to collapse
Execute these commands:
Code:
ls -l /dev/block/bootdevice/by-name/boot
ls -l /dev/block/bootdevice/by-name/system
sadiq1 said:
I have already used the firmware method from Wiko site ,
but my Wifi and bluetooth are not working
Click to expand...
Click to collapse
Flash QMobile factory firmware, not Wiko's. If that doesn't fix, there must be hardware problem.
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
sadiq1 said:
Atif
I tried to copy both files.
on first file its copied 32 mb with no error
on second file it only copied 32 mb and said no space left on device
what its mean , but my device has space
Click to expand...
Click to collapse
You must be flashing wrong partition. Or try changing different dd binary e.g. from latest busybox version.
Or if you can loop mount system.img with ext4 filesystem, simple copy files to /system partition along with file permissions.
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
sadiq1 said:
this time i copied successfully to right partitiones then Wipe DALVIK-CACHE, CACHE & DATA.
then restart but stuck in start loop
Click to expand...
Click to collapse
Then other firmware partitions from Wiko must be incompatible with QMobile ROM. Simple is to use a flasher which flashes all partitions. But replace the recovery image with custom recovery like TWRP. After that you may flash this rooted ROM if needed.
yar mujhe app se bat kerni he 03343210716/03028484502
I downloaded some firemware for qmobile , using QFile application
every thing was ready when i click on download there was error "download fail:sahara failvalue canot be null"
sadiq1 said:
yar mujhe app se bat kerni he 03343210716/03028484502
Click to expand...
Click to collapse
English please, it's international forum.
PM me for personal assistance.
mirfatif said:
English please, it's international forum.
PM me for personal assistance.
Click to expand...
Click to collapse
He's saying he wants to have a word with you and he has given his number.
x.ak**** said:
He's saying he wants to have a word with you and he has given his number.
Click to expand...
Click to collapse
I know I'm Urdu speaking :laugh:
Just asking to follow the rules.