so i decided to root my phone today, and flash a custom rom. i am using the t-mobile variant.
i used the all in one toolkit to unlock bootloader, and everything was going good, but i think i might have forgot to install superuser? i am not sure what went wrong. but i was trying to flash android revolution hd, and it was stuck in the bootloop. so i thought i needed to flash the boot.img like i had to in past devices. did that, but still nothing.
i go into CWM and now i can't access the sd card. so i did a wipe and it still won't mount on my computer. did a little reading around, and someone suggested relocking the bootloader, and flashing stock recovery file (i don't think i got the right one), and then unlocked the bootloader and reflash CWM, and that sideloading a rom would work. everytime i try to sideload a rom, i get a device not found error, but fastboot responds to other adb commands. i did make a backup in CWM, but i moved it from the phone to my laptop, but i have no idea how to even use it. adb push to device does nothing. =/
i really really really hope i didn't brick my phone. anyone have some insight? help? i tried looking for a RUU but it seems there isn't one for t-mobile.
so i am able to flash recovery, and get into it, when i try to mount sdcard in the options, it doesn't say anything. stuck in bootloop still. can't sideload. can't push. really really wish it had an external sd card which would make issues like this a bit easier to solve.
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
orvon.freeman said:
I advise this due to the fact you can use adb commands.
relock bootloader then run an RUU here is the one from AT&T http://forum.xda-developers.com/showthread.php?t=2287036&highlight=ruu.
Click to expand...
Click to collapse
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
just thought about that. Each carrier is diff my bad. good catch unremarked.
I looked for a nandroid that you could use with the toolbox to flash it is t-mobile http://forum.xda-developers.com/showthread.php?t=2182823
orvon.freeman said:
this is the wrong section for this. This belongs in QA not dev. Next time read the rules http://forum.xda-developers.com/showthread.php?t=2158147
Good luck
Click to expand...
Click to collapse
pandaball said:
Nah, mods don't delete threads like this. Thread moved to T-Mobile HTC One Q&A (and don't post questions anywhere other than the Q&A section in the forum of your device's variant )
Click to expand...
Click to collapse
appreciate it, xda forums sure has grown since when i was on here with my g2/my4g slide, lots of subforums, and in a haze of having soft bricked my phone, i posted in the wrong section. sorry!
TygerByte said:
fastboot won't respond to adb commands because it's fastboot not adb. i would use the toolkit and install TWRP recovery and load up TWRP. from there you can adb sideload or do other adb commands once you get it loaded.
Click to expand...
Click to collapse
unremarked said:
Do not attempt to flash an AT&T RUU to your T-Mobile device. In the best case scenario, it should fail(due to S-ON). I would not recommend fooling around with RUUs on different carrier-branded devices.
As for the OP, I'm not sure what to recommend. Most internal storage-only devices won't mount in USB. Wiping your internal storage was the worst thing that you could have done. I'm not sure why adb sideload won't work if normal adb commands and fastboot commands are being accepted. Have you tried a different USB port? I know it sounds strange, but sometimes that can make a difference.
Click to expand...
Click to collapse
i did what tygerbyte suggested several times with no success. then i decided to reinstall htc drivers, restart the laptop, and use a different usb port like unremarked suggested, i am able to sideload now! flashing my backup i made in CWM right now, hopefully this will give me a working phone again before i try to flash a custom rom again lol.
i have my fingers crossed.
thanks for the suggestions everyone. ill post back in a bit with results.
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
mky4b11 said:
just wanted to update, i was able to flash android revolution after several tries / freezing, but phone is back on and functional now.
thanks for walking me through this, i would have gone insane if i bricked my one.
Click to expand...
Click to collapse
Isn't it the worst feeling, thinking you have bricked your $600 phone? I soft-bricked my husbands Bionic once, stayed up all night long and finally figured out I had skipped a step.
The BEST feeling, though, is realizing that you can, and did, recover from what appeared to be a catastrophic fail. Congratulations!
Related
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
ricm68 said:
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
Click to expand...
Click to collapse
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
garyd9 said:
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
Click to expand...
Click to collapse
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
garyd9 said:
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
Click to expand...
Click to collapse
I flashed the one found at the post: [RUU] att ruu 1.58.502.1 posted
Hmm.. Not sure what to suggest in that case. I'm not very familiar with the whole RUU thing myself...
Sent from my Nexus 7 using Tapatalk
Download the ota update. Extract the firmware.zip from it but don't extract firmware.zip. boot to fastboot.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Do it again
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
Fastboot flash recovery twrp.img
Fastboot erase cache
Load recovery
Wipe, advanced wipe
Select dalvik, cache, data, system, internal. Wipe.
Put Rom on ext sd card or
Adb push Rom.zip /sdcard/
Install zip this will obviously erase everything on your phone.
Click thanks.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
You don't need to repair. You just need to troubleshoot. You are throwing the baby out with the bath water, if you go for a hardware repair for what is likely a software issue that is easy to resolve.
You also need to provide more details, and be specific as possible. Namely:
What recovery and version number?
S-on or off?
What exactly have you tried to flash?
Did you factory reset in bootloader?
Do you have working adb?
What happened when you ran the RUU?
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You wont need the whole thing but some of it might pertain to you
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back.
Click to expand...
Click to collapse
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
ricm68 said:
They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Click to expand...
Click to collapse
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
redpoint73 said:
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
Click to expand...
Click to collapse
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
ricm68 said:
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
Click to expand...
Click to collapse
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
I did the factory reset from within cyanogenmod and it didn't wipe it. It restarted back to cyanogenmod. I copied andoid revolution to my internal memory and try to install from there.
ricm68 said:
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
Click to expand...
Click to collapse
You need to try the things I've suggested. I've made some definitive recommendations, and you seem to have ignored them. Honestly, I don't see a point in trying to help anymore, if you don't read what I'm taking the time to post; or you don't try what I've suggested.
Worst case is RUU and start over (install custom recovery again, etc.). But again, I have no idea what happened when you tried to RUU since you still haven't answered that.
You aren't going to make any progress, if you keep ignoring the advice that is given to you.
I'm doing what you told me!!!
I reinstalled twrp and tried but it failed again. Believe me, I've been doing what you suggested.
Can you please give me the steps to RUU and what ruu file to download and use. I really appreciate all you're doing for me and the time you are taking to help.
Sent from my One M8 using XDA Premium 4 mobile app
I was able to install cyanogen mod again and I am using the phone but I want to install sense again.
Sent from my One M8 using XDA Premium 4 mobile app
Just to be clear. Phone boots normally. All functions seem to work. After a minute or two phone locks up, then reboots. If phone is powered down it boots into recovery then locks up/freezes.
Apologize for length of this question but I wanted to be thorough. I have tried several things to resolve this, lots of reading and think I know a lot of things that are not causing the problem.
I installed the Andrenaline ROM, it ran fine for a couple of days then the phone started rebooting over and over again. Note it does not do this in TWRP (shutdown and reboot by itself) nor does it do it inHBoot. Only when I actually try to use the phone or apps after booting up. Initially I did the following all successfully:
I rooted using firewater using this thread http://forum.xda-developers.com/showthread.php?t=2632385 following the root all was fine and according to plan. No issues.
I then followed this thread http://forum.xda-developers.com/showthread.php?t=2498746
Finishing with this http://forum.xda-developers.com/htc-one-max/development/romsense6-adrenaline-4-4-2verizon-t2842331
Wanting to fix this and learn. I decided to go back to square one and even though TWRP seemed to be working I thought I should start there since I can see that I am rooted and have S off and the phone is unlocked.
That means I booted into the phone. Quickly ran adb and started in doing these steps:
adb devices #to make sure it was there
adb reboot bootloader #as per instructions all went well it booted into fastboot
fastboot flash recovery openrecovery-twrp-2.7.1.1-t6vzw.img
# Here seems to be the issue as it just says waiting for device ..... and nada thing happens. So while adb sees the device, runs the reboot of the bootloader it seems to be losing the connection or something at that point.
I am sure I have done something incorrectly. Can anyone lead me in the right direction toward resolving this? Any help would be greatly appreciated.
If somebody can just give me an idea of where the problem might be I would appreciate that. I thought about trying a different rom but system is so unstable I don't think I could get it loaded.
------------------------------------------------------------------------------------------------------------------
I think I was fooled because it ran well for a couple of days before I had issues. After re-reading the OP on the Adrenaline ROM page for about the 100th time I finally noticed ...
IF YOU HAVE ISSUES RUNNING CUSTOM KERNELS ON YOUR HTC ONE MAX, FLASH THIS IMMEDIATELY AFTER FLASHING THE ROM:
http://forum.xda-developers.com/devd...ct/dl/?id=7779
Click to expand...
Click to collapse
Flashing this from TWRP seems to have solved the issue. Thanks to all who at least read the question my apologies for wasting your time. I really did think I had read and seen everything. Actually read the whole thread and still missed that line in the opening post. Thanks to IAmTheOneTheyCallNeo for being so thorough and Flyhalf205 for having provided this. I can now go back to enjoying this fantastic ROM.
Glad you resolved it on your own. Good job
However, your issue with fastboot sounds like you don't really have working fastboot. While in fastboot, you do a "fastboot devices" instead of ADB devices. Then for recoveries it's a fastboot flash recovery nameofrecovery.img
Also, fastboot commands require a locked or re-locked bootloader to work for flashing things.
Neo
Forum Moderator
you are right
Thanks for the heads up. You are correct I have been working around this by using TWRP. I will do some research on how to get a working fastboot tomorrow. I am a linux only person but assume that being on Linux if I can get adb to work fastboot should work right?
Great call that you caught that it's really helpful to have a direction to head in.
IAmTheOneTheyCallNeo said:
Glad you resolved it on your own. Good job
However, your issue with fastboot sounds like you don't really have working fastboot. While in fastboot, you do a "fastboot devices" instead of ADB devices. Then for recoveries it's a fastboot flash recovery nameofrecovery.img
Also, fastboot commands require a locked or re-locked bootloader to work for flashing things.
Neo
Forum Moderator
Click to expand...
Click to collapse
statmonkey said:
Thanks for the heads up. You are correct I have been working around this by using TWRP. I will do some research on how to get a working fastboot tomorrow. I am a linux only person but assume that being on Linux if I can get adb to work fastboot should work right?
Great call that you caught that it's really helpful to have a direction to head in.
Click to expand...
Click to collapse
As a matter of fact, I downloaded the necessary tools for Linux which contain working fastboot and adb (They are not the same thing and two different entities). If I have time tonight I'll zip it up and upload it for you with command line install instructions for your Linux system. If not the it'll be tomorrow.
Neo
Forum Moderator
IAmTheOneTheyCallNeo said:
As a matter of fact, I downloaded the necessary tools for Linux which contain working fastboot and adb (They are not the same thing and two different entities). If I have time tonight I'll zip it up and upload it for you with command line install instructions for your Linux system. If not the it'll be tomorrow.
Neo
Forum Moderator
Click to expand...
Click to collapse
Above and beyond the call sir. That would certainly save me time, effort and confusion. I know just enough to blow a toe or two off. Tomorrow or whenever you have time. Beggars and idiots should not be demanding and feeling like the latter after this fiasco. Really appreciate your help and support.
statmonkey said:
Above and beyond the call sir. That would certainly save me time, effort and confusion. I know just enough to blow a toe or two off. Tomorrow or whenever you have time. Beggars and idiots should not be demanding and feeling like the latter after this fiasco. Really appreciate your help and support.
Click to expand...
Click to collapse
Download this file and unzip it: Androidv4.zip
then, navigate to the Android folder within terminal and launch the ADB-Install-Linux.sh:
Code:
. ADB-Install-Linux.sh
It will install adb and fastboot for linux.
It will install adb and fastboot for linux.[/QUOTE]
Again many thanks.
I have some meetings this evening but will install and test in the morning. Sure it will work well.
Last question
IAmTheOneTheyCallNeo said:
Download this file and unzip it:
then, navigate to the Android folder within terminal and launch the ADB-Install-Linux.sh:
Code:
. ADB-Install-Linux.sh
It will install adb and fastboot for linux.
Click to expand...
Click to collapse
Fastboot is now working properly. Thank you for your assistance.
No more questions. Worked all the way through the process from start to finish to make sure it was correct. Now 100% confident I have it and that it is correct. Thanks again for all the help.
I can get TWRP 2.8.6.4 but can't flash anything else. No RUUs or Roots.
No joy with ADB sideloads or other fastboot commands.
I'm looking in the area of partitions.
I use WinDroid Universal Android Toolkit v2.3 to get TWRP on.
Sometimes I can see the internal card and other times time the external card.
And I get the "E errors.:mount _o bind '/data/media' ' /sdcard process ended with error=255" and other E: errors.
This is my first HTC since the Vivid and I have a few others laying around but can't even use the M9 sim card. Also I'm S off and unlocked bootloader
I've been running Samsungs with no problem.
I guess the Vivid Jinx is still with me.
TIA for any ideas / help. Also S off and unlocked bootloader
Well I've flashed a few RUUs and tried some other zip ROMs.
I'm at their best since I started this goat rope.
I still have TWP v 2.8.6.4 and I can power down. Currently have the Developers ROM with no red text under the HTC at boot.
It will sit there a couple of minutes and boot again.
I will go back thru this tread again and check more on the 'E: mount errors'
I have also tried the flash from SD card method, different USB ports, different computers & cables
jaxboater said:
Well I've flashed a few RUUs and tried some other zip ROMs.
I'm at their best since I started this goat rope.
I still have TWP v 2.8.6.4 and I can power down. Currently have the Developers ROM with no red text under the HTC at boot.
It will sit there a couple of minutes and boot again.
I will go back thru this tread again and check more on the 'E: mount errors'
I have also tried the flash from SD card method, different USB ports, different computers & cables
Click to expand...
Click to collapse
have you tried formatting everything? I remember on the m7 or m8 there was something that happened where a partition wouldnt show and you had to format everything for it to show up
TWRP will format the data but nothing else.
I did a search of adb & fastboot commands and found nada
jaxboater said:
TWRP will format the data but nothing else.
I did a search of adb & fastboot commands and found nada
Click to expand...
Click to collapse
Sounds like TWRP is keeping system as read only.
2.8.6.4 is really old. Update to 2.8.7.1 and if that doesn't solve the issue, consider posting in the TWRP thread in M9 Original dev section.
Thanks
OP requested an older version TWRP (perhaps due to date of post)
Plus couldn't understand because the International info was mixed in.
I guess I'm too old, set in my ways and expect / desire a post to go step by step and not mix in other info.
I do thank the OP for the info provided.
jaxboater said:
OP requested an older version TWRP (perhaps due to date of post)
Plus couldn't understand because the International info was mixed in.
I guess I'm too old, set in my ways and expect / desire a post to go step by step and not mix in other info.
I do thank the OP for the info provided.
Click to expand...
Click to collapse
So you can always wipe system/cache/data from bootloader.
The fastboot commands are
Fastboot oem task 28
Fastboot oem task 29
In order to then successfully flash an ruu you will need to use the HTC version of fastboot. What error did you get while trying to flash the ruu?
Sent from my HTC6535LVW using Tapatalk
Thanks for the ideas and input.
It's time to step back and take a break. I'd hate to scare the folks who live around me by putting 14 rounds from my Glock into it.
Oops my finger kept slipping......
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition