Database Info

So it has been a year or so

so its been a good year or so since i last played with custom roms on my touch pro 2 from sprint
and i'm ready to experiment in playing with just the titanium rom or an energy rom again
but i don't remember the step process anymore
i know my phone is still unlocked and i still have the links to the different apps and roms i was interested in
but it seems i didn't save the links to the directions i was able to clearly follow in doing this, and for some reason not finding them again
i remember there being talk about the need or no need to task 29 the phone and then flashing the rom
i'm just unclear in the process i should take the steps
i have done some reading and research on this and going to double check for any post i have been in on here and a couple other sites to make sure i didn't over look them
but any guidance or links would be a great help

allusion said:
so its been a good year or so since i last played with custom roms on my touch pro 2 from sprint
and i'm ready to experiment in playing with just the titanium rom or an energy rom again
but i don't remember the step process anymore
i know my phone is still unlocked and i still have the links to the different apps and roms i was interested in
but it seems i didn't save the links to the directions i was able to clearly follow in doing this, and for some reason not finding them again
i remember there being talk about the need or no need to task 29 the phone and then flashing the rom
i'm just unclear in the process i should take the steps
i have done some reading and research on this and going to double check for any post i have been in on here and a couple other sites to make sure i didn't over look them
but any guidance or links would be a great help
Click to expand...
Click to collapse
If you are currently running a custom rom I recommend you task29 before you flash another custom rom. Otherwise, just put it in bootloader, connect to your PC and run the RUU for the new rom. There is a nice Advanced Flashing Utility made by Barian that does task29 and can be very helpful.

thank you for the info
i have made some progress since i posted that
i remember after posting here about you once saying i would probably get more support for my sprint phone at ppcgeeks and so i post there as well, got some help and did more digging on my own
i'm back to designing my own custom rom again and will see if i can get help cooking it and getting any fine details figured out
but it looks to be a long progress and probably when i'm close to done or ready to experiment there will be no support for this phone lol
if your curious as to what i'm working on i can post a link to my first attempt at designing my own rom
i'm still using it as a bases but now that its a second run and i understand more than last time i have made some adjustments but nothing that i have posted yet since im still in the early design points of the new design

I remember your concept thread and you had some great ideas. Good Luck to you!

n00b to rooting and CWM for P3113

First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.

Please be sure and thank the person who decides to do your homework for you.
:laugh:

FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.

ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)

Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.

Flashing and Custom ROMS

Hey, everyone. So I've been trying to figure out how to put ROM's on my Rogers Samsung Infuse 4G. I apologize if this frustrates anyone, I am usually pretty adept at figuring tech things out, however I've been browsing the web and these forums for about three days now and I am so utterly confused that it's beyond frustrating. Every time I manage to find a closely related thread or question I end up with dead links or down some tangent to alternate threads which in the end leaves me with more questions and confusion about how to actually do this. There is never a definitive "do this" thread. So, I've reached the point where I had to come on here and create my own thread.
Here's what I've done to this point;
I tried to root my phone using http://forum.xda-developers.com/showthread.php?t=1197248 that thread. I don't know what happened but it somehow failed and bricked my phone. I was able to get it back up and running using the Odin Stock w/root in this thread http://forum.xda-developers.com/showthread.php?t=1193927 and that's where I sit now.
I've gathered that I need to get CWM and a modded recovery file to be able to flash with a ROM and that's where the problems begin.
I downloaded ROM manager and ES File Explorer to find and rename my recovery file, only to find there is no recovery file in my Bin folder.
From there I've read just about every thread possible and this has lead me to just be more confused, mostly because I can't find many threads pertaining to the specific model I have and I'm paranoid as hell to brick my phone by doing/installing something incompatible.
My phone is a Rogers Samsung 4G Infuse. Model SGH-I997R. Using GB 2.3.3 and I gather my baseband version is relevant as well, it's I997R UXKG3.
If someone could walk me through how on earth to sort this out, or point me in the direction of some active and actually useful threads, that would be amazing!

