Database Info

[Q]Flashing roms help

I have a stock Infuse 4g from AT&T and I would like a step by step, like a tutorial of everything I have to do for flashing custom roms, what to backup, installing CWM, etc. Thanks.

http://forum.xda-developers.com/showthread.php?t=1514886
[REF] Super Infuse Noobie Question Thread. Lots of questions answered
Sent from my SAMSUNG-SGH-I997 using xda premium

Yes, I know about that thread, but they don't answer all of my questions, like for example: I have stock GB, do I still root with super one click? What is the first step in flashing custom roms, rooting and then installing CWM? How do I install CWM? What to use to backup apps? What is Rom manager from the android market and what is it for, is it useful? How to backup contacts? Before flashing, should I remove the sim card? When flashing, is it always done in CWM? If so, what's the exact process?
What I want is more of a fool proof step by step, just to make sure everything goes as smoothly as possible. I had to use Heimdall's one click back to stock to go from froyo to GB UCKJ4 because of the boot loop even though the phone wasn't rooted or anything, it was stock. If I did that, what are my options? What should I do if I want to flash custom roms from scratch? Also, CWM is kept even after a factory reset or a wipe? it doesn't get deleted in any way when you want ti flash another Rom?

Wow, I'm sorry but you should do some research first before you ask these questions. Google has an excellent feature called search. I'm sure if you use it you can find your answers as they have all been asked before. Everything I have learned has been from reading and rereading everything I could before I attempted rooting. Android central has a great guide to everything root. Then come back with questions. Sorry to go off but it seems like people just come here to have their hand held. I'm sure you could find someone to donate to on here that would take you by the hand if that's the route you choose.
Sent from my ADR6425LVW using XDA App

Silvares said:
I have a stock Infuse 4g from AT&T and I would like a step by step, like a tutorial of everything I have to do for flashing custom roms, what to backup, installing CWM, etc. Thanks.
Click to expand...
Click to collapse
Hmm. So how much are you willing to pay for someone who takes time to consolidate this guide. Make it worthwhile for us too

Do I get dibs on this?

qkster said:
Do I get dibs on this?
Click to expand...
Click to collapse
Lol... you may... I only asked that so maybe he would find someone to spoon feed him

diablo009 said:
Lol... you may... I only asked that so maybe he would find someone to spoon feed him
Click to expand...
Click to collapse
lol..somewhere in this thread is the spoon...just have to know where to look.

"There is no spoon."
Sent from my Transformer TF101 using Tapatalk

rxnelson said:
"There is no spoon."
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
He was referring to the link in post 2 by bigjoe.

diablo009 said:
He was referring to the link in post 2 by bigjoe.
Click to expand...
Click to collapse
Yea, I was just goofing. Qksters bald avatar and all the spoon talk reminded me of the matrix....thought someone would get it. Ah well.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Anyway, thanks qkster, with your Heimdall to UCBL3 and CWM installation I was able to do it. And now I have ZEUS on my Infuse :3.
Now, what are some must have apps rooted or not?

Silvares said:
Anyway, thanks qkster, with your Heimdall to UCBL3 and CWM installation I was able to do it. And now I have ZEUS on my Infuse :3.
Click to expand...
Click to collapse
good job..
See how easy it was?
Anyway, lol..the spoon was on all my signature links

