XT1031 restore Boost baseband stuff - Moto G Q&A, Help & Troubleshooting

I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.

HardOnChairs said:
I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.
Click to expand...
Click to collapse
Factory Firmware Images are available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
I would start by only flashing the 'system.img.sparsechunk' files:
mfastboot flash system system.img_sparsechunk1 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot erase userdata
mfastboot reboot​

lost101 said:
by only flashing
Click to expand...
Click to collapse
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip

HardOnChairs said:
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip
Click to expand...
Click to collapse
My recommendation is for your safety. Messing with fastboot has destroyed many phones.

Code:
C:\Users\User\Desktop\New folder>mfastboot devices
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot devices
TA96506RJD fastboot
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (262084 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 14.144s]
finished. total time: 22.361s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256888 KB)...
OKAY [ 8.052s]
writing 'system'...
OKAY [ 12.088s]
finished. total time: 20.142s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (238359 KB)...
OKAY [ 7.485s]
writing 'system'...
OKAY [ 11.907s]
finished. total time: 19.393s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (26644 KB)...
OKAY [ 0.875s]
writing 'system'...
OKAY [ 8.438s]
finished. total time: 9.313s
C:\Users\User\Desktop\New folder>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\User\Desktop\New folder>mfasboot reboot
'mfasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\User\Desktop\New folder>
Everything seems to have gone well but I still get the activation screen and the baseband still has VZW_CUST.
Edit: Here are all of the files in the zip for my phone if that helps:
HTML:
boot.img
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml
fsg.mbn
gpt.bin
logo.bin
mfastboot.exe
motoboot.img
NON-HLOS.bin
recovery.img
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4

Now flash the Radio Firmware only. Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​

The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.

HardOnChairs said:
The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.
Click to expand...
Click to collapse
From memory, I do recall Verizon software being present in the Boost Firmare Images. But you can delete certain apks to stop those activation screens appearing. If you install TWRP, you can use the file explorer to delete the folders. I will try to get the correct names soon, but you might be able to guess them - they are located in /system/priv-app

The weird this is that it is a boost/sprint app.
com.motorola.android.omadm.sprint.client
Click to expand...
Click to collapse
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.

HardOnChairs said:
The weird this is that it is a boost/sprint app.
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.
Click to expand...
Click to collapse
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031

@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.

ATTACK said:
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031
Click to expand...
Click to collapse
I do still get activation alerts on my other ones but they are not intrusive and they can be disabled. All of the xt1031 phones I have are on wifi only. Does that mean that they are still "activated" from before? In that case is it possible to activate these two that I have without actually buying service for them?

lost101 said:
@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.
Click to expand...
Click to collapse
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?

HardOnChairs said:
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?
Click to expand...
Click to collapse
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.

lost101 said:
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.
Click to expand...
Click to collapse
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?

HardOnChairs said:
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?
Click to expand...
Click to collapse
Check the Fastboot screen:
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt or Terminal, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:
Code:
adb reboot-bootloader
I don't know if you can safely flash the XT1031 KitKat Bootloader now that the phone has been converted to XT1028 - but it's likely considering that's the original Model of the phone.

The fastboot screen says
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Click to expand...
Click to collapse

HardOnChairs said:
The fastboot screen says
Click to expand...
Click to collapse
v41.13 is KitKat, v41.18 is Lollipop.

lost101 said:
v41.13 is KitKat, v41.18 is Lollipop.
Click to expand...
Click to collapse
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?

HardOnChairs said:
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?
Click to expand...
Click to collapse
To be sure what is KitKat? v41.13 is 100% not a Lollipop Bootloader.

Related

[GUIDE] Rooted KitKat 4.4.2 on International phones

