Related
ok, so a few days ago i was flashing the G2x weapon rom onto my rooted G2x, but while i was in the clockwork mod to flash it it froze on me, i left it like that for an hour or so, but it didnt work, so i took the battery out. now whenever i turn it on, it loads the LG screen, then nothing, the screen stays turned on, but its black, ive tried to boot it into recovery mode but that does not work either. What should i do?
Did you do One-Click NVFlash>? if u used Rom Manager you probably fake flashed and thats why its not working for you. You should use NVflash followt he steps and boot up into recover and restore a back up. GOod Luck
thanks ill try that
ed116 said:
Did you do One-Click NVFlash>? if u used Rom Manager you probably fake flashed and thats why its not working for you. You should use NVflash followt he steps and boot up into recover and restore a back up. GOod Luck
Click to expand...
Click to collapse
+1
Also try holding the vol down+pwr for longer than usual might just be being difficult
Making bad decision's one at a time.
so when i get into nvflash it says usb not found,
i did all the steps, and had it all done, but it dosent find my phone
Did u install the drivers correctly? That's probably the problem if it says USB is not found. I believe there is a video about how to install the drivers. Ill look for the video now
Sent from my LG-P999 using xda premium
Sorry for the double post, and here is a video link
http://www.youtube.com/watch?v=nmzk92rV6k4&feature=youtube_gdata_player
I used Linux to nvflash mine so I haven't used this method but I'm sure a lot of other people have.
Sent from my LG-P999 using xda premium
moeahmad1995 said:
Sorry for the double post, and here is a video link
http://www.youtube.com/watch?v=nmzk92rV6k4&feature=youtube_gdata_player
I used Linux to nvflash mine so I haven't used this method but I'm sure a lot of other people have.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1054492
This was written for Windows users, I followed this one myself, pretty straight-forward, and "idiot proof". (If anything can be truly idiot proof. Cynical, who, me?)
so, ive flashed my phone through nvflash and i got clockwork mod up and running, but whenever i select the file to flash that is on my SD card, it says no files found. i even tried going to my backup on the clockwork file, and nothing.
reki94 said:
so, ive flashed my phone through nvflash and i got clockwork mod up and running, but whenever i select the file to flash that is on my SD card, it says no files found. i even tried going to my backup on the clockwork file, and nothing.
Click to expand...
Click to collapse
Since changing to Nvflash, did you download the rom you want to install and transfer it to the phone from your computer. Using Rom Manager it may not have left a copy on your phone.
If you cant hook up the SD card to the computer, get an external SD card and make sure u've installed clockwordmod with external sd, hook it up to a laptop with an SD card slot, and put it in , then take the mini sd and pop it in your phone, then boot up and that should do it good luck! atleast now your 1 step closer to recovering your phone
Ughh hate,seeing this happen...hope u flashed nV..all the best
Sent from my LG-P999 using xda premium
Hope you didn't brick your phone.
No you did not brick your phone. Rom manager downloads the file to sdcard/clockworkmod/downloads. Look there for the file. Only if you download a rom from your browser does it go to externalsdcard/downloads
Sent from my LG-P999 using xda premium
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
Pls help-
I'm not quite a noob, but def no dev... got my Atrix 2 rooted using mastermind's 1-click method, installed bootstrap & flashed clockworkmod recovery- everything went fine until trying to flash/restore the ROM itself. I followed the instructions to the letter (save ROM in cwm backup folder, wipe cache & data, do not flash zip... restore in recovery). Yet i've bricked 2 atrix 2's trying to install this rom. Luckily the store I work at was good about letting me switch out, but kinda scared to brick a 3rd device. It just errors on restore then goes back to cwm. I try to reboot and cant get past the moto startup screen.. I'm sure i'm doing something wrong, cuz I know it should work (there are screenshots in the thread)... any help?
Sent from my MB865 using XDA
Did you unzip the rom and then put the contents in the backup folder?
You do know that you are more than likely going to be charged full price of the phone if you are returning a bricked phone to the store.
Sent from my SAMSUNG-SGH-I997 using xda premium
Why not flash the FXZ and start over?
Sent from my MB865 using xda premium
tmease1 said:
You do know that you are more than likely going to be charged full price of the phone if you are returning a bricked phone to the store.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Luckily I work for a phone sales store, so they didn't charge me full price, as I blamed the phone bricking on a "bad software update" (which is kinda true- if the rom had restored properly, I wouldn't have been bricked in the 1st place)
; )
and it was still within the exch. period anyway... But that's neither here nor there... Yez, I unzipped the folder into the cwm backup folder. Not sure about reflashing fxz, havent tried that yet... don't really know how, never had to do that? I've flashed dozens of roms on my HTC & Samsung galaxy phones, but this is my first exp. w/ moto. So any help u can give is appreciated.
Sent from my MB865 using XDA
No, not sure how to do that?
Sent from my MB865 using XDA
jzachary78 said:
Luckily I work for a phone sales store, so they didn't charge me full price, as I blamed the phone bricking on a "bad software update" (which is kinda true- if the rom had restored properly, I wouldn't have been bricked in the 1st place)
; )
and it was still within the exch. period anyway... But that's neither here nor there... Yez, I unzipped the folder into the cwm backup folder. Not sure about reflashing fxz, havent tried that yet... don't really know how, never had to do that? I've flashed dozens of roms on my HTC & Samsung galaxy phones, but this is my first exp. w/ moto. So any help u can give is appreciated.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
I had a similar problem, found the unzipped folder nested 2x under clockwork/backup.
Like this
sdcard/clockworkmod/backup/myrom/myrom
What I did was move all the files from second folder to the first then deleted second folder.
Hope I am clear and that it helps.
ATRIX 2 / Victory Rom
smgulsby said:
I had a similar problem, found the unzipped folder nested 2x under clockwork/backup.
Like this
sdcard/clockworkmod/backup/myrom/myrom
What I did was move all the files from second folder to the first then deleted second folder.
Hope I am clear and that it helps.
ATRIX 2 / Victory Rom
Click to expand...
Click to collapse
Can you post a like for the victory Rom, I'm kinda scared to install without the bootloader being unlocked and Id like something that's not att stock
I actually did find an extra set of files in the cwm backup folder & deleted them... so ur pretty confident that I should be able to install this ROM now? and (just to clarify) I don't need to flash the zip before restoring in cwm (that just doesn't make sense to me, but w/e works)? Thx for ur help
Sent from my MB865 using XDA
jzachary78 said:
I actually did find an extra set of files in the cwm backup folder & deleted them... so ur pretty confident that I should be able to install this ROM now? and (just to clarify) I don't need to flash the zip before restoring in cwm (that just doesn't make sense to me, but w/e works)? Thx for ur help
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Unzip rom, move the folder with the 2 files, to CWM/BACKUP.....boot into recovery, choose BACKUP/RESTORE, and restore the rom.
Sent from my MB865 using Tapatalk 2 Beta-5
So the problem is that you stuck on motorola dual core logo?
Just try to flash fxz,it's pretty simple. You just need the file you need and let the pc doing everything while you watching a tv.
I got this problem twice when i try to flash victory rom this morning,wich is caused by a corrupt file.
And everything is sorted out by flashing fxz.
Trust me,it works! (It sounds like commercials on tv )
You can always boot to recovery and when you see the android with the exclamation press both volume rockers to reset to factory.
Sent from my MB865 using xda premium
elaborate
kisnerct said:
You can always boot to recovery and when you see the android with the exclamation press both volume rockers to reset to factory.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
would you be kind and elaborate on this?
kojitabe said:
So the problem is that you stuck on motorola dual core logo?
Just try to flash fxz,it's pretty simple. You just need the file you need and let the pc doing everything while you watching a tv.
I got this problem twice when i try to flash victory rom this morning,wich is caused by a corrupt file.
And everything is sorted out by flashing fxz.
Trust me,it works! (It sounds like commercials on tv )
Click to expand...
Click to collapse
Just in case that happens again- what is the file I'll need when I connect to PC... u just mean the ROM files, or is there a diff fxz file i'm not aware of?
Sent from my MB865 using XDA
kisnerct said:
You can always boot to recovery and when you see the android with the exclamation press both volume rockers to reset to factory.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
actually tried that a cpl times via chat w/ a tech support rep from moto on first bricked device, it still wouldn't reset...
Sent from my MB865 using XDA
Flash Fix
This link can explain alot of your questions and hopefully have an answer for you as well.
http://forum.xda-developers.com/showthread.php?t=1396650. This is where I started to look when I began researching how to return my phone back to stock.
Installing the roms
if anybody could please tell me.......can I install Droid 3 or Droid razr's custom roms unto my Atrix 2. Would it work..? (Coz of the three phones bear same chipset i.e Powervr540)............Please help me out....i'm afraid if i'll brick my phone by doing this......!
devil.jeet said:
if anybody could please tell me.......can I install Droid 3 or Droid razr's custom roms unto my Atrix 2. Would it work..? (Coz of the three phones bear same chipset i.e Powervr540)............Please help me out....i'm afraid if i'll brick my phone by doing this......!
Click to expand...
Click to collapse
The devs have got some roms from other moto phones to boot but have problems mostly with the radio and probably a handful of other things. I would highly recommend you not try to do this. We have plenty of good roms here in the dev section that you can flash that are good roms. Generally if you follow the instructions for each rom you would be fine but if you are afraid of bricking your phone make sure you read a lot before attempting anything and always make sure you have a way back to stock.
Sent from my SAMSUNG-SGH-I997 using xda premium
ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.
kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.
bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.
I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app
As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader
klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.
Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.
Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:
I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app
I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.
I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app
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