I have the Moto G Stylus from Metro, with the SofiaP board. It will not accept and boot any of the ROMs here! Not in fastboot or fastbootd. It's all unlocked. I've had the TWRP recovery on it. I can't install anything that will boot from there either! The first time I put TWRP on it, it absolutely shredded the fone's internals and put in EDL mode. So, what am I missing here? It'll take root and everything, but no ROMs? Not even a GSI ROM! Nothing! Everything but stock just makes it sit there and bootloop. Any assistance would be GREATLY appreciated! I love ROMs and I hate that I can't use any of these wonderful toys!
If you are on android 11, they wont work. You need to be on android 10.
You are an absolute lifesaver. Thank you very much! That's exactly what it was!
mptech7102 said:
I have the Moto G Stylus from Metro, with the SofiaP board. It will not accept and boot any of the ROMs here! Not in fastboot or fastbootd. It's all unlocked. I've had the TWRP recovery on it. I can't install anything that will boot from there either! The first time I put TWRP on it, it absolutely shredded the fone's internals and put in EDL mode. So, what am I missing here? It'll take root and everything, but no ROMs? Not even a GSI ROM! Nothing! Everything but stock just makes it sit there and bootloop. Any assistance would be GREATLY appreciated! I love ROMs and I hate that I can't use any of these wonderful toys!
Click to expand...
Click to collapse
How did you get out of EDL mode? I seem to have done the same thing. Ugh.
Related
Hello, I have bricked my lg g2, I started to try to unlock the bootloader on my phone so I could flash custom roms and such. Well, being the dumb idiot like I am, I used the wrong unlocker for the wrong variant of the G2. It was stuck in fastboot mode. As I was about to get out of the brick that I had, I deleted aboot. This was the real mistake. It wouldent let me put on the aboot.bin back into the phone because of some directory problem on my computer... (ended up being my fault... AGAIN...) well, now, It doesnt even boot anymore... It vibrates as if it would turn on, then just goes to an extremely dark screen (looks like it's still off...) I tried to put aboot.bin back into the phone via command prompt, I figured out how to find the directory of aboot.bin, but it just waits for the phone. If there is any way I can save this phone, I would love to. I am inexperienced in rooting androids and flashing and this whole root thing was a mistake :silly:
Thanks
- soups
delicioussoups said:
Hello, I have bricked my lg g2, I started to try to unlock the bootloader on my phone so I could flash custom roms and such. Well, being the dumb idiot like I am, I used the wrong unlocker for the wrong variant of the G2. It was stuck in fastboot mode. As I was about to get out of the brick that I had, I deleted aboot. This was the real mistake. It wouldent let me put on the aboot.bin back into the phone because of some directory problem on my computer... (ended up being my fault... AGAIN...) well, now, It doesnt even boot anymore... It vibrates as if it would turn on, then just goes to an extremely dark screen (looks like it's still off...) I tried to put aboot.bin back into the phone via command prompt, I figured out how to find the directory of aboot.bin, but it just waits for the phone. If there is any way I can save this phone, I would love to. I am inexperienced in rooting androids and flashing and this whole root thing was a mistake :silly:
Thanks
- soups
Click to expand...
Click to collapse
doubtful it can be fixed if it wont boot, but you can try asking your question in the g2 q&a. maybe some expert in your device forum can help.
Hey,are you able to boot into boot loader...if you can just lock the boot locker back and type the reboot command from PC itself
arunbiju969 said:
Hey,are you able to boot into boot loader...if you can just lock the boot locker back and type the reboot command from PC itself
Click to expand...
Click to collapse
sorry, but that is actually the worst possible thing you could do in this situation. locking the bl back will prevent you from flashing any further software if needed or possible, to fix this issue.
the g2 bl isnt unlocked as you suggest. it is bypassed with an exploit and not really unlocked.
bweN diorD said:
sorry, but that is actually the worst possible thing you could do in this situation. locking the bl back will prevent you from flashing any further software if needed or possible, to fix this issue.
the g2 bl isnt unlocked as you suggest. it is bypassed with an exploit and not really unlocked.
Click to expand...
Click to collapse
Ok, is there a command that I can use to boot back up?
delicioussoups said:
Ok, is there a command that I can use to boot back up?
Click to expand...
Click to collapse
its been a long time since i used my g2, thats why i suggested you ask in the g2 help forum in post #2.
please dont take my correction of the other guys post as there being a fix for yours. i really believe there is not, but his advice was blatantly wrong, so i had to correct it.
i think aboot is download mode/fastboot (if you have that). so deleting that when the phone cant boot is very bad. if the phone was booting, and rooted, it would be easy to put on a new aboot with dd code.
bweN diorD said:
its been a long time since i used my g2, thats why i suggested you ask in the g2 help forum in post #2.
please dont take my correction of the other guys post as there being a fix for yours. i really believe there is not, but his advice was blatantly wrong, so i had to correct it.
i think aboot is download mode/fastboot (if you have that). so deleting that when the phone cant boot is very bad. if the phone was booting, and rooted, it would be easy to put on a new aboot with dd code.
Click to expand...
Click to collapse
Alright thank you!
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
victor-zorro said:
Hi there,
I looked at a lot of places but I cannot find decent info. Or the Info I search .
So maybe someone can point me to, or may be this thread could be the one...
(And if I missed a post with the right answer, I apologise in front)
So lets face it, I bricked my Fairphone 2. Yep. Whoehoew. :highfive:
What did i do:
Flashed the latest twrp 3.2.2 recovery
Flashed Lineage os 15.1 with gapps pico and su addon
Playing around. Nice working phone. (it is my second, the first one was stolen )
I tried to encrypt my phone. But I encountered the camera reboot to recovery problem. so no encryption. (and really, this is an old bug...?)
Few days later I update lineage os. I just read about the flashlight on workaround. So I tried. And yep, it worked, straight to twrp.
But.
my guess is that now two things happen at the same time. a sort of postponed encrypting. And a non understanding update.
A least. I see the twrp logo. and that is it. If i reboot nothing happens. no os.
I can boot into adb and fastboot, at least, my macbook running high sierra shows the device with adb devices and fastboot devices.
If i am in fastboot, and try to overwrite twrp it stil reboots to twrp 3.2.2.0, so it seems to do nothing. (even an "update" to twrp-3.2.2-0-FP2 does nothing)
It looks like all is locked. My guess is that os wise usb debugging is off? Or that all is hanging an some corrupted mangle between code.
Is there a way to hard format the phone? Do I use software for that? Are I unaware of some "magic" fastboot commands?
Any help is highly appreciated
I also post this at the FF2 Community. But I will post back and forth whatever solution i find.
Cheers,
Vincent
Click to expand...
Click to collapse
Try reflashing it with the factory original firmware using their own flashing tool.
Once you got it working with that, then you can try flashing it with whatever you want.
Till then, there just too many variables with custom ROM.
I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
It seems most phones shipping with android 10 lose touch response in TWRP. Yes you don't have TWRP but I think you're seeing the same behavior.
Plug in a USB c mouse and navigate with that should help you restore normal use.
try this thread https://forum.xda-developers.com/t/stock-rom-for-motorola-g-stylus-retail.4104451/
tatsunn said:
I unlocked my bootloader and flashed boot.img with Magisk and patched, however now after rebooting my touchscreen no longer works and I cant access my phone.
Its basically a brick unless I can somehow undo this, but I cant find any instructions on flashing back to the stock firmware
If anyone could help I would really thank you.
Click to expand...
Click to collapse
Where did you get the boot.img? The non functional touch screen usually means the ROM version the boot.img came from doesn't match the version of the ROM running on the phone.
EDIT - Whoops, didn't notice the age of the post. Didn't mean to bring this back from the dead.
With every update until this one, I was able to keep root (download update, local upgrade via settings, install update, install magisk to inactive slot, reboot and done) but it did not work with this latest one. I tried mauro's toolkit but it didn't work either. What are my options to get root now? Thanks in advance!
https://forum.xda-developers.com/oneplus-8/how-to/guide-magisk-oxygenos-11-beta-1-global-t4160833
Flash the patched img!
I'm a ****ing genius. Managed to bootloop/temp brick my phone. MSM tool saved my ass but it took a usb 2.0 slot and lots of tries to get into edl mode. I am getting tired of fighting for root and it's such a jarring and unpleasant experience to suddenly lose root.
t-mizzle said:
I'm a ****ing genius. Managed to bootloop/temp brick my phone. MSM tool saved my ass but it took a usb 2.0 slot and lots of tries to get into edl mode. I am getting tired of fighting for root and it's such a jarring and unpleasant experience to suddenly lose root.
Click to expand...
Click to collapse
I feel you mate, when my phone arrived I immediately managed to brick it, but it's just part of the game. To be honest I found the unbricking and rooting pretty easy on OP8, I'm quite sure when the next OTA arrives you just have to follow the same method (installing magisk to inactive slot then reboot) just like in OOS10.
Recovered, tried again, same outcome. Patched image installed correctly according to the command prompt but actually resulted in a boot loop. Will hold off from Android 11 for now.
Are you flashing the right img? What's your ROM build version? I bet you flash a wrong img for your ROM. In the above mentioned thread there are only imgs for EU, global and Indian ROMs, if you using some kind of US specific ROM then tell me and I can make you a patched img.
https://oneplus.gadgethacks.com/how...factory-images-for-any-oneplus-phone-0249751/