YU IMEI Issue - YU Yureka Original Android Development

Hello All,
Im writing my experience with Yu Yureka.
The device was working fine, until one day, when i thought of updating the ROM for a stable battery and optimum processor usage.
I was successful in installing the RR 5.8.3 (latest) ROM.
However, I noticed later that the IMEI is wiped, and replaced by 0123456789012345.
Too bad, that i dint search beforehand on this issue.
Now that it has happened, i went searching for an effective solution, but all in vain.
The device is now idle, waiting for a IMEI fix, which as far as im aware of, is nowhere near.
Few people suggested someways, which dint quite help me out. (Thanks to all of them, though, I've also hit the THANKS button)
The point is, please, if you know how to fix it, please direct me the ways.
QPST way dint work for me: (https://forum.xda-developers.com/yureka/help/recovering-lost-imei-yu-yureka-yunique-t3331485)
Also this dint work : https://forum.xda-developers.com/yureka/help/yu-yureka-wiped-imei-t3449513
SAILAKKI's youtube video coudnt help me.
None of those IMEI fixing tools helped.
This is the last resort that i could think of. (I had requested for help, but sadly, none replied to my older thread)
ROM's Ive tried so far:
RR 5.8.3,Haxagon ROM, SlimRom,Lineage OS,Cdroid, CM-13 Tomato.
What i did?
Used TWRP to install RR 5.8.3 + Gapps(7.1 X64 Pico) + Supersu 2.79
And, then, Used Terminal Emulator - Gave SU access - Ran adb shell.
Result:
ADB NOT FOUND
And now, im here, waiting for that person who could assist me/help me with this.
I understand that your Inboxes are already full with many requests like mine.
All i could ask for is, is it fixable? If yes, then please suggest the ways.
Thanks.
(note: if any info is needed, ill share the same here, and im good to test new ways as well)

Did you try qxdm professional?

sohail0098 said:
Did you try qxdm professional?
Click to expand...
Click to collapse
hello
i tried it, but it dint work.
ill retry if you insist
howwver, can you tell me which version to use?
links woudl be helpful
thanks

pdpyen said:
hello
i tried it, but it dint work.
ill retry if you insist
howwver, can you tell me which version to use?
links woudl be helpful
thanks
Click to expand...
Click to collapse
Sailakki's method helped me get back mine. Are you sure u followed every step ?

KumarGautam said:
Sailakki's method helped me get back mine. Are you sure u followed every step ?
Click to expand...
Click to collapse
hello
ive tried it. however, the adb shll on the device is not found

KumarGautam said:
Sailakki's method helped me get back mine. Are you sure u followed every step ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pl;ease see

pdpyen said:
pl;ease see
Click to expand...
Click to collapse
Type su
Give root permission
Type command in given method
And follow steps
QUOTE=botnet.py;65720327]Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app (Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
Code:
setprop sys.usb.config diag,adb
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Code:
IMEI example "123456-78-9012340"
sort it out 1 ,23 ,45 ,67 ,89 01 ,23 ,40
{ 0x08, 0x1A, 0x32, 0x54, 0x76, 0x98, 0x10, 0x32, 0x04 }
As you can see i have sorted it out & swaped the values
0x08 is the length keep it as it
0x1A = first digit of IMEI with A
0x32 = swaped 23 to 32
.
.
after you are done putting value of your IMEI in sim 1 press the write button & wait few sec
now repeatg the step for sim2
Reboot Your Phone & voila
Hit Thanks if you think i have helped you [/QUOTE]
Copied from OP

nischait said:
Type su
Give root permission
Type command in given method
And follow steps
QUOTE=botnet.py;65720327]Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app (Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
Code:
setprop sys.usb.config diag,adb
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Code:
IMEI example "123456-78-9012340"
sort it out 1 ,23 ,45 ,67 ,89 01 ,23 ,40
{ 0x08, 0x1A, 0x32, 0x54, 0x76, 0x98, 0x10, 0x32, 0x04 }
As you can see i have sorted it out & swaped the values
0x08 is the length keep it as it
0x1A = first digit of IMEI with A
0x32 = swaped 23 to 32
.
.
after you are done putting value of your IMEI in sim 1 press the write button & wait few sec
now repeatg the step for sim2
Reboot Your Phone & voila
Hit Thanks if you think i have helped you
Click to expand...
Click to collapse
Copied from OP[/QUOTE]
thanks for pointing
but whre to get xqdm? and which version

pdpyen said:
Type su
Give root permission
Type command in given method
And follow steps
QUOTE=botnet.py;65720327]Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app(Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Copied from OP
Click to expand...
Click to collapse
thanks for pointing
but whre to get xqdm? and which version[/QUOTE]
Google it
https://www.google.co.in/search?&q=qxdm+professional+download
Try anyone

Have you been able to restore your imei??? If not, PM me...
---------- Post added at 12:49 AM ---------- Previous post was at 12:43 AM ----------
pdpyen said:
View attachment 4149101
pl;ease see
Click to expand...
Click to collapse
adb is in pc and not in device. While using terminal app in phone you have just type the following command:-
su
setprop sys.usb.config diag,adb

yureka imei issue resolved
I have also faced the same issue. After flashing imei numbers became 0123456789 or some thing like that. Both sims. So can't connect to the network. I tried several methods. Nothing worked out. Given it to mictomax service centre and after keeping the mobile for a week they washed their hands stating I have to change the board costing 2500..
So I got back the mobile.
Finally I learnt the following facts. To restore the imei you have to flash the stock ROM. That will have the finger print I'd. Only after doing that you can restore the imei. To check the finger print I'd you can download the app called droid hardware info. Using this you can find out build finger print release keys. Then you have to flash that ROM. Then you have to root your phone using any method. Then you have to download the software called miracle mobile 2.27A. You can find it after googling then download terminal emulator on your mobile. Give root access. Enable diagnostic mode by typing the command you can get it googling. Open the miracle box. Before that you have to disable the antivirus on your system. In the tool box mostly start button is hiding. Close the application and change the system year to 2014. Now miracle box strategy button will work. Aftertybing in the command for terminal emulator you just connect the mobile through USB. Drivers will be installed automatically to adb mod. You can confirm it in my computer hardware devises. After that in miracle box go to Qualcomm. Lg imei repair. Type your both imei s in the respective space. Click start. That's all. You imei number will be restored. Network will be connected. Wish you will get your yureka back. Regarding miracle tool box you have to download the modified version using that only you can do. Otherwise it will require box also. Search for without box and how to open without box using miracle box loader etc.,. I lost my imei on 30.12.2016. After trying all methods and service centre visits several times and got it back on 26.01.2017. After 26 days...hope you will get back your yureka imei number

Related

[Tool] VS920 Repair Utility

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This utility will help you recover your IMEI / MEID from a bad flash.
WARNING:
This software only allows you to write to the device if the IMEI / MEID is zero'd out or does not contain anything.
DO NOT WRITE SOMETHING YOU DON'T WANT. IF YOU WRITE THE WRONG IMEI / MEID YOU ARE SCREWED.
I do not condone changing / modifying / tampering with the serial IT IS ILLEGAL. It is however legal to recover the original one, that is what this software will allow you to do.
I will not answer PM's because you typed the wrong serial number or because you tried something you shouldn't have. This is a fair warning. Make sure you type your original serial number in correctly the first time. Both boxes must match.
[How To Use]
1.) Plug device into computer.
2.) Select Internet Connection Mode, select Modem.
3.) Open device manager to see what COM your device is on.
4.) Open software and select the COM, there is two the device will connect on, you only need to write the information to one of them.
5.) Click on Connect.
6.) Type/Paste you're MEID/IMEI, verify it before you click Repair.
7.) Verify again.
8.) Click repair, wait for software to reboot your device.
9.) If the phone doesn't reboot after 1 Min, go ahead and reboot your device.
10.) Enjoy your ICS rom on your working VS920 device.
[Problems]
Q.) What do I need in order to run the software?
A.) Just dotnet 4.0
Q.) Where do I get my IMEI/MEID ?
A.) Remove the back, then remove the battery. There is a white sticker that say's IMEI. Type the whole string in the top box ignoring the last number its a checksum, you will see the last number being calculated on the IMEI field. Make sure it all matches up.
Q.) I didn't listen/read what you wrote about the 1 time write.
A.) I can't do anything for you.
Q.) The application is throwing an error.
A.) Please take a screen shot, and copy the error then paste here.
Q.) The application just randomly quites.
A.) Stop trying to log what the application is doing, quit any debuggers and try to open the app again.
Q.) My antivirus is picking this up a a virus/torjan why?
A.) Most antivirus suck anyway, they scan on the pe header of the file. If its unable to process it, it will automatically flag the program as a virus. I assure you there is no virus. All my software gets protected low level to prevent tampering with.
Q.) Was the license agreement really needed, its annoying!
A.) No it probably wasn't but to protect me, FTT, and XDA-Developers then yes. I put that there you are fully aware that it is an as is software and you are agreeing not to reverse engineer the software as well as agreeing that you are doing this at your own risk.
Video
How it works
Now while I tested this over and over on my two test devices and they work fine. This doesn't mean that it works fine on every machine. I built the app in less then a day. I have added as many checks as I can so it wont mess anything up.
DotNet Framework 4.0 Is needed.
Download Here
VS920 MEID Repair Utility 1.0
MD5 Sum
Exe: 142882a5de3ae3204704626933522fdc
Rar: 48dd4ab56710ce901af9e2e067d11e1f
DO NOT REPOST THIS ON ANY OTHER FORUMS, DO NOT LINK TO THIS FROM OUT SIDE OF XDA. I MONITOR ALL TRAFFIC ON THIS SITE. I WILL PULL THE FILES IF I HAVE TO.
Reserved for later use if i need it.
I'm getting a 404 on that link.
Link is fixed.
I would love for some success or fail stories, some feed back as well. Hopefully all success stories , but I know that never happens lol.
If I have helped you at all please don't forget to say thanks.
The rar file tested ok with 7Z.
I tried to download dotnet 4.0 and my Win7 64 bit machine asked if I wanted to re install it.
The program crashes before it opens.
A popup askes to check the web for a fix.
EDIT:
You sure that was Internet Modem, or Ethernet?
EDIT:
Fail either way.
Same results here. Also what language was this built in?
Hmm can you post a screen shot of the crash. Ill have to check it out. I have another machine ill run it on right now.
Wow I'm an idiot
No wonder it crashed.
dotNet 4.5 ughh...
You can try to install 4.5 if you want or ill have to recompile later tonight.
Application Crash
Code:
Faulting application name: VS920 MEID Repair Utility.exe, version: 1.0.0.0, time stamp: 0x4fc6f0df
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x2224
Faulting application start time: 0x01cd3eef4903a23f
Faulting application path: C:\Users\Blake\Desktop\VS920 MEID Repair Utility.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 874a351a-aae2-11e1-9249-f1c420cf0b5b
And the .Net crash
Code:
Application: VS920 MEID Repair Utility.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeLoadException
Stack:
at System.ModuleHandle.ResolveMethod(System.Reflection.RuntimeModule, Int32, IntPtr*, Int32, IntPtr*, Int32)
at System.ModuleHandle.ResolveMethodHandleInternalCore(System.Reflection.RuntimeModule, Int32, IntPtr[], Int32, IntPtr[], Int32)
at System.ModuleHandle.ResolveMethodHandleInternal(System.Reflection.RuntimeModule, Int32, System.RuntimeTypeHandle[], System.RuntimeTypeHandle[])
at System.Reflection.CustomAttributeData..ctor(System.Reflection.RuntimeModule, System.Reflection.CustomAttributeRecord)
at System.Reflection.CustomAttributeData.GetCustomAttributes(System.Reflection.RuntimeModule, Int32)
at System.Reflection.CustomAttributeData.GetCustomAttributesInternal(System.Reflection.RuntimeAssembly)
at System.Reflection.RuntimeAssembly.GetCustomAttributesData()
at System.Reflection.CustomAttributeData.GetCustomAttributes(System.Reflection.Assembly)
at System.Resources.ManifestBasedResourceGroveler.GetNeutralResourcesLanguage(System.Reflection.Assembly, System.Resources.UltimateResourceFallbackLocation ByRef)
at System.Resources.ResourceManager.CommonSatelliteAssemblyInit()
at System.Resources.ResourceManager..ctor(System.Type)
at System.ComponentModel.ComponentResourceManager..ctor(System.Type)
at ?1?.?3?.?28?()
at ?1?.?3?..ctor()
at ?1?.?7?.?67?()
amoamare said:
Hmm can you post a screen shot of the crash. Ill have to check it out. I have another machine ill run it on right now.
Click to expand...
Click to collapse
I used 7z to test the archive before I tried to run it.
TypeLoadException is thrown when the common language runtime cannot find the assembly, the type within the assembly, or cannot load the type.
My visual studio decided to default 4.5 framework. So until I can recompile, might just need to install dotNet 4.5
Dotnet 4.5 Beta Download link
EEEW a beta? Just kidding.
No problem, thank you for working so hard at this...
No problem.
4.5 is actually pretty stable for being a beta. I've been running it for months now with no issues that I noticed. Then again i'm on my dev machine and it hardly has issues :S except for it doesn't like wireless keyboards and mouse's ha.
Well it looks like it would do the trick.
It ran through all the motions.
Except I haven't tried the ICS update.
I was thinkin of waiting for a .bin file instead of trying to figure out where the hell the Phone Booth could be found.
I have little doubt that this will work for those that wave gotten stuck with the peek a boo IMEI.
Now if you had the time to work out something for my poor LG Fathom.
It got a case of amnesia or something.
cac2us,
If you wan't to try the ICS update, I can team view with you and show you how to use LGNPST in order to flash the .tot. Its pretty simple once you see it the first time.
People that are having Google Play Store issues and no 4G and Intermittent 3G is because there IMEI is zero'd out. I can log into the play store fine, use my internet fine etc, but when I zero'd my IMEI and MEID out it wouldn't download my e-mails or anything, I couldn't log into the play store it would just freeze.
Whats wrong with your Fathom?
Thanks, but if the only way is to use download mode, that's what killed my fathom's MEID.
So,... aw what the hell.
If I put it in download mode then the .tot file should get accepted?
And where the hell is that Phone Booth folder that I read about?
Fahthom got flashed too many times.
And in download mode. Then I spoofed at to be an HTC 6800, and now it won't change back.
I might have to pay the $99.00 for the newer Workshop to write it back.
Maybe if I send it to you along with a bucket of cash, and the box it came in you could maybe fix it?
That Google play store issue makes sense, just like my fathom won't activate without an MEID or an IMEI.
You don't need to flash in download mode.
Connect the phone to the computer, select internet for the connect and then select modem.
Make sure you have registered the dll regsrv32 "Path to dll";
After that open LGNPST you should see that it shows the model VS920. Click on the Phone settings button, then click read. Make sure it reads everything correctly. Close out of phone settings.
The Port will flash to say its done click on it to reactive the port.
Select upgrade and click browse.
Now in the window that pops up, down at the bottom where you can select a file. Don't worry about what it says. The box above it where you can type the location enter in *.* then click enter.
This will display all files. Now select the .tot file. "You can also rename .tot to .bin" once you select the file, click on upgrade. The flash should succeed fine now..
The reason people have crashing issues is because they would go to "Phonebook" section in the software and use that. The phonebook backup/restore is not used for upgrading the phone.
Also to answer your question, yes I could most likely repair it for you. No cost, just pay for shipping here and back.
OK, I'm ready to do it.
The only part "Make sure you have registered the dll regsrv32 "Path to dll";"
Isn't that file in the Windows\System32 folder?
How do I register it. I allready did the right click thing for the 920.dll while it sits in the Models folder of LGNPST folder.
I will PM you with the details of the Fathom.. Thanks..
Yes if your using the right click register, and you right clicked and registered and it returned with succeeded then the dll is registerd and your are good to go.

