Related
probably, i dowgrade my kaiser with lower version...(everything passed(unlock,flash)without problem and error...
after flash phone dead... nothing happen when try to power on,reset,boot,anything...try,almost 4 hour, everything what can find here, but still no luck...
no power, no bootloader, even i can't do anything with mtty couse i run Vista, and have prob to stop activesync working... everything what i got is
ZTE diagnosstics interface 6000 cdma 1x(com5)
zte nmea device cdma 1x (com6)
in my control panel/device manager,
that talking maybe phone is not totaly damage...
anyone help, any idea...this will be long long night...
I'm not sure what you mean exactly but I also had a dead Kaiser. It did not happen after flashing but my phone suddenly turned off and could never be turned on again. I first thought it was a battery issue but no.
Finally I returned it to HTC and they replaced the motherboard under warranty.
yes but my kaiser is not in warranty, customer buy it in Italy... and I kill him, sad but true...
well i might not be correct, bu it looks like you wiped the nand on the phone... i think if you look up the steps in the frankenkaiser thread it should help you out
but i can't go in bootloader mode....
if you look you dont have to enter bootloader mode..: http://forum.xda-developers.com/showthread.php?t=394584
ok, first , from now i'm on XP...
but always same... when attach in any button combination to the pc, it was always see the same, look on the pic
and in MTTY, i have the port from 1 to 10 &usb. on usb cannot connect, with the error "usb port can not open"
btw forgot to write, device is brand new, no hw damage
i make connection between kaiser and MTTY, over diagnostics port, but when try to type command(or Enter) nothing happens. how to use MTTY
as i see my kaiser stuck in download mode... (see in QPST & QMAT)... how to flash it or to restore it to normal mode(phone no power on, no going to boot mode)... i read emi&sbi, if it can help some...
if you look here from step 3 down i think this should walk you thru the process... http://forum.xda-developers.com/showthread.php?t=393337
if you look at the part right below step 2 it says to lower your com port for the diagnostic interface below 10, i think i saw that yours is set to 53...
i try on 3 differnet pc. try all comm port. mtty is my problem(one of them). when run mmty(choose connection base on diagnostic port), i can type anything, any command, enter,etc... nothing on screen, nothing happen after enter...
can someone explane how to flash kaiser via jtag...
someone who allready do it...
or send me to pm
Sorry no idea!
Hi mobilend,
i just saw your message... no idea about that!
Don't know if anybody already traced the testpoints.
You also would need some software tools to access the MSM chip.
Maybe i'm wrong but i read some threads about this kind of brick and maybe your able to recover without JTAG.
Perhaps the kaiser cracks could help you out
Regards,
scholbert
i do nothing since today...
if somebody have idea how to unbrick kaiser with jtag, write here or i may send device to him...
Problem
Hi excuse you have succeeded there?
I have yours same problem.
This is my fear, for this reason I have not had the courage to update my ROM.
I do not understand, the videos appear to be so simple, but at the same time, to read topics like these, I am in panic ...
Will I still be aware and courageous enough to update my ROM?
jonastamborin said:
This is my fear, for this reason I have not had the courage to update my ROM.
I do not understand, the videos appear to be so simple, but at the same time, to read topics like these, I am in panic ...
Will I still be aware and courageous enough to update my ROM?
Click to expand...
Click to collapse
Most of the problems come from not reading the information...
If you look at the number of users on here that have managed to upgrade their phone you will see that it way outways the number of people who have truly bricked thier phone. (A lot of the people who have upgraded thier phone have little knowledge about what unlocking means as well, so don't worry if it's a bit overwelming).
If you want to get started click "KAIS: Getting started" in my sig for a step by step guide by mskip. mskip, myself and some other members will help out with any questions you post in that thread. Also check out the info on the HTC Kaiser wiki page on the xda-developers wiki page.
Ta
Dave
Hello everyone, I bought a brand new IPPO Q78 (Android 4.0.4) via focalprice.com 2 month ago. First day of using it, and by using I mean simply installing a few apps, and after reboot, I got BOOT LOOP problem, so it wasn't able to get to tablets home screen. After lot of reading about similar problems, I was able to successfully unbrick it using (I suggest others with same cheap china tablet that are also soft bricked to use this program, it really was the only one which helped me):
http://forum.gsmhosting.com/vbb/f781/android-tablet-wifi-cpu-a10-a13-wipe-rom-easy-zakir-gsm-1656461
Here is my situation now, you can view it:
http://www.youtube.com/watch?v=cU1KYIrvZWI
Before, when it was soft bricked, at least after this android logo came the android animation that looped forever, but my computer was able to recognize and install the drivers for Android ADB device, now it can't, it won't recognize my tablet no matter what, ONLY when I press volume up and connect it to usb port, then it recognizes and installs vid_1f3a_pid_efe8 driver, which also I cannot use with LiveSuite, why? I really don't know, I've tried every possible solution found on forums (mainly here, but elsewhere also).
Whole this situation is a result of me doing the CWM upgrade/install, I'm a newbie, so I cannot tell for sure what was it, I just know it was from xda--developers forum, more accurately this thread:
http://forum.xda-developers.com/showthread.php?t=2189640
after this, poof. I think it is hard bricked, and my question is, is there a way to flash it (btw, tablet is rooted) by only having access through mentioned driver vid_1f3a_pid_efe8 and without LiveSuit, cause I would have to download and try a 100 ROM's before I pin the one that suits my tablet. It's really a tough program to deal with, but if it's the only one, I would gladly format and reinstall my Windows OS as many times I need to to get it working.
I'm planning of installing a rom on my android device and made me thinking if i install a rom and something happens like hard brick... What causes hard bricked? Is there any way to fix it by not going to a technitian?
Sent from my SCH-I800 using xda app-developers app
Personally I think if it can be fixed it's not bricked. Bricking a phone is pretty much the end of the road for it I think. Others will correct me if I am wrong so best wait for more opinions.
Yes, you are right.
But: Often a so called "bricked device" isn't realy bricked, but the user isn't able to work it again. It depends only at the users knowledge, if he called it "bricked".
I've moded my first smartphone at beginning of this month, but if have modded many other devices before (many Fritz!Boxes, some PDAs, some Mediaplayer for TV, my TV, and many others), but i've never realy bricked a device, but somtimes got bootloops.
1bigguy said:
Personally I think if it can be fixed it's not bricked. Bricking a phone is pretty much the end of the road for it I think. Others will correct me if I am wrong so best wait for more opinions.
Click to expand...
Click to collapse
How do i keep my android device from getting brick when trying to install rom?
Sent from my SCH-I800 using xda app-developers app
If you want to be sure never to brick your device then just use it as it is. I think as long as you follow all the instructions and do research on it before doing it you should be ok. That's just my opinion though.
hi
hi..i have this problem aside from my stupidity that i flashed the wrong rom and yet flashed the wrong boot.img to my xperia go..after flashing the boot.img, my phone screen went black and nothing appears. i tried restarting but nothing happens. I tried to reflash with the original kernel if that's what it is called but i cannot go into fastboot. My computer doesn't recognize my phone anymore and the color of led light notification turns violet everytime i try fasbooting..
PLEASE help..
Tnx..
I think, you have succesfull bricked your phone!
It is possible that only your screen isn't responding, but it is in uploadmode. I would try it several times.
It's in Qcom USB download mode I think. Connect it to a windows pc, go to device manager and look for some 9008 device under com pkrts
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
XDA Visitor said:
Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here:
OnePlus One > ONE Q&A, Help & Troubleshooting
All questions regarding your device belong in the forum linked above. You'll need to create an account first so you can post in the main forums.
Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?
Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse
broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.
broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...