Related
PLEASE help : My phone stopped working after trying to change it to a L09 and now is dependent on the company's logo and does not accept any Software
You need to read about flashing from the bootloader using fastboot. You will be able to get it back working but you will need to get an extracted rom to flash the right parts.
Now I have a bit of time, I will tell you how I solved my issues. My phone was stuck with only the bootloader screen available or the eRecovery screen which would not find any suitable download. It said that the bootloader was unlocked yet I could not flash anything that I have extracted using the ROM extractor.
After much frustration I opened and ADB session and used Fastboot commands and re-entered the number in the Fastboot OEM Unlock command and it then confirmed that it was actually unlocked. It seems that although it said it was, it really wasn't.
Now that I knew it was unlocked, I could now start to flash parts of the extracted ROM.
I used the Huawei Rom Extractor tool to extract the Boot, Cache, Cust, Recovery, System and the Userdata image files of the ROM I needed and in this case it was the CRR-UL00470B110. I renamed the extracted files and removed the prefix numbers and put them in the ADB folder for ease of flashing.
I then used the Fastboot command to flash each part in the normal Fastboot format i.e. - Fastboot flash system system.img , and so on for each part. A reboot after brings it up in a nice new live usable phone. Well that is what I thought until I started to load the apps back on. I then noticed that I only had about 3gb left of my 64gb of memory! This took me a while to resolve and after more reading, more flashing of different ROMs I found the answer.
I had to flash the TWRP recovery using Fastboot, then format the data partition from TWRP. This restored the full size of the partition. Another flash of the correct recovery using Fastboot left me with a fully working unbricked Mate S.
I know that some of you may know all about this but I could not find any information and had to work through it myself and from various websites. I hope that this will help you to unbrick your phone.
I still think there may be something missing like the oeminfo file etc. but at least it works, you may just have to update it in future using adb and Fastboot if no OTA is available or works. Not too much of a worry now you know how to do it.
I should also add that if you ever get an 'Invalid Argument' when flashing in fastboot mode and some oparts flash while others dont, it will be your cable. Trust me, one cable workws well another gives you this Invalid Argument error! Strange but true and may catch you out.
Thank you(Sathelp) to help me to solve the problem of mate s mobile, but I found only three orders adb work when used fastboot screen, there are boot, recovery and cust but the system and other order give fault result in adb. Therefore the phone remain broken. ..sorry for language
Is it possible to provide me a complete backup copy of the phone to be downloaded to my phone via the twrp recovery , perhaps back to life again, I would be grateful to you
my p[hone is a U00 not a L09, so my back up will not work. Have you changed your cable, I had simular problem, changed cable and other ROM parts worked OK. If not, then you will need to ask for a L09 TWRP back up from here. May be someopne will make one for you.
Finally, the problem has been resolved and the phone returned to work and all this is due to the help of (Sathelp), which benefited greatly from his observations in this matter ,the issue has been resolved by updating the ADB and the execution of an order (FASTBOOT FLASH SYSTEM.IMG) , which i could not be implemented except adb updated, but the phone remained unresponsive for OTA updates and remained on the android 5. Thank to xda forums.
Glad it is now working
Huawei Mate S CRR-L09 bricked
Hi
I have a Huawei Mate S (CRR-L09) does not work and remains stuck on the android logo. Mention that is installed TWRP and I tried to "wipe data factory reset". I accidentally erased everything on it, including Systema. I did not back up your data and restore the system. I downloaded firmware B145 stock on which I copied to root your phone but, but can not flash TWRP. I entered the menu Update (Vol + Vol- and Power) but does not see that folder "dload". Can someone help me with a backup or a tutorial on how to flash TWRP firmware.
Thank you
Hello everyone, I have the problem, that my 3T boots to recovery every time I boot. The system is no more booting. What I did was, "updating" in the CM about/update menu (from unofficial cm14.1 13.12. to 14.12. ).
So maybe an open recovery script was created and booted to bootloader. Update failed but I did it manually.
From now on the phone does just only boot twrp recovery (or is it a boot loop ?). I tried to restore a backup and install the oxygen os via zip and wiped all partitions (except internal storage) but nothing helps. Does anyone know this and can give me advice ? Thank a lot in advance.
Edit:
For the OnePlus One if found an error report which look a little bit my error:
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
Click to expand...
Click to collapse
But the partition layout on the 3T seems to be different, I can see only partitions like sda etc ...
same here
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
Thank you!
Enviado do meu ONEPLUS A3003 através de Tapatalk
Thnaks so much
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
:good:
I follow your recommendation thanks for your assistance I fixed my OP3T,
What a mess ... after all this I wanted to install my CM backups again, but TWRP refused to boot. I had only a black screen with a white LED when going to recovery. But now after some hours I have a solution to this. You need to update Oxygen OS before going on !!
Make a full system update or flash this update via TWRP: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.3/
After this TWRP is booting as expected.
Now I'll enjoy a beer or two or ....
Good luck to all others. If anybody needs assistance ... contact me.
never had a issue
Please help!!!! I tried flashing the update for the latest OTA, I had the full zip. I have unlocked bootloader, twrp, phh supersu, magisk and xposed. I did a nandroid backup and then clicked Wipe- Dalvik and Cache. I then flashed the zip. For 20 mins the boot logo was spinning around, so I rebooted into twrp to see what was going on. Now I can't reboot and it shows no data, it says my device is encrypted and I can't see any files. What can I do??
Was your internal storage encrypted before ?
TWRP doesn't show your internal storage and didn't ask for a password ?
fix bootloop
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
I solved the problem
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
RE
TOMASITO95 said:
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
Click to expand...
Click to collapse
how ? can you please teach me ( my op3t didn`t go to system is says " md5 checksum failed , recovery failed , boot failed , system failed , boot_aging failed , dsp failed , modem failed please help me (
Change USB port
Try a different USB port. I flashed it through a 2.0 USB port instead of the 3.0 and no checksum error!
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
sabbath88 said:
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
Click to expand...
Click to collapse
Just flash a custom recovery, the device even had the offical twrp. So?? Just not into fastboot and then flash the recovery by the -- command
fastboot flash recovery recovery.img
(You have to rename the twrp file to recovery or whatever, just write the image file name instead of recovery in the second one. Ex fastboot flash recovery 123.img)
Then command
Fastboot reboot
(Hold the power up button for booting into twrp before hitting enter)
Download a miui recovery rom for your device from anywhere, I don't know I'm lazy.
And before flashing, go into mount select vendor and system if not selected.
And then select wipe
Advanced wipe
Select vendor system data cache.
Swipe to clean
Move the rom to your device
(If your device does not show up in your pc, then go into mount (twrp) select enable MTP if it's disabled, if it shows disabled then enable it again)
After that just flash your rom and then a permissive patch you can ask anyone. Or just flash pitchblack recovery. Fixed my problem of not not booting.
Sorry for the wrong format, wrote it on mobile, as I am a lazy bum.
Wut bruh.
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
ChakibDEV said:
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
Click to expand...
Click to collapse
thanks so much, that helped
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authenticated mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
As redmi 9 is mtk based device so their is not any edl point...if you have authorized account then you can easily flash it without the device open
Just use older preloader.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
That I have an authorized account was a wrong information.
When I try to flash it with sp_tool the following error is displayed: STATUS_CRC_BROM_FAIL 0xC0060005
PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
Disable authorization and unbrick your Redmi 9
Now you can unbrick your device even if the redmi logo not coming..just go to below link and follow their steps.... https://megafon929.github.io/mtk For more information and how to do follow the below post...
forum.xda-developers.com
Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
Oh well, a phone that turns on in fastboot is not a big problem you'll say, and I thought the same as i previously had a problem and solved it by reflashing the stock rom in fastboot, so I took my nice computer (actually it's a 12 year old pc that runs on carbon, but that does its job), I opened the mi flash tool, connected the phone, selected the fastboot rom, precisely the EEA 12.5.7.0 (like the one natively installed before the damage) and started the installation. 20 minutes later ... error: cannot load bla bla bla, ok ok, i seached various solutions on Google and tried every metods, i changed the directory of the mi flash, of the rom, I updated the version of mi flash, i installed both on C:/ drive, reinstalled the drivers, i edited the batch file to remove the anti rollback but nothing, it arrives at flashing the super image and after some minutes it fails the flashing. Before you ask, YES, the bootloader was unlocked. I also tried to flash the rom in twrp, but ... the phone no longer had the twrp. The only way to start it was via command (fastboot boot twrp.img), the onekey injection did not make it permanent, and connecting the phone to the pc it revealed the device, but not the internal memory, I tried to make a format data but nothing. I managed to make it permanent only once, manually flashing only the vendor_boot and boot images in one of the boot_ * slots, in that case incredibly the pc also detected the internal partition, I copied the flashable rom and ... the twrp said to restart the recovery for I don't remember what, but basically I couldn't install the rom via twrp. At that point I finally gave up and took the phone to an authorized xiaomi service center where they fixed it (bye bye 25€), I don't know how exactly, I would opt through edl mode I think, and now i have my working phone...but heeeeeey, they flashed me the 12.0.1 TW version, not the EEA... Ahhhhh come on. They also re-locked the bootloader, so... agaaaain i re-unlocked the bootloader, this time i downloaded the unofficial tool xiaomi flash tool v2, it installed every needed driver, i clicked on "my phone works and i want to mod it", this time i tried to flash the global rom 12.5.7.9 and when it arrives at flashing the super image IT FAILS (fast boot flash_all failed, exit code:1, output: flash super error), and like a nightmare the phone was stuck in fastboot again, fool once but never fool twice, this time I had previously made a twrp backup of everything except the data partition, I install it and the phone restarts perfectly, I also notice that despite the attempted flash of the rom in fastboot after restoring the twrp backup without the data partition, nothing has been deleted from the data partition. So benevolent gods of xda, how the heck should I change rom region? Thanks for your attention and I hope I haven't stressed you out any more than I already am.
you are probably uploading rom miflashem pro and hence this error - I had the same. Use miflash's built-in pro miflash and it should go - it worked for me
SpYneX_ said:
Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
---
Click to expand...
Click to collapse
1/ OMG, take your time, espace your words, compact your questions...
2/ For old configuration a user have fix adb/drivers/detection problem with an another driver pack, and a old is btter than the lastest for some old configuration (so if your conputeur jhave 12 years, maybe...)
So try to install this drivers here
Change your USB port and verify your cable
3/ If problem occur, change computer (family/friend computer), just for flash, for be sure it's a communication/usb/detection problem
PS : Finally, why trying to overclock a soc already overclock by Snapdragon and always overheat ? It's really want finding problems ^^