Let me just throw this out there: as a noob myself, I understand where op is coming from. On forums this large, it is easy to get lost. I also find that I spend so much time reading things that don't answer my questions. I know that's part of the process though, but can feel pretty overwhelming.
May I suggest that not just 1 person has to answer all the questions. Maybe u come across a post like this and answer just 1 or 2 questions, or paste in a link or 2 to where the specific question is answered.
Also, I know that I've asked a question in the most appropriate place & someone has come back saying it's not the right place, even though it's in the q&a - noob - device forum. It's just hard at first. So, pls, don't bust op's chops too bad, b/c somewhere on here it says that it helps everyone if anyone takes some of their time to educate.
Sent from my SAMSUNG-SGH-I997 using XDA
---------- Post added at 03:55 PM ---------- Previous post was at 03:08 PM ----------
Noob here too, but I have done some of this successfully, and then I played around too much and really, really bricked my phone - but fixed it, so I have learned a bit. These are my thoughts:
Silvares said:
I have stock GB, do I still root with super one click?
Click to expand...
Click to collapse
Yes. Get rooted. I've used S-O-C twice. Had to play around with it first. I think I ended up being successful by doing it thru my phone, not on the PC.
Silvares said:
What is the first step in flashing custom roms, rooting and then installing CWM? How do I install CWM?
What to use to backup apps? How to backup contacts?
Click to expand...
Click to collapse
1st step - root, then - backup more than just 1 way-use some from market and put things in more than 1 place; Titanium Backup seems to be standard around here too. Here is a great youtube link that helped me a lot to prepare: http://youtu.be/ozNVeGPUlU8
Silvares said:
What I want is more of a fool proof step by step, just to make sure everything goes as smoothly as possible.
Click to expand...
Click to collapse
Doesn't exist. Try to find a good youtube and follow along.
Silvares said:
I had to use Heimdall's one click back to stock to go from froyo to GB UCKJ4 because of the boot loop even though the phone wasn't rooted or anything, it was stock. If I did that, what are my options?
Click to expand...
Click to collapse
When I got bricked last night, after trying 2 methods and much freaking out, GTG worked. Working link for that download is here: http://www.mediafire.com/?i57410xodydx5l1. Thread here → http://forum.xda-developers.com/showthread.php?t=1116251
Silvares said:
Also, CWM is kept even after a factory reset or a wipe? it doesn't get deleted in any way when you want ti flash another Rom?
Click to expand...
Click to collapse
It stayed for me, even through brick.
I know you got your questions answered, but maybe this will help you, or someone else, in the future. Again, I'm no expert - far from it - but this is what worked for me. Good luck!

Can't think of another way of saying this...HELP!
So, I was able to get 3e and clockworkmod recovery installed on my Infuse. (A great accomplishment for me, trust me)
I went through the process of wiping data and caches to install my new ROM but I put the two zips (Cyan7 & Google Apps) on the external sdcard so when I went to install them I couldn't see them. I thought my only option then was to chose to restore from backup in CM recovery and now I'm stuck on the Samsung boot logo.
I tried a battery pull and VOLup/VOLdwn/POWER to try to get into recovery but I'm still stuck on the boot logo. What can I do now?
I'd really appreciate your help. Cheers.

feroxcvpiditas said:
So, I was able to get 3e and clockworkmod recovery installed on my Infuse. (A great accomplishment for me, trust me)
I went through the process of wiping data and caches to install my new ROM but I put the two zips (Cyan7 & Google Apps) on the external sdcard so when I went to install them I couldn't see them. I thought my only option then was to chose to restore from backup in CM recovery and now I'm stuck on the Samsung boot logo.
I tried a battery pull and VOLup/VOLdwn/POWER to try to get into recovery but I'm still stuck on the boot logo. What can I do now?
I'd really appreciate your help. Cheers.
Click to expand...
Click to collapse
No need to recover. Simple enough. U've tried restarting normal, and it didn't work?

No unfortunately...
I'm stuck on the Samsung boot logo. I think my battery pull after being frozen after the restore didn't help matters. I've tried vol+/vol-/power and vol-/power and still can't get into recovery. Plugged into my MAC it's not recognized.

feroxcvpiditas said:
I'm stuck on the Samsung boot logo. I think my battery pull after being frozen after the restore didn't help matters. I've tried vol+/vol-/power and vol-/power and still can't get into recovery. Plugged into my MAC it's not recognized.
Click to expand...
Click to collapse
Well, if it were me, I'd pull batt and let it sit while I search this site to see what other people have done when stuck in the loop. You're sure to find answers somewhere in/related to being bricked threads, though I'm sure you're not bricked, so relax and take a breath. I'd offer other suggestions, but I'm too new, so it'd just be speculation on my part.

