Hi,
I have a HTC Dream that I found abandoned at work and Im not completly sure if it is the European or American (the company where I work is in Europe, but when I was rooting as per the cyanogen wiki Dream:Rooting, it was the US version which worked for me.
Well, after rooting, I installed the Danger SLP as per the cyanogen wiki DreamangerSLTP and I've used the 2.22.19.26i Non US radio.
Then, I tried running the Cyanogenmod 6 installation as per the cyanogen wiki Dream:Cyanonge5+ , however I must say that the link to the Cyanogem 6 was broken at the cyanogen page so I used the one I downloaded from a blog post as his MD5 hash matched the one described on the broken link at the cyanogenmod wiki.
I've tried 3 times to flash both that cyanogen and the google apps tiny (from cyanogens page) but I was always stuck at the Cyanongem with a bootloop. I've copied the logs to this pastebin link u9uSwpdr under pastebin website (sorry I cant post links =() The log points to a couple of exceptions, but Im new into android and I have no clue which ones are serious =D
However, it is woth to mention that the process works fine (boot/network and everything) if I try to flash the cyanogen 6 without the google apps. I thought it could be a memory issue, but I wiped the memory (with flashboot) before the failed installs and if I go to the memory settings, of the install without google apps, I see that there is 63.91 mb of space on the internal phone storage.
Any ideas of what could be missing for me to be able to install the Cyanogen 6 with the google apps?
Cheers
same problem, got this G1 from my cousin til my N4 arrives
I have 2 year old Touchpad that was running Android 4.2.2 and tried to update to 4.3.1 and trashed it. I was running CM 7, upgraded to 9, then 10, then 10.1. I did everything to try and salvage it and read every article possible with NO luck.
SO, I decide to use Acme Uninstaller to remove it, but had issues seeing the Partition and it wanted to FORMAT - I did NOT FORMAT because everyone said not to.
SO then I did a factory reset on the Touchpad and erased it. This worked and allowed me to try and get back to CM 10.2.
The problem is that I cannot find a single installation method that shows the simplest steps to install CM10.2 ( Android 4.3 ) without having to install older version of CM9, or CM10.
I have tried every possible article and method and so far here is what I am stuck with.
I can install CM9 with Moboot BUT CWM and TWRP will not install so I cannot update GAPS.
I erased and then tried using the TAILOR Web OS app to increase the OS partitions from 400mb to 600 mb and that installed fine.
Then I installed CM 10 using ACMEInstaller 3 and it boot loops.
Then I tried CM 10.2 using ACMEinstaller3 and it will not install and says the package is invalid.
It seems like something do to with the partitions and that is why I cannot installed CWM, TWRP or GAPS or even an update.
The only thing I have NOT done is use WEB OS Dr. because I thought this is for when WEB OS is trashed.
I know this seems like a re-post but it really isnt
IF anyone has a simple document that details exactly how a Touchpad should be correctly erased and then install a fresh CM10.2, I would really appreciated it.
There just does not seem to be any articles or you tube videos that show this processes.
I am sure there are a lot of people that would benefit from a guide for CM9, CM10 or CM.2 by doing a complete erase and start over.
I have started writing my own documents but of course I cannot finish it.
Please help and point me in the correct direction because I am stuck with only WEB OS.
cmakar said:
I have 2 year old Touchpad that was running Android 4.2.2 and tried to update to 4.3.1 and trashed it. I was running CM 7, upgraded to 9, then 10, then 10.1. I did everything to try and salvage it and read every article possible with NO luck.
SO, I decide to use Acme Uninstaller to remove it, but had issues seeing the Partition and it wanted to FORMAT - I did NOT FORMAT because everyone said not to.
SO then I did a factory reset on the Touchpad and erased it. This worked and allowed me to try and get back to CM 10.2.
The problem is that I cannot find a single installation method that shows the simplest steps to install CM10.2 ( Android 4.3 ) without having to install older version of CM9, or CM10.
I have tried every possible article and method and so far here is what I am stuck with.
I can install CM9 with Moboot BUT CWM and TWRP will not install so I cannot update GAPS.
I erased and then tried using the TAILOR Web OS app to increase the OS partitions from 400mb to 600 mb and that installed fine.
Then I installed CM 10 using ACMEInstaller 3 and it boot loops.
Then I tried CM 10.2 using ACMEinstaller3 and it will not install and says the package is invalid.
It seems like something do to with the partitions and that is why I cannot installed CWM, TWRP or GAPS or even an update.
The only thing I have NOT done is use WEB OS Dr. because I thought this is for when WEB OS is trashed.
I know this seems like a re-post but it really isnt
IF anyone has a simple document that details exactly how a Touchpad should be correctly erased and then install a fresh CM10.2, I would really appreciated it.
There just does not seem to be any articles or you tube videos that show this processes.
I am sure there are a lot of people that would benefit from a guide for CM9, CM10 or CM.2 by doing a complete erase and start over.
I have started writing my own documents but of course I cannot finish it.
Please help and point me in the correct direction because I am stuck with only WEB OS.
Click to expand...
Click to collapse
I too am having a confusing time with my TP. I've tried a few ROMs and I just want to basically erase everything and install a single, fresh new ROM. I haven't touched my TP in quite a while so i've forgotten all the confusing steps it took to originally root it. Some guidance would be great.
Finally have CM 10.2 / Android 4.3.1 installed
I wanted to let you know that I was FINALLY able to get a fresh install of CM 10.2 / Android 4.3.1 installed using the NEW ACMEInstaller 5 T.
I also used the ACMEUNINSTALL2 that was re-posted.
So I plan on Factory wiping my Touchpad so that I can document the process from beginning to end and if it works, then I will post my instructions.
Of course I make no guarantees like everyone else states, but I am following pieces and parts of what everyone else posts and just trying to make a simpler guide. There are lots of guides but nothing that seems to work at all for me and lots of other people are saying the same thing.
iamdestruktor said:
I too am having a confusing time with my TP. I've tried a few ROMs and I just want to basically erase everything and install a single, fresh new ROM. I haven't touched my TP in quite a while so i've forgotten all the confusing steps it took to originally root it. Some guidance would be great.
Click to expand...
Click to collapse
Summarized Standard Disclaimer: use at your own risk. I use it at mine
*Full wipe recommended if coming from another rom due do the settings database varying and no way to make them compatible*
My personal Omni Rom 5.0 is based on omnirom with the following additions:
CM12 File Manager
CM11 ssh terminal commands
Bash shell
Nano text editor
Koush's full featured open source superuser integrated into settings***(see potential quirk)
Cyanogenmod custom host name
Cyanogenmod screen off volume key long press music control
The list of personal touches isn't very long right now but they include
Battery percent displayed next to battery icon
Battery icon changes color based on percent: 0-15 red, 16-50 yellow, 51-100 green
Disabled lock screen full screen music.
Disabled SELinux at the kernel
Up to 1.6GHz CPU OC
Automatic 400MHz GPU OC
Not Working/Quirky
Bluetooth audio
Mic can be quirky.
Stock camera (not included) would crash on camera change, photo/video change. Try this open source alternative instead. Full featured, nice and fast.
AOSP keyboard swipe doesn't work: google's fault.
Cellular data probably doesn't work. phone call audio doesn't work. The rest is reported ok.
Flashing SuperSU might cause issues since the su daemon is started by the ram disk script since boot scripts apparently don't work.
Plugging in a charger when turned off causes the tablet to turn on with the touch screen disabled.
Everything else not listed as a quirk probably works.
*First Time*
-Read second post FAQ and other important information
-Make titanium backup (highly recommended)
-Flash TWRP 2.8.1.0
-Flash fixed twrp 2.8.0.0 for TMobile users
-Reboot into new recovery
-Make recovery backup (meh, I don't usually do it but you have been warned)
-Full wipe
-Format system
-Install rom
-install gapps (you can use another one if you want. I always provide the most minimum gapps)
-reboot
-TURN ON WIFI IMMEDIATELY AS SOON AS POSSIBLE
*Subsequent flashes*
-TURN ON WIFI BEFORE REBOOT RECOVERY
-Install ROM
-Install gapps
-Reboot into rom
-Reapply any adblocking hosts file.
Downloads
Mediafire folder (discontinued)
Gapps Android File Host
TWRP Android File Host
Wifi ROM Android FIle Host
3G ROM Android FIle Host
TMobile ROM Android File Host
Credits:
-decatf: your patches were vital to the rom
-drewwalton19216801: used your gapps for the minimal gapps package
-kasper_h: I learned a lot from doing kitkat with you last year
-pershoot: original device/vendor base
-omni team: providing rom
-cyanogenmod team: rom extras
Sources https://github.com/AAccount?tab=repositories
Screenshots: a picture is worth 1000 words but a video is worth exactly 30 pictures/second (mostly).
XDA:DevDB Information
Omni 5.0, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Weekly
Created 2014-11-24
Last Updated 2014-11-23
Delete
FAQ:
OMFFFFFFG: insane boot loop 10 seconds after lock screen: install any rom from the year 2015.
Missing gapps: remember to reflash after every rom.
Adblock hosts stopped working: remember to reapply ad block hosts after ever flash.
Google maps 9+ doesn't work due to an illegal instruction exception. No practical way to fix it. Install google maps 8.4 it works now. Make sure you use the latest google maps.
No keyboard: Settings --> Language & Input --> Current Keyboard --> Hardware (show input method) turn this on.
AOSP swipe doesn't work: apparently google removed these lines of code from aosp keyboard.
Launcher 3 crashes on boot since Feb 8 build: I switched to CM's launcher since it has some customizability. Go to /data/data/com.android.launcher3 FROM RECOVERY and erase this folder.
THIS IS A TEST ROM. PLEASE REMEMBER THAT
For those of you who are itching to try the android 5.1 build I've done some basic quick testing and I like how it's going. The chromium bug I got this afternoon seems to be taken care of with 2 commits. Look at them if you want to know the secret
Installation Instructions (may not be complete as I've installed a lot of zip files. Please try and fill in the missing holes as the rom does install and boot)
Reboot recovery
Wipe data
Format system
RE reboot into recovery
install rom
install my recommended android 5.0 gapps (have heard issues using others but not tried it myself)
try it out
report the bugs
What works: everything thing that worked in 5.0 should continue working.
The camera app has a bit of a "confidence" problem. It will crash on switching to front/back photo/video but if you open it again it will do what you wanted. Sometimes it doesn't crash. Give the camera app patience.
Link: https://www.androidfilehost.com/?fid=95916177934541869
Great news. Downloading asap.
Is just enough to have WiFi on, or it must also connect to some network to avoid bootloop? I'm concerned what happens if I turn it on in the desert where there's no Wi-Fi whatsoever?
Hi.For p4 expected? Thanks.
jaibar said:
Great news. Downloading asap.
Is just enough to have WiFi on, or it must also connect to some network to avoid bootloop? I'm concerned what happens if I turn it on in the desert where there's no Wi-Fi whatsoever?
Click to expand...
Click to collapse
Just on. No connection necessary. You can also feel free to turn it off after a few minutes of just being on. Just remember to turn it back on before a reboot or weekly flash.
@AAccount thanks for bringing omni 5 to the tab was running ur kitkat build, however not sure if anyone else is having install issues, installed twrp 2.8.0.0, factory reset and wiped system, but when trying to install zip i get the following error:
Set_perm: some changes failed
Error excuting binary in zip
Error flashing zip
Any help or info would be appreciated.
Thanks
emu1982 said:
@AAccount thanks for bringing omni 5 to the tab was running ur kitkat build, however not sure if anyone else is having install issues, installed twrp 2.8.0.0, factory reset and wiped system, but when trying to install zip i get the following error:
Set_perm: some changes failed
Error excuting binary in zip
Error flashing zip
Any help or info would be appreciated.
Thanks
Click to expand...
Click to collapse
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
AAccount said:
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
Click to expand...
Click to collapse
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
emu1982 said:
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
Click to expand...
Click to collapse
Maybe you should pull a recovery log and post it here so @AAccount can see what's going on.
Can't download twrp2810-wifi.zip from mediafire, always only download 2m then interrupted.
Anybody who can send me a twrp2810-wifi.zip, my email is
[email protected]
Thank you very much!
mediafire failing to download any file I try to download from it
Can't download twrp2810-wifi.zip from mediafire , I am having a problem too with mediafire, each time I click on download , it refreshes loops the download page, no file is able to access, I think it has something to do with our ISP, we moved into a place that you can only use hughesnet to access the web, I can't get DSL from the house my parents got etc.. , I tried the cleaning the cache like this page
http://topkpop.wordpress.com/2010/05/10/solution-for-mediafire-continuous-refresh-download-problem/
it says that removing cookies fixies this but it is not , still failing to access any files off of mediafire, I was able to create a mediafire account , and download their desktop software, but can't get files like from your links to work, it seems , I have tried internet explorer, firefox, and google chrome, each browser doesn't want to let me download etc to save the file, The only thing I have yet to try is use my android tablet to access the links, I don't no if mediafire will work right or not over my android, if my download pc doesn't download it, from my wireless network ,
my android tablet also can't access the files. I just tried to download twrp2810-wifi.zip from mediafire off of browser on android , when you click download it keeps looping and freshing the page, but what it doesn't do is download, I am in US, CA so it shouldn't be blocking me from downloading files, not sure why this seems to be happening, it was not a problem with our old isp before me moved etc..
I don't no if this explains it, but on android , when click download it reloads this page"http://www.mediafire.com/download/6hc9ws7sd96j3nn", instead of this "http://www.mediafire.com/download/6hc9ws7sd96j3nn/twrp2810-wifi.zip" I been tried to click download over and over , even the repair download thing, doesn't do anything , after clicking on download a few, times I got that message.
I am able to use
Downloads
Mediafire folder
Click on the files, and use the copy to my accounts folder option, which sync it to the desktop software, that feature is working for me, just not mediafire download pages
anyway can you give me access to the folder, that has Flash file TWRP 2.8.1.0, since then I could click the copy feature of mediafire, and transfer it to my account on mediafire, and it will download and sync the file to my folder on my computer, thats the only way or simplist way to get passed that looping on download page problem, or maybe copy the file into your mediafire folder if that also possible I hope,
don't have to have the newest version to flash right away , but it would be nice if I was able to access it, to flash anyway, I still got the 2.7 version of twrp, after using android 4.4.4 nameless etc.. before I got problems with mediafire from my web browser problem, and access to cwm boot flash manager too, which I found files on the web for flashing with touch screen option, while browsing the forums here
attached downloads will download no problem, and other websites besides mediafire will also work just fine for me, since it seems to be a mediafire download page problem only bug,
also talking about bugs, does this rom have that power on charging , bug like the rom [AOSP] Android 5.0.0 Lollipop (LRX21V) has?
"Whenever I try to charge the tab while it's turned off, it boots up. Is this a new feature of Android 5.0? Also it doesn't respond to touches. " , on its last page I read that its a new feature of the android 5.0 based on aosp rom, it reads " It turns out there is a new feature in Lollipop to boot from charger but it is not enabled by default. It is only for one specific device at the moment. I reverted the code anyways but the problem still exists. So the issue lies deeper some where." , source information can be found here, http://forum.xda-developers.com/gal...-5-0-0-lollipop-lrx21m-p4wifi-t2938870/page17
if this rom doesn't have that problem, maybe something can be learned from it , to fix the bug in the other rom, since our tablets , don't like that feature, since it locks up our tablets touchscreen from doing anything but hard rebooting them etc.. when plugged into power when in off mode etc...
emu1982 said:
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
Click to expand...
Click to collapse
Same here, switched from CWM to TWRP 2.8.1.0 and I'm still getting the error D:
AAccount said:
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
Click to expand...
Click to collapse
Was able to download TWRP and gapps just fine but the ReCaptcha you have to complete in order to download the ROM won't load a picture. I have tried on my tablet, phone and computer... Able to pass a ReCaptcha on other pages just fine, clearly an issue with this specific download page. Anyone else having this issue?
L3R0N said:
Maybe you should pull a recovery log and post it here so @AAccount can see what's going on.
Click to expand...
Click to collapse
http://pastebin.com/xSr4TLCY
@AAccount here is a twrp log of the install issue i had trying to install after a full wipe. Hope it helps..
For people with download problems, will it be ok if I register for an account here:
https://www.androidfilehost.com/user/?w=register
Will that be a good file hosting site?
I know its still early development for 5.0 rom versions of android 5.0, do you guys know why scummvm version 1.7.0 release will not download and install, it keeps failing to download for me on android 5.0, from google play website, also the development version 1.8.0 direct from scummvm will install but crashes on play, off of http://scummvm.org/
I know that scummvm app, worked for android 4.4.4 nameless rom, I used it under that android before, never crashed that I can remember, I hope as android 5.0 builds makes progress that whatever causing it to crash gets fixed. I am not sure if its something that needs to be fixed in the android os system of 5.0, or if its something that needs fixing in the scummvm app, that causes it to crash under android 5.0, maybe future development builds of scummvm will fix the crashing under android 5.0.
and below a fix to the charging bug I think its a fix I have yet to test it from this page, since both our based on android 5.0 I am guessing that these files will fix booting on both
source page "http://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-5-0-0-lollipop-lrx21m-p4wifi-t2938870/page17"
decatf said:
Charging mode should be working now although there are still some issues to be ironed out. Note(!) that ADB is running in while in charger mode. I haven't figured out why yet.
It only requires an update to the boot partition. Flash and reboot.
bootimg-p4-lp-20141125.zip
bootimg-p4wifi-lp-20141125.zip
The problem is that Samsung did not follow the Android method of booting into charger mode. With Android 5.0 this method of booting is not working. So I ported it to work with the Android method. Which means it is booting slightly differently than the old charger mode.
Someone others mentioned issues with overclocking. I have not had a chance to look into this yet.
Click to expand...
Click to collapse
Omni 5.0 p4wifi Nov 23
Re scumm vm... Could it be dalvik vs ART? I have done very little research.. Just know that xposed -framework- (and most modules?) require dalvik.. Put another way, not (yet?) compatible with ART
5.0 has no option for dalvik, whereas 4.4.4 can do both
One possible test: reflash 4.4.4, switch to ART, then see if scumm works?
Or if I am off base, hopefully someone else will chime in...
I never tried the android 4.4.4 under art, so maybe it would of crashed scummvm too , I don't no if its compatable with art maybe thats why, also I did want to note , that unlike the AOSP android 5.0 rom, in this one, google now launcher seems to crash , but I didn't notice crashing in the other android 5.0 , is it because it has had more time to fix the bugs in the os system, since Omni 5.0 p4wifi is a newer rom? I am correct or is their something that needs to be fixed in google now launcher or the build of the rom?
Hey guys, I am using open beta 17.. Android Oreo.. Nd I realised that open beta version consumes more battery so I decided to roll.back to 4.5.0 stable os... nd since I was having the zip file in my internal storage, I selected to local upgrade from software updates in my one plus 3t ..
The process started nd after few seconds it went to recovery, and it said that " updating, please wait"... nd after few more seconds, it said that "upgrade failed" ... reboot
help me...
You'll need to flash the special open beta to go back to nougat and then flash the stock build. Before flashing the stock build, clean wipe.
You cannot revert back to Nougat/Marshmallow directly from the Open Beta. There is a special firmware package to be flashed and there is partial loss of data.
As quoted on https://forum.xda-developers.com/one...d-7-1-t3564240
"Notice:
If you want to revert back to the last Open Beta N build (OnePlus 3 Open beta 24 or OnePlus 3T Open Beta 15) you will need to flash the special build provided below. Because of the nature of downgrading from a major version, this will cause you to lose partial data.
Instructions and Info:
The build will wipe app and cache data, but Internal Storage will be saved (ie: pictures and files)
Users who revert their device back to the special build can still OTA update the device to Android O build at a later date."
You can't install the stable version directly, only via the installation of the special build, then installation of the stable package.
That special firmware package totally wiped my phone to zero, all files on the internal drive were wiped and it formated it to f2fs, I have 128gb internal storage, after the boot up it only showed 30gb (afair), I lost everything and I was devastated so please everyone be very careful with that so called "Special firmware", also this is just my experience with that special build other people's experience may be different, all the best to everyone, cheers.
Anandrv said:
You'll need to flash the special open beta to go back to nougat and then flash the stock build. Before flashing the stock build, clean wipe.
Click to expand...
Click to collapse
Was that special build removed ?
Please do not create duplicate threads or posts. Additionally, please post your threads in the correct forum. The development forums on XDA are not for Q&A threads. Your previous thread on this topic has already been moved to the appropriate Q&A forum. This thread is closed.
Cheers,
Magnum_Enforcer
FSM