Related
Hello,
I managed to give some hard times to me, after flashing an i9305 that I bought from eBay. The phone was rooted, in full working order, and when I flashed it to revert to stock, I managed to check EFS CLEAR, without taking any EFS backup beforehand. My odyssey is well knows to many of you; imei null/null, baseband null, to cut a long story short, I have a Samsung Galaxy S3 lte player. It does all but recognizing sim cards and provisioning networks (fair enough as I don't have a valid imei!!!).
I have gon ethrough the whole SGS2 forum, all topics, all solutions; I even unscrewed my phone to see if I can JTAG it, and that's only because QPST and EFS Pro cannot connect to my phone. Octopus and Samsung Tool CAN connect, but I cannot write imei. I cannot upload nvm files (I have a second, stock, and a friend of mine has one rooted from where we extracted the nvm in order to flash it on mine and rewrite imei), so as I read on the i9300 relevant thread, the phone can be jtaged in order to start receiving Rx and Tx commands and be able to upload the nvms and rewrite the imei.
The thing is that nobody tried to jtag this phone, and if someone did, nobody posted the resistance that has to be short circuit. As I saw here: http://forum.xda-developers.com/showpost.php?p=28073021&postcount=5 it is possible for i9300. Is there some schematic for i9305 then, or someone knows which resistance I have to short?
Any help will be appreciated...
you can still connect through Odin or adb, connecting is not the issue. there's nothing to write, imei is not stored in plain text, it's encrypted, so you won't be able to restore it if you don't have a backup. send it to service
I have the same problem bat I have imei back up sent it to repair center and after 2 month have it back
told me replace motherboard pay 250 euro bikose the binary counter 6.
You fixed Patrida?
trifos said:
I have the same problem bat I have imei back up sent it to repair center and after 2 month have it back
told me replace motherboard pay 250 euro bikose the binary counter 6.
You fixed Patrida?
Click to expand...
Click to collapse
Kalimera filaraki!
Unfortunately I was unable to fix it. Sotmax (member on both xda and myphone) offered to fix it. He could do it for a small cost but I would have to ship it from Thessaloniki to Kefalonia, and it was during the days that the ship workers were on strike. So it would delay a bit more, and I preferred to sell it. A guy over here (who then became friend and we exchange from time to time), bought it and fixed it in 10 minutes!!!!
He has schemas and JTAGs for most of the commercial phones, and I think that he had to open it and de/solder some pcb. It's not something difficult for him, but for you and me it's an issue!! The thing is that someone is now happy with the phone, and I am happy with my new gray 9305!
So if you need to fix it and you cannot find a workaround, you can always try talking to one of these 2 guys to have your work done! I know how much Sotmax is charging for the repair, and he says his job is guaranteed. you just have to be patient for 2 days to ship and 2 days to return (the fix takes no more than 30 minutes as he said). The other guy (his nickname is demernick at insomnia) didn't tell me how much he takes to fix, but it's much quicker as he only needs 1 day to ship from Florina to Thess, and another 1 day to return, so it's half time
There is also another one guy who writes in here. He says that he can do the job over the internet via teamviewer (you just have to follow his instructions and post the original IMEI from the box and phone under the battery), and he works with Octopus box ans Samsung Tool. If he manage to fix it, he charges you 10 euros via Paypal! He spent 2 days for me, so I donated that 10 euros to him for his work, even though he couldn't fix it... his website is cvxcvx.pl and I think his name in here has something to do with the website.
All 3 of them are trusted users. 2 of them are respected in here, and demernick is well established on insomnia!
If you need some extra help, feel free to contact me!
latousakis said:
Hello,
I managed to give some hard times to me, after flashing an i9305 that I bought from eBay. The phone was rooted, in full working order, and when I flashed it to revert to stock, I managed to check EFS CLEAR, without taking any EFS backup beforehand. My odyssey is well knows to many of you; imei null/null, baseband null, to cut a long story short, I have a Samsung Galaxy S3 lte player. It does all but recognizing sim cards and provisioning networks (fair enough as I don't have a valid imei!!!).
I have gon ethrough the whole SGS2 forum, all topics, all solutions; I even unscrewed my phone to see if I can JTAG it, and that's only because QPST and EFS Pro cannot connect to my phone. Octopus and Samsung Tool CAN connect, but I cannot write imei. I cannot upload nvm files (I have a second, stock, and a friend of mine has one rooted from where we extracted the nvm in order to flash it on mine and rewrite imei), so as I read on the i9300 relevant thread, the phone can be jtaged in order to start receiving Rx and Tx commands and be able to upload the nvms and rewrite the imei.
The thing is that nobody tried to jtag this phone, and if someone did, nobody posted the resistance that has to be short circuit. As I saw here: http://forum.xda-developers.com/showpost.php?p=28073021&postcount=5 it is possible for i9300. Is there some schematic for i9305 then, or someone knows which resistance I have to short?
Any help will be appreciated...
Click to expand...
Click to collapse
Are you sure you ticked EFS clear? Could it be that you had Perseus kernel prior to installing stock? I had some similar problem and as a result my phone only works with Perseus kernel installed.
I would try installing Perseus kernel to see if the phone magically springs back to life.
Rekoil said:
Are you sure you ticked EFS clear? Could it be that you had Perseus kernel prior to installing stock? I had some similar problem and as a result my phone only works with Perseus kernel installed.
I would try installing Perseus kernel to see if the phone magically springs back to life.
Click to expand...
Click to collapse
I was aware of Perseus, but that wasn't the issue. I DID tick the EFS Clear. After booting back to normal, the imei wasn null/null and the /efs folder was wiped out. it was en empty folder with just 1-2 files in it...
latousakis said:
I was aware of Perseus, but that wasn't the issue. I DID tick the EFS Clear. After booting back to normal, the imei wasn null/null and the /efs folder was wiped out. it was en empty folder with just 1-2 files in it...
Click to expand...
Click to collapse
Thing is, the I9305 doesn't store IMEI in the EFS. Which is why I find this a little strange.
Rekoil said:
Thing is, the I9305 doesn't store IMEI in the EFS. Which is why I find this a little strange.
Click to expand...
Click to collapse
Yes, but the other strange thing is that instead of having a bunch of files, there were only 2 files in the /efs folder!
latousakis said:
Yes, but the other strange thing is that instead of having a bunch of files, there were only 2 files in the /efs folder!
Click to expand...
Click to collapse
So get yourself a donor EFS and substitute the MAC addresses for your own data, it's on the box isn't it?
Rekoil said:
So get yourself a donor EFS and substitute the MAC addresses for your own data, it's on the box isn't it?
Click to expand...
Click to collapse
I think that that'w what he's done!
Okay everybody,
I decided to write a new thread for my problem because I think my prob is a very special thing.
I'm from germany, so please don't wonder about my english. I think it is a understandable.
The story begins with a software update for my GT-I9305. After the update, the IMEI was just "null", after some work with google I found out that the efs partition was broken. With my bad knowledge for this case, I destroyed the whole EFS folder. I installed perseus kernel. And, there it was! The whole and correct IMEI. The solution was the perseus kernel (stock doesn't work, neither reflash). But then, after a while the phone doesn't boot anymore. I flashed Android 4.4.4 and my phone was revived but the IMEI was again "null". I have no backup or anything else!
So I spent approximately 20 hours or more to understand the efs thing. I found much solutions but nothing worked for me. So, here I am.
What I've tried before
-reflash KitKat
-reflash Perseus (not compatible anymore)
-formatting efs partition for a blank and new EFS for editing
-tried to edit nv_data.bin with HEX
-tried to backup efs with a 3rd party app and edit this with hex (the app doesn't support my GT-I9305)
and then, there it was:
-tried to use a working EFS partition from another GT-I9305
-editing with Qualcomm NV Tools! (I think THIS is the solution!)
I tried NV-items_reader_writer (1.0) and EFS Professional (2.1.73), but in both can't find my phone:
What I've done in NV-items_reader_writer
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened NV-items_reader_writer
-checked the both boxes near the SPC box
-selected the right port (last: COM4)
-clicked on "connect"
-clicked on "read"
-> here it search the phone, but it can't find it and says "Failed.. Phone does not answer"
What I've done in EFS Professional
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened EFS Pro
-clicked on "Qualcomm NV Tools"
-refreshed the Available COM Ports
-selected "SAMSUNG Mobile USB Serial Port" (last COM4)
-clicked on "Connect"
-> Here it takes few seconds and he stops and says: "Phone connection has been lost!" and "Unable to send SPC to the Phone!"
What I've tried to solve this problem
-tried QUALCOMM USB Settings: "DM + MODEM + ADB"
-reinstall all Samsung drivers
-tried to install Samsung Modem with Qualcomm drivers (failed due to wrong platform; I've Win7 X64)
-reinstall Samsung Kies (for actual drivers)
-tried to dial *#9090# (in my case, this menu is totaly blank)
-tried in factory mode
It could be that I forgot some....
Now, my question to you all is, do you know what I've done wrong? I mean, this is working for the most users, but why not for me? What do you think? Did you think I really forgot something?
Some informations:
Phone: GT-I9305
Android: 4.4.4 KitKat
Kernel: Stock (3.0.31-2760029 ; [email protected] #1 ; Fri Sep 12 13:08:24 KST 2014)
Buildnumber: KTU84P.I9305XXUFNI3
Windows: Windows 7 X64
Do you need more informations? Post it!
Please help me, I want to bring this phone back to life!
And yes I know, to change the IMEI to a number which is not your own is ILLEGAL and to prevent this, it is not well seen to talk about, but this is MY PHONE and I want to change the "null" IMEI and IMSI to MY ORIGINAL IMEI. If this is a problem, I can send a PM to an mod with my phone (where you can see the IMEI), my username on a sheet of paper and the original box with the IMEI printed on. All on one picture!
Simply... I need a hero! Be MY HERO!
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
vnholden said:
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
Click to expand...
Click to collapse
Thank you for your reply!
I tried this, already. But I can't downgrade from 4.4.4. I don't read very much about this. I just know that this is a new security option from samsung (or Android)... I will tell you when I know more
qasim799 said:
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
Click to expand...
Click to collapse
Thank you for your reply!
The warranty is already expired...
This will be the last step I will do. Before this, I will try my very best to do this at home... But thank you for this tip
Edit:
What do you all think about this idea:
-I try to find somebody with a working EFS on GT-I9305 Android 4.4.4
-I get a backup from him
-I restore this backup to my phone
-I edit the duplicated IMEI with NV Tool to my IMEI
This requires that the NV Tool will with work with an existing IMEI and the the phone will be THE WHOLE TIME IN PLANE MODE to prevent IMEI ban...
What do you think? Will this work? Do I need somebody from germany (DBT) or is this not needed?
Take it to a phone repair shop they might have a way to fix it. And if they don't they might know someone who can and it would likely be cheaper than Samsung service center
Sent from my GT-I9305 using XDA Free mobile app
Identical case (Solved)
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
WesleyPs said:
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
Click to expand...
Click to collapse
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
viktorak said:
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Hello,
someone could give me an EFS file because I deleted mine but my camera would not boot and remains on bootloop
thank you in advance
SurrendeR1993 said:
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Click to expand...
Click to collapse
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
---------- Post added at 05:00 AM ---------- Previous post was at 04:46 AM ----------
banjomike said:
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
Click to expand...
Click to collapse
Sorry dude just found out only samsung can restore Imei give phone shop a try but I don't think they could sorry
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
SurrendeR1993 said:
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
viktorak said:
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
Click to expand...
Click to collapse
Hm okay. I applied a "old bootloader" before here from xda. I don't know what it was exactly. There was a boot.so or so in it.
I will try my best. I mean, if I can beat this, this is a really great success for me. My next step is to restore a full NAND backup from a friends of mine (from a GT-I9305).
I wondered about that, after I restored a working EFS, there were no NV data.
My journey to restore a corrupted GT-I9305 without pay some money
Sent from my GT-I9300 using XDA Free mobile app
how did you success ?
how did you success ?
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed
hope this helkps anyone, took me some 20 hours of tinkering
Oakhand said:
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed(
Click to expand...
Click to collapse
Can you post the links you used?
EwOkie said:
Can you post the links you used?
Click to expand...
Click to collapse
aside from the dropbox link in my post above I did not use much else. I downloaded a stock kitkat rom, but don't know from where.
Hi,
I don't know why this happened. My phone is rooted but just randomly stopped working. It wasn't because of any flash. All I had done was root it about 5 months prior and was still on stock firmware. But now I have no signal. Here is what I have done.
1. Bought new sim board.
2. Flash the parambin file.
3. Tried to the qpst method to use nv reader to manually enter my imei. But the drivers won't work. Always has an ! point next to devices in device manager. Read, could be because I have the international version.
4. Tried flashing 2-3 other modems.
5. Updated to 4.4.4
6. Flash a file EFS_N7100XXND3_KH435987_REV05_user_low_ship to supposedly reset imei. Now I am just in factory mode.
7. Bashed head on desk.
Phone is out of warranty and there are no service centres near me. I really don't want to buy a new phone because I am saving for baby stuff.
Thanks in advance,
Tried efs pro,
It backed up efs, but on restore odin flash fails and soft bricks phone.
Try CM?
Why you don't try CM11 ROM? You only need to replace the bootloader, all well explained here:
http://wiki.cyanogenmod.org/w/Install_CM_for_i9305
jiberz said:
Tried efs pro,
It backed up efs, but on restore odin flash fails and soft bricks phone.
Click to expand...
Click to collapse
Long story short. I received a return on a phone I sold. The person who returned it tries to bypass the google lock on the phone by installing another firmware/rom. Instead of contacting me first so I could help them. they did not back anything up so all files were lost. I fix computer hardware and software but this is my first phone project. I read online how to flash it back to original firmware by using Odin 3.9 and a file I found online (N900AUCUCNC2_N900AATTCNC2_N900AUCUCNC2_HOME.tar.md5) this brought it back to droid 4.4.2. The padlock and custom icon are gone. But still, no IMEI or baseband both unknown. *#06# shows null/null. I need to get this phone able to work on my ATT network. I have no files to recover from. I don't know what files to be looking for or even what to do with them if I find them. I never rooted or jailbroke a phone first time flashing anything. so I need a bit of help. I can do it if I have clear and detailed instruction. but I myself do not know where to even begin. I have a computer and USB cable a note 3 sm-n900a and good computer and know how to get and download software and programs... just need to know what to download and how to use it. If you can help me I would be more than appreciative... thank you in advance!!!! I have attached photos.
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
pepsimaxmjs said:
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
Click to expand...
Click to collapse
Maybe this is kind a ethical question. I don't consider its ok to pay someone to be able to flash your device, specially if you have to send money to some anonymous russian guy and hopping you are not getting scamed. Clearly its not a comfortable method and it shouldn`t be that way.
If I ever need that service I would use it just to record username and password with a keylogger and post it freely, its ridiculous to pay for flashing your phone.
Yes but...
ma259 said:
Maybe this is kind a ethical question. I don't consider its ok to pay someone to be able to flash your device, specially if you have to send money to some anonymous russian guy and hopping you are not getting scamed. Clearly its not a comfortable method and it shouldn`t be that way.
If I ever need that service I would use it just to record username and password with a keylogger and post it freely, its ridiculous to pay for flashing your phone.
Click to expand...
Click to collapse
If you actually hard brick your device (mine shipped from China direct) you have a lot of hassle to get it fixed. If you don't have a service centre nearby, double the hassle and significant costs / risks to ship overseas. Sat at home, someone with the skills and the important EDL keys (i.e. registered repairer with Xiaomi) could fix the device. Mine was an unlocked phone, therefore technically I had removed the warranty. $29 to flash a bricked device and fully recover from my ****-up. OK value for me.
Hello, could you show me how to do it?
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
For removing modules, you have two methods.
For first method, you need to boot in emergency mode, open magisk manager, remove module and reboot.
(It works only with magisk +v21.)
(To boot in emergency mode, keep pressed volume down after boot starts.)
For second method, you need to flash the original stock boot.img, open magisk manager, remove module, reboot and then flash the magisk patched boot.img again.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
CruisaderX said:
he probably used [SPAM] that you can avail 3 months subscription for 19.19 usd, planning to get one when i have the money
Click to expand...
Click to collapse
It doesn't work for redmi note 9, my friend.
I'm sorry.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
pepsimaxmjs said:
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
Click to expand...
Click to collapse
Paid solutions are no longer needed. Redmi Note 9 factory firmware is out, so you can unbrick your phone, even if it's hardbricked, without authorised account.
Communos said:
Paid solutions are no longer needed. Redmi Note 9 factory firmware is out, so you can unbrick your phone, even if it's hardbricked, without authorised account.
Click to expand...
Click to collapse
If you are on MIUI V12.0.5.0 or higher, you can NOT flash without authorised account using flash tool.
You really need the EDL auth if you are on MIUI V12.0.5.0 or higher.