Hello there,
just want to report a few problems I have experienced installing void.delta.
Right after installation, at first boot, I got several forceclose of com.modaco.launcher.gblauncher. Entering the Recovery and wiping data, cache, dalvik-cache fixed the problem.
After the installation of the modules, when trying to install any application from the market I have been getting the error "package file is invalid". Simply rebooting the device fixed it.
At every boot, in place of the "android" text I get a white rectangle. Still not fixed. Any ideas?
krige said:
Hello there,
just want to report a few problems I have experienced installing void.delta.
Right after installation, at first boot, I got several forceclose of com.modaco.launcher.gblauncher. Entering the Recovery and wiping data, cache, dalvik-cache fixed the problem.
After the installation of the modules, when trying to install any application from the market I have been getting the error "package file is invalid". Simply rebooting the device fixed it.
At every boot, in place of the "android" text I get a white rectangle. Still not fixed. Any ideas?
Click to expand...
Click to collapse
White rectange? Void. shows text:
Code:
[B][SIZE="5"]Void.[/SIZE]
Loading modules...[/B]
maybe it have to do with your data wiping after flashing.... just do wipe before install, not after. This should resolve all yours problem.
Offtopic - this topic should be in development part, I thing....
The_ERROR said:
White rectange? Void. shows text:
Code:
[B][SIZE="5"]Void.[/SIZE]
Loading modules...[/B]
maybe it have to do with your data wiping after flashing.... just do wipe before install, not after. This should resolve all yours problem.
Click to expand...
Click to collapse
I remember seeing that "Void.Loading modules...", now I don't see it anymore. It probably happened after I wiped my data, like you said.
So now, how do I get rid of that white rectangle without having to reinstall the system?
The_ERROR said:
Offtopic - this topic should be in development part, I thing....
Click to expand...
Click to collapse
I don't have permissions to post in that area.
krige said:
I remember seeing that "Void.Loading modules...", now I don't see it anymore. It probably happened after I wiped my data, like you said.
So now, how do I get rid of that white rectangle without having to reinstall the system?
I don't have permissions to post in that area.
Click to expand...
Click to collapse
Do backup with Titanium backup, than NAND and just try flash of void over actual. If it doesn't help, you will have probably do full wipe, install and restore from Titanium (from my point of view it will be best solution)
Related
This ROM has been superceded by MCR 1.5 here.
P
aad4321 said:
Sweet, i might give it a shot. quick question tho... will this wipe the device?
Click to expand...
Click to collapse
Modacp said:
I'm pleased to present my MoDaCo Custom Nexus One ROM! No 'wipe' is required to use this ROM.
Click to expand...
Click to collapse
Reading comprehension much?
aad4321 said:
just to confirm, wavesecure add on is a anti theift program which is a monthly service?
Click to expand...
Click to collapse
No, there is no monthly service charge...at least not yet. I have been using wave secure for a little while now, and for a 3rd party security app its pretty damn good.
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
ccunningham83 said:
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Click to expand...
Click to collapse
did you wipe then restore nandroid?
anyone get tether working on this rom?
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
modaco said:
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
Click to expand...
Click to collapse
neither wireless or wired working for me..
Strange, wireless seems to be working for me I think?
P
wireless tethering say "please wait while starting" but never starts...
any suggestions?
modaco said:
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
Click to expand...
Click to collapse
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
my tether puts a signal out and all but i cant connect to it.. only get local
So after downloading the ROM again after the first one didnt work, I got this for the md5 checksum:
Code:
e04970294888313787d0b9d5cb370a12
Which is entirely different than what is posted on the MoDaCo Forum:
Code:
d537e42372a7239dfaf40846ef0b8b4e
However, I could be doing it wrong. This is the first time I tried using md5 checksums to verify a download. However I used two different utilitys to get the same checksum and I don't want to try to flash it again and have it mess up.
ccunningham83 said:
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
Click to expand...
Click to collapse
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
kevinrirvine said:
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
Click to expand...
Click to collapse
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
ccunningham83 said:
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
Click to expand...
Click to collapse
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
The zips are signed, if a download is corrupt it won't flash.
P
kevinrirvine said:
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
Click to expand...
Click to collapse
I need to re-format my sdcard, I still have the three partitions from my G1. I will give that a try, but I am still unsure about the md5 sum issue. Not too worried about bricking the device after all I put my G1 through.
Thank you for posting here on XDA also
Hi all, I have been searching for info on this but I couldn't find anyone with the same issue than me.
I have a Samsung Galaxy S3 mini, GT-8190.
The first symptom was that my phone reboots itself constantly. My phone is rooted. I have TWRP installed.
I tried to flash a stock rom with Odin, it seemed to go well, but when the phone rebooted it was the same as before. I tried wiping the data with TWRP but when it reboots, everything is there again. I tried uninstalling the apps manually, but when I reboot the phone, they appear again. It's like I can't change anything in the internal memory. I can't do a factory reset, it reboots exactly the same as before.
It is like the internal memory is completely frozen. If I uninstall a program, it reappears on reboot, If I install an app, it disappears, If I turn off the wifi, it appears ON when reboot...
I'm going crazy with this, please ask me if you need any more information.
Regards,
Martin.
martinoj04 said:
Hi all, I have been searching for info on this but I couldn't find anyone with the same issue than me.
I have a Samsung Galaxy S3 mini, GT-8190.
The first symptom was that my phone reboots itself constantly. My phone is rooted. I have TWRP installed.
I tried to flash a stock rom with Odin, it seemed to go well, but when the phone rebooted it was the same as before. I tried wiping the data with TWRP but when it reboots, everything is there again. I tried uninstalling the apps manually, but when I reboot the phone, they appear again. It's like I can't change anything in the internal memory. I can't do a factory reset, it reboots exactly the same as before.
It is like the internal memory is completely frozen. If I uninstall a program, it reappears on reboot, If I install an app, it disappears, If I turn off the wifi, it appears ON when reboot...
I'm going crazy with this, please ask me if you need any more information.
Regards,
Martin.
Click to expand...
Click to collapse
if your phone is rooted then try to delete the apps in the system/apps using root explorer
Vaibhav Chauhan said:
if your phone is rooted then try to delete the apps in the system/apps using root explorer
Click to expand...
Click to collapse
I tried, anything I delete, it comes back after reboot, even if I copy a file while being connected to a PC, it disappears after reboot.
martinoj04 said:
I tried, anything I delete, it comes back after reboot, even if I copy a file while being connected to a PC, it disappears after reboot.
Click to expand...
Click to collapse
have you any backup which restores at boot?
Vaibhav Chauhan said:
have you any backup which restores at boot?
Click to expand...
Click to collapse
No, I even tried to flash different roms on the phone, TWRP says it can't open the zip file, ODIN says that everything is OK, but when the phone boots, the old rom with all the files is there.
Any help? anyone has a clue how can I deep wipe this phone?
martinoj04 said:
No, I even tried to flash different roms on the phone, TWRP says it can't open the zip file, ODIN says that everything is OK, but when the phone boots, the old rom with all the files is there.
Click to expand...
Click to collapse
i think you should go to samsung care service center
Hi martinoj04,
Did you found a solution for this?
I am currently having the same issue with an Ace2 (GTI8160).
Any helps or pointer would be appreciated.
I bricked my phone.
h850 open bootloader. i tried to format the internal storage. didnt made a backup. now it wants a password and my own one doesnt work. is there any chance to repair it?
thank you in advance!
What wants password? TWRP ?
Try to flash the latest v10e KZD file with LGUP.
on a side note: what will happen when all tries are gone? will it erase it self? there is nothing to loose for me if this is the case?!
kripo said:
on a side note: what will happen when all tries are gone? will it erase it self? there is nothing to loose for me if this is the case?!
Click to expand...
Click to collapse
I dont know that counter your talking about. After restoring a backup from TWRP I got an issue that it wont accept my pin code to enter the phone. I've followed the steps in this link and it deleted the pin code. I hope this will help you. Please post your result. http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Please delete ALL 5 files one by one. It worked for me every time.
ItsNewDroid said:
I dont know that counter your talking about. After restoring a backup from TWRP I got an issue that it wont accept my pin code to enter the phone. I've followed the steps in this link and it deleted the pin code. I hope this will help you. Please post your result. http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Please delete ALL 5 files one by one. It worked for me every time.
Click to expand...
Click to collapse
hm, i dont think that this is the same thing on my phone.
just to clarify what i did:
i flashed no-verity-opt-encrypt-2.1.zip
i erased userdata and cache in fastboot
i flashed LG-H85010E-Flashable.COMPLETE.zip and FLUENCE_HD24_PATCH.zip
and then my problem(screenshot) occurred
kripo said:
hm, i dont think that this is the same thing on my phone.
just to clarify what i did:
i flashed no-verity-opt-encrypt-2.1.zip
i erased userdata and cache in fastboot
i flashed LG-H85010E-Flashable.COMPLETE.zip and FLUENCE_HD24_PATCH.zip
and then my problem(screenshot) occurred
Click to expand...
Click to collapse
I never ever have seen such a screen
But I would guess that something went wrong when flashing 10E or the patch.
I recommend the following:
- Check if TWRP is still installed
- If yes, format data again
- Re-flash SuperSU or no-verity-opt-encrypt-2.1.zip
- Reboot
If you lost TWRP, you have to flash it again, format data etc.
I've done all the steps you have listed few times but never encountered this problem. Can you even access the TWRP menu? Maybe ask Miustone the developer of HD24? Please tell if you can access the TWRP and your files
BabelHuber said:
I never ever have seen such a screen
But I would guess that something went wrong when flashing 10E or the patch.
I recommend the following:
- Check if TWRP is still installed
- If yes, format data again
- Re-flash SuperSU or no-verity-opt-encrypt-2.1.zip
- Reboot
If you lost TWRP, you have to flash it again, format data etc.
Click to expand...
Click to collapse
after formatting data in TWRP the new screen appears, thanks for that. but the bar in the new screen(screenshot) doesn't change.
the button beneath the bar makes the phone going into recovery and format cache.
repair data after format data did the trick! thanks everyone for the fast help!!! love you all
Hello there. So today for some reason I've got a message from Device Security saying "Unauthorized actions have been detected. Restart your phone to undo these actions."
I did restart my phone, by tapping the restart option on the screen. It turned off, went to a blue screen, restarted and the message kept popping up..
I also tried to factory reset the phone, still no luck.
Has any of you went through this? Or found a way to revert those "Unauthorized actions" ?
Fix system error message
I understand your problem. Just try to reinstall your OS using Samsung Kies. Full tutorial here : https://www.youtube.com/watch?v=LqoX7wNhotk
I hope it'll be fixed as soon as possible
Good luck,
Thanks, but it didnt worked. :| anything else?
Glitchy message. I don't know why it sometimes go in comment part
Well..I tried to flash a frimware hopefully it works. If not, I'l try this :|
Okay, try to install twrp, do a full twrp backup (=nandroid backup) and then install Lineage OS. Full tutorial here : https://www.youtube.com/watch?v=a8-ISL3gM_s
Hope it will solve your problem. Twrp backup is usefull, so you can restore your data in lineage os using Titanium backup.
You also can try to wipe every partitions in TWRP except /sdcard and reinstall os via Samsung Kies
Well...It seems the device is back.. but how it will run..
What do you mean by "the device is back.. but how it will run.. "
Is it working
Yea.. I mean it's working again. Idk how.. But now that I've used Odin to flash a stock rom, the warranty is still available?
GalaxyRSR said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post74899750
Click to expand...
Click to collapse
Have you flash with Odin yet?
yes i did.. its working now
Hi,
After successful rooting and rebooting, i have hit "Cleanup to switch to another superuser app" and now, cannot boot. Phone stays with Mi logo and constanty loops with screen blink.
Tried to go to recovery mode, reinstall SuperSU, clean cache, but no luck.
Kindly asking for help.
Flash fastboot rom and root again.
tried, didnt help.
TWRP loads ok. SR3-SuperSU-v2.79 also installs, cache wiped/dalvik, all same
at4500 said:
tried, didnt help.
TWRP loads ok. SR3-SuperSU-v2.79 also installs, cache wiped/dalvik, all same
Click to expand...
Click to collapse
Wipe data, cache, and dalvik, and reinstall your ROM. You will lose all your data, downloaded apps, and settings (I hope you made backups of them), but you will have your phone back.
at4500 said:
Hi,
After successful rooting and rebooting, i have hit "Cleanup to switch to another superuser app" and now, cannot boot. Phone stays with Mi logo and constanty loops with screen blink.
Tried to go to recovery mode, reinstall SuperSU, clean cache, but no luck.
Kindly asking for help.
Click to expand...
Click to collapse
Reinstall rom as DarthJabba said and also start using Magisk instead of SuperSu, since its more compatible and stable.
MyNameIsRage said:
Reinstall rom as DarthJabba said and also start using Magisk instead of SuperSu, since its more compatible and stable.
Click to expand...
Click to collapse
Thanks, this made my day, finally decided to opt for reflashing.
Here is a good vid guide for ones who do it first time in life:
u tube dot com slash watch?v=mfXd5E-Ix6w
Will look for magisk now. Thanks again. Phone is usable now.
at4500 said:
Thanks, this made my day, finally decided to opt for reflashing.
Here is a good vid guide for ones who do it first time in life:
u tube dot com slash watch?v=mfXd5E-Ix6w
Will look for magisk now. Thanks again. Phone is usable now.
Click to expand...
Click to collapse
Good news. You probably only needed to wipe the data partition - but you might as well start afresh.
BTW, I have been using supersu for a long time, without any problems. So I would very much doubt whether rooting via supersu was the cause of the problem. I suspect that the problem might have been caused by "Cleanup to switch to another superuser app". I have not done that in years, and I am not sure why anyone would want to do it now.
There is no harm trying magisk, but I prefer supersu myself.
DarthJabba9 said:
.. I suspect that the problem might have been caused by "Cleanup to switch to another superuser app". ..
Click to expand...
Click to collapse
Right, this is (silly of me) exactly what i did.