Database Develop

CM10.1 for the HTC Vivid/Holiday/Raider

This is my first Rom port/compile attempt.
Please be patient with me.
As with all other roms on XDA, I am not liable for bricked devices. Hopefully, I can get some real devs to help me get this working.
The port is from a stable build of the CM10.1 Rom for the HTC Sensation.
If a Dev sees this, just know that I will give full credit where it is due.
[UPDATE]Link down till major issues pointed out are fixed[/UPDATE]

Mihir1997 said:
This is my first Rom port/compile attempt.
Please be patient with me.
As with all other roms on XDA, I am not liable for bricked devices. Hopefully, I can get some real devs to help me get this working.
The port is from a stable build of the CM10.1 Rom for the HTC Sensation.
If a Dev sees this, just know that I will give full credit where it is due.
CM10.1_Holiday_Port_v1.zip
Click to expand...
Click to collapse
Link broken...
Updater script is bad... May I ask how you ported this? Like what steps did you take?

Just going to warn everyone reading this right now: as is, the .zip installer in the OP is broken and will not flash WHICH IS A VERY GOOD THING BECAUSE THE MOUNT POINTS IN THE UPDATER SCRIPT ARE ALL ALIGNED TO THE SENSATION'S PARTITION TABLE. You know how it's common knowledge not to flash something designed for one device onto another device? The reason why doing that can brick your device is because THE PARTITION MOUNT POINTS ARE DIFFERENT. The updater script in the OP's ROM flashes /system to the boot partition of the Vivid and it flashes the boot.img to the mmcblk0p20 partition; the boot partition for the Vivid is mmcblk0p22. I'm not sure what function the mmcblk0p20 partition serves on the Vivid, so flashing this ROM on your device could very well brick it. DON'T FIX THE ROM ZIP FILE AND FLASH IT! YOU HAVE BEEN WARNED!

android1234567 said:
Just going to warn everyone reading this right now: as is, the .zip installer in the OP is broken and will not flash WHICH IS A VERY GOOD THING BECAUSE THE MOUNT POINTS IN THE UPDATER-SCRIPT ARE ALL ALIGNED TO THE SENSATION'S PARTITION TABLE. You know how it's common knowledge not to flash something designed for one device onto another device? The reason why doing that can brick your device is because THE PARTITION MOUNT POINTS ARE DIFFERENT. The updater-script in the OP's ROM flashes /system to the boot partition of the Vivid and it flashes the boot.img to the mmcblk0p20 partition; the boot partition for the Vivid is mmcblk0p22. I'm not sure what function the mmcblk0p20 partition serves on the Vivid, so flashing this ROM on your device could very well brick it. DON'T FIX THE ROM ZIP FILE AND FLASH IT! YOU HAVE BEEN WARNED!
Click to expand...
Click to collapse
somebody get a mod to remove both of his ports links before someone actually bricks

ZeRo2o9 said:
somebody get a mod to remove both of his ports links before someone actually bricks
Click to expand...
Click to collapse
The OP's MIUI .zip file has the correct mount points in the updater-script but even if the OP ported vold and all that other stuff correctly there's no way in hell it's going to boot because it's uses the Sensation's boot.img, AKA it uses the Sensation's kernel and ramdisk. The MIUI .zip the OP made also won't flash because the directories inside aren't where they're supposed to be.
EDIT: The MIUI .zip might use a boot.img designed for the Vivid but the CM10.1 .zip file definitely uses the Sensation's boot.img (I just booted the boot.img up on my Sensation).

android1234567 said:
The OP's MIUI .zip file has the correct mount points in the updater-script but even if the OP ported vold and all that other stuff correctly there's no way in hell it's going to boot because it's uses the Sensation's boot.img, AKA it uses the Sensation's kernel and ramdisk. The MIUI .zip the OP made also won't flash because the directories inside aren't where they're supposed to be.
EDIT: The MIUI .zip might use a boot.img designed for the Vivid but the CM10.1 .zip file definitely uses the Sensation's boot.img (I just booted the boot.img up on my Sensation).
Click to expand...
Click to collapse
I kind of guessed that already that was why I was asking for him to post all info and source. He must not have followed porting correctly you need to use your base kernel and create modifications from there I know I did it myself

ZeRo2o9 said:
I kind of guessed that already that was why I was asking for him to post all info and source. He must not have followed porting correctly you need to use your base kernel and create modifications from there I know I did it myself
Click to expand...
Click to collapse
Yeah. The Linux kernel is covered under the GPL so whenever it is publicly distributed, the compiled binary's source code must be posted as well. Or on XDA if a person posts a ROM that uses a kernel that they did not build then they need to add a link to said kernel's XDA thread or source code.

android1234567 said:
Yeah. The Linux kernel is covered under the GPL so whenever it is publicly distributed, the compiled binary's source code must be posted as well. Or on XDA if a person posts a ROM that uses a kernel that they did not build then they need to add a link to said kernel's XDA thread or source code.
Click to expand...
Click to collapse
as far as his miui goes he could use parts from my port if he needs to might make it easier for him just always give credit to creator/source

