Related
Hello all. My wife has a bionic that I rooted and installed for3ver root. I only debloated the phone and installed v6 supercharger on it. I just upgraded her to the OTA .905 now her speaker went out.
I need to send it in for warranty they are sending a new one. I tried last night to RSD lite it back to stock. Now I used RSD a lot on my x2 in the past so no stranger to it. Using RSD 5.6 it would not recognize her phone. I reinstalled drivers and rsd lite and rebooted the computer but the computer would see the usb connected but not RSD lite. After trying several ways to get RSD to recognize the phone I ended up using petes root method to unroot the phone. I unrooted it and was able to erase all rooted apps including SU.
So here is my million dollar question. Since it is stock rom and now unrooted if I do a factory reset will it be safe to send to verizon or do I need to try another computer and try the RSD lite all over again?
Thanks in advance. I think it will be okay after a factory reset but there is pople on here a lot smarter than I am
When you did RSD Lite did you use the provided factory cable with the Bionic? The most common issue with most windows computers not recognizing the phone is due to not using the factory cable. As far as wiping via factory reset I don't know if it leaves remnants of some files used. FXZ'ing it would be your best bet. However some other users have reported that they have sent their phones still rooted and had no issues. Might have been lucky. Good chance is Verizon employees don't check to see if the phone was rooted and send off the phone to Motorola to do whatever they do with the phones.
Thanks for the response. Yes I was using the factory cable and phone was chareged to over 80% battery. My next step was to use another computer and try all over again. But after getting it unrooted I was not sure if it would be needed after a factory reset. But yes I would feel much better if I was able to flash it in RSD. Also I did try multiple usb ports I know voltage can be an issue as well.
Search for rsd version 5.7 and try it that way. Haven't had an issue using 5.7 with the bionic
0001001- 0000011- 0010011
I. C. S.
elreydotcom said:
Search for rsd version 5.7 and try it that way. Haven't had an issue using 5.7 with the bionic
0001001- 0000011- 0010011
I. C. S.
Click to expand...
Click to collapse
Sorry I should of mentioned I also tried 5.7 as well after 5.6 did not work. I might try another computer later and try again tonight just for a piece of mind.
Also just a fyi I am using windows Vista. But same computer I always used on my X2 with no issues. I read someone uninstalled the moto helper and re installed and that worked for them. I think at this point another computer will be my next option if I really need to wipe it clean.
Travisdroidx2 said:
Sorry I should of mentioned I also tried 5.7 as well after 5.6 did not work. I might try another computer later and try again tonight just for a piece of mind.
Also just a fyi I am using windows Vista. But same computer I always used on my X2 with no issues. I read someone uninstalled the moto helper and re installed and that worked for them. I think at this point another computer will be my next option if I really need to wipe it clean.
Click to expand...
Click to collapse
are you making sure to plug the usb into computer first and then the phone?
You very well might be just fine sending it in as is.
If you want to be 100% certain tho, RSD/FXZ(or whatever they call it Lol, fastboot flash) is the way to go
So after talking with Ash and getting his and Nitro's advice it sounds like it is a driver issue for sure. Nitro and Ash pointed me in the right direction for the right drivers again. I will try again tonight. Hopefully tomorrow I can put solved in the title and I will post any links to drivers that helped me out.
Thanks to Ashclepdia and Nitro for the advice!!!! And all others that gave their opinion.
Hope it works!
Now back to playing final fantasy 3 on my nexus.
$16 for it but so far worth it if u like FF3 RPG game. Fun
Travisdroidx2 said:
Sorry I should of mentioned I also tried 5.7 as well after 5.6 did not work. I might try another computer later and try again tonight just for a piece of mind.
Also just a fyi I am using windows Vista. But same computer I always used on my X2 with no issues. I read someone uninstalled the moto helper and re installed and that worked for them. I think at this point another computer will be my next option if I really need to wipe it clean.
Click to expand...
Click to collapse
Windows Vista/7 is notorious for not detecting stuff without the correct driver. I know i've had issues with my Bionic and Kindle Fire on my home computer running Windows 7. Those problems went away but before that I had to bring my stuff to work and try it off my Windows XP work computer which worked flawlessly on both.
amageus said:
Windows Vista/7 is notorious for not detecting stuff without the correct driver. I know i've had issues with my Bionic and Kindle Fire on my home computer running Windows 7. Those problems went away but before that I had to bring my stuff to work and try it off my Windows XP work computer which worked flawlessly on both.
Click to expand...
Click to collapse
Yep during my googling search last night I seen where a lot of people with Vista had the same issue. Damn drivers and Vista I am sure I will get it tonight. I have another computer in the house without vista if it comes down to it.
Thanks everyone specially Ash and Nitro. So my problem was the drivers. Nitro suggested I get the drivers from motorola support website. I deleted my old drivers from my Dinc2 and started over. Installed drivers from the motorola website and re install RSD lite again 5.7 this time. But the main thing is after I downloaded the device manager for the drivers when I plugged the phone in RSD could see it. I flashed it back to ,902 and now going to update it to .905. I feel much better now that I know it had a clean wipe. THANKS! To everyone that gave me suggestions. If anyone else is having this issue feel free to PM me and I can give you files needed.
Finally ready to root my phone, decided I am ready for some extra features and roms. Few concerns
1. The biggest one is how are so many people deleting there entire storage? Is it simple to do? I just don't want to make the mistake
2. Debating between aio or using adb commands just to know how to do it.
3. Never used aroma...how user friendly is it?
This isn't my first time, started rooting on my G1, but I just cannot get Linux down and been on Samsung for a while
Thank you been reading htc one threads and just trying to do it right and not need to use your guys amazing troubleshooting
I followed the information used here: http://forum.xda-developers.com/showthread.php?t=2244060
Unlocking the bootloader did, sadly, reset my phone to factory default, erasing my music, downloaded apps, custom ringtones & such. There may be a way to prevent that, but I didn't look into it too much prior to rooting. Plus, I had the music and ringones backed up to my PC. Anyway, the instructions at the aforementioned link are quite thorough, and very easy to follow. I used adb and flashed TWRP; no Aroma involved. The whole process took me about 15 minutes, once I stopped trying to do it with my Windows 8 laptop (with USB 3.0) and used one with Windows 7 and a USB 2.0 port. Afterwards I flashed Tranquil One.
Not worried about losing stuff during unlock process, but seen a lot of people wiping everything later and having to use adb sideload or ruu.
Don't want to be the guy in a day asking for help because I messed up
But I do know not to load anything but sprint roms and kernels
Here's what I did, if it helps:
1. Downloaded and extracted the package in the link posted above.
2. Unlocked the bootloader.
3. Installed TWRP via adb, both of which were included in the extracted files from number 1.
4. Did a backup in TWRP, so I'd at least have a restore point as close to factory settings as possible. It'll come in handy if I have to take the phone in for service at some point. Just restore the image and re-lock bootloader.
5. Copied that backup to my PC.
6. Downloaded Tranquil One ROM, copied to my phone, did factory reset in TWRP & flashed the ROM.
Honestly, if you're even slightly comfortable doing this and you know how to follow instructions you shouldn't end up being "that guy" asking for help after the fact. The one way I can see it becoming more involved is if you're running Windows 8 and/or using USB 3.0. Drivers can be really irritating.
I think they fixed the windows 8 problem. I had no problems on it. Windows 8 reads this one but not my lte for some reason. But again no problems on the ONE.
Sent from my HTCONE using xda app-developers app
Is there any way to restore stock recovery without using a computer?
I bought a Verizon Moto X developer edition used and the guy has TWRP on it. So now I can't update to 4.4 with that on here.
I don't care if I lose all data in the process.
I'm just having a ridiculously hard time getting anything to recognize my phone on windows 8.1 and I don't have a ton of time in the first place.
I tried a factory reset from twrp but twrp didn't go away.
I DO have an old laptop with... xp on it if anyone has a step by step guide that works 100% they could point me to?
came from galaxy nexus btw.
TheBungle said:
Is there any way to restore stock recovery without using a computer?
I bought a Verizon Moto X developer edition used and the guy has TWRP on it. So now I can't update to 4.4 with that on here.
I don't care if I lose all data in the process.
I'm just having a ridiculously hard time getting anything to recognize my phone on windows 8.1 and I don't have a ton of time in the first place.
I tried a factory reset from twrp but twrp didn't go away.
I DO have an old laptop with... xp on it if anyone has a step by step guide that works 100% they could point me to?
came from galaxy nexus btw.
Click to expand...
Click to collapse
My phone was recognized by windows 8.1 and 7. Sounds like you have an issue with your drivers if its not recognizing the phone.
TheBungle said:
Is there any way to restore stock recovery without using a computer?
I bought a Verizon Moto X developer edition used and the guy has TWRP on it. So now I can't update to 4.4 with that on here.
I don't care if I lose all data in the process.
I'm just having a ridiculously hard time getting anything to recognize my phone on windows 8.1 and I don't have a ton of time in the first place.
I tried a factory reset from twrp but twrp didn't go away.
I DO have an old laptop with... xp on it if anyone has a step by step guide that works 100% they could point me to?
came from galaxy nexus btw.
Click to expand...
Click to collapse
you should use the last version of fastboot (or mfastboot), and you can set fastboot.exe to run in win7 compatibility mode
waiflih said:
you should use the last version of fastboot (or mfastboot), and you can set fastboot.exe to run in win7 compatibility mode
Click to expand...
Click to collapse
Think you could link me to the best directions for this phone? I'm reading a lot of different threads and must be way over my head. I do remember it being a hassle with my droid x all those years ago
TheBungle said:
Think you could link me to the best directions for this phone? I'm reading a lot of different threads and must be way over my head. I do remember it being a hassle with my droid x all those years ago
Click to expand...
Click to collapse
These directions for returning to stock using RSD Lite look pretty good, and include a video:
http://forum.xda-developers.com/showthread.php?t=2446515
kclantz said:
These directions for returning to stock using RSD Lite look pretty good, and include a video:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
OK so I've gotten adb working but can't get RSD lite to recognize my device. Can I just use ADB?
I'm so paranoid of bricking my new device that I fought to activate for two weeks. God damn verizon.
edit to add:
I think RDSlite is the way to go. any commonly known way to get it to find my device?
So i use: adb reboot bootloader
from there if I do: adb devices
it comes up blank like there's nothing attatched.
any ideas?
if there's a donate feature, I'll gladly donate a couple beers to anyone that can help me get this working in the next half hour...
It's not much but...
So I got everything working.... I think. RSD Lite seemed to work fine. Letting everything settle in before attempting the 4.4 update...
Thanks for pointing me in the right direction.
I thought a dev edition would have been a bit more... nexus-ey behind the scenes. Oh well, great device so far...
TheBungle said:
So I got everything working.... I think. RSD Lite seemed to work fine. Letting everything settle in before attempting the 4.4 update...
Thanks for pointing me in the right direction.
I thought a dev edition would have been a bit more... nexus-ey behind the scenes. Oh well, great device so far...
Click to expand...
Click to collapse
Glad you got it figured out, sorry I kind of left you hanging, I got busy at work.
I spent the last two weeks or so bricked and its definitely fun. Be glad you have the Dev edition. My MAXX is not, so I had to wait for the FXZ file to be released, couldn't flash anything else. Not getting the Dev edition was a huge mistake.
I have just bought myself a HTC ONE upgraded from a GS3. I was very familiar with GS3 installing roms, tweaks and modems etc. But HTC ONE is completely different to that. I have been googlin adb and fastboot and gained abit of knowledge through there.
It is completely stock so i have done the following steps:
I have unlocked the bootloader,
Then installed the TWRP 2.6.3.3
Made a nandroid backup through TWRP
Copied TWRP backup folder for future reference to computer.
I wiped the data and adb sideloaded a custom rom. (Thought il start from scratch)
So the device is rooted and running now.
I shall be doing S-Off later on as its getting late now
What else shall i do to the phone to get it at its peak?
Also i went through the file manager in TWRP and realised data reset did not clear everything like i thought it would on the phone.
Shall i wipe data a different method to get it completely reset?
Thanks the help would be appreciated.
Just need pointing in the right direction and how you would make your phone new again.
achieve S-OFF then update your firmware to the latest for "peak" performance
you can find plenty of guides regarding S-OFF & stuff
Sent from my HTC One using Tapatalk
Nazak47 said:
I have just bought myself a HTC ONE upgraded from a GS3. I was very familiar with GS3 installing roms, tweaks and modems etc. But HTC ONE is completely different to that. I have been googlin adb and fastboot and gained abit of knowledge through there.
It is completely stock so i have done the following steps:
I have unlocked the bootloader,
Then installed the TWRP 2.6.3.3
Made a nandroid backup through TWRP
Copied TWRP backup folder for future reference to computer.
I wiped the data and adb sideloaded a custom rom. (Thought il start from scratch)
So the device is rooted and running now.
I shall be doing S-Off later on as its getting late now
What else shall i do to the phone to get it at its peak?
Also i went through the file manager in TWRP and realised data reset did not clear everything like i thought it would on the phone.
Shall i wipe data a different method to get it completely reset?
Thanks the help would be appreciated.
Just need pointing in the right direction and how you would make your phone new again.
Click to expand...
Click to collapse
congratulations.
s-off is kinda overrated. you can pretty much do whatever you want to do with just unlocked bootloader, but hey, you're on a roll so why not go all the way.
I've never bothered flashing updated firmware etc and everything works just fine. Great performance and good battery with everything working as it should....
what stuff did the data wipe leave behind?
So next step firmware can any be installed or does it need to be device specific?
Also how do I get a virtual ad card so when I wipe data that is not affected?
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to flash the ruu. Full disclosure I no longer stand behind this due to lack of wifi. I went ahead and flashed with the RUU and fastboot flashed twrp back. This solution was only a temporary fix for me. As it should be for anybody if its used at all
You reckon this'll work with Boost Mobile?
TeamLiquid.koyo said:
You reckon this'll work with Boost Mobile?
Click to expand...
Click to collapse
There's already a flashable MM ROM for the boost 626s, http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
Yeah. On boost that's all you need
Genius... Simply Genius
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
i2andog said:
Genius... Simply Genius
Click to expand...
Click to collapse
Thanks man. Lol....
Did you try? If so, any issues?
IsaacGuti said:
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
Click to expand...
Click to collapse
I really don't know what causes the red letters. Personally speaking, I can still manage with or without them.
talksickisil said:
Thanks man. Lol....
Did you try? If so, any issues?
Click to expand...
Click to collapse
No I have a working PC... I just really admired your use of magiver like resources
Gotcha. . Yeah, it's not the first time. And not just phones. I Jimmy rig my way thru a lot of life haha. To be honest I'd probably still do this even if I had my PC. I'm just not a fan of fastboot and adb commands. And I don't want to lock my bootloader again
Yes.. those mother f'in boot loaders would burn in hell if I had any say ... in uh.. boot loaders souls or whatever... ... *crickets*.... hey check that out
Sent from my HTC Desire 626s using Tapatalk
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
s3llz said:
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
Click to expand...
Click to collapse
As far as which sprint ROM you flash debloated version or regular it doesn't really matter, since once you restore the twrp backup you're going to be on the standard non debloated metro official MM. As far as UI differences, there's a few things here and there. Nothing mind blowing. What was advantageous for me is the expanded internal storage. I love it.
I tried installing with the RUU and always got error 155 all the time some I am trying this method out. I would like to know will this method still work on a phone with exposed binary, and for those with MetroPCS, does the service still work as well.
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
bnawolf said:
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
Click to expand...
Click to collapse
In my instructions you don't stay on the sprint rom. You're supposed to restore the backup after installing that rom. But I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to re lock your bootloader and flash the ruu