Need Help. Boot Loop - Atrix 4G Q&A, Help & Troubleshooting

I was flashing using the tut for Orange FR 2.3.4 and i got an error for webtop.img could not allocate.... I took a break and came back and my brother had unplugged my phone now it will boot with unlocked in top corner as usual buut then just goes into boot loop. I don't care if i have to wipe it clean i just need to get it working again. Im new to this btw. Thanks
EDIT:
I got it back into fastboot and continued the tutorial i have moto-fastboot flash boot ORFR234-tegrapart-1100100.boot.img and moto-fastboot flash system ORFR234-system.img successfully on the phone but i get an error with webtop still... moto-fastboot flash webtop webtop.img load_file: could not allocate 805306368 byteserror: cannot load 'webtop.img'

Try reflashing the ROM again, this time without any interruptions or phone unplugging... That should work unless there is no webtop support in the ROM, in that case you need to find another one...

MSynco said:
I was flashing using the tut for Orange FR 2.3.4 and i got an error for webtop.img could not allocate.... I took a break and came back and my brother had unplugged my phone now it will boot with unlocked in top corner as usual buut then just goes into boot loop. I don't care if i have to wipe it clean i just need to get it working again. Im new to this btw. Thanks
EDIT:
I got it back into fastboot and continued the tutorial i have moto-fastboot flash boot ORFR234-tegrapart-1100100.boot.img and moto-fastboot flash system ORFR234-system.img successfully on the phone but i get an error with webtop still... moto-fastboot flash webtop webtop.img load_file: could not allocate 805306368 byteserror: cannot load 'webtop.img'
Click to expand...
Click to collapse
If it´s already unlocked, then use fastboot to push the recovery CWM.img - and flash another rom from CWM. (Should be possible? Please correct me if I´m wrong!)
The error seems to be related to the image itself. Try redownloading if you can´t use CWM.

Related

[Q] Fix a soft brick?

I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
IronicUniqueUsername said:
I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
Click to expand...
Click to collapse
Flash a stock 2.3.4 via moto-fastboot
http://bandbinnovations.com/xda/ging...ead-4.5.91.zip
extract boot.img, system.img from the archive and flash via moto-fastboot.
Download moto-fastboot for your OS here:
http://forum.xda-developers.com/showthread.php?t=1138092
Then do the following commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
This one should boot up without problems
You can upload files to flash i get error in the link to download the 2.3.4 stock
Tavo_an said:
You can upload files to flash i get error in the link to download the 2.3.4 stock
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip

[Q] [Help needed] flash failure - Fastboot can't write to device - No error message

Hi Moto guys
I bought this RAZR. It is a GSM one without operator customizing.
I rooted it normally and tried to update to ICS leak (this one if I remember well).
It didn't work.
Anyway I downgrade back to Gingerbread and tried to flash in recovery the MIUI V4 zip.
It bootlooped.
So I wanted by the same way to downgrade to 2.3.6 again.
It was a fail.
From this, I had the flash failure screen at the beginning and lost the recovery.
Because of a "Battery Low" I made a factory cable and I can access again to the "flash failure" screen.
I found a tuto relating to the same problem than me and tried to apply it.
I downloaded this rom (SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.xml.zip) as explained and tried to flash it in RSD lite.
The problem is:
I have no error message, it just stays stuck on "6/11 flash system "system_signed".
I let it several hours, it never passed away this step.
With "Eternityprj_Fla**** script it's the same, it's blocked at "system writing..."
I don't really know if I'm considered to be on ICS or GB. My bootloader version is 0A.75 so I guess ICS one.
Any idea to reanimate this XT910?
Thanks for the help you could bring to me
P.S: I tried these roms since the first fail
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-FR_SIGNEuropeAustraliaEMEA_USASPDRRTFR_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
Since I use XP in a VIRTUALBOX machine, I have an icon with activity on device.
During this operation, the activity on the phone is important
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe flash system sy
stem.img
sending 'system' (793344 KB)...
OKAY [ 28.541s]
Click to expand...
Click to collapse
As it is to this step, no activity...
writing 'system'...
Click to expand...
Click to collapse
I tried with normal fastboot executable from SDK and erpj-fastboot.exe, no difference.
Is it possible I make something wrong with my factory cable?
I don't think so because it makes my phone booting as I plug it and it writes normally boot.img for example with fastboot.
Your help would be appreciated very much guys ^^
Thanks!
Solved!
I can't explain why but I managed to access recovery even if system flash with fastboot never ended.
I flashed ICS rom and it booted well.
So it's solved even if I can't give explanations.
Thanks anyway.
flash fails...repeatedly
This has been covered extensively, but mine is still screwed up, i rooted the phone with clockwork mod. When the official ICS cam eout, i tried to manually download it. I have unrooted the phone and tried to install ics, it failed. So i tried flashing back to factory because clockwork was still popping up on boot. The flash continues to fail. I have tried using moto-fastboot in command prompt, i ha tried rsd lite with the flash(4 different ones). It keeps failing and i end up in the ap fastboot mode. it takes 2 tries to get the phone to boot normally and occasionally the clockwork boot menu pops up on reboot. Any ideas how to just start from scratch. As seen by the problems i have caused myself, i am a complete amateur here.
A little info, the phone is about 8 months old, rooted it once successfully, it is currently unrooted(i tried to reroot but got hung up in ap fastboot), updated drivers twice, moved the flash files all arounf my computer, using windows 7 64 bit. thanks to anyone who may help
Ok ok ok...
if i have an advice, before flashing, read read & read again.
So now.
Give me more info about your phone(xt910 / xt912 / europe / asia / latam /usa ) ??
Can you rsd to system_signed, or flash it manually through fastboot ?
When you installed ics manually which error did you have?
If you can, try to flash system_signed then reflash the OTA package with official recovery & wipe data. But i guess it wont work. For now i can't help you more without more info.
So tell me all you can and write it clear.
Or try this through rsd lite or fla**** http://forum.xda-developers.com/showthread.php?p=28199183
Sent from my XT910 using xda premium
yes, now ics fastboot file is out, you can easily fastboot to get back.
it is usa...i am downloading the ics fastboot now. I have tried the fastboot method with the latest gingerbread build, and also using the command prompt and flash commands....will let you know
thanks
Flash failed right away....how do i know i have the correct drivers? any other ideas?
I had the same issue when attempting to flash. Make sure you switch to a usb 2.0 port.
After that find the moto-fastboot package and then flash all the files manually using moto-fastboot instead of regular fastboot.
You have to do that for every single file. The file names are in the xml in the fastboot file.

