Database Develop

[Q] HTC One - Stuck and need help please.

Hi,
My new HTC One's vibrate isn't very strong, so the vendor is sending me a new one. I'm rooted though, so thought I'd better start looking at ways to "undo" the root. When looking at options on the HTC One Toolkit, I "somehow" did something to my phone. All I "Thought" I was doing was getting the version information off it, so I could find the correct RUU, but when trying to reboot after that, it just kept going back to the bootloader with some error like "re-locked" and "security warning".
After extensive searches, I learnt I could flash the unlock.bin file again to unlock it. Done...but then it just sat at the "Slim" logo [ROM I was running]. I could still boot into Recovery (CWM) and tried clearing cache and dalvik - but still sat at the "Slim" logo. So I started digging in. I tried to mount the SDcard in CWM, but wouldn't mount. So flashed TWRP, but same thing there. When I try to mount anything, the only folder it will let me select is "System" - nothing else mounts and my "Storage" reads "0 bytes".
So I thought maybe I'd lost root, everything was Read Only and that's why I couldn't write to anything. So using the HTC One toolkit, flashed SuperSu. Still same thing.
I did manage to adb the slim ROM and the gapps to /sdcard, but when I tried to install, nothing would "mount" in order to install it...so all I got was errors saying install failed, and a bunch of directories that couldn't be "mounted". In summary I've done the following with Fastboot:
Flashed Unlock file
Flashed boot.img (from Slim Rom)
flashed Recovery (CWM first, but now TWRP)
Fastboot Clear cache
But after all that, when I boot into Recovery, nothing mounts and I can't get past this. Any help you could provide would be MOST welcome!
Thanks in advance.
-- Edit --
Disregard - got it finally. Using TWRP, I formatted the data directory, and it was writeable again. Not sure if it helped, but I then resubmitted everything I did in the list above, booted to Recovery, and was then able to adb the ROM and Gapps over and it installed fine. Phew.... Still need to figure out how to get it all back to stock though. That's my next task.

htc1 m7 keeps rebooting and won't detect network

Last week after software update using auto update Option , after installing the softare , the phone will keep rebooting and won't detect the network. I guess that my phone battery was low at the time of installation(10%) however it was connected to a charger. The problem is after turning on the phone, the phone will reboot after aprox. 1minute 50 seconds and the htc1 won't show network. The settings option in network setting would appear greyed out.
After this problem, I tried factory reset, no avail. Tried recovery from bootloader option but no avail.
Tried Using RUU- RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
Gives me error 155 in Update Utility.
After searching the threads, I decided to unlock and unroot the phone so that I could install any custom ROMs, did unlocking and unrooting.
My htc1 m7 with following specs now
Tampered
Unlocked
M7_U S-On
Hboot- 1.57.0000
Radio0- 4T.28.3218.04
OS-6.15.599.101
Android version 4.4.3 and Sense 6

Some guys recommended me to post my query on xda and I came here with lots of hopes. Unfortunately after couple of days no one from expert community has responded to this query.

htc1resetting said:
Some guys recommended me to post my query on xda and I came here with lots of hopes. Unfortunately after couple of days no one from expert community has responded to this query.
Click to expand...
Click to collapse
you not being ignored, their is no real answer to your problem
you can flash stock recovery for 6.15.599.101 if you can find it
and try the factory reset from stock recovery (not bootloader)
If you have TWRP 2.6.3.3 or higher on the phone now you can choose to format data and then push / sideload a 6.xx.xxx.x rom to the phone. Their are no 6.xx RUU so that's not an option. If the phone died during the update theirs no telling what partitions are damaged so the format data option is your first step

clsA said:
you not being ignored, their is no real answer to your problem
you can flash stock recovery for 6.15.599.101 if you can find it
and try the factory reset from stock recovery (not bootloader)
If you have TWRP 2.6.3.3 or higher on the phone now you can choose to format data and then push / sideload a 6.xx.xxx.x rom to the phone. Their are no 6.xx RUU so that's not an option. If the phone died during the update theirs no telling what partitions are damaged so the format data option is your first step
Click to expand...
Click to collapse
Firstly loads of thanks.
I have tried hard to find 6.15.599.101 RUU but no success.
I should use the second option to push 6.xx.xx.x rom, can you advice where can I find it. I get confused between kernel & OTA, which one is a ROM or neither one?