suits88 said:
Hey, everyone. So I've been trying to figure out how to put ROM's on my Rogers Samsung Infuse 4G. I apologize if this frustrates anyone, I am usually pretty adept at figuring tech things out, however I've been browsing the web and these forums for about three days now and I am so utterly confused that it's beyond frustrating. Every time I manage to find a closely related thread or question I end up with dead links or down some tangent to alternate threads which in the end leaves me with more questions and confusion about how to actually do this. There is never a definitive "do this" thread. So, I've reached the point where I had to come on here and create my own thread.
Here's what I've done to this point;
I tried to root my phone using http://forum.xda-developers.com/showthread.php?t=1197248 that thread. I don't know what happened but it somehow failed and bricked my phone. I was able to get it back up and running using the Odin Stock w/root in this thread http://forum.xda-developers.com/showthread.php?t=1193927 and that's where I sit now.
I've gathered that I need to get CWM and a modded recovery file to be able to flash with a ROM and that's where the problems begin.
I downloaded ROM manager and ES File Explorer to find and rename my recovery file, only to find there is no recovery file in my Bin folder.
From there I've read just about every thread possible and this has lead me to just be more confused, mostly because I can't find many threads pertaining to the specific model I have and I'm paranoid as hell to brick my phone by doing/installing something incompatible.
My phone is a Rogers Samsung 4G Infuse. Model SGH-I997R. Using GB 2.3.3 and I gather my baseband version is relevant as well, it's I997R UXKG3.
If someone could walk me through how on earth to sort this out, or point me in the direction of some active and actually useful threads, that would be amazing!
Click to expand...
Click to collapse
Click the link in my signature and read the thread you land on

suits88 said:
Hey, everyone. So I've been trying to figure out how to put ROM's on my Rogers Samsung Infuse 4G. I apologize if this frustrates anyone, I am usually pretty adept at figuring tech things out, however I've been browsing the web and these forums for about three days now and I am so utterly confused that it's beyond frustrating. Every time I manage to find a closely related thread or question I end up with dead links or down some tangent to alternate threads which in the end leaves me with more questions and confusion about how to actually do this. There is never a definitive "do this" thread. So, I've reached the point where I had to come on here and create my own thread.
Here's what I've done to this point;
I tried to root my phone using http://forum.xda-developers.com/showthread.php?t=1197248 that thread. I don't know what happened but it somehow failed and bricked my phone. I was able to get it back up and running using the Odin Stock w/root in this thread http://forum.xda-developers.com/showthread.php?t=1193927 and that's where I sit now.
I've gathered that I need to get CWM and a modded recovery file to be able to flash with a ROM and that's where the problems begin.
I downloaded ROM manager and ES File Explorer to find and rename my recovery file, only to find there is no recovery file in my Bin folder.
From there I've read just about every thread possible and this has lead me to just be more confused, mostly because I can't find many threads pertaining to the specific model I have and I'm paranoid as hell to brick my phone by doing/installing something incompatible.
My phone is a Rogers Samsung 4G Infuse. Model SGH-I997R. Using GB 2.3.3 and I gather my baseband version is relevant as well, it's I997R UXKG3.
If someone could walk me through how on earth to sort this out, or point me in the direction of some active and actually useful threads, that would be amazing!
Click to expand...
Click to collapse
it makes no difference if you are on att or rogers if you are trying to flash a custom rom.
after you flash, the only difference is the APN - needs to be set to rogers.
use any of the stock rooted packages in the dev section
use odin or heimdall
jscott30 has odin packages avail to get you the cwm you need
i had a uclb3 stock with recovery also
alternatively, you can just use one of the custom gb kernels via odin or heimdall..flash the kernel to get cwm and flash what ever you want
advice:
search and read
gl

I have the problem flashing my friend's i997r, when i do i it reboots into recovery n never goes into the actual os. Phones goes to the galaxy s cyanogenmod screen and boots into recovery each time.
Sent from my SGH-I997 using Tapatalk 4

[Q] I messed up, and I have no idea what I got myself into. (Returning to stock FW)

I decided today to read a few guides and watch some videos on how to root my HTC One M8 w/ Harman audio. So I successfully rooted it, and installed Carbon Rom. At first things went well, and to make a long story short, I would REALLY like to revert back to my original firmware. All bloatware included, I dont care. I really have no idea what I'm doing with any of this, and the internet keeps bringing me here to find solutions so I figured I would post my question. Currently I'm downloading an RUU with hopes that it will magically fix everything (file name: RUU_M8_WHL_K444_SENSE60_SPCS_MR_Sprint_WWE_Harman_3.30.654.2_R_Radio_1.08.20.0916_NV_SPCS_1.52_003_release_395175_signed_2 (1).exe)
If anyone could please just give me some sort of direction on reverting back to the normal firmware, I would be IMMENSELY appreciative.

Tried running RUU. Made it worse. Now it's stuck at the carbon boot splash. Cant even take out the battery. I have no idea what to do now, goodnight.

You might start by checking this thread: http://forum.xda-developers.com/showthread.php?t=2701376
There are instructions on how to get into recovery and download the stock firmware, based on the results returned from running certain fastboot commands.
Please keep in mind that I don't have the M8, nor have I tried the steps mentioned, so this is entirely at your own risk.
Good luck!

The struggle... (64 bit recovery porting)

I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.

finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.

lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse

The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?

finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.

Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?

As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.

Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.

What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.

finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.

jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.