Related
My phone is hard-bricked:
I have a Moto G XT1032 GPE Convert with 4.4.4, the phone out of the blue just rebooted and doens't pass from the ''Google'' screen.
Try with the MotoTool convert again to a GPE, these errors appear:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When the phone reboot, doesn't pass from the screen with the Google Logo.
I Try restore to stock firmware.
I try flashing CM11 through recovery but show up errors like: ''e:unable to mount ' /cache'', ''e:unable to mount ' /system'', ''e:unable to mount the internal storage'' and in the end a FAILED error in red.
I can acess to the Bootloader, the Recovery, not the system.
Dont think my phone is lost, I can acess the Bootloader so,.. but i dont know what to do anymore, can someone help me with some guidance to bring back the phone to life?
sorry my bad english.
You only tried do flash system? Haven't you flashed anything before system?
kirmr said:
You only tried do flash system? Haven't you flashed anything before system?
Click to expand...
Click to collapse
That image is from MotoTool, when i try to convert again to GPE, the moden, bootloader etc flash just fine, until come to the part of flashing the system that error appears 3 times, then the process continues and the phone reboot, appears the screen with the Google Logo, the phone vibrate and that's it, the phone don't even go to the boot animation, get's stuck in the Google logo screen.
_Drifter_ said:
That image is from MotoTool, when i try to convert again to GPE, the moden, bootloader etc flash just fine, until come to the part of flashing the system that error appears 3 times, then the process continues and the phone reboot, appears the screen with the Google Logo, the phone vibrate and that's it, the phone don't even go to the boot animation, get's stuck in the Google logo screen.
Click to expand...
Click to collapse
Chupista, try this guide it worked for me in some occasions.
https://www.youtube.com/watch?v=laU6NQ0LxR0&list=PLB0RKQDFm9rQe5_SlE8zZwBPboy8nzQlf
_Drifter_ said:
My phone is hard-bricked:
I have a Moto G XT1032 GPE Convert with 4.4.4, the phone out of the blue just rebooted and doens't pass from the ''Google'' screen.
Try with the MotoTool convert again to a GPE, these errors appear:
When the phone reboot, doesn't pass from the screen with the Google Logo.
I Try restore to stock firmware.
I try flashing CM11 through recovery but show up errors like: ''e:unable to mount ' /cache'', ''e:unable to mount ' /system'', ''e:unable to mount the internal storage'' and in the end a FAILED error in red.
I can acess to the Bootloader, the Recovery, not the system.
Dont think my phone is lost, I can acess the Bootloader so,.. but i dont know what to do anymore, can someone help me with some guidance to bring back the phone to life?
sorry my bad english.
Click to expand...
Click to collapse
This is caused because you updated to 4.4.4 previously, and the partition table changed. When you tried to downgrade, the partition table didn't accept the old system image. Now you must wait for a 4.4.4 GPE image, that is the only thing that can unbrick your phone, since it will have the updated gpt.bin.
kirmr said:
Chupista, try this guide it worked for me in some occasions.
https://www.youtube.com/watch?v=laU6NQ0LxR0&list=PLB0RKQDFm9rQe5_SlE8zZwBPboy8nzQlf
Click to expand...
Click to collapse
Unfortunately didn't work. But thanks for the help.
tatazeuz said:
This is caused because you updated to 4.4.4 previously, and the partition table changed. When you tried to downgrade, the partition table didn't accept the old system image. Now you must wait for a 4.4.4 GPE image, that is the only thing that can unbrick your phone, since it will have the updated gpt.bin.
Click to expand...
Click to collapse
So... no idea when the Image is release it? Could be tomorrow, next week or month right? Theres really nothing i can do to reverse this?
Well, good luck mate
I'm sure you'll that fixed very soon.
If flashing original file through adb won't do the trick..
Can't do anything more to help u. Propz.
_Drifter_ said:
So... no idea when the Image is release it? Could be tomorrow, next week or month right? Theres really nothing i can do to reverse this?
Click to expand...
Click to collapse
I made a method to recover your phone for use! Sadly, you will only be able to use custom ROMs (at least until there's a 4.4.4 image)
Check it in my thread
http://forum.xda-developers.com/moto-g/help/recover-4-4-4-downgrade-brick-temporal-t2801946
Hi guys,
I made the TWRP from TeamWin official sources for Huawei Nova2 . You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot into fastboot mode
Flash using
Code:
HTML:
fastboot flash recovery cofface_pic_al00_recovery_en.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery
Let me know if there are others
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
email:[email protected]
Unfortunately It is not working!
After flashing your file there is still the Huawei EMUI Bootloader and no TWRP. Bootloader was unlocked before. Fastboot was working fine.
Any idea?
Problem with Google GAPPS
Hi,
Thank you for your tuto and your ROM
I have bought my nova 2 in china.
Do you know how to install GAPPS. I have tried different version (stock, pico,.. ) but it's no use.
Do you know if I have to change the region first ?
Is it ok with your ROM ?
Regards
Perfect
Perfect, thank you!
Not working
Hello,
TWRP ist not working for me, I still have the EMUI bootloader after flash and reboot.
Boot into TWRP Recovery ("fastboot boot cofface_pic_al00_recovery_en.img") is aborted with:
"FAILED (remote: Command not allowed)"
Is there anything I've done wrong?
Thx!
dr.luther.1517 said:
Perfect, thank you!
Click to expand...
Click to collapse
did it work with your Nova 2?
i have got a demo device ( from germany ). Can some one upload his OEM info for a normal device ?
And yeah... it works
Success
Works very well, Thanks !
But ... while playing with it I lost the stock ROM for my Huawei Nova 2.
Since there is no download source available, could anybody share a stock ROM backup so I could restore using Twrp ?
Thanks !
My Nova 2 (PIC-LX9C432) automatically encrypts the disk after the first run, and then TWRP is unable to read /data partition nor do nandroid backups as a result. Can someone guide on how to disable encryption or get TWRP to decrypt data.
I read elsewhere that newer versions of TWRP are able to decrypt if you set a password / screen lock.
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
jusma said:
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
Click to expand...
Click to collapse
Perhaps you could get some tips from nova (1) thread there we had the same problems. But so long we have a working twrp with backup possibility.
Hi, i used this Twrp, but did not notice the error mesaje when i "create" a back up for all my data, then when deleting some things, i went off the road and ended deleting the complete operative system, and know i dont seem to be able to find a room for my phone is a huawei p10selfie(in my country) or huawei nova 2 plus (in the rest of the world) model BAC-L03, sry if i dont use the correct words, since english is not my native lenguaje
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
iamramanlmc said:
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
Click to expand...
Click to collapse
Nova 2i is Mate 10 Lite! https://forum.xda-developers.com/ma...e--roms-kernels-recoveries--other-development
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I have a Galaxy Note 4, running on TWRP 2.8.5 and on OS 6.0.1. I am into a tricky issue as the device is encrypted, and I am unable to load to it, as upon booting into the OS it throws a tantrum about the device being encrypted. I'm unable to factory data reset it via the TWRP as well. The device is not rooted. Long story short, I dont care about the contents and I'm willing to flash to the OEM firmware. Will I be able to do this? The device is not carrier locked. Is there any pre-requisites to check?
Please advise, and many thanks.
abhishek_turbo911 said:
Hi,
I have a Galaxy Note 4, running on TWRP 2.8.5 and on OS 6.0.1. I am into a tricky issue as the device is encrypted, and I am unable to load to it, as upon booting into the OS it throws a tantrum about the device being encrypted. I'm unable to factory data reset it via the TWRP as well. The device is not rooted. Long story short, I dont care about the contents and I'm willing to flash to the OEM firmware. Will I be able to do this? The device is not carrier locked. Is there any pre-requisites to check?
Please advise, and many thanks.
Click to expand...
Click to collapse
I would flash the latest TWRP image, format all partitions and then flash the stock firmware or a new rom to get rid of the issue.
LS.xD said:
I would flash the latest TWRP image, format all partitions and then flash the stock firmware or a new rom to get rid of the issue.
Click to expand...
Click to collapse
Hi, thanks for your reply.
When trying to install the rom, I received the error as below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried the following as well but I received the same error when I attempted to install the rom:
1. Go to Wipe > Advance Wipe > Selected system & data > swipe to wipe
2. Went to Wipe > Format Data > typed yes > and wiped successfully.
Hello, what is your phone's model?
LS.xD said:
I would flash the latest TWRP image, format all partitions and then flash the stock firmware or a new rom to get rid of the issue.
Click to expand...
Click to collapse
-Hope- said:
Hello, what is your phone's model?
Click to expand...
Click to collapse
Hi, It is Galaxy Note 4 N910G
Hello, here is the latest twrp for your device
flash it through Odin:
https://dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar.html
Allow modification then go to wipe > format data > type yes
Then reboot to recovery again and flash the rom
-Hope- said:
Hello, here is the latest twrp for your device
flash it through Odin:
https://dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar.html
Allow modification then go to wipe > format data > type yes
Then reboot to recovery again and flash the rom
Click to expand...
Click to collapse
This actually helped. I was able to flash emotion rom, but I'm unable to flash the official samsung rom downloaded from sammobile. I downloaded the rom file twice, but it simply refuses to install, with the error "failed to map file" and "error installing zip file".
Hello,
Official Samsung ROMs are flashed using Odin, twrp only flashes image and zip files not tar files
Hi,
I was running the latest stock Android 8 firmware for the op6 with magisk & twrp.
I delayed the firmware update since month then yesterday I was forced to update.
My phone reboot everything was fine. no twrp & no root anymore because of the update.
I booted in latest twrp (fastboot boot twrp.img....) then I flashed the twrp.zip. After reboot I flashed magisk.zip.
After the latest reboot phone stuck for ~30 sec at the warning message saying boot-loader unlock blablalbla. then the phone reboot again and put me in twrp.
What can I do from there ?
Thanks for you help.
Julian.
Do I need to use this method to start from scratch ?
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
You have used the latest blue spark TWRP? If not you should do it
Try booting to the other slot
Deacon-Frost said:
You have used the latest blue spark TWRP? If not you should do it
Click to expand...
Click to collapse
I installed the last twrp on official website its not the one ?
I manage to boot the OS with a factory reset on twrp but I lost all my apps. only magisk app what installed. (because it was installed as a system app?)
I flashed the zip again and now it's everything is working but I can't install netflix... so it seems I'm not systemless :/
if you have any idea on how to make all the things right again it will be nice :good:
thanks for you help
foomanjackel said:
Try booting to the other slot
Click to expand...
Click to collapse
I'm still struggling with this A & B. last time I was on twrp it show me I was on B I think
you need to flash two times the full rom, flash rom flash twrp reboot to twrp, flash rom flash twrp, reboot to twrp flash magisk, reboot
Toni Moon said:
you need to flash two times the full rom, flash rom flash twrp reboot to twrp, flash rom flash twrp, reboot to twrp flash magisk, reboot
Click to expand...
Click to collapse
two time like on A and on B ?
how to boot A to B or B to A ?
when you flash one time and reboot to recovery and flash the rom again,you flash the rom in two slots, you didn't need change slots
I had the same problem, boot loops after rooting the recent OTA update. after soem troubleshooting with TWRP and not really getting anywhere I accidentally wiped the phone (stuck in the Chinese menus, was a mistake). prolly for the best, working great after re-flashing the OTA.
Toni Moon said:
when you flash one time and reboot to recovery and flash the rom again,you flash the rom in two slots, you didn't need change slots
Click to expand...
Click to collapse
Understood !
When I flash magisk for the last step do I need to swipe right "to allow modification"? if I want to be systemless?
A guy is talking about that here and I'm confuse about that => https://forum.xda-developers.com/showpost.php?p=76564294&postcount=6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.
crashykk said:
I unlocked my phone, installed TWRP through fastboot, booted recovery, wiped and installed LineageOS. System didnt wanted to boot up so I went back to recovery where I wanted to wipe all and try installing again.
TWRP didn't saw my internal storage. I didnt know what to do, so I decided to download MiFlash and install stock rom, but I got error: "error:Sending sparse 'userdata' 1/3 (740908 KB) FAILED (Error reading sparsefile)" and now my phone boots to fasboot mode.
When I try to go recovery I get stock recovery. Is there anyway to revive my phone? It's m2101j20sg model.
Click to expand...
Click to collapse
Reboot your phone and observe on the top part of the phone while there is the POCO logo showing.
1) If there is an unlocked lock icon on the top, you should be able to rescue with TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Type the fastboot code to get to TWRP again so you can flash ROMs.
Read here for ROM flashing tutorial.
https://forum.xda-developers.com/t/4288121/post-85137963
Step 16 is a must.
2) If you did not see this icon during booting POCO logo, chances are you accidently locked your bootloader with MiFlash. In this case, find Xiaomi repair center for warranty support.
I know how to flash a rom, but TWRP does not see my internal storage. Like it wasnt there.
edit:
I flashed Orangefox recovery and it did the trick. I was able to place some rom on internal storage and install it, but now i have 12 gb of storage instead of 233gb?
edit:2
I formated data and it went back to normal. Now i have my 256gb back.
I think you were encrypted, please read more online and follow rom flashing instructions. You didn't follow it that's why you were in trouble.
I flashed, rooted, unbricked a lot phones back in the Samsung S6 days. Even Redmi Note 5 Pro from xiaomi, but never heard of something like rom encrypting your access in recovery.
I didnt flashed custom roms on my Samsung s8 and s9, cuz they had fine software. MIUI 12 is so bad that I considered selling that Poco.
You didn't follow instructions, TWRP works perfectly fine. And the step you missed is Formatting Data partition after flashing ROM which decrypts it. (thus why you couldn't access internal storage or boot)
And you will run into same issue with OrangeFox aswell if you do the same mistake. Flashing procedure is a lot different in new smartphones.
I didn't follow, cuz I didn't know that flashing procedure is a lot different in new smartphones. I looked at it, it looked very similar, so I went with old habits. Now I know what to expect.