I am porting CM to the ZTE Open. I have CWM recovery working for it, but when I flash my CM builds and reboot, the phone just sits at a black screen and then reboots into CWM recovery. This is my first time porting CyanogenMod to a new device, so I am probably making an obvious mistake somewhere.
My github is: https://github.com/NightlyNexus/android_device_zte_roamer2
If anyone has some time, please take a look and try to figure out what I am doing wrong. I would really appreciate it.
Thanks!
Eric_Eric_Eric said:
I am porting CM to the ZTE Open. I have CWM recovery working for it, but when I flash my CM builds and reboot, the phone just sits at a black screen and then reboots into CWM recovery. This is my first time porting CyanogenMod to a new device, so I am probably making an obvious mistake somewhere.
My github is: https://github.com/NightlyNexus/android_device_zte_roamer2
If anyone has some time, please take a look and try to figure out what I am doing wrong. I would really appreciate it.
Thanks!
Click to expand...
Click to collapse
I was wondering if you made any head way? What did you do for the recovery/fstab issue and storage space?
I would like to see CM on my ZTE Open, some questions:
- Which version of CM are you trying to build?
- Are you using stock boot.img (without init.bg.rc) or the built one?
- Are you able to get ADB working during boot or get stucks earlier?
- Could you provide your compiled files? , I could test (and explore) them..
I'm looking your gihub right now and all seems fine, maybe we can use the extract-files.sh from the B2G project (with some PATH modifications).
Thanks for your time
Eric_Eric_Eric said:
I am porting CM to the ZTE Open. I have CWM recovery working for it, but when I flash my CM builds and reboot, the phone just sits at a black screen and then reboots into CWM recovery. This is my first time porting CyanogenMod to a new device, so I am probably making an obvious mistake somewhere.
My github is: https://github.com/NightlyNexus/android_device_zte_roamer2
If anyone has some time, please take a look and try to figure out what I am doing wrong. I would really appreciate it.
Thanks!
Click to expand...
Click to collapse
Did you get it done?
So... It's works or not?
Related
I was wondering I'm looking to get into android development and I have a few questions that I was hoping someone could point me in the right direction?
I'm looking to make custom roms for the LG Phoenix P505 from scratch or use someones to learn how to? Tutorials or books or something would help, I'm not familiar with the code but I wanna learn so any help would be great, I'll be going into Computer Engineering Technology at a local college so I'm looking for a little head start in some areas.
I understand that a recovery menu or something around those guide lines is needed to use those custom roms? Is there one out for the P505 or is there a compatible one made from a previous rom?
I have the source code for the P505 its up on the LG open source website, can someone tell me what my next step would be?
url for LG Open Source: " lg.com/global/support/opensource/opensource.jsp"
I have the same phone but i cant find any support for recovery or roms! Can we get any help on that?
It would be nice, yeah... seeings how theres a fair amount of developers here,
even tellings us if someone is trying would be nice. I wouldn't mind
customizing my phone a bit more than what stock can do. So a shout
out to the developers, please let us know if anything is going on?
Or is everyone ditching this phone and going for the Thrive?
Any update on this?
I bought a Pheonix as my first android phone and would like to learn how to develop roms for it.
Unfortunately not that I know of, I haven't done any recent searching but yeah like you, the phoenix was my first phone too. Guess perhaps the devs don't wanna do anything for this phone?
Same here. There seems to be progress being made in this thread with the prepaid counterpart but this forum's pesky 10 post minimum doesn't allow me to post in that thread to glean some more information.
rom will be coming for this phone soon I'll make one. But how to you deodex a rom.
giandeli said:
rom will be coming for this phone soon I'll make one. But how to you deodex a rom.
Click to expand...
Click to collapse
you can deodex files using this kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
instructions can be found here (i believe for your scenario you only need to do steps 3 and 5 and your ready to go):
http://forum.xda-developers.com/showthread.php?t=901417
Well, considering I already subscribed to this thread, I'll keep standing by.
yea giandeli we are all here by u! but please keep us updated! but shouldnt we first work on getting a kernel though n then a rom?
Well if its a modification of the original rom, can't you still use
the standard kernel? Or does it need some modification to it first?
i think the most important thing we need for ours is overclock cuz they are a bit slow but i think we need a kernel for that.
This guy is in agreement. Still waiting for something before I up and get another phone with support.
Well, its been two weeks. Is there any progress?
well it seems there is a rom made it isnt much but it is something heres a url:
forum.xda-developers.com/showthread.php?t=1215542
Sweet. Going to check it out when I get home.
however i dont see any instructions to flash it or use it as an update,
so if you have any pointers that'd be great.
I'm in the same boat dude. I've been doing a ton of reading just haven't had the time to act on any of it.
So i have an easy way to get clockworkmod recovery on, however heres my dellema, will and At&T rom work on a rogers phone if it is not unlocked? So is it pointless then for me to install the Carlos rom for phoenix?
** as a note,
A: backups are great
B: AT&T roms on rogers stay stuck at the AT&T logo in a loop of sorts
C: so that means i guess i need help in cooking a rogers rom for my Phoenix... (any pointers/help)
For those that are willing to give it a shot, i sort of had a P500
rom working perfectly, display wise, on a P505....
This is what i did:
1. Installed ClockWorkMod for optimus one through android
market app "Rom Manager"
2. Downloaded the final release of "Devoid"
url: forum.xda-developers.com/showthread.php?t=887281
3. ***MAKE A NANDROID BACKUP***
4. Wiped data, cache, and Dalvik, as well as battery stats
5. install from sd the "devoid" rom zip
Now theres 2 possible routes here....
1. Reboot now, you get the funky cyan messed up video screen
2.... Advanced restore in CWM of your boot partition...
the second route fixed the display, but upon boot, it said the battery
was over heating... and did a shutdown... i have yet to do a boot
up with ac power only, to see if that effects it.
**If anyone can point this at some devs, this may be a possible
work around for some roms?
The rom was a Froyo 2.2 and my boot was for a rooted 2.2.2,
what implications does this have?
So yeah thought i'd post my finding and if anyone knows anything
to add onto this, i don't have 10 posts yet, so I cant put this in
the develop area
***As an update
The "Devoid" Final rom was working full on the P505 from the method above
only if it was plugged in to a power source... It gave 2 errors,
1. When it was plugged in, it said "heat sensor detected high
temps, remove battery and place in cool dry place"
2. When not plugged in, "Battery overheateing, shutting down for safety"
I hope it's almost completed so we can start flashing some ROMs
I've never built a CWM binary before (CWM integration has been done my someone else on every other device I've developed for) and it requires a full CyanogenMod source tree - mine got corrupted so I lost a few hours doing a full resync.
CWM integration is a poorly documented black art - especially on Samsung devices.
I've got something compiling now, maybe 10% chance it works. If it doesn't I won't be touching it again until sometime this week, as a friend of mine is arriving in town in about an hour to visit.
Edit: It booted, but it acted like the VolUp key was stuck (just kept looping up through the menus) and it spewed a ton of errors
Edit 2: Somehow it's treating side-to-side tilt as up/down, and I need to move recovery.fstab somewhere else...
Right now I have it compiled and not spewing errors,however:
Our accelerometer spams /dev/input/event1 with a lot of crap. CWM treats this spam as keypresses, making CWM unusable. I need to figure out how to filter out event1 keycode input to get anything workable.
This is really interesting, please keep us posted! I'm really looking forward to a good custom ROM for my Galaxy 5
Atleast we got a good kernel already :d
Im using rj kernel for sgp 5.0, and its working fine. The games who had some lags after some time playing are runing smooth so far.
Rumirand and I are close - we probably would have it if I didn't have such a busy week.
His beta has a few issues from the looks if it - but he fixed the problems I had and I think my next github push will have fixes for his.
@Entropy512 - Thanks a ton for you efforts! Really looking forward to this.
Entropy512 said:
Rumirand and I are close - we probably would have it if I didn't have such a busy week.
His beta has a few issues from the looks if it - but he fixed the problems I had and I think my next github push will have fixes for his.
Click to expand...
Click to collapse
That's the open-source philosophy.
With r7 kernel, you can do full Nandroid backup and restore (system, data, cache and dbdata). There are issues yet, but hopefully will be fixed soon.
Sorry to bump an old thread, but this thread seems relevant, and I'd like to not make another thread for just the same thing.
QUOTE: "What's the status on CWM development for 5.0?"
What device exactly is this referring to?
I'm assuming this refers to the Samsung galaxy player 5.0?
CWM, that is clockwork mod?
Would the person coding this be connected with ROM Manager?
I read someone was working on a CWM for Samsung 5.0 and they seemed to be close to an answer or something...
I was wondering if you were affiliated with ROM Manager in some way and the clockwork mod recovery and its device list...
zBusterCB87 said:
Sorry to bump an old thread, but this thread seems relevant, and I'd like to not make another thread for just the same thing.
QUOTE: "What's the status on CWM development for 5.0?"
What device exactly is this referring to?
I'm assuming this refers to the Samsung galaxy player 5.0?
CWM, that is clockwork mod?
Would the person coding this be connected with ROM Manager?
I read someone was working on a CWM for Samsung 5.0 and they seemed to be close to an answer or something...
I was wondering if you were affiliated with ROM Manager in some way and the clockwork mod recovery and its device list...
Click to expand...
Click to collapse
ClockworkMod Recovery comes from the same guy who maintains ROM Manager, but they are NOT the same thing.
CWM's source code is published, so people can port CWM without Koush's involvement. Which is what rumirand and I did - we have CWM 5.0.2.7 working on the USA and International Galaxy Player 5.0 units at this point. (You necroed an outdated thread, we've had CWM working for a while now.) For CWM on a USA version, install my kernel, for CWM on an International unit, install his.
Thanks but I'm having problems.
Entropy, I have your Kernel installed and I can boot into the CWM-based recovery but ROM Manager doesn't recognize that I have CWM installed and won't let me do anything. Does this happen to you too?
I have really been having a HELL of a time trying to do things with this since support for this device is so scarce. I couldn't find anything about Clockwork Mod for this device anywhere. I searched for hours and kept hearing people referencing the xda developers site so I decided to look here and I installed your kernel hoping it would help and it does. But ROM Manager still doesn't recognize that CWM is installed and tells me to install it and gives me a list of phones which my device is not on and doesn't let me do anything until I install a version of CWM.
So is there an official port for CWM available that ROM Manager will recognize or is there only the ports contained in your and your friends kernels??
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Two thumbs
Flashes fine and boots into recovery and can flash files as well. On aokp 35.1 for the record.
Sent from my SCH-I500 using Tapatalk
I will warn you all to use care with this, it does not play well with other recoveries and roms, and sometimes even with Odin. I used it a lot trying to test things for steve and we decided to put it on the back burner, it is cool but causes trouble sometimes. Basically, it's awesome to use and has lots of handy features (zip queue ftw) but try not to flash anything with it if you aren't near a computer that you can Odin with just in case.
Sent from my SCH-I500 using Tapatalk 2
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Thanks for the heads up. I did go ahead and flash to play around with it. You are right. There are a bug or two in there. Is there a easy way to get the reg cwm back on like Odin or flashing, or do I need to Odin back to stock first. Its no biggy, just didn't want to waste time when I get home tonight. It is very responsive and easy to navigate though and looks very promising
edit:so odin back to stock and then restore is the way to go. I still like it a lot either way.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
tonu42 said:
Reflashing AOKP glitched version should work? Unless TWRP messes with the way it handles scripting.
Click to expand...
Click to collapse
yeah it changes some boot stuff and tries to reinject itself when you flash kernels. Which is handy if you want it but if you don't it causes problems. I was able to flash a glitch kernel from twrp but then it would just keep rebooting to glitch (cwm) recovery as though I had done three finger reboot. I flashed cm7 which put me back on blue older cwm5 and after flashing it again the phone booted so then I flashed back to ics.
Sent from my SCH-I500 using Tapatalk 2
It is really a 50/50 as to which way to go, a bunch of flashing or a bunch of Odin and then restore. Time difference is not to much. Were you able to do any backups and restores with it. I didn't have time to try that out yet. I also didn't have time to check to see if the problems made the bug report or not
Sent from my SCH-I500 using Tapatalk
Things I would like tested before I include it in AOKP.
1) data wipe. You can flash the ROM again boot and if all is well go back and restore.
2) flash the ROM or Efpophis kernel and tell me what recovery you have. It should be blue or red not twrp.
If those are good I'll look into including it.
Sent from my Glitched AOKP Unicorn.
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
Stephen, I have not tried those due to time. I can tell you I tried flashing the cwm fixed for cm7 twice and I still remained on twrp. I tried once with the injection button checked and once with it unchecked. Same result but no boot loop issues at all from that or any other flashing. This recovery is a tricky one for sure. When I get more time I will try some of your requests. I have limited time at my home computer lately because of work and studying for a test for work.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Dees_Troy said:
How did you flash the CWM CM7? If you (or the zip) used flash_image, then you might need to use erase_image first. flash_image checks the first 2KB of the image against what's already in boot. If it matches then it refuses to flash. The 2KB approach works fine for "normal" Android kernels because the first 2KB contains a "unique signature" but it doesn't always work well for Samsung SGS1 kernels because they are packed differently. I've found that I sometimes had to use erase_image in order to get flash_image to work. I've thought about submitting a patch to CM to fix this issue but haven't gotten around to it yet.
TWRP has been tested on the Epic 4G here:
http://forum.xda-developers.com/showthread.php?t=1622947
And there's a zip here that should re-inject CWM. It would need to be modified slightly to work with the Fascinate, but someone could use this as a base if they wanted:
http://forum.xda-developers.com/showthread.php?t=1651012
I think most of the issues that you'll experience will be due to the "injection process". If your kernel or ROM developer already includes TWRP in their builds then you don't need to try to reinject TWRP every time and we do make it optional. The recovery itself should be pretty solid because we use the same code across all devices (except for the optional injection code) so there's nothing that's specific to the SGS1 devices. Also, for the record, because sk8 loaned me his Fascinate, I was able to add /datadata support to TWRP, so that issue gone now too.
If you do run into any issues, please let me know. It's best to PM me, submit a bug report on github, or catch me in #twrp on Freenode. With over 20 devices to support I can't frequent the threads on the forums or I won't get any coding done.
Click to expand...
Click to collapse
Looks good both issues look fixed. I'll play with it a bit more. But I think you did a great job.
Sent from my Glitched AOKP Unicorn.
I guess you have your answers. I was flashing the zip version, but I do not ha e the further details you want.
Sent from my SCH-I500 using Tapatalk
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Stephen.k.spear said:
Yeah everything looks great I made the changes needed to build it in aokp as soon as I get server access back up I'll test some builds with it in there. Great job dees looks great.
Click to expand...
Click to collapse
ill fershur test this after it gets outta alpha stage, i dont wanna screw up my phone
Okay so far I'm loving this recovery, still have more testing, but I'm insanely impressed!
~~~~There is no spoon~~~~
After serious testing on this recovery last night I have come to the following conclusions:
1 This is the ONLY recovery that will let me backup/restore my device correctly on this phone
2 USB Mount doesn't seem to work, but if I had to trade USB Mount for working backups it is NOT a hard choice.
3 This recovery is one of the simplest to use and most functional recoveries I have used on ANY phone
4 This recovery is extremely responsive, full featured and beautiful to look at with the theme I have on it. Oh yeah, did I mention you can THEME THE RECOVERY?!?! WIN!
5 Any more bacon packed in this package would cause massive coronary problems.
6 If you are scared to try it, don't be. I am using ONLY TWRP recovery from this point on. I'm sold.
So if any of you are on the edge about this recovery, take the plunge. I promise you will not regret it.
my only problem is that i cant restore my CWM backups with TWRP
ztotherad said:
my only problem is that i cant restore my CWM backups with TWRP
Click to expand...
Click to collapse
This is definitely worth starting fresh and making a new backup.
~~~~There is no spoon~~~~
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
ztotherad said:
Honestly? I used TWRP on my Acer & it was okay, but I did definitely have problems, but I'll try it
Can I go back to CWM if I don't like it?
Click to expand...
Click to collapse
I haven't tried that yet, I was waiting for the next kernel it ROM release before flashing just to see if I could get cwm back on.
~~~~There is no spoon~~~~
I lost my Nook Tablet for a while and just recently found it again. I'd like to update the recovery tool and put a new ROM on it so I'm looking for suggestions.
I had previously rooted it and installed ClockWorkMod and then it is running some version of an Android ROM. I'm looking to update the ROM to something newer so I can make use of new apps etc. Also I know newer ROMs need newer recovery tools to install. Is CWM still the go to for that?
Thanks for any help!
OMGitsShan said:
I lost my Nook Tablet for a while and just recently found it again. I'd like to update the recovery tool and put a new ROM on it so I'm looking for suggestions.
I had previously rooted it and installed ClockWorkMod and then it is running some version of an Android ROM. I'm looking to update the ROM to something newer so I can make use of new apps etc. Also I know newer ROMs need newer recovery tools to install. Is CWM still the go to for that?
Thanks for any help!
Click to expand...
Click to collapse
I'm running CM 10.2 and have been very happy with it. This excellent post by digixmax should get you on your way. It's what I used to get up and running, and yes, the recovery is CWM-based.
nmyshkin said:
I'm running CM 10.2 and have been very happy with it. This excellent post by digixmax should get you on your way. It's what I used to get up and running, and yes, the recovery is CWM-based.
Click to expand...
Click to collapse
Thanks for that! Honestly i'm not sure what is going on. I managed to get Cyanoboot on it, installed CWM 6.0.4.8, yet every single 10.1~10.2 CM ROM I get from the official directory seems to cause it to go into a weird state where the screen goes blank, then flashes white, then goes blank again and repeat etc. Eventually the tablet just restarts. I've yet to find a single ROM that I can successfully load via SD card or internal and install it through CWM. For such an old tablet, I'm surprised things are this difficult! I've spent the last few days flashing back to stock on so many occasions when things have gone wrong. I wish I could try some other ROMs that aren't on the official CM repository however most ROMs have been hosted on Goo.im and while the site works, it is so slow you aren't even sure if the file is downloading. I wish there was more custom ROMs I could try because every official CM from 10.1 to 12.1 is bricking or failing to install! I'm honestly at my wits end.
OMGitsShan said:
Thanks for that! Honestly i'm not sure what is going on. I managed to get Cyanoboot on it, installed CWM 6.0.4.8, yet every single 10.1~10.2 CM ROM I get from the official directory seems to cause it to go into a weird state where the screen goes blank, then flashes white, then goes blank again and repeat etc. Eventually the tablet just restarts. I've yet to find a single ROM that I can successfully load via SD card or internal and install it through CWM. For such an old tablet, I'm surprised things are this difficult! I've spent the last few days flashing back to stock on so many occasions when things have gone wrong. I wish I could try some other ROMs that aren't on the official CM repository however most ROMs have been hosted on Goo.im and while the site works, it is so slow you aren't even sure if the file is downloading. I wish there was more custom ROMs I could try because every official CM from 10.1 to 12.1 is bricking or failing to install! I'm honestly at my wits end.
Click to expand...
Click to collapse
I'm not skilled enough to give advice relative to your problem, but I might suggest you go for 10.0. Many people seem to think that this is the most stable of the lot, although it does seem there is something else going on with the problems you describe--maybe the SD card?
Hello all.
I used to mess around a lot with development. Just re discovered that passion. Only problem is..................Ive forgotten 90% of what I knew lol
Now I used to be able to cook a ROM with my eyes closed. But it seems all the methods I used to use or forgot arent working. Maybe missing a step?
I've seen rooted su img install for this device X10-V2-5.1-amw-TWRP_SuperSU.img so it must be possible. And an early tree build.
So what I need help with is either pulling stock base from my phone, factory image, or TWRP back up.
Ive tried XDA Android Development Suit and trying to pull to zip fails, factory image says not valid, and when trying to extract TWRP backup it fails.
Thats where Im at ATM, hoping to start adding chains one day if possible.
Well anyway
Take it easy all