[HOW-TO] Recover your IMEI

Recover your IMEI after erase entire cp
Click to expand...
Click to collapse
EDIT: TUTORIAL TO RECOVER YOUR IMEI
Step 0: Connect your OB to PC via usb cable.
Step 1: Download putty
Step 2: Enter dialer and dial: 3845#*970#
Step 3: Go to AP CP USB Switching and select CP USB
Step 4: Open putty.exe , select Serial as in the image below and replace COM1 with the port your phone uses and click Open.*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 5: Type at in the terminal window that opened if the message received is OK:fingers-crossed: proceed to next step if not redo the steps 2 - 4.
Step 6: Type at%imei=1,2,3,4,5,6,7,8,9,0,1,2,3,4,5 replace the numbers with your imei ( you must keep the , between the numbers )
Step 7: Change from CP USB to AP USB.
Step 8: Reboot your phone.
*To see wich one your phone uses start Smart Flash and use the COM port that SF uses
:good:
happens to many of us
flash with smartflashtool
wipe entire cp
That will erase my imei... are you sure that is the way to do it? or is a hardware problem this didn't happened after i flashed a rom it hapened while it was runing korean rom
smart flash tool wont erase your imei
erasing entire cp will erase your imei and you can restore it back (search question and answers section)
no, i myself thought it was a hardware problem...its not
and what goes in trying?
I did the erase entire cp thing now my imei has lots of 0 but still same network issue.
r3stor3 said:
I did the erase entire cp thing now my imei has lots of 0 but still same network issue.
Click to expand...
Click to collapse
Now you have to restore your IMEI!!!! Without IMEI lot of things wont work at all
as i said, nothing goes in trying. its better than going for repair, paying and waiting
sorry for you mate
baseband maybe?
Are you sure the SIM card is ok ?
I had a SIM card die, I still had access to all the data but the network was unavailable. It did the same in 3 different phones (one of them being a "dumbphone" - Nokia 3410). The network operator replaced the card and the new card worked without a problem ever since.
So, before doing anything drastic, check if the SIM card is still working in another phone, if it's not, then the card is dead and you have to change it, if it works then your phone has problems.
Edit : the girl at the phone store said they have about 2-3 "dead" SIM cards each week, all of them work ok (you can see the phone numbers saved in them) except they cannot connect to the network, so it seems the new SIM cards are more sensitive than the older ones.
What's the reason for causing this?
If u tell, it may help others before doing that wrong step
Sent from my LG-P970 using xda premium
It was actually a SIM card failure! Tested it with a new one and worked! Now someone knows how to change the IMEI back to the original one?
search in the question and answers thread there is atleast one thread about it
one maybe "no sim card inserted"
I did it but i didnt used Hyperterminal .wich was way to complicated for basicaly simple task, I used putty and it worked flawlessly! if needed i can make a simple tutorial using putty!
shall we have to connect the pc and phone with USB cable while this procedure ?
A video availability is appreciated.
all this is made with the phone connected to the pc
you could add it to your OP in case anyone needs it in the future
I though I was finally close to restore my IMEI.
...But: As soon as I change from AP to CP USB Mode, my device only connects for a second and then disconnects. With AP Mode is works like a charm.
Thanks again for the great tutorial.
EDIT: I suspected this to be a problem with Windows XP, but using Ubuntu indicates that if a change to CP USB Mode, the device only briefly appears and then disappears.
Hello guys! Trying to save my girlfriend's phone here...
So the imei write command is not working, showing an error msg, although it shows ok to at command...
Also strangely he is not accepting the same com port of SF but only a dif one...
Can anyone help?
I'd really appreciate it!!!
Cheers
Sent from my GT-I9300 using xda app-developers app
r3stor3 said:
EDIT: TUTORIAL TO RECOVER YOUR IMEI
Step 0: Connect your OB to PC via usb cable.
Step 1: Download putty
Step 2: Enter dialer and dial: 3845#*970#
Step 3: Go to AP CP USB Switching and select CP USB
Step 4: Open putty.exe , select serial as in the image below and replace COM1 with the port your phone uses and click Open.*
Step 5: Type at in the terminal window that opened if the message received is OK:fingers-crossed: proceed to next step if not redo the steps 2 - 4.
Step 6: Type at%imei=1,2,3,4,5,6,7,8,9,0,1,2,3,4,5 replace the numbers with your imei ( you must keep the , between the numbers )
Step 7: Change from CP USB to AP USB.
Step 8: Reboot your phone.
*To see wich one your phone uses start Smart Flash and use the COM port that SF uses
:good:
Click to expand...
Click to collapse
When i type the port and press open nothing happen help me !
Also when i tap CP USB nothing happen and not show any com ports in device manager When i tap AP USB it shows !
But, i can't open the port, can't send AT commands !
Any other method to send AT commads !
*** I also tried with HYPER TERMINAL
r3stor3 said:
EDIT: TUTORIAL TO RECOVER YOUR IMEI
Step 0: Connect your OB to PC via usb cable.
Step 1: Download putty
Step 2: Enter dialer and dial: 3845#*970#
Step 3: Go to AP CP USB Switching and select CP USB
Step 4: Open putty.exe , select serial as in the image below and replace COM1 with the port your phone uses and click Open.*
Step 5: Type at in the terminal window that opened if the message received is OK:fingers-crossed: proceed to next step if not redo the steps 2 - 4.
Step 6: Type at%imei=1,2,3,4,5,6,7,8,9,0,1,2,3,4,5 replace the numbers with your imei ( you must keep the , between the numbers )
Step 7: Change from CP USB to AP USB.
Step 8: Reboot your phone.
*To see wich one your phone uses start Smart Flash and use the COM port that SF uses
:good:
Click to expand...
Click to collapse
Now i configured all ! well the Ok message didn't appear but the black cmd window open and when i send commands no reponce help me ! anyone

