Develop Bugs

[Q] Major confusing Google-apps problem

Have run into a major problem i think, need some of you experts to help me out on this one...all my ideas have failed.
I have been using cmod 6.0.1 for a while now, remember I had some problems to add gapps to that rom, and now the problem is reversed...
No matter how much i whipe/clean/clear I can't get rid of market, facebook, twitter, car home and probably some other app i don't remember right out of my head.
I have entered clockwork, I made a factory reset, cleared cache, and then the part that got my attention. When I press the trackball on option "wipe dalvik cache" (the title, before i press yes) i get this message:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Although this it says Dalvik has been cleared successfully when I have pressed OK to clear.
I recon this might be the problem, but I'm far from certain, I'm still a noob in the progress of learning.
After all this, I have managed to successfully flash cmod 6.1.1, which I at first thought he added some gapps despite Googles opinion about that. Did not fins _any_ parts of those gapps in the rom-package.
Went forward to flash cmod 6.0.1 which I KNOW don't contain there apps (cus I had big problems adding them on that rom in the beginning).
Now I ask you far more learned guys, what can be wrong, and how could I solve this? All i can think of, is that IF they somehow managed to get their way onto a recovery-partition of the phone, but i really don't know...just wild guessing.
On the even more weird side, those gapps is installed onto the regular path "root/system/apps"
I really cant find anything that could put them there, nor find any reference to those .apk-files to even install them in the first place.
Running a GSM Desire.
EDIT: Have read a bit more about the mmcblk0p2-thing, and wow, i have no idea of how to get myself out of that. Most solutions seems to be trough ADB (if im even on the right track?), and I were not at all familiar with linux of any kind before this phone. I am a quick learner, but that doesn't solve what I have yet to learn.

I somehow managed to clear out hose apps, but the thing with dalvik remains (the "file already exists"-thing).
Now im just looking for someone who can tell what could have been the problem, and if the dalvik-thing is normal behavior? I dont have partioned anything nor running any app2sd other than stock.
Could that be it, that theres no extra dalvik-cache on a user-created partition?
...I dunno, just pulling strings here right now.

I believe it's just a message that it can't find a second partition on your SD card, which makes sense since you haven't partitioned it. Shouldn't make any difference.

[Q] LeeDroid 3.0.8.2 Help

hi,
i have just tried to install LeeDroid 3.0.8.2 and am panicked that i've bricked my phone.
I partitioned the sdcard using Rom Manager - also downloaded and flashed the rom via rom manager.
It seemed to do its thing fine and the leedroid screen loaded up, but now it just keeps looping back on itself showing me that its installing making this funny beeping sound and then goes back to the leedroid screen for maybe 15 seconds and repeats.
Anyone know ever have this experience? can any one help?
thanks

Please make a search...
The best way to avoid bootloop is first to partition the SDcard with Gparted...
Then you need to check a few things (your hboot version among others)
good reading !!!

If it's looping at that point it is almost certainly a problem with the SD-card ext3 partition. Rom Manager is not terribly reliable with making that.
The Gparted suggestion is by far the best solution (assuming you have a PC with a card reader, rather than trying to do it with card mounted in phone)
If you *do* have a reader then try LiveCD with gparted, burn to CD and boot from that.
Make your first partition FAT32, and your ext3 partition at the end of the card. (1GB recommended). Make sure both partition are marked as "primary".

Sorry for jumping in here, but I also need help with this rom (sorry uber noob and all). Figured since the thread was so fresh may as well ask here.
Basically trying to install leedroid v3.0.8.2 (data ++) for my original htc desire.
Cant download from either of the links, they both lead to url 404s.
And i also tried downloading from both rom manager and also the minisite, these downloaded but seem to be corrupt. I cant open the zip file and trying to flash it returns a cant flash (bad) message.
Anybody know where i can get a working zip of this version?

cathalfm said:
Sorry for jumping in here, but I also need help with this rom (sorry uber noob and all). Figured since the thread was so fresh may as well ask here.
Basically trying to install leedroid v3.0.8.2 (data ++) for my original htc desire.
Cant download from either of the links, they both lead to url 404s.
And i also tried downloading from both rom manager and also the minisite, these downloaded but seem to be corrupt. I cant open the zip file and trying to flash it returns a cant flash (bad) message.
Anybody know where i can get a working zip of this version?
Click to expand...
Click to collapse
Have you tried here and choose the ROM you want from the white scrolling list? The 3.0.8.3 data version downloads for me.

