After munging about in the forums, lurking and trying to absorb your knowledge, I'm still mysified by how to non-destructively put android on my friend's phone.
It's ether I can't find the files/the info is outdated, or it simply doesn't work.
Here is the skinny -
I own a reflashed and rooted Motorola droid, so flashing a phone isn't that much of a mystery to me.
My friend has a U.S. Vogue CDMA, however it is ABSOLUTELY CRITICAL that we do not touch the nand. He uses it for development and has a few hundred dollars in apps that he has purchased for WiMo. We would like a stright boot directly from the flash card.
SO I guess, here is a run down of what I'm looking for
What files do I need to boot 2.1 off of a flash card? A file manifest with a decent description of what the files do would be helpful. I'll give an example..
Step one:
If you do not have dzo's latest nbh get it from here:
Click to expand...
Click to collapse
I don't think that sentence is in English. I just can't parse it. What is an nbh and what does it do. Is it a bootloader? What is it's payload? Now this is from the tutorial to flash the nand, which is not what I want to do, but it's giving an example of what I'm finding.
I'm under the instructions of "you can put android on my phone, just don't screw anything up", so clear and full explanations would be very helpful...
Any particular reason why you guys just don't package this? On my droid, the whole OS is on a simple update.zip file I have to run with a loader. Are not at that point yet?
There are plenty of guides for installing and running android from the sd card.
Just like on your 'droid' forums all you have to do is search
http://forum.xda-developers.com/showpost.php?p=5579562&postcount=15
And as for packaged compared to the update.zip's you use. It's apples and oranges man
You need to be looking at this post. There isn't a way to boot straight to Android on the Vogue without nuking your WinMo installation.
To install 2.1, you're going to need "haretinstall.zip" and "zImage-eclair" from the Sourceforge page linked in that post. Unzip haretinstall.aip to /sdcard/andboot and replace zImage with zImage-eclair.
Still at Sourceforge, you need to go down to the "2010-01-29" folder and download "eclair.zip". This should contain a file called "androidinstall.tar". Put that file in the andboot folder, but don't extract it. After this, you should be able to follow the instructions I linked.
Any particular reason why you guys just don't package this? On my droid, the whole OS is on a simple update.zip file I have to run with a loader. Are not at that point yet?
Click to expand...
Click to collapse
This is pretty much all you're doing - you just have to jump through a few hoops to get the loader installed since this phone came out about a year before Android was even announced.
Also, make sure he's not expecting this to work perfectly or be super-fast. Bluetooth doesn't fully work with Eclair yet and the Vogue is working with about 1/4th the processing power of the Droid and N1.
you can use y gen dual boot to bring you up to a nice gui to pick what u want to boot into on reset if you would like. Almost like a boot loader. Get it here http://forum.xda-developers.com/showthread.php?t=623792
OK, I have a Droid 3, that I messed up. I spent the last week searching to find a solution, but this has only left me more confused than ever. When I find what looks promising the links to the file don't work. I am a bit overwhelmed now and need help.
Here is what happened. I installed ClockWorkMod Rom Manager on my rooted Droid 3. I tried to make a backup, this did not work. I then found ClockWorkMod Droid 3 Recovery Bootstrap, this worked then I made a backup. I then tried to load cyanogenmod this failed. Now the phone is stuck on the Motorola Logo, I left it on overnight and it was still stuck. Now I can reboot +X , but I only get the Android System Recovery, but it doesn’t see the backup made by Droid 3 Recovery. The phone does not boot to the Droid 3 Recovery menu (or atleast I don’t know how).
I can also get to the “Boot Mode Selection Menu 0A.64” but I am more confused about all these options. I tried looking for file to flash but I can’t figure this out. The options I have on this menu are;
Normal Powerup
Recovery
AP Fast Boot
BP SBF Flash Mode
BP Only
BP HW Diag & Boot AP
BP Tools
I was able to connect my phone to the pc, but I don’t know how to use any of these options or what software I need on the PC to make this work. Yes I am a noob and this is my first post.
So, how can I get my phone to work again?
Please help, Thanks
The best idea is to use RSD Lite with AP Fastboot to restore an SBF to bring the phone to scratch.
sd_shadow has a great resource here: https://docs.google.com/document/d/...gVAeQXxSkaLPlBAAw/edit#heading=h.lpb8vdlj146l
But, to save some time, you'll find the SBF files that you want here: https://docs.google.com/document/d/...gVAeQXxSkaLPlBAAw/edit#heading=h.lpb8vdlj146l
You want the download link in the third line, under build number 5.5.1_84_D3G-66_M2-10
Blur_Version.5.7.906.XT862.Verizon.en.US
To get to AP fastboot mode, follow this: https://docs.google.com/document/d/...AeQXxSkaLPlBAAw/edit#bookmark=id.xj82g0jvczjr
For RSD Lite instructions, see this: https://docs.google.com/document/d/...AeQXxSkaLPlBAAw/edit#bookmark=id.77zigoazhz70
And give a big thanks to sd_shadow for collecting all of those instructions in one place. Totally awesome.
Thanks, that worked great. My phone is working again.
Now on a slightly paranoid note, how can you be sure that the file that was used to program the phone is truely the stock version from verizon and does not contain any malware?
sheatrek said:
Thanks, that worked great. My phone is working again.
Now on a slightly paranoid note, how can you be sure that the file that was used to program the phone is truely the stock version from verizon and does not contain any malware?
Click to expand...
Click to collapse
The locked bootloader prevents anything that isn't official motorola from being flashed to the phone
Sent from my XT860 using xda premium
doogald said:
And give a big thanks to sd_shadow for collecting all of those instructions in one place. Totally awesome.
Click to expand...
Click to collapse
thanks doogald
I started my list, for a few reasons, because like you I post on several other forum's, good threads don't get stickied, stickied threads get outdated very fast and don't get updated because the OP, has moved on to another device
I'm also working on uploading sbfs and xml file to
dev host and android file host
Sent from my XT862 using Tapatalk 2
Did you figure it out if not I did the sane to this phone and fixed it and I'll help you if you didn't fix it
Sent from my DROID3 using xda app-developers app
Sounds like he fixed it.
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Click to expand...
Click to collapse
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
Ouya-XD said:
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Rirere said:
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Click to expand...
Click to collapse
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
glitchhawk said:
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
Click to expand...
Click to collapse
NTFS support can be added at the kernel level, but I don't know of any recoveries that support it, sadly. And that's unfortunately the nature of the beast, and probably why many recoveries will break files up into multiple archives.
Go full *nix and use ext4 like a man... Unless you're a woman, then use it like a woman.
Sent from my SAMSUNG-SGH-I317 using xda premium
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
B4 I updated I needed SU to make the reeboot. Feature work.
Sent from my Amazon Kindle Fire using xda app-developers app
that was my thought, however I just reran the .bat for cwm and flashed that way.
Kickbut101 said:
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
Click to expand...
Click to collapse
I'd assume if it's not working that way then to try the ADB method instead, again, please report all issues to me.
Do you have CWM installed, on a final note?
People cry a out signatures, there's no need for one! I love my community and will stand up for it!
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
If this was useful to you, I can only ask of a favor!
Check out my YouTube channel!
http://WWW.YouTube.com/user/TheDarkRosarySubscribe if you will! I will be covering everything Ouya and doing news soon!
Click to expand...
Click to collapse
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
TadeoNYC said:
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Oscar_david said:
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Click to expand...
Click to collapse
Thanks man, I'll make sure to add it to the OP.
Sent from my HTC One VX using xda app-developers app
Ouya-XD said:
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
TadeoNYC said:
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Don't worry, this morning I was frustrated.
I'm sorry, tell me what you think I'm missing and I'll add the quote to the OP.
I plan on doing a video tut though.
Sent from my HTC One VX using xda app-developers app
worst
this is the worst tutorial I've ever read on xda. mods please take down this how to brick your ouya tutorial before people start downloading wrong files and bricking there ouya.
Okay where is your full proof method of rooting and installing cwm on the ouya?
Sent from my Vivid 4G using xda premium
Going by the threads opened/posts by this fellow, maybe a sticky to let people know who to avoid is needed.
OP, maybe your're over-enthusiastic over your new Ouya, but XDA prides itself on people who actually KNOW what they're doing to help, not rambling nonsense.
I came here looking for root help with this device. I see the autoroot by chainfire is not listed for this. Can i get some direction on how to go about it?
Sm-t805 version should work
Kahun said:
Sm-t805 version should work
Click to expand...
Click to collapse
Ok i understand that you think it should work even though it is not the same nomenclature. Why should i believe that it should work when the nomenclature is different? What are my available options of in fact ir doesnt work and my device is bricked? I saw on other post in this forum on th 807p and it appears the person in that thread now has a bricked device that can not be recovered. So you see my reluctance to trust something that isnt clearly marked as for use with the nomenc.ature of my device. Thanks for your help with this.
liz.beth said:
Ok i understand that you think it should work even though it is not the same nomenclature. Why should i believe that it should work when the nomenclature is different? What are my available options of in fact ir doesnt work and my device is bricked? I saw on other post in this forum on th 807p and it appears the person in that thread now has a bricked device that can not be recovered. So you see my reluctance to trust something that isnt clearly marked as for use with the nomenc.ature of my device. Thanks for your help with this.
Click to expand...
Click to collapse
Could possibly brick try at your own risk if your desperate. Like you said I would just wait for it to get released.
In case it wasn't clear, I acknowledged that the device isn't listed in that thread, as such I am seeking other options for rooting my device. Are there other options available for rooting it?
This is the thread for you to ask:
http://forum.xda-developers.com/showthread.php?t=1980683
He'll need a copy of the recovery file that's inside the rom file. So you'll need access to the full file which I'm not sure it's even been released (try and get it so you have a copy for the future).
Sent from my SM-G900P using Tapatalk
Itchiee said:
This is the thread for you to ask:
http://forum.xda-developers.com/showthread.php?t=1980683
He'll need a copy of the recovery file that's inside the rom file. So you'll need access to the full file which I'm not sure it's even been released (try and get it so you have a copy for the future).
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Thanks for the clue. I still have less than 10 posts so i cant ask a question there yet. Maybe if we post back and forth enough here ill get b my 10 post requirement met?
I tried to find a copy of the ROM your using (T807PVPU1ANH1) but its not available at the regular locations....
http://samsung-updates.com/
http://www.sammobile.com/
No downloads on the Sprint and Samsung sites...
Samsung tablets are fairly hard to destroy as long as you can access recovery (and use Odin to flash a stock ROM) or get this Kies program to work.
i considered trying to extract the recovery.img but after installing android studio and the Java jdk, there seems to be some issue with android studio not recognizing the jdk path so I quit. . If you have some ideas, I'd be glad to take in any assistance you have.