Following up a guide to install CWM, I bricked my Huawei G610. It is on bootloop now. No Fastboot access too.
Any hardware key combination to re-install stock firmware including Recovery?
I recall few phones had a process to put ROM on SDcard and with special hardware key combinations, it used to re-flash fron SDcard.
Help will be appreciated.
sadnblueish said:
Following up a guide to install CWM, I bricked my Huawei G610. It is on bootloop now. No Fastboot access too.
Any hardware key combination to re-install stock firmware including Recovery?
I recall few phones had a process to put ROM on SDcard and with special hardware key combinations, it used to re-flash fron SDcard.
Help will be appreciated.
Click to expand...
Click to collapse
Check on need Rom G610 U20, Download ROM, unzip, theres a doc. file guide attached how to install..
Joe_Live said:
Check on need Rom G610 U20, Download ROM, unzip, theres a doc. file guide attached how to install..
Click to expand...
Click to collapse
Already followed that but it doesn't go to upgrade mode. Tried 2 SDcards so shouldn't be a bad SDcard issue.
If I plug the computer with Laptop, it detects phone but phone keeps rebooting hence I can't control the phone through SP Flash or ADB or other tools. Even in Fastboot mode, it restarts.
Same issue here
Any Luck with your device?
stuck in Bootloop
I faced the same problem after trying to flash TWRP recovery img. I used MobileUncle Tools to flash it. It asked Reboot in recovery, I pressed OK. and it never ran into recovery mode. Its stuck in bootloop now. Any way out? Have tried through ADB but fastboot doesn't work...
My problem was solved by Huawei. I claimed my warranty!
To solve this issue use sp flash tool without batry
Sent from my HUAWEI G610-U20 using Tapatalk
Help
thesumanthapa said:
I faced the same problem after trying to flash TWRP recovery img. I used MobileUncle Tools to flash it. It asked Reboot in recovery, I pressed OK. and it never ran into recovery mode. Its stuck in bootloop now. Any way out? Have tried through ADB but fastboot doesn't work...
Click to expand...
Click to collapse
I have encountered the same problem Is there any solution
sadnblueish said:
Already followed that but it doesn't go to upgrade mode. Tried 2 SDcards so shouldn't be a bad SDcard issue.
If I plug the computer with Laptop, it detects phone but phone keeps rebooting hence I can't control the phone through SP Flash or ADB or other tools. Even in Fastboot mode, it restarts.
Click to expand...
Click to collapse
hi I got the same problem today. can you tell me how did you resolve your issue long time ago.
thanks
Abbas
mobdanish said:
hi I got the same problem today. can you tell me how did you resolve your issue long time ago.
thanks
Abbas
Click to expand...
Click to collapse
Over 2 years now and I probably have changed 4 phones. Don't remember. But to help you. you may try this:
http://forum.gsmhosting.com/vbb/f810/huawei-g610-u20-bootloop-problem-1776731/
my phone isn't working, every time i open my phone it says "unfortunately, dev stopped working". and there are too many viruses that keeps on downloading. any idea how to fix this? huawei-g610-U20
Related
i cant boot my huawei u8180 into recovery
i rooted it by super one click
when i tried to flash recovery with rom manager premium it restarts then freeze in boot screen
tried to reset my phone from settings ,privacy it also reboot but freeze on boot
i dont know wt to do
PLZ HELP ME WITH THIS ISSUE
plz any one tell me anything i can do with this problem
i cant even reset my phone
plz reply
thanks guys , i solved my problem alone ,, and insalled cyanogenmod 7.2
everything is ok now
how do you solved your problem with huawei u8180? i have the same isue.
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Norpan70 said:
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Click to expand...
Click to collapse
So you could only boot into CWM by pressing power+volume+search? The regular way (power+volume) would lock up like it does to me, is that it?
Anyway I tried your key combination and it still freezes...
Codeman666 said:
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Click to expand...
Click to collapse
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Maeur1 said:
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Click to expand...
Click to collapse
I already flashed about 5 times and still freezes
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
bk109 said:
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
Click to expand...
Click to collapse
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Codeman666 said:
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Click to expand...
Click to collapse
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
bk109 said:
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
Click to expand...
Click to collapse
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Codeman666 said:
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Click to expand...
Click to collapse
Nothing specific -you just have to reboot in fastboot mode (just restart the phone while pressing Power and Volume Down. Windows should chirp and install the drivers automagically - afterwards just use that command discussed earlier and it should flash your recovery without any additional prompts (it should only print out a confirmation of a successful flash) and you should have the CWM ready to go
Edit: I put my device into fastboot mode on a clean Windows install (a Win8 Consumer Preview) and it did autodetect and install the relevant driver without restarting itself
No luck... Now it's driver issues
When booting the phone with either the vol up or down pressed and pluging in the USB my PC isn't recognizing the driver, I used both drivers you sent me.
Initially it's detected as Android 1.0 device, upon fetching the drivers it gets named "Android Sooner Single ADB Interface".
As I refresh device manager it goes back to Android 1.0 with an exclamation mark.
I think it's a driver signature issue, I'll try again in a couple of hours in a different PC
edit:in debug mode I have no driver issues and I can even detect my phone with ADB
Finally!
Tried it in another computer, auto downloaded some ASUS adb driver and installed fine.
Flashed latest CWM recovery with fastboot and now I'm able to boot into CWM!
Thank you so much for your help!
Sry for bumping.
So, i had the same trouble with the drivers. But i just downloaded HiSuite directly from the Huawei Site and these fix my problem with drivers to use adb without troubles . Hope this help someone.
BTW, Thanks bk109!
It did helped me thx man
Sent from my U8180 using xda app-developers app
Hi all!!
Yesterday i tried to install android 4.4 but the procces didnt succeed, it stuck at. LG boot logo. So i decided to restore my backup in ckockworkmod,it started the process then stopped at the phase "restoring /system" . I waited about a half hour, and because it didnt take the much time before, i took out the battery. I read somewhere that formatting the system partition in cwm could help, so i did that. Then i retried restoring my backup. It stuck at the same phase. Later i downloaded the official kdz, and decided to flash it. I could bring the phone in update mode, but the process stopped at 15% at lg update manager.
At the moment i can get into clockworkmod, but cant restore /system . The update mode is also okay. I dont know that fastboot works or not. I havent tried it yet. Please help me thanks in advance
@trapistasajt
You will need to get fastboot working and use lelus's fastboot script to flash the "u" and "x" loaders for the device and then perform the offline or online flash
http://forum.xda-developers.com/showthread.php?t=2292828
Also as you found out you cannot flash custom roms without ulocking the bootloader first and you cannot use the L9 CWM bootstrap recovery for Locked Bootloaders, too flash custom roms.
try this online flash methode with B2CAppSetup
http://forum.xda-developers.com/showthread.php?t=2085344
i had the same probleme and i fixed it .
My bootloader is unlocked. I tried the fast boot method, but it doesnt go further than "Waiting for omap...." . So, i couldnt go into fastboot (probably my fault). Yesterday i sent it to the service. If they notice that my varranty is void (because of the unlocked bl) and send it back, i will try it once more. I would be very thankful if someone could write a noob friendly-fastboot guide. As i read, lots of people are struggling with the same problem. Thanks in advance!!!
You have to use LGMobile Support Tool (Install drivers from it first) Then enter in download mode conecting the phone to pc pressing vol+ and the rest its automatic.
jufece said:
You have to use LGMobile Support Tool (Install drivers from it first) Then enter in download mode conecting the phone to pc pressing vol+ and the rest its automatic.
Click to expand...
Click to collapse
I installed the drivers but it didnt work
trapistasajt said:
I installed the drivers but it didnt work
Click to expand...
Click to collapse
what happened??
jufece said:
what happened??
Click to expand...
Click to collapse
It didnt go further than searching for "omap device", so i couldnt load fast boot, as i said. my phone is still in the service
If they 'll send it back to me, because of unlocked bootloader, i wil try it once more. Any suggestions?
trapistasajt said:
It didnt go further than searching for "omap device", so i couldnt load fast boot, as i said. my phone is still in the service
If they 'll send it back to me, because of unlocked bootloader, i wil try it once more. Any suggestions?
Click to expand...
Click to collapse
I dont know about fastboot.
LG Mobile support tool let you download the correct drivers. Then connect your phone while u keep pressing vol+ and it enters in SW Upgrade mode. Then just click "additional features" and "upgrade error recovery"
jufece said:
I dont know about fastboot.
LG Mobile support tool let you download the correct drivers. Then connect your phone while u keep pressing vol+ and it enters in SW Upgrade mode. Then just click "additional features" and "upgrade error recovery"
Click to expand...
Click to collapse
Thanks! What should i do after that? Or it will automatically flash v20h on my phone?
trapistasajt said:
Thanks! What should i do after that? Or it will automatically flash v20h on my phone?
Click to expand...
Click to collapse
It shows something about firmware ir will restore. Ir will flash the latestbfirmware from original carrier release.
For example i actuallybhave v20L but my original carrier only released v10a. It will restore to v10a
None of them works, other ideas?
This fastboot method worked for me in 5 min, pay close attention to the instructions and it works!
http://androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html
Spent days with LG update tool which if you read the log has no url for files to download.
Good luck!
I got my phone back from the service. They didnt repair it, because my varranty is void. I tried the methods mentioned above.
First, I tried flashing kdz, (with the solution for post-jb problem), but i couldn't get into S/W mode, which was available before the service.
Second, since i couldn't load S/W mode, the LG upgrader wasn't successfull, too
Third, fastboot still not work.
I am sure, that im not the only person with this problem, since it happened during installing @artas182x 's JB 4.4 rom. Please @artas182x or somebody write a noob-friendly guide/suggestion which may help to unbrick my beloved phone. Thanks!!!!!
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80120c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
raptorddd said:
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Edit: nvm I read what nuke download mode is (when no recovery and can't boot). I will try it now and see if it helps...
brickedvice said:
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Click to expand...
Click to collapse
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
raptorddd said:
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
Click to expand...
Click to collapse
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
brickedvice said:
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
Click to expand...
Click to collapse
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
raptorddd said:
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
Click to expand...
Click to collapse
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
brickedvice said:
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
raptorddd said:
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
Click to expand...
Click to collapse
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
brickedvice said:
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
Click to expand...
Click to collapse
i do not know either.. shortening the mother board is to enter download mode..
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
This thread here : http://forum.xda-developers.com/showthread.php?t=2449670 might help you installing twrp via adb
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Kingofiron257 said:
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Click to expand...
Click to collapse
Solutions:
1. Boot into recovery (Power + VolUp) and restore last backup (I really do hope you have a backup). It should be enough to restore just boot image. Mine ended in eRecovery few days ago after messing with Magisk and I've successfully recovered my device from there
2. Download original firmware, extract it, boot into fastboot (obv., try fixing it first, but you've flashed TWRP so it must work for other stuff, too) and just reflash original boot image
3. Download original firmware, extract it, boot into fastboot and reflash original recovery, then try eRecovery (this will probably wipe all your data, though)
There are tons of manuals how to extract Huawei/Honor firmware images (even a nice little program to do it for you), so I'd suggest searching around for that SW instead of asking how.
Kingofiron257 said:
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Click to expand...
Click to collapse
what recovery do you have now?? can you access twrp? or you are left with emui recovery??
if you have emui recovery, just perform a dload flash
Looks like he solved it.
adriansticoid said:
Looks like he solved it.
Click to expand...
Click to collapse
We need his solution , the one he tried
gopinaidu77 said:
We need his solution , the one he tried
Click to expand...
Click to collapse
Let's wait for his post.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Let's wait for his post.
Click to expand...
Click to collapse
Its been long he replied. Omg ,what is going ?
Stop. Spamming. The. Thread. For. Points.
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
lucasdeeiroz said:
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
Click to expand...
Click to collapse
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
adri_sefp said:
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
Click to expand...
Click to collapse
When did you buy this phone?
borksek said:
When did you buy this phone?
Click to expand...
Click to collapse
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
adri_sefp said:
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
Click to expand...
Click to collapse
did you manage to solve this problem?
claudiusuflea said:
did you manage to solve this problem?
Click to expand...
Click to collapse
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
that means there's no work-arround
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
Even if you do that, there's no blankflash for this model... as long as I know, I was looking forward to find it somewhere but there is none available.
claudiusuflea said:
that means there's no work-arround
Click to expand...
Click to collapse
That's correct, now my device shows nothing on screen, it is just black but when I plug the usb cable, fastboot detects it as fastboot mode, all commands are working but nothing else works.
I'm giving up now.
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
works if I have the bootloader still locked?
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
claudiusuflea said:
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
Click to expand...
Click to collapse
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
adri_sefp said:
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
Click to expand...
Click to collapse
Indeed, after flashing an Android 8 firmware my phone went into Qualcomm 908 EDL mode. After blankflashing and flashing the latest firmware had the same issue with "No bootable A/B slot". The same state before hardbricking the phone (AP Fastboot flash mode secure).
adri_sefp said:
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
Click to expand...
Click to collapse
maybe works "lenovo rescue and smart assistant"
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
No, lmsa would recognise the phones after A10 update, but the problem persists. Someone who has repaired this or someone who has managed to take it to the service or managed to revive the phone from this state? With locked bootloader
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
That didn't help either, there's nothing else we can do than replacing the main board.
Hello.
I have a similar problem. I have tried all of the methods listed, unfortunately nothing works. I ended up replacing the motherboard. The old PCB is waiting, maybe someday it can be repaired.