Database Develop

[Q] Broke my Hero bad...need help

Yep, I broked it.
So, wanna hear a fun story?
I got a free Hero, and tried to root it. First thing I tried was z4root. It failed. Then I tried RegawMod. Fail. Perhaps it didn't help that I had the latest stock version of the Hero, 2.32.651.x
So, then, me being a wise guy, decided that I'd just try doing it myself through ADB. I tried to follow CyanogenMod adb rooting instructions HERE. I kept getting stuck at step 5:
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
Click to expand...
Click to collapse
It kept saying something about how it couldn't chmod "/data/local/tmp/rageagainstthecage-arm5.bin" because it wasn't a directory. Well, duh, this I know...but I couldn't figure out how to make adb understand that.
Well of course, because I couldn't chmod rageagainstthecage, I couldn't move on to the next step, actually running ratc:
/data/local/tmp/rageagainstthecage-arm5.bin
Click to expand...
Click to collapse
Now, this is where the fun really begins. I rebooted the Hero, just to see if that would help, and then I was going to try again. Trouble is, the phone wouldn't boot. Kept getting stuck on an endless boot on the HTC screen. So, I went into clockworkmod, wiped everything (except boot), and then restored the nandroid backup I had made before I started this whole process. Still no dice. Still stuck at an endless HTC boot screen. I tried a hard reset on the fastboot menu just for ****s and giggles...but still nothing doing. I also tried running the RUU app on my computer to install an older version of the stock ROM, but RUU would not recognize my device (even though HTC sync and ALL of the drivers are installed, and I had it mounted to the computer in clockworkmod).
So...I guess my question is - does anyone have any clue how to fix this? I still want to root the damn thing, but right now I'd be happy just to get the stock rom back up and running. I know if I could find a stock ROM I could probably flash it through clockworkmod...alas, the only one I found turned out to be a corrupt zip file.
Any help is appreciated. Thanks!

u do realize if u have clockwork mod u are rooted right...

Bierce22 said:
u do realize if u have clockwork mod u are rooted right...
Click to expand...
Click to collapse
I'm not sure how, as all three methods I tried to root failed. I even tested it with terminal emulator, got all $, no #. Of course, that was back when I could actually get to Terminal Emulator.

Bling_Diggity said:
I'm not sure how, as all three methods I tried to root failed. I even tested it with terminal emulator, got all $, no #. Of course, that was back when I could actually get to Terminal Emulator.
Click to expand...
Click to collapse
look here for the RUU.zip made by tehdarkknight, get it. Then run in with the instructions from jasonmaloneys thread about fastboot without s-off. http://forum.xda-developers.com/showthread.php?t=1063843
EDIT: that *should" unroot you back to stock. Then follow the REAL rooting thread (adb method) by regaw leinad.

PLEASE DISREGARD this thread. I'm an idiot...apparently the damn thing was rooted before I got it...which explains why my attempts to root it weren't working. Flashed CM7 in clockworkmod and it booted up with no problems.

Bling_Diggity said:
PLEASE DISREGARD this thread. I'm an idiot...apparently the damn thing was rooted before I got it...which explains why my attempts to root it weren't working. Flashed CM7 in clockworkmod and it booted up with no problems.
Click to expand...
Click to collapse
Yeah, that's what bierce22 was saying - if you already had clockworkmod, you were already rooted. But it was a good learning experience for you, right?

no one ever listens to me around here lmao.

Lmao thats hilarious. I fail. Bierce FTW.
sent from a series of tubes.

