Related
Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.
Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.
mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks
Hello,
I recently bought (ON DECEMBER 2017) the moto g5 plus (XT1686) Indian model..
After a week I unlocked the bootloader and installed PixelExperience 8.1 ROM,
unfortunately, I deleted the TWRP backup, so I search for "how to install the stock firmware",
I downloaded an old firmware (it has January 2017 security patch) and installed it thus, I lost my IMEI number it shows 0 when I dialed *#06#.
After that, I got an update on this firmware, when I updated (Hoping for I get back my IMEI), the phone got hard bricked,
then read a forum on xda , tried blankflash and got back my access to bootloader,
after that, i installed "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware over and over but the phone doesn't boot anymore it stucks at boot logo,
then I installed twrp recovery and installed Pixel experience ROM again, but I didn't boot, always it stucks on boot logo,
then I select Factory mode instead of reboot in bootloader menu, then it booted into Pixel experience ROM, but the SIgnal is STill GONe,,
any solution....
i went to a local mobile repair store,
they also not able to fix that,,,
then I go to the Motorola service center, they also failed,,
the moto service center guy told that the Firmware installation stops at 80% because of twrp installed...
any permanent solution, please help..
Thanks in advance.. ?
DEV JC said:
Hello,
I recently bought (ON DECEMBER 2017) the moto g5 plus (XT1686) Indian model..
After a week I unlocked the bootloader and installed PixelExperience 8.1 ROM,
unfortunately, I deleted the TWRP backup, so I search for "how to install the stock firmware",
I downloaded an old firmware (it has January 2017 security patch) and installed it thus, I lost my IMEI number it shows 0 when I dialed *#06#.
After that, I got an update on this firmware, when I updated (Hoping for I get back my IMEI), the phone got hard bricked,
then read a forum on xda , tried blankflash and got back my access to bootloader,
after that, i installed "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware over and over but the phone doesn't boot anymore it stucks at boot logo,
then I installed twrp recovery and installed Pixel experience ROM again, but I didn't boot, always it stucks on boot logo,
then I select Factory mode instead of reboot in bootloader menu, then it booted into Pixel experience ROM, but the SIgnal is STill GONe,,
any solution....
i went to a local mobile repair store,
they also not able to fix that,,,
then I go to the Motorola service center, they also failed,,
the moto service center guy told that the Firmware installation stops at 80% because of twrp installed...
any permanent solution, please help..
Thanks in advance.. ?
Click to expand...
Click to collapse
Try to install this firmware using fastboot...
https://androidfilehost.com/?fid=889964283620771881
It's for the Indian variant XT1686 and is the latest so far. One advice, simply never downgrade a Moto device to a lower version of ROM than what your phone was running before you unlocked and installed a custom ROM, it bricks your phone and you'll end up with an expensive paperweight.
psychopac said:
Try to install this firmware using fastboot...
https://androidfilehost.com/?fid=889964283620771881
It's for the Indian variant XT1686 and is the latest so far. One advice, simply never downgrade a Moto device to a lower version of ROM than what your phone was running before you unlocked and installed a custom ROM, it bricks your phone and you'll end up with an expensive paperweight.
Click to expand...
Click to collapse
thanks for sending the link.......
i tried but it boots into twrp not into ROM
after instalation complete , when select reboot it boot into recovery ,
what may be the problem is ??
DEV JC said:
thanks for sending the link.......
i tried but it boots into twrp not into ROM
after instalation complete , when select reboot it boot into recovery ,
what may be the problem is ??
Click to expand...
Click to collapse
Were all the commands successful? And about the booting condition, someone had this exact booting issue and I can't remember where it's posted, so I may not be able to answer that. Can you try rebooting to bootloader from TWRP's reboot menu?
DEV JC said:
Hello,
I recently bought (ON DECEMBER 2017) the moto g5 plus (XT1686) Indian model..
After a week I unlocked the bootloader and installed PixelExperience 8.1 ROM,
unfortunately, I deleted the TWRP backup, so I search for "how to install the stock firmware",
I downloaded an old firmware (it has January 2017 security patch) and installed it thus, I lost my IMEI number it shows 0 when I dialed *#06#.
After that, I got an update on this firmware, when I updated (Hoping for I get back my IMEI), the phone got hard bricked,
then read a forum on xda , tried blankflash and got back my access to bootloader,
after that, i installed "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware over and over but the phone doesn't boot anymore it stucks at boot logo,
then I installed twrp recovery and installed Pixel experience ROM again, but I didn't boot, always it stucks on boot logo,
then I select Factory mode instead of reboot in bootloader menu, then it booted into Pixel experience ROM, but the SIgnal is STill GONe,,
any solution....
i went to a local mobile repair store,
they also not able to fix that,,,
then I go to the Motorola service center, they also failed,,
the moto service center guy told that the Firmware installation stops at 80% because of twrp installed...
any permanent solution, please help..
Thanks in advance..
Click to expand...
Click to collapse
Try using Albus Blank Flash https://www.google.co.in/amp/s/foru...oto-g5-plus-hard-bricked-solved-t3662734/amp/
And then your device will wake up in dummy bootloader
Then flash the gpt and recovery img
Then flash twrp recovery!
I think this method will work
psychopac said:
Were all the commands successful? And about the booting condition, someone had this exact booting issue and I can't remember where it's posted, so I may not be able to answer that. Can you try rebooting to bootloader from TWRP's reboot menu?
Click to expand...
Click to collapse
Tried in twrp also...
In bootloader menu when select reboot it boots into twrp...
Also while phone is on (in rom) after reboot it goes to recovery mode....
Only when i select factory mode in bootloader menu, then it boots into rom*
Manav10799 said:
Try using Albus Blank Flash https://www.google.co.in/amp/s/foru...oto-g5-plus-hard-bricked-solved-t3662734/amp/
And then your device will wake up in dummy bootloader
Then flash the gpt and recovery img
Then flash twrp recovery!
I think this method will work
Click to expand...
Click to collapse
Hiw to flash it can u guid...
When my phone was hard breaked i connected via cable and i got indication blinking led....
Now i can get access to bootloader
DEV JC said:
Hiw to flash it can u guid...
When my phone was hard breaked i connected via cable and i got indication blinking led....
Now i can get access to bootloader
Click to expand...
Click to collapse
Yes If you can access to bootloader then flash the latest twrp 3.2.1.0 For g5 plus and after flashing recovery then flash the debolated rom first!
Do not flash stock rom first you have to instal Debolated rom you can easily access to the rom from Xda
And then you can flash any rom after debolated
Hi, if you wish to sell your dead mobile,
Please let me know
Thanks
Krishna
DEV JC said:
Hello,
I recently bought (ON DECEMBER 2017) the moto g5 plus (XT1686) Indian model..
After a week I unlocked the bootloader and installed PixelExperience 8.1 ROM,
unfortunately, I deleted the TWRP backup, so I search for "how to install the stock firmware",
I downloaded an old firmware (it has January 2017 security patch) and installed it thus, I lost my IMEI number it shows 0 when I dialed *#06#.
After that, I got an update on this firmware, when I updated (Hoping for I get back my IMEI), the phone got hard bricked,
then read a forum on xda , tried blankflash and got back my access to bootloader,
after that, i installed "XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEF" firmware over and over but the phone doesn't boot anymore it stucks at boot logo,
then I installed twrp recovery and installed Pixel experience ROM again, but I didn't boot, always it stucks on boot logo,
then I select Factory mode instead of reboot in bootloader menu, then it booted into Pixel experience ROM, but the SIgnal is STill GONe,,
any solution....
i went to a local mobile repair store,
they also not able to fix that,,,
then I go to the Motorola service center, they also failed,,
the moto service center guy told that the Firmware installation stops at 80% because of twrp installed...
any permanent solution, please help..
Thanks in advance..
Click to expand...
Click to collapse
Okay 1st of all
install This TWRP only
https://forum.xda-developers.com/g5-plus/development/dev-64bits-t3708091
and Then install any Custom Rom
I suggest these
https://forum.xda-developers.com/g5-plus/development/rom-resurrectionremix-v6-0-0-oreo-t3754057
or
https://forum.xda-developers.com/g5-plus/development/rom-lineageos-15-0-t3673573
Let me know
Only Do Clean Install
I too have the same no signal issue, but I have my EFS so I can get my IMEI but no signal in any sim. The sims are detected but there is no signal and it says Radio OFF , so I tried #*#*4636#8#* menu but it didnt help either. I lost signal when I was on LineageOS and tried flashing magisk and DolbyAtmos. After that I flashed Debloated and got the signal back but then I tried going back to stock and ever since I regret my decision. I have tried flashing different ROMs but no signal issue remains in each and every one of them. Even EFS dont help as I get my IMEI but no signal. Any help would be really appreciated.
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
No help here?
??????????????????????????????/
i don't think so people are helpful here or either not expert as nobody is replying lol
No idea. Sorry
taran181 said:
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
Click to expand...
Click to collapse
4-6 months back there was thread why we should not restore efs of someone & proper tutorial for people who messed up their mac address with some kernel.
Now this tutorial on downgrading pie to oreo. I have no idea. Someone's efs would mess your IMEI, wifi mac, Bluetooth mac, thats what i think. But there are tutorial how to edit imei using some Qualcomm tool.
Ask @CosmicDan. He's the expert.
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
I was having an issue since using custom rom with december fw btw.
and I was mistaken flashing november fw back to solve some calling issue, so I ended up with no signal which should be came from I didn't restore dev's efs backup.
So I start from flashing full clean stock november and ended with bootloop on it, which is something I still curious what cause it.
At that times, I'm on locked bootloader and can't even enter edl to reflash the rom and can't unlock bootloader since the rom still not booting to enable oem unlocking option.
I don't remember what I have done to it, but at times my phone can boot with no signal, 0 imei on sim1 and null on sim2.
So I start to rewrite the imei then everything is back to normal.
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
fhsd22 said:
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
Click to expand...
Click to collapse
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
taran181 said:
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
Well you can try it I guess, just backup the EFS partition and other stuff with my backup tool and you can always go back if worse comes to worst.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
Xiaomi put out a message on their forum that after the Pie update, the phone should not be rolled back. Its for all Android one models. When users flash an older roms, bootloops occur.
https://www.fonearena.com/blog/271177/xiaomi-pie-oreo-downgrading-disabled-android-one-devices.html
taran181 said:
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
Click to expand...
Click to collapse
But what he is saying is that he did downgrade EFS, but IMEI didn't change. This suggests that EFS isn't the original source of IMEI after all. Or maybe the bootloader can re-write IMEI and stuff on boot, who knows... Surely others have actually confirmed that EFS cross-flash = IMEI change, right? Not just assumed?
...point is, you can backup your EFS via EDL mode so there should be no risk. If you made a full EDL backup of your own device when you were still on Oreo then you would be golden, as EDL has full access to all partitions.
Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.
Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something
Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .
Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.
I was using Bootleggers (8.1 Oreo ) ROM on my XT1686 and tried flashing Pixel experience (9.0 pie ).
Steps i went through:
1. Clean Wipe
2. Flashing Pixel Experience
3. Losing my network signals and IMEI
4. TWRP flashable 8.1 stock rom
5. Flashing the bootleggers 9.0pie update
6. Trying the erasemodemst 1/2 commands. NO result.
6. Restoring EFS and persist from the previous backup.
7. Ended up having IMEI back but still no network signals after multiple reboots.
I do know that flashing a STOCK ROM using fastboot and performing a clean reset will get my network back but will i have to stay back in the STOCK ROM ? Can nothing be done that allows me to keep using this amazing rom with a functioning network ?
TL;DR: NO NETWORK, IMEI AVAILABLE. EFS AND PERSIST BACKUPS ARE FLASHED ALREADY.
sjjatin9568 said:
I was using Bootleggers (8.1 Oreo ) ROM on my XT1686 and tried flashing Pixel experience (9.0 pie ).
Steps i went through:
1. Clean Wipe
2. Flashing Pixel Experience
3. Losing my network signals and IMEI
4. TWRP flashable 8.1 stock rom
5. Flashing the bootleggers 9.0pie update
6. Trying the erasemodemst 1/2 commands. NO result.
6. Restoring EFS and persist from the previous backup.
7. Ended up having IMEI back but still no network signals after multiple reboots.
I do know that flashing a STOCK ROM using fastboot and performing a clean reset will get my network back but will i have to stay back in the STOCK ROM ? Can nothing be done that allows me to keep using this amazing rom with a functioning network ?
TL;DR: NO NETWORK, IMEI AVAILABLE. EFS AND PERSIST BACKUPS ARE FLASHED ALREADY.
Click to expand...
Click to collapse
You didn't say from what ROM/firmware the persist.img backup was taken. If it wasn't from your original stock firmware that may be a problem. If it was from stock which version, 7.0 or 8.1?
If you flash a 8.1 signed fastboot firmware you should be able to change to every ROM you want to afterwards.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You didn't say from what ROM/firmware the persist.img backup was taken. If it wasn't from your original stock firmware that may be a problem. If it was from stock which version, 7.0 or 8.1?
If you flash a 8.1 signed fastboot firmware you should be able to change to every ROM you want to afterwards.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I lost the IMEI and VoLTE when i switched from 7.0 (stock) to 8.1 (experience ) rom and then had to use the VoLTE fix to set it straight.
After i got everything working in my 8.1 pixel experience ROM , i made a backup of all the partitions. I used that backup here.
sjjatin9568 said:
I lost the IMEI and VoLTE when i switched from 7.0 (stock) to 8.1 (experience ) rom and then had to use the VoLTE fix to set it straight.
After i got everything working in my 8.1 pixel experience ROM , i made a backup of all the partitions. I used that backup here.
Click to expand...
Click to collapse
Most probably the problem was to switch from 7.0 stock to a custom ROM, you should have updated to stock 8.1 and make a backup of persist before doing that. The persist.img will be modified when flashing a custom ROM.
If you haven't flashed someone else's persist file the best way to go would be flashing a signed Motorola 8.1 firmware by fastboot, take a full nandroid incl. persist and go from there to a custom ROM.
Here's how to do it and links to all available firmwares:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Most probably the problem was to switch from 7.0 stock to a custom ROM, you should have updated to stock 8.1 and make a backup of persist before doing that. The persist.img will be modified when flashing a custom ROM.
If you haven't flashed someone else's persist file the best way to go would be flashing a signed Motorola 8.1 firmware by fastboot, take a full nandroid incl. persist and go from there to a custom ROM.
Here's how to do it and links to all available firmwares:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks alot @Wolfcity. Sorry i couldnt reply sooner. I flashed a twpr flashable 8.0 stock by @NZpred from the page here:
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
It brought back the signals. After that i backed up all the files and EFS and reflashed the custom rom and the EFS and persist.
Thanks alot for your help and timely response.