HTC DESIRE 816 DUAL SIM INDIA ("This built is for developement purposes only do not")
Dear Friends,
My handset HTC Desire 816 dual SIM reboots from this screen "this built is for development purposes do not distribute outside of HTC failure to comply may attract....."
My phone was rooted back in Jan2015
The mistakes I made
a) Not backed up stock firmware
b) Don't remember the name of stock firmware.
c)Don't have backup of the custom ROM either.
d) Don't remember the Bootloader version or any other details.
My phone remains dead when the charger is pulled out .
When connected with the charger it reboots from this screen with "battery symbol" and the Built development message" within 2 seconds and comes back to same screen again.
The only reason I'm posting this thread because I liked using this phone very much Its my first smartphone "In other words you guy's can say I don't have funds to buy a new phone "
Please help me with some valuable knowledge and information you guys poses and May god be with you "God Bless"
Hari Mahto
Feel free to ask me further informations if needed.
This post is in the wrong forum section. Next time, use the Q&A section.
Use fastboot to flash the official TWRP (https://twrp.me/devices/htcdesire816.html).
You can access fastboot by choosing it from the bootloader menu which appears when you hold volume down and power until the screen comes on when the phone is switched off. Press power to confirm the selection in this menu, and select with the volume keys.
The fastboot computer program is found in the Android SDK's platform tools. You will have downloaded it to do the unlock bootloader process. It runs in the CLI.
Once you have installed TWRP, go back in to the bootloader menu and open the recovery.
From there, just install any ROM.
Related
Our Cubot P9 has apparently bricked after a manufacturer firmware upgrade.
The firmware was downloaded from the official website, copied to a uSD card and then installed from via the Android System Recovery menu (accessed after cold boot by pressing volume-up & power buttons together).
Having followed Cubots instructions to the letter, we can only think that they have provided a link to the wrong image, despite it ostensibly being the correct one.
Current symptons are: phone still powers but not off again (requires battery removal). There is no ability to enter the fastboot or firmware recovery menus. The display lights-up but with a random/incoherent output.
All the threads, thus far, have included putting the device into fastboot or firmware recovery mode - which is not an option for us.
We'd like to know if this a recoverable situation? If so, what's the next step?
Hi,
If you can't enter recovery or fastboot mode, you won't be able to do much I'm afraid....but I suggest you ask in this discussion thread about your device....
http://forum.xda-developers.com/showthread.php?t=2612234
Good luck!
KJ said:
Hi,
If you can't enter recovery or fastboot mode, you won't be able to do much I'm afraid....but I suggest you ask in this discussion thread about your device....
http://forum.xda-developers.com/showthread.php?t=2612234
Good luck!
Click to expand...
Click to collapse
Thanks for the reply.
To put the question another way: in general, when the firmware in an Android
device goes awry, is there any way to recover the device using tools available on the user?
The way we see it is thus:-
In our case it's a Cubot P9 phone but it could just as easily be any other, or even a tablet.
Presumably during development and factory manufacture, there is a means to either load firmware in the first instance or reload it when desired. Short of hardware failure, we're sure that the original device developers have done exactly what we have done a dozen times on the bench.
Given the whole nature of the 'eco-system' is much less proprietary than it used to be (remember Nokia S40 anyone?) perhaps devices like ours are entirely lost to scrap heap?
Considering our device though: it still boots with the brand logo displayed, after which, while the display is completely distorted, the wallpaper and menus are visible. Even the volume & power buttons evoke a response. Atop this are its recognition as removable storage under Windows. Surely this indicates some potential for recovery?
Thanks again.
Perhaps, but if you can't flash anything to the device, you can't do anything. Please ask the folks in the thread I linked....or consult a service centre. ?
---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------
If the thread I linked doesn't appeal to you, you can ask here....
>Android Development and Hacking >Android Q&A, Help & Troubleshooting
Thread closed. Thank you.
I am having problem flashing roms my Micromax a68.
The phone is rooted with Kingroot and have Kinguser and busybox installed.
I have installed the Lewa recovery image too.
For flashing the rom, I copied the rom "Cyanbook v0.4" to the sd card in my phone, switched on the phone in recovery mode, cleared out the factory, dalvik cache and caches and then installed the rom.
The rom gets fully installed and a notification on the screen says "Reboot to enjoy Cyanbook". Then I'm rebooting.
The phone starts with the welcome graphics, then after a while, the menu,home and back buttons under the screen lights up and the phone gives a slight vibration.
Now everything till this is as per the protocol as after the vibration, the screen enters the OS.
But the thing here is, even after the vibration, the screen is stuck at the welcome graphics and is not going into the OS.
I tried a different version of the rom and that also gave similar problem.
Now..after this, i tried to reboot the phone, the phone reboots as per norms automatically with the previous OS which was there before i installed the rom.
It would be great if you could give the solution step by step as i am not an expert or anything
N.B- 1. These roms worked perfectly before, but recently i had a brick and had to give the phone to an engineer who used a box to install a stock rom in the phone.
2. I dont think its a regular still boot screen problem, as in those times the phone buttons dint light up, neither was there the vibration.
Hi,
As far as I see, the rom you are flashing was not made for your exact device model number. And so you know, Flashing anything not made for your exact device make and model number is a good way to brick your device. Which you may have done now unfortunately.
You need to only use software made for your device, no other.
Here us a great resource thread for your device and has stock rom information. Try to flash your stock firmware and perhaps you will be fine. If you need any further help with this or anything else, I'd ask in this thread as well,
> General discussion > Upgrading, Modifying and Unlocking > Micromax A68 (Android 4.0.4)
If you can't find help there, try flashing a rom made for your specific device, or ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
First of all i have no knowledge on how to fix my phone or flashing.
My question title are based on what i read from other threads.
My Problem
Connected Phone to USB to Charge
Removed Phone from USB
Lock Screen wont appear
Decided to Reboot the phone
After Rebooting, I got stuck at loading/bootloading screen
Decided to go to Factory menu by holding Vol Down and Power
Chose Reboot Option
After that, the phone rebooted nonstop like 5 times and turned off.
Now my phone won't charge, or power up
Now trying to find how to fix it for hours now
My phone has an internal battery and memory / non removable - cause all the threads about flashing and videos about flashing i watched was removing batteries (but i have an internal battery )
It is a rebranded china phone called Cherry Mobile Omega Infinity.
According to the SPECS sheet:
Mediatek MT6592 1.7GHz octa-core CPU.
Now all i need are the whats and how guides.
Thanks in advance
XDA Visitor said:
First of all i have no knowledge on how to fix my phone or flashing.
My question title are based on what i read from other threads.
My Problem
Connected Phone to USB to Charge
Removed Phone from USB
Lock Screen wont appear
Decided to Reboot the phone
After Rebooting, I got stuck at loading/bootloading screen
Decided to go to Factory menu by holding Vol Down and Power
Chose Reboot Option
After that, the phone rebooted nonstop like 5 times and turned off.
Now my phone won't charge, or power up
Now trying to find how to fix it for hours now
My phone has an internal battery and memory / non removable - cause all the threads about flashing and videos about flashing i watched was removing batteries (but i have an internal battery )
It is a rebranded china phone called Cherry Mobile Omega Infinity.
According to the SPECS sheet:
Mediatek MT6592 1.7GHz octa-core CPU.
Now all i need are the whats and how guides.
Thanks in advance
Click to expand...
Click to collapse
Hello there! Welcome to XDA!
First register an XDA account (so you can ask in the proper forum)
then, you may ask for help here: (see below)
Android Q&A, Help & Troubleshooting
You will have a much much better chance of getting an answer in the above thread.
TEKHD said:
Hello there! Welcome to XDA!
First register an XDA account (so you can ask in the proper forum)
then, you may ask for help here: (see below)
Android Q&A, Help & Troubleshooting
You will have a much much better chance of getting an answer in the above thread.
Click to expand...
Click to collapse
HI!
yes thanks for the reply. i got logged out it seems. i have another post like this one with my acct name on it. just delete the other one if necessary.:good:
I rooted my device and deleted some system apps and then i got lots of problems with my phone:when i turn on wireless phone freezes,cant accsess front camera,flashlight can't start...Restarted phone on factory,wiped data,still same.
Than i tried to find some factory android for my phone and no sucsess.I found some custom roms on some Ru site and tried to flash my phone using guide from some this CZ site: http: //androidforum.cz/ topic48780.html
After i flashed my phone i was unable to enter recovery mode by holding power and volume+ (instead entering recovery mod i got green lines over my phone screen when i do that).
Any solutions?
XDA Visitor said:
I rooted my device and deleted some system apps and then i got lots of problems with my phone:when i turn on wireless phone freezes,cant accsess front camera,flashlight can't start...Restarted phone on factory,wiped data,still same.
Than i tried to find some factory android for my phone and no sucsess.I found some custom roms on some Ru site and tried to flash my phone using guide from some this CZ site: http: //androidforum.cz/ topic48780.html
After i flashed my phone i was unable to enter recovery mode by holding power and volume+ (instead entering recovery mod i got green lines over my phone screen when i do that).
Any solutions?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
First, please create an account so you can post in the other forums, Then, you can post your question here:
Android Q&A
You'll receive expert advice there. Good luck and welcome to XDA!
Hi everyone,
I own a Motorola Moto G2 (XT1068, dual sim) that came used with Android 6.0 on it.
I installed TWRP (twrp-3.0.2-3-titan.img) on it but failed to root Android 6.0 as well as 5.0 for whatever not yet understood reason. I don't do Android development for a living but I'm an IT professional, so handling adb and fastboot as well as reading and understanding instructions isn't a problem.
I flashed stock Android 4.4.4 (RETDEALL_XT1068_4.4.4_KXB21.85-14) which I successfully rooted by installing SuperSU via TWRP.
Next I updated SuperSU, verified that root access is indeed working and installed FlashFire, which I hoped to use to install OS upgrades, possibly without losing root. FlashFire is new to me (as of yesterday), everything else mentioned up to here is not.
I used the "Flash ZIP or OTA" action from within FlashFire and the previously downloaded update file in the /cache directory. I can't reproduce the file name since the phone is currently unusable and I didn't write the file name down prior to using FlashFire.
The state of the phone after this unsuccessful attempt was that of a broken USB device, i.e. unable to even register as whatever type of USB device. I learned that this can be fixed by holding the power button down for more than one minute, after which I managed to
get the phone to be shown as working "RELINK HS-USB QDLoader 9008" USB serial device in Windows 7 device manager.
I used the information in these two threads:
http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Since I started with Android 4.4.4 trying to upgrade to 5.0, I had hoped that the blank flash package for one of these Android versions would help fix my problem, but as of now, this doesn't seem to be the case. At the end of the blank flashing process, I get the message
FAILED <blank-flash:sdl-transfer-image:sdl-hello: error sending packet>
After that, the phone still has a black screen and cannot boot into anything. Repeating blank flash works after resetting whatever part of it is still working by holding the power button down for about 30+ seconds.
Is there anything obvious (or maybe even not so obvious) that I missed?
Thanks for reading and any help and/or pointers in the right direction.
Hello and thank you for using XDA Assist,
please create an account and post your question in our Android Q&A section:
G 2014 Q&A, HELP & TROUBLESHOOTING
The experts there should be able to help you.
Kind regards & good luck
Trafalgar Square
XDA Assist