So guys
I was on twrp and tried to flash a new rom but when it rebooted after the install, my Zuk z2 died.
It does nothing now. If I press the powerbutton for a long time it shortly vibrates for one second and the notification light also lights up for 1 second, but does not boot up. I tried volume combinations, don't work either.
What can I do guys?
Well, this guy managed to fix it
. Not sure if its the best way to fix it but it's still something
Effected said:
So guys
I was on twrp and tried to flash a new rom but when it rebooted after the install, my Zuk z2 died.
It does nothing now. If I press the powerbutton for a long time it shortly vibrates for one second and the notification light also lights up for 1 second, but does not boot up. I tried volume combinations, don't work either.
What can I do guys?
Click to expand...
Click to collapse
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ follow the steps
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146
Use this if you didnt success from other methods.
tlxxxsracer said:
My video. The brick occurs when you usually backup a room with one version of twrp, flash another variant of twrp and then restore the nandroid from before.
Happened to me. Flashed MIUI, and then tried to restore a nandroid (not realising the TWRP changed).
Hope the video helps. Plus then you have a cable premade in case it happens again
Click to expand...
Click to collapse
Hello. Maybe you can give me some advice. I am stuck in engineering/diagnostics mode after I accidentally selected that option when I was in the bootloader trying to flash TWRP.
Basically, I had installed TWRP and Mokee 7.1.1. I wanted to check out the original chinese ROM so I relocked, flashed with QFIL, etc. I had first flashed MM, then I flashed latest chinese Nougat official.
I didn't like it, so I was trying to unlock the bootloader again, and in the process I ended up selecting the diagnostics/engineering mode. The phone was stuck there and I had no way of accessing the bootloader to reflash with QFIL or MiFlash
TO try to fix, I used the deep flash method you describe in the video, only I found it in zukfans. I was able to open the 9008 port, flash with QFIL/MiFlash. Even though both tools describe the flash as successful, on boot, it goes back to engineering mode.
How to I get out of there? Is my phone done?
Thanks!
Related
Hello,
well I read a lot about rooting and flashing custom Roms the last few days and I figured I would give it a try.
I really hope I didn't break my phone, hopefully one of you Android / Defy Gurus can help me out
I rooted my phone with Super-One-Click and that worked fine, then I installed Recovery Bootstrap for Defy from a thread in this forum (can't find it at the moment) but it is this one: "bootstrap-recovery-clockwork-mod"
Anyway, that worked fine too... I make a backup (backup/restore->backup). Then did multiple factory resets and deleted the Cache as well as the dalvik cache multiple times. And then installed CM7 off the SD card.... the first time it didn't work, and it booted back to the setup of blur... I tried it again this time activating "Fix Permissions" before install... it then worked and it booted up CM7 fine.
I then wanted to go ahead and install The Google apps from here: goo-inside.me for CM7 ... did the same thing wiping the caches and then installing off of SD card... rebooted and I get stuck with the motorola logo... which just stays there and does not go away.
I rebooted multiple times (by taking out the battery) entered recovery mode with the volume button (this is the standard android recovery) tried clearing cache and rebooting, same problem... tried "wipe data / factory reset" same problem. No matter what I do it doesn't boot past the motorola logo.
Any ideas? I read about RSDLite and downloaded a stock sbf but my phone isn't recognized by RSDLite while not booted... even in the recovery utlitiy no connection is made (USB Debugging is off I think).
Any help would be very much appreciated. I am kind of freaking out, I just got the phone a few days ago
Thanks so much,
MrPink52
before u turn your phone on hold vol+ key until it loads the bootloader for rsd lite
Didn't want to make the first post overly long or complicated so here a quick update.
I read somewhere else that I could get a connection in RSDLite by holding volume up while booting and entering the bootloader... that seemed to work, so chose this SBF File "JRDNEM_U3_2.21.0" from and developers and told RSDLite to flash it... it said complete...the display then turned black... and now I don't have any image at all. It is still found in RSDLite but nothing happens when I boot... and I don't even see the logo anymore.
Now I will definetly stop trying until someone here can hopefully help me.... it seems like me trying by myself is only making things worse
Please tell me there is still hope for my Def.
Thanks,
MrPink52
When the red M logo is on the screen the led should turn blue for a few seconds, at this point press the Down Volume key & you should then go into ClockworkMod Recovery. I would try clearing the cache from there or maybe even doing a factory reset.
you will probably have to flash stock and start over
gramps50 said:
When the red M logo is on the screen the led should turn blue for a few seconds, at this point press the Down Volume key & you should then go into ClockworkMod Recovery. I would try clearing the cache from there or maybe even doing a factory reset.
Click to expand...
Click to collapse
I already tried that, like I said it didn't start the ClockWorkMod but instead the standard Android recovery Utlity which only has limited options... but now as I have described, the problem has gotten worse... I can't even get in there anymore after flashing with RSDLite.
Help!
MrPink52
im in us and my stock file is this one p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
pmp326 said:
you will probably have to flash stock and start over
im in us and my stock file is this one p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
Click to expand...
Click to collapse
I took the one listed for Germany. My phone isn't branded so I tried to flash it with the sbf that seemed to fit.
Can you tell me exactly how I can do this correctly?
I may be doing something wrong with RSD Lite... but slowly I am really affraid I have bricked my Defy for good
MrPink52
after you flash go into stock recovery vol- key and factory reset then reboot should work fine then
pmp326 said:
after you flash go into stock recovery vol- key and factory reset then reboot should work fine then
Click to expand...
Click to collapse
That gives me hope... the problem is I can't press vol- after flashing... the screen just stays black... I can reflash it and I get white writing on the screen "Updating SW" but when its finished the screen just turns black again... and neither Vol+ nor Vol- during boot does anything.
Any further advice?
try another sbf the one ur flashing isnt the right one
it should show a gray motorola logo when u go to boot
i think this is the one u neeFull SBF name ::JRDNEM_U3_3.4.2_179-6.1_TMNAB_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PD S03C_USAJRDNFRYOTMDE_P016_A013_M005_HWp3_Service1F F.sbfd
Do you have a direct link? I couldn't find it on the and-developers site... so a direct link would be great!
Until then I guess it can't hurt to try various sbf files to see if one works.
The only thing I am afraid of, is that my battery will dy during the flashing... is there a way to charge the battery in my current state? Or will it only charge when Android is booted?
Thanks for your support so far,
MrPink52
go here and follow directions in this thread http://forum.xda-developers.com/showthread.php?t=1175801
after reading that is the only one i could find for ya hope it works for ya
if u can get into a recovery it will charge when plugged in
I have tried some of the sbf files... and tried this one: JOREM_U3_3.4.2_177-003
that seemed to work, at least I got the logo back and could enter the Android utilities... and it seems like it is booting up blur right now... wow... what a scare.
Don't know if I will try to move to CM7 again anytime soon... I don't know what went wrong since I tried to follow tutorials.
But again thank you for your help.. I will update here again when I know for sure that everything is working
your fine dont let that scare you just wrong file its not the end of the world anyways enjoy!!!
I just did mine last night and at times it was a little scary, being the 1st time I had tried to flash a phone. I followed these directions to a point.
http://forum.xda-developers.com/showthread.php?t=897445 I also used these directions pretty much combined the 2 to get the job done. http://forum.xda-developers.com/showthread.php?t=1065798
When I got to the point where CM7 RC1v2 was installed along with Google Apps I then rebooted and let it all start and create all the necessary caches. I then flashed the nightly from the sd card.
I did NOT do the 3g stuff mentioned in the instructions, There is an app that will let you set your baseband for your country in the app drawer called Defy Baseband
Hello,
Here is what led to my issue:
I rooted my phone using this method: http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
Downloaded clockwork rom manager.
Here comes the thing I don't remember. At least i know that the last thing i did was to click on 'backup current rom'
After this the phone reset itself and this message came up:
Secure booting error!
Cause: boot certification verify
Then i tried to reset using the power button, which led me to the 'battery full' screen - afterwards i was able to reboot. As stupid as I am I just tried the same thing again. And ever since i am stuck at the 'Secure booting error!' screen.
I am unable to enter download mode. I get to the 'Hard factory reset' screen, but if i accept doing so, it says 'Secure booting error!' again.
I also remember clicking on 'restart into recovery mode' at some point, but this is not the last thing i did.
I am really desperate. Please, help me!
Well i had the same issue today... It happened after i did two changes. One of them was to to try to relock from freegee and flash twrp again from freegee. In my case i was able to go in download mode and flash original kk rom with lg flash tool.
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Jubi-Wan said:
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Click to expand...
Click to collapse
How are you trying to boot into download mode? And what factory reset screen? It seems as though you did not unlock the bootloader using freegee, if you make any changes and relock the boot loader you will get that error. But it seems that it has not been unlocked. If you hold power and volume up what happens? Same thing when power and volume down, one of them is recovery (possibly factory reset you are seeing) and the other is download mode. I don't remember right now but you should read the whole softbrick thread and see if you are missing something. You may need to use LGPNST to go back to stock, you can also use that program to flash a new recovery so read carefully and follow all steps.
When this happened to me I was able to flash an unlocked bootloader and it allowed me to use my phone again as it was before doing something stupid (for me it was an attempt to re lock the bootloader).
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Jubi-Wan said:
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Click to expand...
Click to collapse
What do you mean when you try to fastboot? Fastboot is basically the bootloader and allows you to select recovery or download mode. What you should have done after following that thread is go to recovery and wipe everything and flash a new ROM.
If you are saying that the bootloader is not coming up and allowing you into recovery then I believe something was missed.
After trying out some varioants of this it worked: http://forum.xda-developers.com/showthread.php?p=40274560&highlight=red+led#post40274560
I wiped the phone, but since I had to leave over the weekend i just turned it off and went away.
Now that I am back, nothing works now :/ The Phone doesnt react to anything, not even donwload-mode.
Is the battery too low maybe? It's on the wall now for a few hours, but it still doesn't react. It's not warm either.
edit:
when i charge the phone, i will get a 'watchdog bark' after some time allowing me to get into recovery. accesing downloadmode from there doesn't do anything. strangely, the recovery isnt trwp although it should be because teenybin comes with it. it's 'bbs.gaodi.net' which doesn't have a sideload feature. what do i do now?
edit2:
after 10000 tries i got into download mode. i don't want to **** up now so i won't do anything until i know exactly what to do.
any advice?
edit3:
got it working by flashing another teenybin which included trwp - then i installed miui via sideload. i don't have signal though, but i will open another thread for this since this is another issue.
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
Nevermind, @sliding_billy has the answer.
I
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
If you can get to BL and fastboot devices is recognizing it, you are only soft bricked. Do a flash-all of the factory image. You will be starting over with the exception of OEM unlock and BL unlock. Once you are up and running, go back to BL, change slots and do the flash-all again. Of course, you will be setting up again but you should be clean. Be sure to use the last Android 9 factory image for flash-all if you are not intending to go to 10 yet. There is one rock solid custom ROM for 10 (Havoc). Take a read of the install instructions as it doesn't use TWRP (not available for 10 yet). It does need the flash-all of November factory image done to both slots, so if you are looking at that do it immediately IMO since you will have to wipe anyways.
If you wipe system in TWRP then you have to flash a ROM from there. That is why it went blank when you rebooted. You have nothing to boot up on.
ADB a stock file and start over...it's not bricked.
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
thex2 said:
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
Click to expand...
Click to collapse
Havoc also had pie builds if you wanted to try.
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
anyone?
SallyTheDevil said:
anyone?
Click to expand...
Click to collapse
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
muhamet said:
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
Click to expand...
Click to collapse
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
SallyTheDevil said:
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
Click to expand...
Click to collapse
Force restart,press volume up and power button same time
muhamet said:
Force restart,press volume up and power button same time
Click to expand...
Click to collapse
Volume up and power doesn't do anything
Volume down + power restarts the phone but it comes to the same samsung black screen
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
k3lcior said:
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
Click to expand...
Click to collapse
I can't enter recovery mode
Volume down + power restarts but I did try to go to recovery by releasing volume down and pushing volume up the second screen goes black but it's not working
I can only enter download mode when it's connected to pc with odin running
Could it be a hard drive problem?
And I'm pretty sure i got the right firmware
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
k3lcior said:
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
Click to expand...
Click to collapse
tried it, it doesn't recognize the phone.
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
SallyTheDevil said:
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
Click to expand...
Click to collapse
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
SallyTheDevil said:
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
Click to expand...
Click to collapse
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
muhamet said:
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
Click to expand...
Click to collapse
done that already, it flashes the firmware successfully but still won't boot, it just gets stuck at the same screen.
JulianaO said:
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
Click to expand...
Click to collapse
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
SallyTheDevil said:
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
Click to expand...
Click to collapse
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
JulianaO said:
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
Click to expand...
Click to collapse
yh I installed that update too and this happened later the same night.
unfortunately for me all the shops n services are currently shut down because of the Co-Vid situation so i have to wait for now.
thanks for sharing, lemme know what happens.
I've had these same problems before. When flashing with Odin, don't populate the last slot with anything (the HOME_CSC slot). Flash it to the device without auto reboot on, restart the device manually and hold vol up + down to get to blue scrern, then unlock bootloader. Let it restart, then reflash ROM.
Hi,
Recently my devices start to boot loop suddenly so, i decide to flash the custom rom back.after flashing the custom rom,the device still boot loop then i try to get into TWRP Recovery mode but it would not appear, then i proceed to flash the TWRP Image recovery (suspecting the recovery already missing during the flashing rom ) via FASTBOOT once the process done, i had disconnect the cable and suddenly the device screen wouldnt turn on even though i pressed the power button for a long time.
Please help.
Thanks.
asen[email protected] said:
Hi,
Recently my devices start to boot loop suddenly so, i decide to flash the custom rom back.after flashing the custom rom,the device still boot loop then i try to get into TWRP Recovery mode but it would not appear, then i proceed to flash the TWRP Image recovery (suspecting the recovery already missing during the flashing rom ) via FASTBOOT once the process done, i had disconnect the cable and suddenly the device screen wouldnt turn on even though i pressed the power button for a long time.
Please help.
Thanks.
Click to expand...
Click to collapse
Connect phone with PC and check if you Notification light turn on or not.
If it's still on, your phone got hard bricked (maybe because you mess with custom roms and TWRP). Next time follow Flash guide in each custom roms.
You can use unbrick hardbrick method (free) or get service (paid). I recommend try free method first but when use SP Flash tool, remember ONLY use "Download Only" (Some stupid local shop can use Format and you can lose IMEI too, so careful).
You can find that method easily on: Youtube, XDA, Github, Telegram,...
If you have any error, you can reply here or join Telegram group to get help.
hi i already using SP Flash tool but i stuck at this level..