Heya guys...thanks to everything so far you have been a great source of information on how to root and flash and modify all my former android phones...so this time i have to ask you this thing...i think i have load a wrong rom on my star n9330 mtk6577 and now it is probably bricked...it will not boot up not even in recovery not even the china stock recovery where you have to press the volume down and boot...pc is recognising it as uknown usb device but when i plug the usb the led is firing up like when it is charghing...please help me i am stuck right now and i rly want to revive this phone cause i have it only for a day and a half....thanks in advance!!!!
P.s please do not answer as this have been answered in an other post...i have bidden my time and searched but found nothing specific for this model!!
Maybe you can start trying by looking here...
http://forum.xda-developers.com/showthread.php?t=1943442
Searched it...searched around meta mode but it did not work either...tried to make a usb jig aswell and think i got it right but nothing happeneded aswell.....:/
Service centre. You're hard bricked.
You reckon they will be able to fix it???
Don't think so but you can always have a try. If you want enjoy custom ROMs and kerenls, you should have gotten supported devices.
Hi all, someone can help me to find the TP on Xtouch X401?
I tried to upgrade this phone following the product guide, with their tool and their firmware, it seem all ok when i flash but when i unplugged usb the phone something has wrong and now the phone will not turn on, does not go into recovery mode and isn't recognized on pc....
I think is bricked, maybe i can try with TP if someone help me to find the point.
Tnx all
Up
anyone help me?
Hi guys, i need your help. So, i installed Chainfire 3d on my Zte kis pro (Orange zali) (bought from Orange Romania) , running Android 4.1.1 JB, without doing a backup. Of course i got stuck into a boot-loop, and I am really desperate. I haven't found any solution compatible with my phone :crying: as i think USB debugging is off. When i plug my device into my pc with a usb cable from recovery mode it says "USB Device Not Recognized". The ROM from the official ZTE website is useless as the zip file is corrupt. I treid using a zip repair program to no avail. I don't have any custom recovery or custom ROM, everything is stock and i have root. So any help would be kindly appreciated (but please explain any method with steps because i am no tech wiz ). PLEASE HELP I AM REALLY DESPERATE!!!!!!!! :crying:
Hi Guys
i have bricked my Vodafone VF685/ Alcatel Pop D1/ Huawei U1860 or whatever make this is (quite confusing) with SP Flash tool MT6572.
I tried to flash CWM recovery (successfully rooted with KingRoot) with the Scatter file compatible with the SP Tool version. All went well, bur my phone didnt want to go past the start up logo. So i tried flashing it again, and now it doesnt want to switch on nor charge, cant boot into recovery. Just a dead phone with a black screen. My pc doesnt pick up my phone via usb and i get error code 4004, i did some searching on how to fix the error code but im still stuck in a rut...
Any advice on how to fix this and please any advice on how to tell which recovery and scatter and firmware is for this phone?
Model: V685-1
SVN: 120HJG1
MANF: TCT MOBILE LTD
CU REF: V685-2AVDZA1
Thank you in advance, i really appreciate your help and advice.
Johan
Well, this is quite dissappointing... Not a yes or a no... Nothing....
Greetings, everyone. I'm unable to boot my Realme U1, after a recent unwise decision of relocking its bootloader after flashing a custom boot image i found over this thread: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683
I hadn't encountered locked bootloaders before, so I realised it isn't supposed to work with android pie, which resulted in a system crash.
Now i'm unable to get the device recognized by my pc at all,and it keeps saying that the current boot image is destroyed and cannot boot.
Also, only recovery mode is working.
Any suggestions on what i must do to fix this?
any kinda help would be greatly appreciated
and thanks
I also have exact problem no solution till now!!!
ps1084 said:
Greetings, everyone. I'm unable to boot my Realme U1, after a recent unwise decision of relocking its bootloader after flashing a custom boot image i found over this thread: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683
I hadn't encountered locked bootloaders before, so I realised it isn't supposed to work with android pie, which resulted in a system crash.
Now i'm unable to get the device recognized by my pc at all,and it keeps saying that the current boot image is destroyed and cannot boot.
Also, only recovery mode is working.
Any suggestions on what i must do to fix this?
any kinda help would be greatly appreciated
and thanks
Click to expand...
Click to collapse
This u read?
https://www.getdroidtips.com/stock-rom-realme-u1-firmware/
Please reply
I accidentally hard bricked my realme u1 while I am rooting it.
Any solution please reply.
ps1084 said:
Greetings, everyone. I'm unable to boot my Realme U1, after a recent unwise decision of relocking its bootloader after flashing a custom boot image i found over this thread: https://forum.xda-developers.com/android/help/method-rooting-realme-u1-t3916683
I hadn't encountered locked bootloaders before, so I realised it isn't supposed to work with android pie, which resulted in a system crash.
Now i'm unable to get the device recognized by my pc at all,and it keeps saying that the current boot image is destroyed and cannot boot.
Also, only recovery mode is working.
Any suggestions on what i must do to fix this?
any kinda help would be greatly appreciated
and thanks
Click to expand...
Click to collapse
Hey man!
It's not a hardbrick, its soft brick.
If you can access recovery then flash a custom recovery, then flash the original boot.img and recovery.img, then reboot to COS recovery flash your ozip and reboot this should fix it!
Hope this helps!
Hi there I am new to this forum and I don't know that I am posting at right place . I have my Ralme U1 phone hard bricked and unable to turn on not Even it is detecting the charger. but when I connect it with my PC and hold power button for 7 to 9 second the device manager shows Realme Preloader as the device name and it stays there only for 2 seconds and then it again gone. Is anyone have the solution on how to unbrick it Please Help!!!!
DHANOLA said:
Hi there I am new to this forum and I don't know that I am posting at right place . I have my Ralme U1 phone hard bricked and unable to turn on not Even it is detecting the charger. but when I connect it with my PC and hold power button for 7 to 9 second the device manager shows Realme Preloader as the device name and it stays there only for 2 seconds and then it again gone. Is anyone have the solution on how to unbrick it Please Help!!!!
Click to expand...
Click to collapse
Hello Mate!
I hard Bricked Realme U1 over 2 times and recovered it!
MTK chipset devices are easy to unbrick.
I would love to help you, anyway to contact??
[email protected]#$ said:
Hello Mate!
I hard Bricked Realme U1 over 2 times and recovered it!
MTK chipset devices are easy to unbrick.
I would love to help you, anyway to contact??
Click to expand...
Click to collapse
You can contact me by mail: [email protected]
DHANOLA said:
You can contact me by mail: [email protected]
Click to expand...
Click to collapse
Hello Everyone!! It has been two years for me to be in this situation. I get mail from many of those who have a similar problem. So I am here, providing the solution to how I solved this solution.
For the solution, you may, first of all, join the given below Telegram. Link from anybody's phone and ask there for your problem or describe your problem in the group someone will help you out. The group icon has been attached.
Just connect to them on telegram and tell your issue they will surely help..
Telegram link
https://t.me/RealmeU1
Or search for Realme U1 group in telegram
Group icon attached
If then also you need help, please contact me by my mail. As mentioned in the above chat reply,