my huawei mate 7 stuck in logo and not turn on when i root it , after that i have wipe t
data and it still not turn on, on the reboot it said '' No OS installed!!!
how to fix it, please help.
I already lost my data and files:crying::crying:
You need to flash your stock firmware via odin
Sent from my SM-N910V using Tapatalk
low user said:
my huawei mate 7 stuck in logo and not turn on when i root it , after that i have wipe t
data and it still not turn on, on the reboot it said '' No OS installed!!!
how to fix it, please help.
I already lost my data and files:crying::crying:
Click to expand...
Click to collapse
Ok, you already have TWRP installed on your phone. So you aren't exactly a newbie. What version of OS did you have installed before you broke the phone?
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
CloudCompute said:
Ok, you already have TWRP installed on your phone. So you aren't exactly a newbie. What version of OS did you have installed before you broke the phone?
Click to expand...
Click to collapse
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
low user said:
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
Click to expand...
Click to collapse
Looks like you accidentally wiped the system partition. Did you already try keeping the 3 keys, vol up, vol down and power key pressed for 9 to 10 seconds to get into recovery mode?
i got myself in the same position to when trying to root.
if you are using this
http://forum.xda-developers.com/mate-7/development/tool-srk-tool-huawei-beta-02-20160501-t3369990
you can use that to restore back your stock bootloader. then rollback then only install back prefered rom.
in my case in got bootloop at b522. use the above batch file i restore stock bootloader. then rollback to b500 ( here it will still bootloop) then i flash back ( using dload in sdcard). it took 20 minutes for the phone to boot to system. lucky.
you have to use sdcard and computer to copy presered rom dload file.
root now works with the latest kingroot but beware the consequences created by kingroot
low user said:
it is marshmallow, it is more bad, my phone not only stuck in logo now it still turn on and turn off itself and just show the logo and turn off.
sorry for my English.
Click to expand...
Click to collapse
i still resolve this problem :
boot into twrp
plug your phone to PC : you can access to your sd card (intern)
copy update.zip (B514) to your sd card
on your phone clique install button TWrp and choose your update.zip und swipe
when done reboot
it's all
ahhl said:
root now works with the latest kingroot but beware the consequences created by kingroot
Click to expand...
Click to collapse
ONLY root by flash from TWRP.
Flashing from an app in the OS is not how to do it.
low user said:
my huawei mate 7 stuck in logo and not turn on when i root it , after that i have wipe t
data and it still not turn on, on the reboot it said '' No OS installed!!!
how to fix it, please help.
I already lost my data and files:crying::crying:
Click to expand...
Click to collapse
Bro, I think we have encountered a similar problem, although our current situation is now a bit different. Your's seem to be your system partition has been damaged, hence, the "no OS" message. For me, it's a stuck-at-the-logo situation. You can check it here in case you're interested... http://forum.xda-developers.com/mate-7/help/hard-bricked-mt-tl10-t3400467
Reading further, I see you're also stuck at the logo. Are you able to boot to recovery or BL?
Related
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.
I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Huzalio said:
I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Click to expand...
Click to collapse
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cache, factory reset, then reboot device.
cooltt said:
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cach, factory rest, reboot device.
Click to expand...
Click to collapse
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Huzalio said:
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Click to expand...
Click to collapse
Mate keep trying you have to be really quick when it goes off to quickly press volume up
cooltt said:
Mate keep trying you have to be really quick when it goes off to quickly press volume up
Click to expand...
Click to collapse
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Huzalio said:
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Click to expand...
Click to collapse
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
cooltt said:
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
Click to expand...
Click to collapse
Yeah did exactly that switched to the combo before it showed anything no succes.
Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
Not sure what's wrong with it then
Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Ulf3000 said:
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Click to expand...
Click to collapse
able to confirm to enter download modus
Huzalio said:
able to confirm to enter download modus
Click to expand...
Click to collapse
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
cooltt said:
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
Click to expand...
Click to collapse
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Huzalio said:
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Click to expand...
Click to collapse
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
cooltt said:
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
Click to expand...
Click to collapse
Okay i see.
Do you somehow have a good tutorial?
Huzalio said:
Okay i see.
Do you somehow have a good tutorial?
Click to expand...
Click to collapse
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Ulf3000 said:
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Click to expand...
Click to collapse
sadly no succes :/
Huzalio said:
sadly no succes :/
Click to expand...
Click to collapse
I think it's obvious you don't know what your doing, no offence. Everything that's been suggested should work with no problems. You are better off taking it to a Samsung centre to fix it. I doubt anyone will be able to help you here.
unbricking with the factory binary
This method is not for the faint of heart; it involves downloading 1) the factory binary for your phone, and 2) the correct firmware for your phone (which you can find at sammobile). I don't know if it will fix your particular problem but if everything else has failed, it's worth a try. You will basically be taking your phone back to its state when it was first set up at Samsung factory, before the firmware for your region was installed. I used this to get past a drk imei error, it's worth taking a look. Anyone else who knows more than me, please weigh in on what you think about it.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal
zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?
zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?
zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\
So i updated my phone automatically yesterday from the latest update, after it was done, i haven't been able to access my phone in anyway, it keeps on looping samsung logo and a window that says "This phone's bootloader is unlocked´and its software integrity can't be verified" and so on, ive tried to enter either Download mode and recovery mode, but none of the methods seems to have an affect on the phone at all, please help, thanks
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
FakerS3 said:
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
Click to expand...
Click to collapse
- The phone does not show up on the pc either
Was your phone rooted? That could explain it.
riggerman0421 said:
Was your phone rooted? That could explain it.
Click to expand...
Click to collapse
Yes
thorius95 said:
Yes
Click to expand...
Click to collapse
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
chibuche said:
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
Click to expand...
Click to collapse
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Never attempt to update if you have rooted and made any changes to the system, deleted or added system apps, modified kernel, changed boot logo,etc.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
So, here's how I put the phone in download mode.
I left the battery to drain completely, then without pressing the power button, I pressed the volume down and Bixby button; and only then I plugged the cable. Without pressing the power button, the phone started straight into Download mode.
Now Odin sees the phone, I'm about to flash it with the stock firmware and see what happens.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
Maybe this thread helps: https://forum.xda-developers.com/galaxy-s10/help/galaxy-s10-bootloop-updte-to-android-10-t4023201
It's probably Samsung's vaultkeeper that caused the bootloop.
thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
I just wanted to give an update of how I rescued my phone and kept all the information on the phone memory intact (this was one of the challenges, as I had some photos on it).
I put it in download mode by draining the battery, then tried to flash the updated firmware. It didn't work, leading once again to boot loop and all I could do was boot to the stock Android recovery - not helpful.
So I got it to download mode again and flashed the stock firmware it originally came with (prior to the update). In Odin, I put HOME_CSC in the CSC field, to keep the phone memory from being erased. This solved it.
Hope this info can help someone having the same issue.