htc1resetting said:
Firstly loads of thanks.
I have tried hard to find 6.15.599.101 RUU but no success.
I should use the second option to push 6.xx.xx.x rom, can you advice where can I find it. I get confused between kernel & OTA, which one is a ROM or neither one?
Click to expand...
Click to collapse
Use this >> http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
adb push Android_Revolution_HD-One_81.0.zip /sdcard/
or adb sideload Android_Revolution_HD-One_81.0.zip

My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.

htc1resetting said:
My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.
Click to expand...
Click to collapse
boot into TWRP
from the PC command prompt
type adb devices
if it's blank you need to reinstall the htc driver
if your device serial number shows it's working normally

When I use the adb command- where should my phone be? adbsideload? fastboot?
The adb won't detect my device even with htc drivers re-installed. When I use the adb sideload button in the TWRP , it stays there for ever.
Can we use fastboot command to flash the ROM, the way we flash recovery?

htc1resetting said:
When I use the adb command- where should my phone be? <<< TWRP
The adb won't detect my device even with htc drivers re-installed. When I use the adb sideload button in the TWRP , it stays there for ever.
Can we use fastboot command to flash the ROM, the way we flash recovery? << NO
Click to expand...
Click to collapse
Go to post 2 of @nkk71 superguide to install the drivers correctly > http://forum.xda-developers.com/showthread.php?t=2541082

Finally I was able to sideload- adb sideload Android_Revolution_HD-One_81.0.zip
After the sideload was 100% my phone was black screen, was no more in recovery TWRP.
What next step to take?
When I restarted the phone, it will again show the white HTC screen , won't go ahead and boot.
I am s-on and with TWRP 2.8.0.1 recovery.

htc1resetting said:
Finally I was able to sideload- adb sideload Android_Revolution_HD-One_81.0.zip
After the sideload was 100% my phone was black screen, was no more in recovery TWRP.
What next step to take?
When I restarted the phone, it will again show the white HTC screen , won't go ahead and boot.
I am s-on and with TWRP 2.8.0.1 recovery.
Click to expand...
Click to collapse
use TWRP 2.6.3.3

Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.
I unchecked zip file verification from settings and this time was able to complete, followed the step by step installation. After the installation was complete, cleared cache and dalvi and performed system boot. The phone restarts but its again stuck at white htc screen.

clsA said:
use TWRP 2.6.3.3
Click to expand...
Click to collapse
Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.

htc1resetting said:
Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.
Click to expand...
Click to collapse
your download is corrupt ..download it again and md5 check your downloads

clsA said:
your download is corrupt ..download it again and md5 check your downloads
Click to expand...
Click to collapse
Made another attempt to sideload and it was successful, phone booted and rebooted. Phone turned on but again restarted after few seconds, the same way it was behaving earlier. Any suggestions?
I was checking htc Dev site, it has download section with my OS version no. 6.15.599.101- is there something I can do with this file to get my phone working.? m7u-3.4.10-ga936d02.zip is the file.
What are options to get RUU for 6.15.599.101 ?

htc1resetting said:
Made another attempt to sideload and it was successful, phone booted and rebooted. Phone turned on but again restarted after few seconds, the same way it was behaving earlier. Any suggestions?
I was checking htc Dev site, it has download section with my OS version no. 6.15.599.101- is there something I can do with this file to get my phone working.? m7u-3.4.10-ga936d02.zip is the file.
What are options to get RUU for 6.15.599.101 ?
Click to expand...
Click to collapse
You still never tried the stock recovery / factory reset
maybe you can extract it from that file
maybe @Danny201281 could help you check and repair your partition's if he has time

I tried factory reset and stock recovery at my first step long time ago. Only after failing, I tried the TWRP recovery and Android Revolution.