Blackout ICS Incredible v3.0.0 - No Music, No files in gallery, no FM radio

Hi,
As i mentioned in topic, music not take in to account from sd also gallery, and fm radio doesnt work
I did full wipe, fix permission, reinstall rom 3 times.... and still the same effect
Have you have some idea ?

vvojtek said:
Hi,
As i mentioned in topic, music not take in to account from sd also gallery, and fm radio doesnt work
I did full wipe, fix permission, reinstall rom 3 times.... and still the same effect
Have you have some idea ?
Click to expand...
Click to collapse
I finally manage gallery and music, I had to format SD card... and recreate manually music folder. For gallery it was enough toke picture and dcmi folder recreated.
Still problem with radio, after plug headphones, told me headphones not plugged etc... any idea ?

Sorry, but...
Is there any way for me (I have registered only for this purpose, otherwise I'm a pretty read only guy and mostly finding the answers otherwise) to post a question about the installation failure of this ROM?
I use 4EXT recovery, done a full wipe (have been using many versions on this and my previous devices so not a completely noob user I guess ), and installer appears to be finishing successfully - but then in the log there are two lines showing it wasn't successful after all:
"mount: failed to mount /dev/block/mmcblk0p26 at /data: Device or resource busy"
and
"error: file_write: write: I/O error
Installer Error (Status 1)"
Now what can the cause be?
Oh, I forgot: have checked the md5sum and was correct (I mean throughout recovery on the SD after the zip was copied to the SD...
Again: sorry but not allowed to post at the ROM's thread...

Totyasrac said:
Is there any way for me (I have registered only for this purpose, otherwise I'm a pretty read only guy and mostly finding the answers otherwise) to post a question about the installation failure of this ROM?
I use 4EXT recovery, done a full wipe (have been using many versions on this and my previous devices so not a completely noob user I guess ), and installer appears to be finishing successfully - but then in the log there are two lines showing it wasn't successful after all:
"mount: failed to mount /dev/block/mmcblk0p26 at /data: Device or resource busy"
and
"error: file_write: write: I/O error
Installer Error (Status 1)"
Now what can the cause be?
Oh, I forgot: have checked the md5sum and was correct (I mean throughout recovery on the SD after the zip was copied to the SD...
Again: sorry but not allowed to post at the ROM's thread...
Click to expand...
Click to collapse
Theres a known bug in the aroma script. Youll have to select "perform a full wipe" in aroma and not tick the reboot checkbox that shows up when flashing is done. Then all should be fine
Script will be fixed in future releases. Sorry for the inconvenience

Mikenif said:
Theres a known bug in the aroma script. Youll have to select "perform a full wipe" in aroma and not tick the reboot checkbox that shows up when flashing is done. Then all should be fine
Script will be fixed in future releases. Sorry for the inconvenience
Click to expand...
Click to collapse
Cheers - I'll give this method a shot right away
EDIT: Apparently this way it worked... Thanks again!

Totyasrac said:
Cheers - I'll give this method a shot right away
EDIT: Apparently this way it worked... Thanks again!
Click to expand...
Click to collapse
Youre welcome Enjoy!
@vvojtek
FM Radio is a known issue. Will be solved in the next update

Mikenif said:
Youre welcome Enjoy!
@vvojtek
FM Radio is a known issue. Will be solved in the next update
Click to expand...
Click to collapse
Thanks
btw.
I have and also others guys problem with "metalic" sound during the conversation, sound is strange comparison for stock rom and ICS AOKP 8.5.
Radio : 12.56.60.25U_26.10.04.03_M
Anyway I have to say again very very good job with this ROOM

in my dhd,music and gallery work well so i think that maybe your sd card need formated.
the same thing is that fm doesn't work,it's universal.

How to flash rom?
Can you guys include some basic steps on how to flash this rom?
My DHD is currently on the Revolution HD rom.

JonCYY said:
Can you guys include some basic steps on how to flash this rom?
My DHD is currently on the Revolution HD rom.
Click to expand...
Click to collapse
its real easy all you have to do is place the rom on your sdcard, coming from another rom I would do a full wipe you can use ARHD superwipe and then flash the rom in recovery.

JonCYY said:
Can you guys include some basic steps on how to flash this rom?
My DHD is currently on the Revolution HD rom.
Click to expand...
Click to collapse
I'm assuming you know how to get in recovery.
Full wipe:
Wipe data/factory reset.
Wipe dalvik
Format all partitions (except sd card).
If you want to go that extra mile, check the md5 checksum to see if it matches right after downloading, before wiping. Do the full wipe, then go wherever you downloaded the rom, flash it. First boot with all roms, is on averqge 5 minutes. If you reach 10 minutes, then something went wrong. Make sure you make a backup of your rom in case anything wrong happens.
Edit: with this rom and only this one - and only this version since it will probably get fixed in the next one, when you are in aroma installer, choose the full wipe. When it prompts you to reboot, say no, and reboot manually. Do not download from dev host. Use one of the mirrors.
Sent from a dream.

So basically when installing this ROM (as of now) to make sure it succeeds all should select to
- wipe throughout the Aroma installer
- select NO to reboot from within the Aroma installer.
Otherwise it doesn't really matter whether you use CWM or 4EXT or any other (Aroma-capable) recovery...
Another issue:
After half a day of awesomeness I ran into the "try to send an SMS and lose your data network" problem described earlier in the original topic the following way (originally Posted by yankee_pr):
"hello!
when sending or receiving mms my data disconnects and signal drops completely to nothing at all then back up to full bars until data connects then back to nothing and so on. this goes on for about a minute. I'm not able to send or receive. when receiving i just get a message trying to download the attachment."
After rebooting or erasing the root_of_cause MMS that I wanted to be sent I went to check APN settings,and figured it wasn't the correct one (for the internet not for the MMS!!!). I have changed it back to the good ones, rebooted and voila.
To be honest I have no clue if the settings were correct beforehand (since installation until it went wrong) so if anyone could check this the community would really appreciate I guess
So 2do:
1. check internet APN settings while it's workin'.
2. Try to send an MMS (like a picture to someone via messages)
3 Wonder why no mobile net connection is available
4. Check if the APN settings are the same or have changed throughout the process
Sorry again but I can post issues here only about this ROM :-o

Gallery and music issues
For those of you that encounter problems of having trouble finding your gallery and music, but yet those files are still in you SD card
Follow instructions below:
1. Plug your phone to your PC
2. Use the search function on your PC and search your SD card for ".nomedia"
3. Delete all
4. Reboot your phone
TADA!!!

Phone no longer has anything in 'Internal Storage', can't download files

A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?

xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root

Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!

dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.

I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!

dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.

NEED HELP! Cant/Denied access internal/emulated storage

i wanted to install new stock rom from here but fastboot wont install it so i went to twrp and tried to flash it from there but during flashing twrp just rebooted itself and saying installation wasnt sucessful, i figured this is due to S-On but prior to flashing it i did possibly the stupidest thing, i went to ADVANCED WIPE and wiped every option on the list(dalvik,system,data,internal storage,cache) except for micro sdcard ofcourse. i then went to FIX PERMISSIONS and stupidly select the ALSO FIX SELINUX CONTEXTS. when those done i then went and install another image which is on the sdcard that i downloaded from here E9pw_Android5.0_Sense70_E1.zip . the installation went well and rebooted itself and got to the homescreen and whatnot. but the troubles came when i tried to install apps from playstore and it gave me all kind of errors known to man, even going into file manager to access the internal storage gave me problem it says something along ACCESS IS DENIED or CANT ACESSS EMULATED OR SOMETHING LIKE THAT. when i opened chrome to download something the browser just crashed because apparently it wont able to access the emulated storage. yeah i fcked up badly here. dont know whatelse to do.
see below of the files that i currently have in my external microsd card:
E9pw_Android5.0_Sense70_E1.zip -WORKS
open gapps arm64 android 5.0 stock
RUU 0PJXIMG_A55ML_DTUL_L50_SENSE70_hTC_Asia_WWE_1.35.7 07.2 - DONT WORK
0PJXIMG_A55ML_DTUL_L50_SENSE70_hTC_Asia_WWE_1.35.7 07.2 - DONT WORK
Thanks!

Got it fixed! by going to TWRP-->WIPE-->FORMAT DATA and reinstall the ROM. if anybody experiencing the same problem please do the same.

Zorg The Great said:
Got it fixed! by going to TWRP-->WIPE-->FORMAT DATA and reinstall the ROM. if anybody experiencing the same problem please do the same.
Click to expand...
Click to collapse
hy i am in exactly same situataion. S ON with twrp installed i accidentaly formatted all and it showd no storage later on i formatted system too and now device has no os. I can still boot in to recovery. DOnt kow what to do now