Develop Bugs

[Q] Error When booting up phone

Hey,
Ill explain where i was when this happened, to give everyone a better overview of the problem so someone may be able to help me more efficiently.
Been using phone for a while since it had some out, without rooting and messing around with anything and using pc companion to update firmware and bits,
2 Days ago i saw a nice theme on the arc forums so i thought, i like that and im going to install it, so i downgraded to 2.3.2 using x10 flasher then rooted with gingerbreak, updated to 2.3.3 using ota to keep root.
I started to install bits a pieces of the theme, using a root explorer, changing permissions to rw--r--r on all of the files to make them work.
It was going swimmingly, status bar changed, applications changed (Sms, Settings, Clock) those sorts of things, and then when it came to putting
SemcGenericUxpRes.apk
&
framework-res.apk
into the correct place on the phone,
/system/framework
i did the first one and it worked perfectly, rebooted itself without me pressing anything but i thought that may be normal for sony erricsson androids as i know their systems are different to the basics you get with a htc android phone.
then i put framework-res.apk into the same folder and again it started to reboot itself and i thought, great its all done and will look amazing.
The Sony Erricsson writing appeared, and then starts to bootloop, so now im thinking oh, s##t.
So i pulled the battery and left if for 10 miniutes and put it back in, no joy.
I now go back to using the x10 flasher to reinstall 2.3.2 but i get an error saying that ive not enabled usb debugging, and i probably hadnt as i had only just reinstalled 2.3.3. so i disconnect my phone and try to turn it on. no joy again
Plugged it back in on the off chance it may just have been an slight bug and tried to flash again, this time it started flashing all the bits as it does and then half way through the process it says, Error! Usb debugging not activated, disconnect phone and turn it on.
So this time when i try to turn my phone on, all i get is a Picture of a phone with an Exclamation mark above it, im assuming because the software has corrupted on the install as its only done half of it.
So here is my problem, i cant turn my phone on to get usb debugging on.
I can get into fastboot mode, blue light, holding search and plugging usb in, but dont know where to go from there.
Any Help will be much appreciated.
Many Thanks.
Shotgunfool

The message in flashtool is generic, it just tells you to enable those things when flashtool is done. It will state this wether you encounter an error or not . It shouldn't matter wether they're enabled or not for flashtool to work and flash your phone.
You might try to use SEUS to restore your phone, if i remember correctly a few others has had this problem and resolved it that way.
You might also try to flash the rooted system.img through fastboot.
Next time you mod your phone with rootexplorer just move all apk's/jar files to /system first and then set the permissions and then move them to /system/framework and /system/app this will prevent a bootloop. I learned the hard way aswell, but then again i learned to use flashtool.
Regards Dousan...

Dousan said:
The message in flashtool is generic, it just tells you to enable those things when flashtool is done. It will state this wether you encounter an error or not . It shouldn't matter wether they're enabled or not for flashtool to work and flash your phone.
You might try to use SEUS to restore your phone, if i remember correctly a few others has had this problem and resolved it that way.
You might also try to flash the rooted system.img through fastboot.
Next time you mod your phone with rootexplorer just move all apk's/jar files to /system first and then set the permissions and then move them to /system/framework and /system/app this will prevent a bootloop. I learned the hard way aswell, but then again i learned to use flashtool.
Regards Dousan...
Click to expand...
Click to collapse
When you say flash the rooted system image through fastboot, how do i go about using fastboot to flash an image?
Cheers
Shotgunfool

shotgunfool said:
When you say flash the rooted system image through fastboot, how do i go about using fastboot to flash an image?
Cheers
Shotgunfool
Click to expand...
Click to collapse
Check this link out (i'm asuming you've unlocked your bootloader. If not you might read up on pros and cons before doing so, if doing so at all):
http://forum.xda-developers.com/showthread.php?t=1043630
Regards Dousan...
If you haven't got an unlocked BL i would first try out SEUS or flashtool again

Dousan said:
Check this link out (i'm asuming you've unlocked your bootloader. If not you might read up on pros and cons before doing so, if doing so at all):
http://forum.xda-developers.com/showthread.php?t=1043630
Regards Dousan...
If you haven't got an unlocked BL i would first try out SEUS or flashtool again
Click to expand...
Click to collapse
I dont have an unlocked bootloader, as i didnt think i needed one to change themes,
when you say SEUS, do you mean Pc Companion?
and just tried flashtool again, same error