Sorry.
ZeRo2o9 said:
as far as his miui goes he could use parts from my port if he needs to might make it easier for him just always give credit to creator/source
Click to expand...
Click to collapse
I am not sure how useful your MIUI Port would be to my little project. I have no idea how the MIUI V4 and V5 files corelate, so I don't know how to interchange them correctly. Thanks for the offer. I will keep it in mind
Believe me, I mean no disrespect or harm to anyone or their phones. Notice I have removed download links.

This post is veeery sketchy I've never heard of this guy and it seems like he doesn't know how to port properly :/. And no screenshots??
Sent from my Vivid 4G using xda premium

Mihir1997 said:
I am not sure how useful your MIUI Port would be to my little project. I have no idea how the MIUI V4 and V5 files corelate, so I don't know how to interchange them correctly. Thanks for the offer. I will keep it in mind
Believe me, I mean no disrespect or harm to anyone or their phones. Notice I have removed download links.
Click to expand...
Click to collapse
the updater script for one is set up right, you can see how the rom flashes and what points, and the boot.img is already edited for miui with the shelld so it starts on boot

ZeRo2o9 said:
the updater script for one is set up right, you can see how the rom flashes and what points, and the boot.img is already edited for miui with the shelld so it starts on boot
Click to expand...
Click to collapse
I see...
so. do i just use your updater script or edit my update points?

ZeRo2o9 said:
the updater script for one is set up right, you can see how the rom flashes and what points, and the boot.img is already edited for miui with the shelld so it starts on boot
Click to expand...
Click to collapse
I tried to flash my MIUI rom, and I noticed a weird type of bootloop. It works fine at first. MIUI logo... then it says optimizing apps. Goes through that. without any hiccups. Then it says starting Apps. Then it goes to the MIUI boot screen (orange MI on black screen.) after that it alternaties between "Starting apps", and the MIUI boot screen.
If someone advises me on how to use Zer0's boot.img and Updater, i think it will work.
UPDATE: I just replaced the boot.img with ZeRo's boot.img from his JB rom, and the issue still persists. Any help would be much appreciated.
Cheers,
Reminder: I am a newbie. this is my first attempt at porting. I realize that my CM10.1 won't work, coz I used a CM10.0 base while porting But I really think, with Zer0's help, I can get MIUI V5 up and running. Zer0, please do PM me if you think you would like to help me get this off the ground.

Try pulling a logcat while it's booting up and bootloops. Think I had this problem before can't remember what it was. You also need the AT&T ext.jar file instead of the sensation one
Sent from my HTC One X using Tapatalk 2

[HOWTO] Boot Ouya Into CWM/Flashing ROMs

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/TheDarkRosary​Subscribe 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.

[DEV][KERNEL] Magic sysrq to boot into bootloader (fastboot) mode

For anyone that is building their own kernels, I highly recommend grabbing this patch:
https://github.com/invisiblek/andro...mmit/f745249b52cab9feb5b7821b54d47176ae093617
Details in the commit comments.

You know what I've been hacking phones for awhile and I forgot about fastboot booting a boot.img

