Related
Hi,
I made a mistake with flashing QTEK S200 with wrong file.
Bootloader was modified. Device can not start at all.
It can not even go to bootloader screen (red-green-blue).
As consequence, no USB connection can be established.
What is the solution? I guess utilities can not be used, because they assume connection to USB, but there is no connection.
Not big deal, because it was not working well anyways, but would be interesting to know a solution in this case. Many ppl. would be happy to know how to manage this situation, I guess.
later.
Not very good news, service center said they don't know how to fix it, but kept the device to make few things with it.
Clearly, bootloader was overwritten.
Will see. Somehow they manage to identify type of rom is installed from i-mate.
So, think before you make any flashing
re: another service said they will do whatever needed, up to replacing chip with flash. I am not ready to go that far yet.
feel like i am missing something
It appears to be a real problem with flash.
No connection to computer with USB.
With power supply connected blue-green-?? screen, but I cannot connect to PC of course.
With USB cable connected blue-green-?? screen does not come up.
I figured out that pins 4 and 5 are shorten when power supply is connected. I did this with USB connection to PC, but still not connected.
For sure, USB is not functioning on device.
Will get new device, but very interested on how to repair this one. I disassembled it completely. There is no way to replace the flash chip at home, you need specific equipment and chip, of course.
What I need is surcuit diagram for S200 or similar, particularly part of diagram related to flash, radio module is not needed. Is there any possibility to get it? If I have it, I think can reprogram chip.
Thanks.
Hm. It looks like extreemly difficult to get pins layout on motherboard.
JTAG is the only solution left to access chips direct. But we need to know where JTAG pins on motherboard.
Recovered S200.
Finally very good news!
Prophet S200 was succesfully recovered with help of Arc.
He managed to discover JTAG pins, afterwards re-flashed SPL and ROM.
REALLY GOOD JOB!
Want to say special THANKS to Arc!!!
Device go live again.
Until next experiment....
But procedure to recover is in place.
Regards,
fdp24
i have a dead one too
Hi there,
I have a dead one too can you tell me how to fix it please?
dead, as in my ppc k-jam is dead
basically it hangup and i soft restarted, tried hard reset. it didnt help either. i tried restoring to factory default same thing it hangup. now it doesnt shows any signs of life . i lost my life, my buddy.
My Orange SPV M2000 will not start anymore after update. I only see Serial (on top)............ V2.07 (underneath)
I tried to update my ORANGE SPV M2000 to Tmobile's newest rom by extracting the exe. file and using maUpdateut. It started well and all of a sudden gave error "country code................"
You will not be able to fix it yourself.
Equipment and phone required physically in order to connect jtag interface and re-flash DOC.
Sorry, but this is the only solution if your bootloader is damaged.
Of course, you can try to ship it to service center. If you are lucky they will change your device. This might more simple.
Good luck.
fdp24 said:
You will not be able to fix it yourself.
Equipment and phone required physically in order to connect jtag interface and re-flash DOC.
Sorry, but this is the only solution if your bootloader is damaged.
Of course, you can try to ship it to service center. If you are lucky they will change your device. This might more simple.
Good luck.
Click to expand...
Click to collapse
I know how to open device and solder some wires to testpoints. Do you have any information where the pins are located and what software and what JTAG adapter you used? I really need to get my phone working again. It was quite expensive to purchase and to ship it to my country. Please don't destroy my hope.
hello friends,
my cousin recently buy O2 XDa ( wallaby ) for cheap one, i check on device it seems cann't boot to windows but if i hard reset and came up red, green, blue and if i press ok it came up with test all thing i confuse all the test is OK, can you all tell me how to repair the phone and waht is the problem?
thank you
dead device hope on the horizon
note my device and troubles is on the xda2
hi - i have had exactly the same issue - i have managed to reload the rom i was trying to swop and here is what i did .... it took ages and lots of patience and it is not an exact work of science but if you try my method 2 or three times it actually comes back to life ... honest !!
down load an xda2i ( yes xda2i )rom extract it using winrar or zip on your pc place dead xda2 into cradle regardless of whats on screen run himupgradenoid - the rom will run and start to load onto your device it will fail once it has failed remove xda but do nt reset - take copy of original rom which was on the device prior to your failed upgrade and extract as above. replace xda into cradle might be detected or not dont worry - run the himupgradeut from your previous working rom and wait it takes ages to connect but eventually heypresto ... you will have a working device. i know cos i done it !!! - i have not resolved all my problems yet - i still want to load latest 02 rom but even after entering correct device data into nbfs using batch file method the device crashes saying incorrect counry id. - i accidently created my problems by accidently running the wrong upgrade rom and i guess it changed somthing on my device " country code" however when i use method above to get original rom inplace and working when i extract device data into windows folder on device i still see the wwe ( world wide english) so i am still in a pickle - can anyone help me .
hello
i'm working on the project of flashing the bootloader into a totally erased and dead phone. can you send us the test points from the prophet please? and if you know their location on a WIZARD. thank you..
Somebody here Please tell what soft to use with JTAG to recover da bootloader!!!!!!!!!!!!!
get the JTAG pins for me, I will send you soft.
Wizard and Charmer pins are both needed.
hi, i've succesfully wrecked my Blueangel PH20B by flashing a modded wm6-universal-rom... i've got all the hw & sw to resurrect the phone but the jtag pins on the BA-PCB...
can someone give me a hint where i may find them? (i'm not wanting to bake the pcb as i know i'll wreck it comletley)
thanks in advance,
mario
Same problem here
Hi,
I believe I'm having the same problem
Please help me
Thax a million
so can you help me i need to write the wizard(g4) bootloader or thell me how can i do this
T-Mobile USA SDA II
Me also, i'm i need of re-writing boot-loader of T-Mobile USA SDA II
well, ok I understand that you can get the Jflash_mm working with PXA systems, you can write the definition for yourself, as for the CPU.
but I have serious doubts that inspire me to suggest you will have tiny chance to actually program a DiskOnChip Millennium series (or familiar) chip used in many platforms (actually I believe most HTC devices).
after all this means that if you are not working for (or in affiliation or partnership with) SanDisk, you are not in position to program bootloader to (not limited to) UNIVERSAL, WIZARD, PROPHET, and CHARMER (and if I remember well, BLUEANGEL and HIMALAYA) devices over JTAG.
any news............
Hi everyone ,
(first sorry for my bad english)
i got a g8 rio-l01 with a few problem ( no imei , no sn , no wifi and bt mac adresse) all this problem was solved using the hcu tool
but the biggest problem is the phone boot in a factory mode ,i can see this in the projectmenu>veneer informaton>other info>run mode: factory
so in this mode :
1-i have no shortcut panel and notification panel when i slide from up to down nothing come
2-no signial or network conection
3-in the first home page in the phone i have MMIs app/software upgrade/MMI/projectmenu/MMIa,
in the second one i have runningtest3
in the last one basic android app
4-i can't use keyboard
so i have trayed i think all huawei g8 firmware and nothing change
trayed with DC phoenix methode (the two methode) and same problem
trayed with the original soft (RIO-L01_M105_Board Software_general_Android 5.1_EMUI 3.1_05021TJY) and no change
trayed with l02 ,l03 ,tl00 ,slim6 and cm13 and the problem persist
bootloader and frp are unlocked ,sim too with hcu and phone rooted
if i remove appfac from user data and reboot the keyboard Appears and other app Appears but the phone stay in factory mode with no upper pannel and no network signial
i can use wifi and bt
in fastboot getvar pruduct give msm8916 (it's normal??? the phone is an msm8936)
i think there is a currupted or a missing file or partition
i have all factory flash file
bootloaderimage: huawei_msimage.mbn, MPRG8936.mbn (i don't know how tu use this two files)
fastbootimage: boot.img, ,cache.img ,cust.img ,emmc_appsboot.mbn ,erecovery.img ,frp.img ,fs_image.tar.gz.mbn.img ,gpt_both0.bin ,hyp.mbn ,log.img ,misc.mbn ,modem_st1.mbn ,modem_st2.mbn ,NON-HLOS.bin ,oeminfo.mbn , persist.img ,recovery.img ,rpm.mbn ,sbl1.mbn ,system.img ,tz.mbn,userdata.img ( and all crc file )
any idea are welcome
thank you
Hi again
So after many test ( and break and unbreak the soft many times) by editing prop and conf files, i noticed that the ro.runmode is the command controling the boot mode.
But i don't know were is this command and if it's possibol:
- To force ro.runmode=normal?
- Or any solution to by pass runningtest3 app or to fake the result?
Thank you (any help are welcome i don't worry about bteaking the phone)
Finally the phone is fully dead ?
After many flash factory, stock and custom i decided to find the way to enter to hs-usb 9008 mode and i find,by flashing the phone with cherry honor 4 rom. And the phone rebooted in 9008 mode, than flashed the ddr and the msm8936 file with zte tool. The msm will not finish and the phone reboot in fastboot (with red, green,blue screen) than reflashed factory rom with dc unlocker the phone rebooted normal but with the same problem that i have in the first.
Second try, flashed with cherry, entred 9008 mode,reflashed with zte tool (by error used a bad msm8936 file from lenovo)
And the phone stop working not detected and black screen
Third try, desassemled the phone, removed battery find test point after many risky test,the phone boot again in 9008 mode.
Reflashed with zte tool, enter red green blue fastboot, and decided to reflash all the factory with fastboot flashall méthode to unbrick an msm8916. Fastboot finish with many failed.
The phone rebooted but black screen and blinking led with continus (red,blue, green), not detected in pc, trayed with test point and nothing
I think it's fully dead now
Sorry for all this long text but just to share expérience
Thank you
And no it's not dead ðŸ˜, find the way to boot it again in 9008 mode with shorting two test point
Here we go for other test
السلام عليكم
hello friend
have you tried to flash the OEMINFO partition (if not be careful because the unlocked code of the bootloader will be changed and you need to read the new one with hcu client)
if you dont know how to do, tell me
sorry for bad english I'm not english man
xzanium said:
السلام عليكم
hello friend
have you tried to flash the OEMINFO partition (if not be careful because the unlocked code of the bootloader will be changed and you need to read the new one with hcu client)
if you dont know how to do, tell me
sorry for bad english I'm not english man
Click to expand...
Click to collapse
allrady solved my problem with an oeminfo but it work only single sim i need an other oeminfo with dual sim
thank you
How To Get Oeminfo
makabress said:
allrady solved my problem with an oeminfo but it work only single sim i need an other oeminfo with dual sim
thank you
Click to expand...
Click to collapse
makabress Please clear here how to get oem info and write it.. i m alredy face same problem..
hellowbd said:
makabress Please clear here how to get oem info and write it.. i m alredy face same problem..
Click to expand...
Click to collapse
Hi , i found the oeminfo searching in google. I will try to find it again
hello
i a have the same prolem but i cant find "the service rom" too, my phone is stuck in mode 9008 i tried to do the rom by myself but witouth any succes.... i read in a post that i cant try to put the "Huawei_Honor_Cherry_L04_V100R001C900B150_India_4.4.4_EMUI_3.0_05021SLQ" who has the same structure but cannot flash phone said "bootloaderimage" fail
please anyone can help me? i am 2 months witout phone... sorry about my bad english im a spanish guy
rio-l01 test point
hi, please i can't found rio-l01 test point can you help me
rmili25 said:
hi, please i can't found rio-l01 test point can you help me
Click to expand...
Click to collapse
test point are in the left/right side of the display connector, you can use a small wire to short it
JoseBankai said:
test point are in the left/right side of the display connector, you can use a small wire to short it
Click to expand...
Click to collapse
thank you brother
please i have the same problem ( rio-l01 no service no call ) can you help me please by oeminfo file or other things
excuse me i'am bad in english
still having the same problem, no solution, try to resoldering emmc, processor, voltage are ok, everything works in other board, so the problem is still the **** mode 9800 and the vanished "service rom" (not trully vanished but every service that i call to fix this ask me for a lot of money just to fix 1 phone... not worth it..) hope somebody can explain this at least, and why is happening, maybe one day can recovery my data on thtat phone....
Greetings Everyone,
I need help regarding my hardbricked LG F460L. As of right now it is in DEADBOOT (The screen won't turn on even if I plug it in) So, I can't boot into RECOVERY, DOWNLOAD MODE, or FASTBOOT. However, when I connect my phone to my Win 7 64-bit PC, it is detected as QHSUSB_BULK.
This nightmare happened because I flashed a D855 modem.iso to my F460L, I accidentally flashed the incorrect modem.iso in TWRP and i've been screwed since then.
After reading and scouring through every LG F460L/K/S Cat 6 Unbricking threads in XDA, I have found three methods:
https://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
- I have installed the QUALCOMM driver, my phone is now detected as Qualcomm QDLoader 9008. This is in accordance to the BoardDiag method. Using willcracker's boarddiag program, I connected my phone to my pc and clicked start HOWEVER I always get the device not found in dload trying flash programmer error after 2 minutes. The AP Chipset I chose is B2 since there is no MSM8084 or APQ8084 chipset for the Cat 6 in the program
If anyone has a working BoardDiag program that supports the Cat 6, please do post a link in the comments or PM me if you so prefer.
= ~FAILED~
https://forum.xda-developers.com/lg-g3/general/unbrick-debrick-f460-boot-security-t3352382
- I tried to boot through an external Micro SD card by flashing a "debrick.img" to the SD card. There were 5 debrick images listed in the guide, however, all of its download links are down (220, 200, 180, 160, and 140 are all down)
Thanks to the efforts of other users, I was able to download a debrick image file for the F460. Upon mounting the flashed Micro SD card, my screen turns on and I can enter download mode BUT it was of no use since I was stuck in an eternal "Secure Booting Error!" bootloop.
If anyone has a working link to the 5 debrick images for the F460, please share.
= ~FAILED~
https://forum.xda-developers.com/verizon-lg-g3/general/fix-unbrick-hard-bricked-lg-g3-vs985-t3467067
-Finally, there is the Wire Trick (Test Point/Shorting Points) method, this method carries a risk of DAMAGING HARDWARE since you can fry your mobo if you're careless.
Since my phone was already detected as Quallcomm QDLoader 9008, I skipped this method, but beacuse the first method is not working for me, I wanted to get back to this.
I was actually desperate enough to attempt this, however, upon reading the warnings and disclaimers, I had to think twice about it. The trick was to short a point near/beside the processor and short it to ground. It is relatively simple and easy (For the International versions) but since I have an F460 Cat 6, my board is SIGNIFICANTLY different from the mobos of the International/European versions.. Images and diagrams online, looks different to an F460L mobo. Can't risk frying my phone!
Since there is no information/images/guides regarding how to short an F460 Cat 6, I put out this method for later study.
If anyone can point me where to short these pins or help me find the correct pins, I would appreciate it.
= ~FAILED~
http://cafe.naver.com/develoid/562849
:crying: I am desperate because support for the Cat 6 seems to be very poor, and the Develoid Cat 6 forum in Cafe.Naver is apparently region-locked, only allowing Koreans. I can't seem to register an account since it requires an I-PIN or a Korean phone number.
Please Help Me!!!!!!!!!!!!!!!!!!!!!!
If anyone can provide me with other methods (except paying for overpriced JTAG repairs ) I will really appreciate it!
and Thanks everyone!
If you have a working link to the 5 debrick images for the F460, please share.
Thanks you so much
Boot verification fail!cause : mismatch_sig_len please help me asap pleaseee
So I already know there is another way to restore a device a hard-bricked device, but I have tried that method many times with no success. I'm able to connect my device in 9008 mode to my computer, but I do not have a singleimage.bin to fix the device. Does anybody have this file, as I cannot otherwise fix my device.
Thanks,
hillj284
Joseph Hill said:
So I already know there is another way to restore a device a hard-bricked device, but I have tried that method many times with no success. I'm able to connect my device in 9008 mode to my computer, but I do not have a singleimage.bin to fix the device. Does anybody have this file, as I cannot otherwise fix my device.
Thanks,
hillj284
Click to expand...
Click to collapse
The problem is coming up with programmer.mbn which is part of singleimage.bin. This file programmer.mbn is like a driver file which drives the entire flashing process and is very much specific to device (g5s). We cannot use a programmer.mbn of cedric with montana. Also programmer.mbn has a code logic which verifies the version of bootloader present in the device using 9008 port. If the version mismatches then it would fail. Likewise there are a lot of fail case scenarios. I am not sure whether it is worth of trying.
Thanks
KS
In addition to kalyansundhar's post, the programmer and the singleimage.bin need to be cryptographically signed by the issuing OEM to work. In other words, you'd need Motorola to make the blankflash singleimage.bin, and they won't leak engineering tools. As such, you likely cannot use programmers and singleimage.bin you may find on the internet, unless they are for the Snapdragon 430, are new (so they can repair newer bootloaders), and are signed by Motorola. You'd have to wait for a sympathetic engineer to risk leaking a blankflash (and possibly risk their job) or consider paying for a new device if the cloned image doesn't work.
kalyansundhar said:
The problem is coming up with programmer.mbn which is part of singleimage.bin. This file programmer.mbn is like a driver file which drives the entire flashing process and is very much specific to device (g5s). We cannot use a programmer.mbn of cedric with montana. Also programmer.mbn has a code logic which verifies the version of bootloader present in the device using 9008 port. If the version mismatches then it would fail. Likewise there are a lot of fail case scenarios. I am not sure whether it is worth of trying.
Thanks
KS
Click to expand...
Click to collapse
So is there anything I can do now apart from send my device to a service centre?
Joseph Hill said:
So is there anything I can do now apart from send my device to a service centre?
Click to expand...
Click to collapse
I ended up with same situation as yours. Except touch panel everything is fine and gave it for servicing. All they say is replace motherboard which would cost as much as buying a new phone. It is not worthy to spend that much.
Thanks
KS
Sent from my Moto G5s using Tapatalk
Guys, i need some help. My cellphone was with a lot of stuck on apps, and i tried factory restoring a lot of times to solve, and i tried upgrading to Android 9 too. After all, i resolved to root the device in order to fix the errors. But I made some mistake in the rooting and it doesn't work. Now I can't put the device to work, i tried all the tutorials here and a lot of roms, but i always get a diferente problem.
I always get "(bootloader) Image signed with key bad key" message when I make the tutorials, I dont know if this is the problem. In some tutorials I get a bootloader looping, in others the device try to initiate and the screen stays flashing, but in any of them the system starts.
If you can help me, i'll thank a lot.
In my bootloader show the following informations:
BL: MBM-2.1-aljeter-retail-02dae09-190122
Baseband: M8937-30.05.80R JETER-LATAMDSDS-CUST
Product/Variant: jeter XT1922-5 32GB P4
Console (NULL): null
Tool Modes Config: DISABLED
flashing_unlocked