First off, I have a Chinese model of the Galaxy Note II SCH-N719. I was given this phone for free by a friend.
The phone is now bricked. I was trying to install a custom recovery. After going into the stock Android recovery, I flashed the CWM zip and it bricked the phone.
What doesn't work
- When I load up the phone it will only load up the splash screen and stay stuck there, it will not go any further no matter how long I wait.
- If I attempt to load the phone into recovery mode (Volume Up + Home + Power) it will show a blank screen. I cannot interface with the device via adb or by any other means.
If I boot the phone into download mode (Volume Down + Home + Power) it will show a blank screen/no activity. However, in this mode I can interface with the device using fastboot so I can issue commands to the phone.
What I've tried so far
So because the phone is apparently bricked, I have
-Attempted to flash a custom recovery via fastboot, no difference
-Attempted to flash the stock recovery, no difference
-Attempted to boot directly into the stock recovering using fastboot boot boot.img but it just produced a blank screen
I downloaded the stock ROM for this phone, which is 4.3 (N719KEUCML2). After unziping the contents of this archive, I was successfully able to use the fastboot flash all command to flash the recovery, system etc partitions to the phone.
However, it produced no change in the phone. I have used fastboot to wipe the partitions and individually flash the partitions using the .img files but with no result.
The only thing I was unable to get working was using fastboot update. The stock (factory) ROM for this phone does not seem to satisfy as an Update.zip. I receive the typical "system.img" not being found and it cannot update from the .zip (which is a shame). My worry is that the bootloader partition has been corrupted, however there is no bootloader.img provided in the stock rom!
Do anyone have any experience with this? Would be grateful for your help! If I should put this in a more suitable section please let me know.
Any thoughts on this? Phone is still unresponsive..
Hello,
my problem is after trying to revert back to the stock rom I messed things up and I can't get back to fastboot mode.
But I will describe what I did. First thing I did many weeks ago was the installation of cyanogenmod 11 KitKat on the P6.
All worked fine except for the high power consumption. Because of that I decided to switch back to the stock rom.
To do that I have made the following steps.
1. I downloaded the Jelly Bean firmware from the official huawei website. (I can't post the link since I'm a new user)
2. I used the download extractor to extract boot.img and recovery.img
3. I flashed them via fastboot
4. I prepared a SD card with the update.app in the dload folder
5. booted the phone with volume buttons pressed. Update process started but failed. There was no error message only a huge FAIL message.
6. After that I switched back to TWRP recovery what worked fine
7. I build a flashable zip file with the update extractor of boot.img, recovery.img, system.img, cust.img, userdata.img and flashed it via TWRP
8. Than I realised that I mistakenly included the recovery.img which overwrote the TWRP recovery
Now the phone always starts to the huawei logo also when starting with volume buttons pressed. I can't access the fastboot mode anymore.
When shutting it down it reboots instantly.
My questions are the following.
* Can a corrupted recovery block the access of the fastboot mode or any mode to access the phone via USB to flash a new recovery?
* Are there other ways to reset the phone?
* Was it a problem to take a Jelly Bean stock rom after a KitKat installation?
* If the phone is bricked, do you have any suggestion what to do with it? Is it worthless now? Sell on ebay? Hope this is not necessary.
Thank you so much!
numbi said:
Hello,
my problem is after trying to revert back to the stock rom I messed things up and I can't get back to fastboot mode.
But I will describe what I did. First thing I did many weeks ago was the installation of cyanogenmod 11 KitKat on the P6.
All worked fine except for the high power consumption. Because of that I decided to switch back to the stock rom.
To do that I have made the following steps.
1. I downloaded the Jelly Bean firmware from the official huawei website. (I can't post the link since I'm a new user)
2. I used the download extractor to extract boot.img and recovery.img
3. I flashed them via fastboot
4. I prepared a SD card with the update.app in the dload folder
5. booted the phone with volume buttons pressed. Update process started but failed. There was no error message only a huge FAIL message.
6. After that I switched back to TWRP recovery what worked fine
7. I build a flashable zip file with the update extractor of boot.img, recovery.img, system.img, cust.img, userdata.img and flashed it via TWRP
8. Than I realised that I mistakenly included the recovery.img which overwrote the TWRP recovery
Now the phone always starts to the huawei logo also when starting with volume buttons pressed. I can't access the fastboot mode anymore.
When shutting it down it reboots instantly.
My questions are the following.
* Can a corrupted recovery block the access of the fastboot mode or any mode to access the phone via USB to flash a new recovery?
* Are there other ways to reset the phone?
* Was it a problem to take a Jelly Bean stock rom after a KitKat installation?
* If the phone is bricked, do you have any suggestion what to do with it? Is it worthless now? Sell on ebay? Hope this is not necessary.
Thank you so much!
Click to expand...
Click to collapse
When you say its bricked does that mean that it gets stuck on huawei ascend logo? If thats the case than you should be ablr to enter fastbboot since thats the sign you are in bootloader mode.
Sent from my P6-U06
tileeq said:
When you say its bricked does that mean that it gets stuck on huawei ascend logo? If thats the case than you should be ablr to enter fastbboot since thats the sign you are in bootloader mode.
Sent from my P6-U06
Click to expand...
Click to collapse
Well that is what I thought too, but I can't get a connection via adb or fastboot.
"adb devices" lists nothing. When connecting the phone via usb to the computer there is no log entry generated on the computer like it's the case with other usb devices.
I tried different usb cables. I'm unsure how to be really sure whether I'm in fastboot mode or not.
Before flashing the zip everything worked fine so it's very unlikely to be a driver issue or something related to the computer I think.
i have the same problem and i cant communicate with the device in any way but what happen to me that i download a wrong recovery img.
if someone can help please
i fix my phone and get it back to the stock recovery ::victory:
Can you please share how you make it? I have the same problem...
I fixed it by replacing the motherboard using a very detailed tutorial on ifixit.
The P6 is not build to be repaired by the customer but with the right tools it was ok.
skyhew said:
Can you please share how you make it? I have the same problem...
Click to expand...
Click to collapse
I turn the phone in the debug mode and flash the stock recovery back you enter the debug mode by press and hold on the volume down then after it the power for 10 sec. after you plug the phone to the computer via usb then download this file: 4shared.com/rar/9HO06Lpjba/p6_stock_recovery.html
and then unzip the file then open by order
1- adb-windows if you have windows
2- fastboot-windows
3- install-recovery-windows
and restart the phone and you have the stock recovery back
I have twrp on mobile usa lg g4, I flash with flashify the newer version but now I cant get in to twrp recovery it shows up as fastboot mode help please...all I realy wanna do now is go back to full stock unrooted...cant figure out how please
Go to here: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848 and download tools required and appropriate rom.
Ensure usb drivers are installed and phone is off (even if you have to remove battery to do so.)
Power on and hold vol up and power until download mode appears, open kdz tool and select your firmware, flash as normal and should put phone back to stock.
Takes about 5-10 mins in total.
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
Click to expand...
Click to collapse
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
Click to expand...
Click to collapse
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
idog8818 said:
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
Click to expand...
Click to collapse
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Same
Hello,
I think I did the same error, flashing a wrong boot.img...
I tell you if I manage to do something.
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
danyv77 said:
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
Click to expand...
Click to collapse
This only helps when boot image is not damaged.
Duchan_xda said:
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Click to expand...
Click to collapse
I'm with you. The boot image has error and when MTK realize it has something wrong it will NOT enter into fastboot. The only way to fix this is too use SP Flash Tool for deep flash. Mi store uses this way as well to fix the issue.
Try this:
https://c.mi.com/thread-2173190-1-0.html
ppthom said:
Try this:
https://c.mi.com/thread-2173190-1-0.html
Click to expand...
Click to collapse
This does NOT work. Please don't waste time on it.
:good:Thanks for clarifying this. Back to square one ...
idog8818 said:
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Click to expand...
Click to collapse
Are you recover your phone? I'm still waiting one year...
Duchan_xda said:
Are you recover your phone? I'm still waiting one year...
Click to expand...
Click to collapse
I didn`t find any background on your issue, just something like you actually have a device with white led light blinking.
I read this thread before (yes, some weeks ago) this happened to me yesterday https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unlock-note-8-pro-authorised-t4168805 the short story is that I were trying to return to Miui 12 after of using some custom ROMs and something in the flashing process failed I mean it was an incomplete flashing and I assumed that most probably just the bootloader partition was damaged. The whole important fact in this situation is that you have yet available fastboot mode but like the splash partition with its image was gone I couldn `t see it and I were anyway in fastboot mode so I could flash the proper files to "unbrik" it. (my device is unlocked)
What you should try is connect it with PC while you`re pressing the volume down, enter to adb/fastboot environment and type fastboot commands to see if device is recogniced, you don`t have to hear constant reboot sounds or in this case press the power button simulating that you are powering off device.