Haven't tried it, but sounds like nice work!
I had another idea for adding some safety - early in the boot process set the bootlloader message to tell the bootloader to boot into recovery mode (but don't actually reboot), then later when the boot is complete, reset the message. That way if the user reboots anywhere in between, they will boot into recovery.
Hope that makes sense, I brainstormed over the idea in another thread: http://forum.xda-developers.com/showpost.php?p=44030783&postcount=8
Feel free to implement any of my ideas you like - I don't have as much time for Android development as I would like.
~Troop

Trooper_Max said:
Haven't tried it, but sounds like nice work!
I had another idea for adding some safety - early in the boot process set the bootlloader message to tell the bootloader to boot into recovery mode (but don't actually reboot), then later when the boot is complete, reset the message. That way if the user reboots anywhere in between, they will boot into recovery.
Hope that makes sense, I brainstormed over the idea in another thread: http://forum.xda-developers.com/showpost.php?p=44030783&postcount=8
Feel free to implement any of my ideas you like - I don't have as much time for Android development as I would like.
~Troop
Click to expand...
Click to collapse
Yea, you could probably make the kernel write to scratch right away, in the case that it panics, dump it into recovery or bootloader, then clear it upon a full, successful boot. But that sounds like a lot more work and in the end, you really don't get anything more than this. This patch will save you from anything except a kernel panic that happens way early. (or of course blatantly flashing crap to the wrong partitions )

invisiblek said:
Yea, you could probably make the kernel write to scratch right away, in the case that it panics, dump it into recovery or bootloader, then clear it upon a full, successful boot. But that sounds like a lot more work and in the end, you really don't get anything more than this. This patch will save you from anything except a kernel panic that happens way early. (or of course blatantly flashing crap to the wrong partitions )
Click to expand...
Click to collapse
Ah, I was just thinking maybe it would be possible to write to scratch earlier than the sysrq method becomes available and thus be a little bit safer. It also wouldn't require a keyboard though that point would be a bit moot as you'd need a keyboard once you reboot into recovery. So you're right, it probably doesn't make much difference.
Have you ever done anything with kexec? That was the next thing I wanted to look into once we got something like this for booting more safely. I know people use it for multi-boot methods and someone even came up with a way to hardboot a Nexus 7 with kexec:
http://forum.xda-developers.com/showthread.php?t=2104706
Eventually, I'd like to develop something like that into a boot image that could be stored on the boot or recovery partitions and function as an extra bootloader to allow booting images stored elsewhere.
Anyway, thanks again for sharing your work, and I don't mean to hijack your thread - if you want to discuss ideas I had hoped more people would join in on brainstorming in my thread: http://forum.xda-developers.com/showthread.php?t=2380314
~Troop

Trooper_Max said:
Ah, I was just thinking maybe it would be possible to write to scratch earlier than the sysrq method becomes available and thus be a little bit safer. It also wouldn't require a keyboard though that point would be a bit moot as you'd need a keyboard once you reboot into recovery. So you're right, it probably doesn't make much difference.
Have you ever done anything with kexec? That was the next thing I wanted to look into once we got something like this for booting more safely. I know people use it for multi-boot methods and someone even came up with a way to hardboot a Nexus 7 with kexec:
http://forum.xda-developers.com/showthread.php?t=2104706
Eventually, I'd like to develop something like that into a boot image that could be stored on the boot or recovery partitions and function as an extra bootloader to allow booting images stored elsewhere.
Anyway, thanks again for sharing your work, and I don't mean to hijack your thread - if you want to discuss ideas I had hoped more people would join in on brainstorming in my thread: http://forum.xda-developers.com/showthread.php?t=2380314
~Troop
Click to expand...
Click to collapse
We used kexec on the vzw sgs3. It may be useful here but really probably isn't too necessary
Sent from my HTC6435LVW using Tapatalk 4

[Q] Anyone still working on these?

I was given a Dell Streak 7 (T-Mobile Branded) by a friend after the tablet would only start booting up in Fastboot mode.
The tablet says:
Code:
[COLOR="Red"]username: cmbuild hostname:QTHBuildPC-17 buildnumber : 14236
build on Jan 6 2011 19:35:54[/COLOR]
Starting Fastboot USB download protocol
I successfully flashed boot_orig.img, recovery_orig.img, and system_orig.img from another post, but I'm still having the same problem.
**EDIT**
I want to make it clear I did try hitting the reset button
giveen said:
Little hole next to SD card, press it with a paper clip
or
Or if you have 'fastboot' program and drivers are installed, at command prompt you would type 'fastboot reboot'
Click to expand...
Click to collapse
I really wanted to install a custom ROM on this thing and let the kids play around with it. I have plenty of experience with TWRP, CyanoMod, ADB, Fastboot, etc...
Anyone have any ideas?

Nobody is working on these anymore. The lack of source and not having an updated kernel to give us anything stable from any jb+ rom...... KK or LP would run much more efficiently on this device but nobody around to try to build kernel or ROM.
Device is old and under powered. Check the threads for instructions how to install back to stock Honeycomb ROM would be your best option at this point.
R.I.P. Streak 7 development

ElfinJNoty said:
Nobody is working on these anymore. The lack of source and not having an updated kernel to give us anything stable from any jb+ rom...... KK or LP would run much more efficiently on this device but nobody around to try to build kernel or ROM.
Device is old and under powered. Check the threads for instructions how to install back to stock Honeycomb ROM would be your best option at this point.
R.I.P. Streak 7 development
Click to expand...
Click to collapse
Thanks for the response.
I bought a couple of these on eBay, all with issues, for me to play around with and possibly, if I get working, to give to the kids to play with. I found another seller on eBay selling otter boxes for $5 and someone on Amazon selling ZAGG screen protectors for $.99.
I was able to boot the one stuck on Fastboot in to APX and try to run the Restore to 2.2.bat from TheManii but it keeps hanging up on various img files. I think I am going to part it out and try fixing another one with a broken charger port.
A second one was stuck on the DELL logo on boot. APG -> Restore to 2.2.bat fixed it up right away. I updated it, and now I'm playing around with CM on it.
Here's hoping I get the third one working by parting out the first. LOL

My sources are still available on github if anyone still wants to take a stab at it. Kernel needs to be brought up to at least a full generation newer (ie 2.6 -> 3.x), and thats just a starting point.

kernels not that bad and i dont think it needs updating myself

http://forum.xda-developers.com/showthread.php?t=3330564

Need help rooting Nexus 6 on 6.0.0

I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks

dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk

blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.

dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk

I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.

dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"

"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...

dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?

Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password

getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.

I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.

@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.

dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.

Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?

danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp

getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread