Related
I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.
I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.
With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.
I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.
Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.
Any help would be appreciated.
You should be able to restore it by installing this RUU with a working goldcard:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you get a CID error your goldcard isn't working. There should be no version error with this.
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.
As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.
We will see how it goes anyway.
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.
Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?
Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Let's try this in order: if you are with Virgin Mobile, it is a CDMA. GSM phones take a sim card, both versions accept an sd card for storage.
Everything looks good until:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Good luck. If you have any more questions, feel free to ask.
pedantfool said:
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Click to expand...
Click to collapse
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
followup
FIRST: Just thought of something that might be very important, I only had a version of android 4.0 installed on my phone. Will that make a difference when installing roms intended for later versions of android? If so, I feel like a huge knuckle-dragging fool.
Update: Was able to install and boot using PACman, but ran into a boot-loop.
But to follow up to your questions:
MameTozhio said:
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
Click to expand...
Click to collapse
I'll admit I've had a hard time find a definitive version of PA or really any other Rom. I've tried going through their thread here and downloading one of the "stables" (http://goo.im/devs/gannon5197/paranoid/primoc/stables/). I've also used other unofficial versions of PA (http://forum.xda-developers.com/showthread.php?t=1799372). I'm currently downloading PACman to see if that will make any difference.
[email protected]@ said:
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
Click to expand...
Click to collapse
I did flash my boot.img using the method explained here:
Copy the kernel image (boot.img file you have extracted from zip file of ROM) to folder in which you have kept your fastboot files.
In the same folder, right click while holding shift button and select ‘Open command window here’.
A command window will appear on your screen. In command window type ‘fastboot flash boot boot.img’ and press enter.
On your screen you will get message ’OKAY/Finished’. You have successfully flashed kernel. Now you can disconnect your phone from computer.
http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
riggerman0421 said:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
Click to expand...
Click to collapse
I'd like to think I'd partitioned it properly, but I keep getting a "unable to mount sd-ext" or "unable to wipe sd-ext" message when I attempt a factory reset. I've tried formatting the the mini sd and set the file type to FAT32, but to no avail as the errors persist. I know you said not to be too concerned, but I keep failing the system wipe from your next suggestion because of that error.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Click to expand...
Click to collapse
Now how important is it that I flash the boot.img after I have flashed the rom? I've been doing it beforehand, but does doing it afterward make a difference?
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Click to expand...
Click to collapse
Those both match my radio and bootloader, what does that imply? I'm planning on flashing this rom: http://forum.xda-developers.com/showthread.php?t=1948034
Will that work?
No, it won't. You have the newer updated hboot and radio. That is the source of your boot loops. The only compatible roms at this time are MyOneV, ExtremeSemse, and RhythmicRom. You can also use Cyanprimo, but you'll have flash the boot.img from RhythmicRom.
Now I've downloaded RythmicRom and I'm still stuck in a boot loop. I'm sorry for being a bit thick, but could you link some roms that would be compatible or explain what I need to be looking for?
Version I downloaded: http://forum.xda-developers.com/showthread.php?t=2147407
You'll need to download the 1.2 update, then extract the boot.img from that. The boot.img in the Rom doesn't work with the new update.
So I've been reading up on the issue over here: http://forum.xda-developers.com/showthread.php?t=2018518&page=14
and while I don't claim to understand it all, I believe I get the gist of it.
I also've managed to get RythmicRom working thanks to riggerman. I guess I'll just play the waiting game until someone rolls out a fix or just replace my phone (though that's very much in the long-run).
Once again, thanks to everyone and hopefully this will be the last we see of this mess.
Glad you got it running, and glad I could help.
Hi all,
Happy new owner of European model HTC One M9. Now stuck with white HTC boot screen and problems to turn it off and random strange things... I'm lost and need help desperately...
Followed all guides in unlocking through htc-dev, installing TWRP 2.8.6.4 (beta).
Made a copy of Stock ROM through nandroid backup.
Flashed SuperSU (UPDATE-SuperSU-v2.46).
Advanced wipe (did I by any means delete internal system?)
When flashing Android_Revolution_HD-One_M9_4.1_eda061 everything went haywire. Got message at end stating that not all processes were finished. Something with regard to E:mount -0 bind '/data/media/'sdcard' process errored with error=255. Now lots of issues...
1) I couldn't get passed the white boot HTC One screen. Had to keep my finger on the power off for ages.
2) Bootloader shows software status: modifed. unlocked. s-on. I assume this is correct?
3) Going into recovery I get a strange HTC message: This build is for development purposes only (+ disclaimer not to distribute outside HTC bla bla bla). Is this normal?
4) when I try to restore my Stock ROM through fastboot I get to the setup of the device, but then FC of different programs. Back, home and settings button are non-responsive. Even entered a strange HTC error check. Upon rebooting, clearing cache and Dalvik, I am stuck at white boot screen. Now I can't even get into android OS setup anymore.
I have tried nr 4 above several times without success. I do get a strange "Invalid sparse file format at header magi
erasing 'system'..." is this normal? I get OK at end - but then still back to white boot screen.
Is my system totally buggered? What have I done wrong? I've flashed HTCs and Samsungs several years as an amateur but I feel like a total noob... Help? Anyone?
robned said:
Hi all,
Happy new owner of European model HTC One M9. Now stuck with white HTC boot screen and problems to turn it off and random strange things... I'm lost and need help desperately...
Followed all guides in unlocking through htc-dev, installing TWRP 2.8.6.4 (beta).
Made a copy of Stock ROM through nandroid backup.
Flashed SuperSU (UPDATE-SuperSU-v2.46).
Advanced wipe (did I by any means delete internal system?)
When flashing Android_Revolution_HD-One_M9_4.1_eda061 everything went haywire. Got message at end stating that not all processes were finished. Something with regard to E:mount -0 bind '/data/media/'sdcard' process errored with error=255. Now lots of issues...
1) I couldn't get passed the white boot HTC One screen. Had to keep my finger on the power off for ages.
2) Bootloader shows software status: modifed. unlocked. s-on. I assume this is correct?
3) Going into recovery I get a strange HTC message: This build is for development purposes only (+ disclaimer not to distribute outside HTC bla bla bla). Is this normal?
4) when I try to restore my Stock ROM through fastboot I get to the setup of the device, but then FC of different programs. Back, home and settings button are non-responsive. Even entered a strange HTC error check. Upon rebooting, clearing cache and Dalvik, I am stuck at white boot screen. Now I can't even get into android OS setup anymore.
I have tried nr 4 above several times without success. I do get a strange "Invalid sparse file format at header magi
erasing 'system'..." is this normal? I get OK at end - but then still back to white boot screen.
Is my system totally buggered? What have I done wrong? I've flashed HTCs and Samsungs several years as an amateur but I feel like a total noob... Help? Anyone?
Click to expand...
Click to collapse
the disclaimer is normal, and all that other stuff. before the fastboot restore did you flash stock recovery, I'm not sure but I think you have to, someone correct me if I'm wrong. pn advanced wipe you wipe cache-dalvic cache-system and data. nothing else before flashing a rom, if it has aroma installer select full wipe.
Aldo101t said:
the disclaimer is normal, and all that other stuff. before the fastboot restore did you flash stock recovery, I'm not sure but I think you have to, someone correct me if I'm wrong. pn advanced wipe you wipe cache-dalvic cache-system and data. nothing else before flashing a rom, if it has aroma installer select full wipe.
Click to expand...
Click to collapse
Hi,
Many thanks for your input. I tried to do a fastboot restore stock recovery (OTA 401.15) and afterwards a fastboot of my Stock ROM nandroid backup. It all seemed to work well (took longer than before - so I guess things got written to system) but I get foreclosures on several programs - most importantly Sense UI (even EasyAccessService and others less important as well). The SenseUI means I dont have any working buttons for apps, back and home. I wanted to see if I could delete the cache for SenseUI - but as soon as I try to go to apps, I get FC on App Helper. Same if I want to install anything.
- so I'm lost again... Any ideas?
robned said:
Hi,
Many thanks for your input. I tried to do a fastboot restore stock recovery (OTA 401.15) and afterwards a fastboot of my Stock ROM nandroid backup. It all seemed to work well (took longer than before - so I guess things got written to system) but I get foreclosures on several programs - most importantly Sense UI (even EasyAccessService and others less important as well). The SenseUI means I dont have any working buttons for apps, back and home. I wanted to see if I could delete the cache for SenseUI - but as soon as I try to go to apps, I get FC on App Helper. Same if I want to install anything.
- so I'm lost again... Any ideas?
Click to expand...
Click to collapse
I don't know. maybe your backup image was corrupted/
Aldo101t said:
I don't know. maybe your backup image was corrupted/
Click to expand...
Click to collapse
I actually made two backups and I tried the second one. I realized I didn't wipe cache and dalvik after installing stock recovery. I've flashed so many times tonight i'm going mad. Went in to stock recovery and wiped it, and upon reset and a lot of sweating it all works back to square 1.
Maybe I'll stick to stock... :silly:
Many thanks for the headsup on stock recovery. That's probably the only thing I hadn't tried and I wouldn't have thought of. :good::good::good:
http://forum.xda-developers.com/showthread.php?p=59896551
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Rename it into 0PJAIMG.ZIP, put it on the ext sd card, reboot into 'download_mode', agree..
jauhien said:
http://forum.xda-developers.com/showthread.php?p=59896551
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
---------- Post added at 01:13 PM ---------- Previous post was at 01:12 PM ----------
Rename it into 0PJAIMG.ZIP, put it on the ext sd card, reboot into 'download_mode', agree..
Click to expand...
Click to collapse
I have exactly the same issue, but can't get past the htc splash screen; any suggestions?
hellejoep said:
I have exactly the same issue, but can't get past the htc splash screen; any suggestions?
Click to expand...
Click to collapse
if you rename it OPJAIMG.zip before moving it to sdcard it will have two zips on it there(OPJAIMG.zip.zip)this will fail.
There is no effective RUU restoration that works once you follow the root, twrp, processes listed here on XDA. I've restored the original recovery.img, still no go. I've tried the full RUU available on HTC to no success. So be forewarned.
However, there is a way to recover your device. I'm no developer by any means, but this is the process which a kind user informed me of, so I'm sharing it at top level. See his comment below which is the true saving grace.
My 530 is a MetroPCS variant, so I went to the HTC site and downloaded RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_TMOUS_1.01.531.25.exe
Then I used a RUU decryption tool, and extracted the files mentioned (boot.img) and (system.img).
I made sure TWRP worked on my handset still, which it did.
I put both files boot.img and system.img on the handset through the USB cable. I also copied the BETA-SuperSU-v2.74-2-20160519174328.zip to the same location.
Then I chose Install in TWRP, and chose "Image" instead of "Zip". It's a little box bottom right in TWRP on the Install screen.
First I installed the boot.img followed up by the system.img. I almost clicked reboot, and TWRP gave me this notice "Warning no Operating System installed." ---
...so I remembered the BETA-SuperSU-v2.74-2-20160519174328.zip file I copied over, and I went and installed it through TWRP.
I then rebooted the phone, and it rebooted a couple times, but then VOILA it was back to perfect, all data wiped of course, but fully rooted and ready to go.
Here is a link to the files I extracted using the RUU decryption tool. It is the T-Mobile variant, but works perfect for MetroPCS as well. https://drive.google.com/drive/folders/0B4K9JR5eVMSnWmtOMlV3Tkx1V2M?usp=sharing
Which carrier is your 530 from?
If you can boot in to TWRP you can install the system.img and boot.img from the install menu, press on install image once you are in the install menu, locate your system.img and choose the sytem partition boot for boot partition.
You can extract the system.img & boot.img using RUU decrypt tool
upperdecker said:
Which carrier is your 530 from?
If you can boot in to TWRP you can install the system.img and boot.img from the install menu, press on install image once you are in the install menu, locate your system.img and choose the sytem partition boot for boot partition.
You can extract the system.img & boot.img using RUU decrypt tool
Click to expand...
Click to collapse
Thanks, and MetroPCS. I'm going to try and decipher what you just typed and see if I can restore the handset, because it's stuck atm.
I flashed the exposed framework but my phone wasn't working right so I did twrp restore from a backup that I had previously used however now my phone is STUCK ON THE HTC logo screen.
I downloaded your files, followed your instruction and OMG! Thank You sooooo much I'm back to normal AND WITH SU. Thanks again!!
WARNING careful when messing with exposed framework its works but my phone had issues
Thanks grmiyce
Woooogh! That info was sooo helpful. I was able to restore my phone ( HTC Desire 530 - TMobile ) to normal behaviour after it was stuck at the HTC logo for 2 days. How did it get there?
Well , long story short, I installed TWRP , did not make a Nandroid backup, and installed super su v2.46. Then to help fix the problem I installed super su 2.74 , all from twrp, but that did not help the situation. I wiped all that could be wiped from TWRP but that did not help.
I tried to install my stock ROM but could not find it in a zip format so that was a failure. I was considering a custom ROM (and still am) but to this point I am uncertain as to what ROM I can use with minimal to Zero issues ( i don't wanna brick the phone). I'll gladly accept any suggestions.
Anyways I came across this info and it saved my life...I am so happy.
Also as i am back to square one, I still have to try to network unlock this phone, it is locked with TMobile device Unlock app. I have paid for an unlock service and i was told that it was good to go but i could not get the device unlock app to reach to the 'permanent unlock' screen so i can unlock the phone. And that is why i was trying to root to uninstall the app and reinstall it since it was a system preinstalled app.
Btu anyways , I'll have to figure that out, at least the phone is back up now..
Thanks.
grniyce said:
There is no effective RUU restoration that works once you follow the root, twrp, processes listed here on XDA. I've restored the original recovery.img, still no go. I've tried the full RUU available on HTC to no success. So be forewarned.
However, there is a way to recover your device. I'm no developer by any means, but this is the process which a kind user informed me of, so I'm sharing it at top level. See his comment below which is the true saving grace.
My 530 is a MetroPCS variant, so I went to the HTC site and downloaded RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_TMOUS_1.01.531.25.exe
Then I used a RUU decryption tool, and extracted the files mentioned (boot.img) and (system.img).
I made sure TWRP worked on my handset still, which it did.
I put both files boot.img and system.img on the handset through the USB cable. I also copied the BETA-SuperSU-v2.74-2-20160519174328.zip to the same location.
Then I chose Install in TWRP, and chose "Image" instead of "Zip". It's a little box bottom right in TWRP on the Install screen.
First I installed the boot.img followed up by the system.img. I almost clicked reboot, and TWRP gave me this notice "Warning no Operating System installed." ---
...so I remembered the BETA-SuperSU-v2.74-2-20160519174328.zip file I copied over, and I went and installed it through TWRP.
I then rebooted the phone, and it rebooted a couple times, but then VOILA it was back to perfect, all data wiped of course, but fully rooted and ready to go.
Here is a link to the files I extracted using the RUU decryption tool. It is the T-Mobile variant, but works perfect for MetroPCS as well. https://drive.google.com/drive/folders/0B4K9JR5eVMSnWmtOMlV3Tkx1V2M?usp=sharing
Click to expand...
Click to collapse
it work on htc desire 530 OR not?
So did anyone end up figuring out how to unroot this phone? Have to send it in for a warranty repair, and need to restore it back to stock settings but only seem to find horror stories like OP's, when it comes to actually trying to do it. Normally I never end up having to unroot a phone, so didn't bother seeing if it was possible ahead of time. Hopefully someone knows how to do this.
m3gapxl said:
So did anyone end up figuring out how to unroot this phone? Have to send it in for a warranty repair, and need to restore it back to stock settings but only seem to find horror stories like OP's, when it comes to actually trying to do it. Normally I never end up having to unroot a phone, so didn't bother seeing if it was possible ahead of time. Hopefully someone knows how to do this.
Click to expand...
Click to collapse
First dsclaimer you find in almost every rooting thread is:
Your Warranty is now VOID
So, it is the risk you just took when decided to root your phone...
sorry mate
yurais said:
First dsclaimer you find in almost every rooting thread is:
Your Warranty is now VOID
So, it is the risk you just took when decided to root your phone...
sorry mate
Click to expand...
Click to collapse
Yeah, I've seen that disclaimer multiple times. However, the warranty portion of my post is non-consequential and unrelated to my real question: *has anyone found a way to unroot the phone successfully, yet?* HTC explicitly states on their website that unlocking the boot-loader doesn't void your warranty, in and of itself. Only damage that occurs as a result of said rooting (e.g: hard-bricking your phone by installing the incorrect ROM or over-clocking the CPU).
That being said, (according to articles like these: motherboard.vice.com/en_us/article/jailbreaking-iphone-rooting-android-does-not-void-warranty) they wouldn't be able to deny me service, even if they wanted to. Not that you asked, but my phone has a manufacturer defect (faulty usb port) and is increasingly becoming more unstable; the root had nothing to do with it.
Thanks for the heads up, I'm simply looking for help in the other matter. I'll keep it in mind when contacting them.
HTC Desire 530 (Canada - Freedom Mobile) Bricked(?)
Hey guys,
I successfully unlocked my bootloader, installed twrp, installed supersu and obtained my root. This being the first time i've really ever used an android phone, I forgot to make a backup at this point, and I moved ahead. First thing I tried doing was uninstalling some of the default HTC apps. I downloaded app remover - started uninstalling, seemed to work fine, deleted a bunch of the files out of the recycle bin and my phone reset and since then will not load past the HTC boot screen. I let it sit over night and nothing changed, I've tried this method, i've tried the RUU files on the htc website. I'm pretty sure I need to flash a custom ROM or find an official rom at this point (Which seems near impossible). I know it's my fault for not backing up, and this phone isn't my main phone or anything, but it's totally driving me nuts at this point that I can't fix it. Anyone have any suggestions?
From the download mode screen :
hTC download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.000
RADIO-01.01_U113251341_59.01.60624G
OpenDSP-UNKNOWN
OS-1.01.1500.31
JUN 28 2016,11:30:13 (773773)
TWRP is still installed and working fine, and I am able to copy things to my phone still.
However it is saying:
NO OS INSTALLED in there somewhere.
Any help would be appreciated.
chiassoo said:
Hey guys,
I successfully unlocked my bootloader, installed twrp, installed supersu and obtained my root. This being the first time i've really ever used an android phone, I forgot to make a backup at this point, and I moved ahead. First thing I tried doing was uninstalling some of the default HTC apps. I downloaded app remover - started uninstalling, seemed to work fine, deleted a bunch of the files out of the recycle bin and my phone reset and since then will not load past the HTC boot screen. I let it sit over night and nothing changed, I've tried this method, i've tried the RUU files on the htc website. I'm pretty sure I need to flash a custom ROM or find an official rom at this point (Which seems near impossible). I know it's my fault for not backing up, and this phone isn't my main phone or anything, but it's totally driving me nuts at this point that I can't fix it. Anyone have any suggestions?
From the download mode screen :
hTC download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.000
RADIO-01.01_U113251341_59.01.60624G
OpenDSP-UNKNOWN
OS-1.01.1500.31
JUN 28 2016,11:30:13 (773773)
TWRP is still installed and working fine, and I am able to copy things to my phone still.
However it is saying:
NO OS INSTALLED in there somewhere.
Any help would be appreciated.
Click to expand...
Click to collapse
Awesome job my man saved me from a brick last night flashed boot system then supersu and all rooted and we'll[emoji41] [emoji12]
Sent from my HTC 2PST2 using XDA-Developers Legacy app
I can confirm that the decryption tool works for update 1.36.1550.5 on the MertoPCS version
http://www.htc.com/us/support/htc-desire-530-metro-pcs/news/
RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.5_Radio_01.01_U113251531_68.01.61229G_release_495720_signed_2.exe
*edit* it still get a notification about an update
guess ill just use htc's method
I can not install a rom on my htc desire 530 because the android version I have is 1.01.619.1 and the one on the htc page is 1.01.617.25.
help
RUU from HTC says phone wrong model, TWRP says right model, update fails!
I'm getting an update available notice on my HTC Desire 530 from MetroPCS. It says that "Software update: 1.36.1550.14 (66.88 MB) This update contains critical security updates and system enhancements to improve overall device performance."
I'm currently on 1.36.1550.5 so I tell it to Install now. It downloads, reboots into recovery, which is TWRP 3.0.2, and when I look at the log, it failed.
"This package is for "htc_a16ul" devices; this is a "a16".
M60QCT.02.003.021
E:unknown command [set_err_msg]
This package is for "htc_a16ul" devices; this is a "a16""
When I am in download mode, it says it is htc_a16ul.
So, I tried downloading the update from HTC on my computer. I grabbed this file:
RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.14.exe
It fails basically with the same error.
How can I flash the update?
Boot into download mode and then run the .exe update
Worked great. Thanks Bennyoo
To whom may help me solve the issues I am facing,
My phone is stuck on the 'Setup wizard has stopped working' and I am not able to flash the original stock rom. Looking up the Setup wizard problem, I came across many posts but none helped. I suspect that the system files of my phone are corrupt. I can't exactly explain why, but it happened. I was trying to uninstall an app (apex launcher) which I had converted to system app. In the end, I had to do a factory reset through recovery.
On booting, I was shown the previously mentioned message and I can't go past it. I can't slide down the notifications nor click any of the soft keys. I tried every solutions posted by other users. This makes me suspect that the system files has become corrupt, and thus the Settings app cannot be opened.
I am new to flashing. I tried to flash the stock rom (RUU - 2gb zip) I found for my a55ml DTUL Europe J15, but it doesn't work. Maybe I need the recovery.img file for it to work? I need some guidance on this one. Can someone send me this recovery.img file?
My phone is rooted (kingroot), bootloader locked, S-ON. And, I can't detect it on ADB. Note: the phone is NOT on bootloop, and boots properly until the 'Setup wizard has stopped working'. I left the phone for flashing at a repair shop, but they tell me they are still trying.
And so, I seek help from anyone who can help me or point me towards someone else who can.