An Android 4.4.2 KitKat update package for S8-301L found on a chinese cloud-drive.
http://pan.baidu.com/s/1i3Fxuh3
Seems to be working well on my M1, bought week ago. I haven't found any bugs so far. Sadly tho, the bootloader stays locked.
Mirror: https://mega.co.nz/#!6hAhhSQI!FUaPFM8uZnKjKSOEh9tAdBg0j1T3NLgV5Uspk7p73Fw
Hi is this still working well?
How to install?
Does it wipe everything?
Thanks...
root
Where/how to you root it, or do I root the
Previous version before?
Bricked huawei m1-s8 301l
HAS ANYONE ENDED UP BRICKING THEIR M1S8 301L BY ROOTING? I HAVE AND NOW IM PRESENTED WITH THE BOOT SPLASH SCREEN, I HAVEVERY LIMITED USAGE TO FASTBOOT, THEREAS ONLY A FEW COMMANDS WORK, IF I FLASH A RECOVERY, IT FINALAZES AND SAYS DONE, BUT IN FACT ITS DONE ABSLOUTLY NOTHING, THE DLOAD IN SDCARD UPDATE DOES NOTHING, IM CONSTANTLY LOOKING AT AN OVERSIZED 4G HANDSET THATS STUCK ON THE BOOT UP SPLASH SCREEN, ANY HELP WOULD BE GREAT, EITHER MESSAGE ME AT tymedwards1 at gmail dot com OR COMMENT HERE FOR OTHERS WITH THE SAME PROBLEM CAN FIX...... THANKS
Flashed some days ago, working great without any problems M1_S8-301L
xmyszka said:
Flashed some days ago, working great without any problems M1_S8-301L
Click to expand...
Click to collapse
Hello!
Any interested . Hungarian languages are available in the Settings menu ? LTE also has a European drive mode?
In case of failure it is possible to downgarde?
tymmuff said:
HAS ANYONE ENDED UP BRICKING THEIR M1S8 301L BY ROOTING? I HAVE AND NOW IM PRESENTED WITH THE BOOT SPLASH SCREEN, I HAVEVERY LIMITED USAGE TO FASTBOOT, THEREAS ONLY A FEW COMMANDS WORK, IF I FLASH A RECOVERY, IT FINALAZES AND SAYS DONE, BUT IN FACT ITS DONE ABSLOUTLY NOTHING, THE DLOAD IN SDCARD UPDATE DOES NOTHING, IM CONSTANTLY LOOKING AT AN OVERSIZED 4G HANDSET THATS STUCK ON THE BOOT UP SPLASH SCREEN, ANY HELP WOULD BE GREAT, EITHER MESSAGE ME AT tymedwards1 at gmail dot com OR COMMENT HERE FOR OTHERS WITH THE SAME PROBLEM CAN FIX...... THANKS
Click to expand...
Click to collapse
Just bricked mine, can anyone post a list from /dev/block....by_name list
That way I'll try the huaweiextract or to unpack update.app
Many thxs
Can someone tell me what i must do with dload folder?
I can't find any instructions about that.
I must download any program to unzip this update or just copy to sd card and then choose updates in my tablet?
Thanks for help.
I help you , why not help me?
To answer your question, after unpacking dload on your PC, copy the dload directory to your
External sdcard.
The either :
1. Goto main menu, about phone, system update, select local sdcard/memory
Or
2. Power down and restart.
Either way you get the green spinning Android update screen is installing...
..when it tells you it has installed correctly, take out the external
card - otherwise it installs again- and hit OK/ or reboot.
OK.. Now before you do that , MAKE A BACKUP, AND THEN with Windows backup everything by copying internal/external drives to your pc.
That way you can restore anything you may need.
Also before you do that could you, using terminal emulator, send me a copy of the result by typing
su;ls -l /dev/block/platform/ms*1/by_name
That way I can extract the update.app and rebuild my tab
Any problems hit reply
And thxs in advance for your info and contribution
Rgds
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
Should have told you my tab is bricked cos it doesn't work at 45°Celsius!
I own this, but my model is EE Eagle branded. Do you think this update will work for it?
hillbillie said:
Also before you do that could you, using terminal emulator, send me a copy of the result by typing
su;ls -l /dev/block/platform/ms*1/by_name
Click to expand...
Click to collapse
Sorry for late reply
Code:
[email protected]:/ # ls -l /dev/block/platform/*/by-name
lrwxrwxrwx root root 2015-09-17 15:53 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-09-17 15:53 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-09-17 15:53 cust -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-09-17 15:53 data -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-09-17 15:53 dsp -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-09-17 15:53 fastboot2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-09-17 15:53 hifi -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-09-17 15:53 hisitest0 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-09-17 15:53 hisitest1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-09-17 15:53 hisitest2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-09-17 15:53 log -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-09-17 15:53 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-09-17 15:53 lowpower -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-09-17 15:53 mcuimage -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-09-17 15:53 misc -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-09-17 15:53 modemimage -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-09-17 15:53 modemlog -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-09-17 15:53 modemnvbkup -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-09-17 15:53 modemnvm1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-09-17 15:53 modemnvm2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-09-17 15:53 nvme -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-09-17 15:53 oeminfo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-09-17 15:53 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-09-17 15:53 round -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-09-17 15:53 secureboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-09-17 15:53 system -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-09-17 15:53 teeos -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-09-17 15:53 userdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-09-17 15:53 vrcb -> /dev/block/mmcblk0p11
[email protected]:/ #
Hey thanks,
maybe that "lowpower" partition could save it!
I'll try the extractor and post it later this week, forgot this handy pagepage:
boot_tips_n_tricks
Managed to fix the problem, but by loafing zyrx(sp?) Cwm mod, problem was found by entering in recovery and mounting all partitions
!!!!
However i suggest anyone should keep the dload, just in case.
If anyone needs a partition, ask and I'll load to mega
working but not stable
Meizirkki said:
An Android 4.4.2 KitKat update package for S8-301L found on a chinese cloud-drive...
Click to expand...
Click to collapse
The guide is included after unzipping.
I have S8-301L. It worked fine. But after this Update you'll not be Able to play Heavy 3d games or open heavy apps since they crash all the time, Like ASPHALT 8 game crashes all the time
I tried everything by getting to developer options and do all the GPU stuff still nothing. Tried to factory reset, didn't help
eventually I DOWNGRADED TO 4.2 Again.
even this is an official rom but seems they didn't finish it well.
thanks for sharing. I'd download a CUSTOM ROM if any :/
EE eagle bricked
Please I bricked my EE eagle. Its can't bypass the boot screen
Please I will be very happy if Someone can help me bring it back to life.. I will be very grateful .... Tnx
have bricked my huawei media pad m1 s8-301L
hillbillie said:
Just bricked mine, can anyone post a list from /dev/block....by_name list
That way I'll try the huaweiextract or to unpack update.app
Many thxs
Click to expand...
Click to collapse
have bricked mine too bruh and i dont know what to do . can someone help me please.
its has been there for 6 month now and dont know what to do... please mail me ([email protected]) if u can help me with the stock rom or any help. i will be very grateful
xmyszka said:
Flashed some days ago, working great without any problems M1_S8-301L
Click to expand...
Click to collapse
Did you had to wipe all your data and how did you flashed it? Thanks.
---------- Post added at 10:30 AM ---------- Previous post was at 10:14 AM ----------
Meizirkki said:
An Android 4.4.2 KitKat update package for S8-301L found on a chinese cloud-drive.
http://pan.baidu.com/s/1i3Fxuh3
Seems to be working well on my M1, bought week ago. I haven't found any bugs so far. Sadly tho, the bootloader stays locked.
Mirror: https://mega.co.nz/#!6hAhhSQI!FUaPFM8uZnKjKSOEh9tAdBg0j1T3NLgV5Uspk7p73Fw
Click to expand...
Click to collapse
How did you flashed it, is it available for all countries and will it flash the ROM even if my recovery is broken? Thanks.
hillbillie said:
I help you , why not help me?
To answer your question, after unpacking dload on your PC, copy the dload directory to your
External sdcard.
The either :
1. Goto main menu, about phone, system update, select local sdcard/memory
Or
2. Power down and restart.
Either way you get the green spinning Android update screen is installing...
..when it tells you it has installed correctly, take out the external
card - otherwise it installs again- and hit OK/ or reboot.
OK.. Now before you do that , MAKE A BACKUP, AND THEN with Windows backup everything by copying internal/external drives to your pc.
That way you can restore anything you may need.
Also before you do that could you, using terminal emulator, send me a copy of the result by typing
su;ls -l /dev/block/platform/ms*1/by_name
That way I can extract the update.app and rebuild my tab
Any problems hit reply
And thxs in advance for your info and contribution
Rgds
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
Should have told you my tab is bricked cos it doesn't work at 45°Celsius!
Click to expand...
Click to collapse
I have a broken recovery, if I update the software to 4.4.2 , will my tab get bricked? Thanks.
I need your help.
Meizirkki said:
An Android 4.4.2 KitKat update package for S8-301L found on a chinese cloud-drive.
http://pan.baidu.com/s/1i3Fxuh3
Seems to be working well on my M1, bought week ago. I haven't found any bugs so far. Sadly tho, the bootloader stays locked.
Mirror: https://mega.co.nz/#!6hAhhSQI!FUaPFM8uZnKjKSOEh9tAdBg0j1T3NLgV5Uspk7p73Fw
Click to expand...
Click to collapse
Hello, my mediapad got bricked after I flashed the ROM and not when I power it on it stays on the boot logo and the LED notification lights up in the following pattern : green>green>green>red. Please help me fast because my mom gonna kill me if she learns about this.?
Try software reinstall with Huawei HiSuite
Related
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
I'm trying to delete the preloaded content in the music folder. Nothing I've tried seems to work. I keep getting permission denied, even under su.
I've gone as far as even trying to do it via an adb shell.
[email protected]:/storage/sdcard0/Music # rm *.mp3
rm failed for 01 Buzz Dees_Mitkomm.mp3, Permission denied
255|[email protected]:/storage/sdcard0/Music # ls -al
-rw-rw-r-- root sdcard_rw 4976141 2008-08-01 07:00 01 Buzz Dees_Mitkomm.mp3
-rw-rw-r-- root sdcard_rw 3939059 2008-08-01 07:00 01 Classic Orchestra_Air.mp3
-rw-rw-r-- root sdcard_rw 9183266 2008-08-01 07:00 01 Orpheum_The Passion.mp3
-rw-rw-r-- root sdcard_rw 6679976 2008-08-01 07:00 01 Passion Crew_Sensual Sax.mp3
-rw-rw-r-- root sdcard_rw 4458172 2008-08-01 07:00 02 Classic Orchestra_Largo.mp3
-rw-rw-r-- root sdcard_rw 2995019 2008-08-01 07:00 06 Buzz Dees_Jaja, Neenee.mp3
[email protected]:/storage/sdcard0/Music #
Click to expand...
Click to collapse
Any ideas how to get rid of these files?
Brosto said:
I'm trying to delete the preloaded content in the music folder. Nothing I've tried seems to work. I keep getting permission denied, even under su.
I've gone as far as even trying to do it via an adb shell.
Any ideas how to get rid of these files?
Click to expand...
Click to collapse
Is this a new stock Prime?
If so I had the same problem ie couldn't delete pre loaded music or pictures, I think it also wouldn't allow me to copy items to these folders either. A factory reset fixed this althought some of the preinstalled apps like the ASUS MyCloud had vanished.
I found these by using a root explorer like Astro and locating the relevent folders in the internal memory and clicking on the (apk??) and then I think from what I remember you got the choice to delete or run/open, I clicked open and it loaded. The icon then appeared where it used to in the app drawer.
Sorry if its not a bit clear but this was something I did the day I got my Prime and my menory is a but hazy now. If you need anyhelp on how to get those apps to reapper if you factory reset I'll get mine out and let you know the path I found the apps in.
LiamThompson said:
Is this a new stock Prime?
If so I had the same problem ie couldn't delete pre loaded music or pictures, I think it also wouldn't allow me to copy items to these folders either. A factory reset fixed this althought some of the preinstalled apps like the ASUS MyCloud had vanished.
I found these by using a root explorer like Astro and locating the relevent folders in the internal memory and clicking on the (apk??) and then I think from what I remember you got the choice to delete or run/open, I clicked open and it loaded. The icon then appeared where it used to in the app drawer.
Sorry if its not a bit clear but this was something I did the day I got my Prime and my menory is a but hazy now. If you need anyhelp on how to get those apps to reapper if you factory reset I'll get mine out and let you know the path I found the apps in.
Click to expand...
Click to collapse
Not a new prime, had it since January. I'm rooted, and running stock jb. I've been able to remove the preloaded apps that I didn't want, but not these music files. Even after chmod 777 both the files and directory, still getting permission denied. I'm stumped...
Sent from my Transformer Prime TF201 using xda app-developers app
Any chance you are only partially rooted, ie did you factory reset after JB OTA? I had the same symptoms you are describing and confirmed through root explorer that I couldn't mount /system/bin to r/w. Despite this root checker showed me as rooted. Gained full root by entering about 15 commands thru adb.
Sent from my NexusHD2 using xda app-developers app
Ruprect said:
Any chance you are only partially rooted, ie did you factory reset after JB OTA? I had the same symptoms you are describing and confirmed through root explorer that I couldn't mount /system/bin to r/w. Despite this root checker showed me as rooted. Gained full root by entering about 15 commands thru adb.
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
I didn't factory reset or get JB through the OTA. It was the one from this post: [ROM] TF201 JB JRO03C 10.4.2.15 (US) Stock Deodexed + Mods [Unlocked BL]
Anyhow, is there a way to tell if I'm only partially rooted? Also, can you point me to the commands you used via adb? It's worth a shot.
Recently purchased Xolo A500, I have been trying to build CWM in builder.clockworkmod.com, but nothing works.
I have tried three times but none works.
Provided with a custom recovery.fstab but still wont work.
So can anyone help me out here.
I can provide the stock recovery.img
BTW, in recovery.fstab provided in builder.clockworkmod.com after it has finished the build the list is
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata length=-16384
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Sdcard location is wrong. It is mmcblk1p1
And mtd file in /proc/ is completely blank so I have no idea from where to get the partitions.
But I have researched enough and understand partitions and after analysing the partitions file I have extracted most of the blocks from the phone.
So now I have dumped the recovery and system partitions.
So I modified the recovery.fstab file like this
# mount points fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/cache ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p13 length=-16384
/misc emmc /dev/block/mmcblk0p19
/recovery emmc /dev/block/mmcblk0p16
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p12
/sys_boot vfat /dev/block/mmcblk0p3
/FOTA emmc /dev/block/mmcblk0p17
Has my recovery.fstab got any errors???
The online CWM builder doesn't work???
So Can Anyone Build For Me A CWM Recovery????
did u got any success
even I am waiting for same if you get any sucess please help
Thanks
kank_fraud said:
Recently purchased Xolo A500, I have been trying to build CWM in builder.clockworkmod.com, but nothing works.
I have tried three times but none works.
Provided with a custom recovery.fstab but still wont work.
So can anyone help me out here.
I can provide the stock recovery.img
BTW, in recovery.fstab provided in builder.clockworkmod.com after it has finished the build the list is
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata length=-16384
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Sdcard location is wrong. It is mmcblk1p1
And mtd file in /proc/ is completely blank so I have no idea from where to get the partitions.
But I have researched enough and understand partitions and after analysing the partitions file I have extracted most of the blocks from the phone.
So now I have dumped the recovery and system partitions.
So I modified the recovery.fstab file like this
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 /dev/block/mmcblk0p15
/data yaffs2 /dev/block/mmcblk0p13
/misc mtd misc
/recovery mtd /dev/block/mmcblk0p16
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system yaffs2 /dev/block/mmcblk0p12
Out of this I don't have any info abt the /boot partition and /misc partition
Although I think /boot partition can be at /dev/block/mmcblk0p8
I have already dumped that partition but I don't know how to analyse any of these files in a windows machine.
Has my recovery.fstab got any errors???
The online CWM builder doesn't work???
So Can Anyone Build For Me A CWM Recovery????
Click to expand...
Click to collapse
Please help
mithani said:
even I am waiting for same if you get any sucess please help
Thanks
Click to expand...
Click to collapse
Dear Sir,
Please help me, i done rooting of Xolo A500, but i done one mistake yesterday, i have done Factory Reset to it, after dt my device is showing that
not rooted, bt still showing Superuser.apk, n i've tried to root again,but it shows error "system/bin/sh : chmod not found", n my wifi is also not working, please help me Sir..:crying:
If you have been able to root the phone, the first thing you should have done is backup all the partitions necessary.
boot is mmcblk0p8
system is mmcblk0p12
recovery is mmcblk0p16
The first thing I done with the phone I recieved after 5mins is root the phone.
I didn't check it before that
So can you guys tell me how did you find the performance of the phone.
Cuz mine, everything is crashing
Phone, messeging, apps, launcher, etc...
I regret actually buying this phone.
Well the first thing I would say anyone should do is backup there boot, recovery, system partitions and whatever else you want to after you root.
I can upload the boot and recovery partitions but i am very sorry I won't be able to upload my system partition.
I backed it up when I was actually using the phone and my persona; data is there i presume.
I totally forgot how I backed up the partitions right now.
I'll post the method I used once I can remember again.
I gave up on building CWM cuz I have failed so many times that I am completely fed up of it.
I am totally new to working in linux and first I need to figure that out.
Usually you use 'cat proc/mtd' to view the partitions, but its empty in our case.
So use 'cat proc/partitions' instead
But you will only get a list of the partitions without any labels.
Out of that,
/boot mmcblk0p8
/cache mmcblk0p15
/data mmcblk0p13
/misc mmcblk0p19
/recovery mmcblk0p16
/sdcard mmcblk1p1
/system mmcblk0p12
/SYS_boot mmcblk0p3
/FOTA mmcblk0p17
/emmc mmcblk0p18
/persist mmcblk0p14
And lots more partitions are there.
I made an image of the whole NAND chip by using mmcblk0 only.
And also the other partitions individually
You can use this command to back up your partitions.
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img bs=4096
And change the names and partitions accordingly I have mentioned.
It should work.
It only works for rooted phones btw.
I have reset my phone a couple of times after I rooted and I didn't loose root.
And please can anyone confirm me about the performance of the phone.
I am having nightmares personally
I wish I could port Gingerbread instead.
Please ppl, reply.
And if anyone can upload there freshly rooted system.img partition, I'll be glad.
Maybe I recieved a phone with a very unstable ROM
Flash the recovery with
fastboot flash recovery XoloA500_Recovery_Original.img
And before you flash any new recovery, try this command
fastboot boot recovery.img
Replace recovery.img with the name you have for your recovery
If it hangs or reboots, that means the recovery is most probably won't work for you.
If still you want to try, flash it
If it doesn't work, flash the stock back
Same can be done for a boot.img you want to try.
Somebody please use the above method and dump a clean stock rooted system.img.
I used to believe backup is useless, but when you have a device that is not supported by any developer, its better to backup before you mess with it urself.
EDIT: DD command might not work for the system partition
I am not quite sure as I haven't tried to restore the backup
So please be cautious.
I am not to be blamed if any mishap happens to you or your phone.
Currently I am out of station to try anything.
I don't use laptops cuz I find it inconvenient.
Research and post your findings
I have also used this 'http://android.podtwo.com/romdump/' to dump my ROM
Use all available methods and backup your ROM in all the various methods possible.
Afterall no one is supporting our device yet.
Require Xolo A500 system.img Pleaseeee
:crying: Please somebody upload system.img of Xolo A500, please its a request to you friends.....Please :crying:
---------- Post added at 07:20 PM ---------- Previous post was at 07:04 PM ----------
kank_fraud said:
Well the first thing I would say anyone should do is backup there boot, recovery, system partitions and whatever else you want to after you root.
I can upload the boot and recovery partitions but i am very sorry I won't be able to upload my system partition.
I backed it up when I was actually using the phone and my persona; data is there i presume.
I totally forgot how I backed up the partitions right now.
I'll post the method I used once I can remember again.
I gave up on building CWM cuz I have failed so many times that I am completely fed up of it.
I am totally new to working in linux and first I need to figure that out.
Usually you use 'cat proc/mtd' to view the partitions, but its empty in our case.
So use 'cat proc/partitions' instead
But you will only get a list of the partitions without any labels.
Out of that,
/boot mmcblk0p8
/cache mmcblk0p15
/data mmcblk0p13
/misc mmcblk0p19
/recovery mmcblk0p16
/sdcard mmcblk1p1
/system mmcblk0p12
/SYS_boot mmcblk0p3
/FOTA mmcblk0p17
/emmc mmcblk0p18
/persist mmcblk0p14
And lots more partitions are there.
I made an image of the whole NAND chip by using mmcblk0 only.
And also the other partitions individually
You can use this command to back up your partitions.
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img bs=4096
And change the names and partitions accordingly I have mentioned.
It should work.
It only works for rooted phones btw.
I have reset my phone a couple of times after I rooted and I didn't loose root.
And please can anyone confirm me about the performance of the phone.
I am having nightmares personally
I wish I could port Gingerbread instead.
Please ppl, reply.
And if anyone can upload there freshly rooted system.img partition, I'll be glad.
Maybe I recieved a phone with a very unstable ROM
Flash the recovery with
fastboot flash recovery XoloA500_Recovery_Original.img
And before you flash any new recovery, try this command
fastboot boot recovery.img
Replace recovery.img with the name you have for your recovery
If it hangs or reboots, that means the recovery is most probably won't work for you.
If still you want to try, flash it
If it doesn't work, flash the stock back
Same can be done for a boot.img you want to try.
Click to expand...
Click to collapse
------------------------
Sir,
Please upload system.img, bcz nobody is given any response, i'm totally depends on ur help.
please sir, bcz my handset was in service center before some days, n again... my dad will kill me.
Please sir kindly use moborobo for backup ur personal data, Sir Please help me Sir please :crying::crying::crying:
Why don't you people research a day or 2 before hanging your phone to death.
And kid, system.img, how the hell do you plan to restore that???
I have just made a fluke backup, not necessary that it will work.
You need an update.zip, which I don't have and I don't know or currently have any resource to make one.
You shouldn't have messed with things you don't know.
Specially a phone that has no developer support currently.
You better send it for service.
I can't help you.
Neither do I have any source, nor do I have the full knowledge.
I have not tried ever to build a ROM before.
And as we don't have CWM for our phone, I am not willing to risk it just for the sake of fun.
And the moment I return station, I personally am gonna send the phone for service as I am sick and tired of it.
Its a headache to use this phone.
Why don't you people research a day or 2 before hanging your phone to death.
And kid, system.img, how the hell do you plan to restore that???
I have just made a fluke backup, not necessary that it will work.
You need an update.zip, which I don't have and I don't know or currently have any resource to make one.
You shouldn't have messed with things you don't know.
Specially a phone that has no developer support currently.
You better send it for service.
I can't help you.
Neither do I have any source, nor do I have the full knowledge.
I have not tried ever to build a ROM before.
And as we don't have CWM for our phone, I am not willing to risk it just for the sake of fun.
And the moment I return station, I personally am gonna send the phone for service as I am sick and tired of it.
Its a headache to use this phone.
Anyone want to knock yourself out by flashing my stock rooted system.img, knock yourself out
http://www.mediafire.com/?3vs68fl1lpsoc9u
If you break your precious phone, I am not responsible
fastboot flash system system.img
CWM for Xolo A500
Well by luck I found a CWM that boots but it doesn't backup
After a bit of modification, I have been able to successfully create a nandroid backup.
But sadly its chinese and I have no idea on how to translate to english, so please ask someone else.
http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
It is originally for the GreenOrange M2S mobile and it also works with the Videocon A30
After a bit of modification, it seems to be working for our Xolo A500
Its in chinese so figure it out yourself.
For now I all I can say is if you want to backup, do not flash
Use this command 'fastboot boot cwm1.img'
Your phone will boot to CWM and from there, select the 3rd option from the bottom and select the first option you see that has 'SD' written on it.
This will back up your current ROM to your microsd along with the stock recovery, I think
Please reset your phone before you backup
And reset your phone after restore
Now you can try flashing this CWM and see what else you can figure out.
Please post your findings.
If nobody would share, we would all be dumb and mentally handicapped
Seems to me this is CWM 6
Many more options I see which I can't figure out just by guessing
These are newly introduced or what, even I have no Idea.
Well hope somebody now can develop a ROM for our phones
CWM6 has incremental backups, no more system.img
As far as I can say
On the main menu
- reboot
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
My phone's performance is really good, no force close or anything, but my phone is just a rebranded Lava XOLO A500, but I think the ROM is still the same, because inside the phone, I can still signs of XOLO A500, so I'd like to help
EDIT:
Thanks for the partition info! I'll try and help you make CWM for our phone
Are you talking about the Cherry Mobile Burst.
If your ROM is stable, can you use the CWM I posted in here and take a backup and upload it.
I'd like to try.
For partitions unpack stock recovery and find the file recovery.fstab and if you also have like the A500 a recovery_mmc.fstab. This is where the real partition Table is, But its missing the emmc partition. EMMC partition in the A500 is mmcblk0p18
kank_fraud said:
Are you talking about the Cherry Mobile Burst.
If your ROM is stable, can you use the CWM I posted in here and take a backup and upload it.
I'd like to try.
For partitions unpack stock recovery and find the file recovery.fstab and if you also have like the A500 a recovery_mmc.fstab. This is where the real partition Table is, But its missing the emmc partition. EMMC partition in the A500 is mmcblk0p18
Click to expand...
Click to collapse
I flashed this CWM and it works.. I even have my nandroid back up.. now I'm looking for custom rom for xolo a500/cherry mobile burst..
hit thanks!
If anybody want a CWM flashable stock ROM the download this and flash away
http://www.mediafire.com/?u1oxl5suz7tsuz2
Perform a factory reset if you desire
Download this CWM http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
Its chinese so becareful while pushing the buttons.
Its rooted but install superuser from Play Store and update su binary
Has a few build.prop tweaks otherwise a full stock
Break a Leg!!!
kank_fraud said:
If anybody want a CWM flashable stock ROM the download this and flash away
http://www.mediafire.com/?u1oxl5suz7tsuz2
Perform a factory reset if you desire
Download this CWM http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
Its chinese so becareful while pushing the buttons.
Its rooted but install superuser from Play Store and update su binary
Has a few build.prop tweaks otherwise a full stock
Break a Leg!!!
Click to expand...
Click to collapse
hey man!! I need your help.. I tried to make my own splash image using terminal emulator and I ended messing up my /dev/block/
now, my phone doesnt have wifi, the icon is gone. my phone cant detect my sim card, and the signal icon is gone..
is there a way to restore this?? please help!! thanks!!
If you have installed cwm. Then just restore your backups if you have other just download a stock rom for your android phone and simply flash it
Nyk Sharma
Can someone help me build twrp recovery for HTC desire 620 dual sim.
Brand: htc
Model: desire 620 dual sim
Root: no
Able to flash img:yes
S-off:no
Recovery:stock
Hi,
I've accidentally deleted app shown bellow.
What is the app used for? Will it cause any trouble?
-rw-r--r-- root root 49706 1970-02-15 13:55 SemcTelephonyProvider.apk
-rw-r--r-- root root 193440 1970-02-15 13:57 SemcTelephonyProvider.odex
My FW is 17.1.1.A.0.402.
Edit: it caused problems with GSM. I've managed to restore it. This can be closed/deleted. Thanks
It seems that flashing a modem on the GS5 can be real pain. Even using a pc w/odin the modem doesn't always stick.
I've been messing around with terminal emulator trying to figure it out. I pieced together a small script that is letting me flash a modem. Its easy and fast for me, so i thought I'd try to share it here.
It is working on my phone without fail, but that doesn't always mean it will work for others.
If anyone is up for trying this out on their phone there are instructions below. However, There is some risk.
DO NOT TRY THIS if you are not experienced with flashing modems. This could possibly soft brick your phone. It could possibly break, or erase your current modem.
If you don't know how to fix it, (i.e.
recover from softbrick, have the ability to flash modem with pc) YOU SHOULD NOT TRY THIS.
If you are comfortable with that then please go ahead and tell me if it works for you:
You will need the modem.bin file extracted from any of the stock .tar.md5s available.
Here is BNG4 if you need one.
https://docs.google.com/file/d/0B4OeXSTx8tgBWGlHWU1mVDZ0cDQ/edit?usp=docslist_api
Make sure the modem.bin is stored on your internal sd. Path: /storage/emulated/0/ -Not in the download folder.
Once you have the modem.bin on your internal sd, you will open terminal emulator. Make sure you are running as superuser.(type: su then hit enter)
Now, just copy and paste this exactly as it is below into terminal and run it(enter)
---------------------------------------------------------
#!/system/bin/sh
# variables
partition="/dev/block/platform/msm_sdcc.1/by-name/modem"
modem="/sdcard/modem.bin"
busybox="/system/xbin/busybox"
# main
$busybox dd if="${modem}" of="${partition}"
-----------------------------------------------------------
Once you hit run, it will take a second or up to 10 before it outputs a confirmation. It should show 100000ish+1 records in/out and copied modem.bin size MB and speed in MB/sec.
Reboot your phone and thats it.
The baseband version should now be updated in settings and anywhere else you might find it.
Ian the Great said:
It seems to be very difficult if not impossible for to flash modems on GS5 without using odin and pc.
I've been messing around with terminal emulator and peiced together a small script that will flash modems for me.
It is working on my phone without fail, but that doesn't always mean it will work for others.
I'm looking for a few volunteers to try this method and confirm if its working for them or not.
HOWEVER, DO NOT TRY THIS if you are not experienced in flashing modems. This could possibly soft brick your phone. It could possibly screw up, or erase your current modem. If you don't know how to fix it (i.e. recover from softbrick, have the ability to flash modem with pc) YOU SHOULD NOT TRY THIS.
If you are comfortable with that then go ahead:
You will need the modem.bin file extracted from any of the stock .tar.md5s available.
Here is BNG4 if you need one.
https://docs.google.com/file/d/0B4OeXSTx8tgBWGlHWU1mVDZ0cDQ/edit?usp=docslist_api
Make sure the modem.bin is stored on your internal sd. Path: /storage/emulated/0/ -not in downloads folder.
Now open terminal emulator and make sure you are running as superuser.(type: su then hit enter)
Then just copy and paste exactly as it is below into terminal and run it(enter)
---------------------------------------------------------
#!/system/bin/sh
# variables
partition="/dev/block/mmcblk0p2"
modem="/sdcard/modem.bin"
busybox="/system/xbin/busybox"
# main
$busybox dd if="${modem}" of="${partition}"
-----------------------------------------------------------
Once you hit run, it should take a second or up to 10 before it outputs a confirmation. It should show 100000ish+1 records in/out and copied modem.bin size MB and speed in MB/sec.
Reboot phone and thats it.
The baseband version should now be updated in settings and anywhere else you might find it.
Click to expand...
Click to collapse
I would change "partition=/dev/block/mmcblk0p2" to this: partition="/dev/block/platform/msm_sdcc.1/by-name/modem"
This will ensure the the correct block is written to no matter what S5 variant they are using. Hardcoding blocks can sometimes yet seldomly lead to bricked devices
elesbb said:
I would change "partition=/dev/block/mmcblk0p2" to this: partition="/dev/block/platform/msm_sdcc.1/by-name/modem"
This will ensure the the correct block is written to no matter what S5 variant they are using. Hardcoding blocks can sometimes yet seldomly lead to bricked devices
Click to expand...
Click to collapse
Yes, that is better. Thanks
First of all thanks for the Tool and instructions.
will it let me flash G900F modem on G900T ?
Ian the Great said:
It seems that flashing a modem on the GS5 can be real pain. Even using a pc w/odin the modem doesn't always stick.
$busybox dd if="${modem}" of="${partition}"
-----------------------------------------------------------
Once you hit run, it will take a second or up to 10 before it outputs a confirmation. It should show 100000ish+1 records in/out and copied modem.bin size MB and speed in MB/sec.
Reboot your phone and thats it.
The baseband version should now be updated in settings and anywhere else you might find it.
Click to expand...
Click to collapse
I have flashed modems via PC with odin and They stick everytime as long as I pull the battery first. I will give terminal a try .Thanks
---------- Post added at 11:44 AM ---------- Previous post was at 10:50 AM ----------
By the way I am trying this right now .. I will post back shortly
spirodave said:
I have flashed modems via PC with odin and They stick everytime as long as I pull the battery first. I will give terminal a try .Thanks
---------- Post added at 11:44 AM ---------- Previous post was at 10:50 AM ----------
By the way I am trying this right now .. I will post back shortly
Click to expand...
Click to collapse
Hey how did this workout for you bud. Thanks
xda23 said:
Hey how did this workout for you bud. Thanks
Click to expand...
Click to collapse
I found i faster to just convert the modem.bin to a tar.md5 . I put the NH5Modem up in the general section . After it wouldnt let me copy and paste the command from chrome to terminal emulator i just decided to convert it . I guess i could have just used ADB but didnt think about it at the time . I didnt want to risk typing the wrong command to terminal to install the modem .
Just tried this script a min ago with the NH5 modem.
It looked like it worked, but then after I rebooted and disabled airplane mode, it still says NF6.
I've done a similar method with my fiancee's Galaxy S T959V and it works fine, apparently not with this phone...
@Ian the Great.
In /dev/block/platform/msm_sdcc.1/by-name/ I have 3 devices: modem modemst1 modemst2
I did everything from an adb root shell.
I backed up all of them with dd.
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st1.ang2
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st2.ang2
-rw------- 1 root root 60227584 2016-11-29 11:59 modembak.ang2
But when I tried to overwrite modem with the new modem.bin I was blocked for some reason:
dd: /dev/block/platform/msm_sdcc.1/by-name/modem: Operation not permitted
I tried disabling selinux (and confirmed it was disabled) but it didn't help.
Lop3 said:
@Ian the Great.
In /dev/block/platform/msm_sdcc.1/by-name/ I have 3 devices: modem modemst1 modemst2
I did everything from an adb root shell.
I backed up all of them with dd.
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st1.ang2
-rw------- 1 root root 3145728 2016-11-29 12:00 modembak-st2.ang2
-rw------- 1 root root 60227584 2016-11-29 11:59 modembak.ang2
But when I tried to overwrite modem with the new modem.bin I was blocked for some reason:
dd: /dev/block/platform/msm_sdcc.1/by-name/modem: Operation not permitted
I tried disabling selinux (and confirmed it was disabled) but it didn't help.
Click to expand...
Click to collapse
I'm not sure It was quite awhile back when I needed this. Sounds like your device is a little different than what I was using when I posted this.
In general from what i remember there number of things can block you from writing there. You may need to be on stock recovery and kernel. Having modified recovery like twrp or custom kernel can alert device so modem won't stick after reboot or it won't write at all .
Another idea to possibly try is, from the stock firmware, extract the file named NON-HLOS.bin and write that to apnhlos slot.
in other words instead of
dd if=/sdcard/modem.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
The command would be something like
dd if=/sdcard/NON-HLOS.bin of=/dev/block/platform/msm_sdcc.1/by-name/apnhlos
I'm pretty sure I was able update modem on newer samsung with just the NON-HLOS file, but can't remember exactly which phone I had and command used. Backing up apnhlos like you did with modem is probably smart.
Also If you are using adb from a pc why not just use Odin to flash it? Probably easier than dd method.
can this work for other brands ? specialy note 3 neo ?