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

mercredi 19 mars 2014

[Q] i9505 possibly USB port broken need to go back to stock rom topic




Hi,

My problem is simple : I have an android i9505 under 4.2 which I rooted (I derooted just yesterday by trying things...) and that'all : never installed a ROM or anything else apart this root thing one day.

When i go to DOWNLOAD MODE it says "Custom" so the Samsung warranty can take it in charge, they say that I have to put it like it was before. Of course I don't have any mention of knox since i'm still in android 4.2

So I want to install a stock ROM but I CAN'T do that with ODIN : I tried 4 PC, 10 USB ports, all the drivers in the world, did a numerous wipe cache and stuff but nothing works : the device (in download mode or in normal btw) is not recognized. In the best cases I have a "unknown device" popping up but no version of Odin recognized the device.

Can I install a stock ROM from the SD CARD ? Because when I start in RECOVERY MODE i can see that i can "apply update from..." but all the tutorial says to install fro example "CWM" and choose "install from zip...". Of course I would like to keep a stock ROM and to not have a know Ox1

So to summarize I have :
- a Galaxy S4 i9505 working, NOT ROOTED (checked with "Root Checker Basic"
- with android 4.2
- apparently which is "Custom" but still the samsung touchwizz stock rom...
- NO WAY to make it work via Odin or anything else because the USB connection doesn't work at all
- an external SD card on what I can install stuff : CWM ? a STOCK ROM ?...

Thank you in advance, I passed hours and hours searching for solutions but now i'm quite desperate... :eek:





samedi 8 mars 2014

Stuck with a possibly bad bootloader topic




Hi all,

I posted this in the S3 specific forum but not getting a lot of traction there. Just picked up a refurbished AT&T Galaxy S3 (i747) and it appears to have the T-Mobile (T999) bootloader for some reason.

Here's what I've found model and version-wise...

System settings - About device:
Model number SGH-I747
Android version 4.1.2 (stock Touchwiz)
Build number I747ZSEMC1

Info app from Play store:
Boot loader version T999UVDMD5
Finger print samsung/d2vl/d2can:4.1.1/JRO03l/I747ZSEMC:user/release-keys
Product d2vl
Model SGH-I747

Download Mode shows T999 bootloader.

Putting a T-Mobile sim in registers on the network and for some reason I get H+, which I didn't think was possible with the I747 AT&T model. Don't have an AT&T sim to test with at the moment.

I've tried flashing the I747 4.1.2 bootloader but I get different error messages depending on which recovery I use to flash it.

Stock recovery:

Verifying update package...
E:signature verification failed
Installation aborted

Clockworkmod:

E:Error in (file path and name)
(Status 7)
Installation aborted.

TWRP:

E:Error executing updater binary in zip (file path and name)
Updating partition details...
Failed


I've also tried using the Cyanogenmod installer under Windows and it says that it installed successfully but Touchwiz is still there. I noticed a red triangle during the process as well so I suspected it wasn't working.

My primary concern right now is how can I fix this bootloader issue so I can get a more recent rom on it? Any suggestions?





dimanche 23 février 2014

Possibly broken device topic




I have an international Note 3 (n9005), running touchwiz on Android 4.3. I also have a custom recovery. I have stock restored ML3 firmware on it, but it does not work. Whenever it boots, it gives a notification saying that "Process system has stopped." After a few seconds, it crashes and reboots. The same thing happens with any ROM I flash on it. All of this started when I was running SlimKat. Randomly, it stopped recognizing the SIM. I had TWRP as a recovery. I tried to flash a ROM for the international version, but it thought I had the T-Mobile version of the phone. Ever since then, no matter how many restores I do or what ROM it runs, the phone cannot stay booted for more than 5 seconds.





lundi 10 février 2014

[Q] Phone possibly bricked, need help topic




SO using odin on my Samsung Galaxy s2x T989D it failed, and my phone could not do anything but bring me to the download mode screen and told me i had to put it in recovery mode and use kies. but i couldint go into recovery mode. afer using google i found a possible solution. I used odin to try and stock again. and that worked..kinda...now when i try and turn on my phone its a Tmobile loading screen, it used to be koodo, my phone wont go past this screen and still cant go into recovery mode. when i go into download mode it still says odin mode. :eek:





mercredi 29 janvier 2014

Unable to save pictures or screenshots: possibly due to corrupt storage? topic




tl;dr: I cannot save pictures or screenshots on my phone, as well as a few other small quirks, can someone help?


Hello XDA, I've just recently encountered a strange issue with my Nexus 5 and I was hoping one of you might be able to help me out. I'd like to have screenshots to break up the text wall, but due to the nature of my issue, that's out of the question.

So my big problem started about two days ago, when I wanted to flash the omnirom nightly (1/27 to be exact) to my phone.

While doing the factory reset before flashing the rom, TWRP got stuck (and I'm talking about 10 minutes) formatting /data not including internal media. I was left with no choice but to hold volume down and power and hope for the best. This is what I bet screwed things up. After that I tried again, and the formatting worked, and omnirom booted, but with the error message of something about device UIDs being inconsistent and recommending I format my data partition.

Well since the rom was a nightly, I felt like ignoring the message, but I did notice issues: I could install and uninstall apps, but none of them could really access the internal storage (for example, any attempts to save a picture, like through chrome, would fail. I also couldn't restore from titanium backup. Connecting to my pc would not display my files).

Dismayed, I obeyed the message and did a full wipe of the data partition and tried again (not just the factory reset one, but the full wipe of /data, and don't worry, I could still backup using ADB pull so I haven't lost anything). This caused the UID error message to go away but I still had issues-not as bad as before-but still issues. Titanium backup worked, so I used that to restore successfully, but I couldn't make new backups. I was frustrated and blamed my issues on using a nightly so I did another full reset and went back to stock.

Now, I wasn't given another UID message, and ALMOST everything works, but I am left with the issue that is the reason I post this thread. I can't take pictures, video, or screenshots and a select few apps fail to recognize the internal sd card (reddit sync, for example, will fail to save pictures when I try to download them, but other apps, like chrome, will succeed to do so, so it is a non-issue. I could also connect to pc again, yay!).

The camera (app and hardware) will still work, and I can tell it takes the picture because the little thumbnail that slides to the side after taking a picture appears. It just fails to save the picture. When I swipe to view the picture, it shows up only as a dark gray box. If I view it in the photos app, I am greeted with the message "media not found." When I try to take videos, Camera will force close the moment I press record.

I've tried a few things, like clearing the camera's data, but that was unsuccessful. Different camera apps (I tried Focal) result in the same problem. Using the Root File Browser app, I also made sure that permissions weren't locking access to that folder. I've also tried deleting the DCIM folder by connecting to PC and then taking another picture, but that still did nothing.

I don't know what else I could do besides another /data format, but I already did that and I don't feel like another format would really do anything since I already did one. I'm left with little that I could think would fix this, but I'm sure someone here could help me.

It is late now and I have school in the morning, so I'll check back on this thread in about 16 or so hours when I'm done with that. Then if anyone has a potential fix, I could try it. If I don't see a fix, I could post a video describing my problem or any more information you might find useful. Thank you all and goodnight.





[Q] HTC One M7 - Possibly bricked? topic




Hi everybody,

Normally i dont get stuck but this time ive hit a rock, basically Ive got a HTC One which then had the bootloader unlocked and a GE ROM with CWM installed.

What I did was possibly stupid as i S-Offed to clear the tampered/relocked status and before running the stock RUU I relocked the bootloader and S-Oned (this is to later sell the handset as close to stock as possible).

What happens now is the phone will boot into the bootloader/fastboot with a TAMPERED/LOCKED/Security Warning status however any attempt to flash ZIP will backfire in signature verify failed.

Ive tried any number of RUU/img/recovery/ZIPs to get it functioning however the closest I've been is using the rom.zip from "RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13 .3231.27_10.31.1131.05_release_310878_signed.exe" which stalled due to the main-version being above the RUU.

My info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

- to note it was ORANG001 before i changed the CID to HTC__001

From what i can tell as i cant boot into anything i cant get S-OFF or unlock the bootloader again, can anyone think of a way to either downgrade/edit the main-version or make it skip the check?

Thanks in advance