[Q] Stuck in Clockwork - T-Mobile myTouch 4G Slide

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

Related

[Q] Help noobe flashing problem

I have been reading threads here and I can't find an answer to my question.
I have an ATT Captivate running ATT 2.2. I ran the super one click app and have superuser available for the apps. I have rom manager free edition but no matter what I try I cannot get it to flash the Clockworkmod Recovery. When I try to flash it I get the message that it's been succesfully downloaded but never get the succesful flash.
I've spent a big part of the day at this and can't figure out why this isn't working. ANY ideas would be appreciated.
TIA, Jeff
[email protected] said:
I have been reading threads here and I can't find an answer to my question.
I have an ATT Captivate running ATT 2.2. I ran the super one click app and have superuser available for the apps. I have rom manager free edition but no matter what I try I cannot get it to flash the Clockworkmod Recovery. When I try to flash it I get the message that it's been succesfully downloaded but never get the succesful flash.
I've spent a big part of the day at this and can't figure out why this isn't working. ANY ideas would be appreciated.
TIA, Jeff
Click to expand...
Click to collapse
It won't actually be flashed to your device. It creates an update.zip file on your internal sd card. What you have to do to get into clockwork is turn your phone off, hold down vol up+vol down+power until you see the AT&T logo show up on the screen. When you see the logo show up, release power but keep holding the volume keys. This will take you into the regular stock recovery. Once you are there, select the 'reinstall packages' option. The phone should reboot, at which point, hold down the volume keys again to get back into the stock recovery. Once it boots into stock recovery for the second time, select 'reinstall packages' again and it should put you into clockworkmod this time around.
At one time in all my trying I've been thru this as well. When I select reinstall packages I get:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted
I really want to get away from this ATT 2.2. I waited for the ATT upgrade but since it still won't support bluetooth voice dial I'm going to go this route if I can get it to work.
Jeff
modest_mandroid said:
It won't actually be flashed to your device. It creates an update.zip file on your internal sd card. What you have to do to get into clockwork is turn your phone off, hold down vol up+vol down+power until you see the AT&T logo show up on the screen. When you see the logo show up, release power but keep holding the volume keys. This will take you into the regular stock recovery. Once you are there, select the 'reinstall packages' option. The phone should reboot, at which point, hold down the volume keys again to get back into the stock recovery. Once it boots into stock recovery for the second time, select 'reinstall packages' again and it should put you into clockworkmod this time around.
Click to expand...
Click to collapse
Beg to differ. He has 2.2. Signature verification error.
Sent from my GT-I9000 using XDA App
Recovery 3E. The fix is in the dev forum
Sent from my HTC Vision
http://forum.xda-developers.com/showthread.php?t=909213
Sent from my GT-I9000 using XDA App
Oh right, totally forgot about that. It's been forever since I've flashed stock 2.2.
You can either follow the guide here:
http://forum.xda-developers.com/showthread.php?t=909213
Or you can simply flash back to 2.1 using this and do what I said in my original post:
http://forum.xda-developers.com/showthread.php?t=751518
Pirateghost said:
Recovery 3E. The fix is in the dev forum
Sent from my HTC Vision
Click to expand...
Click to collapse
+1
I've answered the same question atleast 20 times last week.
Please look around the forum and you'll find your answers!
Thanks Pirate for taking care of this one (with so many more to come )
BWolf56 said:
+1
I've answered the same question atleast 20 times last week.
Please look around the forum and you'll find your answers!
Thanks Pirate for taking care of this one (with so many more to come )
Click to expand...
Click to collapse
bets on number of posts this week regarding this same issue?
Good place for this question would be q&a, next time post there or search first.
Sent from a super smooth captivate running andromeda
Pirateghost said:
bets on number of posts this week regarding this same issue?
Click to expand...
Click to collapse
I got $5 on 7, what kind of odds am I looking at?
studacris said:
I got $5 on 7, what kind of odds am I looking at?
Click to expand...
Click to collapse
I got her under, what's the spread?
Sent from a super smooth captivate running andromeda
studacris said:
I got $5 on 7, what kind of odds am I looking at?
Click to expand...
Click to collapse
lolol
I say 11!
Wouldnt it just be easier to load a kernal tar file in odin? I know that may noy be recommended for noobs but im willing the help out walking someone through steps,if you havent already figured it out
Sent from my GT-I9000 using XDA Premium App
brd912 said:
Wouldnt it just be easier to load a kernal tar file in odin? I know that may noy be recommended for noobs but im willing the help out walking someone through steps,if you havent already figured it out
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
It is a way to do it but Odin can easely brick a phone if not used right.
It's alot easier to just prompt the command (.bat) from our computer with our phone plugged in debugging mode and let it do its magic. Takes a few seconds and it's done

