Database Users

[Q] Stuck at Android trying to downgrade from ICS

I have been running Thor's ICS builds and since I see the official ICS rom is out I wanted to go to that. I assumed I could just revert back to the 3.0.1 unstable rom after removing CWM recovery but I was very wrong apparently...
I removed the CWM recovery and flashed the unstable rom through stock recovery as a update.zip file, rebooted and now it gets to the android screen and just loops in that over and over.
I have tried flashing different Honeycomb roms but all of them do the same thing when I try to boot.
What am I doing wrong?
I am still rooted but I don't think that matters much at this point since I can't get to anywhere that would use it...

You must reset your device. I dont have the link here, but i found it here in the xda forum.
Gesendet von meinem MB525 mit Tapatalk 2

here try this, it works Form me.
http://forum.xda-developers.com/showthread.php?p=23246074#post23246074
Gesendet von meinem MB525 mit Tapatalk 2

[SOLVED] [Help] I Installed an A500 stock rom on an A501.

I Decided to go back to stock yesterday and have followed the many guides on XDA to un-root to stock 3.2. Unfortunately I'm an idiot and installed an A500 rom instead of the A501 ROM. I would like to know if it's possible to "Upgrade" from 3.2 to an a501 rom using a signed official rom and the stock recovery?
I'd really like to have the official A501 rom installed on my A501, call me crazy
I've tried to install a few stock roms by renaming the zip to update.zip and placing it both on my ext_sdcard and my internal sd of my tablet but none of them have given anything more than the green triangle android recovery screen. Can anyone recommend what I should do next?
Do I need to re-root and re-un-root?
UPDATE:
I discovered that when I flashed the stock a500 rom from my CMW recovery initially, it worked great and I could access the stock recovery with no issues. however in trying to backpedal and go back to root so I could flash the correct a501 rom I rooted my rom and flashed a custom recovery without first flashing an unlocked bootloader. Then when that didn't work I re-flashed the stock recovery. Pieces of the custom recovery may have been left behind OR there was a simple version mismatch. Either way, I've now flashed an unlocked BL, custom recovery, and flashed back to stock a501 3.2. Now I'm back to a501 completely stock and just waiting for an official OTA 4.0.3 update.
Just read on acer's website the A501 doesn't get ICS. How sad.

It's possible to flash an a501 stock rom over the a500 one. The stock roms you tried without success could've been encrypted and you'll need to use the acer update decryptor to decrypt them. http://forum.xda-developers.com/showthread.php?t=1099673
After decrypting the file with it, unzip it and use the included update.zip to flash your tab.
Gesendet von meinem A501 mit Tapatalk 2

VelosCohagen said:
It's possible to flash an a501 stock rom over the a500 one. The stock roms you tried without success could've been encrypted and you'll need to use the acer update decryptor to decrypt them. http://forum.xda-developers.com/showthread.php?t=1099673
After decrypting the file with it, unzip it and use the included update.zip to flash your tab.
Gesendet von meinem A501 mit Tapatalk 2
Click to expand...
Click to collapse
If I am able to open the zip file it's already decrypted right?
I wouldn't be able to unzip an encrypted zip file afaik

Yes.You're right.
Gesendet von meinem A501 mit Tapatalk 2

Solved, see OP.

skinnyveganboy said:
Solved, see OP.
Click to expand...
Click to collapse
Dont forget to get the acer update enhancement tool from the play store.
MD

I have it but still no update. I know it takes a while sometimes.

Weird touchscreen issue

I am experiencing some weird touchscreen issues. I turn my screen back on, and the touchscreen goes crazy. It's not like the normal lag, the screen goes crazy until I do a full reboot. So I decided to go back to stock and look if the issue is still there. I found this zip with a stock rom: http://forum.xda-developers.com/showthread.php?t=2251958
So I have a stock rom after flashing, but the recovery is the same. So how do I only flash a stock recovery? Maybe if possible from CWM?
Atm I am on cm10 with pa stock kernel with modified colors.
Greetz, Me
Gesendet von meinem Nexus 4 mit Tapatalk 2

X1r0N said:
I am experiencing some weird touchscreen issues. I turn my screen back on, and the touchscreen goes crazy. It's not like the normal lag, the screen goes crazy until I do a full reboot. So I decided to go back to stock and look if the issue is still there. I found this zip with a stock rom: http://forum.xda-developers.com/showthread.php?t=2251958
So I have a stock rom after flashing, but the recovery is the same. So how do I only flash a stock recovery? Maybe if possible from CWM?
Atm I am on cm10 with pa stock kernel with modified colors.
Greetz, Me
Gesendet von meinem Nexus 4 mit Tapatalk 2
Click to expand...
Click to collapse
Flash official stock and re-lock the bootloader.
You can get it from http://forum.xda-developers.com/showthread.php?t=1995688
or google's website.