Bling_Diggity said:
Yep, I broked it.
So, wanna hear a fun story?
I got a free Hero, and tried to root it. First thing I tried was z4root. It failed. Then I tried RegawMod. Fail. Perhaps it didn't help that I had the latest stock version of the Hero, 2.32.651.x
So, then, me being a wise guy, decided that I'd just try doing it myself through ADB. I tried to follow CyanogenMod adb rooting instructions HERE. I kept getting stuck at step 5:
It kept saying something about how it couldn't chmod "/data/local/tmp/rageagainstthecage-arm5.bin" because it wasn't a directory. Well, duh, this I know...but I couldn't figure out how to make adb understand that.
Well of course, because I couldn't chmod rageagainstthecage, I couldn't move on to the next step, actually running ratc:
Now, this is where the fun really begins. I rebooted the Hero, just to see if that would help, and then I was going to try again. Trouble is, the phone wouldn't boot. Kept getting stuck on an endless boot on the HTC screen. So, I went into clockworkmod, wiped everything (except boot), and then restored the nandroid backup I had made before I started this whole process. Still no dice. Still stuck at an endless HTC boot screen. I tried a hard reset on the fastboot menu just for ****s and giggles...but still nothing doing. I also tried running the RUU app on my computer to install an older version of the stock ROM, but RUU would not recognize my device (even though HTC sync and ALL of the drivers are installed, and I had it mounted to the computer in clockworkmod).
So...I guess my question is - does anyone have any clue how to fix this? I still want to root the damn thing, but right now I'd be happy just to get the stock rom back up and running. I know if I could find a stock ROM I could probably flash it through clockworkmod...alas, the only one I found turned out to be a corrupt zip file.
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
My story is similar. Boot into hboot stay in fastboot mode and DO NOT VOL DOWN. once youve booted into hboot, plug the hero In and get the ruu started up. Once you've started the ruu, if you get the connection error message, click the action button (trackball) on 'fastboot usb mode' and for some reason, the ruu seemed to connect to it then. Hope it works out for ya.
Sent from my HERO200 using XDA Premium App

Also, when rooting with z4, do a temporary first then after a successful temporary root, hit the permanent button. That's done the trick for me in countless seemingly hopeless situations.
Sent from my HERO200 using XDA Premium App

[Q] ADB stopped working on Windows 7

So ADB worked just fine when I was using the stock 2.1 rom. After upgrading to Cyanogenmod 7 it just stopped. If I open ADB and type a command it returns "no device found" and if I put in "adb devices" it's blank. I'm using Windows 7 64bit. I was only able to find some information, but it's for the mt4g. USB and ADB broken on Win7 What should I do now? Thanks

You did make sure that USB Debugging is on, right?

also try switching ports and/or restarting your computer.

Also make sure drivers are up to date. Had the same problem after flashing Andromeda3.
Sent from my SAMSUNG-SGH-I897 using XDA App

I believe you need the nexus s drivers installed for cm7.

Heya, I'm facing the same issue.
Captivate usb driver has an yellow triangle with an exclamation mark on it. Gonna try some stuff after I get home today ,if I manage to get it working I post here.

studacris said:
I believe you need the nexus s drivers installed for cm7.
Click to expand...
Click to collapse
I don't think so, it is still Captivate bootloaders. When i tried cm7 and had to flash back to stock normal drivers worked. Course I have SDK installed don't know if that installs drivers for Nexus S or not. But ya get drivers just in case.
To the op It sounds like a bad cable to me.

cappysw10 said:
You did make sure that USB Debugging is on, right?
Click to expand...
Click to collapse
Lol yeah. I thought that was the problem at first but I have it enabled

crusecontrl said:
also try switching ports and/or restarting your computer.
Click to expand...
Click to collapse
thanks, I'll see how this works

Urgur the Gurgur said:
Also make sure drivers are up to date. Had the same problem after flashing Andromeda3.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Last time I checked they were, but it won't hurt to check again

prbassplayer said:
I don't think so, it is still Captivate bootloaders. When i tried cm7 and had to flash back to stock normal drivers worked. Course I have SDK installed don't know if that installs drivers for Nexus S or not. But ya get drivers just in case.
To the op It sounds like a bad cable to me.
Click to expand...
Click to collapse
I'm pretty sure it's not a bad cable. It still works in all other respects (charging, mounting as usb storage)

andi br said:
Heya, I'm facing the same issue.
Captivate usb driver has an yellow triangle with an exclamation mark on it. Gonna try some stuff after I get home today ,if I manage to get it working I post here.
Click to expand...
Click to collapse
Yeah I just checked, and I have the yellow triangle too. Maybe we should just reinstall the drivers? I'll try and see what happens

