Related
Hello folks!
My name is olddawg, cause I am one!
Love this tablet and see you have ways of making it even better.
Would love to 'give it a go', but I can't seem to get by the first step...
I read the posts, found the ROM I'd like to try and the instructions are pretty thorough, but....
I'll be darned if I see how to back this thing up correctly before I start into any mods...
If I missed the thread, just can't find it or am too blind to see it, please point me that way.
olddawgsrule said:
Hello folks!
My name is olddawg, cause I am one!
Love this tablet and see you have ways of making it even better.
Would love to 'give it a go', but I can't seem to get by the first step...
I read the posts, found the ROM I'd like to try and the instructions are pretty thorough, but....
I'll be darned if I see how to back this thing up correctly before I start into any mods...
If I missed the thread, just can't find it or am too blind to see it, please point me that way.
Click to expand...
Click to collapse
Here's the post that I used....
http://forum.xda-developers.com/showthread.php?t=865245
follow it to the letter, I installed Vegan-TAB GingerEdition RC1
no need to do the Market fix with RC1 Vegan-TAB GingerEdition for me..
Probably should have gone this way right of the bat, but didn't...
The system has upgraded to 3588 and I don't seem to be loading clockworkmod.
I downloaded and see the install in the left corner, but can't enter it.
Shows booting a recovery kernel and loads normal....
Am i too late for the simple change?
I'm following the guide mentioned above....
Is there something different when updated to 3588?
Hello fellow XDA'ers,
With the release of a stable CM9 candidate for the SGH-T849, I wanted to move away from the stock firmware and use a open-source/less-bloatware/pixiedust/unicornmagic firmware. Just like the fat kid squeezing his way into a candy emporium, I ran at the chance to install CM9.
I loaded the page that I had bookmarked for this very purpose:
*I can't post URLs since I am new to XDA, but it is an internal address*
Code:
wiki[dot]cyanogenmod[dot]com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide
I followed the guide for Windows machines. I did not perform any pre-flashing backups, as all data was already backed-up. Furthermore, I'd like to fully format the internal and external SD cards for use with the tablet.
I installed all necessary drivers, and installed Technomancer's ClockworkMod onto the tablet through Heimdall (via download mode). The flash was deemed a success in the command prompt, and the tablet was rebooted by the computer. The blue bar zipped across the tab to show transfer of zImage.
However, after reboot, the tablet is stuck at the T-Mobile loading screen. I force shut down the device by holding the power button, and after shutdown unplug it from the computer.
I turn the tablet back on, and I get the same T-Mobile loading screen. By now, the tablet is looking at me like I'm stupid, which it's fully right in doing. I turn off the tablet by holding the power button, and the tablet turns off.
I try to see the battery level when plugged in via USB-AC power, but I am greeted with a battery icon that has a loading logo.
Before starting this adventure, I made sure the tablet was fully charged.
I can still enter into download mode when connected to the computer. I have only tried Heimdall, and have yet to read up on ODIN.
Relevant device information:
The device was rooted (SuperUser/BusyBox installed)
Model Number: SGH-T849
Firmware Version: 2.2
Baseband version: T849UVJJB
Kernel Version: 2.6.32.9
[email protected] #1
Build Number: FROYO.UVJJB
This is the first time that I have ever tried to flash a firmware onto an Android device. I have successfully flashed my two Nokia N8's with firmwares and have dealt with iPod touch 2Gs jailbreaks, so I am not *completely* computer incompetent. :silly:
I have tried to find the original firmware for the SGH-T849, but all the download links that I have tried to find are either dead or removed. Since only the zImage was replaced, I was hoping to simply re-flash with the factory zImage. Since I can't find the original factory firmware, I have yet to try this option.
I'm not sure what bricked state the tab is in. I'd like to hope it's soft-bricked, but that's probably not the case.
If I need to perform diagnostics on the device (or if any extra informaiton needs to be provided), I can edit this original posting with updated information. I have easy access to a Windows machine, but I may be able to get access to Ubuntu via disk image on another computer.
I don't want to be the jerk who states that "I solved it!" and leaves everyone in the dust: I'll post everything and anything that happens with this problem for future reference.
Other "stuck at loading screen posts" seem very similar to this, but solutions seem to be very divergent. Therefore, I am hoping for some clarity. Considering that the wiki post was designed for the SGH-T849, I think this thread should act as an appendix to the above wiki page for flashing this device.
Thanks,
willing_to_cooperate
Use overcome method.
T849 is the same as P1000 only with different modem.
http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
Sent from my GT-P1000 using xda app-developers app
dropbox *.png image link is 404'd
Hi Priyana,
The missing pictures provided through the Dropbox link at the thread provided is giving a 404 error. Knowing this, there aren't any pictures to follow.
Does anyone have a link to the pictures that *isn't* dead? Perhaps hosting on imgur or bayimg would sove this issue for future users.
I don't want to move on the Overcome method until I have the pictures.
Thanks,
willing_to_cooperate
priyana said:
Use overcome method.
T849 is the same as P1000 only with different modem.
http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hmm.. others can see it, it shouldn't be a drop box.
Here I reattach
Sent from my GT-P1000 using xda app-developers app
Image too blurry
Hi priyana,
The picture looks really tiny with unreadable text. Specifically, it's only 315px wide.
Do you have a better resolution?
Thanks,
willing_to_cooperate
priyana said:
Hmm.. others can see it, it shouldn't be a drop box.
Here I reattach
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
If you search overcome thread you should be able to find.
Nevertheless
http://forum.xda-developers.com/showpost.php?p=25971078&postcount=1316
Sent from my GT-P1000 using xda app-developers app
Hi priyana,
I followed the guide posted, and downloaded all the necessary files (some of the links in the original thread were missing).
Regardless, I downloaded similar files, and cross-checked the SHA-1 hash against what was listed on the Overcome website.
Flashed once (to Samsung factory reset), followed with a second flash to Overcome. Yahoo! :victory:
Thanks again for your guidance, even when I seemed to be a bit of an annoyance.
Again, for those looking to flashing a similar device, I should be holding the files on my computer (just in case). Just in case I need to return the favor.
Cheers!
willing_to_cooperate
priyana said:
If you search overcome thread you should be able to find.
Nevertheless
http://forum.xda-developers.com/showpost.php?p=25971078&postcount=1316
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Update on my GT-P1000/SGH-T849: T-Mobile to Overcome to CyanogenMod9/CM9
For reference:
Some people may be confused on how to move from Overcome to CyanogenMod.
The Overcome guide gives directions for wiping caches before installing the Overcome ROM. However, in the PDF guide, this is crossed out, as it is handled by a script in the Overcome ROM.
CM9 for the GT-P1000 doesn't seem to have that built in, which would cause a boot loop if the cache isn't cleared before installing CM9 for the GT-P1000. Since you can't pop the battery, force-shut-down the tablet by holding the power key until the tab shuts down.
After this, follow the Overcome guide to the point where the section of clearing caches is crossed-out. At this point, it's probably best to re-stock your tab (as priyana always suggests ad nauseum). Read between the crossed-out lines to clear caches, and install CM9 for the GT-P1000. It would be a good idea to install GApps at the same time using the same install procedure.
Hope this helps someone,
willing_to_cooperate
willing_to_cooperate
I'm going to give your username willing_to_cooperate the test
Unbelievably, I have *exactly to the letter* the same problem you had a few months ago. Like you I have a SGH-T849, and like you was trying to breathe some life into it by flashing it with Cyanogenmod. And sadly, like you I "soft bricked" it, so now all I get is a stuck T-Mobile screen on boot.
I've been trying to follow your lead and use Overcome + Odin to make things boot again, but I'm unable to get most of the files necessary. Anything that links to a multiupload.com address right now are broken links. Does anyone have other ways to access the files needed for the Overcome process?
If you have any insight on the specific step of getting the Tab out of its current bricked state, I'd much appreciate it.
Also, SGH-T849 has been mentioned as needing a "different modem". What/where is the correct file to use for that step?
Thanks,
Ben
It is right there in general section.
Or follow my signature.
Sent from my GT-P1000 using xda app-developers app
Completing a request.
Hello bklass!
I will do one better. In this case, I will deliver. As I type, the RAR package is uploading.
I will PM you a link to the file when I have uploaded the necessary package. The link that I will provide to your account will be valid for no more than 72 hours from the time I send you the link to the RAR package via PM, NOT from the time of this public post.
I do not want to post a public link, as people will blindly download it, hoping something works. Better to reply to this thread to get the required package. That way, there's a sense of order for this device.
The size of the package is ~1.23GB.
There are some extra files there, as I was trying to make a full copy of all possible files (to possibly help other users). Please don't be scared with the different modems, just make sure to PICK THE RIGHT MODEM.... or you may screw up your tablet (which you want to avoid).
There is a PDF guide of the steps required for using the different files. I would print this off/have it open on another computer, and read through it SEVERAL times to understand what you are doing. I am not saying it's hard, it is just very technically detailed. Make sure to have an afternoon free for the entire procedure. There is a point in the guide which I labelled as "start here," as I took a break, and didn't want to lose my specific spot. If you want to break up the procedure over two sessions, that'd be a good place to stop.
I am 99.99% sure that all the files are present in the RAR'd directory. However, if by some clerical error I forgot to include a specific file (which may be in another directory on my laptop), please let me know of the exact filename so it can be added to an updated archive I upload and send to interested users.
Simply referring to a post (that may be outdated, littered with dead links, and people thanking in-reply instead of properly using a button) does NOT help potential users/customers entering the Android family.
All I ask is that you publicly reply to this message (when you get the file and go through the steps) if: (1) the package sent to you is complete, and; (2) the package provided actually works.
If you leave this thread empty with no reply, you're not cooperating...which is against my spirit of "willing to cooperate".
If you would like to install CyanogenMod, there is a highlighted step with a red note, and a red box pointing to the red note. I did that, as it is a VERY important step (specifically, making sure you delete the cache to install CyanogenMod properly, as CM packages do not clear caches from previous installations automatically: it must be done manually by the user).
For reference, I am successful in running CyanogenMod 9.0 (stable).
Happy Flashing!
willing_to_cooperate
bklaas said:
willing_to_cooperate
I'm going to give your username willing_to_cooperate the test
Unbelievably, I have *exactly to the letter* the same problem you had a few months ago. Like you I have a SGH-T849, and like you was trying to breathe some life into it by flashing it with Cyanogenmod. And sadly, like you I "soft bricked" it, so now all I get is a stuck T-Mobile screen on boot.
I've been trying to follow your lead and use Overcome + Odin to make things boot again, but I'm unable to get most of the files necessary. Anything that links to a multiupload.com address right now are broken links. Does anyone have other ways to access the files needed for the Overcome process?
If you have any insight on the specific step of getting the Tab out of its current bricked state, I'd much appreciate it.
Also, SGH-T849 has been mentioned as needing a "different modem". What/where is the correct file to use for that step?
Thanks,
Ben
Click to expand...
Click to collapse
Thanks, got the files.
I will post back to the thread when I have gone through the overcome guide and report how it went. (next week at the earliest)
cheers
priyana said:
It is right there in general section.
Or follow my signature.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I'm pleased to say that I've successfully unbricked and flashed the Overcome kernel and 4.1 ROM.
My next step is going all the way to CM9...I'm confused on a few aspects-- First, is it correct to assume that I need to flash to a CM9 kernel before flashing the CM9 ROM?
willing_to_cooperate: if that's the case, that might be the file you forgot to include in your excellent rar archive you sent my way. You really went the extra mile on the instructions btw.
Second, there was a mention earlier in the thread it would be a good idea to go back to stock before moving to CM9. If that's the case, why did I install the Overcome ROM in the first place? Was that a wasted step, considering my end goal was CM9?
cheers,
#!/ben
bklaas said:
Thanks, got the files.
I will post back to the thread when I have gone through the overcome guide and report how it went. (next week at the earliest)
cheers
Click to expand...
Click to collapse
bklaas said:
I'm pleased to say that I've successfully unbricked and flashed the Overcome kernel and 4.1 ROM.
My next step is going all the way to CM9...I'm confused on a few aspects-- First, is it correct to assume that I need to flash to a CM9 kernel before flashing the CM9 ROM?
willing_to_cooperate: if that's the case, that might be the file you forgot to include in your excellent rar archive you sent my way. You really went the extra mile on the instructions btw.
Second, there was a mention earlier in the thread it would be a good idea to go back to stock before moving to CM9. If that's the case, why did I install the Overcome ROM in the first place? Was that a wasted step, considering my end goal was CM9?
cheers,
#!/ben
Click to expand...
Click to collapse
The guide was overcome, that is why overcome ROM was flashed using CWM.
But, actually you don't need that.
You only need to Odin flash the Overcome kernel.
That is it. You don't even need to wait for the robotic voice to complete its thing.
Just force it off.
Then boot to recovery.
use that recovery to flash CM9, twice.
You are kind of right, you need CM9 kernel, but it is done by the first flash
(spot the CWM is different from overcome one, after first flash).
Second flash will install CM9.
Then you flash gapps and reboot.
If you reboot after CM9 without gapps, you can still flash gapps later, but you won't get the setup wizard (the one that ask you to set up wifi, put gmail id, choose to use gmail to backup, bla bla)
So just remember, in the future, restock means Odin flash GB-stock-safe.
Then you will want to Odin flash the Overcome kernel because that is the easiest way to install CWM.
From there it is flashing from CWM.
Full success thanks to this thread
I am 100% up and running with CM9 on my SGH-T849 (T-Mobile branded original 7" Galaxy Tab), thanks to the excellent help from willing_to_cooperate and priyana.
FYI, 2 biggest roadblocks to getting this completed were:
1. Inability to find the necessary files because of broken links, downloads found on sites blocked as malware, etc. [SOLVED] by willing_to_cooperate and him putting together an awesome .rar archive of all necessary files, including a critical annotation in the Overcome guide PDF that told me about the necessary step of wiping cache when flashing CM9
2. Inability to find well-written or even correct information about what to do. As a gadget hobbyist, I have been doing Linux stuff for almost a decade. That community tends to be very sharp and focused to task. The android mod community is quite a bit different I'm finding out-- for every thread with good discussion points there are 25 that say "How do I tweak teh andrd better so I can show everyone how kewl I am". I will concede that this just comes with the territory. Someone tweaking their stock T-mobile phone is quite a bit different than someone installing Ubuntu on a laptop. Nevertheless, [SOLVED] again by willing_to_cooperate and priyana on this thread. Kudos to both of you.
For the record, though I jumped through a few more hoops than was required, these were the steps from getting to "soft-bricked" Galaxy Tab SGH-T849 to fully running CM9 w/gapps.
1. Follow Overcome guide documentation to restock stable Gingerbread
2. Follow Overcome guide to flash Overcome kernel 4.0.0 using Odin
3. Boot and connect Tab as USB storage device
4. Copy CM9 and gapps zip files to mounted Tab (which is the internal SD card)
5. Boot into recovery mode (clockwork mod, which was installed in step 2)
6. Wipe flash/cache through Clockwork Mod
7. Install CM9 and gapps through Clockwork Mod
8. Boot and rejoice in the CM9 awesomeness
cheers,
#!/ben
For the record (as you already have CM9 working on your tablet), I did not include CyanogenMod (CM) releases in the package that I sent to you.
The reason I didn't do that is that the CM ROMs are always updating, and it is easier for the user to find the correct and safest location to download the plain CM ROM files.
For those wondering what address I'm referring to:
http://get.cm/?device=p1 "p1" is the code name for the device.
To clarify, the package that I sent is what I used to get my tablet out of stock (T-Mobile) via Overcome, then updating to CM9.0.
You can select stable, release candidate (RC) or nightly from the menu on the left-hand side. If you are just starting, I would strongly suggest you use the most recent stable ROM for your device (that way, you minimize the risk of using a ROM that may still have bugs).
Good to hear of success relating to your device.
To other people that need the package that I sent to bklass (as you cannot find all the files required due to possible broken links that may happen now or in the future), please PM me and refer to this thread.
I will try to re-write the Overcome guide on a long-term "to-do list" that will clearly delimit what point is restocking, and what point is flashing with another ROM. That, or updating the relevant CM wiki page with proper steps. That way, there is no need to search for a PDF or picture file with relevant steps, just refer to the proper steps in the CM wiki link.
When I rewrite the guide, I'll make sure to include files that are required, with relevant MD5 hashes appended.
Regards,
willing_to_cooperate.
bklaas said:
I'm pleased to say that I've successfully unbricked and flashed the Overcome kernel and 4.1 ROM.
My next step is going all the way to CM9...I'm confused on a few aspects-- First, is it correct to assume that I need to flash to a CM9 kernel before flashing the CM9 ROM?
willing_to_cooperate: if that's the case, that might be the file you forgot to include in your excellent rar archive you sent my way. You really went the extra mile on the instructions btw.
Second, there was a mention earlier in the thread it would be a good idea to go back to stock before moving to CM9. If that's the case, why did I install the Overcome ROM in the first place? Was that a wasted step, considering my end goal was CM9?
cheers,
#!/ben
Click to expand...
Click to collapse
> I will do one better. In this case, I will deliver. As I type, the RAR package is uploading.
Hi! Do you still have that RAR file? I followed the steps at the cyanogenmod site and ended up with the same t-mobile image.
I can still connect to my phone typing "adb shell" on the terminal, and execute commands there, but I do not know how to bring it back to life.
Thanks!
If you're using terminology like shell, I'll assume your on a *nix system.
In short, the files are Windows-based, and should have all components.
PM me and I'll send you the link, as I don't want the RAR file publicly posted (I have limited hosting space via Drop box that I don't want slammed by the XDA community).
Cheers!
willing_to_cooperate
Sent from my GT-P1000 using xda app-developers app
I'm having a difficult time getting mine off the boot screen. Odin doesn't recognize it thus the Overcome steps don't work. Any thoughts?
Thanks,
Holy
Holyloktar said:
I'm having a difficult time getting mine off the boot screen. Odin doesn't recognize it thus the Overcome steps don't work. Any thoughts?
Thanks,
Holy
Click to expand...
Click to collapse
Hi Holykotar,
Hmm... Let me troubleshoot. I'll be approaching your problem from a "cross-examination/troubleshooting" perspective. Please answer all the questions below:
1) Are you having a bootloop? That is, tablet boots up, goes to a logo, then repeats until you get bored?
If you can, it may be wise to enter recovery, delete all caches, and re-start the tablet.
The first time I tried going through the steps, I had a bootloop as the caches were incompatible with the ROM. This may be your case, but it is difficult to determine with the limited information that you have provided me.
Therefore, as stated, I would start off by going into recovery, and deleting all caches. If that works, let me know.
2) What version of ODIN are you using?
Later versions may be incompatible. I used Odin3 v1.7 with success on Windows 7 Ultimate. Also, it could be an issue of not starting ODIN with administrative privileges.
3) What OS are you using?
This may seem silly, but good information for people reading this thread. As stated, I used Windows 7 Ultimate.
4) Have you installed the required computer drivers so the tablet is successfully recognized by the computer?
This would fix some interface issues. If the software (ODIN) can't communicate with the tablet (GT-P1000), then it may be a driver issue.
5) What guide are you using? Better yet, do you have all the required files?
If you are using the guide entitled: "The Overcome Experience" (I have it as a PDF), then there shouldn't be any problems. However, if you are having issues with a proper guide, PM me and I will send you a link to download all necessary files to flash the GT-P1000 (T-Mobile version) without any problems. I request that you PM me for the files, as I don't want the download link distributed (as my bandwidth is fast but limited).
Happy Flashing :laugh:
willing_to_cooperate
Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1
Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium
mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.
professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.
Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.
Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.
i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!
So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium
Hello all, I have a friend who wants me to help him install an updated version of Android on his AT&T Galaxy Tab SGH-i987. I have had god experience with CyanogenMod, so I thought I would try that. I read through quite a few threads and saw alot of confusing information. Many of the main articles had dead links, so I thought I would try the CyanogenMod Instructions. http://wiki.cyanogenmod.org/w/Install_CM_for_p1 I ran through the instructions to the point where I flashed ClockworkMod with Heimdall. Whenever I restart the unit I get a single gray line 2/3 of the way across the screen which quickly fades to nothing. This happens when I hold volume up. Whenever I hold volume down, I can get to the download screen still.
Any suggestions or references to threads that would be helpful now. There are some soft brick instructions I was going to follow if nothing else to get him back to stock, but I would rather get him on CM.
Thanks,
Brennan
OK, I have done a little bit more research, and I am not sure where to go next. It seems I might want to restock (Not fully sure what that means) but all of the files are for Gingerbread, and I (was) on Froyo.
So I guess right now I would take any suggestions that will get the tablet back up and running, though I would still like to get to something Gingerbread.
Thanks for any help you might be able to provide.
Brennan
Follow my signature and use overcome method. It is suitable for your tab.
Sent from my GT-N7100 using xda app-developers app
Thanks! I followed the instructions and got it up and running.
Ok guys THIS IS A ZIP PORT, AND IT IS UNTESTED.
I AM NOT RESPONSIBLE FOR BRICKS, BOOTLOOPS, PHONES WALKING AWAY, GETTING SICK OR ANY OTHER PROBLEMS CAUSED BY THIS.
I have a CM10 zip port from the Esteem, it is a ZIP PORT, and therefore not all features will work.
it is a work-in-progress.
whats done so far:
Switched out meta-inf
Corrected build.prop(may cause problems)
Changed HW, EGL, MODULES folders from lib(this will cause problems)
Changed some stuff from usr folder(may cause problems)
Changed libmultimode-ril.so(may cause problems)
Changed several items in etc folder
Switched out the kernel boot.img
This ROM WILL NOT WORK OUT OF THE BOX, IF you download it ,you must help get it at least bootable.
http://rapidshare.com/share/670E544D81A5DE1226B1BEC75DF89E49
This is NOT a daily driver, it is just a base so eventually we can have a working build.
ROM goals:
Get it to boot.
Get to home screen, run settings, look at jellybean.
Stretch goals:
Get most features working.
Anyone have suggestions or improvements?
And has anyone tested it yet(those with a unused Revolution).
If we can get it working, it will mean that the few of us here will not jump ship.
Hey guys, anyone there?
Is anyone still here?
This ROM is CYANOGENMOD, you'd think people would be all over this.
I need someone to download it, and look it over, to see what needs to be fixed to make it work on the revolution.
And anyway PatchROM is finished, i am working on this now(i am still using PatchROM but is wont be updated, unless i find a new feature that will revive it)
Come on people, anyone here, i need some tips, anything that will help push this thing along.
I'm still here, somewhat, anyway. I just compiled a cm-10.1 build, got it all the way through by adding .so files dl'ed from phone into $OUT folders as it threw errors. First try, had adb, but just bootlooped. Second go bricked my phone. I got it back by factory resetting it and it came back up in recovery. Thank god for backups.
Just dl'ed your build. Will have a look at it. We need a central repo we can work from, so we can work together. No sense in both of us working alone. PM me and I'll set you up with owner rights to a github repo that has all the files I could dig up on this phone. Or your repo, I'm not picky. Maybe we can make progress together. It sure isn't working for me by myself.
If you use dev-host (http://d-h.st/), downloads wouldn't take anywhere near as long. I'm looking at an hour to dl 164 mb's. I can dl a whole ubuntu dvd in less time than that. Just saying...
redwolves said:
I'm still here, somewhat, anyway. I just compiled a cm-10.1 build, got it all the way through by adding .so files dl'ed from phone into $OUT folders as it threw errors. First try, had adb, but just bootlooped. Second go bricked my phone. I got it back by factory resetting it and it came back up in recovery. Thank god for backups.
Just dl'ed your build. Will have a look at it. We need a central repo we can work from, so we can work together. No sense in both of us working alone. PM me and I'll set you up with owner rights to a github repo that has all the files I could dig up on this phone. Or your repo, I'm not picky. Maybe we can make progress together. It sure isn't working for me by myself.
If you use dev-host (http://d-h.st/), downloads wouldn't take anywhere near as long. I'm looking at an hour to dl 164 mb's. I can dl a whole ubuntu dvd in less time than that. Just saying...
Click to expand...
Click to collapse
Have you tested this one yet?
And this isnt a source build its ZIP ported from the esteem.
And yes rapidshare is slow I downloaded saucy salemander in 9 minutes, CM10 takes years.
maybe we could just, use this build and recompile SEPERATE modules as we go to get it working, but I don't know how well it would work.
Plus the build may not work at all, IDK because its untested.
thread closed at the request of the OP