MrClean_RUU_WIZARD_2240001a_AKU23_WWE dead k-jam - 8125, K-JAM, P4300, MDA Vario Software Upgrading

Hi , k-jam was established After
I loaded MrClean_RUU_WIZARD_2240001a_AKU23_WWE room at website.it was resetted after I loaded the applications .İt hasn’t opened .
Now it isn’t entering boot mode and isn’t opened.
Some forums I look for it So 10-15 persons have this room problem and it was connection cagresi jtag for the instrument will enter boot mode
help mee

Can you get into the boot loader by soft resetting the phone (inserting stylus into small hole on side of phone and at the same time holding down the camera button?)
If you can get into the boot loader that way - connect to your PC and rerun the rom update utility

i know these but the phone is not entering boot mode and i dont know how to enter the phone in boot mode, i must learn the jtag connecting points over the main board , anybody help me who know these points? :?:

help me all people

If it's completly bricked, you must send it to service. There's nothing else to do.

your bootloader sector erased probably,i have same problem...i try jtag method for this,but i need bootloader.bin file for k-jam.if i successfully repair my phone,i write here revive method...
ANYONE HAVE BOOTLOADER BIN FILE FOR K-JAM (QTEK 9100)??????

murat1369
hello murat1369
i have the same problem in here...
i will do anything to revive my wizard.
please give me the location of the test points and i will get the bin file in anyway.
i was working on my wizard and i gave up finding the test points. here's my thread:
http://forum.xda-developers.com/viewtopic.php?t=59992
if you want add me on msn or mail me the test points and we'll put together step by step tutorial to revive our bricks.
[email protected]

Related

Can anyone help me putting nexus 6 in edl mode? Please..