dde333 said:
Well, if it were me, I'd pull batt and let it sit while I search this site to see what other people have done when stuck in the loop. You're sure to find answers somewhere in/related to being bricked threads, though I'm sure you're not bricked, so relax and take a breath. I'd offer other suggestions, but I'm too new, so it'd just be speculation on my part.
Click to expand...
Click to collapse
Cheers, I think I will do that. I'm feverishly scouring the site and the interweb...I just hope I don't have to re-flash a stock ROM and start all over again. Of course that would be better than having a paperweight I suppose.
---------- Post added at 07:56 PM ---------- Previous post was at 07:46 PM ----------
Well, I got into Download mode using the vol+/vol- then usb plugin. Just don't know what to do next. At least something is happening...back to my research...

feroxcvpiditas said:
Cheers, I think I will do that. I'm feverishly scouring the site and the interweb...I just hope I don't have to re-flash a stock ROM and start all over again. Of course that would be better than having a paperweight I suppose.
---------- Post added at 07:56 PM ---------- Previous post was at 07:46 PM ----------
Well, I got into Download mode using the vol+/vol- then usb plugin. Just don't know what to do next. At least something is happening...back to my research...
Click to expand...
Click to collapse
fero,
you dont need to look very far...
http://forum.xda-developers.com/showthread.php?t=1524081
the link to unbrick and how to has always been right on my signature links...
read my beginner guide...

How do we get a true CWM recovery, an not just a boot hack

Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.

jimbridgman said:
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
Click to expand...
Click to collapse
a few things.
1. it was not anything you did that made me wipe recovery, it was just me being a complete idiot
2. basically I think we need to figure out how to modify what you cat'd over. then we can pull an image from a similar device that has a true cwm recovery and edit what we need to like the specific partitions in order for it to work on our phone. then we can just cat it over and bingo! working full cwm.
3. why is it that stupid things I do always end up leading to great discoveries on here. this is like the 3rd time it has happened.
so any ideas on how to mount that file in a way we can actually look at it.
---------- Post added at 09:39 PM ---------- Previous post was at 09:22 PM ----------
Some more stuff I found: http://www.clockworkmod.com/rommanager
That has official cwm recovery builds for all supported devices. many have images, I think all the ones with unlocked bootloaders. those images would be flashed with fastboot, or probably could be cat'd over like we did.
others have flashable zips (all the moto devices) and i think those are all the ones with lockked bootloaders. I don't have tie to dig into what they really do right now, but i appears that they just copy some files for recovery to /etc and other places suggesting those devices have a different recovery method
I still think the biggest priority is figuring out how to see the contents of the images with our recovery stuff and those for other devices.

I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!

JRW 28 said:
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
Click to expand...
Click to collapse
what is BP tools even
Sent from my MB865 using xda premium

lkrasner said:
what is BP tools even
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've wondered the same thing????

JRW 28 said:
I've wondered the same thing????
Click to expand...
Click to collapse
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too

lkrasner said:
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
Click to expand...
Click to collapse
Yea but even on a normal boot I could never get past the red moto screen, tried several times hopi g to get into CWM and not have to RSD back.
Just wierd that normal boot wouldn't work but BP tools did?

The only difference I could see is an app called CQATest in the drawer. Has many different tests available. About 50+
Sent from my MB865 using xda premium

made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.

So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff

lkrasner said:
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
Click to expand...
Click to collapse
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl

lkrasner said:
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
Click to expand...
Click to collapse
I suspected that might be the case.

jimbridgman said:
I suspected that might be the case.
Click to expand...
Click to collapse
any ideas why.
Sent from my MB865 using xda premium

jimbridgman said:
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
Click to expand...
Click to collapse
mine gave me a ramdisk.cpio.gz and a kernel.gz, I didn't extract that. it was also a pearl script, so probably the same one.
Sent from my MB865 using xda premium

