I've customized gadgets and electronics before but phones are rather new to me but I'm a very technical person that makes dumb mistakes apparently. Now I seek someone more experienced to put me on the right path.
I'm unable to post links however I followed the directions floating around
directions and now I'm not stuck in the hboot 0.77/fastboot every time it starts. I know my phones not bricked but it's in a very annoying state. I tried a hard reset but this changed nothing.
Currently it's at S-ON and radio 1.00.03 so it seems that downgraded fine. It did get though the whole process fine without error only 2.1 didn't boot up.
I was attempting to do a downgrade so I could root. I had nothing special on the phone so I didn't bother with a backup (besides my sdcard.)
When I run bootloader it tells me "No Images" and "No image or wrong image!" PB31IMG.zip I assume this may have something to do with my problem and I think it's a permissions issue because I didn't re-set them when I backed up my files to format to fat32.
I think this is my problem because I know the files would have lost permissions when I copied. I haven't tried to update again because I assume it will have the same result (that and I've read nasty stories about re-flashing the same version, not that this would do that). I'm unsure on how to get to a shell with the phone in this state or if there is some other way to get it running again. I tried clearing everything and did a hard reset with no luck.
Any help would be much appreciated.
-Blake
Ok I got it working by doing a reinstall. Not sure why it didn't work the first time.
blakeem said:
Ok I got it working by doing a reinstall. Not sure why it didn't work the first time.
Click to expand...
Click to collapse
Reinstall of what? I get the same errors when trying to get any PB31IMG.zip file to load.
dj-anakin said:
Reinstall of what? I get the same errors when trying to get any PB31IMG.zip file to load.
Click to expand...
Click to collapse
I just reinstalled the .zip
What errors?
Ah.
Here's my new thread on my problem.. http://forum.xda-developers.com/showthread.php?t=783123 Been working on it since last night.
I'm going to be away soon and won't have easy access to a non-professional PC (meaning any computer I may have access to - I won't have admin rights with). I didn't want to wait for a root+TWRP dev package for Lollipop to be released. I wanted to just get it done, (I was having bad problems with KitKat on some select apps because of LG's 4.4 coding, long story, but I won't even go there...)
I saw that I can go to the LG support site via a link from Android Central and manually upgrade to Lollipop way before the OTA rollout even begins. I had heard rumors of people having problems, read posts, and learned how to avoid it all. I reset everything before upgrading. I did many factory resets after getting Lollipop, (I know, a lot). I got rooted and set mostly everything up.
I wanted to get Xposed loaded, BADLY. I looked it up for Lollipop and realized that I'd have to flash a custom recovery. I expected as much. When I looked that up, I realized that I would have to either use a downgrade-upgrade method (which I didn't feel like going through) or a mandatory requirement of factory reset though a process. I had already set up all of the system stuff and restored from Titanium backup most of my apps. There was no way I would factory reset because I hate resetting-up the system stuff. - - - - - BIG MISTAKE 1
So I found a thread for the D850 (AT&T) version (no I didn't flash a bad radio or anything, I thought I knew what I was doing because I was only flashing recovery stuff for Lollipop, not an AT&T rom or radio.) This was to install TWRP without downgrading or resetting. The instructions said to copy files from an aboot.img and other boot images and such (to replace the recovery) on to the internal memory and use a terminal to type in code. I did it and rebooted it.
I made a horrible mistake.
When I held the power button on the phone, nothing happened. I found out that when plugging it in to the PC, it seems to be in download mode. It was fully charged. When using the restore/brick recovery software, I have tried different cables, different computers, checking to see if anything is corrupt, different USB ports, etc. with the files... Nothing will work. I keep getting an error with a red box about the model or something. "Model Information Check Fail"
So basically I have broken boot images on my device. I need to fix these.
Where do I go from here? All because I wanted Xposed on Lollipop without resetting.
Click to expand...
Click to collapse
I have this situation. I messed up with laf.img and aboot.img too (from D850, thinking it was harmless since trying to install custom recovery only) and device won't turn on but PC recognizes as download mode but can't flash. Please read above. I'm bricked and all restore methods have failed so far.
Source from u/nicksteron on reddit.
I'm having this issue now too. It seems the thing I downloaded and tried broke my boot images.
Have you been able to fix this?
I'm trying the LG Flash Tool but it stops me at the model check fail as well. Gonna try a kdz method next.
EDIT: I tried the KDZ method with LG Flash Tool 2014 using both a KitKat and Lollipop based ROMs and I get an error. The S/W Upgrade progress gets to 4% and then the error shows up. I need my phone. Help?!
Hello,
I just noticed something the other day and I do not know if this has any effect on my problem with the phone getting a usb not recognized error so I wanted inquire!
So I did a completely clean install of the [ROM] [Touchwiz-PC1,PD1] [100% Stock, Root, No KNOX, No Itson] [4/5/2016] deodox rom and have noticed that my boot screen no longer shows multiple lines while booting. The only thing I get now is:
Set Warranty Bit : Kernel
Before I would get that and several other lines including one about Knox. I also do not get the Sprint logo as one of the bootup screens. My question is, is this rom suppose to do this or did I do something wrong? I followed the directions 100%. I also notice that I also now get an error that it cannot do a fingerprint unlock on boot and I have to enter my emergency password.
Last but not least, if there is a problem. Is there anyway to put a OG5 rom on my micro sd card (I have a card reader I can put the micro sd card into to transfer files, I cannot odin) and restore it to then?
Thanks for any help!
Most of what you describe is not abnormal.
Your fingerprint may be data left over from Lollipop. Try deleting your fingerprints and add them back.
Be aware, if you factory reset, you'll need to flash systemless root again. Google search SuperSU zip if you need it; it's also linked in the ROM thread. If you factory reset for any reason, make sure you don't keep our have a folder in root folder named /carrier/ItsOn. The apk in that folder could activate causing numerous reboot prompts to complete activation.
Eventually, you're going to need access to a PC to do what you want. You might be stuck and unable to update; modified partitions can cause the failure to update on OTA and KIES. Custom stockish ROMs are coming but they won't be for PD1; it's already outdated.
You can't go back to Lollipop without a PC because you need to revert your bootloader to Android 5.1 to run that ROM. Without a TWRP backup to restore, you should also Odin the full stock tar rather than just the bootloader.
Sent from my SM-N910P using Tapatalk
samep said:
Most of what you describe is not abnormal.
Your fingerprint may be data left over from Lollipop. Try deleting your fingerprints and add them back.
Be aware, if you factory reset, you'll need to flash systemless root again. Google search SuperSU zip if you need it; it's also linked in the ROM thread. If you factory reset for any reason, make sure you don't keep our have a folder in root folder named /carrier/ItsOn. The apk in that folder could activate causing numerous reboot prompts to complete activation.
Eventually, you're going to need access to a PC to do what you want. You might be stuck and unable to update; modified partitions can cause the failure to update on OTA and KIES. Custom stockish ROMs are coming but they won't be for PD1; it's already outdated.
You can't go back to Lollipop without a PC because you need to revert your bootloader to Android 5.1 to run that ROM. Without a TWRP backup to restore, you should also Odin the full stock tar rather than just the bootloader.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have a PC, the problem is that it will no longer recognize my phone by USB. It always gives the USB not recognized error. I do have a folder in root called carrier but when I try to go into it with root it tells me my phone is not rooted. This does not make sense as my phone is rooted , per the installtion of the rom and I have other apps I have given root access too.
Arrg! Thanks for the info, any more will help greatly!
h4kudoshi said:
I have a PC, the problem is that it will no longer recognize my phone by USB. It always gives the USB not recognized error. I do have a folder in root called carrier but when I try to go into it with root it tells me my phone is not rooted. This does not make sense as my phone is rooted , per the installtion of the rom and I have other apps I have given root access too.
Arrg! Thanks for the info, any more will help greatly!
Click to expand...
Click to collapse
Did you enable developer options (tap build # in Settings/About device 7 times or more until enabled) and enable USB debugging in developer options?
Yes you should be able to detect device when you plug in to PC but you may not see COM connected in Odin without USB debugging.
If it's always not detecting, could be bad USB cable (broken out missing data lines) or bad PC USB port. Try others first, if that's the case. Hardware failure is rare but has been reported as suspect. Hopefully, it's simple rather than that.
Sent from my SM-N910P using Tapatalk
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
Hi! I have been reading some write ups, but im not sure what to do.
I have a M9 Sprint version that has been unlocked for a while now, like a year, I downloaded an app this morning to delete sprint junk apps and deleted them. Well the app failed and when i reset the phone, the sprint apps just reinstalled. Shortly after, on my drive to work, I felt my phone vibrating, and noticed it was stuck in a reset loop.
I tried loading in fastboot, to re lock boot loaded and attempt to go back to stock image. I used TWRP to root it, and i have formatted my computer since then and dont have any of the associated files, including any backups.
My goal at this point is to return to a working phone, oem image or not, i really dont care. What do I need to do?
I downloaded the adb/fastboot tool to my pc, but no devices are being found, and fastboot is not an option when i go to the boot loader.
THANKS!
thehoss said:
Hi! I have been reading some write ups, but im not sure what to do.
I have a M9 Sprint version that has been unlocked for a while now, like a year, I downloaded an app this morning to delete sprint junk apps and deleted them. Well the app failed and when i reset the phone, the sprint apps just reinstalled. Shortly after, on my drive to work, I felt my phone vibrating, and noticed it was stuck in a reset loop.
I tried loading in fastboot, to re lock boot loaded and attempt to go back to stock image. I used TWRP to root it, and i have formatted my computer since then and dont have any of the associated files, including any backups.
My goal at this point is to return to a working phone, oem image or not, i really dont care. What do I need to do?
I downloaded the adb/fastboot tool to my pc, but no devices are being found, and fastboot is not an option when i go to the boot loader.
THANKS!
Click to expand...
Click to collapse
There is a dedicated thread for sprint versions, you would have better luck posting in there, but check out this thread.
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
You might want to use an ruu via SD card method.
Rogue apps.. A perfect example of why rooted phones aren't for laymen.
As long as you have download mode and the original cable the fastboot issue will be driver related. You might have to force the physical address into the drivers. Google that!. It's about a 6 on the pc illiteracy skill scale (piss, for short, thats what it makes you scream at the screen).
Beamed in by telepathy.
squ89r97 said:
There is a dedicated thread for sprint versions, you would have better luck posting in there, but check out this thread.
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
You might want to use an ruu via SD card method.
Click to expand...
Click to collapse
Thank you,
I dont use the forums much. I will check it out.