The below guide should result in a stock, rooted 4.4.2 phone for International (i.e. non AWS) Moto Gs without going through the monkey business of flashing 4.3 US and then hoping that the OTA works for you. Replacing the image files with the ones for AWS should give the same for the AWS version but lacking a phone I won't be able to test that.
All hardware will work just fine but there will be two side effects from going to the US firmware
1) You lose the carrier name in the topleft (which I actually like)
2) H icon will not show anymore (instead you will get 3G) but HSPA is used where available (i.e. you get the exact same speed as on the other firmwares that display the H)
First, we will assume you have an unlocked bootloader. If not, this is not for you.
Second, grab the 4.4.2 US International image from here: http://sbf.droid-developers.org/download.php?device=14&file=786
As outlined in various threads around here, it needs to be flashed in the bootloader with the following commands (this will wipe data so take precautions if you need any, note: it is recommended that you execute these line by line, as pasting the whole thing into a CMD shell has given weird results at times):
Edit: added mfastboot for convenience: http://forum.xda-developers.com/attachment.php?attachmentid=2475643&d=1388068310
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
(Linux or OSX users need to use the respective versions of mfastboot, obviously)
You now have a stock 4.4.2 US firmware on your phone, all hardware is working. If you do not need root, congrats, you are done.
Now, if you want root, the only way that worked for me was the following approach (thanks to http://forum.xda-developers.com/showthread.php?t=2583652) to restore CWM first, Grab http://forum.xda-developers.com/attachment.php?attachmentid=2473360&d=1387939887, unzip it and then run
Code:
mfastboot flash motoboot motoboot.img
Now reboot to bootloader and flash CWM as usual (get cwm from http://forum.xda-developers.com/showthread.php?t=2563599):
Code:
fastboot flash recovery CWMrecovery.img
Reboot to CWM and install supersu as usual (find it at http://download.chainfire.eu/supersu)
And finally, if you want to get rid of the ugly warning on boot (thanks to http://forum.xda-developers.com/showthread.php?t=2548530), you need to download http://forum.xda-developers.com/attachment.php?attachmentid=2422567&d=1385748174, unzip it and flash it with fastboot
Code:
fastboot flash logo logo.bin
What's AWS?
monchee said:
What's AWS?
Click to expand...
Click to collapse
The codename for the US version of the phone (uses different radio frequencies)
nupi said:
The codename for the US version of the phone (uses different radio frequencies)
Click to expand...
Click to collapse
does the US Global GSM count as non AWS? is the custom recovery and superSU already in the zip file or do we have to find and download it?
This is exactly what I did yesterday to my Koodo Moto G and it worked perfectly. I was sick of all the crashes I was getting under 4.3 and also needed root because I forgot how many ads there were in android (especially slacker radio which is an app I use often)
gwiqu said:
does the US Global GSM count as non AWS? is the custom recovery and superSU already in the zip file or do we have to find and download it?
Click to expand...
Click to collapse
US Global is non AWS.
You can find supersu here http://download.chainfire.eu/supersu and the recovery here http://forum.xda-developers.com/showthread.php?t=2563599 (will update the OP)
nupi said:
US Global is non AWS.
You can find supersu here http://download.chainfire.eu/supersu and the recovery here http://forum.xda-developers.com/showthread.php?t=2563599 (will update the OP)
Click to expand...
Click to collapse
i get i get
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
what do i do? while trying to flash the recovery
edit: nvm, using cmd type out the command does not work, but using the .bat and putting the command in works, WTS siaaaaaa
btw can busybox work if i install it?
Yes once you have root busybox will work.
Excuse my potentially dumb question but i want to flash this on my german Moto G to get KitKat and i am not sure what mfastboot is compared to normal fastboot. Can i just use the fastboot command instead or is mfastboot part of the usual ADB?
bunnahabhain said:
Excuse my potentially dumb question but i want to flash this on my german Moto G to get KitKat and i am not sure what mfastboot is compared to normal fastboot. Can i just use the fastboot command instead or is mfastboot part of the usual ADB?
Click to expand...
Click to collapse
It is a different (customized for moto) fastboot. Let me dig it out
If someone feels really adventurous, I have put a ZIP of a CWM backup of the rooted system onto http://www.mediafire.com/download/1... 4.4.2 US Retail for XT1032 International.zip I presume it should upgrade any international Moto G to a rooted 4.4.2 but proceed with caution (you will need to unpack it into CWM backup folder, install ZIP from sdcard does not work with this).
Okay i copied that in /platform-tools, renamed it to mfastboot and i'll try to flash the files manually tonight!
Thanks for the digging!
bunnahabhain said:
Excuse my potentially dumb question but i want to flash this on my german Moto G to get KitKat and i am not sure what mfastboot is compared to normal fastboot. Can i just use the fastboot command instead or is mfastboot part of the usual ADB?
Click to expand...
Click to collapse
No absolutely not. I did this same thing and ended up in a bootloop (a pretty one but useless all the same). Use the mfastboot executable and do it line by line and it will work fine
Suggestion for OP:
It was already said many times before elsewhere but before somebody asks again -it might be useful to stress in OP that two side-effects will occur - loss of carrier name in stat bar (which is basically good thing) and loss of H+ icon too BUT NOT loss of UMTS connectivity. Data speeds are exactly the same as they were in your location with 4.3.
I have upgraded 4.3 GB to 4.4.2 using this guide - everything works!
Has not tried root yet.
drfr said:
Suggestion for OP:
It was already said many times before elsewhere but before somebody asks again -it might be useful to stress in OP that two side-effects will occur - loss of carrier name in stat bar (which is basically good thing) and loss of H+ icon too BUT NOT loss of UMTS connectivity. Data speeds are exactly the same as they were in your location with 4.3.
Click to expand...
Click to collapse
yea the lost of carrier is really good lol but the loss of the icon that say which kind of connection H+/Edge you can get even if you are not connected is a bit sad it was a good thing
alokhan said:
yea the lost of carrier is really good lol but the loss of the icon that say which kind of connection H+/Edge you can get even if you are not connected is a bit sad it was a good thing
Click to expand...
Click to collapse
you only loose the H logo, edge should still be displayed when 3g is not available
Sent from my phone
Hi, first of all, big thanks for this, you are doing an amazing job! I want to try 4.2.2 but im not sure about how i need to flash 4.4.2 US International image...
I've already downloaded 4.2.2 image and mfastboot.zip but i'm not sure what i have to do with this files...
Could someone post a more descriptive tutorial? like step by step? I have unlocked bootloader...
Sorry for my english, it's not my native language x)
Thanks!
Thanks for this worked perfect now on 4.2.2 on UK moto g
Sent from my XT1032 using XDA Premium 4 mobile app
ponxho said:
Hi, first of all, big thanks for this, you are doing an amazing job! I want to try 4.2.2 but im not sure about how i need to flash 4.4.2 US International image...
I've already downloaded 4.2.2 image and mfastboot.zip but i'm not sure what i have to do with this files...
Could someone post a more descriptive tutorial? like step by step? I have unlocked bootloader...
Sorry for my english, it's not my native language x)
Thanks!
Click to expand...
Click to collapse
Unzip all the individual files from the rom into the same folder as mfastboot and you should be good to go. Hold volume down when you power on to get the phone ready and then paste the commands into the dos window from the guide.
Sent from my XT1032 using Tapatalk
SickBeast said:
Unzip all the individual files from the rom into the same folder as mfastboot and you should be good to go. Hold volume down when you power on to get the phone ready and then paste the commands into the dos window from the guide.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
I did what you say, almost everything went ok but this... Is this normal ?
C:\Users\Dell\Downloads\mfastboot-windows-linux-osx>fastboot-moto-windows.exe fl
ash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (260606 KB)...
OKAY [ 10.566s]
writing 'system'...
(bootloader) Invalid signed image
OKAY [ 14.020s]
finished. total time: 24.589s
C:\Users\Dell\Downloads\mfastboot-windows-linux-osx>fastboot-moto-windows.exe fl
ash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (239692 KB)...
OKAY [ 9.069s]
writing 'system'...
OKAY [ 14.592s]
finished. total time: 23.665s
C:\Users\Dell\Downloads\mfastboot-windows-linux-osx>fastboot-moto-windows.exe fl
ash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (222205 KB)...
OKAY [ 8.033s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 23.909s]
finished. total time: 31.947s
Thanks!

Stucked at "Rom Logo"

Hey guys..
I made a search on google for the best rom for a Moto G, and found a website with links for Paranoid, CNM, and Slim.. and i picked SLIMKAT
But after dong the process of installing twrp or CWM Recovery.. ended up sticking with CWM recovery cause of the buggy touch on the TWRP
so i was able to flash the rom and did it in this order
Flash Rom
Flash Gapps
Flash SU
reboot.. and got stucked at "slimkat logo"
then i decided maybe there was something wrong with the rom so i tried flashing Paranoid.. same deal.. stucked at logo.
Would anyoen please point me in the right direction fo what i need to do to fix this?
Thank you
SD card
Xcarab said:
Hey guys..
I made a search on google for the best rom for a Moto G, and found a website with links for Paranoid, CNM, and Slim.. and i picked SLIMKAT
But after dong the process of installing twrp or CWM Recovery.. ended up sticking with CWM recovery cause of the buggy touch on the TWRP
so i was able to flash the rom and did it in this order
Flash Rom
Flash Gapps
Flash SU
reboot.. and got stucked at "slimkat logo"
then i decided maybe there was something wrong with the rom so i tried flashing Paranoid.. same deal.. stucked at logo.
Would anyoen please point me in the right direction fo what i need to do to fix this?
Thank you
Click to expand...
Click to collapse
Genius me, seems at some point i deleted or formatted the sdcard now when i go to install zip on cwm recovery i get "Can't mount sd card
Xcarab said:
Genius me, seems at some point i deleted or formatted the sdcard now when i go to install zip on cwm recovery i get "Can't mount sd card
Click to expand...
Click to collapse
I'd restore stock firmware (that should get rid of those "sd card" errors) and then flash the custom recovery again.
I'd try the philZ recovery instead of CMW. And finally flash the Rom you want to.
Thank you
Landrea said:
I'd restore stock firmware (that should get rid of those "sd card" errors) and then flash the custom recovery again.
I'd try the philZ recovery instead of CMW. And finally flash the Rom you want to.
Click to expand...
Click to collapse
Ty Landrea.. in the process of doing exactly that now.. struggling on the "bootloader permission denied"
going trought the steps of unlocking bootloader again... will post how it goes
But are you sure that bootloader is unlocked?
Well i guess
denzel09 said:
But are you sure that bootloader is unlocked?
Click to expand...
Click to collapse
This is prove enough that it was
E:\Kindle Fire Utility\tools\Firmware restore lock and more 4.4.2>fastboot oem u
nlock UNIQUE_KEY
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.013s
E:\Kindle Fire Utility\tools\Firmware restore lock and more 4.4.2>
Xcarab said:
Ty Landrea.. in the process of doing exactly that now.. struggling on the "bootloader permission denied"
going trought the steps of unlocking bootloader again... will post how it goes
Click to expand...
Click to collapse
Omg that's strange. Unlocked bootloader once = unlocked bootloader forever, it's impossible you somehow re-lock it.
Did you follow the instructions on Motorola webiste to unlock?
Returning to stock process
Landrea said:
Omg that's strange. Unlocked bootloader once = unlocked bootloader forever, it's impossible you somehow re-lock it.
Did you follow the instructions on Motorola webiste to unlock?
Click to expand...
Click to collapse
Yes i think the problem is in the way i am returning to stock.
I found a thread with here in XDA last night were called "Firmware restock and more 4.4.2
but instead of using the batch file i oped them up in a text editor and run every line manually to see what the console answers after each command.
i downloaded the stock rom according to my country and carrie and simply rpelaced the files but i think the checksum did not match and thats why i was getting the denied message when doing this
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
I'm going to rename my country stock rom xml file to match the original xml file and see
Xcarab said:
Yes i think the problem is in the way i am returning to stock.
I found a thread with here in XDA last night were called "Firmware restock and more 4.4.2
but instead of using the batch file i oped them up in a text editor and run every line manually to see what the console answers after each command.
i downloaded the stock rom according to my country and carrie and simply rpelaced the files but i think the checksum did not match and thats why i was getting the denied message when doing this
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
I'm going to rename my country stock rom xml file to match the original xml file and see
Click to expand...
Click to collapse
Buddy be careful when you go to do all this "stuff" :good:
Try to help you with Moto Tool by Alonosoch in Android Original Development section
Thank you Denzel
denzel09 said:
Buddy be careful when you go to do all this "stuff" :good:
Try to help you with Moto Tool by Alonosoch in Android Original Development section
Click to expand...
Click to collapse
"Man on Fire"
I called in sick for work already.. have to be at this all day.. so i will try everything and wont stop untill it is fixed.
Following the step by step instructions at: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=sparsechunk
Xcarab said:
"Man on Fire"
I called in sick for work already.. have to be at this all day.. so i will try everything and wont stop untill it is fixed.
Following the step by step instructions at: http://forum.xda-developers.com/showthread.php?p=51155548
Click to expand...
Click to collapse
When I restored Stock, in the zip file I downloaded (en version) instead of:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
there were
system.img_sparsechunk0
system.img_sparsechunk1
system.img_sparsechunk2
so I had to edit the prompt commands to match the file names.
May you're facing the same issue?
Try to auto-complete commands witht the tab key, it helps you not to give the wrong imputs
Ok, do you tried the Alonsoch tool? Read carefully the op, there is your "sparsechunk" problem and how fix it.
http://forum.xda-developers.com/showthread.php?t=2635706
Thank you Landrea and Denzel
Yes Landrea, you were absolutely right the file names did not match.. i typed in the propper names and i was able to finish the whole process
Now i'm waiting for it to boot...
Finger crossed.
Thanks a lot to both of you.. You Rock!
:victory: :victory: :victory: :victory: :victory: :victory: :victory:
Xcarab said:
Yes Landrea, you were absolutely right the file names did not match.. i typed in the propper names and i was able to finish the whole process
Now i'm waiting for it to boot...
Finger crossed.
Thanks a lot to both of you.. You Rock!
Click to expand...
Click to collapse
You're very welcome
Keep us updated!
P.S. you could hit the thanks button sometimes <3
Original Post
The original Post was about being stucked at CUSTOM ROM LOGO... since this happened with different roms i decided to go back to stock rom and then the post went in this direction.. will try again tonigh to install a custom rom.. SLIM kat looks just like my style so will go for that again
Thanlk you everyone for the quick responses and this will continue...
Xcarab said:
The original Post was about being stucked at CUSTOM ROM LOGO... since this happened with different roms i decided to go back to stock rom and then the post went in this direction.. will try again tonigh to install a custom rom.. SLIM kat looks just like my style so will go for that again
Thanlk you everyone for the quick responses and this will continue...
Click to expand...
Click to collapse
I think the reason you were being stuck at the ROM logo is because you didn't unlock your phone before you tried all this..
So.. hopefully you can restore your phone back to stock rom and start over..
good luck
neozen21 said:
I think the reason you were being stuck at the ROM logo is because you didn't unlock your phone before you tried all this..
So.. hopefully you can restore your phone back to stock rom and start over..
good luck
Click to expand...
Click to collapse
My boost mobile phone is unlock but I still can't pass the cm logo or PAC man logo or the slimkat logo ... I done try 3 recoveries but I still get the same problem. I'm currently using philz recovery BC its the only one it would let me make a complete back up without any issues.. I try twrp and cwm but I get back up failed when it gets to the "backing up data section". Anyone else get the same issue? And about the ROM getting stuck at the logo any one have any idea what could it be????? I hate stock Roms even though its not that bad since its rooted lol...
Sent from my XT1031 using XDA Premium 4 mobile app
jglm4u said:
My boost mobile phone is unlock but I still can't pass the cm logo or PAC man logo or the slimkat logo ... I done try 3 recoveries but I still get the same problem. I'm currently using philz recovery BC its the only one it would let me make a complete back up without any issues.. I try twrp and cwm but I get back up failed when it gets to the "backing up data section". Anyone else get the same issue? And about the ROM getting stuck at the logo any one have any idea what could it be????? I hate stock Roms even though its not that bad since its rooted lol...
Sent from my XT1031 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going to post all the commands i used to get it to work
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot boot TWRP-2.6.3.3-falcon.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
OKAY [ 0.508s]
finished. total time: 0.807s
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot flash recovery TWRP-2.6.3.3-falcon.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.306s]
writing 'recovery'...
OKAY [ 0.522s]
This i used to send the rom, gapps and superuser to the media card so it was available to choose on twrp
E:\Moto G\Minimal ADB and Fastboot>adb push slim_unofficial_falcon_02-02-2014.zi
p /data/media/0
3769 KB/s (193672391 bytes in 50.180s)
E:\Moto G\Minimal ADB and Fastboot>adb push Slim_minimal_gapps.4.4.2.build.3.x.z
ip /data/media/0
3576 KB/s (62215309 bytes in 16.986s)
After that.. did
.- Do the wipes (cache/data/dalvik cache).
4.- Format system.
5.- Install the rom.
6.- Enjoy!
now on step 4, you will have to
Touch Wipe
Advanced Wipe
Check System
Then Swipe
Xcarab said:
Going to post all the commands i used to get it to work
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot boot TWRP-2.6.3.3-falcon.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
OKAY [ 0.508s]
finished. total time: 0.807s
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot flash recovery TWRP-2.6.3.3-falcon.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.306s]
writing 'recovery'...
OKAY [ 0.522s]
This i used to send the rom, gapps and superuser to the media card so it was available to choose on twrp
E:\Moto G\Minimal ADB and Fastboot>adb push slim_unofficial_falcon_02-02-2014.zi
p /data/media/0
3769 KB/s (193672391 bytes in 50.180s)
E:\Moto G\Minimal ADB and Fastboot>adb push Slim_minimal_gapps.4.4.2.build.3.x.z
ip /data/media/0
3576 KB/s (62215309 bytes in 16.986s)
After that.. did
.- Do the wipes (cache/data/dalvik cache).
4.- Format system.
5.- Install the rom.
6.- Enjoy!
now on step 4, you will have to
Touch Wipe
Advanced Wipe
Check System
Then Swipe
Click to expand...
Click to collapse
I will try this after work man thanks tho..hopefully it works for me 2
Sent from my XT1031 using XDA Premium 4 mobile app

Can't unlock bootloader

I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.
aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?
Any ideas guys?
aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.

No sim status after erasing modemst

Hi,
I was running CM12(5.0.2) on my xt1032 US GSM. I read in some thread for moto G 2014 that erasing modemst1 and modemst2 from bootloader fixed the no GPS fix. so i tried it in my moto g 2013 and after rebooting there is no network status. when i insert other sims, it shows no sim card. How can i fix this?
Thanks in advance
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Report back how it goes.
lost101 said:
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Report back how it goes.
Click to expand...
Click to collapse
Sir, I flashed CM 12 on top of 4.4.4 stock. I never updated my bootloader. Would it be okay to flash XT1032 Retail US 5.0.2 Lollipop Firmware's NON-HLOS.bin?
gearguy365 said:
Sir, I flashed CM 12 on top of 4.4.4 stock. I never updated my bootloader. Would it be okay to flash XT1032 Retail US 5.0.2 Lollipop Firmware's NON-HLOS.bin?
Click to expand...
Click to collapse
You can use the XT1032 Retail US 4.4.4 Firmware files instead to be safe.
I did that but it didnt solve the problem
Just FTR, erasing modemst1/2 can lead to problems: https://github.com/CyanogenMod/android_device_motorola_victara/issues/1#issuecomment-96288956
The method mentioned in the link above worked for me in this situation:
- newly bought xt1039
- ota updated to 5.1
- no gps activation in stock rom ever
- unlocked bootloader, flashed twrp
- backup of stock rom
- flashed cm12.1
- no gps lock
- restored stock rom from backup
- activated gps and got a lock
- re-flashed cm12.1
- gps works
gearguy365 said:
I did that but it didnt solve the problem
Click to expand...
Click to collapse
@gearguy365 - are you using mfastboot? Please provide a fastboot log if you still have problems.
mfastboot: https://www.androidfilehost.com/?fid=23578570567719065
lost101 said:
@gearguy365 - are you using mfastboot? Please provide a fastboot log if you still have problems.
mfastboot: https://www.androidfilehost.com/?fid=23578570567719065
Click to expand...
Click to collapse
I have the complete android SDK, so i am using the ADB provided in its platform tools. So only fastboot commands should work right?
gearguy365 said:
I have the complete android SDK, so i am using the ADB provided in its platform tools. So only fastboot commands should work right?
Click to expand...
Click to collapse
adb and fastboot are not the same thing. Put phone into fastboot mode and use mfastboot and the commands I stated.
lost101 said:
adb and fastboot are not the same thing. Put phone into fastboot mode and use mfastboot and the commands I stated.
Click to expand...
Click to collapse
I downloaded mfastboot and repeated the process, I have attached the cmd log and image of the phone's screen while in fastboot mode:
Code:
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.900s]
writing 'modem'...
OKAY [ 2.258s]
finished. total time: 4.166s
C:\mfastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.167s]
finished. total time: 0.170s
C:\mfastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.027s]
finished. total time: 0.031s
C:\mfastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (707 KB)...
OKAY [ 0.073s]
writing 'fsg'...
OKAY [ 6.819s]
finished. total time: 6.897s
C:\mfastboot>mfastboot reboot
rebooting...
finished. total time: 0.005s
The result is same. Still no network. My phone is even detecting the network name i'm in, but the signal bar is absolutely empty. Pressing and holding the power button gives the impression that its on ariplane mode, but turning the airplane mode off from there makes no effect. Please check the attached images. I'm really puzzled at this moment.....
gearguy365 said:
The result is same. Still no network.
Click to expand...
Click to collapse
Did you have Network connectivity in CM12.1 prior to flashing the GPS fix? Link me to the zip if possible.
I thought recent versions of CM12 required the Lollipop Bootloader to even boot?
lost101 said:
Did you have Network connectivity in CM12.1 prior to flashing the GPS fix? Link me to the zip if possible.
I thought recent versions of CM12 required the Lollipop Bootloader to even boot?
Click to expand...
Click to collapse
Yes, prior to attempting to solve that GPS problem i had full network/data connectivity on both GSM and HSPA on my operator. Only after trying to do modemst 1 & 2 clearing i am facing this problem. And yes, my CM 12 version is quite old. 20150322-NIGHTLY to be specific.
I didnt update to the later nightlys which required the up to date bootloader.
gearguy365 said:
Yes, prior to attempting to solve that GPS problem i had full network/data connectivity on both GSM and HSPA on my operator. Only after trying to do modemst 1 & 2 clearing i am facing this problem. And yes, my CM 12 version is quite old. 20150322-NIGHTLY to be specific.
I didnt update to the later nightlys which required the up to date bootloader.
Click to expand...
Click to collapse
Can you try doing a clean install of the ROM? Alternatively flash via mfastboot the entire Stock 4.4.4 Firmware files, excluding: motoboot.img and recovery.img - you could then wipe and flash CM12 if all was working.
lost101 said:
Can you try doing a clean install of the ROM? Alternatively flash via mfastboot the entire Stock 4.4.4 Firmware files, excluding: motoboot.img and recovery.img - you could then wipe and flash CM12 if all was working.
Click to expand...
Click to collapse
Okay, i will try to flash the 4.4.4 image i have, but i have never updated bootloader. Should i still avoid motoboot and recovery?
gearguy365 said:
Okay, i will try to flash the 4.4.4 image i have, but i have never updated bootloader. Should i still avoid motoboot and recovery?
Click to expand...
Click to collapse
It's dangerous to repeatedly flash the Bootloader (motoboot.img) - even if it is the KitKat one. And skipping recovery will mean you remain with current custom recovery.
lost101 said:
It's dangerous to repeatedly flash the Bootloader (motoboot.img) - even if it is the KitKat one. And skipping recovery will mean you remain with current custom recovery.
Click to expand...
Click to collapse
makes sense! i will try to revert back to 4.4.4 and keep things posted...
Flashing stock 4.4.4 brought back the network!
but when i was flashing the stock firmware, first i avoided flashing motoboot.img. That resulted in failing to erase userdata later on and ultimately resulting in "utag flash fail" and stuck in bootloader. Eventually flashing everything resulted in restoring stock firmware and now i have network again!
gearguy365 said:
Flashing stock 4.4.4 brought back the network!
but when i was flashing the stock firmware, first i avoided flashing motoboot.img. That resulted in failing to erase userdata later on and ultimately resulting in "utag flash fail" and stuck in bootloader. Eventually flashing everything resulted in restoring stock firmware and now i have network again!
Click to expand...
Click to collapse
I should have stated to do the commands manually, one at a time - rather than using the included script.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Download XT1032 Retail US 5.0.2 Lollipop Firmware image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Use only the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Report back how it goes.
Click to expand...
Click to collapse
Just saved my a**! Had a dead baseband. I somehow wrecked my modem on my XT1039. I downloaded a stock rom and used your commands and it worked like a charm! THANK YOU VERY MUCH!
Hello. I have the same issue... No sim/ network. I used mfastboot commands and fully restored to an unrooted stock XT1032 lollipop ROM. The confusing thing is that I still have no network. Does anyone have any suggestions?
Edit:
I used the downgrade to 4.4 thread... Ran the bat file and I'm back in business. The quick YouTube video walks you through the steps.
http://forum.xda-developers.com/showthread.php?t=2969729
Sent from my iPad using Tapatalk

Phone bootlooping on Mi logo after updating firmware, unable to go into recovery

I was using official Lineage 14.1 on Lollipop bootloader with firmware libra_miui_v8120_fw_patch, then today stupidly decided to update firmware with libra-firmware_miui9-7.8.21_7.0.zip which is probably for Nougat bootloader. Now I am unable to go into recovery and also when trying to flash recovery through fastboot I end up with this:
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
So can't even flash recovery. Fastboot oem unlock ends up with this:
Code:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.031s
tried also flashing logo.bin into bk2 just to verify if partition is logged and end up with same issue as with recovery, apparently bootloader locked:
Code:
fastboot flash bk2 logo.bin
target reported max download size of 536870912 bytes
sending 'bk2' (9591 KB)...
OKAY [ 0.329s]
writing 'bk2'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.341s
Is there any way to flash through fastboot just firmware and get back to where I was before screwed update so I don't need to go through flashing fastboot MIUI ROM, losing all my data in phone and setting up phone from scratch? At least in worst case I hope that's an option and it would work just to flash old libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0, then do oem unlock flash TWRP and the go to lineage, as i did without official unlocking before, but I would rather avoid this since I have still some data not backed up in the phone (luckily i backed up photos just before flashing).
EDIT: Or is there a way to at least back up my data out of phone through fastboot?
EDIT 2: according google results not possible to do backup through fastboot and according fastboot oem device-info it's locked bootloader, so back to square one, losing files, grr and start from scratch
https://www.google.ro/amp/s/forum.x...-unlocking-mi4c-bl-verification-t3336779/amp/
Steps 2 to 9. It should work.
Might be another way to save your data but I didn't found one. Maybe your pc will se your folders in fastboot so you can save the data.
Sent from my Mi-4c using Tapatalk
You can also try to unlock the bootloader the official way, then install TWRP and flash a lollipop firmware zip with the lollipop bootloader and try to boot your ROM that way. The zip floats around in one of the ROM threads.
cezarmed2 said:
https://www.google.ro/amp/s/forum.x...-unlocking-mi4c-bl-verification-t3336779/amp/
Steps 2 to 9. It should work.
Might be another way to save your data but I didn't found one. Maybe your pc will se your folders in fastboot so you can save the data.
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
yeah, I did that as usual when unlocking unofficially, but there is no way to see your data, though in miflash it says in bottom "save user data" but nothing was saved, I looked through all phone, can't find it anywhere
OK, I noticed another issue, my available space significantly shrank. I guess it's because during fastboot oem edl flashing fastboot MIUI dev ROM through miflash I left "keep user data" checked instead erase, hoping I can recover them somehow.
Now Settings/Storage shows me that my System takes 21GB out of all 29GB, which is nonsense, since it's pretty much fresh system with few apps and little data used.
So my question is, can I somewhere find my original user data taking all this space and manage them? Or is user data partition (internal storage) somehow corrupted and I should just format it and this should hopefully fix problem with lack of free space (although Settings are showing System is taking all the 21GB)? In Mixplorer Internal storage is showing capacity 7.75GB and Root 1.82GB, so I would think it's corrupted internal storage which should be formatted, although best would be if original data would be somewhere hidden and I could just delete them manually.
EDIT: SOLVED - go to TWRP / Wipe / select Data / Repair button / Resize / and partition was properly resized from 7900MB back to 26136MB without loss of current data, of course original data from before are gone, but I am already over it.

Categories

Resources