I know I have posted here way to many times. But I want to get this to work.
It seems motorola has done more weird **** to their recovery partitions. Normally you can use certain scripts and binaries to separate a boot or recovery image (they follow the same format) into the ramdisk and kernel. That SHOULD be all that is in them. you can then modify the ramdisk to your liking, or use the kernel with cwm or the like to make it work. However it seems there is more to our image than just the ramdisk and kernel. when I extract them and repack them it seems to work fine, but the result is 5.5MB instead of 9.4MB with no modifications.
Does anyone have any idea what the deal is with that? I think if we can figure out that part we should be able to get a true custom recovery.
P.S. are you sure we cannot replace our boot.img with this same copying method? That is if we could even figure out how to modify it. Is there a hardbrick risk in trying? if so, Any volunteers?
EDIT: so our boot image will unpack and repack to the same exact size, so I think that means we could theoretically edit the ramdisk if that would do any good. the question still remains whether the phone checks its signature on boot or only upon flash

Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium

Harrison85 said:
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I can make a small change that would make it un verified then someone could copy it over and see if it boots. the problem is I am not 100% sure we would be able to restore to the original if it would not boot. I am 99% sure we would be fine, but I don't want to risk bricking completely. My guess is jim will know if it is safe to test or even worth trying, but if you want to be the guinea pig just tell me and I'll send you instructions.

By all means throw Me instructions and I will give it a shot right now
Sent from my MB865 using xda premium

Nevermind. I was sort of wrong. Both images separate just fine and can be recombined, but extracting the ramdisk seems to not extract the whole thing, it is much smaller when it is repacked. therefor you cannot really edit it at all.
Any ideas why?? I think it is just Moto being a pain in the ass as usual.

lkrasner said:
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
Click to expand...
Click to collapse
That is it in a nutshell. They pack their boot image in a different way from all other phone manufacturers, and not in a standard way for android. That is why Moto has their own "special" non-standard bootloader. They use a bitblast to package the boot image files, on top of the standard tgz, so the important files are "zip blasted" on top of the others in "superbit blocks", so there is not much we can do, unless we can de-a-line them, but that is not something I even want to start poking at.

I give up

I've been trying to get JB on my phone for a while now. I went back to completely stock and got the OTA. Downloaded and I thought it installed. Rebooted, still gingerbread. So I rerooted from scratch. Installed Codename Android on it. Booted up and was running fine for about 5 minutes, at this point I had only signed in to google. Hadn't restored or reloaded any apps. It rebooted on me again. Now. I can't get /sdcard to mount. Fastboot is saying I have no boot.img or recovery, But I can get scroll and click on recovery from that menu. I can't get the ****ing phone to do anything now. I've had this thing rooted since day 1. I'll be honest I really don't know how to use ADB.
Does anyone have any clue how to fix my damn phone?

Format SD through settings, Odin to stock and try again. This time read the instructions carefully... all of them.
Edit: Also make sure drivers are working for adb. Before moving on to another pc, I spent hours one day trying to get adb to work on one of my thinkpads. For whatever reason, I could not get the pad to recognize phone through adb.
Sent from my Nexus S 4G using xda premium

Bruce lee roy said:
Format SD through settings, Odin to stock and try again. This time read the instructions carefully... all of them.
Edit: Also make sure drivers are working for adb. Before moving on to another pc, I spent hours one day trying to get adb to work on one of my thinkpads. For whatever reason, I could not get the pad to recognize phone through adb.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
STOP TALKING ABOUT ODIN!!!!!!!! u dont need that!! just use fastboot commands to go back to stock jellybean! it takes 4 min!!
xda thread: http://forum.xda-developers.com/showthread.php?t=1572307
my vid showing that it works: http://www.youtube.com/watch?v=K4DePKyRgvU
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
[/COLOR]
Cascabreu said:
STOP TALKING ABOUT ODIN!!!!!!!! u dont need that!! just use fastboot commands to go back to stock jellybean! it takes 4 min!!
xda thread: http://forum.xda-developers.com/showthread.php?t=1572307
my vid showing that it works: http://www.youtube.com/watch?v=K4DePKyRgvU&list=UUTsL8yOHOK7IUQl2tsKId5A&index=1&feature=plcp
Click to expand...
Click to collapse
tutorial and download to get drivers working (dont do the root part): http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/

