Database Develop

[Q] Need help with restoring backup from ROM Manager

I've been searching, and reading, and my eyes hurt. I normally don't like to post threads, but I'm left with no choice. If this topic has been covered, then I guess my searchin' skillz are stating to lack. Here is my delimna:
Rooted, Lagfix, enabled Side-loading, recently installed ClockworkMod, stock firmware. I ran a backup using ROM Manager/ClockworkMod. I was attempting to install the Mobile AP fix for WiFi Hotspotting from designgears. I downloaded the new kernel per instructions (Mobile AP ony). I first tried installing it using ROM Manager's boot option into Clockwork without renaming MobileAP.zip. Still received black screen when I open the Mobile AP settings that the new kernel was trying to fix. So I thought that the flash didn't work, so this time I renamed the kernel file to update.zip and did the standard method of flash using stock recovery mode.
Now the phone boots to the Galaxy S screen, then just a black screen. The bottom row buttons seem to be active, but nothing happens. Holding power....nothing. I have to pull the battery; however, I can boot into stock recovery.
Now here's the delimna. I can boot into recovery, but the update.zip file is NOT the one for ClockworkMod, its the modified kernel. Is there a way that I can browse the files on the phone so I can change the update.zip file? I want to put Clockwork's in place so I can restore using my backup made yesterday....It's not a huge order if I have to flashback to stock and lose everything as I usually do that everynow and again anyways (usually I'm prepared). I won't lose anything important that isn't already backed up except maybe some pictures....
BUT, I can't help but try. It's just me I like to break stuff and fix 'em. I want to try to run that backup I made. I have Odin, and I tried flashing the kernel back to stock (i had one hell of a time finding information on how to use it). As a matter of fact, I found instructions on HOW to use it, but I gave up trying to find useful information on how the program runs (like a user guide, what else can it do, that sort of thing....). I spent hours reading thread after thread........information overload I guess.
I figured someone might point me in the right direction. How can I browse/edit the contents of the phone while in Recovery or Download mode?

You could try letting the phone boot up, yes I know it's only a black screen, then plug in the usb to your PC and see if ADB works.
If so then just adb shell into it and work with command line.
I'm not sure if ADB would work in stock recovery mode but that's worth a shot too.

Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?

swedishcancerboi said:
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
Click to expand...
Click to collapse
Wasn't sure if that would work or not.
So, if you turn it on and just let it sit as long as a normal boot, then try adb does anything work?

I actually let it sit for ~15 minutes. computer doesn't even register the usb being plugged in. I'm going to give it another go or two, but in about an hour I'm going to have to call it quits and just flash it with Odin. Don't want to give up yet, but I am driving out of town later this afternoon and must have my phone for the trip. Maybe I'll break it again tomorrow and play with it over the weekend!
Let me know if you have any other ideas. I'll let you know when I give up.

While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).

swedishcancerboi said:
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
Click to expand...
Click to collapse
Hybrid from eugene is pretty fast especially if you add the voodoo kernel to it. Thats what I heard tho. Because when i tried it out it was pretty quick with out a lagfix and without autokiller. Only used it for 20 min tho as i couldn't get Titanium backup to work. I think the titanium problem is a hit or a miss.

well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!

swedishcancerboi said:
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
Click to expand...
Click to collapse
Well, if your going to do that take an extra 2 minutes and load Eugenes Hybrid R3 while your at it. It's extremely easy to do and in my opinion the fastest thing we can put on these phones right now.

Vibrant ROM? is that safe? I mean, I know they are all Galaxy S, but is the hardware really that identical?

I don't think eugenes captivate hybrid is actually a vibrant rom. I think he just borrowed some of the better parts.
Sent from my SAMSUNG-SGH-I897 using XDA App

