Related
So i'm basically a total noob when it comes to this kind of thing.
I recently rooted my new HTC ONE (International) using a method i found on htconeroot.com
After that the phone could not read the SD card. Every time i open storage in the settings menu it closes.
The phone also would reboot at random moments.
I tried to fix it using some other methods and messed it up. I deleted the original OS and i cant access the backups i made because i switched recoveries from TWRP to CWM. Even when i switched back to TWRP, i couldn't find the backups.
I tried installing two roms (Android Revolution and Maximus) but when i did they would not boot completely and would be stuck on the boot logo.
I cannot flash stock RUU because it is not out yet (1.29.401.12)
I tried to use the Nandroid method i found on this link:
http://forum.xda-developers.com/showthread.php?t=2267435
But the installation aborted for some reason and would not work.
PLEASE can anyone help me find a solution or show me how i make the nandroid backup method work?
Andys1994 said:
So i'm basically a total noob when it comes to this kind of thing.
I recently rooted my new HTC ONE (International) using a method i found on htconeroot.com
After that the phone could not read the SD card. Every time i open storage in the settings menu it closes.
The phone also would reboot at random moments.
I tried to fix it using some other methods and messed it up. I deleted the original OS and i cant access the backups i made because i switched recoveries from TWRP to CWM. Even when i switched back to TWRP, i couldn't find the backups.
I tried installing two roms (Android Revolution and Maximus) but when i did they would not boot completely and would be stuck on the boot logo.
I cannot flash stock RUU because it is not out yet (1.29.401.12)
I tried to use the Nandroid method i found on this link:
http://forum.xda-developers.com/showthread.php?t=2267435
But the installation aborted for some reason and would not work.
PLEASE can anyone help me find a solution or show me how i make the nandroid backup method work?
Click to expand...
Click to collapse
Wait so you cannot ruu back did you oem relock and then try the ruu? Sorry I'm on a US variant and not a international one
Sent from my HTCONE using Tapatalk 2
Could you send us a pic of your bootloader? That way we can determine exartcly what state your phone is in.
Also, I just used HTCOneRoot two days ago without a hitch (AT&T variant). The first boot takes a good 2 - 5 minutes so maybe you just didn't wait long enough.
Sent from my HTC One using xda app-developers app
Lekerstein said:
Could you send us a pic of your bootloader? That way we can determine exartcly what state your phone is in.
Also, I just used HTCOneRoot two days ago without a hitch (AT&T variant). The first boot takes a good 2 - 5 minutes so maybe you just didn't wait long enough.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ok so i had a friend of mine who's a tech-wizz when it comes to this kind of thing help me out. He explained pretty much everything but i still have a problem.
I basically erased the system by accident (playing with TWRP), so i flashed CWM and restored my phone using a nandroid backup for version 1.29.401.12, which was the original version the phone came in.
The backup worked although it still has the same bugs that i had when i first rooted the damn thing.
Basically, some apps would just restart themselves right when i open them, such as google chrome. They would eventually open after a couple more tries. The phone is a bit laggy, and would also reboot at random moments, which i think normally happen when i do something with the phone such as install a new app or simply post a facebook status. Is it possible that i might've erased an important system file? Cuz the backup should've restored all missing system and data files.
Oh and i also couldn't take a photo of the bootloader because my camera has the same image taking capabilities of a potato.
So i'll just copy down everything on there.
*** TAMPERED ***
*** UNLOCKED ***
M7_U PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 4 2013, 16:21:26:-1
I am running CWM-Touch v6.0.3.1 which was the recovery i found within the nandroid backup
If there's anymore information i can supply that would help please let me know.
Alex1123 said:
Wait so you cannot ruu back did you oem relock and then try the ruu? Sorry I'm on a US variant and not a international one
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I looked everywhere but all the threads i found said that the RUU's for the 1.29 base are not out yet so i had to use the nandroid backup instead.
This phone is killing me
I tried re-rooting and giving the phone 10 mins to stable.
I tried flashing AndroidRevolution rom
I tried several nandroid backups, including the software version that i was initially on (1.29.401.12)
Just now i flashed an odexed rom version 2.17.401.1 and it still keeps on restarting.
I'm starting to believe this phone is fake.
Are flashing the boot.IMG through fastboot after flashing the ROM ?
Sent from my One XL using xda app-developers app
Andys1994 said:
This phone is killing me
I tried re-rooting and giving the phone 10 mins to stable.
I tried flashing AndroidRevolution rom
I tried several nandroid backups, including the software version that i was initially on (1.29.401.12)
Just now i flashed an odexed rom version 2.17.401.1 and it still keeps on restarting.
I'm starting to believe this phone is fake.
Click to expand...
Click to collapse
You may try doing a data factory reset in settings/backup and restore/reset the phone.
henslo said:
Are flashing the boot.IMG through fastboot after flashing the ROM ?
Sent from my One XL using xda app-developers app
Click to expand...
Click to collapse
Not really, i install the rom using the recovery. Is there a way to flash it using fastboot?
Andys1994 said:
This phone is killing me
I tried re-rooting and giving the phone 10 mins to stable.
I tried flashing AndroidRevolution rom
I tried several nandroid backups, including the software version that i was initially on (1.29.401.12)
Just now i flashed an odexed rom version 2.17.401.1 and it still keeps on restarting.
I'm starting to believe this phone is fake.
Click to expand...
Click to collapse
Did it look fake?
MacHackz said:
Did it look fake?
Click to expand...
Click to collapse
No it doesn't, but normally rooting the device shouldn't really do this, right?
Cause i've looked everywhere and no one seems to be having this problem with the HTC ONE.
Is there a way to tell if it's fake or not?
gee2012 said:
You may try doing a data factory reset in settings/backup and restore/reset the phone.
Click to expand...
Click to collapse
Tried that, still keeps restarting
Andys1994 said:
No it doesn't, but normally rooting the device shouldn't really do this, right?
Cause i've looked everywhere and no one seems to be having this problem with the HTC ONE.
Is there a way to tell if it's fake or not?
Click to expand...
Click to collapse
Doubt it will be fake, you'd have to be pretty new to not spot a fake one
MacHackz said:
Doubt it will be fake, you'd have to be pretty new to not spot a fake one
Click to expand...
Click to collapse
Ok, so that means it something i did, which can hopefully be fixed
i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?
texaslegend said:
i looked. i swear. however, can't find anything that addresses my issue or at least i don't recognize it at my issue.
I have a DE Moto X on VZN.
unlocked bootloader
reverted from 4.4 to 4.2.2
flashed TWRP-2.6.3.1-ghost-4.4
Everything was working just fine and i couldn't leave well enough alone. I was screwing around and tried to flash/install/whatever an apk that would invert gmail colors....basically white to black. i'm not sure if it was before or after i did that but i created a backup in case it screwed something up and i wanted to revert. well, i loaded it and nothing happened so i went to restore my device from the backup i had just created and TWRP told me it was complete/successful or something and gave me the option to reboot. i did and now my phone is stuck in a boot loop. i've tried to restore several times to no avail.
i can get into bootloader menu but normal start up starts the boot loop process again. TWRP loads if i go into recovery. phone isn't recognized by RSD Lite. not sure what to do.
Can anyone help or tell me what additional info you need to be able to help?
Click to expand...
Click to collapse
So you've tried restoring your nandroid prior to the flash, and still get bootloops, right? Have you tried wiping the caches? You can also try a full wipe and see if that gets you out of the boot loop, and then you can go back and try to restore your nandroid.
If all else fails and you can get into fastboot, there are instructions here on getting back to stock: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images. I would pull my backup from the device first from within TWRP (although if you don't erase userdata it should still be on the phone). You'll have to re-flash TWRP, but that process should get you back to having a working phone.
there might also be a problem with the fact that oyu were running 4.2.2 and using twrp that was built for 4.4. there is a twrp that was built for 4.2.2 so i don't know why you used the one built for 4.4. don't know what the differences are if any that would affect running twrp 4.4 on a 4.2.2 firmware but there may be some major issues.
You could try manually deleting everything with fastboot, then boot into recovery to restore your backup before flashing the 4.2.2 TWRP.
Thanks for the help. I thought I edited my post to say I fixed the problem. Did that with a wipe from the twrp bootloader our whatever that screen is called when you not into recovery.
Thanks
Sent from my XT1060 using xda app-developers app
I am curious as to why you downgraded back to 4.2.2?
Mainly for FoxFi WiFi. I use it on road trips for my kid's iPad and Nabi.
Sent from my XT1060 using xda app-developers app
If you have an unlocked bootloader, why not use one of the available mods with 4.4?
First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app
texaslegend said:
First I guess would be because I didn't know about it. I wasn't really planning on unlocking and rooting to begin with.
I got the DE because at the time I needed a phone it was the only x I could get with 32GB.
Which mood are you talking about I might have to check it out
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
There's a flashable zip in this thread.
http://forum.xda-developers.com/showthread.php?t=2561560
It's for 4.4 not 4.2 though, don't flash it unless you update.
Make it easy on yourself and use the Xposed module http://forum.xda-developers.com/showthread.php?t=2601859
Hey guys,
a few days ago i noticed that some google services drained my battery quite a bit. after some fixing attempts which did not work i decided to perform a factory reset via the stock tool from HTC which you can find in the menu(it was completely stock except the unlocked bootloader and S-OFF). After that factory reset my notification bar lagged every time i pulled it down. I could not find any solution for that so i installed the InsertCoin M7 2.3.1 rom and performed a full wipe. I also installed the ElementalX-m7-14.1 kernel. Both did not fix the problem. The rest of the ui and all my apps run completely flawless.
My Bootloader is unlocked and i have security turned off (S-OFF).
Did you ever hear about something similar?
There is something else about my phone too. A few months ago i "turned" my ONE into a Play Edition. Since that point on every Boot it shows the Google icon before the boot animation no matter which ROM is installed... is that common?
thanks in advance.
That second part is because you are s-off you can change your boot Image. You could find a thread somewhere around here to change it back to HTC. For the first problem, never use stock update or tools on custom rom, how to resolve I do not know.
Sent from my One using XDA Premium 4 mobile app
Zandoz said:
That second part is because you are s-off you can change your boot Image. You could find a thread somewhere around here to change it back to HTC. For the first problem, never use stock update or tools on custom rom, how to resolve I do not know.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for your reply!
i was completely stock when i used the stock reset option.
Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?
you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app
From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device
Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app
I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?
jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk
Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk
Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Bubba Fett said:
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Click to expand...
Click to collapse
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yikes. I didn't even see a ton of info on the subject. I can't imagine there is anything left on the device to cause any issues. Hopefully someone with more knowledge about this sees this post. Note 7 release party Aug 2nd if it comes to that!
same issue i see alot of people with it, its the emmc i confirmed it beause yesterday while i was alseep my emmc decided to give up on life no recovery no download failed to read emmc, the problem is repairing it im not gonna take it to samsung as they will charge almost the price of a new phone i have found a chip for it but it says it has sm n910p/f firmware on it not sure if it would be an issue as i could reflash the tmobile firmware on it.
http://www.aliexpress.com/item/Bran...2630152207.html?spm=2114.40010708.4.13.nPWCQ2
any advice on the chip?
So, what was the final solution?