So I think I just bricked my phone... I tried to update my phone by reinstalling the stock recovery as per this video:
https://www.youtube.com/watch?v=PPPT5J8xG6w
After updating, the phone got stuck on the error screen. I was able to go back into recovery and go back to the home screen. After some googling, I found this:
http://forum.xda-developers.com/htc-one-m8/help/ota-lollipop-update-fails-red-triangle-t3015597
So I followed the steps and unrooted my phone and tried again. After the update, my phone won't go past the splash screen. I tried going into recovery and wiping the phone and rebooting, but it never gets past the splash screen. Help please!
CID-ROGER001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.631.3
eMMC-boot 2048MB
If you can flash an ruu then I would suggest flashing a stock latest Rogers ruu and starting from there
danial.aw said:
If you can flash an ruu then I would suggest flashing a stock latest Rogers ruu and starting from there
Click to expand...
Click to collapse
How would I flash and RUU? And where can I find a Rogers RUU? I can only find US/Europe RUUs. Please bear with me, I'm new to all this, but I'm trying to read as much as I can.
Bump
I'm trying method 2 as per SneakyGhost's FUU guide, but my computer is not detecting my phone despite it showing up in the "Safety Remove Hardware and Eject Media" tab (Android 1.0). In addition, the phone is showing FASTBOOT USB when connected. Stuck at a standstill right now.
Just an update on the situation, maybe this will help someone in the future - Progress so far - I was able to flash TWRP 2.8.7.0 as instructed a guide on the Android forums (I wish I could post links!).
Working on getting a rom to flash onto it now... I think I'm getting close...
ChickenOmelette said:
Just an update on the situation, maybe this will help someone in the future - Progress so far - I was able to flash TWRP 2.8.7.0 as instructed a guide on the Android forums (I wish I could post links!).
Working on getting a rom to flash onto it now... I think I'm getting close...
Click to expand...
Click to collapse
Same issue as you right now. Attempting to download a nandroid backup and then push it to my phone via fastboot and restore using TWRP and see if that works. Let me know how you make out.
essteekay said:
Same issue as you right now. Attempting to download a nandroid backup and then push it to my phone via fastboot and restore using TWRP and see if that works. Let me know how you make out.
Click to expand...
Click to collapse
Unfortunately, I didn't even have a backup - I'm having enough trouble getting the damn thing to boot!
ChickenOmelette said:
Unfortunately, I didn't even have a backup - I'm having enough trouble getting the damn thing to boot!
Click to expand...
Click to collapse
I managed to get a nandroid 4.4 backup onto my device and restored it. Worked and now my phone is back up and running and going through the rigmarole of updating apps and restoring my media/data backups.
essteekay said:
I managed to get a nandroid 4.4 backup onto my device and restored it. Worked and now my phone is back up and running and going through the rigmarole of updating apps and restoring my media/data backups.
Click to expand...
Click to collapse
Who is your carrier? And where did you get this Nandroid backup?
ChickenOmelette said:
Who is your carrier? And where did you get this Nandroid backup?
Click to expand...
Click to collapse
Fido, but my CID is Rogers001 (same network, probably that's why).
I used this thread as reference.
Downloaded the 3.34.631.4 - TWRP Recovery Nandroid from the CID Rogers001 part. Here's a direct link to the Nandroid backup.
From there, I unzipped the file and then transferred it to my M8 using my SD card (you can also push it straight to the device if using fastboot). I used the file manager in TWRP to move it into my backup folder (TWRP > Backup > Serial Number) in TWRP and then restored it.
Let me know if you've got any other questions. Seems to be working for me right now.
essteekay said:
Fido, but my CID is Rogers001 (same network, probably that's why).
I used this thread as reference.
Downloaded the 3.34.631.4 - TWRP Recovery Nandroid from the CID Rogers001 part. Here's a direct link to the Nandroid backup.
From there, I unzipped the file and then transferred it to my M8 using my SD card (you can also push it straight to the device if using fastboot). I used the file manager in TWRP to move it into my backup folder (TWRP > Backup > Serial Number) in TWRP and then restored it.
Let me know if you've got any other questions. Seems to be working for me right now.
Click to expand...
Click to collapse
Seems like amazing news. Hopefully this works. Apparently after this is done the OTA has to be applied? Is that your next step? Will you be flashing a rom after your firmware is updated?
ChickenOmelette said:
Seems like amazing news. Hopefully this works. Apparently after this is done the OTA has to be applied? Is that your next step? Will you be flashing a rom after your firmware is updated?
Click to expand...
Click to collapse
Right now, just going to keep things as is. I'm in a location with pretty spotty internet, so downloading 1+ GB ROMs isn't that easy. Probably just keep it so that I can use my device and then tinker on it when I'm back at home. I was notified that the Android 5.0.1 update is available for download, but right now I'm holding off doing anything else.
I'm just glad I got it back to working order now.
Here's what I got told to do:
If you want to properly update your firmware via FUU, you have to get to a stock rooted rom, stock recovery, s-off using Sunshine, apply the SuperCID mod, and then update your firmware. After that, reinstall TWRP and whatever modern rom.
Click to expand...
Click to collapse
After doing all this, I tried updating the phone from the Rogers pushed update. Unfortunately, that pushed me back to step 1, where the phone wouldn't boot up, so I had to start from scratch. Now that I have SuperCID, I'm going to try to apply a stock OTA from another carrier. Wish me luck!
So I started from scratch and the Rogers update just doesn't want to work. Every time it updates, it would show the red HTC error icon. I ended up taking the update off the phone's internal memory, as it could still boot, and pushing it via Method 2 seen in this guide as a reference. After pushing flashing (it took two times), the update finally installed, BUT it STILL GOT STUCK AT THE DAMN BOOT SCREEN.
At this point, I got frustrated and went straight to flashing a custom ROM as per the instructions given here. After long moments of waiting, it finally started installing. Very important to note, but I got stuck at the AROMA installer at the "Please Wait" screen. After pressing the power button and vol up, the got out of that screen and continued to install. Now I have a custom ROM, updated firmware and SENSE 7.0! Amazing. I hope that this post helps you in what you'll have to do next!
I blame Rogers for pushing out s***ty updates. But consider this problem SOLVED.
Related
Guys,
My Evo says Froyo 2.2 is avail for download when I check HTC Updates... I hit accept, it downloads, then asks if I want to install NOW... I HIT YES, and it takes me to the boot loader page, THEN DOES NOTHING.. It doesn't boot into recovery mode like it is supposed to, and it just sits on the Boot loader screen, NO TRIANGLE, NO BAR on the bottom showing the progress, IT JUST SITS THERE on the boot loader page with the 3 Androids on the bottom... I have already tried to hard reset the phone, BUT that didn't work... PLEASE HELP !!! Is there a way to HARD reset my EVO BACK to BEFORE ALL OF THE UPDATES??? IS THERE A WAY TO Force boot into recovery to apply the "update.zip" ??? Please advise...
Mine did'nt go no where near the bootloader screen...
I hit the download...then it just installed like any other app...except it brought me to a bar progress page a couple of times. Then the phone rebooted and whala...froyo.
I must say this...I was previosly rooted but unrooted to do it!!!
Are you rooted or unrooted to start off with?
Was rooted, but then I did the "update of June 29th" and ruined ALL of my fun... Is there even a way for me to root my phone now??? How do I get it to go into recovery?
Same issue
My EVO ISN'T ROOTED, and I'm having the same exact problem
You're hosed root wise until someone cracks the rom, if they crack the rom. Most likely you'll need to update to the official version once HTC releases an upgrade as they claimed they would eventually do on Twitter.
im not trying to root my phone, i just want froyo
right, I WAS rooted, the update in JUNE fixed that for me =(... NOW I just want FROYO which is available from Sprint/HTC OTA, it just wont install?????????? I think I can install it as an update.zip if I could get my phone into RECOVERY mode... When at the bootloader, if I hit Recovery, it just boots back to the BOOT LOADER????
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
This is a great recommendation, but I haven't done any ROOT or ROMing to my phone since I've owned it, I've stayed true to the true image they released, and I'm not comfortable downgrading it to some other image that wasn't on the phone. I attempted to do the instructions outlined and I was unable to get pas the stage of pushing the:
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
to the phone. It says USB error, and I have debugging mode enabled.
cardiox said:
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
Click to expand...
Click to collapse
I RE-Loaded this version, as the other "older" versions would not work (re-loaded, as this is what I already HAD on my phone)... It wiped the system, and ALL of my info/apps (make sure you back up) and then I was able to do the Froyo Update... YES !!!! Thanks...
http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe
I did the same, thank you !
No prob...have fun!!!
Froyo Update Won't Install
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Nick,
Please read the earlier posts, and follow the link from Cardiox... He said the following...
"I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-...urn-stock.html
This is the route I took and was just like you...I had no probs this way!"
Then read my posts, and you will see that I had the SAME problem you are having, and this worked for me... I posted the thread... It is pretty easy if you follow the instructions... Let me know if it works for you... Good luck !!!
wolverinexc said:
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Click to expand...
Click to collapse
I am not a genius by no means thus I am only sharing info that I have from personal trial and error. If you are going to a bootloader screen during this update process and your SD card is mounted then you most likely will need to bite the bullet and either do a factory reset or follow the link instructions so given. For some reason this update can not find the original factory code or RUU that it is trying to update. Sounds like your SD card is mounted but it can't find it...I would strongly consider just starting over with that link program. It does not root you it just puts you back square one with factory code. Then the update will have something to build off of...which you apparently don't have for whatever reason.
Ok, this is what I needed to know. I'm backing up my stuff with bitpim and will just do this. Thanks for all the help and the speedy responses!
-Nick
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
zwp1990 said:
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
Click to expand...
Click to collapse
Foremost: ugh. Sorry man - that sucks.
So it sounds like your best option would be to get an sd card and apply a RUU from there. Flippy498's Google Sheet is a great resource for where to get them and how to use them.
You might be able to use the Windows-executable RUU directly from Sprint. I'm pretty sure you'd need to be in download mode when you ran it though. It's not as straightforward as the sd card method, but they're usually my first fallback.
Keep in mind that both of these options are destructive - your phone will be brought to a factory state (stock firmware, recovery) and anything on the phone's internal memory will be wiped.
It might be worth exploring why TWRP keeps failing. If we could solve that, you could install the ROM of your choice and not worry about RUUs. But that's definitely more work and probably not necessary if you're not trying to save anything. Once the RUU has been successfully applied, you can just unlock the bootloader anew, install TWRP, and do whatever you want from there.
Thanks a ton that fixed it!
zwp1990 said:
Thanks a ton that fixed it!
Click to expand...
Click to collapse
Wonderful! Enjoy your new phone!
(If you're satisfied with the resolution, the convention in this forum is to mark a thread 'solved' in the title when an issue is resolved. This'll help folks know where to direct their help.)
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