Whats up guys? First I just wanna say hi I am a new member and looks like you guys have a great little community here and I'm glad to be a part of it. I hope someone can help me out. Also, I did watch that noob video, I loved it. Before posting this I have searched found some similar but according to that video service provider matters. I guess no one uses virgin mobile..
Alright, so I have an HTC one S that I have had for almost a year now, bought it brand new through virgin mobile. I used for a while and liked the phone but my buddy at work had a galaxy phone and could do so much cool stuff with his that I wanted to do the same. So one day at work he came to this site and "Rooted" my phone. He was suppose to put a different operating system on it too but never did get around to it (he quit before he could). I didn't know him outside of work so I was stuck with just the root which is cool and all but now jellybean has just come out for my phone about 2 weeks ago. But here's where the problem lies, I go to update my phone and the download and install looks like it goes fine, the phone is plugged in while i update, When the phone restarts after the install, the update is not on it and my phone asks me again to update. I've tried this dozens of times with the same result. I have reformatted my phone in the settings and I lost everything I had on it, but that's no big deal. What I ultimately want is for this update to go through. My question: Is there any thing I can do so that it finally updates to jellybean and this damn notification goes away? Sorry if this is a noob question but I'm really stuck and don't have a lot of techie friends that can help me out.
Thanks in advance
Age
I think your problem is that you're not on the stock recovery. Official updates require stock recovery to be properly installed.
To fix this, first download this http://d-h.st/rZW . It's the stock recovery image. Next you'll need fastboot executable on your computer. This comes with android sdk (google it) but i believe can also be found separately. Then you flash the stock recovery on your phone by first booting your phone into bootloader (by pressing volume down and power button when device is shut down) and then entering fastboot mode by selecting it in the bootloader and finally running a command: fastboot flash recovery ville_recovery_signed.img. Now your phone should be able to install the update.
Option two: as your phone is rooted, you could probably also use an app called flash image gui. It's available in the themes and apps subforum. With it you just first download the file from http://d-h.st/rZW on your phone, then open the flash image gui, browse the downloaded img and flash. After a reboot the update should install.
Please note that I quickly googled for recovery image and even though its named like the correct recovery img I'm not 100% sure its legit. Here in he forums are links to the correct stock recovery if you look around a bit.
Hope this helps!
Sent from my One S. Please hit thanks if I helped.
stonedage said:
Whats up guys? First I just wanna say hi I am a new member and looks like you guys have a great little community here and I'm glad to be a part of it. I hope someone can help me out. Also, I did watch that noob video, I loved it. Before posting this I have searched found some similar but according to that video service provider matters. I guess no one uses virgin mobile..
Alright, so I have an HTC one S that I have had for almost a year now, bought it brand new through virgin mobile. I used for a while and liked the phone but my buddy at work had a galaxy phone and could do so much cool stuff with his that I wanted to do the same. So one day at work he came to this site and "Rooted" my phone. He was suppose to put a different operating system on it too but never did get around to it (he quit before he could). I didn't know him outside of work so I was stuck with just the root which is cool and all but now jellybean has just come out for my phone about 2 weeks ago. But here's where the problem lies, I go to update my phone and the download and install looks like it goes fine, the phone is plugged in while i update, When the phone restarts after the install, the update is not on it and my phone asks me again to update. I've tried this dozens of times with the same result. I have reformatted my phone in the settings and I lost everything I had on it, but that's no big deal. What I ultimately want is for this update to go through. My question: Is there any thing I can do so that it finally updates to jellybean and this damn notification goes away? Sorry if this is a noob question but I'm really stuck and don't have a lot of techie friends that can help me out.
Thanks in advance
Age
Click to expand...
Click to collapse
You can not because your recovery isn't stock so you have to download ruu or ota and flash it vie cmd
Thanks alot guys for the quick reply im going to try this out now. may take me awhile as it looks like i have alot to learn to do this by myself but im sure ill figure it out. and i hit both your little thanks button
All right so after trying both of those out I am still stumped. When I try my first option that adb sdk program package and tried to use the fastboot program on it I get an error. Now I typed this error into your forums and searched around and found some hope but once tried it still didn't work. It's an .".dll" file is missing when I get home to a computer I'll post a link for it. I do understand the steps just this fastboot program won't load.
Now option 2 is what really messes me up because I swear my phone was rooted but I'm scared from trying to factory reset this phone so may ways I may have it only half rooted if that's what its called. Because after I bought this IMG flash program downloaded the image to my phone the program says that there no root so I downloaded and payed for another of this dudes apps that tells me if my phone is rooted and it says sorry has no root access. But if my phone has no root access then why would it boot into that teamwin screen...
I even took a 3rd option and clicked the phone image button on the teamwin start screen. After that flashes I get another error saying that it didn't work so my question now. Is my phone even rooted? And have I ruined anything so far like could I send it in for warranty or is it considers tamperd.
I have tried to explain this the best I can apologize for spelling mistakes. But any help or suggestions would be greatly appreciated.again thanks in advance.
Sent from my HTC One S using xda app-developers app
Install htc sync on your pc to get the drivers. Then download viper ROM along with its boot.img flash script. Flash viper through that "team win thing" (lol
Then put your phone into bootloader, then fastboot USB connected to pc and run the boot.img flash script.
That would be about the easiest way to get jellybean on your phone.
Pm me if you need more help our can't find links.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
So last night I emailed the creator of the app I used to check my root and here is the msg I got back. Today is a day off and I'm just spending the day browsing the forums and looking for the right tools to fix it. if you get this in mean time can you maybe help to point me in the right way. I really don't want to bug you guys on this forum I know how you hate people like me but I live in a small town and am really relaying on this forum to completely teach me everything from scratch. hopefully without bricking my device that's sounds horrible. Here's my email I got back.
Hi,
The Root Checker Pro results show the device does not have root access setup and unless you've erased and re-installed Android, the device appears to have never had proper root access. I would suggest relying on the same forum to locate the latest and most accurate directions on unlocking the internal memory write protection and then gaining proper root access.
Flash Image GUI will loading custom kernels and assist with loading custom ROMs on devices that have internal memory write protection, such as your HTC One S.
Thanks for the support!
Joey
Sent from my HTC One S using xda app-developers app
Sent from my HTC One S using xda app-developers app
oh and here is the results from my root test.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your HTC One S device by Root Checker Pro version 1..3.1 from joeykrim in the Android Market -
Is your bootloader unlocked? You can check by (with your phone on) hold "volume down" and "power" until button lights at bottom start blinking and the screen turns off... At that point let go of the power button but keep holding the volume down button And eventually you will see the boot loader screen. At the top of the screen it will either say locked or unlocked. Check and report back.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Ya its unlocked but now thats the only screen i can get to i tried to flash that stock image and when i did my phone went into some scfeen that showed a phone and some triangle with an explanation mark. my phone either boots up now to a htc quietly brilliant screen or if i hold the volume down button when its off it goes to that boot-loader screen that shows unlocked and tamperd at the top this is all i really know. Guys im sorry im trying to act like i know what im talking about but in all honesty i really have no idea. im really just pissed now that i even touched it cause it was working fine before besides the wifi constantly shutting down and bugging me to update to jelly bean. I honestly really shoudnt be here i just really wanted my phone fixed and i cant find anyone to pay localy to do it for me so thought i would try to do it with google but now im here. please just tell me if this phone has just become an expensive coaster AKA garbage thanks again for all the help.
stonedage said:
Ya its unlocked but now thats the only screen i can get to i tried to flash that stock image and when i did my phone went into some scfeen that showed a phone and some triangle with an explanation mark. my phone either boots up now to a htc quietly brilliant screen or if i hold the volume down button when its off it goes to that boot-loader screen that shows unlocked and tamperd at the top this is all i really know. Guys im sorry im trying to act like i know what im talking about but in all honesty i really have no idea. im really just pissed now that i even touched it cause it was working fine before besides the wifi constantly shutting down and bugging me to update to jelly bean. I honestly really shoudnt be here i just really wanted my phone fixed and i cant find anyone to pay localy to do it for me so thought i would try to do it with google but now im here. please just tell me if this phone has just become an expensive coaster AKA garbage thanks again for all the help.
Click to expand...
Click to collapse
I think what you should do is:
- find ruu matching to your carrier and download it
- relock the bootloader
- flash stock recovery
- boot into bootloader and go to fastboot mode
- connect use cable and wait till phone screen shows fastboot usb
- run the downloaded ruu.exe on pc and wait for it to complete
- on successful completion your phone will be same as you got from a store
Just note that flashing ruu will cause hboot upgrade as well.
If my post helps, remember to use the thanks button.
Sent from my HTC One S using xda app-developers app
wouldnt that "ruu" be what the gentleman in the very first reply in option 1 gave me? i have the file and tried flashing with the one button root tool kit by hasoon2000 i clicked on flash recoveroy then chose the file ville_recovery_signed.img. and let the black screen (beleive its called cmd) do its thing but really it looks like its doing nothing and my phone wont boot up the main screen where i can receive texts or make calls. thanks
Ok so i found a friend that understands the way you guys have explained this. Now the unfortunate part is that the virgin mobile (canada) RUU file is extreamly difficult to find. So my question now is do you know where i can find this file i have searched the forums and google but with no luck. im sure once we find this file my phone will be fixed then im not touching it AGAIN! cant explain how much i appreciate all your guys help and patience with me.
Thanks again
Adrian
Help!!!
I am having the same issue as described only I relocked my my phone.
***TAMPERED***
***RELOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 20 2012,151418
I try to fastboot flash recovery or even the boot image and I get
(bootloader) signature checking...
FAILED (remote: signature verify fail)
I cannot seem to find an ruu for my phone from telus and trying to flash the recovery will not work. Any help would be greatly appreciated.
I emailed HTC and asked for it. if i get it i will send it your way.
Heres my email back does this mean that my phone is broken and garbage now or could i flash it with rogers/telus/bell and then sell it to someone on that service provider or even switch mine???
Dear Adrian Berdux,
Thank you for reaching the HTC Tech Support Team with your inquiry, I’m here to make sure all your questions and doubts are cleared.
In regards of your request, the Jelly Bean RUU for the Virgin Mobile HTC One S is not yet available, nevertheless on the following link, you will be able to find all the Jelly Bean RUU's available for your device:
http://www.htcdev.com/devcenter/downloads/P10
Adrian, if you need further assistance, please do not hesitate to contact us, I’m here to make sure all your questions are addressed in the most efficient way.
Thank you for choosing HTC.
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Ash
HTC
Done
Finally got it, reunlocked my phone, pushed out a stock recovery image using the One S all in one tool and was able to download and install the update.
really and you where in the same position as me but on telus right? My phone is still broken but is it good hands at the moment so hope its fixed soon really starting to miss having it.
Mine is the S3 model and its not rooted but the bootloader says it RELOCKED. So I get the notification yesterday and whenever I try to update it keeps rebooting back to the bootloader. Any solution?
Related
Hi guys, I'm new here.
I have a problem... And I have tried very hard to find a fix over the past few days, but no result. So here I am.
I have a HTC Hero, which was running Android v2.1-update
I rooted it, and used a corrupted rom.
Now I cannot use it. When I start the phone, it takes ages to load, then I am presented with a strange unlock screen. I unlock it, and I am presented with a white HTC-Logo screen. If I wait long enough, a menu appears asking me which update to apply. I select the first, and I am given a choice of 3 languages. I select English, and hit Next. This is where I am stuck. I have an o2 simcard (which works fine) and it doesn't detect it. It keeps asking me to insert the simcard with an animation on how to do this.
I'm not sure if this could be called "Bricked" as I don't really know the meaning of the term, but either way, a Brick is the only thing it's good for right now.
I am desperate for some help. I have just bought it and am feeling kinda sick now. I learned my lesson. Don't Root!
Thanks in advance!
Well..."don't root" is not really a lesson, just when you do something next time, you have to make sure that you are doing everything correct, and following 100% the guides that you find here in XDA..
My Hero is rooted since I bought it...
Anyway, Do you have recovery installed? Amon RA or clockworks?
To find it out, just turn off you phone and press Home+Off button for a few second, then it will go into recovery.
From there you can copy another rom and flash it.
I am currently using Elelinux 3.6, but you can find many others.
By the way, which rom did u flash?
Hi, thanks for the fast reply
I cannot get onto the homescreen to install any apps at all, so all I got to work with is the recovery menu. Fast Boot and SimLock.
I installed what I now know to be a new lockscreen, which was about 2.5mb. So obviously not right now, but I rushed into it without looking things over properly.
I might be able to fix it, if the simcard was detected. It stops me at that point during recovery.
I rooted the device using a terminal app, but as the data has now been wiped, the app doesnt exist. And I cant reinstall it again because I cannot get to the homescreen.
You don't need to install any app, I don't understand if you have recovery installed or not.
Just press home+off button for a few seconds when your phone is OFF.
What do u see?
That gives me the red ! sign, and I can get a menu up by pressing volUp+off
This menu has Fast Boot and SimLock.
Yes, that is the normal bootloader, that means you don't have recovery installed.
You could try to unroot your phone by install the HTC sync software on your PC first, then use it to reinstall the stock RUU 2.1, that you can find on the HTC website:
http://www.htc.com/nl/help/htc-hero/#download (change the language)
Once you have done that, you should be able to root it again if you want, but make sure you will install recovery this time.
Look for the guides in the Hero forum, or you can use this:
http://www.villainrom.co.uk/forum/threads/how-to-root-the-2-1-ruu-or-ota-update-for-the-hero.1930/
Hi. I found this a while ago, and tried it. But I cannot enable USB Debug, as I cannot do ANYTHING on the device...
I just ends up giving me a 170 error, always.
Are u talking about the HTC sync driver?
Yes. I think so.
RUU_Herrange_UK_2.73.61.66_release_signed_NoDriver.exe
It starts a utility up which tells me to make sure the device is connected via usb to my pc, check battery is 30% or higher and something else.
Then it tells me to wait, and returns a 170 error.
Then you should check the HTC Hero forum or Google for any suggestions, I am sure people had the same problem in the past.
I am afraid I can't help you more than this, I am no developer..
Okay, thanks anyways
I have already raked Google and help forums, coming here is my last resourt.
Keep searching, I am sure there is a way to fix it, I have read so many things about the Hero in this two years, unfortunately I forgot most of it...
Sent from my Hero using xda premium
I will do. I have no choice, the warrantly is now void xD
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!
What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD
Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.
It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?
Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89
Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.
opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...
Now quicker and easier!
Please note, this CAN brick your phone. Do not proceed if you are not confident in your ability.
Any damages caused are your own problem and I withhold any liability for any future issues caused by this process
Just a small note, I am aware of the screen in recovery moving, this is because of HTC's framebuffer method, I haven't been able to fix it yet.
1: Unlock your phone at the htcdev site, follow the instructions on the site
2: Download the following two files. Download either ClockworkMod Recovery for ICS OR Clockworkmod Recovery for JB depending on which version you are on and Superuser.zip, Move the Superuser.zip to somewhere on your phone's SD card.
3: reboot your phone into hboot and then into fastboot if you are not already there
4:
Code:
fastboot flash recovery recovery.img
this is presuming the recovery.img is in the same directory as fastboot, you can either move it or point the code to it directly
5: open recovery.
6: Flash the superuser.zip through recovery
7: reboot
8: Congratulations, your phone should now be rooted, go have fun with the ability to access your phone fully!
Edit: Here is a copy of the stock recovery recovery_signed.img
For those who want to install busybox, check out this post.
Also, due to the current issues I still haven't had the time to fix I'd suggest using the TWRP recovery for the time being.
Re: [GUIDE] Root for HTC One SV
Define 'slightly'.
Sent from my HTC One SV using Tapatalk 2
I did it thanks
but I want to do a backup for my rom and as you know cant do it through cwm is there any solution?
caseyjp11 said:
Define 'slightly'.
Sent from my HTC One SV using Tapatalk 2
Click to expand...
Click to collapse
Slightly in that the Clockworkmod recovery isn't fully functional (power as select does not work) and as such is missing some features.
Fatadxb said:
I did it thanks
but I want to do a backup for my rom and as you know cant do it through cwm is there any solution?
Click to expand...
Click to collapse
I'd suggest installing busybox and using something like this , it's how I'm backing mine up currently.
Hello. Thank you very much for your guide, my One SV is now rooted. But I can't install Busybox ("Installing Busybox failed")... Can you tell us how we can install it ?...
Additional info please.
Hello do we leave the phone in recovery while we finish the code for rooting or should we be in the bootloader, fastboot still, or should the rom be booted up. I just wanna make certain so I dont Brick this thing.
---------- Post added at 01:36 PM ---------- Previous post was at 12:36 PM ----------
I have got bootloader unlocked, recovery pushed and installed. Now I have unknown device in device manager named k2u that wont intall drivers. I cannot connect via adb shell because it cannot find device??? Any Ideas??
I had the same problem, and after multiple tries I finally find a solution : install HTC Sync, then edit the androidusb.inf file (in my case, the path is C:\Program Files\HTC\HTC Driver\Driver Files\Win7_x86\androidusb.inf) and add in its "Device section" a line with the ID number of the One SV (you can find it in the Device Manager on your PC) :
%MyHTC%=HTCAND32.Dev, USB\VID_0BB4&PID_0D0F&MI_00
Then, restart your PC, reboot your phone in recovery and connect it, Windows must install "new" driver and recognize it as "My HTC", and you can root your smartphone with the guide of bkcokota. It's the only way I've found, but perhaps there is an easiest solution ?
(Sorry for my bad english... I hope that you'll understand what I wrote !)
Crap....
Fabriel said:
I had the same problem, and after multiple tries I finally find a solution : install HTC Sync, then edit the androidusb.inf file (in my case, the path is C:\Program Files\HTC\HTC Driver\Driver Files\Win7_x86\androidusb.inf) and add in its "Device section" a line with the ID number of the One SV (you can find it in the Device Manager on your PC) :
%MyHTC%=HTCAND32.Dev, USB\VID_0BB4&PID_0D0F&MI_00
Then, restart your PC, reboot your phone in recovery and connect it, Windows must install "new" driver and recognize it as "My HTC", and you can root your smartphone with the guide of bkcokota. It's the only way I've found, but perhaps there is an easiest solution ?
(Sorry for my bad english... I hope that you'll understand what I wrote !)
Click to expand...
Click to collapse
Where can i find the id in device manager.. No HTO One sv listed... Only one listing is My HTC which appears to be fully loaded and functioning. I have htc sync loaded and running i cant adb anything.... Man I am no newbie at this at all but, this is really confusing me!! I hope xxdjvalexx the O.P. Dev pm's me back with some help... I will prevail though!!
The ID is in device manager when you connect your One SV to your PC in recovery ; it's the ID of the "unknown device" named "k2u"... It's normally USB\VID_0BB4&PID_0D0F&MI_00, as I said in my last post.
Open Sesame!!!
Fantastic, Awesome and overall a Great Experience! I have learned a lot over the years with XDA and friends. Patience, is the key oh and reading.. I cant wait until the rom development blows up on this thing. When do you suppose xda will put up a official device development thread??
Probably sometime after it drops on sprint which has anyone heard? Anyway as indicated by my elation above root achieved with this device. Now just wait out the clockwork mod scene. I am on Cricketusers.com on the One SV forum there if anyone needs a helping hand or maybe a beta tester. Just let me everyone. I would love to give something back to this very awesome community I call home on most late evenings and early mornings.
I will be a very active member for this device here as well so hit me up I am constantly on TapaTalk with my phones.
Hooray and Cheers to all the Devs out there!!:highfive:. swes013
Re: [GUIDE] Root for HTC One SV
I'm glad you got it working, I've heard it is coming to Sprint soon but I don't know much more than that, Australia is a bit far away to get the best gossip, I don't know when our if we are getting a forum but considering the fact it hasn't even been out for even a month yet I'd say be patient, just for reference I don't know if this matters to you but I have called up HTC and had a chart to them about getting the kernel source, apparently they don't have out ready yet but it should be up "soon". Hopefully it is soon, I'd love to get cyanogenmod on this. I might drop by the cricket forums and see what is there.
Sent from my HTC One SV using xda premium
Re: [GUIDE] Root for HTC One SV
Alright guys and gals.... Another small update. Still obviously more obstacles and development will continue as the actual root access is only gained while the rom is powered up. After a power off shutdown, and reboot root is lost. Alas you cannot delete bloat ware apps using root file explorer pro. Also tried doing a few tweaks with my rom toolbox pro like, LCD density, configuring A2SD etc.... Any thoughts chime on in guys lets get this thing hashed out before Sprint gets it. That way all our further development can continue without any hiccups... It seems that without a working recovery the root we push with web will be a useless exploit... Alas at least for now!
Sent from my HTC One SV using Tapatalk 2
swes013 said:
Alright guys and gals.... Another small update. Still obviously more obstacles and development will continue as the actual root access is only gained while the rom is powered up. After a power off shutdown, and reboot root is lost. Alas you cannot delete bloat ware apps using root file explorer pro. Also tried doing a few tweaks with my rom toolbox pro like, LCD density, configuring A2SD etc.... Any thoughts chime on in guys lets get this thing hashed out before Sprint gets it. That way all our further development can continue without any hiccups... It seems that without a working recovery the root we push with web will be a useless exploit... Alas at least for now!
Sent from my HTC One SV using Tapatalk 2
Click to expand...
Click to collapse
In my case, the root isn't lost after a power off shutdown : I shutdown the phone every evening, and I've never lost root...
With SuperManager, I can modify system (the weather database for example), and Titanium Backup works perfectly. The only problem which I have is that I cannot install BusyBox.
Re: [GUIDE] Root for HTC One SV
wow I wonder what went wrong in my case?? Its like it only did a temp root kind of process. I may try to re root the thing again just to see but... I don't wanna fry this thing before I have had it for a little longer I think. You are on cricket
Wireless yes? I just don't know why mine wouldn't take a solid permanent root..?
Sent from my HTC One SV using Tapatalk 2
swes013 said:
wow I wonder what went wrong in my case?? Its like it only did a temp root kind of process. I may try to re root the thing again just to see but... I don't wanna fry this thing before I have had it for a little longer I think. You are on cricket
Wireless yes? I just don't know why mine wouldn't take a solid permanent root..?
Sent from my HTC One SV using Tapatalk 2
Click to expand...
Click to collapse
No, I'm not on Cricket Wireless (I'm French), and my ROM is stock HTC. Have you a specific operator ROM? Maybe it is the cause of the problem?
Hi guys, I'm just going to try my luck on this one.. As I see that you guys have managed to successfully rooted your phones, could someone please do a ROM/system dump and share it..? I would like to port this ROM on our devices. Thanks in advance.
Skanob said:
Hi guys, I'm just going to try my luck on this one.. As I see that you guys have managed to successfully rooted your phones, could someone please do a ROM/system dump and share it..? I would like to port this ROM on our devices. Thanks in advance.
Click to expand...
Click to collapse
Sorry, but it's not possible : the recovery isn't fully functional (see the previous posts), and personally I can't install BusyBox, so I can't make any backup or dump...
Fabriel said:
Sorry, but it's not possible : the recovery isn't fully functional (see the previous posts), and personally I can't install BusyBox, so I can't make any backup or dump...
Click to expand...
Click to collapse
Sorry to hear that.. But there's another way AFAIK that works. Using a Root Granted File Explorer (I use X-Plore), you can try to copy the "system" folder to ur sd card.. It "may" copy all of the files of system.. Can you do that for me?
Still cant achieve a permenant root.
Hello everyone, I still cant achieve a permenant root on this one sv. Some more info is that it is Cricket wireless Carrier specific got at a authorized cricket dealer on Like Jan 20 I think. So it saysy its rooted and su asks permission on all root level; apps however when i use root explorer to delete like say cricket nav and crkit mobile browser it deletes them.. they are gone. Until power down or, reboot then they are right back poof. Any bright ideas??
Android 4.04
HTC Sense 4.1
Software number 1.03.1050.5 710RD
Specks in case they help spark any idead although I doubt it...
---------- Post added at 03:39 PM ---------- Previous post was at 03:26 PM ----------
I still dont have a working root for this phone!! Has I tried this mod here and it seemed to work good. At least the for a minute or two. I then tried to delete some system apps I wanted gone with root explorer. It let me delete them just fine.. Wow just when i thought I was a happy man....BAM rebbot, Powerdown, and reboot, then root changes wont commit. All apks I deleted are back even though my root explorer pro said I was mouted to system as root..?? Funny hugh any help from mmaybe someone on cricket with this phone who achieved a permenant root can help me. Or maybe everyone here is waiting patiently for a working CWM recovery before they try and acieve root. Maybe I should have waited too. Alrhough I dont think I boirked my phone because it still works graet except my root level acess that i want so badly...
I saw this same problem with the HTC Droid DNA. I don't have the One SV, but I suspect that the stock kernel will not let you manipulate the /system folder.
With the DNA there was at least one dev that made a kernel which would allow you to change stuff. Also custom ROMs can have everything modified already. That would work as well.
Oh and which recovery are you using? Does it belong to another phone?
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
AndyA2098 said:
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
Click to expand...
Click to collapse
Thread closed as OP fixed his issue