Database Develop

[Q] Aroma installer stuck

Hello,
I am a noob trying to install a rom with aroma installer. But now it has been stuck at the page where it says: The installation wizard has successfully installed *********. Press next to exit.
What do i do? Power off?

Is it definitely stuck? Aroma doesn't always recognise touch events very accurately, and I usually have to tap the "next" button a few times before it registers. Failing that, if it's finished installing whatever you flashed, you should be fine to reboot manually anyway.

Yes,i have tried to push the next button many times but nothing happens. It has been like this for 30 minutes now. The successfully installed text appeared very fast, a second or two maybe after the previous screen. So if it has installed the rom, it was def a fast install.
Anyway, is it safe to try to reboot, even if it was in the middle of the install? Rebot to recovery and try again?

Well, there certainly isn't anything else to be done besides rebooting. I don't know what you were trying to install - if it was a several-hundred-MB ROM, as most things that use Aroma are, you would expect it to take a while. Smaller things can be flashed very quickly. If it _did_ go wrong somewhere, there are a few things:
1. What recovery, and what version thereof, are you using?
2. Did you wipe data before using the installer?
3. Most of all, what were you trying to install? There might be some known issue with certain configurations.
I wouldn't necessarily expect a working OS when you reboot, depending on what you were trying to install and how badly things went wrong, but you should be able to get back into recovery easily enough.

Thank you for your quick reply.
1. I use the CWM recovery in this http://forum.xda-developers.com/showthread.php?t=1914394 thread, not the newest, but 5.5 something i believe.
2. Yes, wiped all data + dalvik.
3. I was trying to install rXTREME on my SGS III lte i9305.
I've rebooted now, and everything works perfect as the phone was before i tried to do the install. No brick. I also tried to flash it one more time, but stuck at the same place again. Rebooted fine at stock rom again. Maybe i should take this as a hint that someone else should be put at the steering wheel.. :laugh:
EDIT: forgot link above

Found out what the problem was.
In Aroma Installer i selected EFS backup both times. The third time i tried i did not do this. And everything went fine. Runs smooth.

my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?

jehad.drarjeh said:
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
Click to expand...
Click to collapse
This is I9305 forum is this your phone ??
This thread is about Aroma installer is that your problem ???
Suggest you read the basic faqs and guides first looks like from your post you are either flashing wrong rom to your phone or have hijacked a thread in the wrong forum ./
jje

[Q] >> I've Installed Xposed & Installed Modules, and Now I'm STUCK! Please Help? <<

[Q] >> I've Installed Xposed & Installed Modules, and Now I'm STUCK! Please Help? <<
Hello, I have a Galaxy S5 G900T and I installed Xposed and it was interesting as I thought it was a "Cydia" equivalent to the Android. And I installed modules that could help "tweak" my S5, and after I have finished installing them and I rebooted, now I CAN'T SEE OR ACCESS MY LOCKSCREEN PASSWORD! The one that is the Pattern Lock where you can do a square or Z pattern.. but it just disappeared and it's not even showing up, even if I tapped a lot. You can see my picture attachment below which even the Emergency Button and even the Camera in the corner was gone in the lockscreen
Although I can still receive Calls, Messages and even Alarm Notifications, my real suspicion is that I've installed an Xposed Module, that Disabled my entire lockscreen or something that I haven't fully checked out yet, that caused this without me knowing it
Now I know I have options to do Factory Reset and etc.. however, I know there is still a way I can AT LEAST access my Home Screen or Have a Lockscreen reset itself to show up so I can figure out which of the apps or modules that made my lockscreen disappeared
Does anyone know a way in which we can reset the Lockscreen for it to show up? Or a way to be able to access the Home Screen? Or be able to uninstall Xposed and its modules remotely?

Boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list

C3C076 said:
Boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list
Click to expand...
Click to collapse
OR he could just flash this http://forum.xda-developers.com/showpost.php?p=60468815&postcount=18

A few fix tips
A few things you could try.
1) Flash the xposed framework disabler zip file via your recovery. Find out how to do that here
2) Use ADB to disable the pattern. Find out how to do so here
3) As a last resort, completely factory reset your phone. A google search will point you in the right direction.
Hope this helps, don't forget to thank if it does.

