Related
Hey guys, please forgive me if I misuse my terminology here but I am still a padawan learner.
My wife's hero is rooted and running a cyanogen rom. All was well for months but now her usb plug is broken and NOT charging. I have not yet verified that the usb won't talk to the pc but I assume it's the case because I can't get the thing to charge. Of course i have tried 5 or 6 diff chargers, tried wiggling, etc. but i am convinced that there is a broken prong in the phones plug. The phone is under warranty for 2 more days but I understand that I need to flash it back to stock before trying warranty stuff.
I have searched and the answers I have found are to simply run the latest RUU from the htc website. I found it, no problem, but it is an .exe file and would require the usb to work, right? The phone is dead right now or i would test the usb>pc connection and I have arranged to briefly borrow a friend's battery later tonight. If i can't get the connection to work is there any other way to flash this thing back to stock? If I just download a stock rom and flash that then i will still be rooted right? Do they check that? and lastly what about running an OTA update? Any advice/ideas are greatly appreciated.
Come to think of it, I might have the original naandroid backup that i did of the phone back in the day. If i restore this, would it go back to stock?
Here's what you can do:
Go HERE and download the S-OFF bootloader.
Flash it
Download THIS - its the zip that gets uploaded/flashed when you run the RUU.
And..as per instructions on that page:
Simply rename this to HERCIMG.zip and place on the root of your SDCard.
Power your phone completely off.
Press and Hold VOL DOWN and POWER until your phone boots into HBoot mode.
Wait for it to verify the zip, then click <ACTION> (Trackball) to update, or <SEND> (Green Call) to cancel.
After it flashes you'll have a stock phone, with the stock bootloader
Its the same setup I have on my phone..Just in case I need to un-root on the fly Except I have two zips. One with the stock bootloader and one without so I can keep it unlocked.
Gotta love XDA, thanks so much. I may have found it if I had thought about searching for "stock sprint zip format". Hopefully the next guy will find this. I have been helped by your advice many times throughout the forums in my searches.
drumstyk1 said:
Gotta love XDA, thanks so much. I may have found it if I had thought about searching for "stock sprint zip format". Hopefully the next guy will find this. I have been helped by your advice many times throughout the forums in my searches.
Click to expand...
Click to collapse
You should add "or computer" to the title as well For those that may search 'unrooting without a computer'
And you're welcome that's why I'm here
Not working (yet)
Hi, another noob here: SAKKA.
I also need to revert to stock. I already switched the phone number (just upgraded and giving Hero to daughter). So have to push everything from Mac via USB. Unable to d/l md5sum: a77a2dee8e903e8f1a18b28b5c5e0b40 b/c it won't connect (too old?) Have HERC in root, did steps 1-4. But no go. Is there someway I can chat and get some help? Or do you know where i can chat now that AOSP is no longer running an online chat room (as far as I know)?
do u have any idea how old this thread is
Oh.
D'oh. Thanks.
That being said. Know how I can find someone to talk me through this?
sethfriedman said:
Oh.
D'oh. Thanks.
That being said. Know how I can find someone to talk me through this?
Click to expand...
Click to collapse
There is this help page :
http://forum.xda-developers.com/showthread.php?p=13479613
I always unroot with this:
http://forum.xda-developers.com/showthread.php?p=8551240
Then I root with the "one click method"
http://forum.xda-developers.com/showthread.php?t=743289
Both never fail me....
Good luck
V's CDMA Hero
V's CDMA Hero
i tried this! it was on the updating part and when it was almost done, the htc screen appear and it started all over with s-off. so it said fail.
Just curious, if phone is already activated to her # then why go back to horrible stock.
If u want a stock ROM flash liquid sense or nfx.
http://forum.xda-developers.com/forumdisplay.php?f=643
From either of those two ROMs u can do all that stock can.. like activation, PRL updates, etc.....
So unless its going for service under warranty there is no need to unroot to stock.
Good luck
V's CDMA Hero
Hello, I have searched for a solution and found some that worked, My WIFI on my moto x will not connect to any network.
it just started a few weeks ago, But going to in to recovery mode and wiping the cache was working it would connect again.
Thing is it's not only on my home network if i go to any place with WIFI it shows the network, I try to connect and it disappears.
I had the kitkat update I tried to factory reset that did not work also reflashed to jelly bean to see if that would fix the problem. I did not restore any back ups of my device since it could have been a corrupt setting or file that was messing it up. Still no luck I tried some of the router options found on the web about changing the channels. Just to be clear it will not connect to any WIFI not just the one at my house.
I spoke with Fido tech support and after explaining everything i tried they said i was out of options and since I bought the phone right out, I would have to call Motorola and see if they can fix it, thing is i unlocked the bootloader when I rooted it when i first had it with it's stock jelly bean.
I know this is a on going issue for many other moto x, could it just be a hardware issue now my phone has been in a otter box defender since the day i bought it, it has no damage or ever been dropped in water.
it's frustrating, my data works perfect and every thing else on phone works great. I really like the phone but since the bootloader is unlocked the warranty is now void and I only had the phone since dec 2013.
does any one have any last options I could possibly try thanks in advance.
xsnyper said:
Hello, I have searched for a solution and found some that worked, My WIFI on my moto x will not connect to any network.
it just started a few weeks ago, But going to in to recovery mode and wiping the cache was working it would connect again.
Thing is it's not only on my home network if i go to any place with WIFI it shows the network, I try to connect and it disappears.
I had the kitkat update I tried to factory reset that did not work also reflashed to jelly bean to see if that would fix the problem. I did not restore any back ups of my device since it could have been a corrupt setting or file that was messing it up. Still no luck I tried some of the router options found on the web about changing the channels. Just to be clear it will not connect to any WIFI not just the one at my house.
I spoke with Fido tech support and after explaining everything i tried they said i was out of options and since I bought the phone right out, I would have to call Motorola and see if they can fix it, thing is i unlocked the bootloader when I rooted it when i first had it with it's stock jelly bean.
I know this is a on going issue for many other moto x, could it just be a hardware issue now my phone has been in a otter box defender since the day i bought it, it has no damage or ever been dropped in water.
it's frustrating, my data works perfect and every thing else on phone works great. I really like the phone but since the bootloader is unlocked the warranty is now void and I only had the phone since dec 2013.
does any one have any last options I could possibly try thanks in advance.
Click to expand...
Click to collapse
Hi,
I suggest you do a full SBF restore. Don't confuse this with a factory reset....SBFing can actually repair a corrupted filesystem, while a factory reset does not.
You can find a great guide here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
There are 2 methods. RSD Lite and manual method. Either will work, but pay very close attention to the instructions.
You will find the SBF file for your particular carrier/version here:
http://sbf.droid-developers.org/phone.php?device=0
Good Luck
P.S. I too was having strange WIFI issues. The SBF back to stock fixed it 100%. Hope it works for you.
no luck
samwathegreat said:
Hi,
I suggest you do a full SBF restore. Don't confuse this with a factory reset....SBFing can actually repair a corrupted filesystem, while a factory reset does not.
You can find a great guide here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
There are 2 methods. RSD Lite and manual method. Either will work, but pay very close attention to the instructions.
You will find the SBF file for your particular carrier/version here:
http://sbf.droid-developers.org/phone.php?device=0
Good Luck
P.S. I too was having strange WIFI issues. The SBF back to stock fixed it 100%. Hope it works for you.
Click to expand...
Click to collapse
I followed the guide step by step, Still no luck.
shows the wifi connections, saves them and shows that it is connecting and just goes back to saved, or disabled. Sometimes even just disappears took it in to have it looked at and the guys at the fido store had the same issue trying to connect to their network.
They keep saying it is a software issue but i'm starting to think it might be hardware. I even tried some fixes with Root to get access to the persist folder to change a file. Tried booting in safe mode to see if it would connect and just does the same thing, I might just be buying a new device just got one of those unlucky ones thanks again tho.
xsnyper said:
I followed the guide step by step, Still no luck.
shows the wifi connections, saves them and shows that it is connecting and just goes back to saved, or disabled. Sometimes even just disappears took it in to have it looked at and the guys at the fido store had the same issue trying to connect to their network.
They keep saying it is a software issue but i'm starting to think it might be hardware. I even tried some fixes with Root to get access to the persist folder to change a file. Tried booting in safe mode to see if it would connect and just does the same thing, I might just be buying a new device just got one of those unlucky ones thanks again tho.
Click to expand...
Click to collapse
I would suspect a hardware issue since you have doctored your persist partition, and you have restored the others via SBF. Bummer :/ Maybe someone else will have another suggestion for you.
Good Luck
Thank you
Thank you Very Much
Working again!
I did not give up and it's working again thanks to samwathegreat, I dont mean to bump my old post but I just want to share with other xt 1058 users that may have been having this issue.
I had mentioned before I used some one else's persist files to try and fix mine and thought it was a hardware problem, Well turns out it was not.
I used the files samwathegreat posted in this post
http://forum.xda-developers.com/showpost.php?p=54089540&postcount=7
I also made a back up of mine, the files in that folder are for a xt 1060 but corrected my problem now I can connect every where again including my house and any other place that offer WIFI.
I was not able to send it to Motorala since I had unlocked the boot loader and warranty was void. All I could do was wait, I even flashed a tmobile 4.4.3 to see if that would fix it with no luck. Any ways just want to say thanks again samwathegreat!!! :good::good:
xsnyper said:
I did not give up and it's working again thanks to samwathegreat, I dont mean to bump my old post but I just want to share with other xt 1058 users that may have been having this issue.
Click to expand...
Click to collapse
Congrats bud!!! Don't worry about the files being from an XT1060 - they are the same on all Moto X variants.
Glad to hear it is all sorted out!!! Enjoy.
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
no one?
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
This updates been a nightmare
synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.
This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys
randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.
I'm still stuck. Any progress ?
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked
I had to RMA
randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.
Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA
im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.
I purchased the H811 off ebay last week because I am finally sick of my old Note 5 with no service at home. The G4 did great until I decided to flash it. The phone was on H81120i.
No big deal unlocking bootloader or installing TWRP. I flashed Lineage OS 14.1. About a minute after booting up, the phone got the error Camera stopped working. After checking more stuff on the device, nothing seems to work - i.e. - The accelerometer, speakers, microphone, flashlight, etc are dead. I installed a sensor test app and it doesn't detect any of the sensors.
After that, I downloaded LGUP and the stock KDZ file to flash back to phone hoping to fix it. Unfortunately, LGUP doesn't recognize the phone. It says unknown model but shows the com port, h81120i on the right hand side. I also tried LG FlashTool to see if that would work but it crashes about 26% into the it.
I have searched the forums up and down and have googled the crap out of this. I did find a thread from last month with a very similar issue a moment ago, https://forum.xda-developers.com/tmobile-g4/help/camera-stopped-audio-flashing-lg-g4-t3620516, and perhaps I should post in that thread, but my issue is that LG Bridge gives me an error stating it can't detect the software version.
If I were using Samsung, I don't think I would have this problem because I have unbricked several Samsung devices. The issue here is I am new to LG and have no idea if files are corrupt, if hardware was screwed, or what the situation is. I would hate to think that it was a $100 wasted.
Any help would be greatly appreciated.
x3n0n907 said:
I purchased the H811 off ebay last week because I am finally sick of my old Note 5 with no service at home. The G4 did great until I decided to flash it. The phone was on H81120i.
No big deal unlocking bootloader or installing TWRP. I flashed Lineage OS 14.1. About a minute after booting up, the phone got the error Camera stopped working. After checking more stuff on the device, nothing seems to work - i.e. - The accelerometer, speakers, microphone, flashlight, etc are dead. I installed a sensor test app and it doesn't detect any of the sensors.
After that, I downloaded LGUP and the stock KDZ file to flash back to phone hoping to fix it. Unfortunately, LGUP doesn't recognize the phone. It says unknown model but shows the com port, h81120i on the right hand side. I also tried LG FlashTool to see if that would work but it crashes about 26% into the it.
I have searched the forums up and down and have googled the crap out of this. I did find a thread from last month with a very similar issue a moment ago, https://forum.xda-developers.com/tmobile-g4/help/camera-stopped-audio-flashing-lg-g4-t3620516, and perhaps I should post in that thread, but my issue is that LG Bridge gives me an error stating it can't detect the software version.
If I were using Samsung, I don't think I would have this problem because I have unbricked several Samsung devices. The issue here is I am new to LG and have no idea if files are corrupt, if hardware was screwed, or what the situation is. I would hate to think that it was a $100 wasted.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
maybe you got a frankenphone .. a supposely H811 and its not .. why not open it and see the actual motherboard and see wich variant you really have .seems like its not a h811 or try uppercut LGUP. see what it finds and downloads.
raptorddd said:
maybe you got a frankenphone .. a supposely H811 and its not .. why not open it and see the actual motherboard and see wich variant you really have .seems like its not a h811 or try uppercut LGUP. see what it finds and downloads.
Click to expand...
Click to collapse
Uppercut found nothing... I opened the phone and found this though... EAX6658501_H810_MAIN_1.0
Of course, the tag on the inside of battery compartment says H811 with a date of 02/2016. Would it be a refurb or what? Anyway, I may be on the right track now.
x3n0n907 said:
Uppercut found nothing... I opened the phone and found this though... EAX6658501_H810_MAIN_1.0
Of course, the tag on the inside of battery compartment says H811 with a date of 02/2016. Would it be a refurb or what? Anyway, I may be on the right track now.
Click to expand...
Click to collapse
maybe yes .. cover h811 and so software easy to edit.. but the only way is that take the motherboard and read the variant.
h810 is att?
I checked out the AT&T forum and found nothing other than stock that, obvious under my current situation, I can't flash because lgup with uppercut nor lg flash tools can flash.
LGUP gives an error code in the log file. PACKET_ERROR code = 1460
The phone internet still works. It has downloaded an update from t-mobile that's 460+MB that I can't install because I'm rooted with TWRP. Is it possible to update the phone with adb and TWRP? If I could find stock recovery, I would flash that and using autoprime's bootloader flash it back, even remove root if the update may revive the device.
After a week, a thought occurred to me and i tried it. I backed up a working h811 ( minus efs partition) with twrp with 20o firmware to an sd card then restored that version to this phone. I immediately wiped and flashed G4 20o with root zip file. It unbricked the phone and I'm currently using it.
Thanks raptorddd for replying and helping me. It seems that somewhere in the flash process something was corrupted and this fixed it.
x3n0n907 said:
After a week, a thought occurred to me and i tried it. I backed up a working h811 ( minus efs partition) with twrp with 20o firmware to an sd card then restored that version to this phone. I immediately wiped and flashed G4 20o with root zip file. It unbricked the phone and I'm currently using it.
Thanks raptorddd for replying and helping me. It seems that somewhere in the flash process something was corrupted and this fixed it.
Click to expand...
Click to collapse
youre welcomed but then phone is H811? or H810 i know that what ever the motherboard says thats your variant. am glad you have back up and running. :good:
It is crazy because the board said 810 but it had h81120i official when i got it. It worked but i have always used custom roms. Oh well, I'm going to stay stock with root. Just need to debloat now.
So I have been up all night and day trying to figure out how to root my old phone, every root app is just BS. I've followed instructions which are not very clear.
The phone is currently at 6.0.1 and apparently I need to downgrade BUT ODIN won't detect it. probably due to the port being wonky. I have tried many troubleshooting tricks and nothing is working.
If someone could please help me figure this out or tell me I am wasting my time and redirect me to another thread that this was already figured out, that would be great. I will try to provide as much information as possible.
mrpoppop said:
So I have been up all night and day trying to figure out how to root my old phone, every root app is just BS. I've followed instructions which are not very clear.
The phone is currently at 6.0.1 and apparently I need to downgrade BUT ODIN won't detect it. probably due to the port being wonky. I have tried many troubleshooting tricks and nothing is working.
If someone could please help me figure this out or tell me I am wasting my time and redirect me to another thread that this was already figured out, that would be great. I will try to provide as much information as possible.
Click to expand...
Click to collapse
If ODIN isn't detecting the phone in download mode, try on a different PC, you might just need to install or replace drivers.
There is a full root guide here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
AptLogic said:
If ODIN isn't detecting the phone in download mode, try on a different PC, you might just need to install or replace drivers.
There is a full root guide here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Click to expand...
Click to collapse
I tried, I did the whole drivers thing, what I'm saying is the COMPUTER isn't even recognizing my phone, the port on my phone has been messed up for a while, it USED to work with ODIN a few months ago but I haven't tried until recently. Again, I heard there IS ways to do a root without ODIN, which would be nice rather than all this complicated driver stuff. That's honestly what I would rather do.
Side note, I was told to post here after a reddit user said the response time and help would be great. (lol @ me)
I don't have another computer to try, and I have tried several versions of ODIN. So could someone please give some advice, I am starting to think I have 0 options. I hate how the G900A is the most difficult (or one of the more difficult).
Currently there is no root method for the S5 on 6.0.1, downgrading and staying on a lower firmware version is the only way to have root for this phone until a viable security exploit is found; and since you cannot downgrade through ODIN because of the damaged port I'm afraid your only option is to accept the phone as is or get a different phone. All carrier branded smartphones are generally difficult to root, but Verizon and AT&T variants are more so. In the future look for a foreign variant (like the G900F in this case) if root is truly important to you if you plan on staying on a GSM network like AT&T.
Alternatively you could try ordering a new board from eBay if your port is bad but that would require some skill putting it back together (and also your phone would no longer be water resistant) but personally that would be too much of a hassle for me, but it is an option.