So I just tested out a marshmallow chinese beta rom for snapdragon, after I used it and tried to install google play store without success I just went back to TWRP, formatted back and installed by previous nandroid backup.
However when I booted in to my backup my SIM-card is not getting detected anymore and my wi-fi refuses to turn on....
Did I just brick it hard? Does anyone know how to repair this?
deleted.
It relocks the bootloader, i hope you unlock officialy. If you do, just boot into fastboot and unlock it using miunlock
Windslash31 said:
It relocks the bootloader, i hope you unlock officialy. If you do, just boot into fastboot and unlock it using miunlock
Click to expand...
Click to collapse
I did an official unlock, but I still have TWRP and can flash many different roms in it, are you sure the bootloader is locked and is the problem?
rhimezz said:
I did an official unlock, but I still have TWRP and can flash many different roms in it, are you sure the bootloader is locked and is the problem?
Click to expand...
Click to collapse
Oh, i read that wrong xD sorry. Yes imei and baseband is gone after you flash M do you havr any EFS backup in twrp?
Windslash31 said:
Oh, i read that wrong xD sorry. Yes imei and baseband is gone after you flash M do you havr any EFS backup in twrp?
Click to expand...
Click to collapse
Ì did a normal nandroid backup, is that what you mean?
rhimezz said:
Ì did a normal nandroid backup, is that what you mean?
Click to expand...
Click to collapse
Well, in a nandroid backup you usually choose the partitions, check if you have efs backup available. If you do, just restore it and your imei/baseband will be restored
Windslash31 said:
Well, in a nandroid backup you usually choose the partitions, check if you have efs backup available. If you do, just restore it and your imei/baseband will be restored
Click to expand...
Click to collapse
I backed up all partition (system, cashe, data, boot), wich ones has the efs?
If I restore the whole nandroid backup I still have the problem. No wi-fi or sdcard detected.
rhimezz said:
I backed up all partition (system, cashe, data, boot), wich ones has the efs?
If I restore the whole nandroid backup I still have the problem. No wi-fi or sdcard detected.
Click to expand...
Click to collapse
Efs has its own partition, its not related to system/cache/data/boot. Check your twrp folder and see if there's any EFS backup
Windslash31 said:
Efs has its own partition, its not related to system/cache/data/boot. Check your twrp folder and see if there's any EFS backup
Click to expand...
Click to collapse
I dont see any :/
{
"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"
}
I dont understand, I made a whole backup of everything
rhimezz said:
I dont see any :/
I dont understand, I made a whole backup of everything
Click to expand...
Click to collapse
There's no efs, try this method http://en.miui.com/thread-245598-1-1.html
Windslash31 said:
There's no efs, try this method http://en.miui.com/thread-245598-1-1.html
Click to expand...
Click to collapse
I tried to do that but in QPST my phone in disconnect/reconnecting all the time, its impossible to do anything. Seems like its a bug, latest posts in that thread there are some people with the same problem.
rhimezz said:
I tried to do that but in QPST my phone in disconnect/reconnecting all the time, its impossible to do anything. Seems like its a bug, latest posts in that thread there are some people with the same problem.
Click to expand...
Click to collapse
Do u have any friend with redmi note 3 and latest official twrp installed in his/her mobile.
sanjib734 said:
Do u have any friend with redmi note 3 and latest official twrp installed in his/her mobile.
Click to expand...
Click to collapse
I have a friend who is about to get his, but cant anyone of you backup your EFS and link it here?
deleted.
sanjib734 said:
If u have faith on me can pm me ur imei no printed on the box clearly mention sim 1 and sim2.
Click to expand...
Click to collapse
I have faith in you, but how will I restore it to my phone? With TWRP?
rhimezz said:
So I just tested out a marshmallow chinese beta rom for snapdragon, after I used it and tried to install google play store without success I just went back to TWRP, formatted back and installed by previous nandroid backup.
However when I booted in to my backup my SIM-card is not getting detected anymore and my wi-fi refuses to turn on....
Did I just brick it hard? Does anyone know how to repair this?
Click to expand...
Click to collapse
I have the same Problem im staying on mm because there the Baseband works but it's buggy as f*ck, on mm i made a qcn Backup with QPST but I can't restore it on 5.1 because there is the QPST Reconnecting bug
rhimezz said:
I have faith in you, but how will I restore it to my phone? With TWRP?
Click to expand...
Click to collapse
Yes with latest official TWRP.
I managed to fix everything following this guide:
http://en.miui.com/thread-260943-1-1.html
thank you everyone for trying to help anyway!
I seem to have not restored my MEID number and it seems important, I cant call.
I would really like help with this, I dont see any guides for redmi note 3 pro.
Related
So, last night I decided to update to one of the CM 10.1 nightlies. I haven't updated in a while and thought why the heck not? So I used the option built in the Settings app to update. I pressed download and waited for it to finish, then hit install and went to sleep while it installed. When I woke up I had no signal. Not even 2g. No calls, texts, data, you name it. Gone.
So I have spent at least 6 hours re installing old versions and scouring the internet and no one has an issue exactly like mine.
Here's a screenshot of what the settings look like:
{
"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 might be an obvious question but have you tried reflashing one of the available modems?
JBeXX said:
This might be an obvious question but have you tried reflashing one of the available modems?
Click to expand...
Click to collapse
Thanks for the quick reply. No I haven't tried that yet actually. I can't find anything on google. Could you point me in the direction to flashing a modem?
Lepryy said:
Thanks for the quick reply. No I haven't tried that yet actually. I can't find anything on google. Could you point me in the direction to flashing a modem?
Click to expand...
Click to collapse
Just flash in recovery. Probably best to use the newer which is the VRALL4. If this doesn't fix it you may want to try a clean flash with a full wipe.
http://forum.xda-developers.com/showthread.php?t=2108510
JBeXX said:
Just flash in recovery. Probably best to use the newer which is the VRALL4. If this doesn't fix it you may want to try a clean flash with a full wipe.
http://forum.xda-developers.com/showthread.php?t=2108510
Click to expand...
Click to collapse
Wait why would I use the VRALL4 and not the VRALLJB?
Lepryy said:
Wait why would I use the VRALL4 and not the VRALLJB?
Click to expand...
Click to collapse
It's the newer of the 2. It was part of the first vzw ota after release.
JBeXX said:
It's the newer of the 2. It was part of the first vzw ota after release.
Click to expand...
Click to collapse
Alright, here goes nothing. I'll post back the results.
JBeXX said:
It's the newer of the 2. It was part of the first vzw ota after release.
Click to expand...
Click to collapse
Umm. So it seems this update did a lot more than mess up my data. It completely wiped my Recovery and removed my Play Store completely. I have no way to even flash this modem.
Lepryy said:
Umm. So it seems this update did a lot more than mess up my data. It completely wiped my Recovery and removed my Play Store completely. I have no way to even flash this modem.
Click to expand...
Click to collapse
Very odd. What recovery were you using? I'm not on cm 10.1 so I'm not familiar with the updater but did it give you options to wipe any data or caches? And did you reflash gapps after updating?
If you can get a wifi connection you could always try and flash TWRP through the goo manager app. Just a thought.
JBeXX said:
Very odd. What recovery were you using? I'm not on cm 10.1 so I'm not familiar with the updater but did it give you options to wipe any data or caches? And did you reflash gapps after updating?
If you can get a wifi connection you could always try and flash TWRP through the goo manager app. Just a thought.
Click to expand...
Click to collapse
I get an error when using the goo manager app. It says no current recovery installed. I am seriously ****ing stuck. Just one harmless update has demolished all the stuff on my phone.
Lepryy said:
I get an error when using the goo manager app. It says no current recovery installed. I am seriously ****ing stuck. Just one harmless update has demolished all the stuff on my phone.
Click to expand...
Click to collapse
You should be able to install recovery from the goo app. Open the all, then hit menu, then install openrecoveryscript. Confirm and see if will flash it.
Had this problem many of times on a gs3.
Calm down, I may be able to help you.
In the settings picture you posted. The my phone number was out of sight.
If the spot said Unknown.
You may be in luck.
But anyways do this either way.
Make sure you back up any thing you don't want to lose.
Boot into download mode.
Flash a stock unrooted official version. I believe this will also flash the modems and radio as well.
Check your signal and phone settings now.
I would expect nothing has changed signal wise.
But if you still have problems you open up dialer and call this phone number
*2767*3855#
Now your phone will cook up some magic and everything will be like the day you opened the box
However if this does not work, I would consider a new sim card (free at Verizon), try and do some more research
Or accept the fact you may have a hardware problem.
Feel free to pm me to let me know how it goes.
God bless the American people.
ok the phone had booted
but if i restore the data on CWM i get fc
android.process.acore force closing
how i can fix this to take backup for my contacts
or i can do it another way by restoring it from the nandroid backup
sparxx4 said:
hii guys
i got S2 on my hand ,, i had flashed Siyah-s2-v6.0b4.tar with odin
it was on 4.0.3 stock ics ,, now the phone dont bootup ,, when it comes to the yellow tringle nothing happend after that
only black screen !!
i still can access recovery and download mode
what i miss here ??
Click to expand...
Click to collapse
do a factoru reset.of not,then re-flash firmware,and use stock kernel
i had flash this
http://forum.xda-developers.com/showthread.php?t=1286432
now i need to get the backup rom worked
it was a backup for 4.0.3 room
what kernel can run this rom ??
i didnt find a stock one with CWM
Siyah v6.0 for jellybean, if you still in ics rom download v4 or v5
http://www.gokhanmoral.com/
guys just to make it clear
a working 4.0.3 FW with cwm to restore only the data from the backup
thats what i need to do i think
any one can help me with the guied and the links
sparxx4 said:
what i miss here ??
Click to expand...
Click to collapse
What you're missing (Like many other n00bs) is the ability to read which seems to be replaced with the overwhelming urge to just blinding flash anything to their device and then afterwards create silly topics which could have been avoided by doing simple things like reading what a kernel supports.
{
"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"
}
READ BEFORE FLASH!!!!!!
Or at least don't come crying when/if you brick device
TheATHEiST said:
What you're missing (Like many other n00bs) is the ability to read which seems to be replaced with the overwhelming urge to just blinding flash anything to their device and then afterwards create silly topics which could have been avoided by doing simple things like reading what a kernel supports.
READ BEFORE FLASH!!!!!!
Or at least don't come crying when/if you brick device
Click to expand...
Click to collapse
your post totaly un usefull
i had read and i had 3 galaxy s2
2 of them i had do them ,, but 3 third one i forgot to make backup for contacts and i want them back
so i dont see any thing noob here
i made a mistake and looking for answers and you not doing this so just stay away of this thread pleas
sparxx4 said:
your post totaly un usefull
i had read and i had 3 galaxy s2
2 of them i had do them ,, but 3 third one i forgot to make backup for contacts and i want them back
so i dont see any thing noob here
i made a mistake and looking for answers and you not doing this so just stay away of this thread pleas
Click to expand...
Click to collapse
Ok, carry on flashing random/incompatible kernels/roms to your device and see what happens. I for one will have absolutely no sympathy for you whatsoever.
Enjoy!
i will end on bricked phone i think
dude im not a noob guy i just made a stupid mistake and looking for a way back
i think flashing a stock frimeware back will make the phone boot again ,, and sorry i dont had enough time for reading its not my phone its for my sister and i shud make it work before morning
mine is Xperia S so its diffrent world
Sent from the little guy
problem solved thanks to every one
the phone booted up
flashed the stock frimware
i will try things now to get the backup work now
gastonw said:
View attachment 2097451
Sent from the little guy
Click to expand...
Click to collapse
Another one of your pics robbed :thumbup:
But it's an awesome pic. It says so much.
Sent from the little guy
sparxx4 said:
the phone booted up
flashed the stock frimware
i will try things now to get the backup work now
Click to expand...
Click to collapse
It's a bootloop not a brick, why did you flash a ROM, just a compatible Kernel was able to save you...
sadekmefti said:
It's a bootloop not a brick, why did you flash a ROM, just a compatible Kernel was able to save you...
Click to expand...
Click to collapse
i tried sya v5 kernel wich shud be work with ICS but this didnt make it work
is there any other kernel i can try ?
after restore only the data from the nandroid backup
i get this
android.process.acore has stopped unexpectedly problem, force close
how i can fix it ??? if i did i will be able to take the contact backup
sparxx4 said:
after restore only the data from the nandroid backup
i get this
android.process.acore has stopped unexpectedly problem, force close
how i can fix it ??? if i did i will be able to take the contact backup
Click to expand...
Click to collapse
after restoring the nand bkp, reboot to recovery and then,
1)wipe cache/dalvik
2)fixpermissions under advance
3) reboot ur phone and see.
4) u should also ensure that ur on the same CWM recovery (the one used to make the bkp) while restoring the bkp, to avoid conflicts
Sun90 said:
after restoring the nand bkp, reboot to recovery and then,
1)wipe cache/dalvik
2)fixpermissions under advance
3) reboot ur phone and see.
4) u should also ensure that ur on the same CWM recovery (the one used to make the bkp) while restoring the bkp, to avoid conflicts
Click to expand...
Click to collapse
will try this and give feedback
i think i did it before but i still get the error android.process.acore force closing
any way i will do it again to make sure
sparxx4 said:
will try this and give feedback
i think i did it before but i still get the error android.process.acore force closing
any way i will do it again to make sure
Click to expand...
Click to collapse
u can also try re-flash the kernel (which was used to make the nand bkp) once and see
im afraid that when i did the backup the rom wasnt bootup !! im not sure
i will wait couple of hours until i get the phone back from my sister will keep you on contacts thank you for your help
MAC address's wifi and bluetooth, imei are here but I have reflashed stock rom but still no luck, any solutions?
kennguy said:
MAC address's wifi and bluetooth, imei are here but I have reflashed stock rom but still no luck, any solutions?
Click to expand...
Click to collapse
Have you tried flashing the att JB radio? (look for it in the general section there is thread with different radios(modems) you can try.
luisoman2000 said:
Have you tried flashing the att JB radio? (look for it in the general section there is thread with different radios(modems) you can try.
Click to expand...
Click to collapse
Hi mate, no luck, any solutions?
Are you 100% sure airplane mode is not activated? I know it sounds dumb but might be the reason if everything else seems working fine.
kennguy said:
Hi mate, no luck, any solutions?
Click to expand...
Click to collapse
If you have an EFS backup, you might want to restore it.
jimbo77 said:
Are you 100% sure airplane mode is not activated? I know it sounds dumb but might be the reason if everything else seems working fine.
Click to expand...
Click to collapse
Yes,,, airplane mode is off... wifi is strange. When I turn it on to scan wifi but wifi automatically switch off.
kennguy said:
Yes,,, airplane mode is off... wifi is strange. When I turn it on to scan wifi but wifi automatically switch off.
Click to expand...
Click to collapse
When you flashed back to stock, did you do it by CWM/TWRP or LGNPST?
I'd recommend LGNPST (made a backup of your internal sd, it will be wiped out) and see if the problem persist.
jimbo77 said:
When you flashed back to stock, did you do it by CWM/TWRP or LGNPST?
I'd recommend LGNPST (made a backup of your internal sd, it will be wiped out) and see if the problem persist.
Click to expand...
Click to collapse
I revert back to stock by this guide: http://forum.xda-developers.com/showthread.php?t=2668412
... but the problem persist... I think may be is a hardware problem...
kennguy said:
I revert back to stock by this guide: http://forum.xda-developers.com/showthread.php?t=2668412
... but the problem persist... I think may be is a hardware problem...
Click to expand...
Click to collapse
I'd say that only option should be to restore the EFS backup. You should have that when first unlocked bootloader with FreeGee
jimbo77 said:
I'd say that only option should be to restore the EFS backup. You should have that when first unlocked bootloader with FreeGee
Click to expand...
Click to collapse
But I did not backup EFS, any solutions except restoring EFS mate?
kennguy said:
But I did not backup EFS, any solutions except restoring EFS mate?
Click to expand...
Click to collapse
Well my only idea right now if for you to get a radio log from the phone and then share it to see if we can spot anything out of usual that might be affecting your phone's connectivity settings.
You can use this app to get the desired logs
http://forum.xda-developers.com/showthread.php?t=1123129
I'll recommend you to try to reproduce the steps so the app can capture the appropriate log, after that share what you get
jimbo77 said:
Well my only idea right now if for you to get a radio log from the phone and then share it to see if we can spot anything out of usual that might be affecting your phone's connectivity settings.
You can use this app to get the desired logs
http://forum.xda-developers.com/showthread.php?t=1123129
I'll recommend you to try to reproduce the steps so the app can capture the appropriate log, after that share what you get
Click to expand...
Click to collapse
OK, I'll send you the log later...but before that I got issue "HW was reset detected".
{
"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"
}
And I tried to back to stock rom then I got no wifi, bluetooth, signal but IMEI is not null. After that, I unlocked bootloader, flash recovery, tried to wipe data and got this issue:
kennguy said:
OK, I'll send you the log later...but before that I got issue "HW was reset detected".
View attachment 2689212
And I tried to back to stock rom then I got no wifi, bluetooth, signal but IMEI is not null. After that, I unlocked bootloader, flash recovery, tried to wipe data and got this issue:
View attachment 2689210
Click to expand...
Click to collapse
The first screen is due to a Kernel Crash, are you running a custom kernel on your phone? I've got that with a few custom Kernels and if that's the case then probably the kernel modules are not compatible with the phone software. Can you flash for example a custom KK Rom without a modified kernel to see if you get any connection?
Now for the second screenshot, my take is that you are using a MicroSD that is formatted as exFAT (Usually that's the format of 64GB cards) and the recovery does not have support for that kind of file system.
{
"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"
}
Here's a screenshot of what im getting after trying to unlock my rn4 with the unlock tool. What this mean? My bootloader unlocked already?
cant boot to recovery i can only see phone and connector icon..
Edit: I realize my bootloader is already unlocked and the thing missing is stock recovery. I installed TWRP and installed xiaomi.eu latest build.
Cheers
mcneil20 said:
Here's a screenshot of what im getting after trying to unlock my rn4 with the unlock tool. What this mean? My bootloader unlocked already?
cant boot to recovery i can only see phone and connector icon..
Cheers
Click to expand...
Click to collapse
What rom do you currently have installed? You must flash the china dev/beta rom, then make sure to enable the OEM unlock option. You then need to boot into fastboot, you should see the fastboot screen as on the phone in the vid below.
https://youtu.be/E-bWR-8EEYU?t=53
You can also log onto the i.mi.com site and log into your mi account and try to locate your device as in the video below.
https://youtu.be/SPyeQjbmQu8?t=55
gsmyth said:
What rom do you currently have installed? You must flash the china dev/beta rom, then make sure to enable the OEM unlock option. You then need to boot into fastboot, you should see the fastboot screen as on the phone in the vid below.
https://youtu.be/E-bWR-8EEYU?t=53
You can also log onto the i.mi.com site and log into your mi account and try to locate your device as in the video below.
https://youtu.be/SPyeQjbmQu8?t=55
Click to expand...
Click to collapse
Then i realize i need to be on china rom before unlocking is done.. *!^#&^&#$&(**$
Edit: Ill flash latest china dev later and hopefully later ill finish my 40gb backup -_-
mcneil20 said:
Then i realize i need to be on china rom before unlocking is done.. *!^#&^&#$&(**$
Edit: Ill flash latest china dev later and hopefully later ill finish my 40gb backup -_-
Click to expand...
Click to collapse
Yes it will wipe everything so definitely backup, i think you can use the built in mi backup to backup apps/some data, then backup that file to a pc.
Use the SP flash tool to flash the china dev rom and stay on this rom to carry out the bootloader unlock. Once unlocked you can then flash whatever you like or install twrp and again flash what you want, you will stay unlocked.
http://en.miui.com/thread-371349-1-1.html
gsmyth said:
Yes it will wipe everything so definitely backup, i think you can use the built in mi backup to backup apps/some data, then backup that file to a pc.
Use the SP flash tool to flash the china dev rom and stay on this rom to carry out the bootloader unlock. Once unlocked you can then flash whatever you like or install twrp and again flash what you want, you will stay unlocked.
http://en.miui.com/thread-371349-1-1.html
Click to expand...
Click to collapse
Helpful indeed! Thanks mate for the hand. Really appreciate it. Coming from S3 to RN4 is a bit hard as i dont get this problems xD
gsmyth said:
Yes it will wipe everything so definitely backup, i think you can use the built in mi backup to backup apps/some data, then backup that file to a pc.
Use the SP flash tool to flash the china dev rom and stay on this rom to carry out the bootloader unlock. Once unlocked you can then flash whatever you like or install twrp and again flash what you want, you will stay unlocked.
http://en.miui.com/thread-371349-1-1.html
Click to expand...
Click to collapse
Yep exactly what he said, btw the Mi Mover app (available from Play Store & install on both devices) works both ways so old phone - new phone & vice versa so you can use that or the MIUI backup.
http://forum.xda-developers.com/redmi-note-4/how-to/creating-backup-using-inbuilt-miui-t3512380
Either way you need to do it achieves the same thing.
Sent from my Redmi Note 4 using Tapatalk
Wilderone said:
Yep exactly what he said, btw the Mi Mover app (available from Play Store & install on both devices) works both ways so old phone - new phone & vice versa so you can use that or the MIUI backup.
http://forum.xda-developers.com/redmi-note-4/how-to/creating-backup-using-inbuilt-miui-t3512380
Either way you need to do it achieves the same thing.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Will update tomorrow and hopefully i finally get what i want xD Currently downloading the tgz file @400-900kbps -_-
UPDATE: I've successfully installed TWRP, SuperSU and Latest build by XIOMI.eu. I'm reinstalling backup and so far my verdict is great! Ram consumption decrease and its more faster than before i think I'll try to install Xposed later this day..
mcneil20 said:
UPDATE: I've successfully installed TWRP, SuperSU and Latest build by XIOMI.eu. I'm reinstalling backup and so far my verdict is great! Ram consumption decrease and its more faster than before i think I'll try to install Xposed later this day..
Click to expand...
Click to collapse
Nice one, glad to hear you got sorted! :good:
I had the same issue. Got to know that it was already unlocked by default (how come?)
The best place tout have latest rom/version of any xiaomi devices global/China developer/stable ?
Hi Team, I Need help with unbricking my device. I'm in a panic state. I had already unblocked my bootloader and downgraded to Oxygen OS 11.3 via MtkClient.
For some weird reason it stuck to bootloader animation and I flashed ROM files again via MTKClient, but it was still on the bootloader screen. Then I thought of flashing preloader files from the backup preloader files I saved before via MTKclient. Now it seems like I have bricked my device. Nothing is showing up.
This is my first post on this forum, Please help me out.
Thanks and apologies for breaking any forum rules.
It seems to be not charging ( I can't tell if it's charging when I'm using my regular charge adapter) and now it's not even showing up on MTKClient.
Hi, First question do you have a warranty?
Kabbutino said:
Hi, First question do you have a warranty?
Click to expand...
Click to collapse
No, this device issues issued for official work :-(
thecreat0rnew said:
Hi Team, I Need help with unbricking my device. I'm in a panic state. I had already unblocked my bootloader and downgraded to Oxygen OS 11.3 via MtkClient.
For some weird reason it stuck to bootloader animation and I flashed ROM files again via MTKClient, but it was still on the bootloader screen. Then I thought of flashing preloader files from the backup preloader files I saved before via MTKclient. Now it seems like I have bricked my device. Nothing is showing up.
This is my first post on this forum, Please help me out.
Thanks and apologies for breaking any forum rules.
Click to expand...
Click to collapse
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
thecreat0rnew said:
No, this device issues issued for official work :-(
Click to expand...
Click to collapse
Yeah, obviously
When you buy your phone?
thecreat0rnew said:
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
Click to expand...
Click to collapse
If you have a backup with mtkclient you can restore that
Kabbutino said:
If you have a backup with mtkclient you can restore that
Click to expand...
Click to collapse
But for some weird reason, MTKclient is unable to detect my device after the bootloader flash operation. Is there any further troubleshoot option to see battery percentage etc or some other operation?
thecreat0rnew said:
PS: I also have backups of all partitions including the bootloader in a separate folder created via MTKClient. I hope the device is recoverable given its bootloader is unlocked but I'm worried that It's now not detected in MTKclient not sure if the charge is depleted and charming a device is not possible without valid bootloader???
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"
}
Above are the files from Preloader backup operation from MTKclient. What file I should flash to fix preloader?
thecreat0rnew said:
But for some weird reason, MTKclient is unable to detect my device after the bootloader flash operation. Is there any further troubleshoot option to see battery percentage etc or some other operation?
Click to expand...
Click to collapse
Can you flash other backup of oos 11.3 and unlock the bootloader?
Kabbutino said:
Can you flash other backup of oos 11.3 and unlock the bootloader?
Click to expand...
Click to collapse
Again, I can but MTKclient doesn't detect my device anymore after pressing Volume +- Plus I don't thin flashing other partition backup would solve the issue cause all of this started to occur as I flashed preloader from the backup files
Can you send the log of mtkclient?
Kabbutino said:
Can you send the log of mtkclient?
Click to expand...
Click to collapse
There is nothing showing up on logs as well. Is it possible due to empty battery it's unable to go into bootrom mode? Below is the logs I was getting after flashing preloader and trying to launch MTKclient.
F
thecreat0rnew said:
There is nothing showing up on logs as well. Is it possible due to empty battery it's unable to go into bootrom mode? Below is the logs I was getting after flashing preloader and trying to launch MTKclient. View attachment 5878273
Click to expand...
Click to collapse
Why do you flash preloader?
And which os do you use?
Kabbutino said:
And which os do you use?
Click to expand...
Click to collapse
Oxygen OS 11.3, I thought the preloader is the issue where I was stuck in boot animation. I think the mobile was not charged enough and hence it got corrupted.
Is there any way to charge the device now?
Do you see the bootanimation of oneplus and the unlock bootloader message
Kabbutino said:
Do you see the bootanimation of oneplus and the unlock bootloader message
Click to expand...
Click to collapse
As of now, nothing is showing up. It's just a black screen.
I was able to get MTKClient to work after the one-plus animation screen.