so im trying to send a modem.img to a lg v10 through fastboot, its bootloader unlocked and rooted.i result with this:
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem' (76800 KB)...
OKAY [ 1.715s]
writing 'modem'...
FAILED (remote: unknown command)
finished. total time: 1.731s
Also twrp cant mount modem or even back it up.I think the partition is read only,is there a way to make it r/w?I also tried clearing cache through fastboot and get the same failed message.
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot format cache
Creating filesystem with parameters:
Size: 1291845632
Block size: 4096
Blocks per group: 32768
Inodes per group: 7888
Inode size: 256
Journal blocks: 4928
Label:
Blocks: 315392
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78880 inodes and 10367/315392 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.000s
also failing to mount partitions through fastboot while in bootloader
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $ mount -o remount,rw /system
mount: Permission denied
any help would be appreciated!
jass65 said:
so im trying to send a modem.img to a lg v10 through fastboot, its bootloader unlocked and rooted.i result with this:
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot flash modem modem.img
target reported max download size of 536870912 bytes
sending 'modem' (76800 KB)...
OKAY [ 1.715s]
writing 'modem'...
FAILED (remote: unknown command)
finished. total time: 1.731s
Also twrp cant mount modem or even back it up.I think the partition is read only,is there a way to make it r/w?I also tried clearing cache through fastboot and get the same failed message.
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\jas\Downloads\WindowsLGFirmwareExtract-1.2.5.0-Release>fastboot format cache
Creating filesystem with parameters:
Size: 1291845632
Block size: 4096
Blocks per group: 32768
Inodes per group: 7888
Inode size: 256
Journal blocks: 4928
Label:
Blocks: 315392
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/78880 inodes and 10367/315392 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.000s
also failing to mount partitions through fastboot while in bootloader
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $ mount -o remount,rw /system
mount: Permission denied
any help would be appreciated!
Click to expand...
Click to collapse
Maybe you can try using adb shell and dd the .img to its correct partition with the proper dd command for your device. You need to find out which mmcblk0 is your modem partition, then use that mmcblk0 as the .img destination in your dd command.
The same command works in Terminal Emulator app also, you just have to enter "su" command first, then the dd command.
TWRP has the ability to flash .img files also, not sure if it works for flashing modem.img though, I've never looked into it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Maybe you can try using adb shell and dd the .img to its correct partition with the proper dd command for your device. You need to find out which mmcblk0 is your modem partition, then use that mmcblk0 as the .img destination in your dd command.
The same command works in Terminal Emulator app also, you just have to enter "su" command first, then the dd command.
TWRP has the ability to flash .img files also, not sure if it works for flashing modem.img though, I've never looked into it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Yes youre right i could try that and will work .its just i need to do it in bootloader mode/ without root su just in case something goes wrong and i dont have access to root to reflash.
ok even using flashwire, it will not flash.In flashfire is says the partition is protected it says it flashed the modem but it doesnt actually. Is there any way to remove this write protection on the modem partition or bypass it to flash?
jass65 said:
ok even using flashwire, it will not flash.In flashfire is says the partition is protected it says it flashed the modem but it doesnt actually. Is there any way to remove this write protection on the modem partition or bypass it to flash?
Click to expand...
Click to collapse
If your bootloader was unlocked correctly then you should be able to fastboot flash it. Are you sure you haven't missed something somewhere along the way?
Sent from my SM-S903VL using Tapatalk
Nope im stumped on this as well.my bootlpader is unlocked even running the fastboot oem unlock command confirms it.frkn LG. I can flash modem in twrp on note 4 with a breeze.
jass65 said:
Nope im stumped on this as well.my bootlpader is unlocked even running the fastboot oem unlock command confirms it.frkn LG. I can flash modem in twrp on note 4 with a breeze.
Click to expand...
Click to collapse
Maybe you need to use LG flashtool and convert the modem file you have to be compatible with flashtool.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:47 AM ---------- Previous post was at 09:33 AM ----------
jass65 said:
Nope im stumped on this as well.my bootlpader is unlocked even running the fastboot oem unlock command confirms it.frkn LG. I can flash modem in twrp on note 4 with a breeze.
Click to expand...
Click to collapse
Ah, I think I just realized your problem maybe, don't know why I didn't see it before.
When in fastboot, did you try
fastboot flash radio modem.img
Instead of fastboot flash modem modem.img?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Maybe you need to use LG flashtool and convert the modem file you have to be compatible with flashtool.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 09:47 AM ---------- Previous post was at 09:33 AM ----------
Ah, I think I just realized your problem maybe, don't know why I didn't see it before.
When in fastboot, did you try
fastboot flash radio modem.img
Instead of fastboot flash modem modem.img?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
so i tried fastboot flash radio modem.img and still get the same unknown command.is there any other commands to do this?.i think only fastboot can flash it since partition is locked.i mean flashing a whole new rom with lgup always works in download mode but im trying to flash a modified modem. this is the modem partition path /dev/block/mmcblk0p1. dd doesnt work in fastboot correct because i would need su permission.
jass65 said:
so i tried fastboot flash radio modem.img and still get the same unknown command.is there any other commands to do this?.i think only fastboot can flash it since partition is locked.i mean flashing a whole new rom with lgup always works in download mode but im trying to flash a modified modem. this is the modem partition path /dev/block/mmcblk0p1. dd doesnt work in fastboot correct because i would need su permission.
Click to expand...
Click to collapse
I'll try to look for other ways but I can't promise any results.
dd is done via adb shell or terminal emulator, not fastboot.
You're trying to flash a customized kernel? You may as well give up on that without root or at least TWRP.
If you have twrp you can try converting your modem to a flashable zip and flash it as you would a ROM but I doubt it will work with stock bootloader.
Have you tried mounting your partitions while in TWRP?
I don't understand why you're trying to do this without su permission when you are already rooted. The purpose of rooting is to use that root to configure the device as you choose. Why are trying to do it without root?
Sent from my SM-S903VL using Tapatalk
Ok so im rooted , bootloader unlocked and have twrp.twrp will not even see the modem partition.there is also no modem mount partition avaliable in twrp.i try flashing modem.img through twrp and can only select boot or recovery as the partition to flash to.do i need to create a flashable zip with a updater scrpit so twrp can see the modem partition ? also i can't flash modem while im in andoid system enviorment, correct? Yes i can dd it since i have root but the phone would have to be on and in android envoirment.So the only option left is fastboot which keeps throwing that error at me.ive also tried flashfire and that doesnt work either.i really appreciate you talking the time to help!
I was just trying to do it without root so i have a fall back plan.say i flash the moden and cant boot into os.at least i know i can fix the problem with fastboot and it will work.
jass65 said:
Ok so im rooted , bootloader unlocked and have twrp.twrp will not even see the modem partition.there is also no modem mount partition avaliable in twrp.i try flashing modem.img through twrp and can only select boot or recovery as the partition to flash to.do i need to create a flashable zip with a updater scrpit so twrp can see the modem partition ? also i can't flash modem while im in andoid system enviorment, correct? Yes i can dd it since i have root but the phone would have to be on and in android envoirment.So the only option left is fastboot which keeps throwing that error at me.ive also tried flashfire and that doesnt work either.i really appreciate you talking the time to help!
I was just trying to do it without root so i have a fall back plan.say i flash the moden and cant boot into os.at least i know i can fix the problem with fastboot and it will work.
Click to expand...
Click to collapse
Who do you have service with? Some mobie carriers remove fastboot feature from their devices, or at least remove functionality for certain commands. Some carriers go out of their way to keep us from messing with their devices.
If you made this modified modem yourself then I doubt you got all the modifications correct on the first try, flashing it will probably softbrick or maybe even hard brick the device. If it hard bricks you're done. Flashing modems other than the one that belongs on a device is risky business.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Who is do you have service with? Some mobie carriers remove fastboot feature from their devices, or at least remove functionality for certain commands. Some carriers go out of their way to keep us from messing with their devices.
If you made this modified modem yourself then I doubt you got all the modifications correct on the first try, flashing it will probably softbrick or maybe even hard brick the device. If it hard bricks you're done. Flashing modems other than the one that belongs on a device is risky business.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
If fastboot is removed from some devices and i can confirm it is missing on mine too.. How can i add it if it's even possible? would building from aosp source actually work or would i be left in the same boat with no fastboot still?
Sent from my LGLS676 using Tapatalk
Sands207 said:
If fastboot is removed from some devices and i can confirm it is missing on mine too.. How can i add it if it's even possible? would building from aosp source actually work or would i be left in the same boat with no fastboot still?
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
If fastboot has been removed then you can give up on trying to "add it".
Sent from my SM-S903VL using Tapatalk
hmm i have a tmobile v10 and its the only variant that comes with oem unlock option and was easiest to root.Actually what im trying to do is not flash a modem modified by me. See, i have a network locked v10 and the only way to unlock it is through the tmo device unlock app, no dialer codes , nothing.T mo won't put my request through for a permanent network unlock, even the previous owner has tried calling them.unlock services were less than 30$ near the v10's release now unlock services are 70$-100USD and they dont guarantee anything . thats crazy to unlock a phone.So i've tried putting international rom's on this thing and i cant get a sim unlock promp to show up.I do have the unlock code for it but can't enter it anywhere.Since the system img doesn't hold the unlock info.i figured the modem partition does and searching around confirmed this.So i had a person very very kind enough to upload his *unlocked* t mobile v10 modem so i could try flashing it.Now i have the unlocked modem*not user modified*. that i can't flash lol.
The thing with fastboot is, it won't even let me clear cache partition which is not even locked!?
jass65 said:
hmm i have a tmobile v10 and its the only variant that comes with oem unlock option and was easiest to root.Actually what im trying to do is not flash a modem modified by me. See, i have a network locked v10 and the only way to unlock it is through the tmo device unlock app, no dialer codes , nothing.T mo won't put my request through for a permanent network unlock, even the previous owner has tried calling them.unlock services were less than 30$ near the v10's release now unlock services are 70$-100USD and they dont guarantee anything . thats crazy to unlock a phone.So i've tried putting international rom's on this thing and i cant get a sim unlock promp to show up.I do have the unlock code for it but can't enter it anywhere.Since the system img doesn't hold the unlock info.i figured the modem partition does and searching around confirmed this.So i had a person very very kind enough to upload his *unlocked* t mobile v10 modem so i could try flashing it.Now i have the unlocked modem*not user modified*. that i can't flash lol.
The thing with fastboot is, it won't even let me clear cache partition which is not even locked!?
Click to expand...
Click to collapse
You'll have to follow the prescribed method of unlocking allowed by your network.
Now that I know you're attempting to do something that your network said they wouldn't allow, that means I have to tell you that there is nothing else I or anyone at XDA will do to help. We customize our devices but we don't discuss things that are against carrier policy.
Their modem probably won't work anyway because the way unlock works, the unlock code for each device is different, their unlock code won't unlock you.
If it were that easy then no one would need to pay for an unlock code, everyone with that device could just share the unlock code, it doesn't work like that. Your unlock code will be specific to your device based on its identifying numbers such as serial number and IMEI number, your numbers and the numbers from the other guys device are not the same.
Sent from my SM-S903VL using Tapatalk
I understand where you're coming from but please don't say this is against carrier policy.the device is paid off in full.carriers are just a bunch of d**ks.i can't count how many sim unlock/carrier bypasses threads are on this site, so no this site isn't just about customization.this site ****s all over carrier policies from the moment you unlock your bootloader to the moment you exchange your bricked phone by lying and telling them it was a software update when in reality u were messing with system files.ive literally bypassed 3 different phones networks using solely xda.tell me that's not violating carrier policy. These threads are still live years later.
The tmobile unlock app is broken not just for me but for many other people.they cant even connect to the remote server just like me.when you tell t mobile, they just say oh well cause they already milked you for the phone.its circumstances like this where you gotta work around the normal field.
Yes you're most likely right about the unlock but I thought I'd just give it a shot.
jass65 said:
I understand where you're coming from but please don't say this is against carrier policy.the device is paid off in full.carriers are just a bunch of d**ks.i can't count how many sim unlock/carrier bypasses threads are on this site, so no this site isn't just about customization.this site ****s all over carrier policies from the moment you unlock your bootloader to the moment you exchange your bricked phone by lying and telling them it was a software update when in reality u were messing with system files.ive literally bypassed 3 different phones networks using solely xda.tell me that's not violating carrier policy. These threads are still live years later.
The tmobile unlock app is broken not just for me but for many other people.they cant even connect to the remote server just like me.when you tell t mobile, they just say oh well cause they already milked you for the phone.its circumstances like this where you gotta work around the normal field.
Yes you're most likely right about the unlock but I thought I'd just give it a shot.
Click to expand...
Click to collapse
As a former Moderator here, I can certainly tell you that unlocking isn't even supposed to be discussed at all at XDA but you will find it. That doesn't mean XDA approves.
If you'll read the rules you'll see all kinds of things that aren't supposed be done or discussed here. XDA is all about sharing knowledge but it is certainly not about breaking the rules, some lines get pushed but they are not supposed to be broken.
Your impression of XDA ****ing all over carriers is not how it is at all, it's the members here saying f*** the rules, not XDA.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
As a former Moderator here, I can certainly tell you that unlocking isn't even supposed to be discussed at all at XDA but you will find it. That doesn't mean XDA approves.
If you'll read the rules you'll see all kinds of things that aren't supposed be done or discussed here. XDA is all about sharing knowledge but it is certainly not about breaking the rules, some lines get pushed but they are not supposed to be broken.
Your impression of XDA ****ing all over carriers is not how it is at all, it's the members here saying f*** the rules, not XDA.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
still, thanks for the help.
Related
I installed the KitKat update recently, tried to rsd back to jellybean, and the modem firmware downgraded. Now the phone won't activate because KitKat can't read the earlier firmware. I have the the soak ota downloaded, I just need a method to get the modem firmware back the the soak ota version.
Also, I tried to install the KitKat ota and I get errors about amazon_kindle.apk having unexpected contents since I disabled it
Sent from my XT907
i have to assume you are unlocked because rsd should have failed long before it got to the modems if you were locked.
that being true, you should be able to grab the 9.30.1 fxz from sbf droid devs and use this modified xml file http://www.mediafire.com/view/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC_DOWN.xml to go back to jb and all should be fixed.
if some how im wrong and you are locked do not do what i posted above!!
I am locked, the problem is I don't know how to flash the files in fastboot to get the modem working again, that's my only problem, I know the commands but don't know what specific order the files should be flashed and what partitions / files need to be erased. I may have to wait until the firmware is released on the sbf droid developers site. Also,
we really need the modem file from the kk sbf to ensure its done right. it may be possible to do it now but im not going to guess as to the proper sequence. there are about 2 dozen files in the modem folder. after we get the sbf they will be compressed into one file thats easy to flash.
sorry i cant be of more help.
on a side note, its very odd that rsd only flashed the modems and didnt bork your phone from the files it would have flashed before that. your phone should be bricked right now from trying, you are very lucky indeed.
Your phone is borked at this point from what is currently known after applying the KK OTA to a locked phone.
If you have already applied the OTA and you're locked, you CANNOT downgrade at all. Attempting to do so will result in what you are seeing I believe.
You will now have to wait for the official KK FXZ full image to come out so you can flash that back to your phone and get it back to operational standards. That could be weeks or months. No one knows for sure, but in the past, it usually takes a few weeks after the official OTA is released.
If, however, your phone's bootloader were unlocked, then you could have gone here and gotten yourself back in operation:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
bweN diorD said:
we really need the modem file from the kk sbf to ensure its done right. it may be possible to do it now but im not going to guess as to the proper sequence. there are about 2 dozen files in the modem folder. after we get the sbf they will be compressed into one file thats easy to flash.
sorry i cant be of more help.
on a side note, its very odd that rsd only flashed the modems and didnt bork your phone from the files it would have flashed before that. your phone should be bricked right now from trying, you are very lucky indeed.
Click to expand...
Click to collapse
The sequence is in the updater-script in the 9.30.1.XT926.Verizon.en.US.zip, I just don't know how to apply that specific part of it. I was just looking over it a few minutes ago. and yes, I'm very thankful my phone isn't a paperweight right now, I thought most soak ota's allow you to downgrade, but I was very wrong. Now I can't run the ota again because it fails due to disabled apps returning errors. I guess I'll just have to wait on the firmware which is weeks away. Sigh. At least I have an Razr M running kitkat, so I'm not missing out on much right now.
I think I know of a method, but it requires me erasing the system completely and re-applying it. Does anyone know the fastboot command to erase the OS off my Maxx HD so I can re-install it? I'm missing an argument when I try to erase the system.
Playb3yond said:
I think I know of a method, but it requires me erasing the system completely and re-applying it. Does anyone know the fastboot command to erase the OS off my Maxx HD so I can re-install it? I'm missing an argument when I try to erase the system.
Click to expand...
Click to collapse
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
Also, I can't seem the get the Motorola device manager from my HD to install, when my computer is connected to the internet, it won't run. But when it isn't, it opens. Has anyone else had this issue?
I checked the file version of the setup file and it seems to be moto device helper 4.0.0.0. I was thinking this would help me fix my phone if I could only get it to install
Sent from my XT907 using XDA Free mobile app
Here's the updated version of it https://www.dropbox.com/s/56jrbm1x0rqzkpd/Motorola Device Manager 4.0.0.0.zip
Sent from my XT907 using XDA Free mobile app
I tried flashing the modem manually and it still won't activate. No one could help me get this back in a usable state?
Sent from my XT907 using XDA Free mobile app
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.
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock
TonikJDK said:
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock
Click to expand...
Click to collapse
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
This is why you should unlock the phone as soon as you buy it.
So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?
Kew01 said:
So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?
Click to expand...
Click to collapse
No. You can do this once you are rooted and have TWRP but not before. Just back up your important data and go for it.
Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
Isn't app data automatically backed up on Google servers? Or am I recalling it wrongly?
Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Whenever I click "Acknowledge" on the page, the page just reloads?
Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Kew01 said:
Whenever I click "Acknowledge" on the page, the page just reloads?
Click to expand...
Click to collapse
**** nevermind I figured it out.
Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.
Kew01 said:
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.
Click to expand...
Click to collapse
1. Flash factory image
2. Boot system
3. Reboot bootloader
4. Fastboot Twrp 3.1.1.1
5. Flash Twrp 3.1.1.1 installer zip or not if you don't want permanent Twrp
6. Flash SuperSU or Magisk
7. Reboot system
I got LineageOS installed, restarted to bootloader and locked bootloader.
I can now:
Get into LineageOS Recovery
Boot to LineageOS ROM
I cannot:
Unlock bootloader
Unlock flashing
Unlock OEM from developer options (Option is greyed out)
What I tried, rooting and trying the following adb commands.
HTML:
adb root
adb shell setprop ro.oem_unlock_supported 1
Got the error:
HTML:
setprop: failed to set property 'ro.oem_unlock_supported' to '1'
I can only run LineageOS and go into LineageOS recovery and Adb sideload from recovery and install rooting apps.
Help! Want to 'fastboot flashing unlock'
Video:
https://vimeo.com/304615053
UPDATE:
UPDATE: Solution given by the dev razorloves(https://forum.xda-developers.com/member.php?u=614507) the dev who mantains the LineageOS ROM for Pixel details here:
https://forum.xda-developers.com/showpost.php?p=78361157&postcount=32
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Archangel said:
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
Click to expand...
Click to collapse
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
tomatosmoothie said:
Yeah, I goofed up.
Tried unlock_critical
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
[email protected]:~$
What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way
Click to expand...
Click to collapse
Archangel said:
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
Click to expand...
Click to collapse
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
I hearya nothings worse than having a problem and your the only one. Did that on a few phones. I have the Pixel 3 too now and I stay stock with some small edits and my Substratum themes running. I love the custom roms but sometimes they can be a real pain. Yeah I would give LOS 16 a try I guess what do you have to lose.
tomatosmoothie said:
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied Thank you!
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
tomatosmoothie said:
Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
Click to expand...
Click to collapse
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
bafforosso said:
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
Click to expand...
Click to collapse
Thanks, I was thinking the same thing, also, the idea was to flash a ROM that would be able to allow OEM unlocking in dev options, but I feel maybe LOS Recovery is not allowing me to unlock.
Also thinking of flashing stock factory image via LOS Recovery.
I will tread carefully though, thanks.
No way your bl is locked.
Sent from my Pixel XL using Tapatalk
lafester said:
No way your bl is locked.
Click to expand...
Click to collapse
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
bafforosso said:
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?
Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?
I think you really should try flashing stock firmware.
Click to expand...
Click to collapse
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
tomatosmoothie said:
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.
No padlock on the google screen.
I'm waiting for a factory image to download and will try flashing.
LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
Click to expand...
Click to collapse
Sorry I mixed things up : use the flash-all.sh (or flash-all.bat if using Windows) script with your device in fastboot mode as described on the stock firmwares download page.
[Correct but not for flashing stock firmware]
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
bafforosso said:
No idea, never used, but you should be able to "fastboot boot" into twrp and flash.
Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
Click to expand...
Click to collapse
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
tomatosmoothie said:
Tried that earlier, didn't work. Trying now.
Advanced Restart is enabled in Dev options.
Restarted to bootloader.
HTML:
[email protected]:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
[email protected]:~$
Click to expand...
Click to collapse
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
bafforosso said:
Sorry edited my post because I mixed up things, my bad.
No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
Click to expand...
Click to collapse
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
HTML:
[email protected]:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.025s
[email protected]:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.034s
[email protected]:~$ fastboot oem unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.027s
[email protected]:~$
tomatosmoothie said:
Yeah, that page says flash unlock is required
Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.
Click to expand...
Click to collapse
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
bafforosso said:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.
As you wish, it is your phone but if you don't try we'll never know...
Click to expand...
Click to collapse
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideload file.zip"
tomatosmoothie said:
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.
So the only choice is "adb sideloar file.zip"
Click to expand...
Click to collapse
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
bafforosso said:
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...
Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :
On your computer, download stock firmware full image for your device.
Unzip the stock firmware image just downloaded.
Open a terminal and navigate to the unzipped stock firmware image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system
P.S.: Forgot to warn but this will delete all your data from your phone.
Click to expand...
Click to collapse
Got a Permission denied.
HTML:
[email protected]:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$ ./flash-all.sh
bash: ./flash-all.sh: Permission denied
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.
I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.
Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.
How can I get things done back, all I've is fastboot.
It's a New set, please help (
dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.
tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img
SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro
joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.