Related
So I've been following unbricking tutorials, and I have fastboot. Serial number is the 0123456789 ABCDEF thing, ifwi is 0094.0177, bootloader and hw version are unknown, and signing and secure boot are ?. So I've tried asus flash tool, and it tells me error 1, and if I check the logs it ends at "fastboot oem partition /tmp/partition.tbl." I've followed a tutorial to do it manually, and whenever I get to "fastboot oem partition /tmp/partition.tbl," it tells me gpt partition error. Recovery doesn't work, but I was able to boot into temp twrp and cwm. They both can't mount anything, and twrp tells me I have 0 mb of internal storage. Is it fixable? Thanks in advance.
135hussein said:
So I've been following unbricking tutorials, and I have fastboot. Serial number is the 0123456789 ABCDEF thing, ifwi is 0094.0177, bootloader and hw version are unknown, and signing and secure boot are ?. So I've tried asus flash tool, and it tells me error 1, and if I check the logs it ends at "fastboot oem partition /tmp/partition.tbl." I've followed a tutorial to do it manually, and whenever I get to "fastboot oem partition /tmp/partition.tbl," it tells me gpt partition error. Recovery doesn't work, but I was able to boot into temp twrp and cwm. They both can't mount anything, and twrp tells me I have 0 mb of internal storage. Is it fixable? Thanks in advance.
Click to expand...
Click to collapse
Can you connect in bootloader again , also load everything to AFT ,then whilst attached to pc ..then press vol+ once ?
Is the serial corrected now ?
Nope nothing. Still the same.
135hussein said:
Nope nothing. Still the same.
Click to expand...
Click to collapse
Have you used xFSTK on this device ? Did you buy this device in this state ?
If you did use xFSTK , then i would reflash again and follow my unbrick procedure in the link in my signature for correcting serial during the two part flash in AFT.
If you did buy this device in this state , then somebody could`ve incorrectly flashed wrong files in xFSTK
.
Going off your ifwi version , you have a 551 , but if someones flashed a 550 with 551 files (which i`ve witnessed on here ) then anything and everything could go wrong.
timbernot said:
Have you used xFSTK on this device ? Did you buy this device in this state ?
If you did use xFSTK , then i would reflash again and follow my unbrick procedure in the link in my signature for correcting serial during the two part flash in AFT.
If you did buy this device in this state , then somebody could`ve incorrectly flashed wrong files in xFSTK
.
Going off your ifwi version , you have a 551 , but if someones flashed a 550 with 551 files (which i`ve witnessed on here ) then anything and everything could go wrong.
Click to expand...
Click to collapse
Yes, I've used xfstk, and whenever I try it, it ends at 11%, and yells me usb_bulk_read() windriver error. I've tried the files from multiple posts, all ZE551ML, but still no luck.
135hussein said:
Yes, I've used xfstk, and whenever I try it, it ends at 11%, and yells me usb_bulk_read() windriver error. I've tried the files from multiple posts, all ZE551ML, but still no luck.
Click to expand...
Click to collapse
Thanks for that , when you get success in xFSTK you will then get temp bootloader 0094 0169 , then if incorrectly flashed raw in AFT you get 0-F serial or if correctly flashed 0-F to start with which is normal but then following the two part flash procedure , it then gets corrected -- Flashed incorrectly or correctly in AFT will leave you with 0094 0177 bootloader.
So , correctly flashing now in xFSTK seems the way to go .
So i am assuming you did get success at some point in xFSTK but are now no longer -- am i right ?
timbernot said:
Thanks for that , when you get success in xFSTK you will then get temp bootloader 0094 0169 , then if incorrectly flashed raw in AFT you get 0-F serial or if correctly flashed 0-F to start with which is normal but then following the two part flash procedure , it then gets corrected -- Flashed incorrectly or correctly in AFT will leave you with 0094 0177 bootloader.
So , correctly flashing now in xFSTK seems the way to go .
So i am assuming you did get success at some point in xFSTK but are now no longer -- am i right ?
Click to expand...
Click to collapse
Thanks for taking the time to help me. I've never gotten success in xFSTK. Always windriver error. I thought I had divers installed incorrectly, since that's what it sounds like, but after reinstalling multiple times, still nothing.
135hussein said:
Thanks for taking the time to help me. I've never gotten success in xFSTK. Always windriver error. I thought I had divers installed incorrectly, since that's what it sounds like, but after reinstalling multiple times, still nothing.
Click to expand...
Click to collapse
Okey so we need to try and get xFSTK to run successfully , i`m not sure whether it part flashing to a certain percent corrupts but i think it must have in your case.
1 if xFSTK Downloader opens up and you can fill in the files , then isoc driver is installed correctly.
2 you are putting in gp over ride value at 0x80000807 in the bottom section that ends in [bla bla CRC] ?
and ticking the box ?
3 you are running xFSTK as administrator too?
---------- Post added at 07:37 PM ---------- Previous post was at 06:56 PM ----------
A few things to try going off what you have give me so far , if above you understand and have already preset in xFSTK -- Try, uninstall AFT -- uninstall xFSTK -- clean pc with ccleaner , registry too(free)
reinstall xFSTK from my files in my unbrick thread in my signature -- the 3 files for xFSTK are there too.
Power off pc , power off phone but leave connected to pc.
Reboot pc -- when set up -- power up phone to bootloader and repeat xFSTK flash with my files.
@135hussein
Hows it going ?
Sorry for not replying sooner. I've been busy. Will try this tomorrow, and I'll get back to you. Thanks for the help.
Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)
Hey guys!
Hard-bricked my Z00AD, I'm able to get to bootloader using xFSTK but AFT flashing fails over and over.
Tried flashing with a couple raw images I found, waited an hour for one to complete and got nothing, then waited 7 hours for the other, still no go. currently have it running with a 2.20.40.139 image that I downloaded from this guy's video: https://www.youtube.com/watch?v=BboYFzgg7Jo
Also searched the forum a bit and found a couple more images that I'm currently downloading (2.15.40.13 and 2.20.40.196, gonna try to revert to android L with the first one, maybe it'll work)
It just gets stuck at the "Flash image" stage with "RESULT: OKAY" on my device.
Tried flashing manually with a later firmware after supposedly cleaning the partitions (I.E. sideloading via fastboot to flash splashscreen, droidboot, boot, recovery and system of the latest firmware) and nothing happened.
ATM Also downloading the 2.20.40.139 zip firmware to try and manually flash the same firmware on the device.
Any suggestions?
Thanks!
Hi @firecharge , there is a two part flash ritual to flashing raw file first part your serial is 0 - F
First flash,is approx 3 mins , where/when it says "RESULT =OK "
close flashtools , force close it. Keep phone attached.
Open /run flashtools again input raw again , press vol+ on phone and serial will be corrected this time ,start 2nd flash and let the second flash complete and it will boot into system by itself.
There is a unbrick thread with vid in my signature showing exactly this , from 2:17 mins in
Here
https://m.youtube.com/watch?feature=youtu.be&v=PmbRaJijIBs
timbernot said:
Hi @firecharge , there is a two part flash ritual to flashing raw file first part your serial is 0 - F
First flash,is approx 3 mins , where/when it says "RESULT =OK "
close flashtools , force close it. Keep phone attached.
Open /run flashtools again input raw again , press vol+ on phone and serial will be corrected this time ,start 2nd flash and let the second flash complete and it will boot into system by itself.
There is a unbrick thread with vid in my signature showing exactly this , from 2:17 mins in
Here
https://m.youtube.com/watch?feature=youtu.be&v=PmbRaJijIBs
Click to expand...
Click to collapse
Thanks for the quick reply
Tried that, the serial on the device does change but afterwards it doesn't recognize it ever on the flash tool or in fastboot (says "fastboot cmd waiting" on the device, tried to check fastboot devices on cmd and it doesn't appear, same for AFT v1.0.0.24)
@firecharge
Have another go with 1.17 AFT download in my unbrick thread.
If nothing gained from that , maybe related to fastboot cmds you flashed earlier so might need to re xFSTK flash again , then re two part flash raw file
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
PS , run aft as admin.
Check you are highlighting serial number before starting flash like in video, that line turns blue
timbernot said:
@firecharge
Have another go with 1.17 AFT download in my unbrick thread.
If nothing gained from that , maybe related to fastboot cmds you flashed earlier so might need to re xFSTK flash again , then re two part flash raw file
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Click to expand...
Click to collapse
Tried to re xFSTK flash with files downloaded from your thread, still has the same result.
Bootloader reads:
Product_name - Z00A
Variant - Asus_Z00A
HW_Version -
Bootloader Version - unknown
IFWI version - 0094.1069
Serial Number - some number other than 0-F
Signing - ?
Secure_boot - ?
Again, tried to disconnect and reconnect phone to USB cable, does that recognition sound but isn't popping up on fastboot or AFT.
Did you buy this phone in bricked state ?
Reflash xFSTK .
Do not flash cmds in fastboot
Two part flash raw
Works
Everytime
timbernot said:
Did you buy this phone in bricked state ?
Reflash xFSTK .
Do not flash cmds in fastboot
Two part flash raw
Works
Everytime
Click to expand...
Click to collapse
Didn't buy the phone bricked, bricked it myself accidentally
Reflashed xFSTK
**Did not flash in fastboot** - fastboot was a measure of seeing if the phone is recognized - which it's not after the first raw flash. -Which is exactly my problem
For some reason the phone does recognize that it's supposed to be in fastboot mode - saying "fastboot cmd waiting", but my pc can't recognize it.
Gonna give it another try with xFSTK then two part as you say, if it doesn't work I'm gonna try it on another machine and see if same happens there.
Good stuff
Your first flash in AFT when it said 'result ok' shown fastboot was working , then you messed about in fastboot sideloading or whatever ,and then no longer with a serial other than 0 to F .
Shows , you did something there to damage the process.
Hopefully it can be fixed now , fingers crossed.
Messing about in temp bootloader with incorrect fastboot commands leads to loss of serial and of course imei.
It really does only take 15 mins from brick to system , flashing this method and safer should errors occur by flashing incorrect fastboot cmds at a critical stage
timbernot said:
Good stuff
Your first flash in AFT when it said 'result ok' shown fastboot was working , then you messed about in fastboot sideloading or whatever ,and then no longer with a serial other than 0 to F .
Shows , you did something there to damage the process.
Hopefully it can be fixed now , fingers crossed.
Messing about in temp bootloader with incorrect fastboot commands leads to loss of serial and of course imei.
It really does only take 15 mins from brick to system , flashing this method and safer should errors occur by flashing incorrect fastboot cmds at a critical stage
Click to expand...
Click to collapse
Thanks for the assistance - My fix was this:
Did the xFSTK to get to bootloader
Flashed once with AFT
Then going to another computer I flashed for the 2nd time since it was recognized and now I have the firmware installed properly and my phone is back up and running.
@firecharge
That WAS hard work
Wow lmao .
Messing with your phone , gives other people headaches
PS hit the thanks for me saving your life ???
Or next time you feck up , no help from me
OK back to plastering the walls , no rest for the wicked , funs over
timbernot said:
@firecharge
That WAS hard work
Wow lmao .
Messing with your phone , gives other people headaches
PS hit the thanks for me saving your life ???
Or next time you feck up , no help from me
OK back to plastering the walls , no rest for the wicked , funs over
Click to expand...
Click to collapse
Pushed that thanks button hard bro
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp
pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Is your bootloader (still) unlocked and do you have access to fastboot?
Veran125 said:
Is your bootloader (still) unlocked and do you have access to fastboot?
Click to expand...
Click to collapse
Yes, bootloader's still unlocked and i have acces to fastboot.
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Thanks for your magic answer, but i can't find your toolkit, BUT i found this https://forum.xda-developers.com/mi...ol-tool-one-driversunlocktwrpfactory-t3866191. Is it good also ?
You can just get newest fastboot rom, and then flash with Miflash
Veran125 said:
You can just get newest fastboot rom, and then flash with Miflash
Click to expand...
Click to collapse
If it was too simply ... I think i did that already, But fastboot room, what do you mean with that ?
I just want, now, to be sure, can i save my phone ? It's not dead ?
Cause it's a very good phone and i don't want to loose it, really.
Nope, it's not dead, even with locked bootloader it wouldn't be. But now that you've got an unlocked bootloader, it's very easy to restore
I'm more happy so, 5 hours ( no fake really ) i search a solution .... SO
I found a global rom without .bat files in this folder so i got an error with Mi Flash Tool .. Tell me more about your idea
What's the error if I may ask?
Veran125 said:
What's the error if I may ask?
Click to expand...
Click to collapse
Can not found ( don't remember the file name).bat
FamosoFT said:
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Click to expand...
Click to collapse
-Tente isso:
Download this official rom: https://en.miui.com/download-354.html
Download this Mi Flash Tool: http://api.en.miui.com/url/MiFlashTool
*I'm assuming you already have the ADB drivers installed on your PC
*Remember to check the CLEAN ALL option
-If the above method does not work, do the following:
* It will only work if you do not have TWRP installed, if it is with twrp installed, I recommend reinstalling the original recovery *
1-Turn off the device and press (POWER BUTTON + VOLUME UP). At that point, the android doll will appear and spelled 'NO COMMAND'
2-Press only (POWER BUTTON) and click quickly (VOLUME UP BUTTON). In this screen you will see the recovery options, use the volume buttons to go to the WIPE DATA/FACTORY RESET option, confirm with YES and restart the device.
3- Wait patiently for 3/5 minutes.
-If none of this works and you can still access twrp, I recommend you try installing a GSI rom using this method: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-functional-twrp-magisk-pie-gsi-t3900119
I recommend this GSI rom (I'm using this now): https://get.resurrectionremix.com/?dir=gsi (choose 'arm64-ab')
This will give you a working system and make it easier to return to stock.
Hope one of these methods helped!
Hi all,
The problem was my PC i had not the .bat files so it couldn't work ...
Thanks @Bruno_Designer for your message, but i hate RROS but you're solution was good
FamosoFT said:
Hi,
My phone is bricked, cause i used twrp temporaly, to install a new rom, but after an unexpected wipe my phone lost OS files so i'm just able to use adb & fastboot with the fastboot mode, so lock & unlock oem principaly. Please help me it's very very important cause i need to use this phone ...
Thanks.
Click to expand...
Click to collapse
If u alredy used twrp den u have adb.
U need mi flash tool.
Download any one of the full fastboot roms for Mi A2 Lie below:
9.6.4.0: https://xiaomifirmware.com/download/10399/
9.6.10.0: https://xiaomifirmware.com/download/10867/
10.0.3: https://xiaomifirmware.com/download/11586/
So to revive ur fone, u do dis. Dis was how i did mine.
1. After downloading a rom of choice, u extract on ur pc using winrar, 7zip or izarc. U basically open the archive using any of these software n copy out the folder contained. The name usually starts with "daisy global ...."
2. U open the extracted rom folder. U will see a bunch of files including "flash_all.bat" etc and a folder called "images".
3. Click on the address bar of d rom folder and copy the address. Den open "mi flash tool" and paste d copied address in the mi flash tool address bar n click on refresh.
4. Boot ur phone to fastboot mode, using "power" & "volume down" buttons together.
connect d phone to ur pc via usb cable.
5. Open ur adb folder and open the adb command window.
Type in the following, one after the other n click enter:
" fastboot devices " dis to confirm the adb connection
" fastboot oem edl " dis to enter edl mode. Ur fone led starts blinking at 1sec intervals.
6. Back to mi flash tool, u click on "refresh". After a second ur fone should be seen as a COM port "COM 10"
7. At d bottom right, u shd find 3 options. Selct "clean all". This shd leave ur bootloader unlocked after the process.
8. U click on "flash" button at the top right. All things going well, within 10 mins the process shd be done and u will see "green" indicator with "success".
9. Hold ur fone n press d power botton for 10 secs. Then ur fone shd power up. Give ur fone exactly about 5 mins to come up "look at the clock & dnt assume"
Dis is an edit of others tutorials. But this is exactly how it worked for me. As long as u use any of the 3 roms i linked u.
Unless i use edl mode, it jus doesnt work for me.
Good luck. Leta know how it goes. And pls click thanks if i helped u.
Problem solved
Thread closed at OP request
Hey,
i have a Moto G5(cedric , xt1677) .
i had recently flashed stock rom (CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) using RSD LITE tool.
When i tried booting( volume down +power ) into recovery it wont boot and it would be looping the bootloader( the bootloader comes and goes then repeat). I tried quickly pressing start to boot the device but it wont boot and keeps restarting the bootloader page. So i removed the battery and tried pressing the power button only it booted the system successfully.
i tried usb debugging there was no notification and adb didn't detect it. (it was already on in dev options).
then i used magisk manager(it was already installed and i was getting root access) to boot into recovery. The device
booted into twrp recovery and i wiped the data and formatted the system and data partition.
then i tried booting into fastboot mode using twrp reboot>bootloader.
The bootloader kept looping(coming and going).
NOW i have NO OS TO BOOT INTO and I'm getting this bootloader loop.
Things I noted:
1. The oem unlcoking option was off when i boot the device.
And i turned it on.Still bootloader keeps looping.
2. NO MTP when device was in the os .
3. no usb debugging notification.
4.no detection by adb devices and fastboot devices.
Please help me!!!!!!!!
Don't use rsd lite - this is not the correct way to flash firmware on this device
All you need is the firmware & fastboot commands
Things that could try
Is the phone actually staying in fastboot mode & it's just the screen that is turning on & off?
fastboot devices
The above command will list connected devices - keep typing it in a command prompt when the screen is off to see if its still connected
If detected try flashing the entire firmware via fastboot including gpt & bootloader (firmware must be the same or newer than what you have on the device already)
You can also use the hard brick solution to boot the bootloader off an sd card
You can then flash gpt & bootloader via fastboot
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
TheFixItMan said:
Don't use rsd lite - this is not the correct way to flash firmware on this device
All you need is the firmware & fastboot commands
Things that could try
Is the phone actually staying in fastboot mode & it's just the screen that is turning on & off?
fastboot devices
The above command will list connected devices - keep typing it in a command prompt when the screen is off to see if its still connected
If detected try flashing the entire firmware via fastboot including gpt & bootloader (firmware must be the same or newer than what you have on the device already)
You can also use the hard brick solution to boot the bootloader off an sd card
You can then flash gpt & bootloader via fastboot
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
Click to expand...
Click to collapse
I tried several times.
fastboot devices command is not detecting my device.
My device is not in fastboot mode also.
It's just looping the bootloader and is not booting up due to the absence of an OS.
Can u tell me how to load bootloader through sd card?
well i tried writing the sd card with twrp.img using diskimagerev2 still nothing.
i tried writng the sd card with bootloader.img from firmware. nothing happened still looping .
If it could somehow enter twrp i cud just chamge the bootloader with the img file from firmware. Won't that work? Wouldn't it fix that looping?
i know that twrp is present in my device.But the method to access it is not working.
Vol down+ power - bootloader looping
adb fastboot- not detecting.
Any solutions?
EMZThe said:
I tried several times.
fastboot devices command is not detecting my device.
My device is not in fastboot mode also.
It's just looping the bootloader and is not booting up due to the absence of an OS.
Can u tell me how to load bootloader through sd card?
well i tried writing the sd card with twrp.img using diskimagerev2 still nothing.
i tried writng the sd card with bootloader.img from firmware. nothing happened still looping .
If it could somehow enter twrp i cud just chamge the bootloader with the img file from firmware. Won't that work? Wouldn't it fix that looping?
i know that twrp is present in my device.But the method to access it is not working.
Vol down+ power - bootloader looping
adb fastboot- not detecting.
Any solutions?
Click to expand...
Click to collapse
I gave you the link to the guide on how to write the sd card - please read it
Also twrp can only flash kernel or recovery images
Firmware must be flashed via fastboot
TheFixItMan said:
I gave you the link to the guide on how to write the sd card - please read it
Also twrp can only flash kernel or recovery images
Firmware must be flashed via fastboot
Click to expand...
Click to collapse
Hey, my phone had fell into water before i had the bootloader loop. The service centre told me to change the motherboard (lol) for 5000Rupees ( around 72$) . The are some shorts in the board. BTW the phone will boot if there is a firmware installed . The bootloader loop is the problem. Now should i try the mmcblk0.img method??
EMZThe said:
Hey, my phone had fell into water before i had the bootloader loop. The service centre told me to change the motherboard (lol) for 5000Rupees ( around 72$) . The are some shorts in the board. BTW the phone will boot if there is a firmware installed . The bootloader loop is the problem. Now should i try the mmcblk0.img method??
Click to expand...
Click to collapse
If you have dropped your phone into water the chances are it's water damaged
Stick it in a bowl of rice and put it in a hot cupboard for a few days
I doubt anything else will work - you may have to replace the motherboard due to water damage
TheFixItMan said:
If you have dropped your phone into water the chances are it's water damaged
Stick it in a bowl of rice and put it in a hot cupboard for a few days
I doubt anything else will work - you may have to replace the motherboard due to water damage
Click to expand...
Click to collapse
I had gone to the repair shop and then cleaned and heated the board to remove moisture. Still that bootloader loops.
So i guess it's a hardware issue. :crying:
EMZThe said:
I had gone to the repair shop and then cleaned and heated the board to remove moisture. Still that bootloader loops.
So i guess it's a hardware issue. :crying:
Click to expand...
Click to collapse
Never heat a phone that's water damaged - you will draw the water up through more components and cause more damage
Stick it a bowl of rice and an airing cupboard for a few days
Chances are you may need a motherboard replacement or just buy a new phone as other components may also be damaged
Hey there ,
I had gone to the service centre and they said the problem is with the board for which they asked for RS 5000 (around $70-75$).
Now I bought a new mi a2 .
Thanks you.