Got it! I used the one click stock down loader to get the phone to boot. I then noticed that many of my files were still there, music, zips.....so I thought....maybe my backup is still there.
Instead of using my original root, I decided to try Unleash the Beast.applied it so I could load Rom Manager.i opened Rom manager and it showed my backup!
I tried restoring then without success (no update.zip) and had to flash clockwork (even though it showed it already loaded, guess it needed to be refreshed, makes sense since it is a fresh firmware), selected my restore and it ran like a charm.
I am just surprised. I thought the act of flashing the Rom would wipe everything. Apparently not if you never do the "master clear."
Thankfully I had just installed Rom Manager the day before and had a fresh backup. Looks liked I'm gonna have to start shelling out more beer money to the devs!
Now I can prepare to break it again and again. Let the fun begin!
Sent from my SAMSUNG-SGH-I897 using XDA App

Nice. Yeah, stuff you have stored on your "internal SD" is safe between flashes. Of course apps, contacts, etc get wiped, but that's an easy fix.

"the more you know," eh? Ha!
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] N00b-danger to myself and others

I have searched this site for a few days trying to find some sort of answer...okay well an answer i can understand. but perhaps my n00banism is getting in the way. I've broken my nookcolor but it's not broken. yep. exactly. Here is my story:
I was able to root my nook thanks to theunlockr.com. I followed those directions and was able to get a nightly of cm7 (which i ran on my device for 3 months or so). when i tried to update to the stable version I kept getting an error message that the file was bad...i forget the exact wording. SOOO enter me, and my awesomeness. I found tipstir.the-talk.net and an option to load honeycomb on my nookcolor (which seems to be running fine btw). Somehow during that my clockwordmod rom manager was missing. I hadn't yet loaded the gap pack so i went online to the android market and downloaded it. yay. I tried to 'reboot into recovery' to load or 'flash'...but it just reboots normally.
I have since found that the kindle app and aldiko (which is the only app i've found that will read my old sony ereader books) just wont run on honeycomb which makes it all but useless to me since i use this primarily as an ereader.
I dont know what to do to fix the situation that i've found myself in. I think i read somewhere that you can load cm7 on an sd card and run it...but how then would I fix the situation that i've gotten myself into?
yhea...i have just enough interest in these sort of things to get myself in trouble, but not enough practical knowledge to get myself out of the pickles. SO please help the lame and powerless!
Thanks so much
Mikaela

The most surefire fix is to make a cwm card, flash back to your stock firmware, then either use cm7 on the card or install it on your nook(emmc). Basically, treat it like you bricked it. There are quite a few threads that can tell you step by step how to do it.
Sent from my NookColor using XDA Premium App
Edit : go to the stickies tab and look, there's a thread with all the info you need

Have you tried to download Rom manager, and then download clockworkmod from within clockworkmod. Then reboot into recovery from Rom manager. Probally, just trying to help.
Sent from my Optimized Shift using XDA App

fix!
I went back to theunlockr.com and reset back to factory settings and essentially re-rooted the device from there. =) i dont know why i didn't think of that in the first place but *someone* pointed that option out to me. thanks for the help!

Help the Hapless...

I got a Viewsonic Gtab last year (Model# UPC300-2.2) and was not happy with the stock OS limitations so...like a Wet Ear Noob I watched a few vids and read a few posts here and thought I could do it all myself. Yeah...now I have a 1lb paperweight. Been trying to fix it ever since. I have tried to follow the various posts and links to even get it to factory restore settings but I think it's dead like Disco.
Might there be a person out there willing to baby-step me through this? I got to warn you I'm a hardware guy not a coder. I bricked this trying to install CLOCKWORK for pete's sake.
I'm still looking to put Clockwork on and some other OS that allows more Flexibility like Vegantab. Sadly I don't know what's even left on the poor girl.
Regards,
CW

Have you tried the gtablet for dummies website yet?

tenet420 said:
Have you tried the gtablet for dummies website yet?
Click to expand...
Click to collapse
Never knew there was one. I was directed here so... thanks I'll look.

http://viewsonic-gtablet-for-dummies.webs.com/

I was there once. But these devices are hard to completely brick. From what I remember, u need to boot to a certain download mode. The screen will stay black, but it will be in download mode, the way u would know is when u see your computer recognizing the tablet. Remember, its the mini usb cable to your pc. Hope this helps
Sent from my SPH-D700 using XDA App

NVflash is where you'll want to start.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
It's a full reset, and you can even install clockwork at the same time. I recommend the 1.2 branch with clockwork installed (you'll see that on the tutorial above).
Once your nvflashed with clockwork installed you can use the other tutorials on the site to flash your rom of choice.

