Database Develop

[Q] HELP! Razr i doesn't get past boot screen!

Hello fellow users of the Razr i.
A friend of mine got this phone a long time ago and complained his phone wasn't starting... Since it seemed he phone got stuck on the bootscreen, i thought it would be quite easy to fix it through re-flashing another firmware, but i encountered some problems...quite a lot of them actually...
First of all, after getting on the bootloader screen, i saw the yellow message;
Fastboot Reason:
fastboot max download size: 100MB
Oddly, it doesn't show any information why it's fastboot download is limited.
I've managed to unlock the bootloader successfuly, even though it didn't really change much...
After downloading a rom and giving an attempt to flash through fastboot, it locks the whole process, failing when sending the system image, which is about 780mbs.
Searching a little bit more, i installed RSD Lite 6.1.4, and on the Device Properties side, it shows nothing at all. Everything is (N / A).
I'm not entirely sure if there's something wrong, but as far as i've noticed, the drivers and everything else seems to be working fine, since unlocking the bootloader didn't fail.
Any help on this is really appreciated!

michaelnishi said:
Hello fellow users of the Razr i.
A friend of mine got this phone a long time ago and complained his phone wasn't starting... Since it seemed he phone got stuck on the bootscreen, i thought it would be quite easy to fix it through re-flashing another firmware, but i encountered some problems...quite a lot of them actually...
First of all, after getting on the bootloader screen, i saw the yellow message;
Fastboot Reason:
fastboot max download size: 100MB
Oddly, it doesn't show any information why it's fastboot download is limited.
I've managed to unlock the bootloader successfuly, even though it didn't really change much...
After downloading a rom and giving an attempt to flash through fastboot, it locks the whole process, failing when sending the system image, which is about 780mbs.
Searching a little bit more, i installed RSD Lite 6.1.4, and on the Device Properties side, it shows nothing at all. Everything is (N / A).
I'm not entirely sure if there's something wrong, but as far as i've noticed, the drivers and everything else seems to be working fine, since unlocking the bootloader didn't fail.
Any help on this is really appreciated!
Click to expand...
Click to collapse
So u unlocked successfully. Then everything should be repairable.
The normal fastboot won't flash past 100mb for this device. So no problem there. U need to use mFastboot to get past that.
I don't know about RSD Lite. Maybe start it in administrator mode. Another thing u can do is get mFastboot and flash the system, recovery and boot manually. If that won't work we can try to use a custom rom with a custom recovery. By unlocking your warranty is already voided.
Do u know what firmware its holding? I know the device doesn't boot, but maybe u know.

Hazou said:
So u unlocked successfully. Then everything should be repairable.
The normal fastboot won't flash past 100mb for this device. So no problem there. U need to use mFastboot to get past that.
I don't know about RSD Lite. Maybe start it in administrator mode. Another thing u can do is get mFastboot and flash the system, recovery and boot manually. If that won't work we can try to use a custom rom with a custom recovery. By unlocking your warranty is already voided.
Do u know what firmware its holding? I know the device doesn't boot, but maybe u know.
Click to expand...
Click to collapse
I see...I'd need a tutorial on how to work properly with mfastboot though, never heard of it before.
And i don't know the firmware version either. I guess this is going to make it a little harder... Or we could, maybe try to use the latest possible firmware version and not worry about downgrade problems...

michaelnishi said:
I see...Id need a tutorial on how to work properly with mfastboot though, never heard of it before.
And i dont know the firmware version either. I guess this is going to make it a little harder... Or we could, maybe try to use the latest possible firmware version and not worry about downgrade problems...
Click to expand...
Click to collapse
Have a look at my signature. The Index guide in the general section. But i think to be really savwe could flash a custom rom and see what happends then. We can always go back after that.
Have a look around. I will help u if still needed, after 23.00 gmt+ for the mefastboot by making a guide for mfastboot and latest firmware. What region did the phone come?

Hazou said:
Have a look at my signature. The Index guide in the general section. But i think to be really savwe could flash a custom rom and see what happends then. We can always go back after that.
Have a look around. I will help u if still needed, after 23.00 gmt+ for the mefastboot by making a guide for mfastboot and latest firmware. What region did the phone come?
Click to expand...
Click to collapse
South America/Brazil. And thanks a lot for replying to me. I'm going to work soon, sadly, and i'm not sure when ill get back home. But as soon as i arrive i will be searching for a custom rom and trying to flash it.

Hazou said:
So u unlocked successfully. Then everything should be repairable.
The normal fastboot won't flash past 100mb for this device. So no problem there. U need to use mFastboot to get past that.
I don't know about RSD Lite. Maybe start it in administrator mode. Another thing u can do is get mFastboot and flash the system, recovery and boot manually. If that won't work we can try to use a custom rom with a custom recovery. By unlocking your warranty is already voided.
Do u know what firmware its holding? I know the device doesn't boot, but maybe u know.
Click to expand...
Click to collapse
Thanks a bunch for the help, Hazou. I've managed to get the mfastboot to work perfectly and it flashed the device as it should have. The thing is already up and running!

michaelnishi said:
Thanks a bunch for the help, Hazou. I've managed to get the mfastboot to work perfectly and it flashed the device as it should have. The thing is already up and running!
Click to expand...
Click to collapse
Glad to hear that it worked

Same issue - I trust this isn't a hijack
Good evening all,
My Razr I fails to boot, hanging on the initial Motorola M logo after the power on vibrate and green LED flash. It is unmolested in any way (no root, no custom anything). It's a UK retail ROM (from memory) and is not locked to a provider
The issue started on Sunday by randomly rebooting, the launcher crashing (home etc soft buttons not displaying). I tried to uninstall a few of the recently installed apps then upgraded what was left, only to have it reboot and not boot.
I have been browsing the forums and read a few bits and pieces, but it doesn't make much sense. I am IT literate, but new to Android in this sense of trying to fix things
So far I have installed
RSDLite v6.16
Clicking on "show device" gives me
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
In the table below Model is Fastboo SMI s
ABD:
C:\Users\User1\adb>adb devices
List of devices attached
Motorola Device Driver:
Device software update - come back later - The server is temporarily unavailable due to maintenance
I can boot into the AP Fastboot Flashmode by all 3 methods I found on here.
I get the menu in blue, where I went into recovery and formatted the cache - to no avail.
In Yellow it says:
Fastboot Reason:
Fastboot: max download size :100MB
USB Connected
I obviously have data which has no back up and I would hate to lose. Can I do a back up of everything in some way then reinstall the OS in whatever way is required?

black_cab said:
Good evening all,
My Razr I fails to boot, hanging on the initial Motorola M logo after the power on vibrate and green LED flash. It is unmolested in any way (no root, no custom anything). Its a UK retail ROM (from memory) and is not locked to a provider
The issue started on Sunday by randomly rebooting, the launcher crashing (home etc soft buttons not displaying). I tried to uninstall a few of the recently installed apps then upgraded what was left, only to have it reboot and not boot.
I have been browsing the forums and read a few bits and pieces, but it doesnt make much sense. I am IT literate, but new to Android in this sense of trying to fix things
So far I have installed
RSDLite v6.16
Clicking on "show device" gives me
ESN: N/A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: N / A
DRM Version: N / A
In the table below Model is Fastboo SMI s
ABD:
C:\Users\User1\adb>adb devices
List of devices attached
Motorola Device Driver:
Device software update - come back later - The server is temporarily unavailable due to maintenance
I can boot into the AP Fastboot Flashmode by all 3 methods I found on here.
I get the menu in blue, where I went into recovery and formatted the cache - to no avail.
In Yellow it says:
Fastboot Reason:
Fastboot: max download size :100MB
USB Connected
I obviously have data which has no back up and I would hate to lose. Can I do a back up of everything in some way then reinstall the OS in whatever way is required?
Click to expand...
Click to collapse
Search for mFastboot in the index thread. Make sure u have your firmware ready and unpacked. Reboot in fastboot mode and do the command "mfastboot devices" when device is connected to usb. It will list your device.
Now try to flash the system partition by sending the command "mfastboot flash system <path to system image>"
Do the same with the boot.img with the command "mfastboot flash boot <path to boot image>
If this wont work, there is no possible way to get your data back as far as i know.

Hi, thanks for the quick reply
Hazou said:
Search for mFastboot in the index thread. Make sure u have your firmware ready and unpacked. Reboot in fastboot mode and do the command "mfastboot devices" when device is connected to usb. It will list your device.
Click to expand...
Click to collapse
I guess I am looking for the closest firmware to what I have? I did see a link to a page of images somewhere in this section, so will find it again
Hazou said:
Now try to flash the system partition by sending the command "mfastboot flash system <path to system image>"
Do the same with the boot.img with the command "mfastboot flash boot <path to boot image>
If this wont work, there is no possible way to get your data back as far as i know.
Click to expand...
Click to collapse
Cool will give it a go

filenames?
I downloaded and unzipped CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml.zip to C:\Users\User1\android\firmware\CFC which contains the following files
Directory of C:\Users\User1\android\firmware\CFC
05/11/2014 19:38 11,534,336 boot_signed
05/11/2014 19:38 8,160,652 bos_signed
05/11/2014 19:39 54,536,192 cdrom_signed
05/11/2014 19:39 1,462 CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
05/11/2014 19:39 66,528 dnx
05/11/2014 19:39 32,768 gpt_signed
05/11/2014 19:39 1,937,660 ifwi
05/11/2014 19:39 875,336 logo_signed
05/11/2014 19:39 23,832,048 motoboot
05/11/2014 19:39 17,501,930 motobp
05/11/2014 19:39 11,534,336 recovery_signed
05/11/2014 19:40 850,539,260 system_signed
05/11/2014 19:40 875,336 ulogo_signed
mfastboot devices results in TA32404O14 fastboot
So far so good
Hazou said:
Now try to flash the system partition by sending the command "mfastboot flash system <path to system image>"
Do the same with the boot.img with the command "mfastboot flash boot <path to boot image>
Click to expand...
Click to collapse
so my commands will be
mfastboot flash system C:\Users\User1\android\firmware\CFC\system_signed
mfastboot flash boot c:\...\motoboot ?

black_cab said:
I downloaded and unzipped CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml.zip to C:\Users\User1\android\firmware\CFC which contains the following files
Directory of C:\Users\User1\android\firmware\CFC
05/11/2014 19:38 11,534,336 boot_signed
05/11/2014 19:38 8,160,652 bos_signed
05/11/2014 19:39 54,536,192 cdrom_signed
05/11/2014 19:39 1,462 CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml
05/11/2014 19:39 66,528 dnx
05/11/2014 19:39 32,768 gpt_signed
05/11/2014 19:39 1,937,660 ifwi
05/11/2014 19:39 875,336 logo_signed
05/11/2014 19:39 23,832,048 motoboot
05/11/2014 19:39 17,501,930 motobp
05/11/2014 19:39 11,534,336 recovery_signed
05/11/2014 19:40 850,539,260 system_signed
05/11/2014 19:40 875,336 ulogo_signed
mfastboot devices results in TA32404O14 fastboot
So far so good
so my commands will be
mfastboot flash system C:\Users\User1\android\firmware\CFC\system_signed
mfastboot flash boot c:\...\motoboot ?
Click to expand...
Click to collapse
The system is good. For boot take boot_signed

Hazou said:
The system is good. For boot take boot_signed
Click to expand...
Click to collapse
mfastboot flash system C:\Users\User1\android\firmware\CFC\system_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 10.125s]
writing 'system'...
OKAY [ 2.769s]
sending 'system' (102400 KB)...
OKAY [ 16.931s]
writing 'system'...
OKAY [ 2.668s]
sending 'system' (102400 KB)...
OKAY [ 14.804s]
writing 'system'...
OKAY [ 2.687s]
sending 'system' (102400 KB)...
OKAY [ 14.098s]
writing 'system'...
OKAY [ 2.497s]
sending 'system' (102400 KB)...
OKAY [ 14.420s]
writing 'system'...
OKAY [ 2.508s]
sending 'system' (102400 KB)...
OKAY [ 12.225s]
writing 'system'...
OKAY [ 2.499s]
sending 'system' (102400 KB)...
OKAY [ 14.111s]
writing 'system'...
OKAY [ 2.474s]
sending 'system' (102400 KB)...
OKAY [ 14.652s]
writing 'system'...
OKAY [ 2.509s]
sending 'system' (11404 KB)...
OKAY [ 8.356s]
writing 'system'...
OKAY [ 2.071s]
finished. total time: 142.472s
mfastboot flash boot C:\Users\User1\android\firmware\CFC\boot_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.448s]
writing 'boot'...
OKAY [ 3.181s]
finished. total time: 4.635s
So it looks like the images were sent.
On the phone I got a few Downloading ... MultiFlashing system ... etc
then
MultiFlashing system ...
Getvar max-sparse-size
Fastboot command failed
Now it says Flashing boot, but seems to be hung, been like that for 5 mins or so. How long should it take?
Actually ignore that, it has booted!
Thanks very much for all your assistance

Glad it worked

[Q] Not quite Bricked, but can't get anything but Fastboot

Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....

Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.

i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:

Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.

Wipe cache through fastboot and try again. It van help

fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s​
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)

ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s​
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!

Installing TWRP on bricked, but not rooted Sprint M7?

After not messing with my wife's M7 for quite some time, I am back for another go at it. She managed to mess up her LG G3, so recovering the M7 is now back on the table. My goal has been to try to recover the data on the phone, so I have not tried a factory reset. Deleting the cache partition in the recovery menu also proved futile.
I have HBOOT 1.57, and a looked bootloader. I have ADB and Fastboot on my PC, and can get the phone into FASTBOOT USB, but my attempts to copy over TWRP 2.7.0.1 haven't worked.
What I got was this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (7918 KB)...
OKAY [ 1.132s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.780s
Can it be done with a bricked phone and a locked bootloader, or am I just wildly grasping at false hope?

groovyz1k said:
After not messing with my wife's M7 for quite some time, I am back for another go at it. She managed to mess up her LG G3, so recovering the M7 is now back on the table. My goal has been to try to recover the data on the phone, so I have not tried a factory reset. Deleting the cache partition in the recovery menu also proved futile.
I have HBOOT 1.57, and a looked bootloader. I have ADB and Fastboot on my PC, and can get the phone into FASTBOOT USB, but my attempts to copy over TWRP 2.7.0.1 haven't worked.
What I got was this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (7918 KB)...
OKAY [ 1.132s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.780s
Can it be done with a bricked phone and a locked bootloader, or am I just wildly grasping at false hope?
Click to expand...
Click to collapse
I hate to be the one, but you are wildly grasping for a false hope. You need unlocked bootloader in order to flash custom recovery

That is actually a pretty big relief at this point. I was more mad that I was doing something wrong than I was about recovering the phone. Thanks! I should have asked the question hours earlier so I didn't waste all that time. I picked up some new understanding though, so all was not lost.

Factory Reset seems to have failed!
Mine shows:
-- Wiping data...
Formatting /data...
Backup Data Preload
Backup CW Package
Restore Data Preload
Restore CW Package
Formatting /cache
Data Wipe Complete.
Write host_mode:0 done
Then it gives me the same system recovery menu. Rebooting just put it right back into the same loop.

TF701T - getting FAILED (remote: Unsupport Flash Unsparse System Image.)

I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s

I've managed to resolve it for anyone else that might read this....
Follow the guide here https://forum.xda-developers.com/tr...f701t-nvflash-unbrick-solutiontested-t3742848 and use the NvFlash TF701T Unbrick tool, you need to do a bit of prep but it worked for me
Big thanks to Mr.Bin for this fix.
Cheers and good luck
Martin
martinnut said:
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
Click to expand...
Click to collapse

Device Locked in fastboot even with unlocked bootloader

Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.

ahsank128 said:
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
Click to expand...
Click to collapse
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?

Mackay53 said:
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Click to expand...
Click to collapse
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image

ahsank128 said:
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
Click to expand...
Click to collapse
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?

Badger50 said:
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Click to expand...
Click to collapse
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked

ahsank128 said:
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
Click to expand...
Click to collapse
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:

Badger50 said:
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Click to expand...
Click to collapse
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol

ahsank128 said:
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
Click to expand...
Click to collapse
I know who you are? At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?

Badger50 said:
I know who you are At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Click to expand...
Click to collapse
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10

ahsank128 said:
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
Click to expand...
Click to collapse
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:

Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Will attempt this, my attempt last night was to do factory reset within the settings (when phone is booted up) and then flashed with -w. But I will try again using the stock recovery. I even changed computers, this stuff is wonky sometimes

Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)

DELETED

ahsank128 said:
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Click to expand...
Click to collapse
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes

ahsank128 said:
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
Click to expand...
Click to collapse
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.

Badger50 said:
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
Click to expand...
Click to collapse
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
Code:
Sending 'bootloader' (8761 KB) OKAY [ 0.218s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_b' (82676 KB) OKAY [ 2.180s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_b
OKAY [ 0.650s]
Finished. Total time: 3.090s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 99171FFAZ006J5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.069s]
Checking 'version-bootloader' OKAY [ 0.069s]
Checking 'version-baseband' OKAY [ 0.068s]
Setting current slot to 'b' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.387s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.139s]
Writing 'boot_b' OKAY [ 0.455s]
extracting dtbo.img (8 MB) to disk... took 0.025s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.117s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_b' OKAY [ 0.072s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.101s]
Writing 'vbmeta_system_b' OKAY [ 0.072s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.069s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_b' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2127 MB) to disk... took 15.801s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?

bb709394 said:
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Click to expand...
Click to collapse
No, this issue happens on stock kernel. And yes USB debugging and OEM Unlock both are checked. I believe the image is correct. US Unlocked Pixel from google store. file ends in 011

ahsank128 said:
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
Click to expand...
Click to collapse
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?

Badger50 said:
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Click to expand...
Click to collapse
I am up and running, I'll check to see if I can get that script running later on

ahsank128 said:
I am up and running, I'll check to see if I can get that script running later on
Click to expand...
Click to collapse
Kinda sounds like you already got the script to work