yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] rcklss1:
The G pro development section is a ghost town compared to the s4.. Take a look at the forums and see for yourself lol

---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------

I haven't checked any other sites but if any site were to have ROMs and mods and whatnot for OG Pro it would be xda and I just checked again so I don't eat my words there isn't one ROM there in fact there's only like 10 topics in the development section
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Blueknight730:
OK I took a look and gpro doesn't have that much in it. So if u just run stock then the gpro would be OK. Think I'll stick with the s4. Thanks everybody.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Blueknight730:
Now if we can get a bootloader unlock for the s4 we would be set.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] dtowngs4g:
I tried this G pro when my s4 was stolen. It's heavy to me but 5.5 inch screen. It seemed a tad bit slower not much than s4. I've mainly owned either Samsung or LG devices so I'm used to the difference between them. I just felt less comfortable carrying the Pro. I would definitely use it at home but not out & about. The storage is great 32gb internal with additional sd storage.
[Android Q&A, Help & Troubleshooting] moriel5:
Hello, l'm using a Pocketbook IQ 701 and for the past few days I've noticed that the power button stopped locking the device.

It boots up and gets to the lock screen, where I can freely lock and unlock the device, but when I unlock it the power button just doesn't lock it anymore ( although if I press and hold, it does bring up the power options such as shut down).

Upon looking at "wake_unlock" in "/sys/power" I get "KeyEvents PowerManagerService", yet "wake_lock" shows nothing, although I've noticed that if I make a copy of it in a different folder it suddenly shows "PowerManagerService".

while I have tried to replace the original file with the copied file, as soon as the copied file is in "/sys/power" it becomes blank.

I suspect that this issue though, is system related and not OEM related, as I've seen similar threads on the Internet, although, either there was no answer, the issue was a completely different issue, or the solution simply did not work.

Thank you in advance, and I hope to receive for a speedy answer.
[Android Q&A, Help & Troubleshooting] moriel5:
In the end I just flashed the official rom and the problem disappeared.
[Nexus 4 Themes and Apps] Pandemic187:
Just wondering if anyone else has experienced this. Ever since updating Google Maps to the new version with the new UI, compass orientation is always wacky while in 3D mode. See the screenshot below to see what I mean:

This is what it looked like immediately after tapping the location button twice. Even worse, the map doesn't even pan in the direction the dot is facing half the time, but instead moves in the opposite direction.

This doesn't seem to be a problem while in navigation mode, but it is nonetheless annoying.

Apologize if someone already posted about this but I couldn't find one. I've only tested on Rootbox, but I've used many ROMs in the past and in my experience that has never made a difference.
[Nexus 4 Themes and Apps] ailwyn2002:
Yep you are correct, mine has been the same. For example completing a whole roundabout before we even get there. Moving to a field even though we're on a marked road. Moving sideways whilst driving forward. Very weird!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Hello everyone,

This is my first post here so I hope I'm posting in the right section regarding to the issue I'm having. Be assured, I have searched DAYS for an answer and tried many ways that solve other member's problems but doesn't work for me.

Cannot seem to flash any custom ROM without STATUS 7 error (I have tried 4 different ones, all AOSP based, if that matters).

I receive the status 7 error on both CWM and TWRP, both on the latest versions. Says nothing about the "getprop" or anything like that, just says "Error flashing zip... (Status 7)" or something close to that.

I did notice that before the error it does say something about "set_perm:some changes failed" on the Zips I have tried to edit by taking out the assert lines in the updater script. Otherwise it shows the error after "Creating Symlinks..."

Phone Info:

-Canadian I747M on Rogers Network, but unlocked, running on chatr

-the stock rom I have is TW 4.1.2 OTA update for Rogers, which I had to flash manually through Odin.

-Stock Kernel

-Rooted

What I have already tried:

-wiping cache, factory reset, system, dalvik 3x before trying to install the zip

-have tried both the latest versions of CWM and TWRP, same error. And yes, I have tried both d2att and d2can recoveries for twrp.

-tried a few different roms

-have re-downloaded all of them to make sure download is not corrupt

-have tried to remove the assert lines within the "updater-script" file withing the ZIP, still get status 7