@C3C076 @Agent-Droid @Kris the wizz 15 Thank you for your replies! I tried doing flash a lot of times and even put the Zip files in my SD card and even tried out the methods in http://forum.xda-developers.com/showthread.php?t=2620456 but now the next problem is I keep getting this error "E: footer signature is wrong, E: signature verification failed", and even if it says "Applying Update Complete'' it just reboots it and does nothing
How can we go through that?
EDIT: I haven't did the ADB procedure as I'm still trying to understand all of this, I would really appreciate any help given

You have to use custom recovery since only they can be set to ignore signature verification of zip files to be flashed. If it is a custom recovery, check its options.

Finally it's fixed now! IT WAS A MIRACLE! I suddenly remembered and I actually used AndroidLost in my computer and it helped "unlocked" the screen, but the funny thing was it didnt fully unlock the screen but it just opened Google Speech, and by that time, MultiWindow was opened so I was scared to death and just backed up everything, removed the lockscreen, and uninstalled Xposed and the modules that messed up.. I was scared as hell but now its working lol
But what I found out about my recovery is that, It's pretty much "broken" seeing that even USB debugging wont work in my computer, Kies and Odin can't read my phone being plugged in, and My Recovery can't even Flash zip files anymore therefore kinda rendering it useless not unless, I fully factory reset my phone
Now for people who don't wanna go through this experience, I fully recommend you download "AndroidLost" or any of those apps that help you unlock your phone when your phone is lost.. and to also read http://forum.xda-developers.com/showthread.php?t=2620456 so you can be prepared and have a better Recovery so you don't have to go through this
Take note of that

Just to clarify
MoRTiZz3 said:
@C3C076 @Agent-Droid @Kris the wizz 15 Thank you for your replies! I tried doing flash a lot of times and even put the Zip files in my SD card and even tried out the methods in http://forum.xda-developers.com/showthread.php?t=2620456 but now the next problem is I keep getting this error "E: footer signature is wrong, E: signature verification failed", and even if it says "Applying Update Complete'' it just reboots it and does nothing
How can we go through that?
EDIT: I haven't did the ADB procedure as I'm still trying to understand all of this, I would really appreciate any help given
Click to expand...
Click to collapse
Well, the xposed disabler zip counts on you having a custom recovery installed. You (correct me if I'm wrong) seem to be running stock samsung recovery, which won't flash the zip properly due to certain signatures that the recovery needs.
Since you've already rooted, any warranty you may have had is probably null and void anyway, so you may as well go the whole nine yards and install a custom recovery. You can find out how to do so here or here
Not only will this enable you to flash the xposed disabler zip file, it will also open you up to a world of custom Roms.
The ADB procedure basically uses root access to reset the pattern in your phone so as to enable you to use any pattern you please. That should help you access the xposed app to disable all the modules, and re-enable them as needed.
None the less, here's a few informative links:
1) What is ADB?
2) What's fastboot?
3) Easily intall ADB and Fastboot
4) What is a custom recovery?
5) What is a custom ROM?
Read through these, and then we can make a comprehensive decision.
Sorry for assuming you don't already know this stuff.

Rooting Samsung Galaxy Tablet E (8.0) SM-T377V Please Help

So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:

I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!

I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!

Yep
Ok

Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.

Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.

Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.

stock rom lockscreen problems

Hi, this is my first post and im having problems with my A6.
I tried to install TWRP wich mostly worked fine, but i didnt follow the tutorial correctly wich left my device boot looping at the boot-logo (i didnt install the zip files needed),
so i thought i soft-bricked my device and i downloaded correct stock rom versions from [cant post outside link because im new, but it would go here]
and installed it with Odin3.
This has worked fine and i restored it again, but for some reason if i set the lockscreen protection (like PIN or Fingerprint) it first wont work (but it shows changed in settings)
and when you reboot the device it soft-bricks at the lockscreen and keeps showing the samsung logo then lockscreen for 1 second and samsung again etc. (this wont brick if i dont set any protection)
I have tried a lot of things like installing TWRP again and clearing cache but none seem to fix the problem (other than doing a factory reset).
so im asking here if someone has a clue to what is happening?
EDIT: i will try to install a older version and try to update it with the official updater and i will report back shortly
Results: It did fix my problem with the lockscreen but if i flash TWRP and install Magisk it wont work again
EDIT2: apparently if i wait long enough at the lockscreen-bootloop(atleast couple of minutes) it will grant me access but the protection still doesnt work
EDIT3: Im using Android 9 and i noticed that this is probably the cause, but i didnt find a updated version

Recovery mode and Root issues after stock flash

Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.

Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..