shotgunfool said:
I dont have an unlocked bootloader, as i didnt think i needed one to change themes,
when you say SEUS, do you mean Pc Companion?
and just tried flashtool again, same error
Click to expand...
Click to collapse
Nah SEUS is another tool like Pc Companion . Check out this link, the only one i could find:
e: seems that SE has taken it of their own site as the link, linked to SE's homepage and can not be found. Must be another link somewhere floating around?
You're right you don't need an unlocked BL for theming and it's weird you get that error while flashing.
Regards Dousan...

Dousan said:
Nah SEUS is another tool like Pc Companion . Check out this link, the only one i could find:
e: seems that SE has taken it of their own site as the link, linked to SE's homepage and can not be found. Must be another link somewhere floating around?
You're right you don't need an unlocked BL for theming and it's weird you get that error while flashing.
Regards Dousan...
Click to expand...
Click to collapse
Ive followed the previous link that describes unlocking the bl and flashing a rooted image, ive unlocked the bootloader, just got 2 miniutes left of the download of the custom image, so ill let you know if that works.
Thanks for your help Dousan

No Luck, im getting this error when trying to flash the modded image
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot flash system play_modded.img
sending 'system' (236189 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 667.320s
Any idea?

shotgunfool said:
No Luck, im getting this error when trying to flash the modded image
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot flash system play_modded.img
sending 'system' (236189 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 667.320s
Any idea?
Click to expand...
Click to collapse
Did you put the play_modded,img in fastboot folder?
Regards Dousan...

Dousan said:
Did you put the play_modded,img in fastboot folder?
Regards Dousan...
Click to expand...
Click to collapse
Yes,
and just got a copy of seus, and it says cannot update phone contains modified software.
This is because i removed aload of the bloat when i was rooted.

shotgunfool said:
Yes,
and just got a copy of seus, and it says cannot update phone contains modified software.
This is because i removed aload of the bloat when i was rooted.
Click to expand...
Click to collapse
Hhhmm there should be a choise to repair only in SEUS?
Regards Dousan...

Dousan said:
Hhhmm there should be a choise to repair only in SEUS?
Regards Dousan...
Click to expand...
Click to collapse
It doesnt get that far does it, it checks the current firmware before allowing you to choose whether or not you want to update/repair

shotgunfool said:
It doesnt get that far does it, it checks the current firmware before allowing you to choose whether or not you want to update/repair
Click to expand...
Click to collapse
I've google the error and a few people seems to have had it to. There's no rel fix to it as far as i can read, more like suggestions.
Try another usb cable. Try another usb port on the pc. Try it on another pc.
Ohh didn't know about SEUS haven't used it my self.
Regards Dousan.

Dousan said:
I've google the error and a few people seems to have had it to. There's no rel fix to it as far as i can read, more like suggestions.
Try another usb cable. Try another usb port on the pc. Try it on another pc.
Ohh didn't know about SEUS haven't used it my self.
Regards Dousan.
Click to expand...
Click to collapse
Thanks for the help but nothing has worked,
if anyone has any other suggestions i would greatly appreciate the help.
Many Thanks
Shotgunfool

shotgunfool said:
Thanks for the help but nothing has worked,
if anyone has any other suggestions i would greatly appreciate the help.
Many Thanks
Shotgunfool
Click to expand...
Click to collapse
You could try this:
fastboot erase cache
Regards Dousan...
e: I've googled some more and it seems that it's kind of random and most people get it resolved some how. Trying flashing over and over, waiting till the next day, using a usb cable with ferrit (absolutely no idea what that is), changing usb port, changing cable, changing machine, changing OS etc.
It might be that the file it's sending is to big to handle somehow.
Maybe try to find bin4ry's trhead in the dev section on how to boot CWM (ClockWorkMod) and from there restore your phone with zerojay's rom. It's a flashable .zip to flash from CWM. That might work if it's about the size being send when flashig/sending/booting from fastboot.

Dousan said:
You could try this:
fastboot erase cache
Regards Dousan...
e: I've googled some more and it seems that it's kind of random and most people get it resolved some how. Trying flashing over and over, waiting till the next day, using a usb cable with ferrit (absolutely no idea what that is), changing usb port, changing cable, changing machine, changing OS etc.
It might be that the file it's sending is to big to handle somehow.
Maybe try to find bin4ry's trhead in the dev section on how to boot CWM (ClockWorkMod) and from there restore your phone with zerojay's rom. It's a flashable .zip to flash from CWM. That might work if it's about the size being send when flashig/sending/booting from fastboot.
Click to expand...
Click to collapse
I get this when trying to erase cache
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot erase cache
erasing 'cache'...
(bootloader) Erase of partition 'cache' requested
FAILED (remote: Partition not found, or permission denied)
finished. total time: -0.000s
when trying to boot CWM it just hangs on
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
and then when i disconnect the usb i get
Code:
FAILED (data transfer failure (Too many links))
finished. total time: 78.086s
Any other ideas?
Thanks, Shotgunfool

I'm out of ideas, but i see that you disconnected the phone after 78 secs when booting the CWM image. I've heard it could take a few min. to boot into. So I would try agian and let it 'hang' for atleast 2-3 min.
If nothing comes out of it i would pm Bin4ry or Alejandrissimo or Blagus for help as i think they would know alot more and they've might encountered this error before. and know how to solvd it?
Regards Dousan...
e: the last code snip you stated seems to point at the fact it's not sending or able to send anything through your usb to your phone for som reason. That error comes up while it's plugged in and while it's unplugged. It might be a drivers problem. Try to reinstall the drivers that came with the fastboot package again. I could be something in your windows settings that's preventing it from working correctly?

Dousan said:
I'm out of ideas, but i see that you disconnected the phone after 78 secs when booting the CWM image. I've heard it could take a few min. to boot into. So I would try agian and let it 'hang' for atleast 2-3 min.
If nothing comes out of it i would pm Bin4ry or Alejandrissimo or Blagus for help as i think they would know alot more and they've might encountered this error before. and know how to solvd it?
Regards Dousan...
e: the last code snip you stated seems to point at the fact it's not sending or able to send anything through your usb to your phone for som reason. That error comes up while it's plugged in and while it's unplugged. It might be a drivers problem. Try to reinstall the drivers that came with the fastboot package again. I could be something in your windows settings that's preventing it from working correctly?
Click to expand...
Click to collapse
Im getting closer, just got CWM Up and running, and i knew it shouldnt have taken long to put the image on my phone, i have a fast pc
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
(bootloader) USB download speed was 129134kB/s
OKAY [ 0.530s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ -0.000s]
finished. total time: 0.530s
lol
im pretty sure thats an error on fastboots part thats a lot of kbs
Although, ive found the weirdest fix to it hanging on sending 'boot'
and you probably wont believe me, but i was just about to go and try another pc so i plugged in my memory stick and as soon as i did, it sent it immediatly, so i have no idea, why, how, but that works
just downloading a rom to flash and fingers crossed it'll work

That's really good to hear, hope it works out this way
About the the fastboot error you refer to, it's all abaout Bits and Bytes - kB and kb and there's a huge difference between them and it's something like 8 times the difference as in 8kB is 1kb. I saw someone explain it somewhere on xda (might've been here in the play forum), that providers use it for misleading costumors to believe they get a much faster internet connection and such
Regards Dousan...

Hey, ive sent you a pm

unbrick Nokia 3.2

Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!

After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!

page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.

HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!

page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.

Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?

Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.

Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.

page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!

@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now

Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader

I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!

Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?

Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.

Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them

hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much

thanks so much i was able to put my phone back to life. i had almost given up.

smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.

damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.

I Locked my Redmi 7

Hello guys, last night bought a redmi 7. But this i check this cell phone and the MIUI LOCK is unlocked.
I had a brilliant idea to block using adb. And i destroy the system.
I tryed MI PC Suite, I Tryed mi flash is faild(remoite: Update sparse crc list failed), I Tryed in adb fastboot oem unlock, i tryed mi flash unlock and I was unsuccessful.
Did i throw my money in the trash?:crying:

You mean MIUI (System ROM) is gone?

Yes.
The message in Main Menu is ""this miui version can't be installed on this device !

I think you have to flash TWRP in ADB Mode (Volume - and Power button). And in TWRP, connect USB to "computer" then copy MIUI stock rom to SD Card or Internal. Hope it helps.

H3XUS said:
I think you have to flash TWRP in ADB Mode (Volume - and Power button). And in TWRP, connect USB to "computer" then copy MIUI stock rom to SD Card or Internal. Hope it helps.
Click to expand...
Click to collapse
Thank you guy, but i don't have any idea how to install TWRP in my cell phone. I tryed but have a error:
fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
erasing 'recovery'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.006s
Can you help me ?

Please, Help !!!

Mr.Nexus said:
Yes.
The message in Main Menu is ""this miui version can't be installed on this device !
Click to expand...
Click to collapse
Maybe the rom is not for redmi 7, check this and try search a rom for the phone.
I buy a redmi 7 root and later i unroot..... the phone had acount of miui and block my new phone, i erase all operative system and installed Twrp (not all Twrp work on this device)
If your phone doesnt work whith miui, try another rom like a Pixel and ¿Aoex?

ericklawliet said:
Maybe the rom is not for redmi 7, check this and try search a rom for the phone.
I buy a redmi 7 root and later i unroot..... the phone had acount of miui and block my new phone, i erase all operative system and installed Twrp (not all Twrp work on this device)
If your phone doesnt work whith miui, try another rom like a Pixel and ¿Aoex?
Click to expand...
Click to collapse
Guy, I tried to use multiple versions of MIUI. But to no avail.
As I understand it, I need an authorized xiaomi account.
I particularly lost the money. In the past, changing the rom on xiaomi devices was an easy thing, today if there is some kind of problem in the most serious system, you practically lose the device.

Stuck at boot screen after trying to restart my device, don't want to lose data

Hey there, so I was playing a game PubG in which in the middle of a match the screen got stuck. I waited for 10 mins for it to go back and tried locking the screen with power button but nothing happened. When I long pressed it closed for a second then restarted and got stuck on bootscreen with only mi logo and no animation. Now it isn't switching off it gets rebooted to the same screen again. Only fastboot is opening. I don't want to lose my personal data there photos, videos that includes all my college life. If I try to flash it I think I will lose all data. Also I didnt backup all the data on mi cloud or anywhere. Please help me.
Also in flashing if I select the option 'save user data' will my data be saved?

same issue
same issue
happened to me just now
should be common software/update issue

Is your bootloader unlocked?
If you only want to back up your music, photos,videos,documents etc. , flash twrp recovery then boot into it (power+vol up about 11s). Connect your phone to PC. Then copy all data you need to save. Then reboot to fastboot and do a clean flash (clean all).
If you either want to back up the application data, do the previous operation without flashing first, and then do a "dirty" flash (save user data). At this time, your phone should be able to boot, use the BACKUP app to back up all your application data and copy it to your computer. The backup file seems to be stored in /storage/emulated/ 0/MIUI/backup, I don't remember it well.
After backing up all data you needed to save, you'd better do a clean flash using fastboot method. Make sure you choose "clean all".

Yuki1001 said:
Is your bootloader unlocked?
If you only want to back up your music, photos,videos,documents etc. , flash twrp recovery then boot into it (power+vol up about 11s). Connect your phone to PC. Then copy all data you need to save. Then reboot to fastboot and do a clean flash (clean all).
If you either want to back up the application data, do the previous operation without flashing first, and then do a "dirty" flash (save user data). At this time, your phone should be able to boot, use the BACKUP app to back up all your application data and copy it to your computer. The backup file seems to be stored in /storage/emulated/ 0/MIUI/backup, I don't remember it well.
After backing up all data you needed to save, you'd better do a clean flash using fastboot method. Make sure you choose "clean all".
Click to expand...
Click to collapse
Thanks for replyling. I think my bootloader is not unlocked. Also power+vol up is not working, only power+vol down is working. Can I flash twrp with bootloader locked?

Arun pm said:
same issue
happened to me just now
should be common software/update issue
Click to expand...
Click to collapse
So what did you do? Please tell me the method if you were able to solve it.

Re: Prakharpathak
I'm sorry because I can't save a phone that have a locked bootloader. If you wish to try Qualcomm QDLoader9008, maybe it will not work. Xiaomi has locked the 9008 port for their phones. Unless you have an authorized Mi account to get the verify token and send the authentitation tag to your phone, or the phone will reject all flashing commands. QPST is not working. The only difference is that the bootloader can be unlocked, but the 9008 requires authorization every time.
If you want to try the force unlock bootloader tool, once the force unlock is successful, you will lose all your data. Unless you can erase the recovery partition before the bootloader send a wipe command to Mi-recovery. In other words, if the recovery partition is erased or the recovery is not stock recovery (like twrp, etc) , unlocking the bootoader will not lose any data. Twrp does not accept the wipe command from the bootloader.
[edit]Now we have working firehose programmer could be used. Use QFIL to dump your userdata.

Yuki1001 said:
Re: Prakharpathak
I'm sorry because I can't save a phone that have a locked bootloader. If you wish to try Qualcomm QDLoader9008, maybe it will not work. Xiaomi has locked the 9008 port for their phones. Unless you have an authorized Mi account to get the verify token and send the authentitation tag to your phone, or the phone will reject all flashing commands. QPST is not working. The only difference is that the bootloader can be unlocked, but the 9008 requires authorization every time.
If you want to try the force unlock bootloader tool, once the force unlock is successful, you will lose all your data. Unless you can erase the recovery partition before the bootloader send a wipe command to Mi-recovery. In other words, if the recovery partition is erased or the recovery is not stock recovery (like twrp, etc) , unlocking the bootoader will not lose any data. Twrp does not accept the wipe command from the bootloader.
Click to expand...
Click to collapse
my bootloader is locked but i am ready to lose all my data , can you please tell me how can i boot my device

Re: @jagannath287
If this is also useful for you @Prakharpathak , you can also try.
If you are ready to lose all your data, you can try to use Mi PC Suite. Offical link of MI PC SUITE:
http://pcsuite.mi.com
You must be able to boot into Mi-Recovery, otherwise my solution will not help you.
Download the recovery ROM for your phone. Note that you can't upgrade or downgrade the OS version using this method.
After downloading and installing the Mi PC Assistant application on your computer, run it and login to your MI account. Then select FLASH ROM section and connect your device to your PC. Make sure your device is booted into Mi-recovery and selected “Connect with MiAssistant”.
Warning: you can't downgrade/change ROM region (you can only install the same area version to your phone, like MI-MI, RU-RU, EEA-EEA, etc) using this method.
Make a full wipe for your phone and select the RECOVERY ROM package: fast update and agree with full wipe. Then wait for the data erasing is fully done. After you see “Checking zip file update” and if all ok, the flashing progress will start and you will see the flashing is in progress. At last, you will see the window with successfully flashing. In theory, the phone will reboot to system automatically. The first start will take about 10 minutes. Be patient and wait the welcome screen.
There is another MI PC SUITE version that I found and I attach with my post. There is also a XiaomiADB flashing program.
Alternative method:
Download the adb driver and install it on your computer. Use the XiaomiADB full-auto flash program to flash your phone.
Select “Connect with MIAssistant” in the recovery and connect the phone to PC.
Make sure the recovery ROM zip file and XiaomiADB flashing program that in same folder. For start flashing just HOLD zip ROM AND DRUG IT TO THE XiaomiADB. After this command your DATA will be reset! You lost all files and Settings on your device.
At last, I suggest you to unlock the bootloader for your phone as soon as possible and flash your phone using MiFlash in fastboot mode in order to avoid facing mysterious bugs. A phone that have an unlocked bootloader is easy to save (unbrick) or backup all data from the phone without booting into system.
Attachment:
1.XiaomiADB:
https://drive.google.com/open?id=1BIlCd5wFFFlU2ObIQ-AtBNp3jlSj_5L1
2.MI PC SUITE 4.0 Beta:
https://drive.google.com/open?id=1_QoNlQFVj7lPo5iqM8jdrNmRwPztHQbV
If you find it useful, please click thanks.

I have an unlocked bootloader with latest stock rom
Stuck at MI logo
>No stock recovery loading
>Unfortunately the usb debugging is off (Automatically by MI security app :crying
>Tried Mi flash, Fastboot, Qualcomm Qflash with test point connection
>Is there anything left to try
Thanks

Re: @Arun pm
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
Can your phone boots into fastboot?
Did you try to flash every partition manually?
Did you try to flash the oldest version--V9.5.19?
More information needed. It can save time and guesswork.

Yuki1001 said:
Re: @Arun pm
Thanks for the reply bro
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
>> tried failed; stuck at the twrp logo(tried multiple versions and built)
Can your phone boots into fastboot? :
>>yes, but cant flash, permission error (usb debugging is off)
Did you try to flash every partition manually?
>>yes, even tried it with qualcomm tools but failed
Did you try to flash the oldest version--V9.5.19?
>>yes : same
More information needed. It can save time and guesswork.
Click to expand...
Click to collapse
Thanks for the reply bro
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
>> tried failed; stuck at the twrp logo(tried multiple versions and built)
Can your phone boots into fastboot? :
>>yes, but cant flash, permission error (usb debugging is off)
Did you try to flash every partition manually?
>>yes, even tried it with qualcomm tools but failed
Did you try to flash the oldest version--V9.5.19?
>>yes : same
More information needed. It can save time and guesswork.

Re: @Arun pm
You'd better create a new thread otherwise we will disturb the original author of this thread (Prakharpathak).
Did you mean the returned message from your phone is like this:
Sending "recovery"...
OKAY. Total time: 4.016s
Writing "recovery"...
FAILED<remote: Permission Error>
finished. Total time: 4.016s
In theory, the fastboot won't return this message and the USB debugging switch has no relation with fastboot flashing.
All partitions can't be flashed and return the "permission error" message?
Can you take a photo of the flashing error message?
[edit] Now we have working programmer and you could do all you want via EDL.

Yuki1001 said:
Re: @Arun pm
You'd better create a new thread otherwise we will disturb the original author of this thread (Prakharpathak).
Did you mean the returned message from your phone is like this:
Sending "recovery"...
OKAY. Total time: 4.016s
Writing "recovery"...
FAILED<remote: Permission Error>
finished. Total time: 4.016s
In theory, the fastboot won't return this message and the USB debugging switch has no relation with fastboot flashing.
All partitions can't be flashed and return the "permission error" message?
Can you take a photo of the flashing error message?
Click to expand...
Click to collapse
I am currently facing a similar situation.
My device redmi note 5 pro was running on miui 11 and suddenly its screen froze and then it got restarted and stuck at mi logo. It has locked bootloader and I can't access the stock recovery but I can access fastboot mode. I tried flashing different miui versions with different flash tools and everytime the process starts then after 9 seconds I get the error "ack count doesn't match". I tried flashing with edl point method as well and with a patched firehose file to bypass mi authentication but still got the same error. Can you please help me? I searched around the net and I can't find anything related to this particular error I am getting. I would really appreciate if you can help.

oh god same issue its not booting, checked with service centre not able to update software, one of the mobile shop guy told that mobile mother board working fine but unable to locate software so that it can boot, now i am blank and helpless can you guys help me out please.. if people in chennai here let me know guys.. its been 5 th day without my mobile...

Hi,
I got similar issue. I had installed GFX tool for cod on redmi note 5 pro and got hang on call of duty mobile. After long press power button, got stuck at mi boot logo. Only able to do connect phone in fastboot to PC. Anybody found solution? I want to back up all data excluding apps. Kindly suggest working solutions.

Deep3004 said:
Hi,
I got similar issue. I had installed GFX tool for cod on redmi note 5 pro and got hang on call of duty mobile. After long press power button, got stuck at mi boot logo. Only able to do connect phone in fastboot to PC. Anybody found solution? I want to back up all data excluding apps. Kindly suggest working solutions.
Click to expand...
Click to collapse
Flash orangefox recovery, then boot to recovery and there you can disable all the apps you want

kadyt said:
Flash orangefox recovery, then boot to recovery and there you can disable all the apps you want
Click to expand...
Click to collapse
Thanks for reply.
I tried to flash orange fox recovery but bootloader is locked and no fastboot commands working. I have tried mi unlock flash tool to unlock bootloader but error is comming "couldn't unlock more devices by this account this month" on official tool and on unofficial tool error is "current account is not bounded to this device". I cannot add device to this account since phone is into bootloop and wanted to save data. Is there any way to unlock bootloader and get access to storage data?

Deep3004 said:
Thanks for reply.
I tried to flash orange fox recovery but bootloader is locked and no fastboot commands working. I have tried mi unlock flash tool to unlock bootloader but error is comming "couldn't unlock more devices by this account this month" on official tool and on unofficial tool error is "current account is not bounded to this device". I cannot add device to this account since phone is into bootloop and wanted to save data. Is there any way to unlock bootloader and get access to storage data?
Click to expand...
Click to collapse
Sorry I took for granted that you had the bootloader unlocked. Then I don't know. Hope someone else can help you
Anyway, if somehow you could unlock the bootloader now, as far as I know, you will lose your data when doing it

any development in the above event i am in the same stage

[GUIDE][UPDATED] Unlocking JioFi 3 JMR540 & JMR541 for all networks

Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
​I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
UPDATE 17-10-21: Jio pushed a firmware update which is locking boot loader. If your device is not updated yet it is advised to re-flash your firmware with patched image given below which basically disables auto updates. If you're already locked out, currently there's no easy fix for that.
If you haven't used your device from a long time or you're still on lower or equal version than below it is advised not to use JioFi with SIM, flash this firmware first if you want to test SIM unlock.
Guide
Make sure you're on same or lower firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_patched_system.zip​
JMR541_unlocked_patched_system.zip​
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)​
Install Fastboot ( google it for mac and linux it's easy to find)​
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.​
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip​
JMR_541_original_system.zip​
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
fastboot erase recoveryfs
fastboot flash recoveryfs "D:\system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
.
Q. I 'accidentally' flashed my recovery and boot partition
A. Well accidentally I've backed up recovery and boot download from below
1. JMR540_boot_recovery.rar
2. JMR541_boot_recovery.rar
.
Q. FAILED: (remote: Image is locked) issue while erasing/flashing image
A. Jio recently pushed an firmware update which re-locks simlock and bootloader which basically means you can't flash unsigned/custom firmware. Currently there is no fix.
​
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
What about JioFi 2, 4, 5, 6?
Reverse Engineering takes lot of time and coffee. Until I get physical access to device I won't be able to unlock it. I'm constantly searching them on OLX as soon as I get hands on I'll surely try to RE and unlock it. I'll update the same here if there is no update here at the time of your reading then I haven't got the device yet so please don't spam for update hope you understand that I don't get anything by doing these things, I do it for liberation of locked hardware to meet it's real destiny and of course for the people. I also have a day job so no I cannot guide or teach you, hope you understand why.
For Devs:
JMR_540_FLASH_DUMP.rar
​

Reserved

successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.

sksinha said:
successfully unlocked my jiofi 3 JMR541. tested with voda and its working well and good. Thanks a ton for this bro.
I was late in checking this thread and got shipped airtel unlocked mifi from home.
Click to expand...
Click to collapse
Can you show us dashboard screenshot. This will help other users to verify

abhimortal6 said:
Can you show us dashboard screenshot. This will help other users to verify
Click to expand...
Click to collapse
...

Nice, enjoy!

abhimortal6 said:
Nice, enjoy!
Click to expand...
Click to collapse
bro is unlocking more 4g bands or manual selection of bands can be done ?

sksinha said:
bro is unlocking more 4g bands or manual selection of bands can be done ?
Click to expand...
Click to collapse
Totally possible even 3G but it can't be done through WebUI it'll requires shell access.

Totally working! thanks a ton a bro <3

srbhsngwn said:
Totally working! thanks a ton a bro <3
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"
}

Great

..

myapky said:
JMR540 ERROR
Click to expand...
Click to collapse
you haven't properly specified the address of system.img Please give the complete path

srbhsngwn said:
you haven't properly specified the address of system.img Please give the complete path
Click to expand...
Click to collapse
Fixed issue.

myapky said:
there is a issue with JMR540, however I have successfully flashed JMR541 file on friends JioFi 3.
There is definitely a issue with JMR540 system.img file. request @abhimortal6 to check the file and reupload.
I have added a device info details for JMR540
Click to expand...
Click to collapse
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.

abhimortal6 said:
This issue is not related to flash file as I own JMR 540 and it's been tested on multiple devices (refer attached image). "Not working" and "Not flashing" are two different things.
"flash write error" is a sign of bad emmc/nand, bad partition table can also be the cause. Please first try with original firmware and collect information by different permutations (re-downloading image, erasing system before flashing etc) before spamming.
View attachment 5326935
Click to expand...
Click to collapse
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?

myapky said:
I am not spamming i am facing issue so I mentioned at XDA. I am facing 'flash write error' with the original system.img file too. Unable to flash img files.. Any solution to that ?
Click to expand...
Click to collapse
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"

abhimortal6 said:
A single post with all the details in it would be sufficient.
As stated in previous post please try the following.
Try flashing original firmware first
Try erasing system partition ( fastboot erase system)
Try re downloading image
If you're getting flash write error in original firmware too then you're nand is probably fried.
try flashing recoveryfs partition
Bash:
fastboot flash recoveryfs "system.img"
Click to expand...
Click to collapse
nand was dead...due to all day work on JioFi, now all good thanks for help.

abhimortal6 said:
Unlocked Firmware for JioFi 3 JMR540 & JMR541
Disclaimer
I am not responsible for any kind of damage to your device.
Use this firmware at your own risk
Post is for educational purpose only.
ONLY FOR JMR 540 & JMR 541
​I was able to dump and reverse engineer JioFi 3's firmware to see if I can unlock the SIM restrictions. JioFi 3 is designed by Foxconn it uses generic firmware. Unlocking took time though. Tested with Vi, Airtel.
Guide
Make sure you're on same firmware version
JMR 540 - FXN_JMR540_R6.16
JMR 541 - FXN_JMR541_R3.10
If not please use the device for sometime it'll autoupdate.
1. Locate your device model and download the respective Firmware and extract it to a known location
JMR540_unlocked_system.zip​
JMR541_unlocked_system.zip​
2. Install drivers and tools (skip if already installed)
Install Fastboot drivers ( google it for mac and linux it's easy to find)​
Install Fastboot ( google it for mac and linux it's easy to find)​
3. Prepare device
Remove battery from JioFi 3
Locate reset pin hole button
Lay down JioFi 3
Use Paper Clip / SIM Ejector Tool to press button inside (using sharp object is not recommended)
Keep pressing button down and insert USB cable
Release button as soon as all the LEDs in Display turns RED. This means device is in boot loader mode
4. Flashing Unlocked Firmware
Open adb and fastboot tools terminal
Enter following to check if device is connected
fastboot devices
It will return something like this
baxxxxx fastboot
This means device is connected. If your device doesn't show up here please check drivers in Device manager
Now first erase the system partition (Skip for JMR 540 )
fastboot erase system
It will return something like this
erasing 'system'...
OKAY [ 1.104s]
finished. total time: 1.105s
Now flash the firmware
fastboot flash system "D:\system.img" ( replace path )
It should return something like this
sending 'system' (34306 KB)...
OKAY [ 1.276s]
writing 'system'...
OKAY [ 9.462s]
finished. total time: 10.741s
Now send reboot command to device
fastboot reboot
You'll notice device will reboot normally now you can unplug the cable.
Congratulations your device is now unlocked and you can reinsert battery and another SIM for testing.
Firmware will take long time than usual to boot do not panic.​
4. Changing APN
Insert SIM connect with JioFi 3 wait it to intialize
Open Web UI from browser (http://jiofi.local.html/)
Now login (default username/pwd is administrator/administrator)
In Network Tab you'll find setting for changing APN
Put it on manual and enter "internet" as APN (without quotes)
Hit apply/save device will reboot again automatically and it'll auto connect
Just wait patience is the key here it'll connect.
If something goes WRONG or you want to UNDO you can re flash original firmware which is provided in this post.
Original backup
JMR_540_original_system.zip​
JMR_541_original_system.zip​
FAQs
Q. My device is not visible in fastboot devices
A. Confirm driver installation a faulty cable can also be the issue.
.
Q. Everything went well but still no changes in dashboard
A. After successful flash if you still don't see the changes your device is probably booting from recovery partition. Try flashing recovery partition by
Bash:
fastboot flash recoveryfs "system.img"
.
Q. After resetting device from pin hole button it shows INVALID SIM.
A. This is supposed to happen just reboot the device it'll work again.
.
Q. Can I undo all this and get back to original firmware
A. Yes just flash the original firmware provided in post and reset the device.
​
Mentions:
Thanks to Karuppusamy for testing it on JMR541.
​
Click to expand...
Click to collapse
Hi, i just read ur article on unlocking jiofi 3 and that looked amazing.But i have a jiofi JMR815 and have been looking for help to unlock it from a couple of years.But till date only your post looks promising and i ask yourhelp in helping me unlock my JioFi JMR815.Kindly consider helping me.Also i created an account in XDA just to ask your help
View attachment 5327245
View attachment 5327247
View attachment 5327249
View attachment 5327251

This is completely genius! I am now able to use Airtel sim on my JioFi! Thanks!