Database Develop

[Q] Phone will only succesfully flash certain roms

Hey guys!
I have a problem, and to be perfectly honest I am not a massive expert at this sort of stuff, but bare with me.
I am trying to install Virtuous ICS Rom RC2 on my Incredible S, but once I've done so it won't boot past the HTC logo. Tried a clean wipe (factory reset/cache/dalvik cache), and even changing from EXT3 to EXT4 and back, but nothing works. Now, I've had this problem before with other various ROMs, and it seems that I can only get flawless installs and boots from Cyanogenmod 7.1 and MIUI (not the ICS version).
Currently running 4EXT recovery and MIUI, but I want the ICS rom really bad, and other Incredible S users are flashing without any problems, so I'm not sure what gives.
Any and all help would be appreciated (and sorry if this is a noob-ish question and/or in the wrong forum)!

Make sure you have the newest ClockWork Recovery Mod installed. If you do try reinstalling it and an engineering hBoot. I would say the problem would be that one of those are corrupt.

I will try both of those and get back to you with the results! Thanks!

Okay, so I updated CWM to 5.0.2.0, which did not do anything. When you say reinstall, do you mean a completely removal of CWM and then installing it again? Because I'm not sure how to do that.
Also, as usual, MIUI 1.2.30 installs just fine, but I just tried installing MIUI 2.12.13 and ended up in a bootloop. So, thus far, I can only flash two roms; CM7.1 and MIUI 1.2.30. These two were the first two roms I ever flashed, not sure if that has anything to do with anything but I thought it might be worth mentioning.

Unlocked bootloader with htcdev? You might need to reflash the boot.img from your desired rom's zip file with the command
Code:
fastboot flash boot boot.img

i think you should flash the new ROM image
please refer the the post
http://forum.xda-developers.com/showthread.php?t=1337105

How do I flash a ROM via HBOOT? Do I just load it up, wait for the SD card to be read then plug it in via usb, go to cmd and type in the necessary prompts, and the boot.img file from my rom.zip will be flashed?

Hexykins said:
How do I flash a ROM via HBOOT? Do I just load it up, wait for the SD card to be read then plug it in via usb, go to cmd and type in the necessary prompts, and the boot.img file from my rom.zip will be flashed?
Click to expand...
Click to collapse
Read the FAQ sticky post for info on how to flash the boot.img file in a custom ROM.zip file.

Will do, thanks guys, wish me luck.

The correct first question is: Is the OP S-Off or HTC unlocked? if it's the latter, follow Nonverbose's advice.

My phone is S-OFF.

Hexykins said:
My phone is S-OFF.
Click to expand...
Click to collapse
Please boot into Fastboot mode and run the following:
Fastboot getvar all
And post the results so we can see how your phone is currently set up

Okay, so I highlighted FASTBOOT and pressed the power button, then plugged in the USB and it changed to FASTBOOT USB. However, my PC doesn't find my phone, so I can't run the cmd prompts. Should I just go through the steps listed in http://forum.xda-developers.com/showthread.php?t=1337105?

Hexykins said:
Okay, so I highlighted FASTBOOT and pressed the power button, then plugged in the USB and it changed to FASTBOOT USB. However, my PC doesn't find my phone, so I can't run the cmd prompts. Should I just go through the steps listed in http://forum.xda-developers.com/showthread.php?t=1337105?
Click to expand...
Click to collapse
No that would not be applicable in your case from what you have told us. If you are S-Off and have a custom ROM installed, then you probably don't have HBOOT 1.16 or 2.00. That is why I wanted you to get the Fastboot getvar all information.
Have you installed HTC Sync on your PC to get the appropriate drivers set up?

Just installed HTC Sync and got all the appropriate drivers. Still won't show up as a disk when I'm in Fastboot, but I'm guessing it's not supposed to either.

Hexykins said:
Just installed HTC Sync and got all the appropriate drivers. Still won't show up as a disk when I'm in Fastboot, but I'm guessing it's not supposed to either.
Click to expand...
Click to collapse
No it won't show as a disk drive. Open a command window and set the working directory to the one where you installed adb.exe and Fastboot.exe and then type:
Fastboot devices and it should respond with your device serial number. If it does then you can type:
Fastboot getvar all