What's up with people and fcking odin?
Sent from my Nexus S

kwibis said:
What's up with people and fcking odin?
Sent from my Nexus S
Click to expand...
Click to collapse
i dont now, but what they should know is that when u buy a nexus phone, its made to be easly flash and modified!! = fastboot commands
nexus s isnt a galaxy s2!

Odin, one click toolkits... smh

Odin isnt the best option!!!!!! Fastboot is!
sent from my Nyan NeXus S
"You're either NEXUS or against us!"

I ended up just filing a claim and getting a new-ish one. Mine wouldn't run jellybean to save it's life. Even unrooted and did the OTA update. New one came today and is rocking JB like a champ. I had it rooted about 5 mins after activation.

[Q] Unlocked S-ON and can't get past Splash Screen

I unlocked the phone using the HTC unlock tool so I'm still S-ON. After the phone booted I did a back up and installed a custom ICS ROM and now I can't get past the splash screen. Backup failed with FAILED (remote: not allowed) I tried to install the stock ROM and that didn't work Actually tried multiple ROMs and no luck. Any ideas?

It sounds as though you read THIS THREAD, but most likely didn't read THIS THREAD.
Neither maybe?
---------- Post added at 01:30 PM ---------- Previous post was at 01:20 PM ----------
First of all you'll need to install your basic drivers so your phone & computer can talk to each other. It should have come on your phone's sdcard. It's called HTCDriver.exe. If so, store it on your computer in a new directory so you can find your new Android stuff and run it. If it isn't let me know and I'll post it for you.
After you've done that we're going to need to get ADB (android debug) installed on your computer so you can control some funtions of your phone from there. This is where that tutorial is located. http://forum.xda-developers.com/show....php?t=1858478 It's a bit more plain language than the guide in the first thread I linked for you but either is your call. Be sure not to overlook installing the fastboot drivers before you do the ADB installation though.

Thank you. I actually tried the fastboot but couldn't get a connection. I forgot that I uninstalled the HTC drivers and installed the PDA instead to try something different. After reinstalling the HTC drivers all is working again. Thanks again for the quick response.

NO problems. I'm just happy for you that is was such an easy solution.:good:

Go introduce yourself to juopunutbear.
Sent from Spaceball One.

I'm just a little skeptical and afraid of jbear. Does it actually work?

Short answer, yes. Took me numerous attempts but it does work.
Sent from my myTouch_4G_Slide using xda app-developers app

just grab the boot.img from the rom you installed
go to cmd
if you have the fastboot and adb folder (together) on your c drive
then type
cd/adb then it will change to c:\adb> then type
c:/>fastboot flash boot (your roms boot.img directory here) just make your life easy just drag and drop your img
then boom your good to go just make sure before you start go to fastboot mode
(ahhh memorys)

freefallpunk said:
I'm just a little skeptical and afraid of jbear. Does it actually work?
Click to expand...
Click to collapse
Yes. Just get a SD card you're not using and go to work.
Sent from Spaceball One.

[Q] Stuck in Clockwork

hello to all, i was given this phone by a friend cuz its stuck in CWM. im not new to android but i am to this phone( i have a G2x wich was easier by far to figure out). anyways after much searching in these forums i couldnt find anything to do with this problem so here it is.
I am stuck in CWM. i try to flash a rom( i have tried multiple times with different roms) and i get an error 7. does anyone one know what that means, and if so how do i fix it?
ive been trying to re root or revert to stock but adb must have been disabled and or debugging. any help would be awesome. for now ill keep searching and trying to get adb up and going...
i wonder if having lg drivers for my g2x on my comp would mess with adb....
any comments and or suggestions would be greatly appreciated