[TUT] Unlocking 262-000 bootloaders

Alright, so let's start the fun
These are the steps i did for successfully unlocking my BL.
I can't and won't guarantee that theese steps are going to work for you. please report back here if it worked for you or not and please post also the buy-date of your phone
it might be possible that this works for other firmwares too, please try and report back here thanks
Requirements
- a Linux distro (mine is Xubuntu 12.10, but should work on every Linux OS)
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware (preferably ANEUBK)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The steps
1) charge your phone to 100%
2) connect your phone in LG software mode
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
(if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
4) now you should see this on your phone:
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
10) do the harlem shake and be happy about your unlocked BL
and please, don't post "thanks" if i've helped you, just hit the thanks button
Does it applies on 234 devices too? I ll not have access on a linux pc till monday!
Cool dude, thanks.
Do you think its possible to do this with those bootable Linux OS cd (so i dont have to install linux on my hd just for dooing that) ?
Do you loose the unlocked BL if you install another KDZ after the unlocking?
Someone know why not working on every windows?
I have the android sdk installed and the same procedure worked for me without linux.
nikosblade said:
Does it applies on 234 devices too? I ll not have access on a linux pc till monday!
Click to expand...
Click to collapse
i honestly don't know try it, like i've said, give it a try and report back
profyler said:
Cool dude, thanks.
Do you think its possible to do this with those bootable Linux OS cd (so i dont have to install linux on my hd just for dooing that) ?
Do you loose the unlocked BL if you install another KDZ after the unlocking?
Click to expand...
Click to collapse
hmmm, possible? maybe, but this would be extremely slow, cause you've gotta get adb working first and so on. so i'd say it won't work, but not sure.
but some distros have got the ability to install them as a "windows prog", this creates a virtual harddrive where linux can be booted from, so no need for reformatting the hdd just google about it
some users reported that it will not be lost after flashing a kdz. but also here: not sure, cause i haven't tried it myself yet (my BL is now unlocked for about 3h yet )
verlol said:
Someone know why not working on every windows?
I have the android sdk installed and the same procedure worked for me without linux.
Click to expand...
Click to collapse
i guess it is driver related... what firmware do you use? german or euro-open?
laufersteppenwolf said:
View attachment 1861354
Click to expand...
Click to collapse
This "final" screen I can confirm on my 262-000 from Amazon. I used Windows and http://forum.xda-developers.com/attachment.php?attachmentid=1859693&d=1365149301 for the ADB driver but the same method. It takes like 2sec to do! I installed CWM etc. fine afterwards!! Thank you!
Security error
I don't get the screen like in 4)
I just get Security Error, any ideas?
Don't work with ADEUBK 262 000
I can only unlock with the china 20a.
mrlollog said:
I don't get the screen like in 4)
I just get Security Error, any ideas?
Click to expand...
Click to collapse
This is not universal, seems with latest update LG showed some mercy on German users...rest can feel screwed all over again
F*ck you LG retards they are only good if Google screws them good, who's your papa :silly:
On 234 this didn't work with Linux and the leaked 20A.
I might try later to update the phone (GBR) with the official one but I wouldn't hold my breath.
Sent from my Nexus 7 using Tapatalk 2
laufersteppenwolf said:
i guess it is driver related... what firmware do you use? german or euro-open?
Click to expand...
Click to collapse
I use euro-open.
If its driver related, which driver is needed?
I only know of the Google USB Driver for the Android Composite ADB Interface.
Not works (on linux vitural machine ) The pone says ... Lg Security error...
me too
I do not get unlock
tiflao said:
Not works (on linux vitural machine ) The pone says ... Lg Security error...
Click to expand...
Click to collapse
same here, on win or on vm i got this error ...... (262-00)
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
DavidXanatos said:
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
Click to expand...
Click to collapse
The Phone reboots after ~5 secs.
laufersteppenwolf said:
Alright, so let's start the fun
These are the steps i did for successfully unlocking my BL.
I can't and won't guarantee that theese steps are going to work for you. please report back here if it worked for you or not
it might be possible that this works for other firmwares too, please try and report back here thanks
Requirements
- a Linux distro (mine is Xubuntu 12.10, but should work on every Linux OS)
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware (preferably ANEUBK)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The steps
1) charge your phone to 100%
2) connect your phone in LG software mode
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
View attachment 1861346
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
(if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
View attachment 1861348
View attachment 1861349
4) now you should see this on your phone:
View attachment 1861353
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
View attachment 1861354
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
View attachment 1861355
10) do the harlem shake and be happy about your unlocked BL
and please, don't post "thanks" if i've helped you, just hit the thanks button
Click to expand...
Click to collapse
Thanks for the tutorial - but can you explain why is this just working on a Linux OS ? I mean what's the difference between trying to unlock the BL on a Win7/8 OS or a Linux OS ?
THanks
DavidXanatos said:
when you get " Lg Security error..." is the phone bricked or you just need to pull the battery and reboot and than its fine again?
Click to expand...
Click to collapse
Sometimes is semi-bricked, specialy after the "morning-call empty"
Don't worry, re-flashing will solve the problem.