S III owner --> New to S IV

Hi guys,
So, I just got an S IV today, as a replacement for my beloved S III.
As I've been running CM11 for a long time on my S III, I'd like to keep it that way on my S IV.
However, I've been looking a bit in the forums, and as I got the official 4.4.2 on my S IV, I see that I might be running into some problems, due to Knox - Or will I?
As far as I've understood, I just have to be sure not to flash something that downgrades or installs another bootloader, correct?
If a kind person can clearify for me, that I just can go ahead and do an auto-root, flash a custom recovery and a custom CM11 build - Or what I should avoid, that would be perfect.
Thank you in advance

Your only problem will be that your warranty will be voided if you flash a custom recovery. Other than that there should be no big issues if you are using aosp roms.
Gesendet von meinem GT-I9505 mit Tapatalk

Scumbag Sammy.. But I guess it's almost the same as the flash-counter on my SIII.
Anyway, then there's no chance of bricking and so on?
And if I choose to go back to official Sammy software, I will have to only upgrade, not downgrade?

Well there is always a minimal chance of bricking but if you read the instructions carefully then you will be fine.
Just search for a custom recovery and flash it via odin. Then install the rom you want.
You will not be able to downgrade but in my opinion KitKat is good
Gesendet von meinem GT-I9505 mit Tapatalk

Neo3000x said:
Scumbag Sammy.. But I guess it's almost the same as the flash-counter on my SIII.
Anyway, then there's no chance of bricking and so on?
And if I choose to go back to official Sammy software, I will have to only upgrade, not downgrade?
Click to expand...
Click to collapse
Yes it's the same flash counter ? Very difficult to brick as long as you follow guides ?
If you want to go back official you can use odin & correct there's no way to downgrade only stay same or upgrade when next version comes up ?

Help with Xposed for Galaxy A3 (A300FU)

Hi.
I need a little help with Xposed, but before I get to what help I need I'll give you a little background info.
I have the Galaxy A3 (A300FU) and it's actually the first smartphone I've ever owned (I know I'm a bit late to the party). When I got it it had kitkat installed which I promptly rooted. I then found out about xposed and installed it and some modules. Recently my carrier, EE, finally released their lollipop upgrade (5.0.2) so I downloaded it from Sam mobile and flashed it over with odin. I then rooted using the method I found here of using the kitkat autoroot and then flashing the correct recovery to get rid of the error it caused. This left me with a working rooted phone running 5.0.2 lollipop however if I turned the phone off while it was charging it automatically rebooted into recovery. I read various ways of fixing this but since I wanted to use the TWRP recovery anyway I went and flashed that too. This also fixed the issue of the phone rebooting into recovery.
Now comes the issue with Xposed. When I had kitkat I installed xposed and a few modules like wanam and everything worked fine. However now I have lollipop it's telling me it doesn't support 64 bit architecture. I looked into this and found a lot of threads that were talking about using an unofficial version of xposed and needing deodexed roms anyway. However when I was using kitkat I was using an odexed rom and I had no issues with it. Also the unofficial xposed that I have found seems to be for 5.1.1 or 5.1.2 not 5.0.2.
Is there a version of xposed that will work on my A300FU running 5.0.2 and if so do I need to deodex my rom first? If so how do I go about doing that? Also could someone tell me why xposed worked with my odexed kitkat rom (I'm just curious about the inner workings) since everything I have read seems to indicate that it shouldn't have worked then either?
Many thanks in advance and sorry for such a long winded beginning I just wanted to explain exactly where I'm at with it and to give an idea of what I've done before so you can get an idea if what I should know how to do.
Thanks again.

I hate to bump but it's been a while since I posted.
Does anyone have any help for me? Really missing some of the things that I used to have with Xposed.

You might give this a shot: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463/ you'll need to deodex first
Gesendet von meinem SM-A300FU mit Tapatalk

prometh696 said:
You might give this a shot: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463/ you'll need to deodex first
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
I tried to deodex using the TUTO on here but had no success. Just ended up with a bootloop.
Also after doing a little research I have come to the conclusion that because my device is running ARMv7 that it must be 32 bit. However I'm also being told that I'm running 64 bit so I'm a little confused as to whether I should install the 32 bit Xposed or the 64 bit Xposed if and when I manage to deodex my ROM.

I managed to get it running:
http://forum.xda-developers.com/sam...to-5-0-2-xposed-custom-recovery-knox-t3251317
Gesendet von meinem SM-A300FU mit Tapatalk

prometh696 said:
I managed to get it running:
http://forum.xda-developers.com/sam...to-5-0-2-xposed-custom-recovery-knox-t3251317
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
Thanks. I didn't see that thread when I was looking for a solution.