• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help formated rom

meetmehta

meetmehta

Lurker
I have a HTC desire 816 dual SIM whos SIM 1 Has both cdma and gsm and sim 2 is gsm. I have rooted my phone with cwm recovery mode and installed super user.everything was ok but once I entered into cwm recovery mode. Then I selected mounts and storage. Then I formated system,data cache ,boot and everything and when I rebooted I could see HTC logo only .I gave my phone for repair but after that there is one another problem.when I switch it on it does shows HTC logo ,but goes to bootloader and shows tampered and locked but when I directly enter the bootloader through recovery mode then it shows unlocked,I don't know what's the problem,pls pls help
 
Last edited by a moderator:
Well when you formatted system you erased the Android ROM, and formatting boot erased the kernel. So it was not surprising it didn't boot after that. If you didn't know what was in those partitions, why did you format them?

As for the current state, the worrying one is when you switch it on it goes to the bootloader. If it doesn't boot normally then it's not been fixed by your repairer. What recovery do you have now (CWM or stock)? We need to know what the state of the device is, what works and what doesn't, before we can know how to fix it.

Also, and I know this is a long shot, did you use CWM to make a backup before you started formatting everything in sight?
 
Does that phone have an sd card or do you have a rom zip in the phone storage?

And PLEASE let this be a lesson to always have a recent backup before doing ANYTHING to your system (especially wipe it lol)
What was going through your head when you did that mate? (sorry I'm trying not to be rude, just trying to understand)
 
So your options now are either:

1) Find a custom ROM for that device, copy it to the sd card (you can see whether CWM lets you mount the card over USB, otherwise use a card reader or adb push it to the phone while in CWM). Then you can use CWM to install it.

2) Find a RUU (a HTC ROM Update Utility) for that model and that CID (customer ID - basically region + network branding if any), put the phone in fastboot mode (select from bootloader), connect to PC via USB and run the RUU to reflash the whole phone. You may be able to find an RUU at HTCdev.com, or else try shipped-roms, androidruu or a search of XDA, or see whether there is anything in our desire 816 forum.

3) If someone else has made a CWM backup of the stock ROM and posted that you could download it, copy to the card or phone, then restore using CWM. As with ROMs it's vital that it's a backup of exactly that model of phone, or else you'll just make things worse.

It's perfectly fixable, any of those methods would work.

BTW it sounds like whoever you took it to to fix it did exactly nothing, since if I understand right it sounds like it's in the same state it was in before.
 
[QUOTHadron, post: 7000615, member: 219218"]So your options now are either:

1) Find a custom ROM for that device, copy it to the sd card (you can see whether CWM lets you mount the card over USB, otherwise use a card reader or adb push it to the phone while in CWM). Then you can use CWM to install it.

2) Find a RUU (a HTC ROM Update Utility) for that model and that CID (customer ID - basically region + network branding if any), put the phone in fastboot mode (select from bootloader), connect to PC via USB and run the RUU to reflash the whole phone. You may be able to find an RUU at HTCdev.com, or else try shipped-roms, androidruu or a search of XDA, or see whether there is anything in our desire 816 forum.

3) If someone else has made a CWM backup of the stock ROM and posted that you could download it, copy to the card or phone, then restore using CWM. As with ROMs it's vital that it's a backup of exactly that model of phone, or else you'll just make things worse.

It's perfectly fixable, any of those methods would work.

BTW it sounds like whoever you took it to to fix it did exactly nothing, since if I understand right it sounds like it's in the same state it was in before.[/QUOTE]
Repairer iinstalled the Rom ,phone started ,but again software got corrupt
 
What's the difference between A5_dug and A5_dwg,because my bootloader shows A5_dwg but when I tried to flash Rom for A5_dwg through cwm it shows that your device is A5_dug
Can service centre repair my phone???
 
So your repairer installed a custom ROM? Interesting. (I infer that from the fact that you still have CWM).

I would normally trust the bootloader on things like device identity. If you are unsure and have fastboot set up on a computer try connecting the phone in fastboot mode then using the command "fastboot getvar all" - that should be definitive. It's easier to imagine recovery having the wrong ID (or having been built for the other variant) than the bootloader being wrong.

An md5 mismatch implies you had a bad download.

I've not so far been able to get an answer to what the difference between dwg and dug is. There is a thread for a different recovery here, which you could try: http://forum.xda-developers.com/des...recovery-twrp-2-7-1-0-touch-recovery-t2854392
 
A properly-equipped service centre can repair it. Whether they will agree to do I don't know - possibly depends where you are. Nothing to lose by asking, but do tell them up front that it is rooted - they'll know the moment they look at it, so no point sending it to them if that's going to be a problem. But if your problem is just software you should be able to fix it, it's just a matter of finding the right software for it.

This XDA thread seems to have backups for the A5_DWG which can be restored using TWRP (another custom recovery - it also has links for TWRP versions you could install). That's assuming that your bootloader is giving the correct information about which device you have. A couple of posts in this thread have links for a TWRP backup for that device as well. I've not been able to find a CWM backup, so you'd need to change recovery to use either. I've also not managed to find an RUU for that device (which would return it completely to stock, which is the first thing I'd expect a service centre to do).
 
You must log in or register to reply here.
Back
Top Bottom