[HOWTO] Boot Ouya Into CWM/Flashing ROMs

First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!

Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
Click to expand...
Click to collapse
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?

glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app

glitchhawk said:
just as an add: my Ouya did not detect a exFAT MicroSD in a USB reader. Maybe CWM only works with some formats?
Click to expand...
Click to collapse
Ouya-XD said:
I do believe there's been a certain format to use, though I'm unaware on how this works.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.

Rirere said:
FAT32 is more or less the "golden" standard for portable devices. glitchhaw, you are aware that exFAT is one of the most laughably locked down filesystems for portable devices out there, right? If you're being official at all, you have to pay royalties to Microsoft to be able to work with exFAT, and I doubt OUYA built support in for that.
Click to expand...
Click to collapse
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.

glitchhawk said:
i know that I don't like exFAT and that its annoying and glitchy sometimes with android.. but I don't like the fat32 4gb limit.
i wish CWM/TWRP worked with NTFS or EXT, at least they are more reliable.
Click to expand...
Click to collapse
NTFS support can be added at the kernel level, but I don't know of any recoveries that support it, sadly. And that's unfortunately the nature of the beast, and probably why many recoveries will break files up into multiple archives.

Go full *nix and use ext4 like a man... Unless you're a woman, then use it like a woman.
Sent from my SAMSUNG-SGH-I317 using xda premium

I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?

B4 I updated I needed SU to make the reeboot. Feature work.
Sent from my Amazon Kindle Fire using xda app-developers app

that was my thought, however I just reran the .bat for cwm and flashed that way.

Kickbut101 said:
I am unable to get the unit to respond to Rom managers attempt at rebooting into recovery, I'll give the command via the app and it will just continue sitting there at the menu. CWM was successfully installed and I made a backup. I downloaded the app to my phone and then TB'd it and sent it to my device. did I miss something?
Click to expand...
Click to collapse
I'd assume if it's not working that way then to try the ADB method instead, again, please report all issues to me.
Do you have CWM installed, on a final note?
People cry a out signatures, there's no need for one! I love my community and will stand up for it!

App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app

Ouya-XD said:
First off, I wanna apologize if the has been discussed.
I see a lot of you broke your device by trying some form of method to fix the device in any fancy way.
I had a friend brick by trying the Cyanoboot method.
First off, assuming you have already got CWM installed via the tutorial that's been posted already.
Secondly, make sure you have some form of way to side load apps onto the device. Be it Dropbox, Google Drive, or maybe your using an ADB method.
Lastly, I have found this to be the easiest way.
So, let's begin. Please make sure you have a way of grabbing ROM Manager, back it up, download an .apk from a Google search or just port it from one device to another via an app.
Once you've found your method of getting the side loaded .apk let's make sure it's installed, any newer version will work(Older versions have been reported of not installing and allowing a proper clean reboot). So let's make sure it's a newer updated version, secondly test it and make sure the version you're using will reboot the device properly without issue. Working? Good.
Now let's use our nifty tool as soon as you have CWM installed, you should get a proper reboot!
This is good.
As a side note, I've had mine give issue and make me wait a few for a full reboot into CWM.
Now you're done!
Flashing ROMs.
It's just as easy as you'd think it'd be as long as you've got a properly packed ROM onto your device.
Note: If you're looking for a tut on porting the ROM, please check the Dev forum as there is a tut posted that is clean and simple using ADB.
Also, there are some that say you can using a cloud storage method.(Try it at your own risk!)
Once you've got your ROM onto Ouya you should check with an explorer to confirm that it was saved onto the device.(I have an issue of downloading things of the Internet with Ouya and them not showing up).
Now, using the method I first mentioned to get into CWM, do so.
You should see an option to search through your internal SD, this would be the next step as we can't/don't have any form of using an external SD, that is if you could connect a flash drive to the back and use it, though I can't confirm it would work.
Lastly, once you've scanned the internal SD and found your ROM, flash it. Sometimes this could take a bit, being my case it took 10m to install Ouya Plus.
If any issues occur, feel free to post and I shall try my best to answer anything!
If this was useful to you, I can only ask of a favor!
Check out my YouTube channel!
http://WWW.YouTube.com/user/TheDarkRosary​Subscribe if you will! I will be covering everything Ouya and doing news soon!
Click to expand...
Click to collapse
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta

TadeoNYC said:
I have to say this is probably the worst how to/tutorial I have seen on XDA.
If you're intent is to help users inexperienced with CWM, then you need to write clearly defined steps. The whole thing is vague. You don't give links to a single file or other tutorial, a how to shouldn't keep telling people to do a Google search for things. On four steps you make people search for files or another how-to.
What is the new version of Rom manager? How do you make sure it will reboot the device properly? Be specific.
You say flashing Roms is easy as long as you have a properly packed Rom. How does one go about checking that? How do you flash the Rom?
This is what a how-to is supposed to include. This is equivalent to just telling people GIYF and RTM.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app

Oscar_david said:
App: Quick Boot . reboot into fast boot, recovery, or shut down the console.
Sent from my SGH-M919G using xda app-developers app
Click to expand...
Click to collapse
Thanks man, I'll make sure to add it to the OP.
Sent from my HTC One VX using xda app-developers app

Ouya-XD said:
There's no need to bash peoples thread first of all.
And secondly, you'll be reported for this.
As of how to to do this, I can't always "be specific" like you want when I post a good amount of this from my phone, so do be prepared for a tut that's not fully helpful.
Lastly, I HIGHLY doubt that you've read every tut on here, and trust me, I've seen so much worse that go down to the nick of; "If you wipe and install first, this version will fully brick the device, this version will half brick it".
So explain to me, since I've made ROM packages, I've had more tuts than just this, what do you wanna see more in a tutorial from me? Tell me and I'll try my best to help.
Don't go barging in with the intent of anger in mind and begin bashing me to the fullest.
Most people PM me and I give them what they need if they can't find it, as for you? Nuh uh, after this, NO is my final answer.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta

TadeoNYC said:
You reported me for what? That your feelings are hurt?
Ostensibly you created this tutorial to prevent people from bricking their OUYAs. That is why I was expecting a detailed walkthrough and was very disappointed. You created a tutorial on your phone that is lacking vital info that I have already detailed. I did not bash you to the fullest. You admit that your tut is not fully helpful, and I've seen other comments on another tut of yours that were a great deal harsher than mine about your motivation to post a poorly written tut.
I apologize for the severity of my opening line. I was and am annoyed that the "how-to" does not provide any info vital to users so that they don't brick their OUYA. Every time they are sent elsewhere for a file or info there is a risk of getting bad info or a malicious or corrupt apk. I outlined a lot of the information I think should be included. If I had all the answers I'd have included those as well, but I am here because I thought I could learn something. Maybe I still will.
Edit: I see now what type of person you are and how helpful you can be. http://forum.xda-developers.com/showthread.php?p=43031832 so the next time you see me ask for help go ahead and flame me. Don't worry I have a thick skin, so I won't feel the need to cry to the mods you hypocrite.
Sent from my GT-P3113 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Don't worry, this morning I was frustrated.
I'm sorry, tell me what you think I'm missing and I'll add the quote to the OP.
I plan on doing a video tut though.
Sent from my HTC One VX using xda app-developers app

worst
this is the worst tutorial I've ever read on xda. mods please take down this how to brick your ouya tutorial before people start downloading wrong files and bricking there ouya.

Okay where is your full proof method of rooting and installing cwm on the ouya?
Sent from my Vivid 4G using xda premium

Going by the threads opened/posts by this fellow, maybe a sticky to let people know who to avoid is needed.
OP, maybe your're over-enthusiastic over your new Ouya, but XDA prides itself on people who actually KNOW what they're doing to help, not rambling nonsense.

Restore htc one to bone stock

Ok so I've looked through some threads on the forums. I found plenty with "restoring htc one" in the title, but my circumstances are weird. I have a t mobile htc one I use in the USA. Recently, I unlocked the bootloader via htcdev, all went well. I used a video tutorial on youtube and followed along to root it. I installed twrp recovery and was about to install supersu, that's when things got weird. When I tried navigating to the supersu.zip file via recovery menu, all I see (up a level). After clicking that, I am taken to files like cache, data, dev, and so on. Nothing related to the files on my internal sd card. I didn't see supersu.zip either. So here I am, with a phone that has an unocked bootloader, twrp recovery and no root access. Ever since I did this, my signal has been randomly dropping and I can't get lte speeds anymore. What happened here?
I was wondering if anyone knew a tutorial that will restore my phone back to stock. I don't mean just stock firmware, I mean absolutely factory bone stock. No recovery, android 4.1.2. htc sense, the whole bit. I know I could just use one of the tutorials available in one of the threads I found, but every single one of them is related to a rooted phone, and mine is sort of in between. I don't want to risk bricking it or anything like that.
If you've made it this far into the read, congratulations you are better than 95% of the people I know. If anyone has a link to a tutorial like this, and it works exactly how I asked it to, I will send them $10 via paypal.

Viruz32 said:
Ok so I've looked through some threads on the forums. I found plenty with "restoring htc one" in the title, but my circumstances are weird. I have a t mobile htc one I use in the USA. Recently, I unlocked the bootloader via htcdev, all went well. I used a video tutorial on youtube and followed along to root it. I installed twrp recovery and was about to install supersu, that's when things got weird. When I tried navigating to the supersu.zip file via recovery menu, all I see (up a level). After clicking that, I am taken to files like cache, data, dev, and so on. Nothing related to the files on my internal sd card. I didn't see supersu.zip either. So here I am, with a phone that has an unocked bootloader, twrp recovery and no root access. Ever since I did this, my signal has been randomly dropping and I can't get lte speeds anymore. What happened here?
I was wondering if anyone knew a tutorial that will restore my phone back to stock. I don't mean just stock firmware, I mean absolutely factory bone stock. No recovery, android 4.1.2. htc sense, the whole bit. I know I could just use one of the tutorials available in one of the threads I found, but every single one of them is related to a rooted phone, and mine is sort of in between. I don't want to risk bricking it or anything like that.
If you've made it this far into the read, congratulations you are better than 95% of the people I know. If anyone has a link to a tutorial like this, and it works exactly how I asked it to, I will send them $10 via paypal.
Click to expand...
Click to collapse
Try plugging your phone into your PC, and in the files you can see, like Music, Movies etc, make a folder called Super and put the zip in there, see if once you go to recovery you can now find it, because to browse root don't you have to have SuperSU anyways?
I am new to this but idk, figured I would atleast try.

I don't think there are some videos about this, however.
If you will fully restore your HTC One, you've to go S-OFF (with revone o rumrunners method) and flash a ruu for T-Mob.
However, you can always root your device.
Probably you have to navigate to "sdcard" in the screen of install of TWRP and after select supersu.zip or whichever

Tried navigating to sdcard, but the folder is just empty. Also, it says internal storage memory: 0mb
Sent from my HTC One using XDA Premium 4 mobile app

Try to use the command:
Code:
adb push name_of_su.zip /sdcard/
and
Code:
adb push name_of_su.zip /data/media
and check if you can see the file or if you got an error.
p.s. You've to use a prompt where you have adb/fastboot and the file will be in this folder...

Im a bit of a noob, could u write out the steps? Because im sure ill screw something up lol
Sent from my HTC One using XDA Premium 4 mobile app

Viruz32 said:
Im a bit of a noob, could u write out the steps? Because im sure ill screw something up lol
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can't do the step i wrote if you're from phone

I know, my house is a little messy right now. We're moving stuff around to replace the floors so my computer and desk and stuff is all over the place.
Sent from my HTC One using XDA Premium 4 mobile app

Update: I fixed it. It turns out it was easier than I thought. All I had to do was fastboot OEM lock the bootloader, and then install the T Mobile RUU file. Who knew it was that simple?