Affichage des articles dont le libellé est tried. Afficher tous les articles
Affichage des articles dont le libellé est tried. Afficher tous les articles

mardi 25 août 2015

Tried to return to stock, soft bricked my phone.



I tried a method which made me flash a stock RUU, it came up with certification errors.
os- 2.24.401.8
Relocked
Stock recovery
S-ON
When I connect my phone to my Mac, "/.adb devices" returns a blank, but "/.fastboot devices" works.

What can I do to get my device back to stock?



ME176CX: Unlocking the bootloader -- has someone tried this?



Hi,

I found this and asking me, whether it may THAT easy to get rid of our problems
or it will completely brick the device:

https://wiki.cyanogenmod.org/w/Templ...oot_oem_unlock

Best regards,
tuxic

PS: See also here:
http://forum.xda-developers.com/nexu...bling-t2951312



vendredi 21 août 2015

Tried replacing my screen, need some advice



I think I'm out of luck but I figured I'd post here before giving up on it. Cracked my screen, got a replacement, when I was putting it back together I accidentally broke the plastic part that covers the pins that hold the screen cable in place (see the picture). I am guessing I need an entire new motherboard.

MB" width="240" height="360

I thought it was that clip that released the connector, it clearly wasn't. This off itself wasn't actually an issue, I got the phone all the way back together and working when I realized I didnt use enough tape to hole the screen to the frame and it was coming apart. When I was putting the phone back together I accidentally bent one of the pins on the connector and that was the end of it. I tried carefully bending it back it only made it worse. I was beyond frustrated to have spent about 0 and 20 hours (I originally tried a LOCA glass replacement and cut one of the ribbons while trying to separate the cracked glass) to fix the thing and 1 bent pin turned the entire thing to a paperweight.

Please save your "should have let a professional do it" comments.



I have tried everything , i need YOUR HELP!



It works again!



mercredi 19 août 2015

Softbricked after AT&T OTA, tried many things, any help appreciated



Had stock AT&T SGH-I747 at Android 4.2.2 rooted with chainfire working fine. Today an update installed automatically and now I'm dead.

At first, it would show the Samsung logo and maybe another, then just go black.

Now normal booting, or attempting to boot into recovery gives: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."

If attempt to boot into download mode, it succeeds. But everything will end up with "FAIL!" in Odin and show "fused 3 > binary 0" on the phone. I've tried multiple Odins: v3.10.6, 3.09, 3.07 and multiple recoveries (Clockwork 6.0.4.7, etc.) and stock ROMS (UCALG1, UCDLK3).

Even Kies "Firmware Upgrade and Initialiasion" option, where you enter in SGH-I747 and the serial number will go through all the motions and then fail, with the same "fused" message showing on the phone.

Grendelin had the most similar situation (I can't post external links yet, but you can get to it at http:__androidforums.comthreads_at-t-gs3-at-t-issues-after-downloading-newest-update.860382_ by replacing _'s with /'s) as me but the difference is that he was able to flash a recovery image which led to further restoration.

Please help. If it's not possible to recover this, I would just like to get a couple years' worth of pictures from /sdcard/DCIM/*.



dimanche 16 août 2015

ADB Recovery Mode won't work ( Tried Everything ! )



Hello everyone. As you know, ever since the whole stagefright bug thing and google & other companies said they will be launching regular OTA updates on a monthly basis.

I'm using window 8.1 x64

Android version Lollipop 5.1.1 LMY48B

USB debugging and MTP are ENABLED.

My nexus 5 is NOT rooted, I have some system apps DISABLED from app settings, I HAD CUSTOM recovery (latest twrp) to use teenf00t's (Nexus 5 real volume booster).

But now STOCK recovery is flashed and volume xml paths files were set back to default

NO CUTOM ROM's or anything else.

Still couldn't use OTA update normally :(

And since I can't download & flash a whole new system img and back up & restore my data just for a 10 mb update every month, I need to ADB sideload the OTA update , and here comes the problem .

Obviously, when my nexus is connected when it's turned on or in bootloader, nothing is wrong. As soon as I get into recovery mode and the device becomes undetected.

I tried EVERYTHING I could find which is :

1- Got the latest Minimal ADB & Fastboot installed

2- Used latest ADB & drivers 15 seconds installer

3- Latest google USB drivers

4- Lg united mobile driver

5- Manually assign composite ADB interface driver to nexus in "portable devices" when it's connected in recovery mode.

6- Modify "android_winusb.inf" file with the hardware ID of the nexus found in the inactive "composite ADB interface" driver when connected in recovery, and installing it using advanced windows 8 boot to remove digital signature verification requirement :

In the x64 & x86 "nexus generic" tab of inf file I replaced this line :

%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01

with this :

%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&REV_0232&MI_01

7- I tried different USB ports

8- Made sure ADB runs in compatibility mode with windows 8 but its process still shows "ADB 32"

And ofc, when removing or installing drivers or ADB, I made sure the previous ones were uninstalled and restarted pc when necessary.


What the hell can I do for this damn thing to work ??!! :eek: :mad:



Has anyone tried unlocking the basebands through this guide yet?



Source: http://forum.xda-developers.com/gala...ds-to-t2886059

Use your phone anywhere


Have you ever wondered why your phone doesn't work nearly as well when you travel?
Or tried to change carriers only to be told that you'd need to buy a different version of your high end phone for it to work properly?
It's happened to a lot of us and there is no good reason for it. Other than greedy carriers that is.

Most phones should work on a lot more bands. And have good reception when roaming. The S5 in particular is one of the first phones that is fully capable of working on every GSM and LTE frequency in the world. So.. why doesn't it actually do that? Well because your carrier doesn't want to make it easy for you to leave. And because Samsung and other manufacturers want to force you to buy a new phone everytime you change telephone companies. So they put restrictions in your phone to limit how many bands you can use. Wouldn't you rather have your phone work on all carriers?

This guide will show you how to do that.


Okay okay, I'm convinced already.
I don't want to read any more. I'm a power user (or reckless).. just show me how to do the hack!




The lawyers made us do it

We have to post an obligatory warning

We don't think that this mod will cause you any problems. But we can't guarantee that.
You assume all risks if you proceed, including the risk that your phone might object, meltdown, brick or void your warranty.




Quick Start Guide

CLICK TO HIDE CONTENT

This mod makes a night and day difference when you travel, roam or change carriers. It's a dramatic improvement.
But it's not an easy, one click process. There are a lot of steps to add this to your phone.

And due to minor differences between brands (finding the hidden USB settings menu), it may take a little experimenting to succeed. So this mod won't be for everyone. But if you have some patience, you can add a lot of bands to your phone. Just post in the thread and we'll figure it out as we go. This Quick Start guide will show you how to add bands to a Samsung S5. It can also be used on dozens of other Samsung, Sony, LG, HTC, Nexus, etc phones with minor differences in the steps here. I'll add comments for other brands when I have them. If you get stuck anywhere, post in the thread for guidance.



The Mod:

Step by step guide

1. You need a phone with a Qualcomm processor that has been rooted.
2. If you need to root your phone, click on the button below for guidance. Otherwise skip to step 3.
CLICK TO HIDE CONTENT

How to root your phone

There are a lot of XDA threads explaining how to root your phone. Towel root will work with almost all phones (and doesn't increment the Samsung Knox flag, if you care about that). You need a pre June 6, 2014 firmware build for the original Towel Root method to work. Otherwise, downgrade to an older firmware first (Use Odin software for Samsung), then root with Towel root. Or you can look for the modified Towel root that is said to work with newer firmware (unconfirmed by me). Another excellent root method is CF-Autoroot which works with most popular phones.

3. If you are running a custom ROM and kernel that were compiled from source code, well done. Skip to Step 4.
Otherwise click on the button below for more information.
CLICK TO HIDE CONTENT

Custom ROM & kernel

Qualcomm apparently reads XDA too and appears to have added some anti-tamper code to keep this hack or similiar mods from working. Drat! Until we figure out exactly what they added, you will need a custom ROM & kernel for this mod to work. This works because a kernel made from scratch won't have the anti-tamper code in it. Probably you only need the custom kernel and not the full custom ROM (unconfirmed). Configurations known to work include CM11 + Ark kernel. And Phoenix V3 ROM + kernel. But any custom ROM + kernel that is made from source, rather than modified stock will probably work fine. If anyone is still running Jelly Bean (firmware versions 4.2.2. and below), you probably don't have the anti-tamper code and won't need a custom ROM or kernel.

You can go ahead and try adding bands without a custom kernel. It probably won't work, but you can leave the custom kernel as the very last step if you want to and see if adding bands without a custom kernel succeeds. Note that installing a custom kernel on a Samsung phone will increment the Knox flag if you care about that (the Knox flag might affect a warranty claim).

If you have a Verizon or ATT phone, you should know that these two carriers do something that almost no other carrier does. These two carriers lock the bootloader which prevents installing a custom kernel in the normal manner. The Safestrap program can emulate another ROM, but we won't know if that is sufficient or not for this mod. If you are with Verizon or ATT, let us know if you were able to add bands or not.

Follow this link for details about the Phoenix ROM + kernel for the S5.
You can find CM11 downloads here for various phones. Then look for an XDA support thread for your phone.
Ark kernel

4. Download and install QPST. We will use this program to edit your phone settings. This runs best on Windows XP. But you can use Windows 7 (and probably Win 8, if you must). Right click on setup.exe (not the .msi file) and choose run as adminstrator.

5. Download and install QXDM. We will use this program to "write enable" your phone settings. QXDM won't work unless QPST is also installed, so you need both programs. Right click on setup.exe and choose run as administrator to install.
6. Open the USB settings screen on your phone. Change USB from AP to CP. And USB settings from MTP + ADB to RNDIS + DM + Modem mode (after you have finished making edits in your phone's memory, remember to revert the original settings in this screen).

This is the hardest part of this mod as the USB setting menu is usually hidden and the method to access it is slightly different on some brands. For the S5, you can open it by dialing *#0808# . Other phones may use *#7284# , *#8778# , *#*#8778#*#* , ##3424# or something else entirely. If those codes don't work on your phone, try a Google search for keywords like those below to find out how to open the USB settings menu for your phone:

Google: USB settings <brand> xda
Google: how to use QPST <brand> xda

6a. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
For Sony, the following CLI commands have been reported to work. These may or may not work for other brands.
You can enter these using a terminal emulator app or from an adb shell.

From terminal emulator:
Code:
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable

Or using adb:
Code:
adb start-server
adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable
exit

If you use either of these, remember to revert the USB settings after you finish your phone edits. e.g.
Code:
su
setprop persist.usb.eng 0
setprop usb.rndis.enable 0
echo 0 > /sys/class/usb_composite/modem/enable

6b. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an LGE phone, try the dialer codes here and change the USB mode from AP to CP (Modem mode). If that doesn't work, then it has been reported that the following commands will also enable diagnostic mode for you:
Code:
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb

6c. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an HTC phone, this diagnostic driver may work for your phone.

6d. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an Opo phone, it been reported that the following commands will enable diagnostic mode for your phone.

Code:
su
setprop sys.usb.config diag,adb

6e. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have a custom kernel installed (which has permissive permissions) then you can probably enable diagnostic USB mode from the EFS Professional program menu.

6f. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you cannot find out how to access the USB settings on your phone anywhere, you may be able to force diagnostic mode by installing the Windows USB drivers for your phone in advance. You can download Motorola /Sony/ LG/ HTC/ ASUS/ Huawei /Google, etc drivers here. Otherwise do a Google /XDA search to find USB drivers for your phone. Install the USB driver.

7. Enable USB debugging on your phone. This is a hidden menu. Look for Settings menu > System > About Device > Developer. If you don't see a Developer option, then tap on the firmware build number about ten times to unhide it.
8. Connect your phone to your phone to an USB port on your PC. Do not use an USB hub, connect directly to your computer. Windows will install a diagnostic driver.
9. Open the Windows (Control panel) Device Manager and confirm that you see something like "Samsung Mobile USB Serial Port" listed there. If you see a yellow triangle there > right click and update the driver.

10. Open the "QPST Configuration" program > Ports > Add new port > choose the port labeled diagnostic > OK.
If you do not see a diagnostic port listed and you were not able to explictly able to set USB diagnostic mode earlier, then right click on the driver that Windows has assigned to your phone in the Windows (Control panel) Device Manager > Update Driver Software > Browse. Choose the folder where you extracted the USB driver that you downloaded for your phone. This forces Windows to use the downloaded driver.
11. Now select the QPST Start Clients > Software download > Backup > Start. This saves a backup copy of your phone's stock NV memory to your computer in case you need it later.
12. Navigate to the C:/Program Files/Qualcomm/QPST/bin folder.
13. Right click on ServiceProg.exe > run as administrator.
14. Choose Phone > Read from phone > UMTS System. This will show which 3G bands are currently enabled. Add checkmarks to the additional 3G bands that you would like to add. Resist the temptation to check everything unless you are prepared to troubleshoot possible issues with non-existant bands, slow boot times and other issues. Just add specific bands that you need for another carrier or are missing in the areas you travel. If you aren't sure what to add, then don't check any extra bands for now - you can always come back later after you find out which 3G bands you can actually make use of.

Either way, do not click write to phone yet. And do not close the Service Programming window either.

15. Before we write anything to your phone, we need to write enable the locations we are going to edit. Navigate to the C:/Program Files/Qualcomm/QXDM/bin folder.
16. Right click on QXDM.exe > run as administrator. If you are not adding any new 3G bands at this time, skip to step 21.
17. In the NV Browser window, scroll down to ID 01877 (aka NV 1877) > Read.
Then write "0" to NV 01877 with QXDM. This initializes (write enables) the item for QPST. We need to do the same for several more NV items.
18. Select ID 00441 > Read. > Write "0" to NV 00441 with QXDM. This initializes (write enables) the item for QPST.
19. Select ID 00946 > Read. > Write "0" to NV 00946 with QXDM. This initializes (write enables) the item for QPST.

20. Select ID 02954 > Read. > Write "0" to NV 02954 with QXDM. This initializes (write enables) the item for QPST.
21. If you do not intend to add any new LTE bands, skip to step 24. Otherwise,
Select ID 06828 > Read. > Write "0" to NV 06828 with QXDM. This initializes (write enables) the item for QPST.
22. Select ID 06829 > Read. > Write "0" to NV 06829 with QXDM. This initializes (write enables) the item for QPST.
23. If you wish to add LTE bands and have already calculated a custom value from the instructions in the thread, then use QXDM to write that value to both ID 06829 and ID 06829, writing one item at a time.
Otherwise, write (decimal) "17592185995263" to both ID 06828 and ID 06829, writing one item at a time. This will enable all LTE bands.
Note that LTE edits will only work if your firmware has an LTE modem. If you already have at least one LTE band active, then you are OK. If your current firmware is from a carrier that does not use LTE at all, then you'll also need to update your modem to an LTE capable version as well.
24. Now go back to the Service Programming window that you left open. If you added any new 3G bands, click on write to phone to write the current selection of 3G bands to your phone. Otherwise do not click write, simply continue on to the next step.

25. You are now finished editing the NV values in your phone.
26. Reboot your phone.
27 In the Service Programming screen, choose Phone > Read from phone > UMTS System to confirm that your new 3G band selection are persistent. If they revert and you don't have a custom kernel installed, this confirms that you will need a custom kernel for this mod to work.
28. In the QXDM NV Browser screen, scroll down to ID 06828 > Read. Note the value.
29. In the QXDM NV Browser screen, scroll down to ID 06829 > Read. Note the value.
ID 06828 and ID 06829 should both show the custom value that you wrote. i.e. "17592185995263" (or hex "0xFFFFFFF3FFF") or the custom value, if you had used one.

30. Remember to change your USB settings back to normal mode, e.g. on the S5, dial *#0808# again and choose USB = AP and USB Settings = MTP + ADB > Click OK.
31. Celebrate! And let us know about your success (or sticking points).
32. You can test your results by checking whether your phone uses the new bands when you roam onto other systems that use them. Or if you have a SIM card for an alternate carrier. To tell if your phone is using the new bands, you can look at the current band being used in the Service menu or with various apps, e.g. LTE Discovery.

.


So now what?

Well, if you decided to jump in and follow the Quick Start Guide.. that's it. The Quick Start Guide has everything that you need to add new bands to your phone. Unless you run into difficulties, you don't need anything else. The guide is a bit terse as I don't have a lot of spare time to rewrite or polish it. But all of the important information is there.

If something doesn't make sense or you get stuck somewhere, you can (and should) try a quick search for details. If that doesn't resolve your issue, then post in this thread for help. If you want to learn more about how this works, why more bands is a good thing. Or how to make custom edits that choose particular frequency bands, then keep reading this post and the rest of the thread.

This is a proven working method, despite a few trolls claiming otherwise. It's also new territory and there are model specific quirks.
If you run into problems, most likely you missed a step somewhere. Less likely, you may have discovered something new that needs to be unraveled.

The purpose of this thread is to discuss new findings and suggest ways to improve this method.
This is not a support thread, although if you make an effort to provide enough detail about your situation, someone will probably try to help you.




Is this mod hard to do?

No. There really isn't anything hard about it. But it's not a one click kind of mod either. These are recent discoveries and there are a lot of steps needed to make these changes. Samsung doesn't want to make it easy for you - they'd rather sell you another phone. In particular, there is one hidden menu (USB settings) that is hard to find because it's in a different place on almost every brand of phone. So we have to Google around for details and experiment a bit to find the hidden menu for some brands. But the mod works. If you have a little patience and don't get frustrated at temporary obstacles, then you can add bands to your phone!

One surprising finding was that people with older phones were having better results. Why? It seems that Qualcomm quietly added some anti-tamper code into recent Android versions to keep us from doing this. It's almost like they read our forum and know what we're trying to mod. But they wouldn't spy on us like that, would they?

We don't know where the anti tamper code was added yet but we found that we can avoid it on newer phones by installing a custom kernel & ROM. So until we discover where they added the anti tamper stuff, you also need a custom kernel & ROM (probably the custom kernel is the essential part) to make this mod work. Unless you happen to have an older phone that is still running Jelly bean (4.2.2) firmware. So that's it in a nutshell.



Okay. So give me a quick overview again

Our phones have artificial restrictions in them so that they only work properly on the original carrier. If you travel (roam) or change phone companies, your phone won't work 100% because it will have gaps in coverage. It will be missing some of the frequency bands that the other carrier uses. This isn't a technological limitation. It's just your wireless carrier siphoning more money out of your pocket by forcing you to buy a new phone when you change carriers.

This mod has a lot of steps in it, so it won't be for everyone. But if you have some patience or enjoy a challenge then it's a great way to really improve how well your phone works when you roam onto another carrier. There are three parts to this mod. You need:

1. A phone with a Qualcomm processor, that is rooted.
2. (For now) Install a custom ROM & kernel to get rid of the anti-tamper code
3. Edit six values in your phone's non volatile (NV) memory to enable a lot of additional frequency bands


That's it. It takes about thirty steps to do those three things but nothing really good ever turns out to be easy, right?



lundi 10 août 2015

Anyone tried Kodi with gear vr for S6?



I'm interested to know what the zoom out rate is in order to see the entire 16:9 movie screen.



samedi 8 août 2015

[HELP] WiFi not working (I tried almost everything !)



Hello everybody !

Ok, I am use to not ask any help, and to find out by myself. But I have to admit I don't have any idea remaining to solve this problem.
Let me explain you the situation :

I explain everything with details to not waste your time when you will help me ! :)

When I first bought my Zenfone, everything worked properly. Then, I decided to flash a Custom ROM (to remove the bloatware, and to get the others optimizations). So what I did :
- I unlocked the bootloader,
- I flashed TWRP,
- I installed my custom ROM (SuperZen R15, super clean install) => at this moment, everything is working perfectly,
- I installed a custom Kernel (ProjectT, v56) by fastboot => here we are, the problem just appeared.

At this moment, the WiFi issues appear. When I boot the phone, I can turn on the WiFi (in most cases), then, WiFi just turn off. It is impossible to activate it again. In the best case, I can switch on/off the WiFi, but as soon as I download something, the WiFi just turn off immediately. Often, I just don't detect any network. In the worse case, it is impossible to activate again the WiFi, the ON/OFF button is grey.

So here is what I tried to get it back :
1) put the standard kernel with my TWRP backup => no success
2) flash another ROM (CM12, Paranoid Android, Barebone,...etc) => no success
3) flash my whole TWRP backup (system + kernel) => no success
4) flash the official Asus ROM (recovery.img, system.img, boot.img, droidboot.img) => no success

At the moment, I started thinking that maybe the WiFi just "forgot" my WPA key. So I modified the build.prop :
5) modification of the build.prop by adding the line ro.securestorage.support=false (instead of "true") => no success
6) flash the last Asus update 2.20.40... => no success.
...

I haven't any idea remaining !So I need your help ! This problem seems very standard, but I just couldn't find any solution yet !

P.S : I almost forgot. I talked about the wiFi signal, but it is exactly the same for the bluetooth signal : working on first boot, then when I use it, it just stop working and disconnect itself, and then, impossible to activate it again (grey button)
=> My last idea was to flash the radio directly by TWRP, but I didn't find any radio files for the zenfone 2...

Many thanks for your help, and thank you for reading everything !! ;)
Max



Tried to Install TWRP, I think I deleted Android...



I was following originally this guide by a user who posted steps that would basically allow me to move all of my apps from my internal storage to external SD card. The link to the thread I had posted about this can be found here: http://forum.xda-developers.com/lg-l...2/post62245649

I managed to root my phone using the KingRoot method, right after, I installed Flashify, flashed the TeamWin Recovery Project, and right after, it automatically rebooted me. After that, I went to the reboot section, clicked on recovery, and than, it loaded me to an icon where the Android logo is opened from its belly with a red triangle with the ! mark inside the red triangle.

I am assuming that my Android OS was deleted, as I see I now have 3 GB of free internal storage space. I originally was running everything on stock. Is there any solution here? I did manage to install CM12.1, but I forgot to flash GAPPS, thus I had to manually download the Flashify and KingRoot APK's and ended up deleted CWM12.1 as it just seemed buggy.

At this point, I want to just go back to my normal Android, I am fine with using Stock, as long as I have free storage. Though, if using another ROM would be better (where battery life improvements and overall faster performances is always acceptable). I don't want to brick my phone, as it so far seems to be working.

I currently don't have any other backup phone on me, so I would love to solve these issues ASAP as I do need my phone to make calls and answer SMS Text Messages.

Thanks!



samedi 1 août 2015

Help tried first flash and it's gone wrong



Hi all

I downloaded the nexus root kit and also the xenon HD rom and gapps zip files. I followed the instructions word for word but have hit a snag. The rom has flashed OK and works but when it was trying to put the gaaps file on it said insufficient memory and wouldn't do it. So now when the nexus boots up I don't have Google play store on it.

I have tried Re flashing the gaaps file again but nexus root kit won't let me as it does not recognise the build number of the nexus anymore.

Am I ****ed lol



Tried Installing Cloudy G2 3.3, bricked my F320L



I flashed the rom, followed all the steps. Everything was perfect, didn't get any errors.

When it told me to reboot however, i did, and just got the LG logo followed by a persistent black screen of death.

The phone that i am using is LG G2 F320L. I am using TWRP Recovery. I am able to access recovery, and have done that several times since the issue, to wipe everything, reinstall, what not. Doesn't help. Even after a reinstall, the black screen after LG logo is there.

Can anyone help me out? :(