[GUIDE] [NEW] Root All L90 Varients with Latest updates [EASY]

All Credit to @thecubed. Please thanks him on his OP here
This is not my original work.I am just sharing this GUIDE for easy rooting of L90 with latest updated, those are not supported by towelroot.
I have tested this method myself and it is working perfectly for me, but it is also possible that it might not work for you for some reasons, so don't panic, just post your problem or whatever error you are facing (please attach screenshot if possible). I or other thread members will try to troubleshoot it. After resolving the problem I'll update this post, so that other members do not face such problem again
Click to expand...
Click to collapse
PLEASE, USE THIS TUTORIAL AT YOUR OWN RISK, IF SOMETHING WENT WRONG (because of your stupidity) ME OR XDA WILL NOT RESPONSIBLE FOR YOUR LOSS.
I HAVE ONLY TESTED THIS METHOD WITH MY L90 D410 AND IT MUST WORK WITH OTHER VARIENTS:fingers-crossed: . BUT STILL FOLLWO THIS GUIDE AT YOUR OWN RISK
Click to expand...
Click to collapse
First of all Install USB Drivers from following link :-
Click here to download L90 USB Drivers
After installing USB Drivers, download Rootl90.zip file attached to this post below and extract it to C Drive of your PC.
On your phone, Goto Settings -> General -> Developer options and enable USB debugging by ticking the check box.
(If you are unable to find Developer options, then go to About phone -> Common -> Software Information and continuously tap on Build amount for 5 to 6 times, it will enable developer options)
Now Connect your phone with PC in LG Software mode, open device manager and confirm ADB Device listed at the top of the list, as an image attached below:-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now open Rootl90 folder, that you extracted to the C drive in the first step.
In this folder, press and hold shift key on the keyboard, right click on blank place and click on open command window here. The command prompt will start with c:\Rootl90>
Now type following commands one by one in the command window (simply copy, paste and hit enter) :-
Code:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
and match result as shown in following images :-
Command 1
After this phone will reboot into recovery as shown in the image below
Now Proceed to Command 2.
Command 2
Command 3
Command 4
After the last command your device will reboot, congratulations your phone is now rooted. Download and install Supersu form playstore.
reserved
Guys plz reply if worked for other than D410 Model
D410 here, after first command wait til the drivers are installed,
There is a redaction error in your comands, the correct are:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
VainxTheLurker said:
D410 here, after first command wait til the drivers are installed,
There is a redaction error in your comands, the correct are:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
Click to expand...
Click to collapse
Thanks for correction
gdjindal said:
Thanks for correction
Click to expand...
Click to collapse
Aren't these the same commands available in the purpledrake script?
Sent from my LG-D405n using XDA Free mobile app
razoract said:
Aren't these the same commands available in the purpledrake script?
Sent from my LG-D405n using XDA Free mobile app
Click to expand...
Click to collapse
yes it is from purpledrk script.
thanks!
thanks!
I've tried it on D405n and it works. Thank you.
.
LOOOL
Why should i use
Code:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
when i could use simple original purpledrake way. i think you took the files from purpledrake thats all ? or i am wrong ???
Does not work on t-mobile LG L90, D415 with the software version D41510e.
adb reboot --bnr_recovery reboots to a blank screen. Presumably it's still a recovery -- adb connects. But "adb push start_recovery /temp/start_recovery" does not work -- no such file or directory. Changing the destination to /tmp in both adb push commands does push files to the phone but there is no root after reboot.
Looking at the purpledrake script, I also see that the vulnerability tests looks for a process "brd" on the phone but there is no such command in the output of ps.
Any ideas?
LG L90, T-mobile D415 with SW version D41510c also does not work.... same exact issue as described above...
---------- Post added at 10:36 PM ---------- Previous post was at 10:17 PM ----------
voland66 said:
Does not work on t-mobile LG L90, D415 with the software version D41510e.
adb reboot --bnr_recovery reboots to a blank screen. Presumably it's still a recovery -- adb connects. But "adb push start_recovery /temp/start_recovery" does not work -- no such file or directory. Changing the destination to /tmp in both adb push commands does push files to the phone but there is no root after reboot.
Looking at the purpledrake script, I also see that the vulnerability tests looks for a process "brd" on the phone but there is no such command in the output of ps.
Any ideas?
Click to expand...
Click to collapse
You should use TowelRoot app, it roots the phone in like 2 seconds and no reboot is required...
Search in google for "how to root T-mobile LG D415" - first link has few instructions but leads you to the website where to download the tr.apk (if doing from phone) long click on lambda sign and select "save link" ... thank install the app and run it... 2 seconds... done...
996
cardusan said:
LG L90, T-mobile D415 with SW version D41510c also does not work.... same exact issue as described above...
---------- Post added at 10:36 PM ---------- Previous post was at 10:17 PM ----------
You should use TowelRoot app, it roots the phone in like 2 seconds and no reboot is required...
Search in google for "how to root T-mobile LG D415" - first link has few instructions but leads you to the website where to download the tr.apk (if doing from phone) long click on lambda sign and select "save link" ... thank install the app and run it... 2 seconds... done...
Click to expand...
Click to collapse
Towelroot works on the previous SW version (was it D41510c? I don't remember). But there is an update to the version 10e and towelroot does not work on it (at least it did not work yesterday, this was the first thing I tried). Unfortunately, I updated without checking forums and I might have forgotten to turn on survival mode in supersu (although i'm not sure survival mode works).
voland66 said:
Towelroot works on the previous SW version (was it D41510c? I don't remember). But there is an update to the version 10e and towelroot does not work on it (at least it did not work yesterday, this was the first thing I tried). Unfortunately, I updated without checking forums and I might have forgotten to turn on survival mode in supersu (although i'm not sure survival mode works).
Click to expand...
Click to collapse
Towelroot worked fine on my D41510c. I have not updated though, and probably won't as some say nothing really changed with the update.
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
cardusan said:
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
Click to expand...
Click to collapse
Which version do you have 10c or 10e? Is this T-Mobile phone? If it is 10e -- did you just use towelroot straigtforwardly? Was the phone rooted prior to 10e upgrade?
I upgraded rooted phone from 10c to 10e, possibly having forgotten to turn on survival mode in supersu, and lost root. I still have adaway's host file (so ads are blocked, now permanently since I can't go back to the standard host file), I still have supersu files in relevant directories but no root when the phone is running. And towel root says that it can't work on my phone. I was just assuming that the update has a newer kernel that fixes vulnerability exploited by towelroot. I'd love to recover root if I could.
cardusan said:
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
Click to expand...
Click to collapse
Hello!
I would have just a short question about the root. If I make the root with this towelroot am I loosing the guarantee? I mean this procedure is open the bootloader or this is just a "smooth" root?
Thank you!!!!
fynky said:
Hello!
I would have just a short question about the root. If I make the root with this towelroot am I loosing the guarantee? I mean this procedure is open the bootloader or this is just a "smooth" root?
Thank you!!!!
Click to expand...
Click to collapse
Yes, you will lose the guarantee. I believe towelroot just roots your phone.
D1358531 said:
Yes, you will lose the guarantee. I believe towelroot just roots your phone.
Click to expand...
Click to collapse
Thank you for your quick reply.
So if it is just a simple root and in the future I will have some problem with my phone I will be able to put back the original software to the phone without any mark? Because at Samsung phones have a special trick. If you root your phone and the bootloader is open the Knox code (this is the special trick) is jump from 0 to 1 and you will not be able to replace it anymore and you will lose the guarantee forever with it.
I wouldn't like to change the software on my phone I just would like to install programs to the SD card but it is not allowed under the KitKat unless I root my phone. But I think the simple root should be enough for that isn't it?
BTW. Will I need a special program after the root is I want to install to SD card?
Thank you very much!!!!
Before I do this I would like to know if there will be a custom recovery like two? Does this work with the D415? Would I still have my T-mobile connection? I only rooted my Nexus 7 2012 with the Nexus root Toolkit.

