Here's the background on how it got bricked
i tried unlocking bootloader whcih went succesfully.
then flashed twrp, also succesfully. Could boot into it and the rom
So i started flashing a custom rom without a backup..erased system,cache,dalvik,userdata etc and went into flash rom but it was 64bit rom but my twrp was 32 bit.
i tried installing 64 bit one but phone wont boot into it.
so i decided to flash stock through fastboot
i downloaded a rom which was for moto g5 plus...i didnt realised 5s plus and 5 plus were two different phones...fricked up there
i went to reboot and the phone just went blank, wont display anything,wont boot or any response at all.
but its being recognized as Fastboot Sanders S on my PC and i can access fastboot but phone wont turn on no matter what roam i flash through fastboot.
I was on latest Oreo 8.1 august patch and the flashing goes smoothly, only getting error in bootloader...."security downgrade" stuff
Is there a way i can fix this or is the device just gone?
{
"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"
}
[/IMG][/IMG]
dr3mz said:
Here's the background on how it got bricked
i tried unlocking bootloader whcih went succesfully.
then flashed twrp, also succesfully. Could boot into it and the rom
So i started flashing a custom rom without a backup..erased system,cache,dalvik,userdata etc and went into flash rom but it was 64bit rom but my twrp was 32 bit.
i tried installing 64 bit one but phone wont boot into it.
so i decided to flash stock through fastboot
i downloaded a rom which was for moto g5 plus...i didnt realised 5s plus and 5 plus were two different phones...fricked up there
i went to reboot and the phone just went blank, wont display anything,wont boot or any response at all.
but its being recognized as Fastboot Sanders S on my PC and i can access fastboot but phone wont turn on no matter what roam i flash through fastboot.
I was on latest Oreo 8.1 august patch and the flashing goes smoothly, only getting error in bootloader...."security downgrade" stuff
Is there a way i can fix this or is the device just gone?
[/IMG][/IMG]
Click to expand...
Click to collapse
If you got fastboot, then just flash the stock firmware and boot it. Note:- remove bootloader and gpt commands from the fastboot so it won't get brick.
Related
I'm a newb..
Atrix HD with unlocked bootloader and rooted. Installed cwm recovery, flashed to the latest nightly cm 11 for atrix hd, rebooted and stuck at cyanogenmod loading screen (head with the spinning circle around it). left it that way over night with no change still stuck on bott.
I've spent several hours following several guides with no success
I think the problem started whn I did a factory reset and clear cache in cwm before I flashed cm 11. it gave an error on data or something.
fastforward several hours later I now have philz touch 6 recovery which I read on this guide http://forum.xda-developers.com/showthread.php?t=2577447 you could use to fix the corrupted data partition. problem is when booted to philz recovery the driver for phone is not installed correctly.
{
"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"
}
The phone is recognized fine in fastboot mode however.
Is there a way to fix the corrupted data partition using fastboot?
I've already tried fastboot -w and reflashing but that did not work.
I have the latest motorola drivers and latest sdk with google usb installed etc.
Unfortunately I was stupid and didn't make a nandroid backup so I hope there is another way to get this phone working.
thanks
Solved
After 2 days of monkeying around I finally got it fixed.
I never could get the phone recognized in recovery mode (philz mod) and using ADB as suggested by the guide I linked.
Finally what worked is I downloaded the stock rom zip, extracted it, edited the xml file in MS word deleting the 2 lines with "getvar" in them, booted the phone into fastboot mode, connected the phone to my PC and made sure it was recognized in device manager, loaded the xml from the stock rom into RSD Lite and flashed back to stock, rebooted, and all was working fine.
I know there's a million and 1 guides that say to do what I just described and believe me I tried the exact things I posted above for the better part of 2 days and rsd lite would always fail with some kind of error. Finally I rebooted my PC, downloaded the stock rom again, edited the xml, and tried one last time and it finally worked...I don't know what made the difference.
Now if I could just find a trick around this darn subsidy (hard) lock this Atrix HD would be back in business.
Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"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 mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:
Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!
Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!
Basically i have been trying to root my phone (Redmi 9c) everything was going well until i got to the pathching the boot.img with magisk and got the error
'booting...
FAILED (status read failed (Too many links))'
and after that i was stuck on a boot loop i looked for a guide and i re-flashed (not sure if i'm using the correct terminology. sorry im a noob) the original xiaomi angelica boot.img it fixed the issue but i was still not rooted i went to another guide everything went smoothly until i got to the booting part and...... got the same error i have tried everything, (changing charger, usb port, using windows power shell and normal CMD) and nothing all i get is this:
{
"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"
}
and once again to a boot loop. i have tried re-flashing the factory boot.img and nothing. Im seriously starting to go insane because i cant fix this problem and can't get the phone to boot again or even find something to help me.
thanks to anyone who might help me in advance
Elizabeth_304 said:
Basically i have been trying to root my phone (Redmi 9c) everything was going well until i got to the pathching the boot.img with magisk and got the error
'booting...
FAILED (status read failed (Too many links))'
and after that i was stuck on a boot loop i looked for a guide and i re-flashed (not sure if i'm using the correct terminology. sorry im a noob) the original xiaomi angelica boot.img it fixed the issue but i was still not rooted i went to another guide everything went smoothly until i got to the booting part and...... got the same error i have tried everything, (changing charger, usb port, using windows power shell and normal CMD) and nothing all i get is this:
View attachment 5373903
and once again to a boot loop. i have tried re-flashing the factory boot.img and nothing. Im seriously starting to go insane because i cant fix this problem and can't get the phone to boot again or even find something to help me.
thanks to anyone who might help me in advance
Click to expand...
Click to collapse
Hey has it been sorted out already? Try flashing with fastboot ROM. Also see thread about rooting redmi 9c under guides
You cant boot into recovery from fastboot command, just enter recovery manually by pressing vol+ and power button.
Hello,
I've been trying to install Pixel Experience on my phone following these guides
Install PixelExperience on NB1 - PixelExperience Wiki
Install PixelExperience on NB1 - PixelExperience Wiki
wiki.pixelexperience.org
Nokia 8 (NB1) Full ROM Installation Guide
In this guide, you will find: What you should do before installing a custom ROM on your Nokia What are the button combinations of Nokia 8 for reboot to download mode, recovery mode, and etc How to install T-Virus (project treble) on Nokia 8 How...
forum.xda-developers.com
Just as described I've downloaded Nokia drivers. My phone already had unlocked bootloader via official HMD method so i went over to the next step and T-Virus.
I entered fastboot sucesfully by enabling USB debugging. Downloaded T-Virus from the guide link and executed Windows command. Followed all steps in command window.
During the process I've noticed repeating error "Invalid sparse file format at header magic" if it's important.
Anway it finished and said that my phone will enter ROM now but after restarting it's back at bootloader.
I tried entering recovery via key combinations but they won't work.
I can detect my phone in fastboot and even when i type in
fastboot reboot recovery
It will still reboot into download mode.
Any help appreciated how to get my phone to work again.
Okay, crisis averted, I reverted T-Virus and now i can boot to android again.
But I still want to know why T-Virus failed and cause bootloop on my device?
I've noticed that despite having unlocked bootloader my critical is locked. Could t
{
"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"
}
his be the source of issue?
Yup that was it.
I had to repeat fastboot flash unlock unlock.key and then fastboot flashing unlock_critical to get critical unlocked and now T-Virus installed without any issues.
Hey got the same problem, how did you revert and unlock critical?
Hi good evening, this is my first post in xda, I've used the forum since my first android back in the htc era, since 7 years I used my s8 with the hadesRom and everything was amazing, then I've broken my beloved s8, really the best smartphone ever, and I've bought an s10 a couple of month ago
Then, yesterday I start to follow the Magisk guide for unlock the bootloader and root my S10 G973F-DS and after it the the one for install the TWRP with the PlayStore method.
Unlocked the bootloader, rooted it, Magisk was installed, then I had the first problem: the internal storage was down to 25gb, I've wiped from recovery data and cache and the storage came back to normal, I've installed the twrp with the appstore method, rebooted to twrp, and wiped again data and cache as said in the hadesRom install guide and then all the system was gone, the twrp refuse to reboot to the stock one so I've tried to flash the HadesRom and now it's stuck in the Samsung GalazyS10 bootup splash screen, it just reboot with Bixby+volumeDown+Power but it always just go back to the splash screen, it doesn't recognize any other button sequence neithe the adb devices recognize it...
can I save it?
Thanks in advance..
Use ODIN to flash latest firmware again. Then use ODIN to flash LineageOS, then install lastest PixelExperience and boot on it. After boot PE, use ODIN again to flash TWRP and flash any rom u like.
Thanks for the answer, but I can't flash anything, it's stuck in this splashscreen, It only reboot with volume- bixby and power, but it just goes back to this one again.
I've tried flashing the orIginal fw, but it's not recognized by Odin so if I start Odin nothing appens actually.
{
"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"
}
Samsung Galaxy S10 G973F Test Point – EDL 9008 Mode
By using the Samsung Galaxy S10 G973F Test Point, you can easily restore the stock ROM, bypass FRP lock, or reset user data on your device via UFi Box. In
www.mobilerdx.com
This link may help u