Just curious if anyone was going to try and build 3.5.2 for sunfish? I'd have to get a build environment set back up and if someone is working on it, I'll just wait. I never like releasing files as I am not feeling competent enough to risk bricking YOUR device.
I don't think anyone is working on it.
But if you do pick it up, it would be greatly appreciated if you could create a version for Android 10
Related
I have had a rooted G1 for a while. With the news of Android 1.5 SDK I thought that I would have my hand at building Cupcake and intalling it. Well it didn't work.
So what I have now is a G1 with a serial0 screen that has the skateboarders on it and a recovery screen running test keys.
I have been able to update the recovery screen with different images and they all seem to work. I do get errors about files not being signed though, so I'm not sure where to go with that.
What I have been trying to do is the the DREAIMG.nbh to work. I though that it would be best if I just started over, punishment or not, I don't have a working phone right now. I was trying to follow directions here http://forum.xda-developers.com/showthread.php?t=442480. I would like to say that I'm on Linux and mkdosfs -F 32 /dev/sdc1 doesn't seem to be doing the same formating as a Microsoft box. Anyone had luck with this?
So I don't really know where to go from here. I'm currently downloading the latest source for Android, and not Cupcake. I thought that I would give that a shot.
If anyone could offer me any help it would be great. I'm tired of looking at a G1 screen.
I also think that I need to get back to the rainbow Serial0 screen. I don't even know when I did that change, so I am going to to searching for a way to undo everything so that I can redo it again. Please let me know if you can offer any help.
Got it working. I had an update.zip on an old sdcard. It is the 1.43 version. I don't know why it worked and other ones didn't. It is lat though and I'm going to bed.
I want to try to port AOSP to my Samsung Infuse, but I need a little help. I heard that in order to port ROMs like this, you basically start by getting the source, building it, then putting it on your phone. Then try to boot into it and see what's broken and fix it(I realize fixing what's broken is going to be where majority of the work will be at.).
I downloaded the source to AOSP from Google and was able to build it, then I tried putting it on my phone but I'm unable to boot into it. How do you figure out why it won't boot? I tried running logcat on my computer when booting but it just says waiting for device and nothing else ever comes up.
Any help regarding helping me get it booting or any other general porting advice would be greatly appreciated!
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
SedentaryDev said:
Using CM11 has been a disaster. Processes keep shutting down, the phone spontaneously restarts, and features seize up until I restart. I didn't upgrade it myself, so I don't know much about this process. I'd appreciate it if someone could help me get back to CM10. This phone is not officially supported, so I'm guessing that's why the guys at the CM forum haven't responded.
I have a Huawei Ascend Y300-151 with Android 4.4.4.
Of course, if someone thinks that my phone should work fine with CM11, and can suggest how to make that happen, that'd be just fine, too.
Click to expand...
Click to collapse
did you installed cm from here http://getcm.thebronasium.com/?device=u8833?
303
I didn't install it at all. This is just how I got the phone. I can tell you that it's CyanogenMod version 11-20141114-NIGHTLY-u8833
That could be the problem. You never know what the previous owner did or what they flashed could be a bad download, the wrong firmware, etc. Best to get back to stock and start over so you know exactly what has been done.
Hmm... probably. Right now going back to the stock ROM would be an improvement. Could I get some help with that, then? I haven't been able to find clear steps to do that with my specific phone, and when I went to Huawei's web site, I couldn't find the ROM for the Y300-151 and wasn't confident the Y300-100 was suitable.
I've used CM11, but I'm not familiar with that phone, so unfortunately I can't help with that specifically. There should be plenty of help on XDA. Just search for that specific model. Sometimes it takes a while to find what you need, but I'm sure its there. If it's done right CM11 has never let me down.
I'm sure CM11 works fine for most people, but my instincts tell me that my phone is underpowered for it. Ok, I'll look elsewhere or start a new thread about getting back to the factory ROM.
Yes, first thing to do is get back to stock. But don't give up on CM11. It should work fine on underpowered phones. It's just a slightly modified version of vanilla android which is a fairly light ROM.
I hope you figure it out.
Good luck!
If what you say is true, then I expect I'll be right back here again. I doubt that the wrong binary was used--I dunno, maybe something was wrong w/the installation procedure, but I'm sure the right binary was downloaded. In which case, maybe I should be attacking these problems directly, since I'm having trouble getting support for installing the factory ROM.
Is anybody trying to root this phone? I just bought this phone to learn android development and up my skills in it. I currently don't have that much experience that I can root a device myself, but I would like to learn.
Anyways, Please let us know if you are developing a way to root the device. I would be happy to help in every possible way I could.
It shouldn't be hard to port my surnia (2015 Moto E LTE) TWRP recovery to this device (osprey). Just change the device name to osprey and update the resolution in BoardConfig.mk
See my device tree for it:
https://github.com/sultanqasim/android_device_motorola_surnia/tree/twrp
I can make a build of my recovery with these minor modifications if you're willing to try it out. I can't promise it will work and not mess up your device, since I don't have it to test on.
I will give it a try since we have factory images now.
Working on it:
https://github.com/sultanqasim/android_device_motorola_osprey
----------------------------------------
Test build is up:
http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github
THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.
*deleted*
sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?