EDL flashing (MTK) Hard Brick

Hello,
I've recently hardbricked my Redmi Note 9
I've tried shorting some of the pads to see if I can flash it through the communication ports using EDL. I've shorted some of the pads and the flash tool shows these logs..:
[17:54:15]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:54:15]:ls ubs :Communications Port (COM1)
USB Serial Device (COM5)
[17:54:15]:GetScriptDevices
[17:55:24]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:55:24]:ls ubs :Communications Port (COM1)
How do you get the flash tool to recognize the communication port as a device?
Redmi Note 9 uses MTK if I remember correctly.
I hardbricked it while trying to flash the most recent ROM.
One of 2 things could've gone wrong:
Either the fact that I was jumping from Android 10 to Android 11 ( I was using the fastboot ROM)
Or the fact that I accidentally clicked "Clean All and Lock", and then something went wrong there.
However one thing is for sure, the preloader is corrupted. I don't think FRP is gone though.
Any tips?
-Thanks
FriendlyChemist said:
Hello,
I've recently hardbricked my Redmi Note 9
I've tried shorting some of the pads to see if I can flash it through the communication ports using EDL. I've shorted some of the pads and the flash tool shows these logs..:
[17:54:15]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:54:15]:ls ubs :Communications Port (COM1)
USB Serial Device (COM5)
[17:54:15]:GetScriptDevices
[17:55:24]:lsusb path:"C:\Users\Friendly Chemist\Downloads\mi-globe.com_Xiaomi_Mi-FlashTool_20200314\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[17:55:24]:ls ubs :Communications Port (COM1)
How do you get the flash tool to recognize the communication port as a device?
Redmi Note 9 uses MTK if I remember correctly.
I hardbricked it while trying to flash the most recent ROM.
One of 2 things could've gone wrong:
Either the fact that I was jumping from Android 10 to Android 11 ( I was using the fastboot ROM)
Or the fact that I accidentally clicked "Clean All and Lock", and then something went wrong there.
However one thing is for sure, the preloader is corrupted. I don't think FRP is gone though.
Any tips?
-Thanks
Click to expand...
Click to collapse
Not EDL exactly, devices with MediaTek SoC don't use EDL (this is for Qualcomm), MTK uses Preloader (download) and BROM modes, the preloader is usually inaccessible in newer models or at least useless, so you can use an exploit to bypass the BROM restriction, follow carefully this thread https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
SubwayChamp said:
Not EDL exactly, devices with MediaTek SoC don't use EDL (this is for Qualcomm), MTK uses Preloader (download) and BROM modes, the preloader is usually inaccessible in newer models or at least useless, so you can use an exploit to bypass the BROM restriction, follow carefully this thread https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/
Click to expand...
Click to collapse
Interesting, thank you very much..
But here's the thing, whenever I plug it in it still loops, even with the battery being disconnected from MB.
Do I need to let it just... stay put for a very long time? I've done that for 2 weeks and it still loops.
(Windows disconnect / reconnect sound, even when the OS does not recognize any new device)
One more thing, is there a possibility for this method to corrupt the firmware even more? Or is this some real bare-metal stuff that as long as you do correctly you should be fine?
Try this place first
[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN 🤓 (Redmi Note 9 / Redmi 10X 4G)
DISCLAIMERS: This help is specific for MERLIN devices only ! (Xiaomi Redmi Note 9 and Xiaomi Redmi 10X 4G) Keep atention. This is an UNOFFICIAL thread. This thread was based on the thread by Agent_fabulous. Thank you very much ! DON'T ask by PM...
forum.xda-developers.com
that doesn't give you the insight you need LMK
FriendlyChemist said:
Interesting, thank you very much..
Click to expand...
Click to collapse
I missed that thread, I used in the past within other threads/guides, the link provided by @L!V3_4_XC3SS has the steps better done, or at least is more comprehensive.
FriendlyChemist said:
But here's the thing, whenever I plug it in it still loops, even with the battery being disconnected from MB.
Click to expand...
Click to collapse
You need to power it off completely by pressing the three buttons, in the short period you see device is off, then release the PWR button and keep pressing the two volume buttons to enter to BROM mode while you connect to the PC, run first the bypass bat.
FriendlyChemist said:
Do I need to let it just... stay put for a very long time? I've done that for 2 weeks and it still loops.
Click to expand...
Click to collapse
If the trick doesn't work instantly then waiting is no sense, try again.
FriendlyChemist said:
(Windows disconnect / reconnect sound, even when the OS does not recognize any new device)
One more thing, is there a possibility for this method to corrupt the firmware even more? Or is this some real bare-metal stuff that as long as you do correctly you should be fine.
Click to expand...
Click to collapse
Always that you use the Download option you are safe, if preloader is un-ticked from the partitions and if the option Format Whole Flash except Bootloader is ticked too in the Format tab then you are totally safe.
How do I know my device is in BROM mode?
I've tried to first power it off, then pressing the 2 vol buttons. It just.. reboots and keep bootlooping.
FriendlyChemist said:
How do I know my device is in BROM mode?
I've tried to first power it off, then pressing the 2 vol buttons. It just.. reboots and keep bootlooping.
Click to expand...
Click to collapse
Read carefully the thread linked and follow one-by-one all the steps, if you run first the bypass.bat then you will see a message that the DA/SLAA protection was disabled. This way, you'll go to know that you are now on BROM mode.
SubwayChamp said:
Read carefully the thread linked and follow one-by-one all the steps, if you run first the bypass.bat then you will see a message that the DA/SLAA protection was disabled. This way, you'll go to know that you are now on BROM mode.
Click to expand...
Click to collapse
So the payload launches on COM5 correct?
Also I have no way to stop it from bootlooping. I've tried shutting it down, same thing,
Like I said before.
While it's online, it's detected as a USB serial device on COM5.
FriendlyChemist said:
So the payload launches on COM5 correct?
Also I have no way to stop it from bootlooping. I've tried shutting it down, same thing,
Like I said before.
While it's online, it's detected as a USB serial device on COM5.
Click to expand...
Click to collapse
You have to achieve here two main things; install the USB MediaTek preloader using the LibUSB device filter and the second, get your device detected to BROM mode.
For the first thing just connect your device without pressing a button, open the device filter window and see the variants, when a new item appears quickly press on it to install the drivers.
For the second thing, although your device is trying to rebooting this doesn't matter if you learn to make the right combination buttons variables at the right time, wait the exact time that device gets off and press the two volume buttons to attach it to the PC, but first launch the bypass.bat. Be sure that you are understanding what is written here, I had the same issue in two devices and got to sort it anyway.
SubwayChamp said:
You have to achieve here two main things; install the USB MediaTek preloader using the LibUSB device filter and the second, get your device detected to BROM mode.
For the first thing just connect your device without pressing a button, open the device filter window and see the variants, when a new item appears quickly press on it to install the drivers.
For the second thing, although your device is trying to rebooting this doesn't matter if you learn to make the right combination buttons variables at the right time, wait the exact time that device gets off and press the two volume buttons to attach it to the PC, but first launch the bypass.bat. Be sure that you are understanding what is written here, I had the same issue in two devices and got to sort it anyway.
Click to expand...
Click to collapse
I tried running the bypass,
I followed all the steps, installed the drivers, and the filter lib usb thingy.
I got an error while running the first bypass:
Traceback (most recent call last):
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 213, in <module>
main()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 44, in main
config, serial_link_authorization, download_agent_authorization, hw_code = get_device_info(device, arguments)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 136, in get_device_info
hw_code = device.get_hw_code()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 178, in get_hw_code
self.echo(0xFD)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 110, in echo
self.check(from_bytes(self.read(size), size), words)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 88, in check
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0xfd got 0xfe
FriendlyChemist said:
I tried running the bypass,
I followed all the steps, installed the drivers, and the filter lib usb thingy.
I got an error while running the first bypass:
Traceback (most recent call last):
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 213, in <module>
main()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 44, in main
config, serial_link_authorization, download_agent_authorization, hw_code = get_device_info(device, arguments)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\main.py", line 136, in get_device_info
hw_code = device.get_hw_code()
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 178, in get_hw_code
self.echo(0xFD)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 110, in echo
self.check(from_bytes(self.read(size), size), words)
File "C:\Users\Friendly Chemist\Desktop\F1\bypass\src\device.py", line 88, in check
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0xfd got 0xfe
Click to expand...
Click to collapse
Don't worry, this message usually appears, just keep it trying, you need to get device in BROM mode, and it'll work. Also, you can check for this thread, if you are lacking or missing some info https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
Hello guys, I have a problem with the Redmi note 9 phone. You know that the Xiaomi interface has more negatives than the stars of the universe, but the Indonesian ROM has no problems, so I tried to change the phone from the world version to the Indonesian one, but in a way somewhat like a loophole, which led to the phone restarting itself Over and over again, I went to the phone maintenance specialists, and they told me that it needed a memory ic, but someone was able to download the Xiaomi system, which resembles a little Nokia, but through it I entered a new Xiaomi version, but the only remaining problem is the lack of service. I cannot call or receive calls or data, but all Something other than this works, so I understood from a phone specialist that the files in the memory ic have been corrupted, so the service does not work, so is there a solution
NB
The phone is rooted, but I can remove it​
The Wi-Fi is working and the Wi-Fi IP address is working​
the IP address of the network tells me that it is not there​
The serial number of the phone itself is not with me, but I think that if the Indonesian version has the serial number, I can find it​
I welcome any risky method​
Sorry for the weak language​
OMAR1.zx said:
Hello guys, I have a problem with the Redmi note 9 phone. You know that the Xiaomi interface has more negatives than the stars of the universe, but the Indonesian ROM has no problems, so I tried to change the phone from the world version to the Indonesian one, but in a way somewhat like a loophole, which led to the phone restarting itself Over and over again, I went to the phone maintenance specialists, and they told me that it needed a memory ic, but someone was able to download the Xiaomi system, which resembles a little Nokia, but through it I entered a new Xiaomi version, but the only remaining problem is the lack of service. I cannot call or receive calls or data, but all Something other than this works, so I understood from a phone specialist that the files in the memory ic have been corrupted, so the service does not work, so is there a solution
NB
The phone is rooted, but I can remove it​
The Wi-Fi is working and the Wi-Fi IP address is working​
the IP address of the network tells me that it is not there​
The serial number of the phone itself is not with me, but I think that if the Indonesian version has the serial number, I can find it​
I welcome any risky method​
Sorry for the weak language​
Click to expand...
Click to collapse
Don't take to "specialists" if you hope for a solution when it has nothing to do with hardware, they know no more than a little about software, it is very risky to let it people that can make more harm than good.
The serial number is always there, but the issue may come from an altered IMEI, or a lost baseband connection. Take your IMEI, dialing *#06# and put it here https://imei24.com/imei_check/Samsung/ to see if it matches with your device, then check if your baseband is there.
And ask the service center in-charge, which method they used to flash the software, an incorrect one could make the issue be triggered.
good forums. I'm new to the forum and I have a problem. My research to solve this has brought me here. I couldn't find the exact answer and wanted to ask you guys. I have a redmi 9c (m2006c3mg) device and I took this device in a mode from test points with a request to flash it. But I don't know exactly this mod I bought. The phone appears as Mtk Com Port in my device manager, but I could not boot my device normally with any key combination, battery removal and removal. All I want is to boot my device normally thanks for your help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources