Hello, I'm porting Cyanogenmod to my phone, it boots of course many functions don't work, but I can't diagnose anything as logcat fails. http://pastebin.com/r39RsiUM Is what I get....I googled and haven't found anything to fix this. Logcat works just fine stock. Could anyone offer advice? If this is in the wrong place please move it! Need to get this cat out of the way to move on to fixing everything else!
Related
I have a problem with my device(HTCTattoo) that I cannot solve and I hope the you can help me.
I cannot successfully boot some custom roms(which no other users have problems) and it seems that the wiping is the problem. In fact seems that the wipe doesn't work right. I've tried to to flash the stock htc rom and wipe, make root proccess from the begining several times but the same errors still exist. Here are the recovery.log and adb logcat file(when the unbootable rom starts) to help you understand better.
Thanks in advance.
Any ideas??
Was about to start a new thread and saw yours, well Just last night I had helped someone with not quite the same but "Unbootable" Evo, this is the link to what I had did and I do hope it can give you some ideas on how or other ways to getting into your device before the unthinkable occurs
It may or may not be for you but just wanted to share how I had got into this device, Good luck!
http://www.youtube.com/watch?v=yh6PkKMwvKc
I want to try to port AOSP to my Samsung Infuse, but I need a little help. I heard that in order to port ROMs like this, you basically start by getting the source, building it, then putting it on your phone. Then try to boot into it and see what's broken and fix it(I realize fixing what's broken is going to be where majority of the work will be at.).
I downloaded the source to AOSP from Google and was able to build it, then I tried putting it on my phone but I'm unable to boot into it. How do you figure out why it won't boot? I tried running logcat on my computer when booting but it just says waiting for device and nothing else ever comes up.
Any help regarding helping me get it booting or any other general porting advice would be greatly appreciated!
Hi all. I'm having an issue and i know that the awesome people on here will be able to help me out. I have a Samsung Vibrant, rooted, 8GB class 6 sd card, running Cyanogen 7 (loving it) and for some reason lately, my phone will reset itself during phone calls. i'm not sure if it's Cyanogen 7 or not, but i haven't had this issue before running Bionix and Trigger and so forth. It may just be a huge coincidence, but it's annoying none-the-less. Thank you in advance for your help.
/proc/last_kmsg
Is there a file named /proc/last_kmsg that has a time stamp similar to when the phone rebooted? Sometimes you can look there to see if there are any useful kernel messages that can help you narrow down the problem.
mrpaulmanley said:
Is there a file named /proc/last_kmsg that has a time stamp similar to when the phone rebooted? Sometimes you can look there to see if there are any useful kernel messages that can help you narrow down the problem.
Click to expand...
Click to collapse
i don't have /proc/last_kmsg, but i do have /proc/ksmg and it does have a timestamp, but when i select it, nothing happens.
jon_yarbrough said:
i don't have /proc/last_kmsg, but i do have /proc/ksmg and it does have a timestamp, but when i select it, nothing happens.
Click to expand...
Click to collapse
/proc/kmsg is the current file that is being written to. It probably doesn't have any useful information since it gets recreated at boot and the details of your crash would be gone.
Have you tried running fix permissions or anything like that? Could be a good general troubleshooting step. Also, maybe look at your radio version and see if there are other versions our there you could flash.
Other than that, I would turn to the XDA forum for your device, or even the cyanogenmod forums.
mrpaulmanley said:
/proc/kmsg is the current file that is being written to. It probably doesn't have any useful information since it gets recreated at boot and the details of your crash would be gone.
Have you tried running fix permissions or anything like that? Could be a good general troubleshooting step. Also, maybe look at your radio version and see if there are other versions our there you could flash.
Other than that, I would turn to the XDA forum for your device, or even the cyanogenmod forums.
Click to expand...
Click to collapse
I had this happen on another device type and it turned out the Radio needed to be re-flashed. Started working fine after that.
thanks to both of you. i will give that a shot.
Greetings and salutation;
I've been fiddling around with my new tablet, learning about flashing ROMS and such, now I`m trying to get back to the original stock. I think I deleted it, or the recovery image from the device because I keep getting a Cyanogen Mod load screen.
Anyway...
I've search the forums and seems like most of the information either dated with broken links, unclear, or assumes most viewers understand the vernacular/terminology.
Basically, I need to find the stock ROM for the Acer Iconia Tab A700, in English. I'm fairly confident with flashing it as I have that figured out. I just need to get my hands on a copy of something that will install.
I have an image right now, but I keep getting the following error bounced back to me;
"assert failed: getprop("ro.product.name")=="a700_pa_cus1"
"Error in /cache/acer_ug/update.zip"
If I can figure that out, then maybe I'm good to go.
Anyone feel like helping me out?
Thanks.
I've been having the same issue, I was following a guide on how to root this device when something went wrong (a file was out of date or something). Anywho, the devices now just loops at the Iconia animation on boot & I'm trying to find the best way to revert back to the stock rom, or something at all at this point. I'm currently getting the same error as you, I'm hoping someone more knowledgeable can help out or something. I'll continue my search tomorrow when I get back from work.
I see that this post was from about a week or so ago, have you found a solution yourself or are you still waiting?
Anything at all would be greatly appreciated!
Thanks a ton!
Hey there, not sure if you're still looking but I found how to restore stock!
Check out the following link, if you follow the steps exactly you're tab will have the stock rom.
http://forum.xda-developers.com/showthread.php?t=1812635
Just a note, the first time you restart is after flashing it might freeze on the iconia boot logo after it's animation. Just restart it with either the power button trick or the pin hole at the bottom...or side, depending on how you're holding it I guess.
Hope this helped!
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
SedentaryDev said:
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
Click to expand...
Click to collapse
did you installed cm from here http://getcm.thebronasium.com/?device=u8833?
303
I didn't install it at all. This is just how I got the phone. I can tell you that it's CyanogenMod version 11-20141114-NIGHTLY-u8833
That could be the problem. You never know what the previous owner did or what they flashed could be a bad download, the wrong firmware, etc. Best to get back to stock and start over so you know exactly what has been done.
Hmm... probably. Right now going back to the stock ROM would be an improvement. Could I get some help with that, then? I haven't been able to find clear steps to do that with my specific phone, and when I went to Huawei's web site, I couldn't find the ROM for the Y300-151 and wasn't confident the Y300-100 was suitable.
I've used CM11, but I'm not familiar with that phone, so unfortunately I can't help with that specifically. There should be plenty of help on XDA. Just search for that specific model. Sometimes it takes a while to find what you need, but I'm sure its there. If it's done right CM11 has never let me down.
I'm sure CM11 works fine for most people, but my instincts tell me that my phone is underpowered for it. Ok, I'll look elsewhere or start a new thread about getting back to the factory ROM.
Yes, first thing to do is get back to stock. But don't give up on CM11. It should work fine on underpowered phones. It's just a slightly modified version of vanilla android which is a fairly light ROM.
I hope you figure it out.
Good luck!
If what you say is true, then I expect I'll be right back here again. I doubt that the wrong binary was used--I dunno, maybe something was wrong w/the installation procedure, but I'm sure the right binary was downloaded. In which case, maybe I should be attacking these problems directly, since I'm having trouble getting support for installing the factory ROM.