Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is here: http://www.youtube.com/watch?v=KEP9aJzUFGo
dh2311 said:
Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is uploading as I type this, allow 20 minutes (my internet is that bad)
Click to expand...
Click to collapse
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
skinsfanbdh said:
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
Click to expand...
Click to collapse
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
dh2311 said:
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
Click to expand...
Click to collapse
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
skinsfanbdh said:
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
Click to expand...
Click to collapse
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
dh2311 said:
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
Click to expand...
Click to collapse
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
skinsfanbdh said:
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
Click to expand...
Click to collapse
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
dh2311 said:
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
Click to expand...
Click to collapse
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
skinsfanbdh said:
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
Click to expand...
Click to collapse
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
ive had that also i just restored my backup and quit for the day then tried the next day and it worked
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
try with re-downloading the file and put it in root of your sd card
rambo12345 said:
try with re-downloading the file and put it in root of your sd card
Click to expand...
Click to collapse
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
dh2311 said:
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
Click to expand...
Click to collapse
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Okay, in a weird turn of events, I thought i would rather than going to an RUU just wipe everything and reinstall everything, and the Aroma installers for the ROM and tweaks are working so far...
EVERYTHING WORKED! Dont know whether it was the wipe, just luck, installing using only volume keys and power button. But this seems to have gone away :fingers-crossed:
nolimit78 said:
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Click to expand...
Click to collapse
I could well be... have some working now, but if one breaks, Ill try reinstalling using volume keys and power button and never touch the screen
awesome. glad you got through it bro:good:
Related
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
I've tried many different things in alot of the threads I've read on this forum and nothing is working. I tried using the One-Click root on my Droid and it didn't work, come to find out, it was an outdated method for the Droid 3. It messed up my phone. My apps constantly crash. My texts disappear, then sometimes reappear switching the place of the texts randomly. When I reset from settings, it restarts phone, but nothing is reset. It won't let me check my e-mails(G-mail). I can hardly do anything. I've tried flashing back using the AP Fastboot method from psouza(spelling?). On my phone it says Battery OK/Program OK/USB Connected. So I run the "CLICK HERE - Flash Verizon DROID 3 OTA 5.6.890 to phone.bat". It failed.
Then I tried ovelayers method. Everything seems to go good. And I was happy! But when it rebooted, it took me to the android triangle screen. SO I selcected reboot. And absolutely nothing changed. Am I Missing a step? I also tried doing it again, but after it went to traingle android screen, I selected the update from the SD card, installed it, rebooted, and STILL nothing. Nothing changes. Ever. Nothing is working. Please help. I tried being as descriptive as possible so that it answers most potential questions.
*Edit* I've also tried the RDS Lite method. Crashes on step 3.
Phone specs: Version: 5.7.906.XT862.Verizon.en.US
Kernel: 2.6.35.7-g5fa4155
Android 2.3.4
download full system file
http://dev-host.org/uEA
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Make sure you use the sbf for. 906 and not the one for. 890
http://d-h.st/mvX
niko99 said:
download full system file
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Click to expand...
Click to collapse
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
xJolly said:
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
Click to expand...
Click to collapse
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed
http://db.tt/pi5c484a
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
DoubleYouPee said:
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed.
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
Click to expand...
Click to collapse
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
xJolly said:
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
Click to expand...
Click to collapse
First you need root access. Use Motofail if you haven't:
https://www.dropbox.com/s/wpl88mwm6eilhe6/motofail.exe
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
DoubleYouPee said:
First you need root access. Use Motofail if you haven't:
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
Click to expand...
Click to collapse
Figured. My phone won't root. Like I said, nothing will change about it.
xJolly said:
Figured. My phone won't root. Like I said, nothing will change about it.
Click to expand...
Click to collapse
Ok so what about x+power?
DoubleYouPee said:
Ok so what about x+power?
Click to expand...
Click to collapse
No. It doesn't work. I've tried that.
xJolly said:
No. It doesn't work. I've tried that.
Click to expand...
Click to collapse
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
DoubleYouPee said:
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
Click to expand...
Click to collapse
I'm going to record a video. And show you the multiple things that happens. I'll have to PM it to you though, and anyone who wants to see it.
I remember someone else having a similar issue on their device. Since I'm home sick today I'll see if I can find the thread and if it ever got solved
Sent from my XT860 using xda premium
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
DoubleYouPee said:
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
Click to expand...
Click to collapse
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
xJolly said:
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
Click to expand...
Click to collapse
You're right. No way you can send it back for replacement? Your phone seems stock
DoubleYouPee said:
You're right. No way you can send it back for replacement? Your phone seems stock
Click to expand...
Click to collapse
Well, I don't have insurance on it, as I had gotten it from a friend. So, no. Not without paying an arm and a leg, at which point I'd pay for a new phone instead. I just really wish this could be fixed. I've heard no phone was unbrickable. AM I THE PRODIGY?!
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
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
spazzy1912 said:
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
Click to expand...
Click to collapse
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
markj338 said:
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
Click to expand...
Click to collapse
woops, i forgot to mention that i was on 4ext touch before and it still happened :S
it used to happen before, but not as frequently, so that is why i am a bit worried
when i get my pc back ill try reverting back to 1.13 bootloader :S
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
wilsonhlacerda said:
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
Click to expand...
Click to collapse
Unfortunately, nope..
Jasiniok said:
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Click to expand...
Click to collapse
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Kglim said:
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Click to expand...
Click to collapse
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Jasiniok said:
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Click to expand...
Click to collapse
I think you could save ur data partitiin and sjust system wipe and dirty flash for carry yiur data.
Good luck to ya!!! :fingers-crossed: