Related
I know there is few hundered threads with "unbrick" in title but I read them all and nothing seems to work.
Friend brings me kenzo that he gets since his cousin brick it while trying OTA.
When I power phone its start to load system and it has 3 stages:
1. Show screen with "powered by Android" and 3 dots in the bottom, usualy about 4 min and restart
2. After restart just get black screen with Mi logo in the middle, for about 30 sec and restart
3. Instead of Android with dots bottom have white line progres bar, it takes 4 to 5 min and restart again.
After that stage 2 and 3 repeat for long as you have nervs to wait .
Phone can get in recovery and fastboot mode. And when I put him in test mode just show test screen and cant do anything.
In fastboot mode MiFlash recognize phone but report "device is locked" (try with 20160401 and 20160830).
After that i put him in EDL mode (fastboot reboot-edl) and MiFlash report successful flash. But nothing changes.
I try flashing global stable v8.0.5.0, china stable v8.0.4.0, global dev v6.10.13 and at the end global stable v7.2.5.0.
Any idea welcome. Thx
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
banana_bender said:
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
Click to expand...
Click to collapse
Cant do that. Even unofficial unlock need phone to be working to enable USB debbuging and accept RSA kay from PC.
Edit: Right now looking for ways to edit boot.img to unlock bootloader in attempt to get any useful recovery.
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
abihary said:
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
Click to expand...
Click to collapse
I will try... but dont think it will do the job. Will post result little later.
EDIT
It dose not work, just as I think.
All that kind of method/advice need 2 things:
1. Enabled USB debbuging - You cant do that on bricked phone even if you edit boot.img ( ro.debuggable=1 ) because fastboot will not execute command since you will not have option to accept RSA kay from PC on your phone and complete that action.
2. Dev ROM - since you have to enable OEM unlock and that option you have only in dev ROMs. Even Xiaomi official unlock requires that you must do it on dev ROM and that is a reason for "stuck on 50% in unlocking".
I try all that I can think: edit boot.img file, use patch emmc_appsboot.mbn, use edited flash_all.bat and rawprogram0.xml, insert sTWRP and ZCX TWRP in fastboot ROM... and all combination of that. Did it on 7.2.5.0 and 8.0.5.0 stable and 6.8.18 dev (since its last 5.1 ROM that I have).
Most of this attempts ends with "3 stages" explained in the first post. Some just show Mi logo for few sec and restart, once even power off phone. And once I even get phone to go directly to sideload/recovery state showing picture of the phone and usb cable.
Only thing left now is to find info is there difference in accessing to EDL mode between software (reboot-edl), deep flash cable and testpoint. IMHO there is none or little difference. Since software and deep flash can be troubled with bad USB cable or connector or USB board in phone.
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.
I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?