This thread is outdated. To visit the current thread view this thread
Due to not having enough posts or something i am unable to post in the Dev section so i am going to have to post in the general section. If an admin would be so kind as to transfer it to it's rightful place it would be greatly appreciated.
Down to business, i have been working on a rom as of the last few weeks and finally got around to finishing it. It is still in early stages but i have flashed it multiple times with no issues and i am awaiting confirmation from one other upon successful flash.
Unfortunately the IRC hasn't been to active as of lately so i have been out of touch with people untill recently.
Anyways, heres the writeup of this rom in question:
Code:
Initial Release of Miunia
This rom was initially based off of ec07-nuckin, it has been made to my liking using other things out there. so enjoy.
Current Tweeks include:
Custom kernel with custom boot and memory management(imnuts)
AOSP lock screen(imnuts)
AOSP Launcher (Launcher2)
reboot options(imnuts)
soft keys themed with white text (modified framework-res to include aosp lock screen, reboot options as well as themed soft keys)
removed swype
added back in file browser(had issues with music play and a few other things when removed; makes it easier when you want add in your own apks without downloading a browser from the market)
hacked browser (trailblazer101)
Inverted market(credit where it belongs, i forget where i got this from)
Theres a few other things i have done that i can not remember off the top of my head.
To DoList:
build.prop
Boot animation
zipalign
Remove more bloat
touch sensitivity
Busy box
Credit goes out to:
imnuts
trailblazer101
nuckin
Download from one of the links provided, unzip the folder and install miunia.tar through pda via oden.
Enjoy!! let me know what you think, any issues, critiques, etc. let me know.
Forum link: miunia unzip me.zip - 145.5 MB
http://www.filefactory.com/file/ce6466d/n/miunia_unzip_me.zip
Here is a copy of the actual odin file not zipped so it is about 330MB
Miunia.tar Odin file
This is how it will look upon install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
by holding down the launcher tab it opens up a view of all 5 screens
I have created a basic boot animation update.zip installer file for CWM
that's the animation.
i'll post it up. if any others want an animation for this rom let me know.
rename this to animation.zip, open in CWM and install. You must be running the custom kernel to allow boot animations though.
http://www.mediafire.com/?ccag34xcurxxt70
apparently there has been an issue with the downloads so i will be reuploading them tomorrow afternoon.
Yes.
I'm all over this! Flashing it over now we'll see what happens!
First Impressions
Flashed from EC03 and just rebooted. I have CWM2.5 and the first boot took a while to load. I waited about a minute. The lock screen looks pretty standard with the slide to unlock and unlocks responsively though waking up seems to lag the tiniest bit. Didn't wipe or factory reset so everything still seems to be intact. I'm enjoying the custom soft keys.
Though I've upgraded to EC07 I'm still seemingly having radio problems. Still have the big red D under my 3G where my green arrows used to be. Otherwise everything is running smoothly. I'm going to play with it for a while and see if anything changes, try to push some data through and see if my connection snaps out of whatever kind of rut it's in. Smooth ROM, nice and simple.
+Browser! Loads the XDA Forums nice and quick.
+Fixed an issue I was having when clicking "read the full story..." from the RSS menu.
I'll post more as I screw around with this but it's certainly nice to be a part of the EC07 world. Props to Miunia thus far. Hope to see an update and maybe a little love this way in the future.
EDIT: UPDATE!!
Cleared cache from Recovery and rebooted phone. Almost instantly turned on. Removing some old apps like the GoLauncher and Dolphin HD from the old CM03 because they interfere and when I tried to factory reset from Recovery it wouldn't allow it. I'll have to try from the UI menu. Also I'll be attempting to flash the new animation in with CMW. Looks neat. Can't wait. More info soon!
When installing you have two options, if you choose to flash normally it will flash the launcher, kernel and other tweeks ontop of your current state, essentially cleaning it up a bit, but you will have all contacts, and other data intact.
If you want the full Ron I recommend wiping system data and dalvik prior to the install. This will ensure a full and complete install of only this rom.
Please let me know of any issues you run into. It is considered beta and is my first release. Current known issues are:
Cannot edit launcher preferences
Force closing on browser
Easy solutions are to get a new browser untill I release another beta, and for the time being deal with the lack of launcher preferences. I will look into that this evening.
Sent from my continuing.. ummmm. using Tapatalk
err....
Tried running the Factory Reset from UI after failed in Recovery. Phone rebooted into recovery again and failed.
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please UI menu for format and reboot actions
copy application failed.
Go Into cwm, mounts and storage, format system and data then flash.
Don't do it from within the Odin gui
Sent from my SCH-I400 using Tapatalk
Reflashed CWM2.5 on Odin just to be sure but I'm still booting into the regular Samsung Recovery Utils for BML <2e>.
EDIT: Didn't apply update.zip that's my fault for being a retard, one moment while I do my reset.
EDIT EDIT:: Reflashed Miunia, then applied update.zip in the recovery reboot, then tried to wipe data but every time I get snagged on something. Pretty frustrated but working through it. Just want to know I'm doing something right.
After you format the system and data you have to reinstall the Ron through Odin. By formatting it it deletes the data on that partition. So you will be flashing the new data in place.
I will add a script to format everything for you.
Sent from my SCH-I400 using Tapatalk
Yeah, I reflashed once again this time getting:
when phone boots into regular recovery
E:Can't mount /dev/block/stl11
(invalid argument)
#manual mode#
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
after applying update.zip into CWM 3.2.0:
CWM Voodoo Lagfix Recovery v3.2.0.0
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
under mounts and storage:
- mount /cache
- unmount /data
- mount /datadata
- unmount /sdcard
- unmount /system
then options to format the above followed by
- mount USB storage
---------- Post added at 06:00 PM ---------- Previous post was at 05:43 PM ----------
I have absolutely no idea what I did or touched but the phone booted back up into Miunia! Thank god. I'm back to the UI. I'm assuming those error messages in recovery are still present but I'm a little scared to boot back into it at the moment. Let me know where to go from here, otherwise it looks like a clean install of your ROM. I'll play around and see if anything goes haywire, keep me in the loop.
-Asellite.
Probably just some weird glitch. They happen from time to time. If it happens again id flash a 100% stock copy then do it again.
For now though, enjoy and keep us posters on your thoughts and opinions. Also, let us know anything else you would like to see and I'll try and take it into consideration
Sent from my SCH-I400 using Tapatalk
pattielipp said:
When installing you have two options:
if you choose to flash normally it will flash the launcher, kernel and other tweeks ontop of your current state, essentially cleaning it up a bit, but you will have all contacts, and other data intact.
If you want the full ROM I recommend wiping system data and dalvik prior to the install. This will ensure a full and complete install of only this rom.
Click to expand...
Click to collapse
Excellent explanation.
Unfortunately, wiping system data and dalvik doesn't seem to wipe any of my existing stuff (not even account information!). Weird, but this is a fact, at least on my particular ec07-clean device.
Right now, I am in a rush to meet a deadline, but when I get a chance I would love to have your ROM instead of what I have now. And then I will research this strange phenomenon.
In the meanwhile, I suggest adding an article about your ROM to this excellent list of articles.
asellite said:
Yeah, I reflashed once again this time getting:
when phone boots into regular recovery
E:Can't mount /dev/block/stl11
(invalid argument)
#manual mode#
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
after applying update.zip into CWM 3.2.0:
CWM Voodoo Lagfix Recovery v3.2.0.0
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
under mounts and storage:
- mount /cache
- unmount /data
- mount /datadata
- unmount /sdcard
- unmount /system
then options to format the above followed by
- mount USB storage
---------- Post added at 06:00 PM ---------- Previous post was at 05:43 PM ----------
I have absolutely no idea what I did or touched but the phone booted back up into Miunia! Thank god. I'm back to the UI. I'm assuming those error messages in recovery are still present but I'm a little scared to boot back into it at the moment. Let me know where to go from here, otherwise it looks like a clean install of your ROM. I'll play around and see if anything goes haywire, keep me in the loop.
-Asellite.
Click to expand...
Click to collapse
Iseen ur using cwm 3. 2
Use cwm 2. 5 red or cyan
Sent from my SCH-I400 using xda premium
Just got back from dinner and my basic plan is to flash from Miunia to ec07 clean and then try my wipe with CWM 2. 5 and reflash Miunia. Noticed the browser force close since I've gotten the UI to boot back up so you aren't the only one noticing that, but like you said it's an easy work around to handle. Also, I can't get my XDA app to open correctly. This may just be something associated with my specific issues I've been having but I'll give it another shot once I've reflashed. Will update.
Thanks for all the input! I'm going to work a few bugs out.
Sent from my SCH-I400 using Tapatalk
Moon Shadow - NM said:
Just wondering if anyone else is experiencing this issue.
I just upgraded TiBu from 4.1.0.1 to 4.2.0. Oh, first I upgraded the key from 1.1.0 to 1.2.0 (per the directions listed in the market).
On the first run, it hangs at Checking License for about 45-50 seconds, then does a force close.
I have reported this to the developer and no response yet. (3 days out.)
Here is the sequence of events that I have taken to troubleshoot the problem (it's a problem with the key, or how the key is being read by TiBu).
1. Upgraded the TiBu key from 1.1.0 to 1.2.0
2. Upgraded TiBu from 4.1.0.1 to 4.2.0
3. Ran TiBu. Had the FC issue.
4. Uninstalled BOTH the key and TiBu.
5. Reinstalled the key.
6. Reinstalled TiBu.
7. Ran TiBu. Had the FC issue.
8. Removed the key.
9. Ran TiBu, No FC issue! But, now I paid $6.00+ USD for an app that doesn't work...
10. Installed the key.
11. Started a logcat recording session.
12. Started TiBu and let it run until it FC'd.
13. Stopped the logcat recording session.
14. E-mailed the logcat to the dev at [email protected].
15. Waiting...
I did locate a downlevel copy of TiBu (4.1.0.1) because I couldn't figure out where TiBu backed itself up when I ran the backups. (It may be due to the fact that I was trying to use the TiBu Free since TiBu Pro didn't work.)
TiBu 4.1.0.1 and the Pro key 1.1.0 work just fine. Just waiting for the Dev to get back with me.
Oh, one other note, TiBu 4.1.0.1 stopped running my scheduled backups. This was after I flashed to pastorbennett's Froyo 2.2 odin image. I don't know if the two are related, I will see if my backups run tonight... If they do, then all is good there. IDK.
I'm just hesitant to keep working on the development of my phone without a backup... Oh, crap... Don't say it... I just remembered about the Nandroid Backup through CWM Recovery... Stupid, stupid, stupid... Okay, enough of that...
01SEP2011 - 0657MDT: Okay, I received a reply from the dev, asking to send the logcat. It's been sent and we wait again.
03SEP2011 - 2004MDT: I FINALLY have a resolution, and it isn't pretty. Apparently my Continuum has a problem with memory management.
"The problem is on your ROM: there are memory management problems and many services (including Google's license manager service) are getting closed down all the time. Because of this, the license verification cannot even complete once. It's also probably the cause for the scheduling problem, by the way. We'll send a license file to you (that will work despite the memory problems) but we'd still recommend that you try a different ROM."
So, based on this, I need to go back and tweak my AMM settings some more. Probably back it off so it is not so aggressive...
Anyhow, they sent a license key file and told me to remove the market one and use the license key file. TiBu works again.
Click to expand...
Click to collapse
This could be an issue as well as someone else has told me titanium force closes.. i have had issues with the browser since purchasing the phone with force closing.
i am working on a flashable zip to fix/change a few things causeing issues.
Ok. Bug issues.
1. CFC on gps based apps. This isn't your rom. Its been an issue with all of the ec07 clean.
2. Maker. Its showing my version as 3.1.3 and has a black out icon. It refuses to load titanium backup. It fc's on it every time. Beyond that, there are random fc issues and "insufficient space" errors. I have done a reset, wipe and reset, with a reflash prior to reboot. The problem persists.
Sent from my SCH-I400 using Tapatalk
Click to expand...
Click to collapse
well apparently this message is too short according to XDA
So my current update.zip is removing maps.apk and street.apk which are both gps services as i'm sure you could guess. i am adding in a different music player.. just as a test and i added in torch.apk
Related
I have JACMan Hero r1.62, and when i install another firmware such as the JF 1.51,CyanogenMod and even SuperHero v1 i get force close for all my applications when i use apptosd.
I wipe before i update, im tired of Hero...force close like every minutes...so i want to move back to normal JF v1.51, but everytime i use apptosd the apps installs and i see the icons and everything but they force close when i tap it. But when i use apptosd on JACMAN hero i get no force close.
Help please :]
Run fix_permissions and if that doesn't work try reformatting your SDcard
sounds like permission issues
search for that.
alritewhadeva said:
Run fix_permissions and if that doesn't work try reformatting your SDcard
Click to expand...
Click to collapse
beat me to it!
ahaha
10 chars
Okay running it, lets see if it works.
I still get tons of force close after running fix_permissions.sh
it doesn't sound like a permissions error it sounds like a corrupt file system, either do a file system check using cyanogen's recovery or reformat your ext2/3 partition. if the file system check won't run it's cause you need to reformat
the force closes are coming from the apps...i think the cause may be the hero apps that are still on my SD, anyone know of a way to get rid of them easy?
Also I don't think is a corrupt file system, since all my apps works for the JACMAN builds and not for others.
and could you provide a link to cyanogen's recovery, thanks.
Bump, for helpp.
http://tinyurl.com/mqhx4d
Google does wonders...First post
Sorry couldn't resist
Okay i installed cyanogen's recovery and ran repair ext file system, and i got "error checking filesystem! Run e2fscl manually from console!" so i go to console and run e2fscl and now im stuck from there and have no idea what to do now.
If it failed running you have a corrupt file system, I don't care what you say you're wrong and need to reformat
Thanks.
is there a guide reformating my ext2 without destroying another gb on my sdcard?
Hi! i really don't understand why my gallery is slow, laggy and unusable so i try some ways to make it works...
at least (after flash rom again, some factory reset, deleting apps..and more try..) i found that "wipe cache partition" make gallery really *REALLY* fast! (do from recovery 3.0, wipe cache partition is not factory reset, you lose nothing, so if you wanna try.. ;-) )
but...
what happen with /cache ? after a while the gallery became slow again, and i don't understan if it's my fault or what
could someone help me?
now, half of day since clear, gallery it's ok, fast and smooth, but i'd like to understand how /cache is involved with gallery
bye ;-)
hmmm 170 viewers and no reply...I'm going to think I made a stupid topic... :-D
EDIT: if you think your gallery is not so fast, try wipe cache partition from recovery, and then try gallery again, i'm sure you will notice the BIG difference ;-)
However, i made some other try, all work fine with gallery until i place VOICE widget on homescreen, try voice command for a while, exit and try gallery, it's became slow AGAIN !!!.... so i removed VOICE widget, enter recovery, wipe cache, reboot , and gallery fly again...
i really don't understand where is the problem....
I guess u are using RFS file sistem... Things u say are logical.. When your cache is full, everything works slowly... There is another option to clear cache... Open Settings/Application/Gallery/Clear Data
I am using Galaxian kernel with EXT4 file system, and it is faster in every way...
hi medvedic! thanks for your answer!
i use ext4 with darkcore kernel, so thinghs are more strange eh ?
i try your suggerst to clear data from application settings menu' ! next time i found gallery slow i'll sure try this first
however, i think that, more modding we made on rom, more is risk to have some bugs somwhere...
CrashV5 said:
hi medvedic! thanks for your answer!
i use ext4 with darkcore kernel, so thinghs are more strange eh ?
i try your suggerst to clear data from application settings menu' ! next time i found gallery slow i'll sure try this first
however, i think that, more modding we made on rom, more is risk to have some bugs somwhere...
Click to expand...
Click to collapse
How ext4 works with ROM, that depends of kernel... Kernel is in charge for that..
P.S. You are welcome... We are here to help each other...
Well I just cleared the data in Gallery and it worked for me thanks much faster now
emmm,
let me tell you sth, if you use your PC or Root Explorer, you can see the there is a folder called .thumbnails. Inside the folder, there is a log of samll size images for previes which are useless if you have deleted the original photos, or move to other folder. These images will still stay in your phone which will make your gallery loading slower. Just try to delete this folder if you wish. Although it will recreated for preview sizes, but it clean the other and set your gallery free from jamming or lagging.
I own an Acer Iconia Tab A500. I am currently on...
Android version 3.0.1
Kernel version 2.6.36.3
Builder Number Acer_A5001.141.07_com_Gen1
I rooted the tablet and ran into a problem. I was in my Titanium Backup and erased a file by accident. Now, I have the com.google.process.gapps error occuring. I read multiple websites trying, what feels like, everything under the sun. Here are some things I tried...
Erasing gmail accounts
Downloading files
Factory Reset
The problem is that I did a factory reset and if I would have come here first I could have used my file explorer to reinstall the gtalk.apk. Now, I cannot install the file explorer, because of factory reset and feel that I am at a loss.
Here is the good news! I downloaded the Acer A500 driver and I am connected with ADB. I just need someone to help me with some commands for manually putting the APK file back on my tablet. I seem to be struggling with getting this done and any help would be greatly appreciated!
I have checked, to the best of my understanding, all the links the XDA, but to no avail.
Would somebody please be willing to help me?
Ryon
The command you're looking for is "ADB PUSH"
Type that in the command window (in the same folder as the ADB command), and it will give you the usage syntax, but it will be something like:
adb push gtalk.apk /system/apps/
That destination might not be the correct place for it, but it probably is.
You will need to be rooted, in SU mode, and have system mounted as RW to do this.
I don't see why you can't install a file explorer though... That FC shouldn't stop you installing one from the Market... Doing this copy would be a lot easier with something like eStrong...
Thanks for the help floatingfatman!
Maybe I am doing something wrong! I am a sponge and wanting to learn more and more about these OS. Everytime I go to download an app I get an automatic fc. In fact, it boots me right out of the market.
Just for information sake I am rooted and know how to get into su mode. Can you help in one of two ways? I am not real familiar with getting into RW or if you I could help me get file explorer, astro, and proper apps that would be great.
I am not good with using ADB. I tried doing what you said, but failed when it came to getting into RW.
Any further help would be greatly appreciated.
To mount the system as RW (rewritable, this is not a folder, it just makes the folder so you can write files to it), do this in a command window.
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p3 /system
Then, in a different command window, use ADB push to copy the file to /system/apps/. Finally, unmount system as RW.
Code:
mount -o remount,ro /dev/block/mmcblk0p3 /system
That should enable you to copy the file to your device, but I make no guarantees that it solves your problem.
Thanks again floatingfatman!
I did everything you told me to do, but to no avail! Would you suggest me trying anything else?! Everyone seems to be saying that I need to be get this apk file because something within gmail is missing.
Any more help would be greatly appreciated!
Ryon
Well, did you get any errors? I'm not saying that /system/apps is even the correct place for that file, or even if its the right file, btw.
These are the three errors I receive...
Upon start up I receive...The process com.google.process.gapps has stopped unexpectedly. Please try again.
If I try to download an app from the Market I receive...The applicatin My Apps (process com.android.vending) has stopped unepectedly. Please try again
If I tap on the the download app I get process android.process.media has stopped unexpectedly Please try again
Any help or moving in a direction would be great appreciated. Thanks for al lthe work so far!
Ryon
RyonAdcock said:
These are the three errors I receive...
Upon start up I receive...The process com.google.process.gapps has stopped unexpectedly. Please try again.
If I try to download an app from the Market I receive...The applicatin My Apps (process com.android.vending) has stopped unepectedly. Please try again
If I tap on the the download app I get process android.process.media has stopped unexpectedly Please try again
Any help or moving in a direction would be great appreciated. Thanks for al lthe work so far!
Ryon
Click to expand...
Click to collapse
At this point, it's probably best for you to reflash with a clean ROM. Vache has just posted a clean 4.010.22 that you can flash with CWM...
That sounds great, but how do I flash a rom when I can't download any programs such as Titanium Backup, etc. on to the tablet. Don't you need these to be able to flash?
If you could help me with the process I would be greatly thankful!
Ryon
RyonAdcock said:
That sounds great, but how do I flash a rom when I can't download any programs such as Titanium Backup, etc. on to the tablet. Don't you need these to be able to flash?
If you could help me with the process I would be greatly thankful!
Ryon
Click to expand...
Click to collapse
This 3.1 offical ROM will flash with stock recovery.
http://forum.xda-developers.com/showthread.php?t=1159443
Try going to the market website on your PC. Log into your Google account.find the app you need click install. And it will show a list of devices you can push the app to.this has worked for me. With a issue I had in the past with a app crashing the market.
Thou I do know in not so smart with android.
Acer so should have a complete wipe reinstall recovery.but ibguess if you do not root your device these things can't happen. Mess with the win directory in windows can mess you up as well.but I can fix windows.not android
Hey FloatingFatMan,
I just personally wanted to say thank you for sticking with me through this process. You truly were a God send for me! I downloaded the Rom and did what you said. I am now back in the game and can download apps from Android Market.
Thanks again!
Ryon
RyonAdcock said:
I own an Acer Iconia Tab A500. I am currently on...
Android version 3.0.1
Kernel version 2.6.36.3
Builder Number Acer_A5001.141.07_com_Gen1
I rooted the tablet and ran into a problem. I was in my Titanium Backup and erased a file by accident. Now, I have the com.google.process.gapps error occuring. I read multiple websites trying, what feels like, everything under the sun. Here are some things I tried...
Erasing gmail accounts
Downloading files
Factory Reset
The problem is that I did a factory reset and if I would have come here first I could have used my file explorer to reinstall the gtalk.apk. Now, I cannot install the file explorer, because of factory reset and feel that I am at a loss.
Here is the good news! I downloaded the Acer A500 driver and I am connected with ADB. I just need someone to help me with some commands for manually putting the APK file back on my tablet. I seem to be struggling with getting this done and any help would be greatly appreciated!
I have checked, to the best of my understanding, all the links the XDA, but to no avail.
Would somebody please be willing to help me?
Ryon
Click to expand...
Click to collapse
Happened to me once, I fixed it by going into recovery and going to advanced and did the fix signatures and rebooted and everything works, seem to happen mainly with titanium backup
Sent from my A500 using XDA Premium App
Thanks for the info! Everything is working well right now and I am once again a "happy camper".
Thank you again and hope this helps other people down the line!
Ryob
Moved as not dev.
Hey guys sorry im new to the android scene and never had any problems untill now, i looked around and cant find a solid solution. Im on honeycomb 3.2 with Tiamat Katana and im trying to wipe data/factory reset but everytime i enter recovery mode i get this
E: Can't open /dev/block/mmcblk1p3
E: Can't mount cache/recovery/command
E: Can't mount cache/recovery/log
E: Can't open cache/recovery/log
E: Can't mount cache/recovery/last_log
E: Can't open cache/recovery/last_log
Everything works i was just trying to update my android market because for some reason it is on a very low version and i have no clue what any of that means.
Please if anyone can help me in anyway that would be awesome thanks guys.
mecks69 said:
Hey guys sorry im new to the android scene and never had any problems untill now, i looked around and cant find a solid solution. Im on honeycomb 3.2 with Tiamat Katana and im trying to wipe data/factory reset but everytime i enter recovery mode i get this
E: Can't open /dev/block/mmcblk1p3
E: Can't mount cache/recovery/command
E: Can't mount cache/recovery/log
E: Can't open cache/recovery/log
E: Can't mount cache/recovery/last_log
E: Can't open cache/recovery/last_log
Everything works i was just trying to update my android market because for some reason it is on a very low version and i have no clue what any of that means.
Please if anyone can help me in anyway that would be awesome thanks guys.
Click to expand...
Click to collapse
What version of CWM recovery do you have installed?
i got this to work now, my only problem now is my android market i dont no why its such a out of date market, it only has the apps tab no movies no books or anything i tried to download one but it was the phone version im so lost.
mecks69 said:
i got this to work now, my only problem now is my android market i dont no why its such a out of date market, it only has the apps tab no movies no books or anything i tried to download one but it was the phone version im so lost.
Click to expand...
Click to collapse
What did you do to fix it?
Sent from my PC36100 using XDA App
I've gotten the same messages before when I open my recovery, but it doesn't seem to effect my ability to use it.
I have version 3.2.0.0 for the sdcard support. Is this an issue I should seriously address or can it be ignored?
Koulack said:
I've gotten the same messages before when I open my recovery, but it doesn't seem to effect my ability to use it.
I have version 3.2.0.0 for the sdcard support. Is this an issue I should seriously address or can it be ignored?[/QUOTE
This sounds strange to me...the Recovery app is looking for files it can't find where it expects them or otherwise, can't access them. Do you have an sdcard inserted? Can you backup to the external sdcard and then restore from it? Can you successfully flash a file from it? If so, you are probably ok.
Click to expand...
Click to collapse
okantomi said:
This sounds strange to me...the Recovery app is looking for files it can't find where it expects them or otherwise, can't access them. Do you have an sdcard inserted? Can you backup to the external sdcard and then restore from it? Can you successfully flash a file from it? If so, you are probably ok.
Click to expand...
Click to collapse
In fact, last night, not only did I create a new Nandroid backup, I also used my xoom to manually enter recovery, used ADB to enter recovery, installed 7 different zip packages from my sd card, and restored it to a Nandroid backup 3 times.
I'm just wondering what these files are, and if I should look into fixing it or not. It doesn't seem like a big issue, but when something gives you an error message, you usually don't just let it slide.
Koulack said:
In fact, last night, not only did I create a new Nandroid backup, I also used my xoom to manually enter recovery, used ADB to enter recovery, installed 7 different zip packages from my sd card, and restored it to a Nandroid backup 3 times.
I'm just wondering what these files are, and if I should look into fixing it or not. It doesn't seem like a big issue, but when something gives you an error message, you usually don't just let it slide.
Click to expand...
Click to collapse
I'm stumped...when you have enough posts, why not ask this question in the ClockWorkMod Recovery thread...I'm sure that someone with more knowledge will answer.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
installed last night. already liking it a lot! no problems so far.
I also am enjoying this. No issues to report. I am waiting for some loving for my xoom. Great job guys!
Amazing work as always, love it guys!
Finally decided to give twrp a go after reading so many praises about it. Very nice... Very fast!
Hmmm. Cant believe I'm the only one where Capacitive keys don't light up. Any Ideas? Love the hell out of this Recovery.
this recovery is full of win!
Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?
stevey5036 said:
Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?
Click to expand...
Click to collapse
Has nothing to do with the recovery, been running it since the first day and zero problems
False alarm.. The OTA was pushed to my phone (again) and would reboot the phone to try to install via stock recovery but it obviously wasn't there. Sorry.
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.
Sent from my rabbit hole using my carrotbolt.
Me likey. Thanks for this!!!!
droid future said:
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.
Sent from my rabbit hole using my carrotbolt.
Click to expand...
Click to collapse
Just shooting in the dark here, but have you tried a different kernel?
USB Mass Storage works for me with TWRP2 & LiquidSmooth 3.2.
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.
Sent from my ADR6400L using Tapatalk
PeteLopez197 said:
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I used ROM Manager to reflash CWM.
The way TWRP backs up the rom seems to be different than CWM (hooray compression!), so you can't restore a CWM Nandroid directly. At least, not that I've noticed.
So i may have bricked my phone...
Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?
twrp works great for me. its very fast. made a backup of lgb 3.2 in about 2 minutes!
I just flashed this. It worked for me. Did u make sure you renamed the zip and put it root of sdcard. This recovery has potential. I do like using the touch screen instead of my hardware, especially if volume keys are not responsive.
Sent from my ADR6400L using Tapatalk
GatoEnFuego said:
So i may have bricked my phone...
Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?
Click to expand...
Click to collapse
So the twrp IRC chat was extremely helpful in getting my phone working again. Great group of guys! Lesson learned, if you're going to flash a new recovery make sure you have a working ROM installed or else you can get caught in a bind if you pull the battery during the white HTC screen.
And if you do, make sure you lick your terminals...
I really like the concept of this recovery (touchscreen instead of hardware keys), but I feel it still needs some work to become "idiot proof", and needs to be more thorough.
For example, I decided to try restoring a backup of Skyraider Zeus, coming from Gingeritis1.1. After it completed and I rebooted into the system, there were all sorts of "leftovers" from the Gingeritis ROM packed in with Skyraider Zeus.
In other words, the recovery doesn't format the partitions prior to restoring the backup. This could lead to some serious issues for people when restoring backups of one ROM from another without manually formatting everything first.
Sent from my ADR6400L using XDA App