htc1resetting said:
My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.
Click to expand...
Click to collapse
When you say it's formatted are you sure about that?
Format Data is not the same as Factory reset or Wiping partitions. You need to use the Format Data option in twrp to be sure. So in case you haven't already and probably wouldn't hurt to do it again anyway.
Boot into twrp recovery Select the Wipe option and then Format Data option. You will be prompted to type "yes" to confirm. This will wipe everything from your device including your Rom and internal storage. Reboot to recovery to restore a completely new file system to your device.
Now with the phone still in twrp recovery, Select the Mounts option and uncheck all the boxes to unmount the partitions. Return to the twrp home screen (you don't need sideload mode for this part) in the command line type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk35
e2fsck -fvy dev/block/mmcblk36
e2fsck -fvy dev/block/mmcblk37
exit
Once that's done you can push or Sideload your Rom. Personally I prefer the push method but which is easiest for you is fine.
Ideally you want to do a factory reset with Stock recovery also but since you can't find one unless you can extract it from the file on HTC dev just try the above.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
When you say it's formatted are you sure about that?
Format Data is not the same as Factory reset or Wiping partitions. You need to use the Format Data option in twrp to be sure. So in case you haven't already and probably wouldn't hurt to do it again anyway.
Boot into twrp recovery Select the Wipe option and then Format Data option. You will be prompted to type "yes" to confirm. This will wipe everything from your device including your Rom and internal storage. Reboot to recovery to restore a completely new file system to your device.
Now with the phone still in twrp recovery, Select the Mounts option and uncheck all the boxes to unmount the partitions. Return to the twrp home screen (you don't need sideload mode for this part) in the command line type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk35
e2fsck -fvy dev/block/mmcblk36
e2fsck -fvy dev/block/mmcblk37
exit
Once that's done you can push or Sideload your Rom. Personally I prefer the push method but which is easiest for you is fine.
Ideally you want to do a factory reset with Stock recovery also but since you can't find one unless you can extract it from the file on HTC dev just try the above.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I was using the format data option before as well.
This time, followed the step by step procedure and installed the OS, the phone booted again but it restarts after sometime as it was at the beginning of the problem. Any suggestions?

htc1resetting said:
I was using the format data option before as well.
This time, followed the step by step procedure and installed the OS, the phone booted again but it restarts after sometime as it was at the beginning of the problem. Any suggestions?
Click to expand...
Click to collapse
When the phone is booting, does it take longer than normal? And does it bootloop before finally booting.
Unfortunately this is starting to sound like a hardware problem. After formatting the memory, repairing partitions with e2fsck and flashing a new Rom there's not much else can be done. If your still getting random reboots then something is defiantly a miss.
You can check your supersu app to make sure is properly rooted, by opening supersu, it may ask you to update the Binary's.
Or just flash this in recovery to make sure your on the latest.
http://download.chainfire.eu/452/SuperSU/
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Build.prop, stuck in boot screen

Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.

Neblue said:
Hello guys, i need a little help.
I was looking for some tutorial to unlock dev cameras on my xt1225. I found one tutorial and he said to edit Build.prop, i'm noob at this, so I downloaded a file manager and entered in /system/, copied build.prop for backup, and edited the original build.prop. I restarted my phone and now i'm stuck in the boot screen.
I don't know for what reason but ADB (properly configured) does not show any device connected to the PC so I can't use the commands adb pull and adb push.
I have tried copy the backup of build.prop and overwrite the modified one, but no sucess (I did it in TWRP file manager)
I'm using XT1225 5.0.2 Stock ROM.
Edit: So, i tried to change his permissions (or think that i tried, in twrp filme manager with chmod command,), now the phone runs the boot animation and turn black, before he did not do it, before he just stuck in the white screen with motorola logo. (Tried chmod 644, 755, 777)
Sorry for bad english.
Click to expand...
Click to collapse
I don't know about the chmod command, but the TWRP "Fix Permissions" does not work with our current (old) version of TWRP. It just messes up the phone.
1) since you have TWRP, did you make a back-up? If so, restore that. Problem solved.
(If no back-up, why not? That's one of the reasons we use TWRP, so we can restore a good backup when we screw something up.)
2) If you have TWRP, that means your bootloader is unlocked. GOOD.
Boot back into recovery, reflash your ROM. Problem solved.
Reboot, make sure everything is OK, then make a TWRP back-up!
EDIT: OOPS. I see you are using stock 5.0.2, not custom ROM. OK, I hope you made a backup. See #1.
There may be other solutions but all the ones I find seem to involve pushing new files to your phone and you say you can't do that...
______
Also in our version of TWRP, if you wipe cache do NOT attempt it from the "install" prompt (There's an option there to wipe cache. Ignore it.) Only wipe Cache from the "Wipe" section/Advanced Wipe/checkmark Cache and Dalvik Cache. (Even though we use ART, habits die hard.)

OK, I restored a backup following your thread, but before, searching for a solution, I formated the cache/data partition from f2fs to ext4 (so dumb), there's a way to undo it? There's no f2fs wipe option in twrp, I think I'll need to wait to a new version of twrp? Or flashing with rsd lite will do it?
Everything is working fine.
Thanks for your answer.
Sent from my XT1225 using XDA Free mobile app

Neblue said:
OK, I restored a backup following your thread,
Everything is working fine.
Thanks for your answer.
Click to expand...
Click to collapse
Glad your phone is back up and running! Aren't you glad you made a back-up?
Not sure about the F2Fs stuff. I haven't messed with it.
Yes, I agree we need a newer version of TWRP. I would gladly donate money toward to the developer!

[Q] TWRP 2.8.7.1 - Cannot see files under /sdcard

Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?

mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act

The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:

Dead android with warning triangle on XT1072

Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.

mclovin9091 said:
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
Click to expand...
Click to collapse
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.

stonedpsycho said:
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
Click to expand...
Click to collapse
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"

Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.

mclovin9091 said:
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Click to expand...
Click to collapse
Have you enabled "usb debugging"? in developer settings (tap the build number 7 times) Do you have ADB installed? If so did you open CMD in the ADB folder?

FCorvin said:
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
Click to expand...
Click to collapse
Cheers, any info on what files need modding?
Was rooted, managed to get adb to work last night and managed to reinstall twrp but now i can't get the rom to load and can't flash any CROM.
So used the all in one tool to re install stock 5.0.2.
Going to grab a brew and chill for a bit.

Aiight, once you downloaded the zip on your PC, go to:
1. ...titan.zip\META-INF\com\android
Drag the "metadata" file on a notepad page and replace 0x4882 with 0x4821 (your phone's bootloader code) and save.
2. ...titan.zip\META-INF\com\google\android
Drag the "updater-script" file on a notepad page, hit "Search and replace" for any of the XT's in there with yours, XT1072.
You will have 3 hits.
Example: Search and replace XT1069 with XT1072 ->
getprop("ro.product.device") == "XT1069"
getprop("ro.build.product") == "XT1069"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069
will become:
getprop("ro.product.device") == "XT1072"
getprop("ro.build.product") == "XT1072"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1072.
(3 - while still here)
Search and replace the initial 0x4882 bootloader with yours, 0x4821.
Save the changes.
And... you're good to go.
Some native Moto apps won't show up in PlayStore because of this, but you can get all the Moto stuff from here (if you really love them).
Once installed, enjoy the full power of your brand new Android 6 phone.
Don't forget to do all the things you did as a kid once: activate the developer options as mentioned above, set the SuperSu permissions and so on.
However: screw-ups occur mainly because of conflicts between the new and the old, so you will have to perform a clean install as advised here, which means wiping everything you had - so you won't be able to return to your Lollipop Stock through any recovery.
So chill some more and consider everything thoroughly.

Cheers.
bloody phones, dunno ewhat happened but seems like reinstalling the SROM for the 2nd time allowed me to boot into recovery, twrp and load the CROM. Only issue this time was that apparently stock gapps was too big for the phone so had to download and install the mini version.
Will see how CM13 goes and download the Temasek for install later once im happy everythings working.