-Downgrading my bootloader from MVLDMF1 to MVLDLK4

-USB debugging is on

I could try and get a picture if anyone needed it of the error in recovery.

Any idea what could be causing this and how to overcome it? Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Last time I helped someone with your issue everything was tried. Turned out he flashed the modem not the bootloader.

In terminal emulator type

su

getprop ro.bootloader

If its the same as the baseband I'm not sure what else to suggest. If it's different than make sure you're on the right bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
The terminal emulator confirmed that I have the I747MVLDLK4 bootloader...

Do you think maybe try a full internal storage wipe/factory reset and root again might do the trick?

Hopefully someone can figure this out... It's so frustrating. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Sometimes a complete return to stock can solve many issues. Another guy had this same issue. I'm wondering if it has something to do with Canadian carriers and the boot loader. He removed the bootloader check from the install script for a couple months and that's the only way a non TW ROM would flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] susram:
I have tried BOOT LOADER UPDATE instructions from http://xdaforums.com/showthread.php?t=2321310

Now, I have my baseband (from settings UI screen) and bootloader version (from terminal getprop ) both as I747UCDLK3 ; Still I get this Status 7 error while installing any CM ROM. Similar issue mentioned by OP (original post)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
You can always Odin to stock and flash the twrp.tar in odin while you're there. I've seen recoveries flashed with goo and ROM manager not stick.

I'm on Telus and have never had any issues since flashing the d2att recovery.

Wish I could be more help.

Let me know if going stock and re rooting helps.

If you rooted with a tool kit I'd recommend doing it manually.

---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------

A) Thread jacking isn't really nice.

B) status 7 isn't just bootloader. You could have an out of date recovery or an incorrect recovery.

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

Removing the bootloader check can not only cause issues down the road (downloading the wrong ROM) but is also a bandaid fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
I know haha. It was just a temp fix that of course one wouldn't do unless you knew what you were doing. Just wondering why Canadian guys are having this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
When most Canadians root their phones it loads d2can recoveries and the at&t Roms aren't "compatible" with our phones.

This usually comes up nightly.

Op's problem is odd though. I'm sure it's going to end up being something simple.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
I shall try and do a pre rooted firmware flash through odin and write everything back to stock tomorrow. I will post back and let everyone know how it goes after rooting again and trying to flash CM10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Craptain Krunch:
Change the Recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
He stated in the op that he had.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daroco:
I fixed mine

Hey, I had the same issue when I just tried to flash a CM rom. I flashed the bootloader baseband update with no success. as someone has mentioned a few replys prior to this one I tried to change the recovery. I had the latest CWM downloaded from their site. Instead I installed TWRP and it now work I have successfully installed CM 10.1. I used ODIN to flash TWRP. For whatever reason it does not show the status 7 error anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Now recieving new Error!

OK, so I went ahead a did a complete data wipe and flashed a stock ROM through ODIN once again leaving me completely stock except for installing root and custom recovery. What I notice now is that on the latest version of TWRP for d2att & d2can I get an error stating :

set_perm: some changes failed

E:Error executing updater binary in zip '/sdcard

Error flashing zip '/sdcard/[ROM Name Here].zip

Updating partition details...

So I searched again and came along someone saying to try to use an older recovery, so I tried TWRP 2.3.3.1 for d2att and got:

set_perm: some changes failed

E:Error in /sdcard/[ROM Name Here].zip

(Status 7)

So the STATUS 7 is being resolved, but there is another error in the updater binary..!!!

I really need some help, hopefully someone can find a solution to this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
So [MENTION=4853127]KorGuy123[/MENTION] this is third guy I've seen with this issue that seems to not make sense as to why he can't flash a rom. Status 7 makes sense with an older recovery but they use a newer one and it doesn't work at all. So if you knew you downloaded a ROM that was compatible for your phone, d2can and removed the bootloader check what harm could be done ? We know the bootloader is correct.

So honest question fmr ym own knowledge and his.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
If you KNEW what ROM you downloaded and flashed nothing is wrong other than you'd have to do it to every ROM you download.

The problem is this is an open forum and someone who didn't know what they were doing is bound to flash something they shouldn't.

The other day there was a guy that admitted he "downloaded the first file that resembled a ROM" those are the people I / we don't need reading a suggestion like that.

---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------

I wouldn't have gone so old. Latest is 2.6.0.0

2.3.3.1 is probably too old and can give status 7 try 2.5.0.0 or the one older than that 2.4.4.1 I think.

Also check under mount that "system" is unchecked. If it's checked it can prevent proper flashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
Good point

http://techerrata.com/browse/twrp2/d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
I was going to chuck my S3 out the window just now. :mad:

Followed through with those suggestions also, tried latest 2.6.0.0 recovery and 2.5.0.0 and both still give me the error:

set_perm: some changes failed

E:Error executing updater binary in zip '/sdcard

Error flashing zip '/sdcard/[ROM Name Here].zip

Updating partition details...

or something to do with symlinks... and the "system" under mount was not checked.

I am downloading a TouchWiz based ROM right now (Wicked v10) to see if its just AOSP based that are giving me problems.

Now I have to stay on laggy stock TW without everything that I had before because I wiped it. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Don't get too frustrated. We'll get this figured out. Wonder if [MENTION=4945572]xBeerdroiDx[/MENTION] has any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Anything [MENTION=4945572]xBeerdroiDx[/MENTION] ?

Anyone know anything else I could try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hednik:
So I've read up some and some people have issues flashing custom rom's on 2.5+. Have you tried to down grade to something like 2.4.1.0 and then wiping cache ? I know it was mentioned but I didn't see if you tried. It's an issue some HTC phones have so I'm not sur eif it applies to your situation.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] DeliveryNinja:
Hi,

I was using Slim Rom 4.2.2 on my note,

I rebooted into CWM and flashed SpeedMod k3-11 and rebooted the phone without wiping anything on the device.

It is now stuck where I cannot get to recovery mode the phone screen goes strange and the image distorts before it turns itself off again.

Any idea what I can do to try and recover the phone, is it possible without being able to get to CWM?

Thanks :crying:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ttibbetts83:
If you can get to down load mode you can use PC Odin to flash a kernel like pilz kernel and do all wipes then flash the ROM again from pilz kernel after flashing with PC Odin phone should reboot on its own and then boot loop just hold power - up - and home and you should get pilz recover witch is safe and can handle your flashing needs
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] muskanstha:
Flickers like this? http://m.youtube.com/watch?v=jJNBnKMLVWU&desktop_uri=/watch?v=jJNBnKMLVWU . Then time to replace battery..
[Xperia Z Q&A, Help & Troubleshooting] kdavidyates:
Camera quality on my Xperia Z is great apart from the corners of each picture (especially the top corners), which are always very blurred compared to the rest of the image. I've tried all sorts of different settings, seems to make no difference.

Does anyone know if this is just the way things are with the Z, or a defect which they might fix/replace under warranty?
[Xperia Z Q&A, Help & Troubleshooting] thalada:
Post pictures taken from your cam.
[Xperia Z Q&A, Help & Troubleshooting] danw_oz:
The design of lenses have this inherent fault, corners are always more soft than the center.

However post some shots so we can see, because if you are claiming that they are very blurred it would be good help diagnose if the quality does seem worse than the norm. Also double check that the lens is in fact clean all over.
[Xperia Z Q&A, Help & Troubleshooting] Dsteppa:
Here since 2009 and still don't know how to read:silly:

http://xdaforums.com/showthread.php?t=2116920
[Xperia Z Q&A, Help & Troubleshooting] kdavidyates:
Ok thanks for the heads-up but I could just as easily have posted this as a thread (i.e. 'Possible camera defect', and without the 'Q'). I wasn't aware of the restriction on questions here.

Let me rephrase: "It seems to me that there's a defect with my camera which blurs the corners of pictures. Does anyone else have a similar experience with their camera?" (Or does that count as a question too?)

Here are some links to pictures, anyway, assuming the thread doesn't get deleted (and thanks to those who posted asking for them):

As long as there's nothing in the top corners, it takes really nice pictures:

https://www.dropbox.com/s/zww62ysjtsicr1v/2013-06-06 10.52.43.jpg

https://www.dropbox.com/s/4r3lzcdeuuk7rb0/2013-07-20 19.34.35.jpg

But these three (taken to test for this fault) clearly show blurring in the top corners (comments on whether this is excessive are welcome):

https://www.dropbox.com/s/8odsgf5xdkpld5f/2013-04-20 17.55.15.jpg

https://www.dropbox.com/s/xs3r79awos2dc65/2013-04-20 17.56.42.jpg

https://www.dropbox.com/s/5um2bst8i2tgji5/2013-05-07 14.00.20.jpg
[Xperia Z Q&A, Help & Troubleshooting] Luke_dD:
I have the same problem. When I'm holding the phone in landscape mode, the left corners are also very blurry.

I experienced the same problems with my Xperia Neo, but in contrast to the Xperia Neo, the Xperia S didn't had that problem.

I'm very disappointed in Sony, because I have more problems with my Z :(
[Xperia Z Q&A, Help & Troubleshooting] kdavidyates:
Bump - does anyone else experience blurring in the top corners of their pictures? Thinking about returning under warranty, as I use the camera quite a lot. Sample photos linked below...

As long as there's nothing in the top corners, it takes really nice pictures:

https://www.dropbox.com/s/zww62ysjtsicr1v/2013-06-06 10.52.43.jpg

https://www.dropbox.com/s/4r3lzcdeuuk7rb0/2013-07-20 19.34.35.jpg

But these three (taken to test for this fault) clearly show blurring in the top corners (comments on whether this is excessive are welcome):

https://www.dropbox.com/s/8odsgf5xdkpld5f/2013-04-20 17.55.15.jpg

https://www.dropbox.com/s/xs3r79awos2dc65/2013-04-20 17.56.42.jpg

https://www.dropbox.com/s/5um2bst8i2tgji5/2013-05-07 14.00.20.jpg[/QUOTE]
[Xperia Z Q&A, Help & Troubleshooting] Dsteppa:
[/QUOTE]

I'd say send it back, must be a hardware failure.

I'll be sending mine back for dead pixels on the damn sensor. New sensor so lots of problems.
[Xperia Z Q&A, Help & Troubleshooting] danw_oz:
I do not see really problems with this, I am sure it is a slight misalignment of the lens, this happens on P&S cameras, they are typically worse than this in all corners. This effect even happens on some of the most expensive DSLR lenses, the more wide angle typically worse the issue.

If you can get the whole phone replaced because of this then you will be extremely lucky.
[Galaxy S 4 Q&A, Help & Troubleshooting] checasey:
Anyone know how to increase size of icons in simi folder they never used to be so small!
[MDA III, XDA III, PDA2k, 9090 General] cpaustin:
Well, I never wrecked a phone yet - then I invest in an XDA IIS and spill red wine on the front keys (4 app keys and joystick thing) - after only one week.

Luckily I'm pretty handy with the ol' "spanners" and was able to take it apart and clean it out.

What I did find out though was that contact cleaner doesn't mix too well with the silicone inserts behind the buttons. Some have since hardened and the joystick one has a small tear.

All is working ok, but i've had a few dodgy buttons from time to time.

I want to replace these and probably just replace the boards behind the buttons as well. (One small narrow one for the 4 app buttons, one larger one for the joystick thing)

Anyone know if parts are readily available ???

(I'm in Australia)

PS : is there a proper term for the ''joystick thing" ??

Thanks.[/b]
[MDA III, XDA III, PDA2k, 9090 General] derosnec:
Wow - I have almost the exact same story. Always careful with PDAs, managed to spill rum on my front buttons. Buttons would then fire off randomly (well, the hang up and down buttons would). Opened it up, cleaned it and the PDA now works again, but the Up and Right buttons don't work.

So yeah, spare parts would be great :-)
[Samsung Galaxy Nexus] furious anger:
This mod implements the fix for bug master key (Bug 8219321) and (Bug 9695860) of which much has been said.

WARNING: This is only for stock 4.2.2 roms (JDQ39) odex or deodex choose the corresponding download for your rom.

Screenshots:

installation:

- Must have a recovery installed CWM or TWRP.

- Move the file for your rom to SD.

- Turn off the phone and boot into bootloader:

For this you press VOLUME UP + VOLUME DOWN + POWER all three at once. In the bootloader by pressing the volume buttons, until appears the word RECOVERY MODE and pressing the power button.

- In the recovery:

- install zip from sdcard

- choose zip from sdcard

- Find the downloaded file.

- yes

Recommended wipe dalvik cache and cache.

Downloads:

ODEX

DEODEX

Credits:

AOSP

Cyanogenmod
[Samsung Galaxy Nexus] furious anger:
Over thirty downloads, two thanks and no commentary. :good:
[Samsung Galaxy Nexus] Sanjay:
Spoiler content hidden.

Sent using xda premium
[Sony Xperia P, U, Sola, Go] kedzi.szymon:
Hi everyone!

I looking for "Official GB" for recovery of root (I must have root in official GB) because my Xperia U has BL can't be unlocked (Polish mobile network Orange) and in my opinion this ROM is the best. GB V3 is good rom but has more bugs than official GB. Please, help me.

Sorry my English language.

Best regards!
[Sony Xperia P, U, Sola, Go] Deleted member 3493119:
I have no idea what you mean, if you are in need of a custom recovery there is some which can be found in the development section, if you need to root your device you just have to follow some of the guides.
[Sony Xperia P, U, Sola, Go] kedzi.szymon:
I need ROM GB official when will have root and I will can install by recovery. Now I have ICS root and cwm, because in my opinion Gb is the best Rom from lock BL I need package when will have official gb& root.
[Sony Xperia P, U, Sola, Go] kedzi.szymon:
When I install official gb by flashtool after I can't install root because Now it is impossible there is no way and any way
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] uspole:
Im have a lot of problems getting my P7510 Galaxy Tab working on new firmware.

Ive tried several different firmwares and none of them have worked properly. Currently I am working with Stock Firmware from January 2012 (http://xdaforums.com/showthread.php?t=1452060). After using Odin, it installs better than any of the other firmwares ive tried, and after every fresh installation Android will sometimes open up normally after which it then crashes! On subsequent attempts to run it I always end up with the Samsung Logo screen.

Ive always done a Factory Reset before & after installation, also Wiped Cache occasionally. I have also installed CWM and cleaned the Dalvik Cache on several occasions.

Maybe I should try a different Stock Firmware. Ive done some searches (ie, sammobile) but cant find any. Can someone give me a link where I can get a different Stock Firmware. Or maybe this isnt the problem. Can somebody tell me where I go from here.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] John Kester:
The problem is likely not to be the firmware or ROM you are installing but the procedure you are following. You only do Factory Reset before a fresh installation. However, you do not need to do a Factory Reset after installation as that amounts to wiping off the installation you had just done. In order words, your device is blank and has NO SYSTEM TO RUN IT! Try installing a custom ROM again without the factory reset. The other wipes you do i.e. cache and dalvic are in order, before and after installation.

For a very clean installation also format system under Mounts and Storage in CWM. Ensure you have the latest version of CWM 6.0.3.3 before you start, especially if you intend to run Jelly Bean 4.2.2 based ROM such as CM 10.1 etc.

Hope this helps you.

Cheers.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] eushaun99:
Actually, factory reset wipes data and cache. It doesn't wipe system so after a ROM installation its OK to factory reset.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] uspole:
Thanks for your advice folks. This is where ive got to now:-

After cleaning Dalvik Cache, a Factory Reset and formatting system under Mounts and Storage I installed the stock firmware and the device booted as it should. I was able to connect to wi-fi and Play Store and do some updating etc., But once I Powered Off the device it wouldnt boot up properly again, it just hung on the darn Samsung Logo. So I installed CWM and on reboot, lo-and-behold, the device started working normally (without me having run CWM at all). Then I subsequently Powered Off and started again but once more got stuck on that Samsung Logo. So then I wiped Dalvik Cache to see if it would boot properly, and it didnt. And then I did a Factory Reset to see if it would boot properly and it didnt.

Where do I go from here?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] John Kester:
What stock firmware did you install?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] uspole:
I used:

P7510XEUKL2_P7510XXKL2_HOME.tar.md5 from:- http://xdaforums.com/showthread.php?t=1452060