[Q] Soft bricked my Atrix 4g

I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.

unbrick atrix rsd waiting for re-enumaration

how can i solve that this is what i did t the phone get brick SO I download the sbf and rsd 5.7
the phone is whit the unlock bootloader so i get this sbf
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012
i flash it the 2.3.4 and the rsd lite said "Flash failure: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent."
and the phone dont reboot so i take the battery off go to fastboot and did this
fastboot erase system
fastboot erase user data *or just data if user data doesn't work for you*
fastboot erase boot *this is important*
fastboot erase cache
fastboot reboot
Then boot into RSD mode flash the SBF file again.
but nothing happen i did whit he two sbf 2.3.4 and 2.3.6 also i try to flash the 2.3.4 via fastboot but the system image said is too large and failed
any ideas?
First off, what stock version were you on before you started flashing custom ROMs?
Sent from my MB886 using xda app-developers app
i guess wass 2.3.4 cause i flash CWM and isntall the CM7 it was running ok but one day it just reboot it selft and didnt boot up
It must have been on 2.3.4 because you flashed CWM and CM7? How is that even related?
well really dont know cause i was using the CM7 well till it failed dont know why or how so i decided to flash via rsd a stock sbf i ve flashed both i posted but still given me that error in the rsd lite re-enumeration so any ideas to solve that and flash the stock sbf on it
luismrosa said:
well really dont know cause i was using the CM7 well till it failed dont know why or how so i decided to flash via rsd a stock sbf i ve flashed both i posted but still given me that error in the rsd lite re-enumeration so any ideas to solve that and flash the stock sbf on it
Click to expand...
Click to collapse
Stock 2.3.4 and stock 2.3.6 have nothing to do with CM7. They are 2 different types of ROMs. Sbfs deal with stock, and thats all we're focused on right now, the stock version.
@ravilov does his result look like a bad file download/flash or does that look like a brick caused by a downgrade?
Sent from my MB886 using xda app-developers app
palmbeach05 said:
@ravilov does his result look like a bad file download/flash or does that look like a brick caused by a downgrade?
Click to expand...
Click to collapse
Not sure really. Actually I'm not quite sure what he's trying to accomplish here, and why bother with SBFs if he has working fastboot. Why not just get a fruitcake, unpack it, and flash boot and system manually through fastboot?
Also, more knowledgeable people say it is actually very hard to make a true hardbrick. If the phone is showing any signs of life, it is probably fixable (unless of course there is something wrong with the hardware). So there is at least that...
ok i did a few things like flash via fastboot bud to make more sure please can anyone of you give a link to re download the stock sbf and also the fruicake for fastboot flash cause it could be a problem whit the file i download it
guys i download a fruitcake from here http://forum.xda-developers.com/showthread.php?t=1583199
specially this 234-sb-release
but i get that flashing the system image in fastboot
sending 'sytem' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.001s
any ideas help
Use moto-fastboot instead of fastboot. And don't be afraid to use forum search next time...
i flashed but nothing happend it stock on the unlocked screen like before
Did you try moto-fastboot? (Its different than regular fastboot)
Enviado desde mi MB860 usando Tapatalk 2
yesss i try it after doing the moto-fastboot it still doing the same stck in the unlocked screen
people thank for you respond i ve solve my problem i did this i think i have problem whiit the battery i guess i dont know but what i did was flashing via moto-fastboot the CWM recovery them i enter to it it appears run well so just flash again the CM7 and gapps for GB and thats it
enter to fastboot
moto-fastboot erase recovery
moto-fastboot flash recovery "CWM recovery"
moto-fastboot rebooot
enter to android recovery and flash ZIP
thanks to all for you rapid respond

Messed up trying to root

i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.

Categories

Resources