lmao your lucky your friend never heard of google, but I guess you haven't either haha. Anyway, you need to download a new rom and flash because the one on your sdcard is corrupt

Yup more than likely a bad download or possibly a corrupt partition of sdcard, reformat card, redownload rom, check md5sums
Nope having lg drivers won't effect this phone, but not having the right drivers for this phone is probably why adb doesn't work
Also the g2x is kinda fake rooting funky business, as you found this phone is much different. I would suggest booting into hboot and checking what bootloader you have and if the security flags are still on or not, can make a difference when flashing a rom.
Probably worth your while to read through the stickies and search the forum a bit too
Sent from my MyTouch 4G Slide using xda premium

Lol. Seriously dude. I'm not a noob at flashing Roms. I have tried to flash at least 6 different Roms all ending up with error 7. I'm brand new to this phone so treat me like I need a step by step, but don't be condescending plz.
Sent from my LG-P999 using xda app-developers app

demkantor said:
Yup more than likely a bad download or possibly a corrupt partition of sdcard, reformat card, redownload rom, check md5sums
Nope having lg drivers won't effect this phone, but not having the right drivers for this phone is probably why adb doesn't work
Also the g2x is kinda fake rooting funky business, as you found this phone is much different. I would suggest booting into hboot and checking what bootloader you have and if the security flags are still on or not, can make a difference when flashing a rom.
Probably worth your while to read through the stickies and search the forum a bit too
Im gonna have to read the stickies. im gonna have to read the whole forum....dont let the g2xers hear you say its fake flashing lol. first order of buisness is figuring out how to get into this hboot you speak of. everytime i trun the phone on it hits lg splash and then goes straight to cwm
Click to expand...
Click to collapse

In my signature you'll see a "Mirrors" link. Go there and at the bottom of Post #1 you'll see HTCdrivers.exe. Grab them & load 'em up. ADB should work for you then. Then issue "adb reboot recovery" from a cmd line and when there go to "mounts & storage" & activate. Copy the ROM you want to your SD card while retaining your boot.img in your ADB folder. Wipe Dalvik twice. format cache & then factory reset. Format system then under "mounts & storage". After ROM has flashed from .zip in CWM leave it there and issue "fastboot flash boot boot.img" fom ADB. Reboot & let it settle. Should work.
Don't turn your phone on.....go to HBoot by holding volume down & power at the same time & bypass boot sequence..

I should also mention the reason why this phone is messed up like it is. It was rooted running a custom Roman and then the previous owner did and total. Is that gonna matter much?
Sent from my LG-P999 using xda app-developers app

grantusmantus said:
I should also mention the reason why this phone is messed up like it is. It was rooted running a custom Roman and then the previous owner did and total. Is that gonna matter much?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I don't think I understand.
---------- Post added at 11:12 PM ---------- Previous post was at 11:07 PM ----------
Sounds like maybe he was flashing while unlocked with the kernel going in seperately. Your HBoot will tell you that if it says "S-On".
All that aside, XMC is right though. Somehow your ROM is corrupt.

Sorry my typing sucks. The previous owner did an OTA update. i try to get to hboot but it goes straight to cwm. downloaded the drivers from the link provided even...still no adb devices listed in the device manager or when i type in "adb devices" command. if i can get adb working i can get this all fixed, but ill be a raped ape if i knew what the hell happened to this phone.
Sent from my LG-P999 using xda app-developers app

grantusmantus said:
Sorry my typing sucks. The previous owner did an OTA
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thats where your issues are coming from then. You probably have the ....1313 bootloader with S-On. Reread all your responses here & it should get you there.

