Database Info

[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.

Bricked HTC ONE X AT&T

I checked all the other bricked threads and none have the same problem as me.
My HTC ONE X will not boot and or charge. I cannot get access to the bootloader or recovery.
My HTC ONE X had it's bootloader unlocked via the rogers htc-dev method. I also installed clockwork recovery. It is rooted also but you prob figured that already...
I pulled a bonehead move by flashing the MIUI rom the international one x by changing the update script to flash onto my phone. After it flashed it looked like it worked. When I left recovery and shut the phone off it would not turn back on.
I called AT&T they said they will switch it for me when they get a shipment but I want to keep this phone because the boatloader is unlocked and they might patch the rogers method.
Thanks in advanced.
P.S. I know how to use adb and other tools such as RUU and they did not work.

Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.

Ouch.... Another loss for htc sales
Sent from my HTC One X using xda premium

you cant get to hboot? 0.o

First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras

Reply
equlizer said:
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Click to expand...
Click to collapse
No nothing happens even with the charging adapter plugged in.
kevina90 said:
you cant get to hboot? 0.o
Click to expand...
Click to collapse
Nope

sassafras_ said:
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Click to expand...
Click to collapse
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.

jfn0802 said:
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
Click to expand...
Click to collapse
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.

gunnyman said:
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
Click to expand...
Click to collapse
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.

And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2

jfn0802 said:
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
Click to expand...
Click to collapse
Where do they have them in stock? I need to replace mine (screen issue) and can't find any around here.

powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+ 1
Sent from my HTC One X using xda premium

powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+2
Honestly, not trying to call you stupid or something, but did you really think it was going to run on this phone when it was meant for another one? The GPU and CPU are completely different...
Anyway, I'm glad AT&T is replacing it for you. Hopefully if someone else bricks the same way then they will be able to get a replacement as well.

so you are smart enough to use adb, an RUU, unlock your bootloader, root, flash roms.......but you aren't smart enough to see the hundreds of posts saying that the international roms don't work on our phones??

lol

Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?

Just pull the batte..... oh

jmattp said:
Just pull the batte..... oh
Click to expand...
Click to collapse
+1 for when I drowned my first one and it was stuck in a boot loop. I know it could have been saved if the battery would have been taken out.
Sent from my HTC One X

modest_mandroid said:
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Click to expand...
Click to collapse
My EVO was unbrickable too, I flashed a rom that was designed for the international version. It only contained system and other basic rom stuff, nothing that was crazy.

No idea why you wouldn't be able to boot into recovery then. I hope all HTC handsets aren't like this..
Sent from my SGH-I897 using XDA

Restored from a backup on newly half-rooted Shift

I got into a tiffy...and Im in fear I may have bricked my phone with a boot loop.
Somehow my shift installled ROM manager in process. It is acting as if I am getting SU .. I had "temproot" though I guess i screwed it. I'm going to try to jump on a PC if I can to get this all running. We'll see (osx snow leopard here).
HBOOT screen:
Speedy XE SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
My phone came with it like this. gahhh is this still true?
I cannot use the recovery either.
Help!

If your HBoot is 0.98.0001 with " S-On " your going to have to start the whole Root process over. Check THIS thread. Watch the Videos, and Read the Info. It's all fairly straight forward. The biggest thing is to take your time, and make sure you do the process correctly. I would suggest watching the Videos several times. Also reading the Instructions several times before you start.

Good News *
looks like I was able to make a Nandroid backup of an unrooted Shift I still have that was unrooted. After much trial and error I was able to Restore from a backup. However, the HBoot was HBOOT-0.93.0001 on the other model, the newer one is HBOOT-0.98.0001.
One problem, now the wifi does not work, probably due to the HBoot.
I think a previous user left ROM Manager on it which is how this all happened that a another user tried installing and made it all messed up, somehow CWM 5.8.1.6 was installed already. I was getting ready to install 5.0.2.0 onto it. Now I am trying to recover this persons errors. Funny.
Any of the obvious methods of running a "Back to Stock" routine or using RUU was not working whatsoever since the HBoot was different.
Basically troubleshooting at this point. No idea what to do. I am calling CREDO to see if they can help me update my radios but i am betting i'll probably just get another phone from them. This may be the end of my Shifting since i'll be upgrading to something in the next few months..hopefully htc will save me somewhere, but samsung may be where I land next.
LASTLY :: I found the RUU HERE..but it gave me the same error... "Customer ID Failed"
man.... what a pain in the arse. Guess I'll be getting another shifty from them soon, unless anyone else has any brighter ideas.

So are you saying the 2.2 RUU ran all the way through ? The "Customer ID Failed" is when you boot up ?

prboy1969 said:
So are you saying the 2.2 RUU ran all the way through ? The "Customer ID Failed" is when you boot up ?
Click to expand...
Click to collapse
RUU ran through but stopped at customer ID, I tried running through bootloader, running the original back to stock 2.2 Froyo, and none of this is working. The phone came with Froyo 2.2. I also tried removing the boot.img from newSENSE in a zip and placed that on the SDCard during another reinstallation of the zip, and none of that seemed to work. I feel like I have tried virtually everyhting and nothing is seeming to work.
I think I am almost figuring out how to crack this new egg, but no idea what's up with it.

If you got it booted but wifi isn't working, that means in system/lib/modules the modules are not matching the boot.img and will throw a WiFi error everytime
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

strapped365 said:
If you got it booted but wifi isn't working, that means in system/lib/modules the modules are not matching the boot.img and will throw a WiFi error everytime
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Yes, that totally makes sense..is there a fix for that ?

konichwa said:
Yes, that totally makes sense..is there a fix for that ?
Click to expand...
Click to collapse
Push either the modules folder from the ROM your on now, or reflash the boot.img again. It depends on where you are at now
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

strapped365 said:
Push either the modules folder from the ROM your on now, or reflash the boot.img again. It depends on where you are at now
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm push from the rom? Interesting. Well I'll see what I can do..maybe somehow it did not get in there?? Super strange.
Thanks for all the help y'all..doing my best.
Sent from my PG06100 using xda app-developers app

konichwa said:
Hmmm push from the rom? Interesting. Well I'll see what I can do..maybe somehow it did not get in there?? Super strange.
Thanks for all the help y'all..doing my best.
Sent from my PG06100 using xda app-developers app
Click to expand...
Click to collapse
Yeah you will need the modules from the boot.img your running. So say you were on newSense while being s-on unlocked and wifi was working, and then you decided you wanted to run a new kernel so you fastboot flash a new boot.img, well when you boot in, the modules in system/lib/modules won't match the new kernel your running, so you have to grab the modules folder from the kernel and push them one at a time to be sure they all go to the right place. I don't remember all the modules names by memory(just know where they are in a ROM and after a compile) but ill give an example command to push a module with an easy module name my simple mind can remember. So place the modules in your platform-tools folder, plug your phone in on charge only and open a terminal to cd to platform-tools then enter these commands*
adb remount
adb push tun.ko /system/lib/modules (tun.ko and cifs.ko are not used in every kerenel)
adb push *the rest of the modules* /system/lib/modules
adb reboot
We are trying to get you on the right page, but on the weekends I dedicate all my free time to my family, and don't mess with xda or anything untill Sundays
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

Rebooted into fastboot mode, and did not work. nope..acted like it..but firstly it failed on the remount. but said Success?
Okay well guess thats the deal. ugh, seriously.

konichwa said:
Rebooted into fastboot mode, and did not work. nope..acted like it..but firstly it failed on the remount. but said Success?
Okay well guess thats the deal. ugh, seriously.
Click to expand...
Click to collapse
Modules are not pushed while in fastboot, their either pushed while running or in recovery
Sent from my myTouch 4G Slide using Tapatalk 2

strapped365 said:
Modules are not pushed while in fastboot, their either pushed while running or in recovery
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Yes, i ran it in recovery. it acted like it pushed, and probably did, but did not work. it is what it is :\
Basically it ended up being some weird halfroot that seemed it had no way on getting it to work . somehow the hardware was flashed earlier on before.
I had it and had the newer CWM, I wonder if that had anything to do with it.
Well, thanks all for the help!
best

[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] 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