Related
This thread is an attempt to help out the Tiamat Developers by answering the frequently asked questions in one consolidated thread. This thread should also be helpful to those who either cannot use the search feature or are having a hard time figuring out the correct search terms to find what they are looking for. If you have suggestions or added questions/answers feel free to reply and I will update the OP.
NOTE: I am not a developer. All of the information in this thread is from other members who have helped me out or information I found in the XDA forums. I do not take credit for any of the great work that has been done on this ROM and I will point back to the original answer when possible. I am only trying to help lessen the burden on the developers so they can spend more time getting us the best features. Hopefully you find this helpful as well.
I've flashed this ROM and now I get update notifications. Should I accept the update? How do I stop these notifications?
No, you should never accept an OTA upgrade when using any custom ROM/Kernel. This could result in severe problems. Your best bet is to be patient and give the developers time to react. If the update is worthwhile I am sure they will roll it out pretty quickly.
To get rid of the notifications flash Mod pack 3 as noted here.
OK I made the mistake of accepting the OTA update and now my Xoom won't boot. What can I do?
okantomi said:
Can you make it reboot by pressing volume up and power at the same time and holding? If it reboots, wait about 3 seconds once you see the dual core logo and then tap volume down you shoud see android recovery, then tap up to choose it. I hope you did a nandroid backup. If not, you can try and get fastboot by tapping volume down sooner after it reboots.
Click to expand...
Click to collapse
From this thread.
With this ROM certain websites don't load correctly or I can't get to the mobile version of a site.
This ROM by default sets the User Agent String to "desktop". If you want to revert to the stock settings flash either Mod pack 1 or 2 depending which version of Moray you are running. Look here.
I flashed this ROM and now when I click links in email or my file explorer the screen just dims and nothing happens.
This is a bug in Android 3.2 and not specific to this ROM. To solve this, simply ensure auto-rotate is enabled and rotate the device from landscape to portrait and back to landscape. The app chooser window should appear allowing you to choose which app to open the selected file.
I just flashed this ROM and the speed is amazing, so I OC'd it to 1.7GHz cuz I want more and I am now stuck in a boot loop. This worked for others why not me?
The Xoom was only specified to run at 1.0 GHz, anything beyond that is a gift. Due to part-to-part variation not everyone's Xoom will be stable at the same speed. Yes some people are able to run at 1.7 GHz, but many cannot. For your specific Xoom try out the various speeds, but do NOT click "Set on Boot". This way if it crashes it will revert back to stock speed and you will be able to boot. Once you are satisfied with a speed then feel free to enable "Set on Boot". Before you do so I would suggest making a nandroid backup so you can restore just in case.
How do you get out of this boot-loop? The only way I know of is to boot into recovery and restore a nandroid backup if you have one or perform a full wipe if you do not.
I updated to the latest CWM and I cannot find the zip card or I get "get error: E:failed to mount /sdcard (No such file or directory)."
Latest is not always the best, for the Xoom you need to either use ClockworkMod 3.2.0.0 (R4C) or CMW Rogue Recovery v1.1.1
After flashing this ROM the Motorola icon gets distorted during boot up, is that a problem?
Basically it is not a problem. This kernel has a patch provided by NVidia which causes the distortion during boot. It does not cause any problems after it boots.
Is there a way to get the stock WiFi and Battery icons?
Yes
How do I boot into recovery without ADB or my PC attached?
There are a couple methods.
1) The latest Tiamat ROM includes this if you press and hold the power button. Just pick what you want and hit OK.
2) Download and install "Quick Boot" from the market. It gives you the above options as well as others when you run the app.
3) Turn the Xoom on, wait ~2 seconds after your see the Dual Core logo, then press the volume down key. In the upper left corner it should say "Android Recovery", then press the volume up key to select it.
How do I get started? Any good guides?
There are several guides that are pretty good. The best one I have found and personally used is here.
The Xoom Heaven thread found here is also a good place to start for all sorts of information.
If you have another question please feel free to post to this thread. If you are having a problem or have a question it is likely that someone else along the lines will have the same problem or question. I will continue to update this OP with the list of F.A.Q.s.
Additional Q&As
After installing this ROM I am having issues with the market not finding all of my apps or apps are giving errors when trying to install them.
See this post for one possible solution.
One more for good measure...
HuckFinn, I think you have covered most of the hot issues. Great job!
Stickied. Thanks for posting this, and Solarnz for giving me the heads up to do so.
Sorry for the newb question, but what's "root"?
Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
oh kitty, you funny!
Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
It's what you pull your hair out by when something is not working properly!!
darn you... I earned 1/2 my posts responding to the "why does my screen dim" question... now I'll have nothing to say!
i performed a factory reset from the os-> settings and once again performed a wipe/factory reset from the cwm recovery but still can't get back to the initial setup screen (where you enter your google a/c, etc)
any idea?
Thanks!!
Here is one..
Why does Market show up in USD even though my locale is set to UK, my language is English British along with my keyboard layout?
Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?
madamimadam said:
Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?
Click to expand...
Click to collapse
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.
okantomi said:
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.
Click to expand...
Click to collapse
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you
madamimadam said:
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you
Click to expand...
Click to collapse
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads
LPHS said:
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads
Click to expand...
Click to collapse
OR here:http://forum.xda-developers.com/showthread.php?t=1209341
Links to both of these recoveries are also in the first post of this thread.
HuckFinn said:
Links to both of these recoveries are also in the first post of this thread.
Click to expand...
Click to collapse
Guess I should have read the thread before posting here, sorry for being a troll.
I tried this ROM on my 4G Xoom, but it left me without 4G or 3G (wifi only). Any way to get this working, or do I have to wait for an update?
I did try activating the network in settings, but it never connected even half an hour.
Thanks to steps mentioned by user 'LordDeath' in another thread and a bit of experimenting with a rooted 4G Xoom and a friends 3G Xoom running Moray, there seems to be a remedy for those who are having issues with the market compatibility issues as well as missing apps. I did not activate until attempting to sign in to the market and had missing apps and compatibility issues. I simply did a full wipe & reset and made sure the full activation went through in set up then let it automatically start restoring. I took a peek in the market after a a minute and all my apps were back with no compatibility issues. Here is a copy of his original post and mine but the last step was not needed for me.
Originally Posted by LordDeath
Something more about the market:
After I restored my backup of the official 3.1 ROM I still had some issues. On http://market.android.com I still saw that my Xoom is not compatible with some apps. The market app on the device did show these apps but upon installing I got the error message: "Fehler beim Verarbeiten des Kaufs". Translated into English it means "Error while processing the purchase". It was a free app, btw.
To solve this issue I did the following:
1. Wipe data/factory reset
2. Active the device during the wizard on the first boot with my Google account
3. Restore the nandroid backup of the official 3.1 ROM
Therefore it seems that the market servers check your device-compatibility only during the activation process at the first startup.
----------------------------------------------------------------------------
"This fixed everything for my friend running Moray and even corrected the issues on my 4G Xoom..."
I should add that though this fixes the issue, if you change your pixel density you may run into similar issues but can correct it by setting it back to 160 before going into the market.
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10
Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1
CZory91 said:
Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1
Click to expand...
Click to collapse
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.
Sythrix said:
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.
Click to expand...
Click to collapse
Well. Good and bad news. Good news is it's fixed. Bad news is there is no way that I can find of updating the firmware/modem while running an AOSP ROM. The first try worked great, wanted to see if I could update the firmware, no go. Restarted from the beginning again to see if taking the OTA updates while not rooted would allow me to have it work when rooted. Updates went through, everything went fine. Camera didn't work on AOSP still. So at least it works... I can deal without the firmware I guess, definitely worth a working camera and fully stable CM10.1.
Had some issues with the root, however a few tries at it and it eventually worked. This requires no input on your screen (first try SU popped up on me and I granted access, it rebooted and didn't root correctly) Edit: This time around I granted it and it worked. Heck if I know what/why. Just just keep doing it until it works, worked for me. Don't press anything the first try, then do so the second, etc.. Start it as soon as your device is connected to your computer and let it do it's thing. Don't let it have the chance to switch from its "installer" mode on the phone to a media device (unsure if that was the problem, but that seemed to be the reason why after the second round, 4th attempt).
Also, I had to battery pull and wipe data on the stock recovery listed as optional on the first link after it was rooted (WAIT UNTIL ODIN SAYS PASS before pulling the battery out when it's at the boot logo).
The only other thing I would say is that my phone initially came with the VRBLK3, and that may be the reason why this worked for me. Don't know. If your phone shipped with a different version, and my process doesn't work for you, try finding an MD5 with your shipped firmware version that will odin you to that version, and then continue with the root.
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.
Sythrix said:
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.
Click to expand...
Click to collapse
It's in the first post on both CM10.1 threads (Q&A and Developer forums).
Sythrix said:
Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10
Click to expand...
Click to collapse
Props on providing all that data with your question.. wish everyone was as thorough as that when needing help..
Sent from my Nexus 7 using Tapatalk 4 Beta
Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Did not and still does not work for me.
Sent from my SCH-I535 using Tapatalk 4 Beta
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave
READ IN ENTIRETY BEFOR INSTALLING
I have procured a new Nexus Q. Work has resumed on Android 7.0, from a hardware and specs standpoint, there is no reason to think that this device is not capable of running Nougat if the Galaxy Nexus can. Stay tuned for a build in the coming weeks, I will also be uploading this project to github shortly
AOSP 7.0 Nougat for Nexus Q
Code:
Quote:
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Working:
TBD
Not Working:
TBD
Recovery
https://drive.google.com/file/d/0B7WYr1U8sRRAM1d3czhER0RoTGM/view?usp=sharing
./fastboot flash recovery
MAKE A BACKUP BEFORE INSTALLING AND SEND ME A LOGCAT WHEN YOU ENCOUNTER ISSUES SO I CAN TRY TO RESOLVE THEM
DL Link (Google Drive):
***LINK REMOVED*** -
Anyone interested in an early build send me a PM
Nice! Thanks very much for this! I'll try it when I'm back home in a few days. I was planning to try and work on this myself but perhaps I can transfer some efforts over to Android TV. Do you have the source for this on GitHub as that could also be really helpful - that way a few of us can contribute to help fix things etc.
New build coming soon with proper sources and fixes posted to GitHub. Also, if anyone would be interested, I believe that it may be possible to use an OTG webcam for Skype/etc.
Great stuff, thanks for doing this. Should be able to get android TV then since it's just a separate launcher.
Hmm, not having any luck flashing this. I get an "Installation aborted" error. What recovery are you using?
New build. Testing needed.
jyeley5 said:
New build. Testing needed.
Click to expand...
Click to collapse
What are the changes?
jyeley5 said:
New build. Testing needed.
Click to expand...
Click to collapse
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
wollac11 said:
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
Click to expand...
Click to collapse
Updated the CM base and merged some changes that I've been porting over. Did you install over another build or wipe fresh?
jyeley5 said:
Updated the CM base and merged some changes that I've been porting over. Did you install over another build or wipe fresh?
Click to expand...
Click to collapse
It was a fresh install, cleaned system, data and cache.
wollac11 said:
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
Click to expand...
Click to collapse
Try installing over a working CM11 build. Can you get me a logcat if that still doesn't resolve the issue?
jyeley5 said:
Try installing over a working CM11 build. Can you get me a logcat if that still doesn't resolve the issue?
Click to expand...
Click to collapse
I just tried flashing over Cm11 and nothing so far. Seems also to not boot. The speed at which it flashes in recovery says to me something isn't right with the updater script. There is no way it is copying the 255MB contents onto the Nexus Q in that time. Cm11 (which is smaller) takes far longer.
I tried to get a logcat but as before I am not able to get one of the boot attempt as the device appears as offline (because I can't authorise the PC RSA keys with adb as that would need Android to finish booting at least once). I can get you a recovery log or a logcat while flashing the Zip from recovery if you like but that's about it.
Have you actually had this booting on a Nexus Q then at all yet? And if so, how exactly did you install it, with which recovery and if over another ROM which one was it?
Possibly stupid question...
I'm new to this forum, at least posting here. So, since the Nexus Q app is no longer supported, how does one enable USB debugging on the Q? Any redirects and help would be greatly appreciated! I just got a brand new Q today for $10 at a local Goodwill (accompanied by fellow Q's). I was very sad to see these are no longer factory-functional.
If this is the wrong place to post, I apologize in advance, and would gladly accept on where-to-post details.
Thanks!
Natodroid1 said:
I'm new to this forum, at least posting here. So, since the Nexus Q app is no longer supported, how does one enable USB debugging on the Q? Any redirects and help would be greatly appreciated! I just got a brand new Q today for $10 at a local Goodwill (accompanied by fellow Q's). I was very sad to see these are no longer factory-functional.
If this is the wrong place to post, I apologize in advance, and would gladly accept on where-to-post details.
Thanks!
Click to expand...
Click to collapse
You've replied to a post about a specific custom ROM in the development section (which is completely the wrong place) and failed follow the XDA rule of searching before asking a question, because if you had you'd find the answer has already posted multiple times. Not trying to be harsh or rude - just letting you know!
If you have general questions or need help you should really go to the the "Nexus Q Help, Q&A and troubleshooting" section.
However, the situation is that you can't enable debugging on the stock ROM, but you can boot the Nexus Q into fastboot mode by holding your hand over the Q while you turn it on - this will make the led turn and stay red if successful (nothing will be shown onscreen). From there you can unlock your Q and boot a custom recovery image by issuing the correct fastboot commands from your PC. The custom recovery allows you to flash a custom ROM. The stock ROM is no use without the app which cannot be registered anymore since the servers are down.
Huge update, let me know how it's working
jyeley5 said:
Huge update, let me know how it's working
Click to expand...
Click to collapse
How to install this? Please give us some instruction.
Recovery added to original post, flash in fastboot. An amplifier build will be posted as soon as I finish it.
I keep getting "Installation aborted" when trying to flash. Not sure what I'm doing wrong. Used the recovery you just posted.
jyeley5 said:
Huge update, let me know how it's working
Click to expand...
Click to collapse
Tried to flash this latest version but it seems that there is an error in the updater-script. I get a status 6 error in recovery: "Installation Aborted".
Edit: So I edited the updater-script to remedy the status 6 error and then it progressed through most of the way before giving a status 7. I managed to fix the status 7 with a further edit to the updater-script but it still won't boot anything at all. I cannot take a logcat because it isn't booting anything at all and so there is no adb server.
I presume that you have this running on your Q but if you do then you clearly did not use the ZIP that was provided as that doesn't work. Do you have the system images which you just flashed from the bootloader with fastboot? If so perhaps you could share those so I could have a go flashing those instead and see if it will boot then.
wollac, you are correct in stating that I posted the wrong build (uploaded the wrong zip from my dev folder. However, the build I MEANT to post is booting on my Q, though BT and the Amp are not working yet. I'm a tad scatterbrained with finals, but I am compiling a new build that should hopefully resolve the bluetooth issues at least, and I will upload as soon as it's done.