Related
My autorotate isn't working on CM 4.2.6, it is checked off in settings. I read the FAQ about removing some files to get it to work, but I have a mytouch 3g, so no physical keyboard and therefore no keyboard at all under su. Is there any way to do this without adb? If I need to use adb to do this, can someone point me in the direction of a quickstart guide?
no one has these issues with cyanogen unless you messed something up like didnt wipe everything when you flashed the rom guarentee you wipe of everything and reflash the drc83 image and then the cyan rom reboot you will have your rotate back....
I don't think that is true. It doesn't have anything to do with Cyanogen, but in the Cyanogen FAQ, it is answered.
20. My auto-rotate/accelerometer isn't working!
Not really the fault of the ROM, but here's how to fix it: Open terminal, su, then "rm /data/misc/akmd* /data/misc/rild*" and reboot.
Click to expand...
Click to collapse
Therefore, other people have problems with it. The phone was unrooted, wiped, and root was attempted 3 times before I was able to get into recovery mode. I used RA 1.2.3 as the recovery image, then flashed HTC ADP 1.6 (DRC83), followed by Cyanogen 4.2.6.
In conclusion, I just need a way to type in the terminal on a MT3G under superuser.
autorotate problem
i try this, but still not working..
awebagar said:
i try this, but still not working..
Click to expand...
Click to collapse
maybe hadrware problem , same like mine.
Hey guys,
I finally decided to root my eris today. I used the revoked method on my mac and everything worked flawlessly. I then downloaded a ROM FroShedYoV7 and followed the installation steps. About half way through I received the error symlink /system/xbin/busybox SYSTEM:xbin/arp. I then tried a few different ROMs and received the same errors. I did a backup beforehand; however, I can not even restore to that. I was going to use the RUU method on my school's PC (I have a mac) but when I tried it, it was unable to recognize that the phone was connected - probably because it stuck at the fastboot screen. I still have access to the recovery though.
I did a little research on the matter and found that chrome sometimes messes up zips so I tried it with firefox and had no success.
Any help would be appreciated, I just want my phone back rooted or not.
what recovery are you using?
first, i'd pull the battery, re-insert and then try booting into recovery (volume up + power)... then, full wipe and try to flash again. are you verifying the md5 of the download to ensure it's not bad?
if you happen to be using clockwork, i think there is a thread that discusses cleaning some things up... i'll see if i can find it.
I'm not sure what you mean by verifying the md5, but I have tried multiple ROMs downloaded by multiple browsers. And also I did full wipes before each attempt.
I also just attempted this fix the RUU ROM rename to PB00IMG.zip fix, but had no luck.
Thanks for your help!
Also, I am using clockwork.
Use RA... CW has issues
Sent from my ERIS using XDA App
Try this thread and good luck.
EDIT: The below issue has been fixed. Here's the guide: http://forum.xda-developers.com/showthread.php?t=1110599
---
Howdy folks!
I've just bought a Nook Color, and I followed these instructions to the letter:
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide
(I've done it before and it worked perfectly)
However, this time after installing CM7 and the GApps zips, I reboot and I cannot see the Market app. It doesn't exist. (see attached image).
I thought maybe it was just a problem where I simply have to add a google account...
I go to menu->settings->accounts and sync->add account
Rather than the normal "choose an account type" dialog, It says "you can configure an exchange account" and I am not given the option to choose a Google account.
I reimaged a different SD card and rebooted into recovery using that card and wiped data, wiped cache, installed CM7, installed gapps, and rebooted.
Once again, the same exact issue.
I reboot to recovery again and this time I just install gapps and reboot... same issue...
Any help would be extremely appreciated, and if you can solve this problem for me, I'll even 'donate' 5 bucks if you have that set up.
Any help or advice would be greatly appreciated here.
Thanks!
Could it matter what version of CM7 you're using?
Thank you for the response.
I've tried CM7.0.3 and the latest nightly [today]
Google Apps pretty clearly did not install. My best guess is either you somehow grabbed the wrong package or your download just got corrupted. You should scrap the gapps...zip you downloaded and re-download this package:
I just tried it to double-check, and the main download link was flagged malicious by Avast and didn't load, so I used the mirror. Try that.
With CM7 installed, make sure Wi-Fi is set up (sometimes prevents complications), then reboot into ClockworkMod Recovery. Insert the SD card with the new gapps-gb-20110307-signed.zip file in the root directory. Choose "install zip from sd card," then "choose zip from sd card," then "gapps-gb-20110307-signed.zip," then "Yes."
You should see some text in the bottom half of the display indicating that the install is proceeding, and eventually that it has finished. Click the power button to back out to the main menu, then "reboot system now."
If that doesn't do it, I've about exhausted my knowledge.
Hello, and thank you for the reply.
I've tried it on two different sytems on 3 different nooks with 3 different SD cards and various different versions of gapps and CM7 including the nightlies.
This problem started when the nooks with the "green stickers" came out.
(Green sticker indicates that it has the new version of Nook software, while a blue sticker indicates that it has the weird new partitioning scheme. These do not have the blue sticker.)
I've tried enabling wifi and whatnot, and then reinstalling the gapps package but no bueno. The apks don't even seem to exist in the system\app directory.
This is a global problem with any new Nooks. I think i just happen to be one of the first ones to experience it.
Sent from my Transformer TF101 using XDA Premium App
This has been an ongoing problem for me since I came back to CM7 from HC last week. I don't think it has anything to do with the old or new because I got my NC on launch day.
I had figured that it was just something I had done (I get distracted easily so following directions is....oooooh! A bunny! ) but I've reflashed CM7 and GApps 3 seperate times.
It's only really an annoyance for me since I had most of my apps backed up and I've managed to get the Amazon store and AppPlanet up and running. I'd just like to get the Google market running just so I can have the Trifecta.
I really hope we can figure this out. I know this can't be just me.
What actually happens when you try to install the gapps zip? Does CWM indicate that it is in fact installing the package, and then that it's done?
Taosaur said:
What actually happens when you try to install the gapps zip? Does CWM indicate that it is in fact installing the package, and then that it's done?
Click to expand...
Click to collapse
indeed it does
some added info:
on the "green sticker" nooks, when you try to flash the update OR the gapps, it says it can't mount system or data to make logs, but still seems to work fine. If I manually mount system or data first, it doesn't throw the errors. After flashing CM7, I get fewer errors. CM7 flashes just fine, and the gapps install and CM7 both say install completed, it's just the gapps that don't show up :S
I've heard some people were having trouble flashing the latest stable 7.0.3 and getting gapps to install. This worked for me. I flashed cm7.0.2 from cyanogens site and the google apps add on on the same page. I then flashed 7.0.3 without the google apps add on included with 7.0.3 and it worked. Hope that helps some people
I'm not really sure what you're saying. The gapps aren't installing is the problem.
S/He's saying try installing the previous stable build and see if gapps will install with that. If so, you can then upgrade to 7.0.3 and gapps should remain in place. Technically that's what I did, just because the new stable came out after I had 7.0.2 up and running on SD, but I didn't have any problems flashing gapps with the 7.1 beta to eMMC later on.
ah, I see - I tried that. in fact, I know that on previous versions of the Nook, the gapps installed just fine. I think it's something to do with the 'green sticker nooks'.
I hope this gets or has gotten solved as I just bought a "green dot" NC.
The issue persists, I'm afraid. While it seems I'm not the only one with the problem, there appears to be no solution.
Update: The issue persists on the "blue dot" nooks.
Several 'green-dot' owners have reported installing everything just fine, so that may not be the source of your woes. Have you tried the repartitioning thread for blue-dots, even though you don't have a blue-dot? It seems like your best bet is to one way or another get your NC into a state identical to machines that aren't having this issue.
Taosaur said:
Several 'green-dot' owners have reported installing everything just fine, so that may not be the source of your woes. Have you tried the repartitioning thread for blue-dots, even though you don't have a blue-dot? It seems like your best bet is to one way or another get your NC into a state identical to machines that aren't having this issue.
Click to expand...
Click to collapse
yes sir, I've repartitioned as well.
Could it be the fact that I'm using CWM 0.7?
thisnameissoclever said:
yes sir, I've repartitioned as well.
Could it be the fact that I'm using CWM 0.7?
Click to expand...
Click to collapse
0_o where did you even get something like that? The current version is 3.0.2.8
You need one of the images from here: http://forum.xda-developers.com/showpost.php?p=13283643&postcount=34
I used the one on the CM7 wiki but I can see that wiki has been updated this week. I will try the one you linked and get back on this thread if it works. Thanks a ton. Hope this hasn't all been due to my retardedness. B-)
So basically, I tried to help out my friends continuum and ended up with some problems.. these are the exact steps I took..
-Flashed adrynalynes test4 cwm file via odin..
-Put yellow_update.zip on the sdcard, and updated it through that, which seemed -to work
-Flashed within CWM, IMNUTS 530 PBJ voodoo kernel, and rebooted
-Converted successfully as stated by the robot voice, but after it was done I had both the scrambled screen issue, as well as I was unable to download things from the market.
-I attempted to convert back to rfs by disabling lag-fix.. but I still had the problems
**After rooting which seemed successful, I also did not have Superuser.apk installed, and since i could not get a file explorer from the market I am basically screwed.
I have done quite a bit of reading and people seemed to have solved these problems so it must have been something that I was doing wrong originally. One thing I found is that I should try using the blue update instead of the yellow one..
Also has anybody flashed the newest IMNUTS voodoo kernel without facing market issues.. or how about the nonvoodoo one??
What I want to do now is get back to stock unrooted, simply so I can be sure that Im starting clean when I attempt to root again.. (or should I just try to flash stock rooted)..
If anybody has faced issues like this or know how i can fix them, please let me know.. THANKS
These problems are known, and you can fix them by flashing adrynalynes kernel and odining to dl17 stock xP
Sent from my SCH-I400 using XDA Premium App
kamikazemike6 said:
So basically, I tried to help out my friends continuum and ended up with some problems.. these are the exact steps I took..
-Flashed adrynalynes test4 cwm file via odin..
-Put yellow_update.zip on the sdcard, and updated it through that, which seemed -to work
-Flashed within CWM, IMNUTS 530 PBJ voodoo kernel, and rebooted
-Converted successfully as stated by the robot voice, but after it was done I had both the scrambled screen issue, as well as I was unable to download things from the market.
-I attempted to convert back to rfs by disabling lag-fix.. but I still had the problems
**After rooting which seemed successful, I also did not have Superuser.apk installed, and since i could not get a file explorer from the market I am basically screwed.
I have done quite a bit of reading and people seemed to have solved these problems so it must have been something that I was doing wrong originally. One thing I found is that I should try using the blue update instead of the yellow one..
Also has anybody flashed the newest IMNUTS voodoo kernel without facing market issues.. or how about the nonvoodoo one??
What I want to do now is get back to stock unrooted, simply so I can be sure that Im starting clean when I attempt to root again.. (or should I just try to flash stock rooted)..
If anybody has faced issues like this or know how i can fix them, please let me know.. THANKS
Click to expand...
Click to collapse
just download dl17 stock odin image and you'll be back to full stock with superuser and market should work.
and upgrade to FROYO, just saying.....
and i am not sure why alot of people had market problems because i used both voodoo and non-voodoo and had no problems at all, maybe i'm just lucky...
Well, I loved this kernel! But I appear to have bricked when flashing another (also aparrently kernel fixed) rom.
I *could* get to CWM, but I can't touch system. The phone freezes if I try to do anything.
Odin will not flash.
I'm an experienced user, I've owned several Android phones in the past and understand how everything works, however, this time, it really appears I am dead.
I can take the phone back so no big deal, but I just wanted to let people know. If I am unable to get this working, it appears the new kernels still have some risk involved.
I was on UK Stock ICS (Not sure what the version was now), flashed Francos using DD, everything was fine but Wifi did not work, so I wanted to try Speedmod. This caused a bootloop. So I reverted, and the bootloop remained. At this point I downloaded a Lite rom that used Franco V4, (sorry, the name has escaped me) this flashed but also gave a bootloop. So I wiped, and re-applied.
When I reinstalled after wiping, the install bar glitched and flew past it's usual 100% right off the side of the screen. Then it froze.
After this I am unable to flash *anything* to the phone. CWM boots but I can't do anything within it. Odin attempts to flash but I see the phone send invalid responses back (non-alphabetical characters) and Odin then fails.
Anything else I could do? I think I've tried everything possible at this point. Gutted!
[edit]
UPDATE: This does currently appear to be a case of bad luck, and NOT The eMMC Bug. The eMMC Bug fix is now under critical testing by myself (as I have access to replacement phones within minutes), though I have flashed 18 times at present with no superbricks or broken eMMCs. So far so good!
I think u wiped from ICS kernel and this may have caused u a brick. At first when you flashed speedmod and had bootloop you could have flashed back to Abyss kernel wiped and reinstalled the whole rom instead of wiping from ICS kernel and installing rom. Its a known fact that while installing or restoring roms from ICS kernels people have faced lot of issues..
I'm aware of that issue. I used Franco's R5 kernel (which is ICS and superbug fixed. The fix was not a guaranteed fix, and sadly I appear to have proven this fix to be non-working at the moment.)
I guess I'll be popping back to the shop at lunchtime!
Cheers.
One last try just pull the battery for 30 seconds and try to get into download mode and try to flash stock GB with 16gb pit file and gb bootloaders
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
When i had Galaxy s same thing happened to me only download mode no cwm nothing and Odin was failing to flash stock roms even with a pit file and what i did was flash with bootloaders along with pit file and rom files and voila my phone was back to bussiness
You might be right about the PIT files. It would make sense, Odin almost completes when the phone throws out the invalid text- might be trying to put data out of the partition.
I'll give it a go, thanks. I do still have Download mode. I no longer can access recovery though.
so you cant flash on ODIN?? stuck on factoryimg??
Well, that didn't go to plan. Crashed again, and now I have no download mode, instead the phone appears to be insisting that the battery is not installed. How odd!
musashiro said:
so you cant flash on ODIN?? stuck on factoryimg??
Click to expand...
Click to collapse
This was the case, yes.
Oh, I just got Download mode back, Stupid thing. What odd behavior.
I can get the phone replaced within minutes if required (I'm 5 mins away from the shop) but I'd rather try to keep my internal storage intact
Here's the guide to fix it. I along with many others managed to fix our phones using this guide: http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
Thanks for that. I'd just found it before you posted and am reading through it now.
I am half tempted to try it, but I think if there are now "bad blocks" in internal memory, I will just get it swapped for a fresh device.
It's behaving weird, sporadically thinking the battery was removed etc. so I am not 100% sure this is a superbrick /mmc problem, and it could be some other issue that cropped up. Let's hope so (because I'd really like to think Superbrick is fixed as we had suspected!)
Thanks for your input. I'm off down the shops!
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
damiensturdy said:
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
Click to expand...
Click to collapse
Yes seems like a good plan to me, looking forward to get results from you soon.
Thanks
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Glad to have someone willing to risk their devices in these dark times. Well appreciated!
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
In order to run the test, you need to actually boot up the device, go through the settings, and install a few apps. Then go to recovery, and perform a wipe.
Simply hitting the Wipe key in succession (like 100 times) does not work. There must be something to format in the respective partitions.
Thank you for doing what you're doing. But if you could, and only if you have the time, could you try wiping from CWM (just wiping, not nandroid restore), for say 20 ~ 30 times? It's very tedious to do it due to the setting up and needing to wait for it to boot and install a few apps from the market.
I'm sure with 20 ~ 30 or more wipes on a single device, we can safely say that the fix is a likely permanent fix.
damiensturdy said:
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Click to expand...
Click to collapse
So, in short, you had /system corrupted at the filesystem level, not the eMMC level. This seems to be a common problem on the Note, and some people falsely describe it as "partial root". CM9's initramfs has had changes made to make it easier to fix these problems by not automatically mounting /system on entry into recovery.
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Good input guys. Thanks.
Yes, indeed this didn't appear to be the eMMC Bug. I can't guarantee what it was on the old phone (which did appear bricked.), I just know I started off the same. It's more likely that I knackered it with failed Odin flashes than the eMMC bug at this time.
I'm still flashing, installing, wiping, etc. I'm basically trying everything that we're not supposed to do. So far the worst I've got is a corrupt system partition (indeed, that is not an eMMC bug) but the only CWM able to fix that was Thors.
Basically if I knacker the phone I can get it replaced within minutes, so I might as well take advantage so that we can all relax knowing it's fixed (or continue to look for a fix if it isn't)
Obviously I shouldn't take the piss. If somehow I brick it a couple more times I'll be forced to stop. But I like to help so let's go! :-D
What does "flashed Franco from DD" mean? After that process did you ever verify that you where actually on Franco?
Perhaps the kernel flash didn't take and your subsequent wipes/flashes where from stock ICS kernel.
Sent from my GT-N7000 using xda premium
Entropy512 said:
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Click to expand...
Click to collapse
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
damiensturdy said:
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
Click to expand...
Click to collapse
That's because he kangs from CM and then releases warez based on our work.
Linux kernel without source code published = warez.