Related
Hey everyone. Just got the Samsung Nexus S... and I've got a question.
I've read on these forums that the OTA makes it so you have to flash CWM recovery everytime you want to reboot into recovery to flash a ROM and that it's more difficult to root.
Should I flash the OTA then root or root prior to OTA?
Thanks in advance.
m00n
Sent from my SGH-T959 using XDA App
You should get the OTA before you root and it is very easy to make the root stick. I did it with root explorer but I heard you can do it without it.
Sent from my Nexus S using XDA App
tominater12 said:
You should get the OTA before you root and it is very easy to make the root stick. I did it with root explorer but I heard you can do it without it.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Which method did you use to root. And how did you manage to use root explore to get root access when root explorer needs root access first in order to operate? Thanks for your response.
Sent from my SGH-T959 using XDA App
No after you root you can use root explorer to make the recovery stick and there are like 5 guides on how to root on every OS in the android development sub-section. (They are stickied)
m00nshake said:
Which method did you use to root. And how did you manage to use root explore to get root access when root explorer needs root access first in order to operate? Thanks for your response.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
Thanks again for your response and for the clarification about using root explorer. I have read the stickies regarding rooting the phone, and because there are a few, I was wondering which method you used. I've read that superboot is the easiest and that you can rename a particular system file so the recovery sticks. Thanks again for your response.
Sent from my SGH-T959 using XDA App
m00nshake said:
Thanks again for your response and for the clarification about using root explorer. I have read the stickies regarding rooting the phone, and because there are a few, I was wondering which method you used. I've read that superboot is the easiest and that you can rename a particular system file so the recovery sticks. Thanks again for your response.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Get the OTA.
Apply it.
Boot up to make sure everything is ok. Then boot to bootloader
fastboot oem unlock, confirm it, wipes everything including your internal sd.
flash clockwork mod recovery.
go to clockwork mod recovery from bootloader menu.
mount "internal sd" copy the su-2.3.6.1-ef-signed.zip you downloaded (from the guide) to your internal sd.
unmount internal sd.
mount /system
flash the su-2.3.6.1-ef-signed.zip file.
reboot phone as normal.
login to your gmail account. go to market, download a rooted app like titanium backup free version, and also download rom manager, and buy/get root explorer.
install all those make sure super user is granted and works.
use root explorer to rename/delete the file in: /etc/recovery.sh file or whatever it's actually called.
go to rom manager, and flash the latest clockworkmod recovery (3.0.0.5)
turn off phone and boot to recovery and make sure it's clockwork mod 3.0.0.5, if it is, you're set.
Very helpful post, nxt. Thank you very much.
Sent from my Nexus S using XDA App
nxt said:
Get the OTA.
Apply it.
Boot up to make sure everything is ok. Then boot to bootloader
fastboot oem unlock, confirm it, wipes everything including your internal sd.
flash clockwork mod recovery.
go to clockwork mod recovery from bootloader menu.
mount "internal sd" copy the su-2.3.6.1-ef-signed.zip you downloaded (from the guide) to your internal sd.
unmount internal sd.
mount /system
flash the su-2.3.6.1-ef-signed.zip file.
reboot phone as normal.
login to your gmail account. go to market, download a rooted app like titanium backup free version, and also download rom manager, and buy/get root explorer.
install all those make sure super user is granted and works.
use root explorer to rename/delete the file in: /etc/recovery.sh file or whatever it's actually called.
go to rom manager, and flash the latest clockworkmod recovery (3.0.0.5)
turn off phone and boot to recovery and make sure it's clockwork mod 3.0.0.5, if it is, you're set.
Click to expand...
Click to collapse
Don't you need the android sdk?
tominater12 said:
Don't you need the android sdk?
Click to expand...
Click to collapse
Yes, you need to have the Android SDK properly installed and you're able to do a 'fastboot devices' command properly and your Serial number comes up.
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Questions belong in Q&A. Moved
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
i cant c y u would have to unroot, it shouldnt matter as apps dont care if it is rooted or unrooted, correction some apps u have to b rooted to work properly.
do u actually get an error message when trying to install an app
the only way is to restore back to stock, or if u just rooted ur stock firmware, meaning u didnt flash a rom, u can try flashing the system.img file, that might work but i never heard of any1 doing that
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
artisticcheese said:
Yes, application refuses to work telling me that "rooted" phones are not supported. So basically it installs, checks if phone is rooted and refuses to proceed. I hoped I can flash something in CMW to temporarely unroot, then run application, let it do it one time thing (I need to run this application only once successfully) and then I root back in CWM again.
Click to expand...
Click to collapse
dont think there is a temporary unroot method, going back to stock was the true method to unrooting, which app were u trying to install.
u can trying going back to stock, installing app, let it do its thing, backup with tibu or some other backup, reroot and then restore backup of app.....maybe wont work as restoring a backup is actually reinstalling the app
edit: try this i havent so try at ur own risk http://www.thespicygadgematics.com/2012/06/how-to-easily-unroot-any-android-phone.html it seems easy enough, i didnt think it was possible but it seems to b
artisticcheese said:
Hello,
I need to unroot by ICS ROM temporarily so I can install and run certain application, how do I do that with minimum amount of work?
Thanks,
G
Click to expand...
Click to collapse
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
cschmitt said:
Using root explorer or ES File Explorer, mount system as r/w, delete /system/app/Superuser.apk, /system/bin/su or /system/xbin/su (it will be in one of those two places), and then reboot. done.
Click to expand...
Click to collapse
Thanks,
How do I root back after that though?
vincom said:
thats deleting the app the rooted the phone, but does it actually undo the rooting process, the system files the app changed to make it rooted r still there, the way to check is if u do delete su app, c if root explorer can can mount ur system folder to r/w, or op can c if it the app does install after deleting su.
actually u need su to grant su, so that might not b a good test
Click to expand...
Click to collapse
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
artisticcheese said:
Thanks,
How do I root back after that though?
Click to expand...
Click to collapse
Flash superuser zip in cwm.
cschmitt said:
The superuser cwm zip installs su and superuser.apk, that's it. There are no other modified apps.
You can remove busy box also if you like, but it's not much use without su.
Click to expand...
Click to collapse
kool. i learn something everyday
There is cool app in Playstore (free) which allows rooting/unrooting with no reboots and other complicated steps
FYI
https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0
Voodoo OTA can do a temp unroot as well. The Flixter app will not allow you to stream movis on a rooted phone. I used Voodoo to temp unroot then went back into Flixter and it started to play the movie.
I use an app called Temp root remover
It allows you to temporarly unroot and reroot in a matter of seconds
hi,
i did a big mistake. I wanted to install some vpn apps, which requires write permission on /system. I downloaded root explorer und tried to set all permissions for the system folder. But the app stills lacks the wanted permissions, so i started root explorer again and additionally checked the checkboxes under "special permissions". After doing that android crashed, the "systemui" process crashed and restarted and crashed ...
I rebootet the device, but i only see "google" and then comes a reboot and the device boots into recovery (TWRP 2.6.3.4). I already tried the "fix permissions" under advanced, but it didn't helped.
Is there any way to fix whatever i did wrong and not lose any data?
Any help would be greatly appreciated
Greetings k1x1987
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
d
jyuuken said:
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I don't want to miss something this time and complety brick my device. Could you/anybody tell me exactly what and how do flash to recover my device?
I did all the rooting stuff with the "Nexus Root Toolkit" program and followed strictly guides, except this time
Do i have to flash the rom with ADB? which file(s) should i flash system.img only? Or i have to flash more files?
A short noob guide would be really appreciated :good:
Greetings k1x1987
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
es0tericcha0s said:
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
Click to expand...
Click to collapse
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
k1x1987 said:
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
Click to expand...
Click to collapse
Just flash the system.img in fastboot.
Most devs recommend wiping /system first.
fastboot erase system
fastboot flash system system.img
I would also erase cache too.
fastboot erase cache
That will clear the cache, not the dalvik, but think that should be enough to get going.
...and once it is fixed, never change system permissions again.... Same a Linux, never change permissions at /root
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
k1x1987 said:
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
Click to expand...
Click to collapse
Using fastboot, flash the cache image from the factory image, fastboot flash cache cache.img
^ That should do the trick. If not, well, let's not go there yet. The cache should fix it. If that does, do yourself a favor and back up your EFS folder and save it somewhere safe. Either use TWRP or flash the EFS backup tool from here: http://forum.xda-developers.com/showthread.php?t=2514095
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
So long story short I got myself in a reboot loop. I have an unlocked bootloader and TWRP installed on my MHA-L29C636B110 and it's always rebooting itself until it reaches back to Huawei eRecovery. I tried everything I could by factory resetting on TWRP, reflashing SuperSU and data files, and still end up in constant reboot loops until I reach eRecovery. Please someone help me resolve this issue!
Did you try wipe+reflash the Rom?
If your afraid you'll lose data just backup using twrp and then use helium once your set to restore apps and data from the backup.
IronSingh said:
Did you try wipe+reflash the Rom?
If your afraid you'll lose data just backup using twrp and then use helium once your set to restore apps and data from the backup.
Click to expand...
Click to collapse
I can't seem to find a ROM for MHA-L29C636B110. Also I don't have a SD card so if I do find the ROM, do I just flash it on TWRP? I tried everything I could think of and it always leads me back to reboot loop to eRecovery
Ben_Li said:
I can't seem to find a ROM for MHA-L29C636B110. Also I don't have a SD card so if I do find the ROM, do I just flash it on TWRP? I tried everything I could think of and it always leads me back to reboot loop to eRecovery
Click to expand...
Click to collapse
Which SuperSU did you install?
And did you decrypt first if the supersu you're installing needs decryption?
If you didn't 'Format Data' in TWRP and SuperSU removes encryption you're trying to boot with an encrypted /data partition which doesn't decrypt.
Ben_Li said:
I can't seem to find a ROM for MHA-L29C636B110. Also I don't have a SD card so if I do find the ROM, do I just flash it on TWRP? I tried everything I could think of and it always leads me back to reboot loop to eRecovery
Click to expand...
Click to collapse
Do you want to install custom Rom or do you want stock Rom. If you want stock Rom why did you root?
Also as ante0 asked did you decrypt?
ante0 said:
Which SuperSU did you install?
And did you decrypt first if the supersu you're installing needs decryption?
If you didn't 'Format Data' in TWRP and SuperSU removes encryption you're trying to boot with an encrypted /data partition which doesn't decrypt.
Click to expand...
Click to collapse
So at first, I flash the SuperSU files and data files from here: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. It worked perfectly fine and my storage was decrypted. But then i got into another issue so I rebooted into twrp, wiped, format data, and installed the files again (SuperSU and both data files) from the same link above. If my phone is already decrypted, and I wiped and format the data, I only need to flash SuperSU and the data files? I'm lost and this is a new phone.
Can you please give me a step by step rundown of what I need to do to get my phone back working. Again, the phone is a MHA-L29C636B110 with the bootloader unlocked, TWRP 3.1.0-1-hi3660 installed. Whenever I flash something or even factory reset it reboots for a while and then goes back to eRecovery.
IronSingh said:
Do you want to install custom Rom or do you want stock Rom. If you want stock Rom why did you root?
Also as ante0 asked did you decrypt?
Click to expand...
Click to collapse
At first everything went well and I decrypted the data. I wanted a custom ROM but I knew it would be a lot of work and I could get into a lot of problems. But then the SuperSU kept giving me the notification that the binary needs to be updated. So I downloaded the SuperSU v2.46 update on the Chainfires website and gave me a bootloop. I then went back to TWRP, wiped, format data, and sideload flashed the SuperSU files and both data files from: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986 which ended up giving me a reboot loop back to eRecovery.
Ok
Do This.
nicenice00 said:
If your Model is MHA-L29 you can try this.
Load and Exract to SD card .
Push Power button and vol+/vol- to recovery mode.
I think it can help you. (Sorry, my english isn't good)
drive.google.com/open?id=0B9GG_Oe0gQDyUWlCS3lTRm5IOUE
Click to expand...
Click to collapse
Download the file extract it to your internal Storage.
So there should be a Folder in your /sdcard folder named dload and there should be update.app file in that folder.
while you are in TWRP you can simply do adb push /dload /sdcard/dload from command line
Ben_Li said:
So at first, I flash the SuperSU files and data files from here: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. It worked perfectly fine and my storage was decrypted. But then i got into another issue so I rebooted into twrp, wiped, format data, and installed the files again (SuperSU and both data files) from the same link above. If my phone is already decrypted, and I wiped and format the data, I only need to flash SuperSU and the data files? I'm lost and this is a new phone.
Can you please give me a step by step rundown of what I need to do to get my phone back working. Again, the phone is a MHA-L29C636B110 with the bootloader unlocked, TWRP 3.1.0-1-hi3660 installed. Whenever I flash something or even factory reset it reboots for a while and then goes back to eRecovery.
Click to expand...
Click to collapse
what did you wipe (Other than tapping the 'Format Data' button)?
If dload update doesn't fix it, as mentioned above, you could (You should!!) update to B181 using this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Download HWOTA_2017050101_Base.zip, HWOTA_2017050101_Windows.zip (if you're on Windows), HWOTA_2017050101_Linux.zip (If you're on Linux) and HWOTA_2017050101_MHA.zip.
Extract all to the same folder.
MHA-L29C636B181 firmware: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v85049/f2/full/update.zip
MHA-L29C636B181 public data zip: http://update.hicloud.com:8180/TDS/...49/f2/full/public/update_data_full_public.zip
MHA-L29C636B181 hw data zip: http://update.hicloud.com:8180/TDS/...hw_spcseas/update_full_MHA-L29_hw_spcseas.zip
Place update.zip, public zip and hw zip in HWOTA/update/ folder.
Rename update_data_full_public.zip to update_data_public.zip
Rename update_full_MHA-L29_hw_spcseas.zip to update_all_hw.zip
Run update.bat if windows, ./update.sh from terminal if Linux.
Put phone in Download mode (Vol down+power+usb plugged in).
Select Same Brand Update when it asks.
Select Script Update Directory when it asks.
If all went well you should be on B181.
IronSingh said:
Ok
Do This.
Download the file extract it to your internal Storage.
So there should be a Folder in your /sdcard folder named dload and there should be update.app file in that folder.
while you are in TWRP you can simply do adb push /dload /sdcard/dload from command line
Click to expand...
Click to collapse
So there is a file named TWRP in the /sdcard when I am on TWRP. So I move the dload.rar into the /sdcard/TWRP then flash it? I apologize if this sounds stupid I want clear specifications so I won't fall under any more problems
No you have to extract dload on your computer the move that folder to the phone.
This will Restock your device and lock it.
If you don't want to do that, I suggest you download RomAur from here
Download the following files
RomAur B182 v1.5
KangVip Framework for v1.5
L29C636 Data Files B181
Then copy them to your Internal or External Drive
Then follow from Step 7
7 - Make a FULL Wipe if come from another FW, before installing the ROM on TWRP(DALVIK-CACHE,CACHE,DATA,SYSTEM)
8 - Install Rom
9 - Install Data Files
10 - Reboot
11 - Install KangVip - Optional
12 - Enjoy
IronSingh said:
No you have to extract dload on your computer the move that folder to the phone.
This will Restock your device and lock it.
If you don't want to do that, I suggest you download RomAur from here
Download the following files
RomAur B182 v1.5
KangVip Framework for v1.5
L29C636 Data Files B181
Then copy them to your Internal or External Drive
Then follow from Step 7
7 - Make a FULL Wipe if come from another FW, before installing the ROM on TWRP(DALVIK-CACHE,CACHE,DATA,SYSTEM)
8 - Install Rom
9 - Install Data Files
10 - Reboot
11 - Install KangVip - Optional
12 - Enjoy
Click to expand...
Click to collapse
THANK YOU SO MUCH IT WORKED! In all honestly, I cannot thank you enough as I've had issues with this phone for the past 3 days and it's been messing with my head. Again, thank you so much for helping me out today! You are a great member of this wonderful community
Ben_Li said:
THANK YOU SO MUCH IT WORKED! In all honestly, I cannot thank you enough as I've had issues with this phone for the past 3 days and it's been messing with my head. Again, thank you so much for helping me out today! You are a great member of this wonderful community
Click to expand...
Click to collapse
Just out of curiosity did you get the custom Rom or did you go stock?
It's no problem,I was once where you are. I wanst born with knowledge someone shared it with me and the least I can do is share it back.
I flashed the custom ROM. I tried it at first but I didn't wipe the system. This time I did and it worked like a charm thank you for everything I look forward using this device for the next few years
You can done follow link .
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
newyesor said:
You can done follow link .
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Click to expand...
Click to collapse
Everything was fix thank you though
That link is a good way for comeback .
Sorry guys i have same problem but with L09, can someone give me files for L09 ?
Thanks a lot