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
Related
I downloaded this so called donut update and had problem with it after flashing it. It got stuck at the G1 screen. I was still able to restore all my data though... does any one know what could have goon wrong. And by the way I am trying to create a copy of the donut for cupcake and was wondering how to create a boot image(boot.img). I am also having problems with the smilocks I think that is what it is called how do u fix it?????
mohsinkhan47 said:
I downloaded this so called donut update and had problem with it after flashing it. It got stuck at the G1 screen. I was still able to restore all my data though... does any one know what could have goon wrong. And by the way I am trying to create a copy of the donut for cupcake and was wondering how to create a boot image(boot.img). I am also having problems with the smilocks I think that is what it is called how do u fix it?????
Click to expand...
Click to collapse
First and foremost, this should have been posted in the Q&A forum. This is development, not a place to fix your boot looped phone.
Now, to help you. Where did you get this update? Why were you installing it?
I would suggest booting to recovery and wiping your phone. Then reinstall the ROM that you were on and see if it will boot up after that. Or just restore your nandroid backup if you have one. If that doesn't work you may need to wipe your ext partition too. Without knowing what the update was or what was included in it, it's hard to say how much you will have to wipe to get your ROM working again. For instance, if it included a radio update you might have to reflash your radio.
I got this from droidheaven.com. sorry that I posted it in the wrong place
He said he did restore his phone and that he wanted to build a boot.img, so in a way it is devolpment since he is not at a boot loop
Yeah I wiped flashed but I didn't wipe the ext
mohsinkhan47 said:
I got this from droidheaven.com. sorry that I posted it in the wrong place
Click to expand...
Click to collapse
its not a donut update its cyanogen mod with some donut ported! droidheaven.com is a joke!
?...? Ok.... can u guys help me with the boot.img and that lock thing... I don't understand it... it's for scripts right. How do u unpack it and than repack it
mohsinkhan47 said:
?...? Ok.... can u guys help me with the boot.img and that lock thing... I don't understand it... it's for scripts right. How do u unpack it and than repack it
Click to expand...
Click to collapse
all of ur questions are already answered throughout this forum, use the search function. but to make ur troubles a bit easier. find a rom on here that is declared stable, reformat ur sdcard with the correct partitions(again everything u need to know can be found with the search function) and just reflash. if u cannot figure any of this out, throw ur g1 into the wall as hard as possible. fixed my problem.
gridlock32404 said:
He said he did restore his phone and that he wanted to build a boot.img, so in a way it is devolpment since he is not at a boot loop
Click to expand...
Click to collapse
My bad. I must have read it wrong.
mohsinkhan47 said:
?...? Ok.... can u guys help me with the boot.img and that lock thing... I don't understand it... it's for scripts right. How do u unpack it and than repack it
Click to expand...
Click to collapse
Read up some in the themes and wall paper section.
And I found this thread is helpful!
http://forum.xda-developers.com/showthread.php?t=527200
Good luck!
mohsinkhan47 said:
I downloaded this so called donut update and had problem with it after flashing it. It got stuck at the G1 screen. I was still able to restore all my data though... does any one know what could have goon wrong. And by the way I am trying to create a copy of the donut for cupcake and was wondering how to create a boot image(boot.img). I am also having problems with the smilocks I think that is what it is called how do u fix it?????
Click to expand...
Click to collapse
This belongs in the Q&A forum. Please read the stickies before posting.
MOD EDIT
Moved to Q&A forum
mohsinkhan47 said:
?...? Ok.... can u guys help me with the boot.img and that lock thing... I don't understand it... it's for scripts right. How do u unpack it and than repack it
Click to expand...
Click to collapse
You want to build a boot.img, but you don't understand it...What are you trying to do exactly?
Cyan's latest experimental ROM has a few faetures from Donut and has working Wifi, unlike that donut preview ROM, why not use that?
Drizzy Drake Rogers said:
its not a donut update its cyanogen mod with some donut ported! droidheaven.com is a joke!
Click to expand...
Click to collapse
Too right, I highly doubt they got permission to host any of those ROMs, and that fact that they release them with no information leads to people coming to xda for help.
If u open up a rom. There is a boot img.. do I need it or should I edit. What is it for
mohsinkhan47 said:
If u open up a rom. There is a boot img.. do I need it or should I edit. What is it for
Click to expand...
Click to collapse
If you don't know what it is, leave it alone.
Don't just go messing with files all willy nilly. Read through this forum and you'll find all kinds of helpful things, like what a boot.img file is for. Start messing with things like that and you'll be crashing your phone faster than I can type this (and I type fast).
Just leave your phone alone. If you feel like doing some modifications to it, just use some of the stable builds here and don't fuss with them, they are stable for a reason.
Gilliland12 said:
If you don't know what it is, leave it alone.
Don't just go messing with files all willy nilly. Read through this forum and you'll find all kinds of helpful things, like what a boot.img file is for. Start messing with things like that and you'll be crashing your phone faster than I can type this (and I type fast).
Just leave your phone alone. If you feel like doing some modifications to it, just use some of the stable builds here and don't fuss with them, they are stable for a reason.
Click to expand...
Click to collapse
Tinkering with things is how some people learn! I completely disagree with your statement.
To the OP, mess with whatever you want, just be prepared to break things if you don't know what they do. Reading and learning is part of the journey, but eventually you are going to have to start futzing with things. When you do, be prepared for failure and technical problems. I bought a spare G1 on ebay for just this purpose. If it breaks, gets bricked, or is down for a few hours, then I still have my primary phone. If you want to start tinkering seriously, then consider a spare phone.
Ok... is there an how to make a rom guide or something.... I searched I couldn't find anything
edit: I just put the zips on the sd-card and installed them from recovery. Thread said NOT to do that, but it seems to be working fine. Still interested in knowing how to do it the other way.
Hi, i have Evervolv-Perdo-2.1.0p3 and trying to upgrade to Evervolv-Perdo-2.2.0a2... not as easy as last time.
I've blackrose and the special partitioning from last time so that's all done.
The thread says to
fastboot flash system system.img
fastboot flash boot boot.img
But there's only a boot.img in the zip. There is a "system" dir though, i guess you are supposed to build it some way?
Also same with gapps, (not included in this version) a "system" dir in the archive, how to flash those?
Any tutorials on this? Didn't find anything, not here nor in the texasice-thread... Guess nobody is as noob as me
nexus1user said:
edit: I just put the zips on the sd-card and installed them from recovery. Thread said NOT to do that, but it seems to be working fine. Still interested in knowing how to do it the other way.
Hi, i have Evervolv-Perdo-2.1.0p3 and trying to upgrade to Evervolv-Perdo-2.2.0a2... not as easy as last time.
I've blackrose and the special partitioning from last time so that's all done.
The thread says to
fastboot flash system system.img
fastboot flash boot boot.img
But there's only a boot.img in the zip. There is a "system" dir though, i guess you are supposed to build it some way?
Also same with gapps, (not included in this version) a "system" dir in the archive, how to flash those?
Any tutorials on this? Didn't find anything, not here nor in the texasice-thread... Guess nobody is as noob as me
Click to expand...
Click to collapse
fastboot imgs are not added for this version i believe. You have to use the install any zip from sdcard option from recovery
Sent from my Nexus One using XDA
nexus1user said:
edit: I just put the zips on the sd-card and installed them from recovery. Thread said NOT to do that, but it seems to be working fine. Still interested in knowing how to do it the other way.
Hi, i have Evervolv-Perdo-2.1.0p3 and trying to upgrade to Evervolv-Perdo-2.2.0a2... not as easy as last time.
I've blackrose and the special partitioning from last time so that's all done.
The thread says to
fastboot flash system system.img
fastboot flash boot boot.img
But there's only a boot.img in the zip. There is a "system" dir though, i guess you are supposed to build it some way?
Also same with gapps, (not included in this version) a "system" dir in the archive, how to flash those?
Any tutorials on this? Didn't find anything, not here nor in the texasice-thread... Guess nobody is as noob as me
Click to expand...
Click to collapse
your best bet is to ask the MASTER himself i did what you did myself too but realized it's stupid as i get FC all the time just do your BEST to fallow the instructions not everyone on XDA is a noob hater most are ungrateful bastards lmfao gotta love that ending on that sign up video heres the link lol http://www.youtube.com/watch?v=JmvCpR45LKA
i'm still a NOOB ^_^ joined 2 months ago
juliusedward, the does say not to do it though so i dunno...
Jay_Rulen, that sounds sucky... Mine has been going for 24h with a hitch though, so knock on wood. I hope it continues like that otherwise i guess i'll be back here Thanks to you both.
nexus1user said:
juliusedward, the does say not to do it though so i dunno...
Jay_Rulen, that sounds sucky... Mine has been going for 24h with a hitch though, so knock on wood. I hope it continues like that otherwise i guess i'll be back here Thanks to you both.
Click to expand...
Click to collapse
Glad to help bro ^_^
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
The One remix has S-off and root now thanks to the sunshine team. how hard would it be to get cyanogen mod onto this device?
Fullmetal99012 said:
The One remix has S-off and root now thanks to the sunshine team. how hard would it be to get cyanogen mod onto this device?
Click to expand...
Click to collapse
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
csoulr666 said:
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
Click to expand...
Click to collapse
I'm also curious about this too, but I am not in a position to flash the current build right now...
Somewhat off topic, is there something I have to do to the stock firmware to get root to stick after running Sunshine? Flashing the zip in twrp doesn't work...
Txjacob said:
I'm also curious about this too, but I am not in a position to flash the current build right now...
Somewhat off topic, is there something I have to do to the stock firmware to get root to stick after running Sunshine? Flashing the zip in twrp doesn't work...
Click to expand...
Click to collapse
I used SUInstaller from the same guys who do sunshine. worked fine for me.
How did you get TWRP installed? I can't seem to get it to work.
As for installing the current build, not really sure I want to do that, since I don't have a backup phone to use right now.
I had to use a different TWRP from the official website for the HTC One Remix. I can't seem to get SU installed... The package from the Sunshines guys just reboots my phone and doesn't do anything, while flashing through TWRP has no errors, but doesn't do anything either...
This is where I got TWRP:
http://twrp.me/devices/htconeremix.html
Txjacob said:
I had to use a different TWRP from the official website for the HTC One Remix. I can't seem to get SU installed... The package from the Sunshines guys just reboots my phone and doesn't do anything, while flashing through TWRP has no errors, but doesn't do anything either...
This is where I got TWRP:
http://twrp.me/devices/htconeremix.html
Click to expand...
Click to collapse
That's where I looked too. did you do the fastboot install? I'm trying the app from the store, but it doesn't list the device.
also, interesting. the SUInstaller worked on mine, but it is hit and miss. not sure how to root it otherwise.
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Txjacob said:
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Click to expand...
Click to collapse
glad to hear!
ill have to do the fastboot TWRP when I get home.
not sure what is needed for the One Remix to get CM12 support. HTC has the kernel source for the M7 and M8 online(and even the one Max), but not the remix.
It doesn't seem like a whole lot should be done. The hardware ought to be very similar to the HTC One Mini 2, just has to be adjusted for CDMA rather then GSM.
I tried to flash the current CM 12 build, but TWRP complains about the code-names not matching, and the update script failed. I then had to restore from a backup to get it to boot up to the original firmware.
csoulr666 said:
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
Click to expand...
Click to collapse
Could everyone please stop suggesting One Remix owners try flashing One Mini 2 stuff? It's not gonna work. Ever.
While they probably share >90% of the same features, they're not the same device.
One Remix won't be getting CM builds until someone starts working on it. Given that CM has a policy of not maintaining devices you don't own, it's not gonna be me.
u-ra said:
Could everyone please stop suggesting One Remix owners try flashing One Mini 2 stuff? It's not gonna work. Ever.
While they probably share >90% of the same features, they're not the same device.
One Remix won't be getting CM builds until someone starts working on it. Given that CM has a policy of not maintaining devices you don't own, it's not gonna be me.
Click to expand...
Click to collapse
what is needed to work on a build? I would be interested, but not sure If i need kernel source or device specific drivers. neither of which HTC dev supplies for the One Remix.
It doesn't appear to be much. I've been digging through the CM Porting Guide, and specs on the phones and they appear pretty similar. They both have the same SoC (Qualcomm Snapdragon 400) and GPU (Adreno 305), but the Remix has 1.5GB RAM instead of 1GB. Haven't had a chance to compare the partition schemes, but Verizon might have made them different... Some things need to be changed in the source of the Mini 2 to make it compatible, but the Kernel should be fine.
What about the Radios? does the difference in Radio CDMA vs GSM change anything major. I'll take a look at the porting guide and see if I can get something booted.
https://github.com/kfechter/android_device_htc_memwl
I forked the memul build of CM and renamed it. any help in grabbing stuff from the Remix would be great (kernels, drivers, recovery images)
One more update.
I've asked HTC for kernel source for the one remix. hopefully HTCDev actually comes through and provides it. hopefully also for Lollipop.
I don't think there is a separate kernel source for the Remix. On the cyanogen wiki for the HTC One Mini 2, they are just using the kernel source for the M8. That should work fine for the Remix also.
Txjacob said:
I don't think there is a separate kernel source for the Remix. On the cyanogen wiki for the HTC One Mini 2, they are just using the kernel source for the M8. That should work fine for the Remix also.
Click to expand...
Click to collapse
I did see that. I've been editing the build files and device information that I forked from the one mini 2 device repo. I've been having issues with the repo sync for actual cyanogenmod though(my repo is just the specific device properties). I'll work on it when I can, but I'm also working on intelligent vision stuff and schoolwork.
Also, Need to figure out what to change to get the CDMA radio support, and need to grab the partition tables from my device.
Is there somewhere I would be able to restore the stock rom from in case something goes horribly wrong?
Txjacob said:
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Click to expand...
Click to collapse
How do you install the twrp img file from fastboot? I've rooted my remix and am with you guys in the search for a Rom or help building one. Just need to get a recovery installed. Have SuperSU installed as well, thanks
Fullmetal99012 said:
I did see that. I've been editing the build files and device information that I forked from the one mini 2 device repo. I've been having issues with the repo sync for actual cyanogenmod though(my repo is just the specific device properties). I'll work on it when I can, but I'm also working on intelligent vision stuff and schoolwork.
Also, Need to figure out what to change to get the CDMA radio support, and need to grab the partition tables from my device.
Is there somewhere I would be able to restore the stock rom from in case something goes horribly wrong?
Click to expand...
Click to collapse
Yes, in TWRP you can make a backup of your current partitions (It just dumps the current partition to IMG files), then if you have a problem you can just restore back from those files.
neuclear said:
How do you install the twrp img file from fastboot? I've rooted my remix and am with you guys in the search for a Rom or help building one. Just need to get a recovery installed. Have SuperSU installed as well, thanks
Click to expand...
Click to collapse
First, download the TWRP build from the TWRP website, the one in this forum is for the Mini 2 and won't work with the Remix. Then boot your phone into fastboot mode and run "fastboot flash recovery twrp.img" on your computer. Then reboot, and after when you select recovery from the bootloader it should open TWRP.
When I boot into fastboot usb, i enter the command to flash recovery and it says error cannot load twrp.img BUT when i type the same command but add USB after fastboot it loads the commands list. Still cant get it to load. The file name in the Android-adb file is twrp.img as well. Ive done everything correct as far as I know. Any input would be appreciated. thanks.
---------- Post added at 08:06 AM ---------- Previous post was at 07:55 AM ----------
I figured it out.
Went into file Android-adb and did shift right click open command window here. typed the command and it worked on the first try. now its time to develop a rom and make this phone worth something!
Hello! So, I've tried creating a device tree for the Leon LTE (H340n) based on ms345, and after some changes I've compiled TWRP for this specific model, with it identifying as c50n, which should allow for custom ROMs(I'm building LineageOS 13 right now, but don't get your hopes up) Also, there's a way to flash TWRP and get root on 6.0, here's a guide (https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25) and you can flash my recovery instead.
Link: https://www.androidfilehost.com/?fid=961840155545578919
Sources: https://github.com/dadziokPL/android_.repo_local_manifests
Also, this recovery wouldn't work if it wasn't for Charles-IV's help on Github, a huuuuge thanks to him!
dadziokPL said:
Hello! So, I've tried creating a device tree for the Leon LTE (H340n) based on ms345, and after some changes I've compiled TWRP for this specific model, with it identifying as c50n, which should allow for custom ROMs(I'm building LineageOS 13 right now, but don't get your hopes up) Also, there's a way to flash TWRP and get root on 6.0, here's a guide (https://forum.xda-developers.com/showpost.php?p=72501544&postcount=25) and you can flash my recovery instead.
Link: https://www.androidfilehost.com/?fid=961840155545578919
Sources: https://github.com/dadziokPL/android_.repo_local_manifests
Also, this recovery wouldn't work if it wasn't for Charles-IV's help on Github, a huuuuge thanks to him!
Click to expand...
Click to collapse
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
jazzdglass said:
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
Click to expand...
Click to collapse
the official twrp one is for all c50 devices, but this one is specifically for the c50n, but im not sure how much of a difference it makes.
You can find out if yours is c50n or not in about phone.
Strange thing is its twrp 3.0.2 , and i cant find anything about this on the internet
Charles IV said:
the official twrp one is for all c50 devices, but this one is specifically for the c50n, but im not sure how much of a difference it makes.
You can find out if yours is c50n or not in about phone.
Strange thing is its twrp 3.0.2 , and i cant find anything about this on the internet
Click to expand...
Click to collapse
The difference is that the c50n did not have a device tree, there was no way to build custom ROMs, so I started working on a tree, and TWRP now compiles with it. It also identifies as c50n inside the recovery when checking compatibility with a ROM, so if I ever manage to get Lineage working, it will flash properly, being meant for THIS specific phone, the LG Leon 4G LTE aka H340n aka C50n. Previous TWRP was for all LG Leons, built on a common tree. With a specific tree, it allows for specific fixes for this device if needed in the future. The version is older since I used TWRP android6.0 branch, I could build an updated version, but right now I'm taking a break.
jazzdglass said:
Hi? The metro pcs version is what model? C50n? Also I found anoth4r version of twrp on 5he site twrp.me.. I saw twrp-3.1.1-0-c50.img... Is this appropriate? I hav the metro version and I'm confused what to use
Click to expand...
Click to collapse
MetroPCS is ms345, I just needed a base for C50n, the international LG Leon 4G LTE. The devices are similiar, so I thought I could use the existing ms345 tree to create a tree for the C50n. I don't know if there is a specific TWRP for the ms345, if there is, you should find it and use it. If not, the C50 from twrp.me should work. Also, my recovery for C50n should work too, just try flashing, if some **** goes sideways, just flash another one and try again. The difference is basically what TWRP thinks your device is, and if you flash a ROM for ms345 it would expect your recovery to be for ms345, and not anything else. Get it?
Hey, I'm from Brazil and I own a H342 model of this cellphone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build, but I know that even if the processor is the same for both devices the baseband will still differ.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
mateus.sc said:
Hey, I'm from Brazil and I own a H342 model of this cellphone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build, but I know that even if the processor is the same for both devices the baseband will still differ.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
Click to expand...
Click to collapse
Sorry about the lateness, but don't do it.
The baseband was built with code specifically for lollipop, flashing it on top of marshmallow will most likely lead to incompatibility.
What about LineageOS?
rusiu559 said:
What about LineageOS?
Click to expand...
Click to collapse
Any news ?
rusiu559 said:
Any news ?
Click to expand...
Click to collapse
None other than it might take a long time. @dadziokPL has a lead on what the current error is though.
Charles IV said:
None other than it might take a long time. @dadziokPL has a lead on what the current error is though.
Click to expand...
Click to collapse
It's all going so terribly wrong tho. I've managed to get it to compile, but it does not boot. Goes to "AP Watchdog bark" green screen, so probably can't even boot into the Linux kernel, since if it did we'd get some boot animation and logcats. I'm totally stuck.
Also, the recovery does not boot anymore, I'm gonna revert some commits up until you merged all the common trees, modular approach is much better
dadziokPL said:
It's all going so terribly wrong tho. I've managed to get it to compile, but it does not boot. Goes to "AP Watchdog bark" green screen, so probably can't even boot into the Linux kernel, since if it did we'd get some boot animation and logcats. I'm totally stuck.
Also, the recovery does not boot anymore, I'm gonna revert some commits up until you merged all the common trees, modular approach is much better
Click to expand...
Click to collapse
Yes, I was worried that I might break something with the merging, but we can re-merge when everything's working to see if it does break things.
The kernel might need to be modified - all I did is went onto lg leon's source code site and downloaded the H340N one. It contained two zips, one with the kernel in, and one supposedly with the rest in, but it was really messed up and I couldn't get it working.
I'll build the kernel in that tree using their instructions (not sure what I'll get!) and we'll see if we can use that as a prebuilt kernel.
Is your bootloader definitely unlocked? I remember getting a greenscreen when I was messing about with the partitions, trying to put the recovery on it etc.
Charles IV said:
Yes, I was worried that I might break something with the merging, but we can re-merge when everything's working to see if it does break things.
The kernel might need to be modified - all I did is went onto lg leon's source code site and downloaded the H340N one. It contained two zips, one with the kernel in, and one supposedly with the rest in, but it was really messed up and I couldn't get it working.
I'll build the kernel in that tree using their instructions (not sure what I'll get!) and we'll see if we can use that as a prebuilt kernel.
Is your bootloader definitely unlocked? I remember getting a greenscreen when I was messing about with the partitions, trying to put the recovery on it etc.
Click to expand...
Click to collapse
Yeah, the bootloader's got to be unlocked since old TWRP boots fine
dadziokPL said:
Yeah, the bootloader's got to be unlocked since old TWRP boots fine
Click to expand...
Click to collapse
I'm trying to figure out a way of how to unmerge, and restore the combined branch it was on - i spent so long on that! -_-
To me it looks like the error is to do with the bootloader rejecting it. Could it me something to do with the system.prop. Fingerprints, maybe?
Charles IV said:
I'm trying to figure out a way of how to unmerge, and restore the combined branch it was on - i spent so long on that! -_-
To me it looks like the error is to do with the bootloader rejecting it. Could it me something to do with the system.prop. Fingerprints, maybe?
Click to expand...
Click to collapse
I have completely no idea what the problem is. I'm gonna hard reset the repo to the last commit before the merge, but we'll lose all commit history after the merge. We'll have to start over from before you merged it all. Why'd you even do it? It was totally fine being modular
dadziokPL said:
I have completely no idea what the problem is. I'm gonna hard reset the repo to the last commit before the merge, but we'll lose all commit history after the merge. We'll have to start over from before you merged it all. Why'd you even do it? It was totally fine being modular
Click to expand...
Click to collapse
Well I'm used to a single device repo, so I tried merging it, to see if it worked. Personally I didn't like having 3 repos to look at, but three of each file is also hard!
Tbh I was surprised when you pulled it, I just did it as an experiment.
Charles IV said:
Well I'm used to a single device repo, so I tried merging it, to see if it worked. Personally I didn't like having 3 repos to look at, but three of each file is also hard!
Tbh I was surprised when you pulled it, I just did it as an experiment.
Click to expand...
Click to collapse
I thought maybe you did something important with the merge and just pulled it, but it seems like it broke it. Anyway, now I know how to revert commits, so I'll be building the recovery, and if it does not work, I'll just revert one commit back and gradually figure out at what point it broke.
dadziokPL said:
I thought maybe you did something important with the merge and just pulled it, but it seems like it broke it. Anyway, now I know how to revert commits, so I'll be building the recovery, and if it does not work, I'll just revert one commit back and gradually figure out at what point it broke.
Click to expand...
Click to collapse
When you've got recovery working, if booting still doesn't work, let me know, I've noticed a minor difference in fingerprints and build description (the same difference) in my build.prop compared to the build prop overrides. It is probably because they are different builds, and shouldn't make a difference, but if it's not working, I'll try it.
On a side note - if we change the overrides, in theory, with suhide, it should pass safetynet!
Charles IV said:
When you've got recovery working, if booting still doesn't work, let me know, I've noticed a minor difference in fingerprints and build description (the same difference) in my build.prop compared to the build prop overrides. It is probably because they are different builds, and shouldn't make a difference, but if it's not working, I'll try it.
On a side note - if we change the overrides, in theory, with suhide, it should pass safetynet!
Click to expand...
Click to collapse
Okay, so the merge must have screwed something up, since recovery works perfect now! I'll be back to building now. Also, I'm not building Lineage anymore, I switched over to RessurectionRemix, it's totally awesome.
Edit: You know what. I'm actually going to build the kernel itself for now and see if it works, since I'm on a CM12.1 ROM for ms345, it works but is quite bugged. I'll do an experiment and try to flash the kernel I'll build. Probably won't work, but I'll see what will happen
Edit 2: Okay, green screen again, I'll try to build the full ROM again, if that happens again, that is bad news, since I have no idea how to fix this thing.
Just another edit: I have an idea. I just downloaded the Qualcomm QPST tool, I might be able to debug this. No promises tho, we'll see.
dadziokPL said:
Okay, so the merge must have screwed something up, since recovery works perfect now! I'll be back to building now. Also, I'm not building Lineage anymore, I switched over to RessurectionRemix, it's totally awesome.
Edit: You know what. I'm actually going to build the kernel itself for now and see if it works, since I'm on a CM12.1 ROM for ms345, it works but is quite bugged. I'll do an experiment and try to flash the kernel I'll build. Probably won't work, but I'll see what will happen
Edit 2: Okay, green screen again, I'll try to build the full ROM again, if that happens again, that is bad news, since I have no idea how to fix this thing.
Just another edit: I have an idea. I just downloaded the Qualcomm QPST tool, I might be able to debug this. No promises tho, we'll see.
Click to expand...
Click to collapse
The kernel is probably originally for aosp 6.0.
Personally I think Lineage is better, but then I've never personally used RR.
I'll also make the fingerprint commits.
edit: trying to figure out how to only make a pr of one commit to your tree.