New factory image MMB29V released - Nexus 5 General

https://dl.google.com/dl/android/aosp/hammerhead-mmb29v-factory-62a68ee9.tgz go and get some'
Sent from my Nexus 5 using XDA Free mobile app

Thanks for the heads up. I think I'm going to wait for the OTA with this one. I'm hoping there's more than just security updates here, fingers crossed for some 800MHz LTE capability with my carrier.

dkconor said:
Thanks for the heads up. I think I'm going to wait for the OTA with this one. I'm hoping there's more than just security updates here, fingers crossed for some 800MHz LTE capability with my carrier.
Click to expand...
Click to collapse
I read they were going to fix the bug related to volume control arrows disappearing :fingers-crossed:

Kustaa said:
I read they were going to fix the bug related to volume control arrows disappearing :fingers-crossed:
Click to expand...
Click to collapse
Oh I hope that's true.. that has been driving me insane!

I flash it and rooted, but I can´t change build.prop anymore. strange.
edit: only one build prop editor worked. trough kernel auditor and throug explorer cant´t change.

Google Keyboard
error stop work

I just flash factory images without wipe. Everything worked fine as usual. But afterwards, I tried to flash the last twrp recovery, 3.0 but I can't flash it!!! After I flash it, via fastboot commands, when I try to enter recovey all I get is the stock recovery!!!
The other times I did this and twrp did flash ok!! Am I doing something wrong?!? Help me please!!

After flashing TWRP, are you booting directly to recovery using the buttons or are you rebooting the phone and then trying to enter recovery?

audit13 said:
After flashing TWRP, are you booting directly to recovery using the buttons or are you rebooting the phone and then trying to enter recovery?
Click to expand...
Click to collapse
I think I did both, and it didn't work on both methods after glashing two times...

I would try 2.8.7.1 instead of 3.0. I have seen a couple of posts from other XDA member with phones that work fine with 2.8.7.1 but not 3.0.

Hello! After flashing this, I've got Google Services battery drain again. Anyone else? Regards, Zagor

Hope it's the System UI memory leak fix...

the sound bar bug is not fixed

---------- Post added at 03:51 AM ---------- Previous post was at 03:51 AM ----------
[/COLOR]
onesolo said:
I just flash factory images without wipe. Everything worked fine as usual. But afterwards, I tried to flash the last twrp recovery, 3.0 but I can't flash it!!! After I flash it, via fastboot commands, when I try to enter recovey all I get is the stock recovery!!!
The other times I did this and twrp did flash ok!! Am I doing something wrong?!? Help me please!!
Click to expand...
Click to collapse
Recovery Fix -
Flash recovery in Fastboot
Use power button to manually power off
Reboot bootlader, then recovery. Voila.

Related

Problem with flashing & booting recovery? Go here!

Hey guys,
when I tried flashing CWM on my new HTC One it just booted in normal mode over and over.
I tried every recovery-image available and it nerver worked.
While playing around I finally got it working without flashing the recovery image to the boot partition!
No need to copy root files and CFW files before flashing the recovery!
Instructions
Unlock your device at http://www.htcdev.com/bootloader/
Reboot into bootloader
> fastboot flash boot boot.img - thanx to Paul O'Brien
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img - thanks to Flyhalf205
> fastboot erase cache
After this you should be able to enter recovery via bootloader or 'adb reboot recovery'.
The recovery image is CWM Touch 6.0.2.8 which worked great for me, didn't try the other ones right now.
I hope I could help
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Nekromantik said:
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Click to expand...
Click to collapse
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
zantekk said:
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
Click to expand...
Click to collapse
Ah ok.
only issue for me now is aroma freeze issues.
Nekromantik said:
Ah ok.
only issue for me now is aroma freeze issues.
Click to expand...
Click to collapse
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
zantekk said:
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
Click to expand...
Click to collapse
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Device still rebooting
Can't flash recovery
same here - no access to recovery so far
Same for me too
Why ?
Got a HTC One from Orange france, and NO RECOVERY seems to stick. That thing boots, but i cannot enter recovery
I've tried using the AiO-Kit to flash CWM touch and normal as well as TWRP as well as the two CWMs manually and then this method. Still can't get access to recovery though
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Lothaen said:
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you mean clearing the cache as mentioned in that thread I've tried it with no success
SoLdieR9312 said:
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Click to expand...
Click to collapse
Had the same problem again and again flashing TrickDroid on my HTC One (M7). Can confirm, that avoiding touch will relieve things but freezes can still occur. A few times I even could not reset the phone long-pressing the power + volume up buttons, means I was completely stuck on the frozen aroma screen (since a battery pull is not possible with this device). For anybody who may be in the same situation, try the "[FONT="Courier New]fastboot reboot[/FONT] command, this still came through and rebooted the device.
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
pwr2wh8 said:
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
Click to expand...
Click to collapse
Yes, worked for me. I had the same issue. While flashing Renovate rom, Aroma crapped out right at the end where it was installing the kernel. I was then stuck on boot image until i found this thread.
Also, for what it's worth, i thought I'd flash the boot image again after i got my device running again but it killed my wifi. I had to reflash the rom as wifi in settings was `out of order`....
//edit: okay. i've been able to reproduce the crashing. seems it's an aroma/rom issue (i couldn't tell one way or the other). what matters here is flashing boot image with the provided image does the trick. whatever magic it does, i'm able to flash cwm recovery 6.0.3.1 but I have to flash boot image before, else flashing recovery is fruitless.
anyways, thanks. this thread help me solve what i thought was `bricked` device.

[Q] Vivid with CM 10.1 Stops

I've installed the CM 10.1 to my vivid, I flashed the boot.img using fastboot usb, and installed the rom via TWRP 2.4.4.0. before any install i used the all the wipe functions im suppose too.
When it finally boots it works for like maybe a 1 sec and then reboots. What did I do wrong?
XxnubzxX said:
I've installed the CM 10.1 to my vivid, I flashed the boot.img using fastboot usb, and installed the rom via TWRP 2.4.4.0. before any install i used the all the wipe functions im suppose too.
When it finally boots it works for like maybe a 1 sec and then reboots. What did I do wrong?
Click to expand...
Click to collapse
Update: The start screen works until i select my language and press start.
XxnubzxX said:
Update: The start screen works until i select my language and press start.
Click to expand...
Click to collapse
Use wcx recovery in version 2.2 of hasoons toolkit. Wipe system, dalvik, cache, data, and do a factory reset all in wcx recovery then flash the rom then flash the correct gaps for cm10.1 or android 4.2.2 then go into the bootloader (advanced option) then flash the boot.img (fastboot flash boot boot.img)
bilibox said:
Use wcx recovery in version 2.2 of hasoons toolkit. Wipe system, dalvik, cache, data, and do a factory reset all in wcx recovery then flash the rom then flash the correct gaps for cm10.1 or android 4.2.2 then go into the bootloader (advanced option) then flash the boot.img (fastboot flash boot boot.img)
Click to expand...
Click to collapse
Still having the the issue, I took a video.
youtube(dot)com/watch?v=9RFd_FZI-1A
Too new of a member to post links.
I'll paypal anyone who can help fix this some money, amount depending on how hard the problem is.
XxnubzxX said:
Still having the the issue, I took a video.
youtube(dot)com/watch?v=9RFd_FZI-1A
Too new of a member to post links.
Click to expand...
Click to collapse
Says video is private
bilibox said:
Says video is private
Click to expand...
Click to collapse
Public now, I fixed it.
XxnubzxX said:
Public now, I fixed it.
Click to expand...
Click to collapse
Your device mobo is probably going bad and needs more power than usual to run it. Sorry. If i can get linux to boot I'll send a kernel your way to flash and see if it fixes the problem
Try overvolting the CPU, with an init.d script, that should stop it freezing up, init.d because you won't have a chance of doing it with an app
Sent from my One using xda app-developers app
In the bootloader boot a recovery if you are s-on
"fastboot boot recovery recovery.img"
Sultans thread (android12345*) his kernel thread has details on how to do it
If you are s-off just flash this. This has higher voltages. Maybe itll help ya
bilibox said:
Your device mobo is probably going bad and needs more power than usual to run it. Sorry. If i can get linux to boot I'll send a kernel your way to flash and see if it fixes the problem
Click to expand...
Click to collapse
Please send a kernal. Also, how would I flash it without S-off. Could this also cause digitizer issues? i've been seeing like a 10% line in my phones that spams touch now.
Please do I need to download any kernel to flash my HTC with cyanogenmod 10?
Sent from my HTC Velocity 4G X710s using xda app-developers app
tybaba08 said:
Please do I need to download any kernel to flash my HTC with cyanogenmod 10?
Sent from my HTC Velocity 4G X710s using xda app-developers app
Click to expand...
Click to collapse
Flash the boot.img in the rom.zip
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
XxnubzxX said:
Please send a kernal. Also, how would I flash it without S-off. Could this also cause digitizer issues? i've been seeing like a 10% line in my phones that spams touch now.
Click to expand...
Click to collapse
Last post of the first page I already attached the kernel. With a recovery.img in fastboot do "fastboot boot recovery (nameofimgfile).img" Its in android1234567's sultan kernel thread in the vivid development. all instructions are there

[Q] Xperia Z1 is recognized as "togari", Z Ultra

As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
HellRoot said:
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
Click to expand...
Click to collapse
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Sari95 said:
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Click to expand...
Click to collapse
well..i have never had problems with it being the recovery... what error does it make now?
HellRoot said:
well..i have never had problems with it being the recovery... what error does it make now?
Click to expand...
Click to collapse
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
[/COLOR]
Sari95 said:
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
Click to expand...
Click to collapse
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
HellRoot said:
[/COLOR]
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Sari95 said:
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
I had this problem when I try to flash with LB.
HellRoot said:
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Click to expand...
Click to collapse
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Sari95 said:
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Click to expand...
Click to collapse
good to hear hope you enjoy the CM.... if you want then please tell me how it is running.. performance, battery, camera etc
have a good day

[ROM] Stock rom kitkat 4.4.2 for T210R

Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes

N9208 updated to OL1

Hi guys, anyone updated to OL1? I tried to flash TWRP recovery or Philz recovery but both failed as seem nothing happen after flash... just the software status changed to custom now. please help, i need root very much
it says "recovery is not seandroid enforcing"
i have tried google but non fix my problem
I updated but he never tried to flash so can't help there. Trying to figure out what improvements it has.
casper1 said:
it says "recovery is not seandroid enforcing"
i have tried google but non fix my problem
Click to expand...
Click to collapse
that message appears everytime i boot to recovery; it means you aren't using a stock recovery. from power off, did you reboot holding the Home Button, Volume UP and Power Button all at the same time? that would boot you to recovery. From there, i would wipe caches or perform a factory reset if your phone does not boot up normally. by the way, this new release is available at sammobile.com for the N9208 with the BRI CSC code. i just downloaded it, but will hold off flashing till i'm sure it's rootable.
cortez.i said:
that message appears everytime i boot to recovery; it means you aren't using a stock recovery. by the way, this new release is available at sammobile.com for the N9208 with theBRI CSC code. i just downloaded it, but will hold off flashing till i'm sure it's rootable.
Click to expand...
Click to collapse
but if i tried to go back to recovery the next time, the stock 3e recovery still appears. could i still root it then, and how?
casper1 said:
but if i tried to go back to recovery the next time, the stock 3e recovery still appears. could i still root it then, and how?
Click to expand...
Click to collapse
read the recovery thread (where you posted the same questions) and look for post number 323; it suggests using an older bootloader to flash recovery and further in the thread i believe there's a link for "rootable" kernal from gundal. good luck!
---------- Post added at 04:07 PM ---------- Previous post was at 03:42 PM ----------
also wanted to know if you tried flashing the tar files that contained rooted kernels from the Original shipping firmware and the AOJ3 update.
casper1 said:
Hi guys, anyone updated to OL1? I tried to flash TWRP recovery or Philz recovery but both failed as seem nothing happen after flash... just the software status changed to custom now. please help, i need root very much
Click to expand...
Click to collapse
OL1 still rootable. But OK3 blocked non Samsung recovery. So you would need to downgrade bootloader to OK2.
Boot loop if you try to flash custom recovery without OK2 bootloader.
Mr. Gundal ..we love you!!
cortez.i said:
read the recovery thread (where you posted the same questions) and look for post number 323; it suggests using an older bootloader to flash recovery and further in the thread i believe there's a link for "rootable" kernal from gundal. good luck!
Thank you thank you... the Sboot solved the problem, appreciate that very much... i have been trying that for 2 days...
Click to expand...
Click to collapse

Categories

Resources