Well I wouldn't be the first to say that about the g2x, a friend of mine has one and I needed to root it for him, kinda laughed as I read through the forum on how everything is done there, not saying devs aren't talented just saying the phone is well... I don't know how to say it politely so I just won't
Boot into your bootloader and write down everything on that screen here so we can help, if you get adb running just type
adb reboot bootloader
If not power on while holding volume down and you'll get there
My guess is the phone is s-on and the bootloader was at one point unlocked, glad you still have a recovery though, I warned people about this type of stuff before... not to say that I warned you or your friend, just feels as if people believe me some times
Read last post on page 4 some info about your situation, hell skim the whole thread to understand a bit more about htc phones
http://forum.xda-developers.com/showthread.php?p=35743946
Sent from my MyTouch 4G Slide using xda premium

WeekendsR2Short said:
In my signature you'll see a "Mirrors" link. Go there and at the bottom of Post #1 you'll see HTCdrivers.exe. Grab them & load 'em up. ADB should work for you then. Then issue "adb reboot recovery" from a cmd line and when there go to "mounts & storage" & activate. Copy the ROM you want to your SD card while retaining your boot.img in your ADB folder. Wipe Dalvik twice. format cache & then factory reset. Format system then under "mounts & storage". After ROM has flashed from .zip in CWM leave it there and issue "fastboot flash boot boot.img" fom ADB. Reboot & let it settle. Should work.
Don't turn your phone on.....go to HBoot by holding volume down & power at the same time & bypass boot sequence..
Click to expand...
Click to collapse
got adb working...well, adb recognizes a device.....it give me no name just a string of numbers and letters
i followed your instructions to the T. got as far as flashing the rom...error 7 again(big suprise lol)after said error, flashing boot.img doesnt work terminal hangs at waiting for device.
In case your wondering what comes before the error 7....here is:
assert failed: getprop("ro.product.device)=="doubleshot"
E:Error in /sdcard/mikTouch.zip
(Status 7)

String of numbers is your phone, that's normal
Flashing boot.img is done through fastboot not adb, did you ever make it into your bootloader? It may help if you do and write down everything here.
Sent from my Nexus 7 using xda premium

Your gonna laugh at me. Idk what happened, but cwm is gone now. Device isn't recognized by the computer.
Sent from my LG-P999 using xda app-developers app

Pull your battery for 15 seconds then pop it back in. Then hold volume down + power & make sure your usb cord isn't plugged in or it will just start booting. That will take you to your bootloader. Write all that down the use volume down to navigate to the "recovey" option. Use power button to select it. From recovey's initial screen use trackpad to to get to the "install from .zip". Next screen select ".zip location" (or something like that). Trackpad down to the ROM.zip file & select. Install. After done...."fastboot flash boot boot.img" then reboot. Let it settle for 5 minutes.

grantusmantus said:
everytime i trun the phone on it hits lg splash and then goes straight to cwm
Click to expand...
Click to collapse
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.

Fuzi0719 said:
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Click to expand...
Click to collapse
Nice catch Fuzi! That passed right on over my head. Unless the guy before changed the splash screen this is a big UH-OH!!

Fuzi0719 said:
You get an LG splash??? The MyTouch 4G Slide is made by HTC, not LG. If you get an LG splash, either you have a different MyTouch phone, or something is seriously wrong.
Click to expand...
Click to collapse
Wow didn't even see that!
Yeah if the phone you have in your hands is made by lg then that's your issue, you have a my touch q or something, this forum is for the HTC made mytouch 4 g slide. If this is the case it makes a whole lot of sense your errors when flashing, not being able to get into bootloader, etc.
The old good news would be you probably didn't brake anything, just find the right forum, put it into download mode and restore with some kinda lg stock thing.
Sent from my Nexus 7 using xda premium

Lmao. Sorry guys,i wish this was my phone, you guys have a really great community and I was happy to be part of it for the night.
Sent from my LG-P999 using xda app-developers app

grantusmantus said:
Lmao. Sorry guys,i wish this was my phone, you guys have a really great community and I was happy to be part of it for the night.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
come back anytime