TheJareBear said:
Yeah I just checked, and I have the yellow triangle too. Maybe we should just reinstall the drivers? I'll try and see what happens
Click to expand...
Click to collapse
YEAH! Fix it!
So do the following :
1) Install Android SDK (developer.android.com/sdk/index.html)
2) Make sure to install Google USB drivers package (developer.android.com/sdk/win-usb.html)
3) After it's installed go to the devices manage , right click Captivate Driver you have issue (yellow triangle) and select to Update driver. Now pick to choose location and go where Google's usb drivers are installed for me (D:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver) and wait till it gets installed.
Hope it helps ! Let me know if you have any doubts.

andi br said:
YEAH! Fix it!
So do the following :
1) Install Android SDK (developer.android.com/sdk/index.html)
2) Make sure to install Google USB drivers package (developer.android.com/sdk/win-usb.html)
3) After it's installed go to the devices manage , right click Captivate Driver you have issue (yellow triangle) and select to Update driver. Now pick to choose location and go where Google's usb drivers are installed for me (D:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver) and wait till it gets installed.
Hope it helps ! Let me know if you have any doubts.
Click to expand...
Click to collapse
Did this work for you? I'm doing it right now, but I thought the Google drivers wouldn't work because they're only for ADP's and the Nexus line of devices. I also downloaded (but haven't installed) the Samsung drivers. But I'm pretty sure I already have these, lol.
[Edit]
It worked! Thanks!

TheJareBear said:
Did this work for you? I'm doing it right now, but I thought the Google drivers wouldn't work because they're only for ADP's and the Nexus line of devices. I also downloaded (but haven't installed) the Samsung drivers. But I'm pretty sure I already have these, lol.
Click to expand...
Click to collapse
Rofl! I said you needed the damn nexus s drivers a few posts ago.
CM7 is based on nexus s firmware. That os has nothing to do with samsung. It's AOSP which is why the google drivers are required.

studacris said:
Rofl! I said you needed the damn nexus s drivers a few posts ago.
CM7 is based on nexus s firmware. That os has nothing to do with samsung. It's AOSP which is why the google drivers are required.
Click to expand...
Click to collapse
Lol yeah at first someone said you don't because of like different bootloaders or something like that, I figured it would work since nothing else would

Not to talk poop about anyone else in this thread, but op pay attention to the post count/thanks ratio, that is usually a good indicator to tell if someone knows what they are talking about.
Just sayin...

Thanks, it pays to be more attentive. Could've saved the time of asking another question or confusing a newer member.

I did say i had SDK installed, and I also said you should try it. I just said that since it shared same bootloaders it probably wasn't it. I was wrong though.
But ya I'm still a newb.

No problem, at least you put out a helpful answer. Lol, made me think of another thread I posted awhile back that nobody answered but it had 140-something views!

Need help getting back to stock

I followed this site religiously for nearly the first year that I had my captivate. I've been busy for the last few months and am completely lost on where I am and where I need to go to get my phone back to stock and then updated to the newest rom.
My phone was running CM7 just fine in April (I haven't updated anything since then, I think) but recently began force closing EVERYTIME that I tried to open ANY program. I used cwm and restored my system to what I had previously installed but am getting random reboots (this had never been an issue before).
I've been pretty good about taking care of my phone in the past, but it's been so long since I've messed with this stuff I have no idea what I have installed or what to do to get rid of it.
Right now my phone info says this:
android version 2.3.3
JK3 modem
Kernel version; 2.6.35.7 codeworkc #1
Mod version: Nightly 03042011
Build Number: GRI40
I'd like to get back to stock so I can reorient myself before catching up with current versions.
Thanks

I forgot to point out that odin doesn't recognize my phone.

moorent said:
I forgot to point out that odin doesn't recognize my phone.
Click to expand...
Click to collapse
Do you have the phones drivers installed? Do you have Android SDK installed with Nexus S drivers? Did you run ODIN as Admin?

you might want to just keep trying odin. Restart or reboot your computer.. try a different USB port. I had Odin stop recognizing my phone once. All it took was a restart of the computer and has worked fine for me since.
That's what I would suggest

My drivers say they were successfully installed but don't seem to work in download mode. I can drag and drop files without issue when the phone is on.
I don't have SDK installed.
I've tried all my USB ports on each of my computers, restarting, and have even unplugged every USB device except for my phone; no dice.
At this point I'm considering throwing my phone at the wall and running over it a few times to cash in on my warranty and maybe even have a shot at getting a captivate with a working gps.

moorent said:
My drivers say they were successfully installed but don't seem to work in download mode. I can drag and drop files without issue when the phone is on.
I don't have SDK installed.
I've tried all my USB ports on each of my computers, restarting, and have even unplugged every USB device except for my phone; no dice.
At this point I'm considering throwing my phone at the wall and running over it a few times to cash in on my warranty and maybe even have a shot at getting a captivate with a working gps.
Click to expand...
Click to collapse
If you have cwm recovery.. just flash another ROM in recovery. Wipe your caches data and dalvik before you flash and even factory reset. Unless you need gingerbread bootloaders, a lot of ROMs can be flashed right over one another without the whole FTS biz.
*edit* also wanted to mention CM7 is funky with storage space. If you go into terminal emulator in your apps and type "df" ..look for your datadata, make sure your under 90%. Once that fills up you'll start to get more and more force closes. The cure is to move some apps to your SD card.
Sent from my SGH-I897 using XDA Premium App

moorent said:
My drivers say they were successfully installed but don't seem to work in download mode. I can drag and drop files without issue when the phone is on.
I don't have SDK installed.
I've tried all my USB ports on each of my computers, restarting, and have even unplugged every USB device except for my phone; no dice.
At this point I'm considering throwing my phone at the wall and running over it a few times to cash in on my warranty and maybe even have a shot at getting a captivate with a working gps.
Click to expand...
Click to collapse
I recommend you install SDK and install the Nexus S drivers with it. Its stupid but considering CM7 is based of Nexus S phone those drivers might be needed. On other cases it seemed to help.

prbassplayer said:
I recommend you install SDK and install the Nexus S drivers with it. Its stupid but considering CM7 is based of Nexus S phone those drivers might be needed. On other cases it seemed to help.
Click to expand...
Click to collapse
Odin is seeing my phone after doing this.
I love you

moorent said:
Odin is seeing my phone after doing this.
I love you
Click to expand...
Click to collapse
lol Glad to hear its working, best of luck. On a side note I really do recommend sticking with I897 roms they tend to work better with the phone. I9000's ported ones would be a close second for GB. Just my 2cents. Im a big fan with Cyanogenmod on other devices like HTC and Motorola, but on SGS they still need some work ^^

I've already got cognition 5 up and running.
I've always been happy with designgear's stuff

[Q] Another fastboot issue (i have searched everywhere..)

First off,
I love this site, I normally come here to troubleshoot my issues w/ eletronics and always helpful... Thank you!
That being said.... here is my issue:
I have searched every thread i could find... tried everything I could, and still am having difficulties:
My verizon LG revolution is stuck in fastboot, but completely unable to get out. I have followed the instructions by TheCubed here:
http://forum.xda-developers.com/showthread.php?t=1131671
arvinoids here:
http://forum.xda-developers.com/showthread.php?t=1088046
and mazodude here:
http://forum.xda-developers.com/showthread.php?t=878786
Backstory...
I was unrooting my Revolution (which had gingervolt on it) because I have a replacement on its way (not getting here till thursday though)... My phone had kept randomly turning off every 20 min or so.
While using LGNPST i began to have the v7.tot file installed on the phone... my computer froze at about 17 percent, then the phone shut down (my computer had to be restarted at this point).
I got the pc up and running again and then hooked up the phone, which is now not showing in LGNPST. powered phone on and got:
Fastboot mode started
USB init ept @ 0x3e000
smem ram ptable found: ver: 0 len: 6
fastboot_init()
fastboot maximum download size : 450 mbytes
udc_start()
--reset--
--suspend--
--portcharge--
--reset--
--suspend--
--portcharge--
--reset--
--suspend--
--portcharge--
I have tried the Fastboot erase recovery (and flash recovery)
on the phone screen i got :
error no.2: failure sending write command to the fastboot
On the computer screen I got :
FAILED (remote: failed to erase partition)
I have followed the 3 threads above to a t... Has this happened to anyone else? Is there a way I can force the v7 (or older) firmware to the phone without LGNPST?.... I need this phone functional for the work week (as well as being functional when I turn it in...)
Thank you so much for the help in advance. I look forward to posting on here more often now!
I apologize if the answer is out there. I have 5 different tabs with the resolutions given actually fixing the issue, but havent seen anyone run into this yet..

Iration_Sti said:
First off,
I love this site, I normally come here to troubleshoot my issues w/ eletronics and always helpful... Thank you!
That being said.... here is my issue:
I have searched every thread i could find... tried everything I could, and still am having difficulties:
My verizon LG revolution is stuck in fastboot, but completely unable to get out. I have followed the instructions by TheCubed here:
http://forum.xda-developers.com/showthread.php?t=1131671
arvinoids here:
http://forum.xda-developers.com/showthread.php?t=1088046
and mazodude here:
http://forum.xda-developers.com/showthread.php?t=878786
Backstory...
I was unrooting my Revolution (which had gingervolt on it) because I have a replacement on its way (not getting here till thursday though)... My phone had kept randomly turning off every 20 min or so.
While using LGNPST i began to have the v7.tot file installed on the phone... my computer froze at about 17 percent, then the phone shut down (my computer had to be restarted at this point).
I got the pc up and running again and then hooked up the phone, which is now not showing in LGNPST. powered phone on and got:
Fastboot mode started
USB init ept @ 0x3e000
smem ram ptable found: ver: 0 len: 6
fastboot_init()
fastboot maximum download size : 450 mbytes
udc_start()
--reset--
--suspend--
--portcharge--
--reset--
--suspend--
--portcharge--
--reset--
--suspend--
--portcharge--
I have tried the Fastboot erase recovery (and flash recovery)
on the phone screen i got :
error no.2: failure sending write command to the fastboot
On the computer screen I got :
FAILED (remote: failed to erase partition)
I have followed the 3 threads above to a t... Has this happened to anyone else? Is there a way I can force the v7 (or older) firmware to the phone without LGNPST?.... I need this phone functional for the work week (as well as being functional when I turn it in...)
Thank you so much for the help in advance. I look forward to posting on here more often now!
I apologize if the answer is out there. I have 5 different tabs with the resolutions given actually fixing the issue, but havent seen anyone run into this yet..
Click to expand...
Click to collapse
I personally don't know how to fix it but I do have an idea on how to explain what is wrong with the phone if Verizon says anything Just say it was doing one of it's reboots and rebooted into that Let them deal with the issue. As for you not having a phone I'm clueless on that

Is this phone still under one year warranty with Verizon??
Sent from my VS910 4G using Tapatalk

Haro912 said:
I personally don't know how to fix it but I do have an idea on how to explain what is wrong with the phone if Verizon says anything Just say it was doing one of it's reboots and rebooted into that Let them deal with the issue. As for you not having a phone I'm clueless on that
Click to expand...
Click to collapse
Yeah I had that part pretty much down... I think i will be all set there as they know I am returning this one because of the frequent rebooting. I just hope when they get it all powered up that it doesnt say "gingervolt" haha. (I believe I am getting a droid charge sent to me as a replacement because this is my 5th revo... I had been having the issues where the screen was black and only the softkeys were lit up...)
Thanks though! I will keep trying different tactics with the command prompt (seeing that LGPST doesn't recognize it... I primarily need it because I do a lot of my work stuff on my phone when I am on the road. This will make this week tricky...

jackpot08 said:
Is this phone still under one year warranty with Verizon??
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Yes, It is, and I am getting a replacement sent to me (but they need to order from the warehouse to get the back/battery because I am getting a Droid Charge I believe...
The only issue is that I need the phone for work... My replacement won't get here till Wednesday-Thursday.

Iration_Sti said:
(I believe I am getting a droid charge sent to me as a replacement because this is my 5th revo... I had been having the issues where the screen was black and only the softkeys were lit up...)
Click to expand...
Click to collapse
FYI That isn't a "fixable" issue persay. It's something that happens on GB

Haro912 said:
FYI That isn't a "fixable" issue persay. It's something that happens on GB
Click to expand...
Click to collapse
Yeah I found that out the 4th new phone I got.... haha. I got used to that, in fact, that didnt happen with this phone. This phone just shuts off on its own every 20 minutes... haha

I've had a person fix their phone following these instructions:
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse

adrenaline_rush said:
I've had a person fix their phone following these instructions:
Click to expand...
Click to collapse
Thank you... but that is where I have been running into issues, I actually have that thread in my OP i think... It is not allowing me to push through cmd.
I am getting all types of errors through command prompt.

Shots in the dark here, but maybe uninstall/reinstall the driver and/or try another USB cable.
Sent from my VS910 4G using Tapatalk

Idk if this is mentioned anywhere or has been tried yet. But if cwm is still on the phone try to boot into it and mount /system. see if it will let you do anything that way.

jackpot08 said:
Is this phone still under one year warranty with Verizon??
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
As the phone was released in May... It is still under the 1 year...

Haxcid said:
As the phone was released in May... It is still under the 1 year...
Click to expand...
Click to collapse
+1 Nice smartass answer that no one else seemed to think of

Haxcid said:
As the phone was released in May... It is still under the 1 year...
Click to expand...
Click to collapse
Haro912 said:
+1 Nice smartass answer that no one else seemed to think of
Click to expand...
Click to collapse
Warranty is only available to the original buyer... (?)
VS910 4G Kangwich

Iration_Sti said:
Thank you... but that is where I have been running into issues, I actually have that thread in my OP i think... It is not allowing me to push through cmd.
I am getting all types of errors through command prompt.
Click to expand...
Click to collapse
You the Android SDK installed with the Platform-Tools add-on? Also the JDK installed? Also the three files AdbWinApi.dll, fastboot.exe, and the Clockwork recovery.img together in the same folder?

adrenaline_rush said:
You the Android SDK installed with the Platform-Tools add-on? Also the JDK installed? Also the three files AdbWinApi.dll, fastboot.exe, and the Clockwork recovery.img together in the same folder?
Click to expand...
Click to collapse
Just double checked and yes... still coming up with the same error. Unfortunately I think that the phone has no OS right now... I mean, it was an unrooting process throwing on v7, which means if v7 failed, even my rooted firmware is no longer on the phone.. right?
Edit: the reason i believe i dont have a recovery to begin with is it is failing under the command erase recovery...

S.Meezy said:
Warranty is only available to the original buyer... (?)
VS910 4G Kangwich
Click to expand...
Click to collapse
You just have to be awesome and you can get around that

Haro912 said:
Idk if this is mentioned anywhere or has been tried yet. But if cwm is still on the phone try to boot into it and mount /system. see if it will let you do anything that way.
Click to expand...
Click to collapse
There is no recovery at all.... only fastboot. It will bring me to the screen where it wants me to confirm deleting all data. but after that goes straight to Fastboot... no idea... never seen anything like it haha

Iration_Sti said:
Just double checked and yes... still coming up with the same error. Unfortunately I think that the phone has no OS right now... I mean, it was an unrooting process throwing on v7, which means if v7 failed, even my rooted firmware is no longer on the phone.. right?
Edit: the reason i believe i dont have a recovery to begin with is it is failing under the command erase recovery...
Click to expand...
Click to collapse
Sounds like this issue is deeper than most have experienced, being that it has to do with the .tot failing and not just a corrupt recovery installation.
Can you get to the battery charging screen? On my phone the battery charging screen comes up and the LG program was ready to flash the phone

Originally Posted by Iration_Sti
Just double checked and yes... still coming up with the same error. Unfortunately I think that the phone has no OS right now... I mean, it was an unrooting process throwing on v7, which means if v7 failed, even my rooted firmware is no longer on the phone.. right?
Edit: the reason i believe i dont have a recovery to begin with is it is failing under the command erase recovery...
Click to expand...
Click to collapse
Sounds like this issue is deeper than most have experienced, being that it has to do with the .tot failing and not just a corrupt recovery installation.
Can you get to the battery charging screen? On my phone the battery charging screen comes up and the LG program was ready to flash the phone
Click to expand...
Click to collapse
nothing ended up working... Hopefully verizon doesn't penalize me for it but my lg went in the mail today. Got a Droid Charge and enjoying it fairly well. Ill still jump in these forums to assist when I can and say hi.
Thanks again to everyone, meaning EVERYONE in these forums. Those who created roms, roots, themes. Those who assist, help guide, and answer questions. Big applause. Talk to you all soon!
Sent from my SCH-I510 using XDA App

Totally Confused/Need help!!

So, i got an HTC ONE in august or so, and then i had it rooted last month or so, but i didnt really do anything. The problems all started going downhill last night. I was looking on how to update it to 4.3 Jellybean, and when i downloaded the ZIP, i went to my recovery(Teamwin or something) and installed it, but after that ,my phone would use like a black screen and not everything would work. So somebody suggested that if that occurs, factory reset your phone, or wipe it. And i did both, and then i ended up here. I have No OS, my screen is stuck on the "HTC-QUIETLY BRILLIANT" Page, and nothing works. The only thing that i can access is my bootloader and my recovery, etc. I am what you guys may call a half-way noob, i know a lot, but this topic is totally confusing the heck out of me. If somebody could help me fix this, i would owe them so much. Please help out a fellow HTC Oner.
-Harchint

harchint said:
So, i got an HTC ONE in august or so, and then i had it rooted last month or so, but i didnt really do anything. The problems all started going downhill last night. I was looking on how to update it to 4.3 Jellybean, and when i downloaded the ZIP, i went to my recovery(Teamwin or something) and installed it, but after that ,my phone would use like a black screen and not everything would work. So somebody suggested that if that occurs, factory reset your phone, or wipe it. And i did both, and then i ended up here. I have No OS, my screen is stuck on the "HTC-QUIETLY BRILLIANT" Page, and nothing works. The only thing that i can access is my bootloader and my recovery, etc. I am what you guys may call a half-way noob, i know a lot, but this topic is totally confusing the heck out of me. If somebody could help me fix this, i would owe them so much. Please help out a fellow HTC Oner.
-Harchint
Click to expand...
Click to collapse
You need to get s-off then ruu your phone back to stock.
Here's how to get s-off
http://forum.xda-developers.com/showthread.php?t=
Here's how to ruu
http://forum.xda-developers.com/showthread.php?p=44017799
Sent from my HTCONE using XDA Premium 4 mobile app

Wait, What?
jab74101 said:
You need to get s-off then ruu your phone back to stock.
Here's how to get s-off
http://forum.xda-developers.com/showthread.php?t=
Here's how to ruu
http://forum.xda-developers.com/showthread.php?p=44017799
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Now, it says in the tutorial that you need to enable usb debugging and stuff, but how would i do that? All i need to do is install a stock rom so i can just get 4.3 and move on. I havent used my phone in a lonnng time and i need it very much!

harchint said:
Now, it says in the tutorial that you need to enable usb debugging and stuff, but how would i do that? All i need to do is install a stock rom so i can just get 4.3 and move on. I havent used my phone in a lonnng time and i need it very much!
Click to expand...
Click to collapse
I'm not an expert, but it doesn't seem too bad if you can get into recovery. First thing is to find out if you have a suitable ROM on the phone. If you inadvertently wiped internal data, you will probably need to sideload a ROM. If you do have a ROM on the phone AND you are sure it is one for the M7WLS, you can try flashing it again. If it were me, I'd download a stock rooted ROM and either sideload it or just push it via ADB. Your problems might have been the result of a bad download or installing a ROM for the wrong phone. If you did indeed flash a GSM ROM, the RUU is the way to go, but I've never messed with that process, so hopefully someone else will give you more details on that process.

harchint said:
Now, it says in the tutorial that you need to enable usb debugging and stuff, but how would i do that? All i need to do is install a stock rom so i can just get 4.3 and move on. I havent used my phone in a lonnng time and i need it very much!
Click to expand...
Click to collapse
Here use these for the drivers. Make sure you have no other drivers installed, if you do delete them and install those drivers. There should be a tutorial.