MI-Verification indelible !! - Redmi Note 9 Guides, News, & Discussion

To get rid of Mi-verification :
Deleted all partition under mtkclient
Formatted-all with SP Flash Tool several time (i repeat, several time)
NVdata (is Corrupted)
IMEI1 - IMEI2 lost
1 week of hard hard work day and night to understand how its working and how to restore
.... and now I let it revive, got into wifi for verify it could work and then ..... MI-verification back again !!!
no way to get rid of it, didn't know !
MI -- won !!!!
MI 7 - Me 0 = lost the battle

Related

S8500 stuck at Bada screen

I hope someone can help me. I tried almost everything. My wave just won't boot normally. It all started when I tried to downgrade from Bada 2.0 (S8500XPKH3) to 1.2 (S8500XXJL2) and got a security port error while flashing (used Multiloader 5.65). My wave wouldn't boot up so I got someone to repair it with JTAG. Good thing it was revived. It can now go to download mode, however, i tried flashing almost all firmware versions (Bada 1.0, 1.2, 2.0) in different regions from samfirmware but to no avail.
I browsed through the forums hoping I can get an answer but I didn't see any similar case. I'm sure I'm doing the flashing right 'coz I get "All files complete." when flashing is done. Only that, every firmware that I try, it just stays in the logo screen when it starts up.
I'm looking forward for any response.
Best regards.
I guessed you have done all well. But still try this process:
1. Download a fresh, full and original firmware for your region from samMobile.com
(The firmware version does not matter, but it has to be full and for your region).
2. Make sure your battery is fully charged
3. Remove SIM and memory card from phone.
4. Ensure that all kies drivers are successfully installed.
5. Use multiLoader v5.65
6. Cross-check that your USB plug is not damaged (if possible use another one)
7. When flashing, make sure you tick the FULL DOWNLOAD option in multiLoader.
Try the above and report back. Best of luck.
yeah you should tick boot change and full download for a complete fresh installation
Good thing it was revived
Click to expand...
Click to collapse
Depend on how it was repaired via JTAG...
Maybe NV items are overwritten... this could be bad.
It is not the best idea to use Fullflash from others...
I have RIFF Box experiences...
Best Regards
P.S.:
Try to flash some Rsrc2_S8500(Mid).rc2
Maybe Bluescreen tell you what is missing...
adfree said:
Depend on how it was repaired via JTAG...
Maybe NV items are overwritten... this could be bad.
It is not the best idea to use Fullflash from others...
I have RIFF Box experiences...
Best Regards
P.S.:
Try to flash some Rsrc2_S8500(Mid).rc2
Maybe Bluescreen tell you what is missing...
Click to expand...
Click to collapse
Thanks for the tips guys. I tried the routine checking. I've also tried different a different pc. Same thing.
I'm more inclined to this adfree. NV items might be corrupted. I just know the basics of flashing.I tried several Rsrc2_s8500 (Mid) and yes I got a blue screen with details. I don't know how to interpret it myself but I remember there was IMEI not active. Will post the details later. Hope you or someone can share your thoughts.
Best regards.
I tried S8500XPKH3 again with Rsrc2_S8500(Mid).rc2 and I got this from Multiloader 5.65:
Download Start Ch[0]
BootLoader 1703.9KB OK[0.7s]
Dbl 281.5KB OK[0.8s]
Wait reset !!
Amss 12740.3KB OK[5.0s]
Apps 26214.4KB OK[12.3s]
Rsrc1 37748.7KB OK[14.4s]
Rsrc2 2884.3KB OK[1.3s]
FFS 49217.5KB OK[111.8s]
CSC 36085.8KB OK[106.0s]
SHPAPP 203259.9KB OK[368.3s]
All files complete[638.0s]
Phone reboots and comes up with blue screen:
S/W version: S8500+XP+KH3
Modem: Q6270B-KPRBL-1.5.45t
SHP: VPP R5 2.1.1
Build Host: S1-AGENT08
Build At: 2011/08/16 20:56:16
Aoo Debug Level: 0
ASSERTION_ASSERT: 0 failed. (file SysSecureBoot.c, line 4193) BoAn4193
<Call stack information>
PC = 4000C8D3 OemDumpRegister
LR = 4000C8D7 OemDumpRegister
<Mocha Task Call stack>
_SysAssertReport
__SysSecBootReadNetLockInfoFromFile
ALL HW Information:
HW VERSION: S8500_rev07
IMEI VERSION: Not Active
RF CAL DATE: Not Active
Bad Block Information:
nNumBMPs: 0
nAge: 0
Run Time Bad Block Occurred:
Init BMPs - 2, Current BMPs = 0
Nucleus Task Information:
Running Task name - Mocha Slices = 0000001E Wait = 00000000
Signal = 00000000 Priority = 0
I've been working on this for a week now but no matter what firmware I flash, i can't get my wave to boot normally
Try qualcomm tools to activate imei
ask Adfree or use google to find the qualcomm tools program and then make your imei active using your pc.
what region was your 8500 originally?
remember that different region firmware use different boot files.
Try to use the boot files that was on your wave originally.
For some reason, it's showing "IMEI not active" when I get the blue screen after flashing with Rsrc2_S8500(Mid).rc2.
I read adfree's qualcomm tools guide and it was more on editing the product code. And, i can't access the configuration mode/hidden menu since I can't boot the phone normally.
IMEI is NV item 550 and ...
But it is secured by...
I have never tried on S8500...
Lost IMEI is enough evidence, that NV items are corrupt/missing/damaged...
I'll try to analyze your Error message...
.. will report later.
Best Regards
Edit 1...
SysSecureBoot
SysSecBootReadNetLockInfoFromFile
Click to expand...
Click to collapse
Maybe also Netlock? So maybe without IMEI Security check failes...
I think the guy who tried to resurrect my phone was using JTAG Medusa. Is there any possibility something went wrong during the process? I was just happy that the phone can go on download mode but didn't expect that whichever firmware I try, phone is just stuck on logo.
With regard to the IMEI, should i recover it, will it have a good chance to fix the problem? Can i use qualcomm tools even if the phone can only run on download mode?
if use medusa make this erase full flash after that write full from support stop writ flash in 6% in flash procedure after this flash full flash all files with boot after this pach wit z3x pachv2.Repair imei and al by ok
tested with s8500 whoo come in donload mode with 3 butons vol - lock and power
in first when try flash bada 1.0 soft after ffs write in screen see missing fota 2.0 please instal instal bada 1.2 after this
@OP:
Your SysSec data, which is closely related to NvData, has been damaged, probably by JTAG ovewrite. These data are encrypted by device-unique key.
It is possible to repair it without JTAG, through modified FOTA. But I don't think I'm the one to try this. Last time I played with that data I damaged my BL3. :\
Thanks for those who provided their insights. I kind of gave up last week and had to bring my phone to the service center. Fortunately or not, the tech had to replace the motherboard which cost around 170 USD including the "repair fee". My phone's back with a new motherboard and ready for some risky flashing again. Hehe.
Anyway, thanks again guys. Good day to y'all!
full erase flash only 6% from full after thath full flash with orginal flasher now read wit rj45 cable with z3x nvm from phone in 550 string see if imei is 359321654 need write 8a31391256 and write in phone now imei ok or select in z3x i 5500 put orginal imei and sn repair all come good and working
after all ok read full again from phone search s8500 and see you detail if need edit as your orginal string
ЄЇ~GT-S8500............їµ±№....................................TMU.....2010-06-01....АМАз±Х..................S8500BOJE7_TMOJE7...564C......9750......86210000114318......KAC007021M(S8500)...-
During my plays with RIFF JTAG and few stupid experiments with full erase I'm now facing same problem...
Strange, but this happens with my own JTAG dump...
Will see how long I need to repair this...
Best Regards
It seems no good idea to be. To erase whole NAND via JTAG...
Anyway... long time and luck... I was able to bypass Boot Cycle and then to Restore NV items via QPST...
Maybe 1 part of solution is, to use Firmware BOJE7 with Bootloader XXJEE...
Then maybe your handset start...
Now you can access menu to change to Qualcomm Diag Port for restoring NV items...
Best Regards

[Q] LG G3 stuck in fastboot mode .... command write failed

hey guys my phone stucked in fastboot mode (D855) and its a bout week that i searched every where and have done hundred of ways from hundred of forumes but still no success ... whenever i want to write an img file backed up from another phone ( such az boot laf recovery sbl1 tz ) it says :
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
i dont know what else to do .... my phone hangs on logo and after sometime it goes fastboot mode .... any idea how to solve this problem ???
flashing
did you changed port number to 41 ? sorry if you did.
Edit: Run all programs as Administrator if you are on windows !
درورد بر برادر شیرازی
هماهنگ کن یه سر بیا مغازه ببینیم چیکارش میشه کرد
ضمن اینکه هزار تا تالار رفتی ولی یه سر به
تالار اندروید ایران
هم نزدی !
MOD EDIT - Translation added (seems a bit off)
Drvrd brother Shirazi
Come shop to see Chykarsh 's now a head coordinator
While thousands were leaving the hall , but a head
Android Forums Iran
Is near !
scamex said:
did you changed port number to 41 ? sorry if you did.
Edit: Run all programs as Administrator if you are on windows !
Click to expand...
Click to collapse
yes ... my problem is with the phone .. i guess one partition must be written in first place to get the other work and writeable .. but i tried all solution and still the phone give me no answer ... all i have tried to write even one partition failed .... any other ideas ???
mastershex said:
salam bar to ey hamshahri
dadash man khodam tahe LG kara hastam ... lg khamush hanuz az zire dastam birun narafte .... inam az save vasam umade .. teh rafte ... yazd rafte .. shirazam dase kolofta gashte alan reside dastam mikham kar be taviz hard nakeshe ... yani kari nis k nakarde basham rosh pasazh soti tasvir das doktor ham boode nashode ..... dg mundam chikaresh konam ... age rahnamaee ya file dari mamnon misham
Click to expand...
Click to collapse
ok , dar har soorat
dr ham ehtemalan vaght nadashte vagarna injoor mavaredo ghablan too g2 hal kardim
agar khasti ye sar biar checkesh konim
do you have sdcard inserted in the phone ? or maybe you are mistypping partition name .... sorry for my english.
in linux that error is based on fstrim error, wich means that the memory hardware is corrupted.
If you want you can jtag that phone via Octopus box.
scamex said:
do you have sdcard inserted in the phone ? or maybe you are mistypping partition name .... sorry for my english.
in linux that error is based on fstrim error, wich means that the memory hardware is corrupted.
If you want you can jtag that phone via Octopus box.
Click to expand...
Click to collapse
in this case that solution does not work i tried but no success ... im 100% sure of the spelling of what im typing .... any other idea ???
mastershex said:
hey guys my phone stucked in fastboot mode (D855) and its a bout week that i searched every where and have done hundred of ways from hundred of forumes but still no success ... whenever i want to write an img file backed up from another phone ( such az boot laf recovery sbl1 tz ) it says :
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
i dont know what else to do .... my phone hangs on logo and after sometime it goes fastboot mode .... any idea how to solve this problem ???
Click to expand...
Click to collapse
Just stop using your phone and keep it dead for a week. It will get back to normal.
LG G3 Fastboot
i am having the exact same problem with my lg g3, and i cant find the solution anywhere on the internet. If you solved your problem please kindly share the procedure.....
Same problem here
Any news from the topicstarter? I have the same problem as well on my D855 that only fastboot is working.
I am not sure what happened but my phone just rebooted out of the blue and booted android as far as the lockscreen when it froze and rebooted again. After that only fastboot is showing up.
*Update: I brought my phone back to the store and it is fixed under warranty. I haven't received a report on the repair carried out so I only can guess what they have done and that is that they have replaced the mainboard (different IMEI now). Good news is that it works like it should. It's shipped to me running Lollipop so I will downgrade to Kitkat but that's just my personal preference.
I have the same problem with D855, is it dead mmc? any suggestions, anyone knows something?
Same problem here. Anyone can help finding a solution for this?
soltution for no download mode, stcuk in fastboot mode, stuck lg logo, qhsusb bulk mo
Hi dear frends.
Its sad to know that all you guys cant go to download mode or facing security error or stuck in lg logo or in fastboot mode
And some guys stuck qhsuab bulk 9008
So the solution is here.
If you are unable to get into download mode then you need to force your g3 into qhsusb bulk mode by shorting the test point.
I will help u all guys.....
I will help u to unbrick ur any lg model wothout download mode or stuck in 9008 or anytype of problem.
Please let me know your problem in pm.
i have got this prob with my lg g3 d855 32gb model. phone is not responding to anything . it neither goes into download mode nor the recovery mode it has got complete dead idk why. please help out if u can solve this through team viewer ?
masrooraly said:
i have got this prob with my lg g3 d855 32gb model. phone is not responding to anything . it neither goes into download mode nor the recovery mode it has got complete dead idk why. please help out if u can solve this through team viewer ?
Click to expand...
Click to collapse
Send me ur team vuewer id and pass
Trying to respawn the post, becouse i have the same proble with my phone. I want to know if someone find a solution for it. Thanks
Same problem here..
mastershex said:
hey guys my phone stucked in fastboot mode (D855) and its a bout week that i searched every where and have done hundred of ways from hundred of forumes but still no success ... whenever i want to write an img file backed up from another phone ( such az boot laf recovery sbl1 tz ) it says :
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
i dont know what else to do .... my phone hangs on logo and after sometime it goes fastboot mode .... any idea how to solve this problem ???
Click to expand...
Click to collapse
Same Problem here.. Any luck ?

huawei g8 rio-l01 stuck in run mode:factory

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....

ZE551ML, rom 4.21.40.223, no root, issue to connect to G account after a reset

Hi
I upgraded my asus to the 4.21.40.223 with no issues.
like I have an issue an issue with my GPS FIX, I did a reset of my phone, via the recovery mode :
- wipe data /factory reset
and
- Wipe cache partition
and when I turn on it, I put my gmail account, but the phone doesn't reconize me. (I put the same G account than before the reset : the phone request a previous account already used with the phone)
When I check my G account, the name of the phone is changed to ASUS Z00AD, previouly it was Asus ZenFone 2.
may be it s due to this change I cannot use my phone... :crying:
any ideas?
should I flash all the phone (like the brick phone procedure?)
pichteam95 said:
Hi
I upgraded my asus to the 4.21.40.223 with no issues.
like I have an issue an issue with my GPS FIX, I did a reset of my phone, via the recovery mode :
- wipe data /factory reset
and
- Wipe cache partition
and when I turn on it, I put my gmail account, but the phone doesn't reconize me. (I put the same G account than before the reset : the phone request a previous account already used with the phone)
When I check my G account, the name of the phone is changed to ASUS Z00AD, previouly it was Asus ZenFone 2.
may be it s due to this change I cannot use my phone... :crying:
any ideas?
should I flash all the phone (like the brick phone procedure?)
Click to expand...
Click to collapse
Re ... last comment, NO-Keep away from xFSTK
Make sure you have stock recovery first ?
Try a factory reset within settings .
If fail there , downgrade to LP using ext SD card ..in my signature below, which factory resets to .196 LP,set it up .
Then put ... M .223 on ext SD like in video of downgrade... and reboot .
Bingo !
Bingo !
it s worked !
I flahed to Lolipop, and reflash to M, with the SD card solution.
Perfect,
thanks.
I ve still my GPS issue : no satelites.. I have this issue since I unpluged and replug the battery connector (my phone was not responding).
I will check if I closed my phone correctly.
pichteam95 said:
Bingo !
it s worked !
I flahed to Lolipop, and reflash to M, with the SD card solution.
Perfect,
thanks.
I ve still my GPS issue : no satelites.. I have this issue since I unpluged and replug the battery connector (my phone was not responding).
I will check if I closed my phone correctly.
Click to expand...
Click to collapse
Marvelous stuff happy days :highfive:

Another hard brick ?

So i got one of these vs985s. and nothing. screen lit up but nothing else.
so i had a unknown or damaged usb device .long story short
got it in 9008 i follow all the guides emmc and ap test past.
but when i to the sd ram test i get a error of
========DDR TEST START
Test level = 0(check data/address line)
sbl1 partition write FAIL.. senctor 0x28000
WRITE FAIL During ddr test..
Aborted..........
Also everytime i click a restore boot image in any version of board diag tool whatever partition im trying to restore write fails....
Now i remeber back on my g2 i got the 9006 mode i was able to zero all the partitions in linux when it mounted 30 somthin drives.
Is there any info any one could give me as i have followed all the guides.. But might be missing something somewhere.
any help is greatly appreiciated
I have the exact same problem here with my father in law's D852. The phone was never rooted. I was trying to unbrick it but it didn't reboot after flashing sbl1. So I decided to try a stock rom form another source and that's when this happened. Trying to go back to the first rom didn't work, even after erasing the entire emmc. My guess is somehow, we activated permanent paper weight mode. I hope someone more qualified than us can help us, or at least confirm our phones are good for recycling...

Categories

Resources