[Q] HELP xoom root!

ok so i rooted my xoom the other day flashed hammer head 2.1. restored my tablet to stock rooted rom buwhen i did i have now found a way to lock my device. i can boot up and have my su icon available to me however i cannot gain root access even through adb it tells me the file system is read only. so i figured i some how unrooted the device and proceeded to begin the root process for honeycomb. however when trying to push su over to the tablet it tells me the file failed to transfer because the file system is read only what do i do now? Any help would be appreciated.
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
your a noob mate seriously... these board are full of people like you... 1.. download the stock images from
http://developer.motorola.com/products/software/MZ604_HWI69.zip/
if your device is a wifi only and then push the files with fastboot...
ie.. unzip the folder into where the adb fastboot exe are
1. fastboot flash system system.img
2. fastboot flash boot boot.img
3. fastboot flash user user.img
4. fastboot flash recovery recovery.img (as you obviously cant handle root..)
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not talking mounting in cwm here bud
Get to fastboot mode not android recovery same process power plus vol down
Then flash the files not push as mounting in cwm only put the files on sd card not flashing it outright from what your reply was
I was a noob once and soft bricked everything and yet i read and read and fixed stuff myself through searching.. Cuz ultimately if its bricked what do u have to lose then ey lol just find and try everything cant make a worse paperweight than one u may already have eh
But get to fastboot not cwm then flash the files like i said and it will almost certainly work
Sent from my HTC Sensation 4G using XDA Premium App
Thats my other problem my sd card slot isnt wrkn that was my initial instinct. If i try to flash to the sd card it says no directory found. Ive used 3 different sd cards and get the same message. Im really thinkin i got a bad sd slot even when it was rooted and running i had issues with the sd card not wrking. I had several back ups on it when it did wrk and those dissappeared as well. I bought the xoom soley because of the sd card slot was pretty much going to be my saving grace when doing back ups if i ever messed up. I tried wrking it in fastboot as well if i try to flash to the system its read only. If i flash to the sd card directory not found. I know these questions are irritating to more savy individuals and i looked around trust me the last thing i like to do is say der i dun broke it i need an adult. Im just makin sure i didnt over look something more savy ppl know about. I honestly think its bricked at this point. Ive tried what you said and any other way i can think of but i alway get some kind of error.
Sent from my ADR6400L using XDA Premium App
Sent from my ADR6400L using XDA Premium App
What version of clockwork mod recovery are you using?
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would use this recovery instead of 4.0.0.2.
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
you needed to flash the recovery with FASTBOOT.. not adb push chmod stuff; much easier and the process works
read the top post again.. get the recovery.img file (the v3 one the other fellow told you to grab)
1. hold the volume down button and the power button... some text will come on up the top about fasboot protocol and then
2. leave it plugged in to your computer and DONT TOUCH THE XOOM...
3. get your cmd.exe prompt window out and navigate to where your adb.exe AND fastboot.exe files are (should be tools or platform-tools...)
4. Place the recovery.img file into the explorer window where the adb.exe and fastboot.exe both are.... (this should be there as u keep trying to use adb commands but do it again to make sure)
5. type fastboot flash recovery recovery.img
thats the recovery.img flashed...
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Well, there's your answer. You did not successfully unlock.
Glad that you learned some useful things.
flying honey comb on xoom mz601
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
aKolp2010 said:
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
Click to expand...
Click to collapse
You should open a new thread with your issue. Seems the OP in this one has fixed his issues by replacing his Xoom. You'll get better attention by creating a new thread in this forum.

[Q] Getting my hands on a bricked g2x today....

he said he bricked it trying to upgrade to ICS.
is the sticky at the top still the way to unbrick it? i noticed that a couple links were dead in the first post. granted i didn't go through all 17 pages, just wanted to make sure there wasn't anything newer then whats already been posted.
edit: he did say that the screen is showing s/w if that matters
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
LurkerRWO said:
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
Click to expand...
Click to collapse
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
im on windows 7 if that matters
and after i boot into recovery the screen is just flashing black. any ideas?
everything i do with flashing it just sits at the prompt saying "flashing" and nothing else happens.
blackbeasst said:
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
Click to expand...
Click to collapse
You apparently you did not even read the first post. XP only, will not work with Windows 7.
"As many have stated, pushing the v21E_00.kdz via the KDZ_FW_UPD program does work. It's just touchy.
This is a step by step guide to get you back in to working shape.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.
Edit: As an alternative, a virtual environment running XP will do the job. Those steps are up to you."
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
LurkerRWO said:
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Can confirm that too. Was working fine on 32 bit win7, using the method from the stickies upgrading wind's June baseband.
Sent from my LG-P999 using xda premium
duple and lurker, thanks for the confirmation that it works with 7
when i try and push the kdz i get the dreaded phone not found.
ok im on my xp machine here at work and heres what i got:
Part 1: Download the files you will need below.
V21E_00.kdz
KDZ_FW_UPD_EN
One-Click-G2x-recovery-flasher-06-16.rar
LG USB Drivers G2x
Part 2:
1) Install the LG G2x USB drivers to your WinXP machine.
2) Extract the entire contents of the One-Click recovery in to a folder and keep it handy.
3) Remove the battery from the phone. Hold both volume buttons and plug in the USB cable. If you are asked for a driver, look in the APX folder where you extracted the One-Click recovery archive.
4) Run OneClickRecoveryFlasher.exe and flash the stock recovery. Wait for the process to finish and close all windows and unplug the phone.
no problems with above steps. after that nothing works. when i put the battery back in and turn on thats when i get the flashing black screen, not back to the s/w screen.
5) Put the battery back into the phone and turn it on. You will be back at the S/W Upgrade screen. This is where you want to be! Now plug the USB cable back in to the phone. If everything is up to snuff you should have no driver problems at this point.
6) Extract KDZ_FW_UPD_EN.7z in to a folder. Inside is a msxml.msi. You need to run and install this first!
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)
ok just for craps and giggles i tried booting into recovery and actually got the box with arrow and android! but it then reboots back to the lg screen and then flashing black screen
WOOT! finally able to get into CWM recovery!
is all that needs to be done now is install a stable rom?
double WOOT! back up and running. time to test the functionality of if though!
edit: can't find the sim and no service.
blackbeasst said:
double WOOT! back up and running. time to test the functionality of if though!
Click to expand...
Click to collapse
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
DupleX01 said:
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
and im a tard. sim was inserted bass akwards
blackbeasst said:
and im a tard. sim was inserted bass akwards
Click to expand...
Click to collapse
Congrats man.
Sent from my LG-P999
wifi seems to be flaky. keeps scanning and dropping work and home network
also it appears that the market wasn't on that version of the rom. is that a quick fix?
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
DupleX01 said:
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
blackbeasst said:
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
Click to expand...
Click to collapse
You were lucky, indeed!
A CM nightly can be stable too, however I would flash either Weapon or Eagles Blood for a couple of days to have a piece of mind that everything is working cool. The most important would be a proper full wipe (cache, dalvik, system under mounts and storage, battery stats and imho internal and external SD too) too get rid of the previous mess caused by the unsuccessful flash, etc.
Sent from my LG-P999 using xda premium

[Q] Is there a way to completely wipe HTC One XL?

Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
don't flash ICJ, just relock bootloader and ruu.
if you have no physical damage why are you getting a replacement phone?
Did you flash boot.img?
And how about you not ask how to defraud att because you don't know how to flash and fix a botched flash.
schumachermp said:
Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Click to expand...
Click to collapse
... and this is why we can't have nice things. Thanks, guy.
All I can think is, at least he did not throw it under his car.
It can be salvaged, where as other clown just destroyed it for nothing.
WR
Sent by WR's One XL
omario8484 said:
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
Click to expand...
Click to collapse
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
schumachermp said:
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
Click to expand...
Click to collapse
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
InflatedTitan said:
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I did flash boot.img. It just never moved past the CM10 starting animation. And honestly, not super familiar with fastboot three days ago... fairly familiar at this point. But nothing seems to get this thing to work. Please tell me what to do!
(BTW - I only called warranty at the advice of an AT&T employee in the store. I'd love to just fix my phone)
Twrp 2.3.1.0, wipe everything, flash boot.img in fastboot, and flash cm10 and gapps in twrp.
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
schumachermp said:
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
WarRaven said:
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
Click to expand...
Click to collapse
Ok, great. I've downloaded the TWRP recovery image and the Goo Manager APK... now how do I use Goo Manager on a device that won't boot up?
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
InflatedTitan said:
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
schumachermp said:
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
Click to expand...
Click to collapse
I'm happy you got your phone running.
Don't get it all sticky with all that love.
Lol good job bro
Sent from my One X using Tapatalk 2
ECEXCURSION said:
... and this is why we can't have nice things. Thanks, guy.
Click to expand...
Click to collapse
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
rodpgfx said:
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
Click to expand...
Click to collapse
Completely agreed. The notion astounds me (and disappoints me also) that the OP was going to send the phone in for a warranty replacement simply because they didn't do the proper research and learning before modding the phone. And when the condition was completely and easily reversible. If the screen comes on with this phone, it can be recovered.

[Q] First time rooting/S-Off/new ROM

Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium

Categories

Resources