Related
According to Droid Life, the Verizon Soak Test that just came out today doesn't break root.
heres the link
http://www.droid-life.com/2013/10/2...o-x-rolling-out-to-testers-doesnt-break-root/
WARNING DO NOT UPDATE IF YOU ARE USING PWNMYMOTO, some people are confirming bootloops. I believe this "keeping of root" is in relation to motoroot, but as always, do so at your own risk.
looks like the editor of droid life was rooted via motoroot and it kept that. I believe we have seen that with other OTAs. maybe not as exciting.
Glad to hear this. Of course, I un-rooted when I got the invite a week ago because I figured I either wouldn't get the OTA or it wouldn't install if I stayed rooted. I wonder if I can root again.
Tried to update with PwnMyMoto installed
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
tyguy829 said:
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
Click to expand...
Click to collapse
I would try to clear your cache, hopefully that works for you
Sent from my XT1060 using Tapatalk
Can't Clear Cache
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
tyguy829 said:
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
Click to expand...
Click to collapse
would
fastboot erase cache
command not work in the bootloader?
tyguy829 said:
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
Click to expand...
Click to collapse
I believe you can also clear cache through TiBu
Be careful according to JCase the soak does break root. Check his twitter.
I'm in the same boat as above. Phone stuck in a bootloop. If anyone figures it out I'll be in your debt. Also rsdlite doesn't detect my phone so I can't even restore it that way. I'm hoping there's at least a way to restore to factory through adb but Google is coming up empty.
- Nathan
tyguy829 said:
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
Click to expand...
Click to collapse
After your phone reboots hold down vol down + power to get into the bootloader. Now you can flash recovery through fastboot. Get the fastboot files from here if you don't already have it and the FXZ file for your carrier here. Now you can either just flash the recovery or flash the entire rom. If you just flash the recovery then the next time you boot it will reboot into recovery and run the update. If you choose to flash the entire rom then you will be wiping everything. To flash using fastboot you will first need to make sure the contents of the FXZ file are in the same folder as the fastboot files. Next open a command prompt and change the directory to the folder with your fastbboot files (eg. cd C:\). Now use the following commands to flash the FXZ files. If you choose to just flash the recovery then skip all the other commands except the command to flash recovery.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem fb_mode_clear
fastboot reboot
Thank you so much!! Worked like a charm as far as restoring my phone to defaults. The update is no longer showing in the software update section but that's ok. :good::good:
Dark9781 said:
After your phone reboots hold down vol down + power to get into the bootloader. Now you can flash recovery through fastboot. Get the fastboot files from here if you don't already have it and the FXZ file for your carrier here. Now you can either just flash the recovery or flash the entire rom. If you just flash the recovery then the next time you boot it will reboot into recovery and run the update. If you choose to flash the entire rom then you will be wiping everything. To flash using fastboot you will first need to make sure the contents of the FXZ file are in the same folder as the fastboot files. Next open a command prompt and change the directory to the folder with your fastbboot files (eg. cd C:\). Now use the following commands to flash the FXZ files. If you choose to just flash the recovery then skip all the other commands except the command to flash recovery.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Anyone know how to cancel the reminder on the update? My phone downloaded the update, when I click install later it makes me set a time to be reminded. Don't really want to lose root for this update. Any ideas?
Sent from my GT-N8013 using Tapatalk 4
whitlecj said:
Anyone know how to cancel the reminder on the update? My phone downloaded the update, when I click install later it makes me set a time to be reminded. Don't really want to lose root for this update. Any ideas?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
delete the download through Tibu and then freeze the ota apk in Tibu
what i did to keep root with pwnmymoto was make sure my phone was 100% stock then root using pwnmymoto boot into recovery and back up root with ota rootkeeper. then i temp unroot and reboot to bootloader and flashed the original recovery back and installed the update which aborted near the end so i did it again and it did the same thing. after rebooting it was the new software update with no root so i flashed the boot.img into the recovery partition and booted back to recovery to restore root which you may have to grant a app su permisions for it to stick when you reboot. so far its running good. idk if the update applied properly but it booted up and runs great
FeaR_x_KhAoS said:
what i did to keep root with pwnmymoto was make sure my phone was 100% stock then root using pwnmymoto boot into recovery and back up root with ota rootkeeper. then i temp unroot and reboot to bootloader and flashed the original recovery back and installed the update which aborted near the end so i did it again and it did the same thing. after rebooting it was the new software update with no root so i flashed the boot.img into the recovery partition and booted back to recovery to restore root which you may have to grant a app su permisions for it to stick when you reboot. so far its running good. idk if the update applied properly but it booted up and runs great
Click to expand...
Click to collapse
anyone know if safestrap will be available after the ota (assuming we apply the update as you mentioned)?
has anyone tried rooting via motoroot 1.1 after doing the OTA from an unrooted device?
jayboyyyy said:
delete the download through Tibu and then freeze the ota apk in Tibu
Click to expand...
Click to collapse
Thanks for the response. Where do I find the download using tibu?
Sent from my GT-N8013 using Tapatalk 4
whitlecj said:
Thanks for the response. Where do I find the download using tibu?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
check out here. It is a big list but i think it has what things to freeze for the OTA. there is just one maybe two i think.
http://forum.xda-developers.com/showthread.php?t=2432729
just checked that he only disabled motorola OTA. i am on Vzw and don't have an OTA yet so im not sure thats all you need to freeze. I read some where to freeze updater.apk as well. maybe its either or. I don't have updater.apk frozen but if motoOTA doesn't fix it then do updater as well
jayboyyyy said:
check out here. It is a big list but i think it has what things to freeze for the OTA. there is just one maybe two i think.
http://forum.xda-developers.com/showthread.php?t=2432729
just checked that he only disabled motorola OTA. i am on Vzw and don't have an OTA yet so im not sure thats all you need to freeze. I read some where to freeze updater.apk as well. maybe its either or. I don't have updater.apk frozen but if motoOTA doesn't fix it then do updater as well
Click to expand...
Click to collapse
You have to.freeze the update.apk and if you've downloaded the update its in your cache.
Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help
Hello!
My nexus 4 started to optimize app on each reloading few days ago. At last reload it stucked on "starting apps". I flashed factory 5.1 rom by default guide("run flash-all"). It not helped, starting apps stuck again. I flashed 4.4, it not helped too.
I find few tips.I tried.
(4.4) lock, unlock bootloader, flash
(4.4) flash twrp, change filesystem of cache to fat, return to ext4, flash
(4.4) flash by update without -w
(4.4) erase all particles by fastboot, flash manually each particle
(4.4) flash by update, go to default recovery and do factory reset
it not helped.
what could happen? What I can do?
Sorry for bad english
Boot into fastboot, issue the commands "fastboot erase userdata", "fastboot erase cache", "fastboot flash userdata usedata.img", use volume button to boot into recovery, perform a factory wipe using stock recovery, and reboot.
The userdata.img file needs to be extracted from the stock ROM.
Hope this helps get the phone booted.
audit13 said:
Boot into fastboot, issue the commands "fastboot erase userdata", "fastboot erase cache", "fastboot flash userdata usedata.img", use volume button to boot into recovery, perform a factory wipe using stock recovery, and reboot.
The userdata.img file needs to be extracted from the stock ROM.
Hope this helps get the phone booted.
Click to expand...
Click to collapse
Thanks, but did not effective: it stuck on boot animation(flying ovals)
It could be a possible hardware problem in that the memory chip is defective.
Try flashing stock ROM with Nexus Root kit. If that ROM fails to start then there is a likely hardware issue
Sent from my Nexus 4 using Tapatalk
Yesterday afternoon my phone decided to throw a fit. I was listening to a podcast via AUX, and all of the sudden my phone reboots. No big deal. However, the phone never booted. So I enter TWRP to restore a backup. Restoration completes fine, however my backup bootloops (uh oh).
LONGG story short, my phone will not boot. Fastboot tells me "Baseband: Not Available" which is...unpleasant. I have tried manually flashing firmware, no dice, bootloops. I finally decided to try RSD Lite, but when it gets to the modem (NON-HLOS.bin) the flash fails. For the record, I'm using the full firmware from the May Security Update, XT1575.
Im starting to become worried this is a real issue. Any help or experience with this type of issue is greatly appreciated!
Are you wiping data?
lafester said:
Are you wiping data?
Click to expand...
Click to collapse
After originally bootlooping, i tried restoring a good nandroid. When that also bootlooped, i reentered TWRP and tried a fresh install of an CM nightly. That install began, but wouldn't progress nor fail. I eventually encountered an error regarding the data partition, so i rebooted TWRP again and formatted data, and again tried installing CM.
When that also failed, I began attempting to flash stock firmware via fastboot.
Sent from my m8wl using Tapatalk
Can you manually push the firmware via fastboot?
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Some people have noted doing the erase command before the flash commands helps, or make 2-3 attempts at flashing the NON-HLOS.bin file are required to get an OK.
Otherwise try flashing the full factory firmware, but expect gpt.bin to fail, that is normal, when you get to NON-HLOS.bin flash execute the command up to 3 times to try to get it to go.
If you continue to get failures, it is possible that your emmc chip is corrupt or defective. :/
acejavelin said:
Can you manually push the firmware via fastboot?
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Some people have noted doing the erase command before the flash commands helps, or make 2-3 attempts at flashing the NON-HLOS.bin file are required to get an OK.
Otherwise try flashing the full factory firmware, but expect gpt.bin to fail, that is normal, when you get to NON-HLOS.bin flash execute the command up to 3 times to try to get it to go.
If you continue to get failures, it is possible that your emmc chip is corrupt or defective. :/
Click to expand...
Click to collapse
Yes, multiple times. The modem would always flash on second attempt. Still wouldn't ever boot.
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
Yes, multiple times. The modem would always flash on second attempt. Still wouldn't ever boot.
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Dumb question... is it looping, or just sitting at the boot logo after the initial boot animation appears? First boot can take what seems like a really long time, over 20 minutes sometimes.
acejavelin said:
Dumb question... is it looping, or just sitting at the boot logo? First boot can take what seems like a really long time, over 20 minutes sometimes.
Click to expand...
Click to collapse
I was getting bootloops originally, since flashing firmware each time I try to boot it sits at the unlocked bootloader screen for a couple seconds, then the blue M for a couple seconds, then the screen turns off and immediately returns to the unlocked bootloader message.
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
I was getting bootloops originally, since flashing firmware each time I try to boot it sits at the unlocked bootloader screen for a couple seconds, then the blue M for a couple seconds, then the screen turns off and immediately returns to the unlocked bootloader message.
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
So it is truly bootlooping... And you tried the full factory images?
acejavelin said:
So it is truly bootlooping... And you tried the full factory images?
Click to expand...
Click to collapse
I believe so! I'm using the following:
XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
I believe so! I'm using the following:
XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Did you manually flash all 8 sparsechunks? According to the file contents and service.xml file, the appropriate way to flash this image is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- May fail, if fails twice, just continue
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
EDIT: Also note that after flashing the factory images it is known to fail to boot if you do not do a factory reset with the stock recovery prior to flashing the images... fastboot flash the recovery image, do a factory default, then go through the full list above, step by step, and verify you get an OK after every step, if you don't repeat the step before continuing. I would suggest using the above method manually.
acejavelin said:
Did you manually flash all 8 sparsechunks? According to the file contents and service.xml file, the appropriate way to flash this image is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- May fail, if fails twice, just continue
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
EDIT: Also note that after flashing the factory images it is known to fail to boot if you do not do a factory reset with the stock recovery prior to flashing the images... fastboot flash the recovery image, do a factory default, then go through the full list above, step by step, and verify you get an OK after every step, if you don't repeat the step before continuing. I would suggest using the above method manually.
Click to expand...
Click to collapse
Those were the instructions i was following, but i did not know about this stock recovery issue.
You're saying flash stock recovery, enter recovery and perform a factory reset, and then fastboot flash the firmware package as instructed?
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
Those were the instructions i was following, but i did not know about this stock recovery issue.
You're saying flash stock recovery, enter recovery and perform a factory reset, and then fastboot flash the firmware package as instructed?
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
acejavelin said:
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it, thank you, I'll try this as soon as i get home
Sent from my m8wl using Tapatalk
acejavelin said:
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just followed this step by step, the only thing that failed on first try was the modem, second attempt flashed okay. After sending the "fastboot reboot" command, I get the unlocked bootloader message for a few seconds, the stock blue Moto M for about 10 seconds, and then the screen remains on but blank (black). Its been sitting there for a few minutes and nothing is happening..
Edit: Fastboot is now showing "Not found" under baseband instead of "Not available", as it had been previously.
DonKilluminati23 said:
Just followed this step by step, the only thing that failed on first try was the modem, second attempt flashed okay. After sending the "fastboot reboot" command, I get the unlocked bootloader message for a few seconds, the stock blue Moto M for about 10 seconds, and then the screen remains on but blank (black). Its been sitting there for a few minutes and nothing is happening..
Click to expand...
Click to collapse
Give it at least 20-25 minutes without touching it... too early to make a call yet.
acejavelin said:
Give it at least 20-25 minutes without touching it... too early to make a call yet.
Click to expand...
Click to collapse
After a few more minutes it returned to the unlocked bootloader message and is now back to cycling back and forth between that screen and the blue M..
DonKilluminati23 said:
After a few more minutes it returned to the unlocked bootloader message and is now back to cycling back and forth between that screen and the blue M..
Click to expand...
Click to collapse
Hmm... I am at a loss for what to do then. Sorry.
Sent from my XT1575 using Tapatalk
acejavelin said:
Hmm... I am at a loss for what to do then. Sorry.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So I decided to try again from scratch, this time its actually staying on the boot screen (the blue M) and has been sitting just like that for almost 30 minutes? WTF. All I can think to do at this point (after letting it set there for another 30 minutes) is letting the phone charge for a few hours to guarantee low battery isnt an issue.
Regardless, I really appreciate your help!! At this point Im hoping I can send it to Motorola to see if they can successfully flash factory software.
DonKilluminati23 said:
So I decided to try again from scratch, this time its actually staying on the boot screen (the blue M) and has been sitting just like that for almost 30 minutes? WTF. All I can think to do at this point (after letting it set there for another 30 minutes) is letting the phone charge for a few hours to guarantee low battery isnt an issue.
Regardless, I really appreciate your help!! At this point Im hoping I can send it to Motorola to see if they can successfully flash factory software.
Click to expand...
Click to collapse
i have the same problem like you
my base band in fastboot says NOT FOUND
even after flashing stock and cutom rom my phone con not recognize simcard signal.
did you solve your problem?
if yes, how?
ehsan_991 said:
i have the same problem like you
my base band in fastboot says NOT FOUND
even after flashing stock and cutom rom my phone con not recognize simcard signal.
did you solve your problem?
if yes, how?
Click to expand...
Click to collapse
I sent it to Motorola to have it "repaired". Basically they just reflashed stock software. I was not under warranty, but they fixed it for free so i didn't bother trying to fix it over and over.
Sent from my XT1575 using Tapatalk
Are you on a 64bit rom ? If yes please read on!
Us developers have had reports of you guys loosing imei number. We can re gain your imei number however you will no longer have 4g.
HERES HOW TO FIX LOSS OF IEMI
Install 32 bit twrp
Go back to stock with fastboot method using full commands
Fastboot 32 bit twrp
Flash no verity zip
Reboot twrp
Wipe data
reboot recovery
Install 64 bit twrp
Reboot recovery
Install any 8.1 ROM
Reboot on first boot.
IF U DO NOT FLASH 32 BIT TWRP YOU WILL NOT GAIN IMEI NUMBER BACK
*THE CAUSE*
THE MAIN CAUSE OFF LOSSING IMEI IS FASTBOOTING STOCK WHILST HAVING 64BIT RECOVERY , ROM AND MODEM SO MOVE TO 32BIT BEFORE FLASHING STOCK . I REALLY DONT RECOMMEND YOU GO BACK TO STOCK UNLESS YOU KNOW WHAT YOU ARE DOING.STOCK FLASHIBLE WILL NOT LOOSE IMEI!
I'm just staying on a fully working 7.1.2 rom until an official oreo rom comes out, I'd say that's the wisest choice at this time.
Exanneon said:
I'm just staying on a fully working 7.1.2 rom until an official oreo rom comes out, I'd say that's the wisest choice at this time.
Click to expand...
Click to collapse
Very true!
infixremix said:
Are you on a 64bit rom ? If yes please read on!
Us developers have had reports of you guys loosing imei number. We can re gain your imei number however you will no longer have 4g.
HERES HOW TO FIX LOSS OF IEMI
Install 32 bit twrp
Go back to stock with fastboot method using full commands
Fastboot 32 bit twrp
Flash no verity zip
Reboot twrp
Wipe data
reboot recovery
Install 64 bit twrp
Reboot recovery
Install any 8.1 ROM
Reboot on first boot.
IF U DO NOT FLASH 32 BIT TWRP YOU WILL NOT GAIN IMEI NUMBER BACK
*THE CAUSE*
THE MAIN CAUSE OFF LOSSING IMEI IS FASTBOOTING STOCK WHILST HAVING 64BIT RECOVERY , ROM AND MODEM SO MOVE TO 32BIT BEFORE FLASHING STOCK . I REALLY DONT RECOMMEND YOU GO BACK TO STOCK UNLESS YOU KNOW WHAT YOU ARE DOING.STOCK FLASHIBLE WILL NOT LOOSE IMEI!
Click to expand...
Click to collapse
oh wow ...so there no way to get back 4g???
infixremix said:
We can re gain your imei number however you will no longer have 4g
Click to expand...
Click to collapse
So there's no way to get 4g working?
Can I get volte by doing this.? because I had lost volte,lte works fine.
infixremix said:
Are you on a 64bit rom ? If yes please read on!
Us developers have had reports of you guys loosing imei number. We can re gain your imei number however you will no longer have 4g.
HERES HOW TO FIX LOSS OF IEMI
Install 32 bit twrp
Go back to stock with fastboot method using full commands
Fastboot 32 bit twrp
Flash no verity zip
Reboot twrp
Wipe data
reboot recovery
Install 64 bit twrp
Reboot recovery
Install any 8.1 ROM
Reboot on first boot.
IF U DO NOT FLASH 32 BIT TWRP YOU WILL NOT GAIN IMEI NUMBER BACK
*THE CAUSE*
THE MAIN CAUSE OFF LOSSING IMEI IS FASTBOOTING STOCK WHILST HAVING 64BIT RECOVERY , ROM AND MODEM SO MOVE TO 32BIT BEFORE FLASHING STOCK . I REALLY DONT RECOMMEND YOU GO BACK TO STOCK UNLESS YOU KNOW WHAT YOU ARE DOING.STOCK FLASHIBLE WILL NOT LOOSE IMEI!
Click to expand...
Click to collapse
Hi,
My G5 is on Atomic 8.1 ROM. If i want to return to stock ROM and IF i apply your commands, i won't loose IMEI ?
Regards
006fazer said:
Hi,
My G5 is on Atomic 8.1 ROM. If i want to return to stock ROM and IF i apply your commands, i won't loose IMEI ?
Regards
Click to expand...
Click to collapse
No , u need to flash 32 bit recovery without stock then a 32 bit rom.
infixremix said:
No , u need to flash 32 bit recovery without stock then a 32 bit rom.
Click to expand...
Click to collapse
Ok and after a 32 bit rom I can flash the stock rom ?
An advice, please. Which is a fully working 7.1.2 custom rom?
salsaelpato said:
So there's no way to get 4g working?
Click to expand...
Click to collapse
This would be up to Lenovorola, whether or not they want to provide a fix for a flaw in their phones design
What interests me, is the varying degrees of severity. Some have no issues, some lost only VOLTE, some lose 4G/VOLTE altogether. It's well past time for an official statement from the developers of the phone. Maybe it's why an official Oreo update is taking so long and they are hiding behind the "your fault, you unlocked your phone" banner instead of acknowledging their ineptitude, whether purposefully or not, really messed up some of these devices.
Lol. A design flaw...... seriously? We are talking about custom roms NOT about an official software from Motorola! =))
Necesito ayuda quien me podrá a ayudar o explicar bien como puedo recuperar mi imei de mi moto g5 por favor
2211190794 manden whats si me podrán ayudar
Ema172161 said:
Necesito ayuda quien me podrá a ayudar o explicar bien como puedo recuperar mi imei de mi moto g5 por favor
2211190794 manden whats si me podrán ayudar
Click to expand...
Click to collapse
Please read the rules again - you have only just signed up!
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
I installed Lineage on my XT1672, but can not call anyone on Phone app, Google Camera does not work (if I update the app, I discovered that ...), Netflix is not compatible...
I installed stock ROM and bazinga... Without SIM signal... I am very sad...
I will stay in Lineage, because the things that not work are less important ... At least I have SIM signal...
Hi,
I restored with success the Lineageos 14.1 ROM from Atomics 8.1 Oreo ROM, no imei lost.
Should i can test a fastboot flash of the stock ROM Motorola ?
Regards
Hi,
i can confirm that we can return to stock !!! ;-D without loosing IMEI
- Reflash a 32bits TWRP recovery
- wype DATA
- reboot to bootloader
- use this command to flash stock ROM :
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Don't run those commands (IMEI = 0) :
fastboot erase modemst1
fastboot erase modemst2
After that you can boot the stock rom.
If you want to relock the boot loader, use this :
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Reboot
After i immediatly receive notofication for OTA update, download in progress....
EDIT : I can confirme that OTA updates are fully working
EDIT : after the OTA of january security patch : IMEI = 0 i test with the OTA with march security patch....
006fazer said:
Hi,
i can confirm that we can return to stock !!! ;-D without loosing IMEI
- Reflash a 32bits TWRP recovery
- wype DATA
- reboot to bootloader
- use this command to flash stock ROM :
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Don't run those commands (IMEI = 0) :
fastboot erase modemst1
fastboot erase modemst2
After that you can boot the stock rom.
If you want to relock the boot loader, use this :
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Reboot
After i immediatly receive notofication for OTA update, download in progress....
EDIT : I can confirme that OTA updates are fully working
EDIT : after the OTA of january security patch : IMEI = 0 i test with the OTA with march security patch....
Click to expand...
Click to collapse
Hello!
So I installed this update and lost IMEI.
Now I am trying flashing 32 bits twrp and stock rom and no success...
Can anybody help me please?
Thank you!
infixremix said:
Are you on a 64bit rom ? If yes please read on!
Us developers have had reports of you guys loosing imei number. We can re gain your imei number however you will no longer have 4g.
HERES HOW TO FIX LOSS OF IEMI
Install 32 bit twrp
Go back to stock with fastboot method using full commands
Fastboot 32 bit twrp
Flash no verity zip
Reboot twrp
Wipe data
reboot recovery
Install 64 bit twrp
Reboot recovery
Install any 8.1 ROM
Reboot on first boot.
IF U DO NOT FLASH 32 BIT TWRP YOU WILL NOT GAIN IMEI NUMBER BACK
*THE CAUSE*
THE MAIN CAUSE OFF LOSSING IMEI IS FASTBOOTING STOCK WHILST HAVING 64BIT RECOVERY , ROM AND MODEM SO MOVE TO 32BIT BEFORE FLASHING STOCK . I REALLY DONT RECOMMEND YOU GO BACK TO STOCK UNLESS YOU KNOW WHAT YOU ARE DOING.STOCK FLASHIBLE WILL NOT LOOSE IMEI!
Click to expand...
Click to collapse
OMG! Thnks!
I spend all day, testing a bunch of solutions and finally I have my phone back, thank you a lot, I can confirm that this works, tomorrow im gonna focus on get the 4G back, if something works, I let you guys know
https://forum.xda-developers.com/g5/how-to/how-to-recovery-4g-moto-g5-t3787208 this tutorial saved my 4G signal :good:
Just a little edit: for getting H+ signal in first step, I recommend installing PixelExperience ROM (based on Android 8.1.0) along with LATEST 64bit TWRP.
PixelExperience for G5: https://forum.xda-developers.com/g5/development/rom-pixelexperience-t3756673
TWRP x64 for G5: https://androidfilehost.com/?w=files&flid=236353
No verity opt (flashable TWRP zip, I recommend version 6.0, use in case if you are installing TWRP on stock ROM- without flashing this file on first run of TWRP, stock ROM won't boot): https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
EDIT2: It may take a little bit longer to establish network after boot with restored EFS (for me, it took almost 30 seconds). If phone logins into 3G network, just go to settings and make it search for all possible networks in range (there should be your 4G network also).
I AM NOT RESPONSIBLE FOR ANY DAMAGE, YOU ARE DOING THIS AT YOUR OWN RISK!