Here you go, sorry it took so long, had to set up a few things:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hexykins said:
Here you go, sorry it took so long, had to set up a few things:
Click to expand...
Click to collapse
Ok you still have S-Off and now that you have fastboot working I would try reflashing CWM 5.0.2.0 recovery image in fastboot mode.
Copy the CWM recovery.img file to the directory where you have fastboot.exe. If you have a zip file for CWM5.0.2.0 then open the zip and copy the .img file.
Then in fastboot mode type the command:
fastboot flash recovery recovery.img
Then I would try flashing Virtuous ICS.

Hm, sadly that didn't help, it still just bootloops and/or get stuck on the bootscreen (depending on the ROM, tried both the Virtuous ROM and the new MIUI).

Hexykins said:
Hm, sadly that didn't help, it still just bootloops and/or get stuck on the bootscreen (depending on the ROM, tried both the Virtuous ROM and the new MIUI).
Click to expand...
Click to collapse
Full wipe (data,cache,dalvik)

[Q] OTA update on stock ROM, but custom recovery

Good morning, all:
I just got my HTC One the other day and, in the process of transferring content from my Galaxy SIII, I rooted and installed CWM recovery, but kept the stock ROM because I liked the change from what I'd been using on the SIII (CM).
Unfortunately, in the last day or so, an OTA update was released for the One and, as I found out (and you likely know), you can't perform OTA updates with a custom recovery. The constant notifications are enough to make me want to update, besides the obvious benefits of increased stability.
I was wondering if I could flash the recovery found in the [Recovery] Stock HTC One post (http://forum.xda-developers.com/showthread.php?t=2158763) to the device so that I could update? Also, would this break my root/superuser? The device is a TELUS model (if they differentiate by carrier) with software no° 1.29.661.5.
Any advice would be appreciated. Thanks!
------------------------------
UPDATE - 2:38 PM
------------------------------
Hey, guys:
Sorry for all of this noise, I figured things out and wanted to delete this thread, but can't seem to do that.
For those of you experiencing similar issues, who followed mike1986.'s Complete Flashing Guide post, the process for restoring your stock Recovery image to do OTA updates is actually super simple:
- Connect your phone to your computer and pull the backup you did of your device before flashing the custom recovery image.
- Open the folder and move the Recovery.img file to your Android SDK folder.
-Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
-Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
- Navigate to [your SDK directory] (type in Command Prompt: cd c:\[directory]).
- In the Command Prompt type following command: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Using this method, you could flash your stock recovery back onto the device, perform the OTA, then flash the custom Recovery.img back onto your device all in the span of 5 minutes.
This is probably standard stuff for most people on this forum.

[DELETED]

Could you please post your custom recovery?
I need to do the same procedure as yours, and I am currently on same fw, from Telus.
Many thanks.
Sent from a pizza

millicent said:
Could you please post your custom recovery?
Click to expand...
Click to collapse
Sure thing, millicent.
Tried attaching it to the post, but that wasn't working so here's a DropBox link: HTC One Stock Recover (1.29.661.5). Happy OTA updating!

I've tried this, but the OTA update package won't install. Flashing the Recovery.img isn't enough.

Sonnyw said:
I've tried this, but the OTA update package won't install. Flashing the Recovery.img isn't enough.
Click to expand...
Click to collapse
I assume you're running a stock ROM, so did you delete any stock apps(i.e bloatware)? If so, you will need to NAND restore to a stock backup or get those apps back. First thing an official OTA does is check the signatures on all the files it'd expecting to be on the device and if any come back wrong or missing, update aborts.
Sent from my Galaxy S4

unremarked said:
I assume you're running a stock ROM, so did you delete any stock apps(i.e bloatware)? If so, you will need to NAND restore to a stock backup or get those apps back. First thing an official OTA does is check the signatures on all the files it'd expecting to be on the device and if any come back wrong or missing, update aborts.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Remember that unlocking the bootloader automatically deletes a few apps, which you will need to install back

MacHackz said:
Remember that unlocking the bootloader automatically deletes a few apps, which you will need to install back
Click to expand...
Click to collapse
So I was just wondering, if i install the bloatware/default apps back manually (using the .apk files) and flash the recovery back to stock. Will I be able to do an OTA update Without loss of data? If that´s possible, I wil flash the custom bootloader back after performing the OTA update.

Guys, thanks for helping me out. I've done an OTA update without any data loss, you can read about it in thishttp://forum.xda-developers.com/showthread.php?p=42122514#post42122514 Thread.

MacHackz said:
Remember that unlocking the bootloader automatically deletes a few apps, which you will need to install back
Click to expand...
Click to collapse
Really? I did not know this! Out of my curiosity, do you know what apps get deleted?
Sent from my Galaxy S4

unremarked said:
Really? I did not know this! Out of my curiosity, do you know what apps get deleted?
Sent from my Galaxy S4
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MacHackz said:
Click to expand...
Click to collapse
What a strange assortment of apps to be removed. Thanks for the info!

Can you tell me where to find the stock recovery I'm moto e
No one ever mentions where to find the stock recovery file for a noob like me
When I find it, Should I flash it via cmd and I'll get my stock recovery back?I want it back to install official lollipop 5.1 I downloaded.It won't install after downloading but just takes me to the TWRP Screen(ya I have TWRP installed)

HELP ME PLEASEEE said:
No one ever mentions where to find the stock recovery file for a noob like me
When I find it, Should I flash it via cmd and I'll get my stock recovery back?I want it back to install official lollipop 5.1 I downloaded.It won't install after downloading but just takes me to the TWRP Screen(ya I have TWRP installed)
Click to expand...
Click to collapse
This is the HTC One M7 forum, if you need help with your Moto E post in the Moto E forum.
http://forum.xda-developers.com/moto-e

[Q] cant install latest OTA..

I've got an HTC one which is unlocked and S-Off with CWM and still running 1.29.401.13.
I received a notification of an OTA (2.24.401.1, which includes android 4.2.2) the other day..
I downloaded it and chose to install it. Once I did, my phone booted into CWM and instead of a new ROM, I'm shown an error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've also found the downloaded OTA.zip and tried to install it manually through CWM, but I get this:
Could anyone point me in the direction of the cause or fix please?
Thanks in advance,
'tunes

mad_tunes said:
I've got an HTC one which is unlocked and S-Off with CWM and still running 1.29.401.13.
I received a notification of an OTA (2.24.401.1, which includes android 4.2.2) the other day..
I downloaded it and chose to install it. Once I did, my phone booted into CWM and instead of a new ROM, I'm shown an error:
I've also found the downloaded OTA.zip and tried to install it manually through CWM, but I get this:
Could anyone point me in the direction of the cause or fix please?
Thanks in advance,
'tunes
Click to expand...
Click to collapse
flash stock recovery and relock your bootloader for official OTA updates. you can't install OTA's with a custom recovery and an unlocked bootloader.

herwegan said:
flash stock recovery and relock your bootloader for official OTA updates. you can't install OTA's with a custom recovery and an unlocked bootloader.
Click to expand...
Click to collapse
Thanks herwegan. I've just flashed a stock recovery and relocked my bootloader (now shows relocked).
I let the phone re-download the OTA and chose to install it. Now, it restarts and stops at this:
any more ideas please?

mad_tunes said:
Thanks herwegan. I've just flashed a stock recovery and relocked my bootloader (now shows relocked).
I let the phone re-download the OTA and chose to install it. Now, it restarts and stops at this:
any more ideas please?
Click to expand...
Click to collapse
is your device rootet? if yes, unroot it temporary for OTA

herwegan said:
is your device rootet? if yes, unroot it temporary for OTA
Click to expand...
Click to collapse
I've unrooted it and tried the same again... and got the same.
I've found that I get stuck at the same screen as above if I try to do a factory reset from within the bootloader too.
.. I also can't sideload a ROM, The ROM's copied to my phone, but I'm then told:
E:\ cant open /tmp/update.zip (bad)
installation aborted

I think I might be making some progress.
After setting every back to as stock as possible, I was still finding the same problem.
So, I found and installed an old RUU, which installed OK on the second attempt. (I was oriignally running .13, the RUU was an older .7)
This has let me run through the OTAs back up to .12 so far, it's re-downloading the latest one atm. I'm hoping it'll install OK like the .12 and then I can re-unlock everything.
edit:
the latest OTA installed just fine.
Thanks for the suggestions

I thought I'd got this sorted out but something's still not right.
Everything looks fine once booted but whatever I backup from within CWM, it runs through as you'd expect but its not shown when I browse my SDCard once booted.
inside CWM, I see just
0/
clocworkmod/
legacy/
obb/
the contents of the sdcard are shown as being inside 0/, it's like CWMs working at a folder higher up the tree then it has for me before.
that means I cant delete or copy backup from a pc..
does anyone know what might be wrong please?

mad_tunes said:
I thought I'd got this sorted out but something's still not right.
Everything looks fine once booted but whatever I backup from within CWM, it runs through as you'd expect but its not shown when I browse my SDCard once booted.
inside CWM, I see just
0/
clocworkmod/
legacy/
obb/
the contents of the sdcard are shown as being inside 0/, it's like CWMs working at a folder higher up the tree then it has for me before.
that means I cant delete or copy backup from a pc..
does anyone know what might be wrong please?
Click to expand...
Click to collapse
you're running 4.2.2 now, so this is normal, you need to move your backup files to the sd card folder to be able to see them on a pc.
get a root explorer, the cwm backup files are now in mnt/shell/emulated/clockworkmod/backup
cheers

i had just been doing some reading and have backups moving to I can pull them off onto my laptop.
Thanks a ton though, that could have cracked it if I hadnt kept searching.

HTC one M8_WHL H/K sprint version no OS showing in bootlooder.

Hello all,
I bought this new HTC one m8 few days back, it was in kitkat so i tried the Software update thing, but it keeps searching it for hours then I tried to flash ROMs and then i messed up in TWRP. I accidentally deleted everything without any backup. I tried to flash CM12.1 (not nightly)+ gapps, the logo of cm appears and after that my phone auto reboot and same thing is happening again and again. What i did so far is, i changed my CID, I unlocked my device, tried flashing many ROMs like SkyDragon, and also tried many RUU.zip/RUU.exe files but non of them work. When i tried to open zip files it says cannot open the file/ file maybe damaged or corrupted. I can get into recovery(TWRP 2.8...) I tried to flash through SD but after showing successfully done I get back to this white HTC screen again.
I am seriously in trouble.. please somebody help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SaifAhmed said:
Hello all,
I bought this new HTC one m8 few days back, it was in kitkat so i tried the Software update thing, but it keeps searching it for hours then I tried to flash ROMs and then i messed up in TWRP. I accidentally deleted everything without any backup. I tried to flash CM12.1 (not nightly)+ gapps, the logo of cm appears and after that my phone auto reboot and same thing is happening again and again. What i did so far is, i changed my CID, I unlocked my device, tried flashing many ROMs like SkyDragon, and also tried many RUU.zip/RUU.exe files but non of them work. When i tried to open zip files it says cannot open the file/ file maybe damaged or corrupted. I can get into recovery(TWRP 2.8...) I tried to flash through SD but after showing successfully done I get back to this white HTC screen again.
I am seriously in trouble.. please somebody help.
Click to expand...
Click to collapse
You need to make sure you follow the instructions while flashing a ROM. If you already did check the following:
1. Check if you have custom recovery (TWRP) and custom bootloader (check the thread in development for your device).
2.. Did you flash the right ROM? International (GSM) ROMs are not compatible with Sprint M8. Make sure you are using one from this thread.
3. Most of the time, the ROM zip you have is not completely downloaded. sometime it's error with the download. Whenever you download a ROM/any file make sure the downloaded item matches the MD5 sum.
4. Before flashing a ROM make sure you did a clean wipe. This includes system, data, cache and dalvik cache (but not the data in the sd card - last option shouldn't be checked in twrp). Also for some ROMs you need to be S-OFF. Try installing boot.img using the CMD window.
Let me know if anything mentioned above works for you

Cashreedhar said:
You need to make sure you follow the instructions while flashing a ROM. If you already did check the following:
1. Check if you have custom recovery (TWRP) and custom bootloader (check the thread in development for your device).
2.. Did you flash the right ROM? International (GSM) ROMs are not compatible with Sprint M8. Make sure you are using one from this thread.
3. Most of the time, the ROM zip you have is not completely downloaded. sometime it's error with the download. Whenever you download a ROM/any file make sure the downloaded item matches the MD5 sum.
4. Before flashing a ROM make sure you did a clean wipe. This includes system, data, cache and dalvik cache (but not the data in the sd card - last option shouldn't be checked in twrp). Also for some ROMs you need to be S-OFF. Try installing boot.img using the CMD window.
Let me know if anything mentioned above works for you
Click to expand...
Click to collapse
Thanks bro.. I waited for 1 day then I didnt came back though i fixed it later that day by flashing sprint bad boyz rom and their firmware.. It worked for me

just wanted to point out that the OS showing in the bootloader changes while flashing a zip file in the fastboot. Whatever zip you flashed last, check android-info.txt file. (ofcourse you can flash custom zip files with firmware if you have SOFF only)

TWRP / Encryption / Mount issue when trying to root [OP3T]

Hi All. Complete newbie to the forum here......in search of advice!
I've just got my new OnePlus 3T, so wanted to get it all set up and rooted before switching over from my Galaxy S5.
After reading several guides I followed the below steps:
Completed the OTA update to OOS 4.0.2
Unlocked the boot loader
Flashed TWRP 3.0.3
Booted into Recovery and TWRP asked for the encryption password (which was the same pattern I used in normal mode)
Internal memory was accessible so I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip. (I couldn't tell if they flashed successfully).
Rebooted
When the phone tries to reboot, I eventually get a screen saying 'Encryption Unsuccessful' and suggests I need to factory Reset.
When I select to reset, it boots back in to TWRP, but there is no request for the encryption pattern this time, and internal memory doesn't seem to mount. (showing as 0mb).
I'm wondering what my next step should be?
Should I try to flash the latest TWRP (3.0.4) via ADB?
Or would I be better off trying to flash back on stock recovery and the stock OOS 4.02 rom, and then wait for a newer TWRP before trying to get root access again?
.......Or will none of the above work?!
All I was really looking to do was root the phone. I'm not planning on changing from the stock OOS rom. I also don't mind if its encrypted or not encrypted.
I have had a look through some of the threads, but cant find examples of this scenario. Any help appreciated!

Which SuperSU file did you flashed?

The-Wexican said:
I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip.
Click to expand...
Click to collapse
I hope you didn't flash in that exact order. That could possibly be the reason for your issue. Also, you don't need the verity zip if you're flashing SuperSU.

Thanks for the feedback. Below is a link to the guide I followed on the Oneplus forums:
[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !! (It wont let me link the thread as I'm a new user, but Google will show it!
That suggested to flash them in that order, I think.
SuperSU-v2.79-201612051815.zip was the SuperSU I used.

All, just to add, I don't need to recover any data or anything like that. I'm just looking for the best way to get out of this bot loop (of sorts).
I'm kinda thinking that because TWRP Recoveryseems to load OK, I could maybe flash back on the stock recovery and then side load the stock rom?
Any thoughts?
Or is it worth a shot at updating to the latest TWRP first (3.0.4)?

Below is the message I see when I try to boot the phone normally now (not in recovery)........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The-Wexican said:
Below is the message I see when I try to boot the phone normally now (not in recovery)........
Click to expand...
Click to collapse
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success

stephlal said:
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
Click to expand...
Click to collapse
Awesome!
That worked. Thanks for your help!
Now running OP3T with OOS 4.0.2, TWRP recovery, rooted with SuperSU, and I even cleared the DM-Verity nag screen by booting into bootloader and running:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Very happy now!