Hi everyone,
I have bricked nexus 6. It has a locked bootloader plus no bootloader, no recovery, no system no nothing.. If i boot up the phone it goes into bootloader kind of thing and pc can recognize it as a fastboot device but since it has locked and corrupt bootloader there is no command i could get it to run anything.
I know most of you think its simple bricked and cant work it again but refuse to believe that just because the simple fact that i couldnt get any answers from anyone relavent to this. I have been using android for years, basically from the beginning, i know i am not a developer but i think i know few things and i been in similar situations before but this is the first time i got stuck. I know it can be done since its a qualcomm device. There should be a way to put the device in edl mode flash with qfil or something. I know all the post about these kind issues i read them all. Whenever somebody asks about how to put it in edl mode the answer is always go check that post about how to recover from edl mode. Please understand i need to put it in edl mode first to get it out of there.
So if anyone knows a way to put this device in edl mode please help so i can try to recover from there..
I already tried modified fastboot so it can run "fastboot reboot-edl command" it doesnt work for me.
I also tried a custom cable for triggering edl mode on xiaomi devices. But it doesnt work either.
The only other way i know is the short test points on the board or on the chips legs itself.
Like i said there may be no way because the lack of information out there if it is please say so so i can rest
Thank you for your time patience.
The best I can do is point you to [FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1
If memory serves, there was a point when the adb reboot edl was patched in an upgrade. That was rather late in the device's supported lifetime. Maybe when Pie came out?

Urgent help needed cant boot in recovery or bootloader after relocking the bootloader

Today i unlocked the bootloader and installed AOSIP rom but i decided to revert to stock rom and flashed it( version c26). Then i checked i was on stock recovery. After confirming i was on stock recovery i re-locked the bootloader from fastboot command. After that the phone has gone into loop. It restarts continuously displaying the message "The current image(boot/recovery) have been destroyed an can not boot. Please flash the correct image or contact customer service to fix it". Since i can't get into fastboot mode/bootloader (pressing volume down + power key does nothing) i can't do anything. So if anyone know the solution please help me.
Note: my Computer recognizes the device if i press all three buttons simultaneously( i get device connected sound ).
Bro in the same boat, atleast you get the message saying boot image destroyed, in my case, phone keeps restarting and realme logo flashes
I read thread on gsmmafia that one can help to unbrick for money.
I can't put the external links due to xda policy, write me in direct message
Helg1002 said:
I read thread on gsmmafia that one can help to unbrick for money.
I can't put the external links due to xda policy, write me in direct message
Click to expand...
Click to collapse
Yes he solved it...
How?
Milan-XDA said:
How?
Click to expand...
Click to collapse
He recovered my phone today, CN version. He will provide the tool and image files and use TeamViewer for remote access to enter the username and password. It took approximately 15 minutes to finish. Contact him via his website -
https://www.gsmmafia.com/relame-x2-pro-rmx1931-flash-file/

Please help me device is corupted it cant be trusted and will not boot

I just instaled andriod 10 beta and this happend please help
i cant open my phone
Have you managed to do something or you are still stucked?
The message is normal after unlocking the bootloader.
Use the red magic 3 unbrick tool
I would have suggested the same, but things might have been sorted out with a restart or something..

Lumia 1320 in flash mode "NOKIA FLASH" loop restarts

I recently recovered my nokia lumia 1320 RM-994 from death, thanks to some .hex and .mbn files posted in a thread on this forum. But now I'm in another very big problem and I need help.
It turns out that a red screen appeared with white letters saying: NOKIA. The problem is that the phone restarts every two minutes or so constantly and so on. I can't find a solution to this problem, please help!
Could you send a picture of said screen?
That's the problem, the one in the video.
Update: The other problem is that when I flash the phone, it gets to 30% or 25% and finishes and doesn't go any further, I use thor2, plus I've also tried wpinternals and windows phone recovery tools.
Thanks for replying.
felipeunderx said:
That's the problem, the one in the video.
Update: The other problem is that when I flash the phone, it gets to 30% or 25% and finishes and doesn't go any further, I use thor2, plus I've also tried wpinternals and windows phone recovery tools.
Thanks for replying.
Click to expand...
Click to collapse
What software are you flashing and have you tried dirty flashing the phone?
You need to try only with wpInternals 1.2 . You can enter into emergency download mode by following key combination specified at 'restore bootloader section', try for restoring bootloder first.
You need original FFu image and emergency files.
All key combinations to be tried while you have connected your device to the pc's usb port.
Or just follow this tutorial
Tutorial | Lumia devices flashing
Tutorial | Lumia devices flashing Hello world Please, use Archive for Tutorial | Lumia devices flashing if you have an issue. No entity or person can not be responsible if a software damage occurs from the Lumia device by the utilization of...
forum.xda-developers.com
I have tried to flash the phone with wpinternals 1.2 and it has now reached 45%, I will keep trying until I reach 100% and complete the flashing
At this point the phone stopped rebooting, so I was able to try to flash it.
Thank you.
Now it's up to 52%, and it stops, but I'm already in the middle of the process, I hope to finish these days and we'll see what happens in the end.

Dead ROG 2 and what's next?

Hello
My Asus Rog Phone 2 died (WW 12/512, bootloader blocked)
I replaced the battery, the phone turned on and switched to EDL mode, only in EDL mode you could do anything with it.
I made flash ASUS_ROG2_ZS660KL_QPST_Firmware with XiaoMiFlash.
After rebooting, the phone went crazy !!! lost serial number, imei, the camera does not work, does not detect fingerprints and does not detect sim cards. The screen is cut, etc. Total massacre.
In fastboot mode it shows up as 11111111111111 and in system mode as C4ATAS000000 or something like that.
The phone boots once and not once, after executing the reboot command, etc. It works as it wants and if it does not, it does not work (you can go crazy )
I read here on the forum that the persist.img file is responsible for it
I bought another phone of the same type and I want to put my dead man on his feet
I have questions for honorable colleagues:
- how do I get the persist.img file from a new phone?
- what program to use to make a complete picture of the new phone in case of any problems?
- can the motherboard be damaged?
How do I get persist.img from a new phone and save it to my old phone after editing? The new phone is unlocked and rooted.
I am asking for help because I cannot cope with it myself
Regards
Thank you for your help
I managed on my own.
Regards

Categories

Resources