Problems with fastboot - Motorola Photon Q 4G LTE

Right after getting my phone, I went ahead and unlocked the bootloader (as doing it will wipe the phone). It's been a week, and today when I went to reboot, I'm getting a "flash failure" and the phone is dropping me into fastboot. If I reboot the phone using power-M, it will boot normally.
Any thoughts?

nightwkr said:
Right after getting my phone, I went ahead and unlocked the bootloader (as doing it will wipe the phone). It's been a week, and today when I went to reboot, I'm getting a "flash failure" and the phone is dropping me into fastboot. If I reboot the phone using power-M, it will boot normally.
Any thoughts?
Click to expand...
Click to collapse
All you have to do is reflash any partition and you'll be completely fine. What I normally do is flash a logo.img like this:
Code:
fastboot flash logo logo.img
or
Code:
fastboot flash logo logo.bin
Logo.img can be a custom logo.img or one from a similar device.
This is one I have from the Atrix HD for example:
https://dl.dropbox.com/u/15093625/logo.bin

Partition?
mattlgroff said:
All you have to do is reflash any partition and you'll be completely fine. What I normally do is flash a logo.img like this:
Code:
fastboot flash logo.bin logo.img
or
Code:
fastboot flash logo.bin logo.bin
Logo.img can be a custom logo.img or one from a similar device.
Click to expand...
Click to collapse
Pardon my ignorance, but which partition should that be flashed onto? I'm getting "Invalid partition name 'logo.bin'", I expect that is supposed to be a partition rather than a filename.

nightwkr said:
Pardon my ignorance, but which partition should that be flashed onto? I'm getting "Invalid partition name 'logo.bin'", I expect that is supposed to be a partition rather than a filename.
Click to expand...
Click to collapse
It's either "logo" or "logo.bin" for the partition. On OMAP phones its logo.bin, sorry for the mistake

nm - Worked it out
nightwkr said:
Pardon my ignorance, but which partition should that be flashed onto? I'm getting "Invalid partition name 'logo.bin'", I expect that is supposed to be a partition rather than a filename.
Click to expand...
Click to collapse
Thank you very much for your help - It's the logo partition. My phone is now working correctly!

nightwkr said:
Thank you very much for your help - It's the logo partition. My phone is now working correctly!
Click to expand...
Click to collapse
Curious though, does your boot logo look different from original? I know the screens are supposed to be different between the 2 phones anyway.

Bootloader logo
mattlgroff said:
Curious though, does your boot logo look different from original? I know the screens are supposed to be different between the 2 phones anyway.
Click to expand...
Click to collapse
My bootloader logo is the "Warning: Bootloader is unlocked" message. I wonder if when the bootloader is unlocked that Motorola overrides the actual logo to give the message.
After that message, I have the glowing Motorola M, followed by the Sprint boot screen - I expect those are the bootup animations in the OS itself.

nightwkr said:
My bootloader logo is the "Warning: Bootloader is unlocked" message. I wonder if when the bootloader is unlocked that Motorola overrides the actual logo to give the message.
After that message, I have the glowing Motorola M, followed by the Sprint boot screen - I expect those are the bootup animations in the OS itself.
Click to expand...
Click to collapse
On the Atrix HD bootloader strings.exe did show mention of logo_locked and logo_unlocked. Must have been that indeed. Thanks!

Bootloader logo
mattlgroff said:
On the Atrix HD bootloader strings.exe did show mention of logo_locked and logo_unlocked. Must have been that indeed. Thanks!
Click to expand...
Click to collapse
I'd love to confirm that's the filename on the Photon Q. I very much want to replace that stupid message.

nightwkr said:
I'd love to confirm that's the filename on the Photon Q. I very much want to replace that stupid message.
Click to expand...
Click to collapse
Try to see if you can fastboot to logo_unlocked and see what it says.

mattlgroff said:
Try to see if you can fastboot to logo_unlocked and see what it says.
Click to expand...
Click to collapse
No go:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash logo_un
locked logo.bin
sending 'logo_unlocked' (4096 KB)...
OKAY [ 0.328s]
writing 'logo_unlocked'...
(bootloader) Invalid partition name logo_unlocked
FAILED (remote failure)
finished. total time: 0.421s
C:\Program Files (x86)\Android\android-sdk\platform-tools>

nightwkr said:
No go:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash logo_un
locked logo.bin
sending 'logo_unlocked' (4096 KB)...
OKAY [ 0.328s]
writing 'logo_unlocked'...
(bootloader) Invalid partition name logo_unlocked
FAILED (remote failure)
finished. total time: 0.421s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
I think you need to go complain on the Motorola forums lol

mattlgroff said:
I think you need to go complain on the Motorola forums lol
Click to expand...
Click to collapse
Heh - Well, thanks for your help anyway.

nightwkr said:
I'd love to confirm that's the filename on the Photon Q. I very much want to replace that stupid message.
Click to expand...
Click to collapse
Yeah, seriously!

kcrudup said:
Yeah, seriously!
Click to expand...
Click to collapse
+...3?
I'd like to try and figure this out as well... I guess in time.

arrrghhh said:
+...3?
I'd like to try and figure this out as well... I guess in time.
Click to expand...
Click to collapse
It is the logo, flash a new one.
Sent from my XT897 using xda premium

fallnSaint said:
It is the logo, flash a new one.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
+1 mentioned that in the other thread.
Sent from my XT897 using xda premium
---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------
I just installed recovery over again and the failed fastboot went away.
Sent from my XT897 using xda premium
---------- Post added at 08:21 PM ---------- Previous post was at 08:05 PM ----------
Also fallnSaint has thread about the logo thing. In the themes and apps section also the right command to flash the the logo.bin.
http://forum.xda-developers.com/showthread.php?p=31223746
Sent from my XT897 using xda premium

Sure, this might be just a plug...
But I didn't have this issue, at all, since playing with TWRP.
I'm curious if anyone else has the issue with TWRP

It's not a recovery issue, it's a bootloader issue. Flash a bad image (or try to use "fastboot boot" on an unsigned image) and you'll have the same problem until you make a good flash, regardless of recovery.

kcrudup said:
It's not a recovery issue, it's a bootloader issue. Flash a bad image (or try to use "fastboot boot" on an unsigned image) and you'll have the same problem until you make a good flash, regardless of recovery.
Click to expand...
Click to collapse
Ah, it could very well have been my 'fastboot boot' attempts. I tried doing this before flashing, with the hopes that I could give the recovery a shot before flashing...
Thanks!

Related

Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"

Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
You can read this to see if it helps..good luck..:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2528313
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
Sorry, but after reading your post 4 times I still have no idea what you actually did.....
If you still have access in ADB (since you can't access the bootloader??) the link LMK gave you may save your bacon.
If you don't have any kind of access: ADB or fastboot and you do not have nvFlash blobs - sorry, you bricked.
Can I access fastboot when I get the menu at RCK / Android / Wipe? Because if I click con any of these its says that bootloader is corrupted.
What's the Command to fix TWRP using a computer / or other Android device?
ANDROiD_eKa said:
Can I access fastboot when I get the menu at RCK / Android / Wipe?
Click to expand...
Click to collapse
Does it say something about fastboot in the upper left corner?
ANDROiD_eKa said:
What's the Command to fix TWRP using a computer / or other Android device?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Thanks _that for the advice...:good: You are the expert in this area... I am done with my job to bring you in here for helps..haha...
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Yes it says
Code:
Starting Fastboot USB download protocol
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
ANDROiD_eKa said:
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
Click to expand...
Click to collapse
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
LetMeKnow said:
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
berndblb said:
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
Click to expand...
Click to collapse
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
LetMeKnow said:
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
Click to expand...
Click to collapse
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
berndblb said:
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
Click to expand...
Click to collapse
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
LetMeKnow said:
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
Click to expand...
Click to collapse
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
berndblb said:
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
Click to expand...
Click to collapse
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
buster99 said:
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
ANDROiD_eKa said:
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
Click to expand...
Click to collapse
Buster99 deserves a medal or something for this post. Dozens of people have recovered from a brick using his method!
Glad you got it going!

[Q] XT925 partition error?

My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>fastboot flash re covery twrp-hdrecovery.img
sending 'recovery' (6678 KB)... OKAY [ 0.844s]
writing 'recovery'...
INFOFailed to erase partition INFOFailed to flash partition recovery
FAILED (remote failure) finished. total time: 1.000s
Click to expand...
Click to collapse
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
"Partition signed?"
is0lde said:
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
Click to expand...
Click to collapse
I have also tried reflashing rom using RSD Lite, and get a the Following error
Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL.
Click to expand...
Click to collapse
is0lde said:
I have also tried reflashing rom using RSD Lite, and get a the Following error
Click to expand...
Click to collapse
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Same problem
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
kumeipark said:
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
mari18cf said:
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
Click to expand...
Click to collapse
flash the partition file with "Mfastboot", then re-flash the stock file with only the partition, tz, and getvar(you may not have this) removed.

Fastboot "Command not Allowed"

Hi!
I am trying to flash my Xperia L which is already rooted.
I got my "unlock bootloader key" and not when I try to unlock it with the key it says-
FAILED <Command did not succeed.>
Second time try the same statement again and it says OK!
After that when I try to flash a recovery it says-
F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery
philztaoshan.img
sending 'recovery' (12452 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.402s
It is able to write a kernel's boot image however, but then it doesn't not even boot. (Even the screen doesn't turn on)
I will be thankful to any help!
srishabhiitk said:
Hi!
I am trying to flash my Xperia L which is already rooted.
I got my "unlock bootloader key" and not when I try to unlock it with the key it says-
FAILED <Command did not succeed.>
Second time try the same statement again and it says OK!
After that when I try to flash a recovery it says-
F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery
philztaoshan.img
sending 'recovery' (12452 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.402s
It is able to write a kernel's boot image however, but then it doesn't not even boot. (Even the screen doesn't turn on)
I will be thankful to any help!
Click to expand...
Click to collapse
Is you're phone bootloader unlockable?
Yes!
Lazynestor said:
Is you're phone bootloader unlockable?
Click to expand...
Click to collapse
Yes, Unlockable and unlocked!
Actually I was using Cyanogenmod 12 by Varun Chitre and when I wanted to switch to Nightly version this error came and I couldn't find a s loution.
srishabhiitk said:
Yes, Unlockable and unlocked!
Actually I was using Cyanogenmod 12 by Varun Chitre and when I wanted to switch to Nightly version this error came and I couldn't find a s loution.
Click to expand...
Click to collapse
Did you try to flash it with Flashtool?
Also try right click on cmd and open as administrator
Fabulous_Pancake said:
Did you try to flash it with Flashtool?
Also try right click on cmd and open as administrator
Click to expand...
Click to collapse
Yes, I've tried flashtool and it gives same error. I didn't try running cmd as administrator but I doubt it would change anything..
hmm you have this problem with other kernels? also try fastboot flash boot philztaoshan.img
You can't use fastboot with recovery command.
Xperia doesn't have recovery partition
Fabulous_Pancake said:
hmm you have this problem with other kernels? also try fastboot flash boot philztaoshan.img
Click to expand...
Click to collapse
Yeah! I couldn't flash anything after that error started coming.
underd0g said:
You can't use fastboot with recovery command.
Xperia doesn't have recovery partition
Click to expand...
Click to collapse
I guess that may be the problem because everything was working fine. Until I had to flash a custom recovery like Philz through fastboot.
I didn't know the command so I searched for a general one. I used "fastboot flash recovery recovery.zip".
But there is one other thing that when I tried to install Thunderzap Kernel through Flashtool my phone even stopped showing SONY splash screen and just vibrated trying to boot!
Please tell me the correct procedure to flash custom recovery through fastboot in Xperia Phone.
As far as I know there are 2 recovery that can be flashed to FOTAKernel partition.
TWRP compiled by rohan.purohit and Phil ported by sdt.
The only method to flash FOTAKernel (recovery) is via adb shell or terminal emulator.
See TWRP thread at Original Dev section
just flash thunderzap 4.14 and cm12. extract boot.img from tz zip and go into fastboot mode on your device than simply flash extracted boot img with flashboot
Fabulous_Pancake said:
just flash thunderzap 4.14 and cm12. extract boot.img from tz zip and go into fastboot mode on your device than simply flash extracted boot img with flashboot
Click to expand...
Click to collapse
I tried to install thunderzap using Flashtool, the device stopped booting. I had to flash stock ftf!
underd0g said:
As far as I know there are 2 recovery that can be flashed to FOTAKernel partition.
TWRP compiled by rohan.purohit and Phil ported by sdt.
The only method to flash FOTAKernel (recovery) is via adb shell or terminal emulator.
See TWRP thread at Original Dev section
Click to expand...
Click to collapse
I will try that and get back to you!
srishabhiitk said:
Hi!
I am trying to flash my Xperia L which is already rooted.
I got my "unlock bootloader key" and not when I try to unlock it with the key it says-
FAILED
Second time try the same statement again and it says OK!
After that when I try to flash a recovery it says-
F:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery
philztaoshan.img
sending 'recovery' (12452 KB)...
OKAY [ 0.397s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.402s
It is able to write a kernel's boot image however, but then it doesn't not even boot. (Even the screen doesn't turn on)
I will be thankful to any help!
Click to expand...
Click to collapse
your command is just wrong... even if you flash recovery you have to flash it as kernel in xperia devices
fastboot flash boot boot.img
is the correct command eg:
fastboot flash boot c:\recovery.img
Sent from my C2105 using XDA Free mobile app
---------- Post added at 12:55 PM ---------- Previous post was at 12:55 PM ----------
srishabhiitk said:
I will try that and get back to you!
Click to expand...
Click to collapse
you cant flash fota recovery ob stock...
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
your command is just wrong... even if you flash recovery you have to flash it as kernel in xperia devices
fastboot flash boot boot.img
is the correct command eg:
fastboot flash boot c:\recovery.img
Sent from my C2105 using XDA Free mobile app
---------- Post added at 12:55 PM ---------- Previous post was at 12:55 PM ----------
you cant flash fota recovery ob stock...
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Should I simply try flashing Philz Recovery with command-
fastboot flash boot c:\recovery.img
srishabhiitk said:
Should I simply try flashing Philz Recovery with command-
fastboot flash boot c:\recovery.img
Click to expand...
Click to collapse
if recovery is in c then yes
maybe its / not \
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
if recovery is in c then yes
maybe its / not \
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
I guess it is, because it has already worked before using just normal commands.
srishabhiitk said:
I guess it is, because it has already worked before using just normal commands.
Click to expand...
Click to collapse
lol you mean you are not knowing where your file is? crazy xD
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
lol you mean you are not knowing where your file is? crazy xD
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Oh! You meant recovery on my PC.. I thought the partition on my phone
srishabhiitk said:
Oh! You meant recovery on my PC.. I thought the partition on my phone
Click to expand...
Click to collapse
and did it work
Sent from my C2105 using XDA Free mobile app

Stuck at boot up failed!

Hey guys,
I wanted to have the Android 5.1 update so I looked up how I can do this.
I ended up at a youtube video called ''How to Install OFFICIAL Android 5.1 Lollipop GPe on Moto G [XT1033 & XT1032]'' by Samanyou Garg.
I did the first thing he said with the file called 5.x to 4.4.4 gpe. after I did this my phone didn't boot up. Now i'm stuck at th bootloader menu and if i try anything it says ''boot up failed''
Please help me with this problem, im stuck for 4 days right now! and I really need my phone tommorow.
poolta321 said:
Hey guys,
I wanted to have the Android 5.1 update so I looked up how I can do this.
I ended up at a youtube video called ''How to Install OFFICIAL Android 5.1 Lollipop GPe on Moto G [XT1033 & XT1032]'' by Samanyou Garg.
I did the first thing he said with the file called 5.x to 4.4.4 gpe. after I did this my phone didn't boot up. Now i'm stuck at th bootloader menu and if i try anything it says ''boot up failed''
Please help me with this problem, im stuck for 4 days right now! and I really need my phone tommorow.
Click to expand...
Click to collapse
Flash a custom recovery and wipe system ,data,dalvik and cache then flash cm 12.1 nightly
sjandroiddeveloper said:
Flash a custom recovery and wipe system ,data,dalvik and cache then flash cm 12.1 nightly
Click to expand...
Click to collapse
I tried to flash TWRP but when I put ''adb devices'' in cmd it doesn't come up with my device
update: wait It does work now with fastboot devices
poolta321 said:
I tried to flash TWRP but when I put ''adb devices'' in cmd it doesn't come up with my device
update: wait It does work now with fastboot devices
Click to expand...
Click to collapse
Okay I flashed TWRP but when I do recovery It still says Boot up failed
poolta321 said:
Okay I flashed TWRP but when I do recovery It still says Boot up failed
Click to expand...
Click to collapse
First if all don't do things you don't know about, just watching a random YouTube videos and following is a stupid thing
Now try this
In fastboot mode enter following commands
fastboot erase recovery
fastboot flash recovery recovery.img
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
And why did you make 4 threads for the same thing
Dont spam please
sjandroiddeveloper said:
First if all don't do things you don't know about, just watching a random YouTube videos and following is a stupid thing
Now try this
In fastboot mode enter following commands
fastboot erase recovery
fastboot flash recovery recovery.img
---------- Post added at 12:24 PM ---------- Previous post was at 12:23 PM ----------
And why did you make 4 threads for the same thing
Dont spam please
Click to expand...
Click to collapse
sorry for the many threads.
I did what you said and reflashed TWRP but it still says Boot up failed when I go to recovery
poolta321 said:
sorry for the many threads.
I did what you said and reflashed TWRP but it still says Boot up failed when I go to recovery
Click to expand...
Click to collapse
When you flash recovery what does it say on phone's fastboot screen
sjandroiddeveloper said:
When you flash recovery what does it say on phone's fastboot screen
Click to expand...
Click to collapse
cmd: getvarartition-type:recovery
cmd: erase:recovery
cmd: getvarartition-type recovery
cmd: getvar:max-download-size
cmd: download:007b1800
cmd: flash: recovery
Mismatched partition size (recovery)
Boot up failed
poolta321 said:
cmd: getvarartition-type:recovery
cmd: erase:recovery
cmd: getvarartition-type recovery
cmd: getvar:max-download-size
cmd: download:007b1800
cmd: flash: recovery
Mismatched partition size (recovery)
Boot up failed
Click to expand...
Click to collapse
lol didn't mean to put the smileys there
poolta321 said:
lol didn't mean to put the smileys there
Click to expand...
Click to collapse
Try to flash Philz
And if that doesnt work out then flash the stock 5.0.2 Asian firmware for xt1033
That's the only thing you can do
sjandroiddeveloper said:
Try to flash Philz
And if that doesnt work out then flash the stock 5.0.2 Asian firmware for xt1033
That's the only thing you can do
Click to expand...
Click to collapse
tried Philz and it still says Mismatching partition and boot up failed
Tried stock 5.0.2 Asian firmware for xt1033 but it didn't do anything. on cmd I typed the code but nothing came up
poolta321 said:
tried Philz and it still says Mismatching partition and boot up failed
Tried stock 5.0.2 Asian firmware for xt1033 but it didn't do anything. on cmd I typed the code but nothing came up
Click to expand...
Click to collapse
Mismatch partition size will always occur while flashing a custom recovery, no need to worry about it
And what do you mean nothing came up when you typed commands
Some output must have come
sjandroiddeveloper said:
Mismatch partition size will always occur while flashing a custom recovery, no need to worry about it
And what do you mean nothing came up when you typed commands
Some output must have come
Click to expand...
Click to collapse
image is in attachments.
this happens for all the codes i type via mfastboot.exe
poolta321 said:
image is in attachments.
this happens for all the codes i type via mfastboot.exe
Click to expand...
Click to collapse
Wait it works right now.
I didn't knew I needed to paste the mfasboot in the SDK folder
poolta321 said:
Wait it works right now.
I didn't knew I needed to paste the mfasboot in the SDK folder
Click to expand...
Click to collapse
Okay it finished. but still doesn't do anything.....
It still says Boot up failed an when I try to turn it on it says Fastboot Reason: Fall-trough from normal boot mode
poolta321 said:
Okay it finished. but still doesn't do anything.....
It still says Boot up failed an when I try to turn it on it says Fastboot Reason: Fall-trough from normal boot mode
Click to expand...
Click to collapse
I think your bootloader is corrupted or something like that
sjandroiddeveloper said:
I think your bootloader is corrupted or something like that
Click to expand...
Click to collapse
Is there a way to fix it?
poolta321 said:
Is there a way to fix it?
Click to expand...
Click to collapse
There are plenty of people who have killed their phones by doing something the result of which was corrupt bootloader
And sadly there is no way to fix it
sjandroiddeveloper said:
There are plenty of people who have killed their phones by doing something the result of which was corrupt bootloader
And sadly there is no way to fix it
Click to expand...
Click to collapse
So my phone is broke?
poolta321 said:
So my phone is broke?
Click to expand...
Click to collapse
Technically its called hardbricked

Razer phone Android 9.0 Pie cheryl-P-Magisk-twrp-boot

This boot comes with twrp and Magisk
Fastboot command :
fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
fastboot flash boot_b cheryl-P-Magisk-twrp-boot.img
fastboot reboot
download
https://drive.google.com/file/d/1VbmtVm3OGLxXYZ92YOOxsQkoyuOvi91_/view?usp=sharing
Thanks @将军和妓 Making a boot file
Twrp is working for me but not Magisk, I had to flash it via recovery. Thank you very much for sharing
MusTangKKK said:
This boot comes with twrp and Magisk
Fastboot command :
fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
fastboot flash boot_b cheryl-P-Magisk-twrp-boot.img
fastboot reboot
download
https://drive.google.com/file/d/1VbmtVm3OGLxXYZ92YOOxsQkoyuOvi91_/view?usp=sharing
Thanks @将军和妓 Making a boot file
Click to expand...
Click to collapse
I tried with fastboot boot cheryl-P-Magisk-twrp-boot.img and nothing happened.
I'll try properly flashing the image when I have the time to make a backup.
Anyone has been able to backup the clean Pie boot.img ?
EDIT: Tried flashing the boot image and it bootloops. Maybe device encription has to be disabled for twrp to work?
thank you so much for this
I worked after I flashed my phone to 7.1.1 and updated to 9 but when I did it again and after updated did a wipe(just going into the setting and wiping) I couldn't flash part b of the boot just got an error
:tools root# ./fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
Sending 'boot_a' (26840 KB) OKAY [ 0.840s]
Writing 'boot_a' OKAY [ 3.657s]
Finished. Total time: 4.503s
:tools root# ./fastboot flash boot_B cheryl-P-Magisk-twrp-boot.img
Sending 'boot_B' (26840 KB) OKAY [ 0.659s]
Writing 'boot_B' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
(EDIT: I'm retarded didn't notice the uppercase B but it seem they really didn't care of Gen1)
If you can't get into the system, you can go in twrp to restore factory settings and then restart, you can enter the system
MusTangKKK said:
If you can't get into the system, you can go in twrp to restore factory settings and then restart, you can enter the system
Click to expand...
Click to collapse
No everything is working just notice it said Razer 2
Djcall11 said:
No everything is working just notice it said Razer 2
Click to expand...
Click to collapse
This boot only supports Razer phone 1
[/LIST]
[/LIST]
MusTangKKK said:
If you can't get into the system, you can go in twrp to restore factory settings and then restart, you can enter the system
Click to expand...
Click to collapse
MusTangKKK said:
This boot only supports Razer phone 1
Click to expand...
Click to collapse
My guy only Razer 1 has 7.1.1 I just seen this after I reset after updating to pie everything I fine thank or care doe
I made the mistake of trying to get into recovery after this update using the Volume + plug in USB-C. (Update removed root/Magisk of course). It then wiped my entire device!!! No warning. No recovery screen. Just a message saying wiping device.
I immediately wiped it to put Lineage on it.
waiflih said:
I tried with fastboot boot cheryl-P-Magisk-twrp-boot.img and nothing happened.
I'll try properly flashing the image when I have the time to make a backup.
Anyone has been able to backup the clean Pie boot.img ?
EDIT: Tried flashing the boot image and it bootloops. Maybe device encription has to be disabled for twrp to work?
Click to expand...
Click to collapse
You need to make a copy of the flash all batch file and edit it and take out the line that reads "erase userdata" save the file. What this will do is make the factory image skip factory reset if you want to keep your files but wanna restore to fix or whatever.
---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------
MusTangKKK said:
This boot comes with twrp and Magisk
Fastboot command :
fastboot flash boot_a cheryl-P-Magisk-twrp-boot.img
fastboot flash boot_b cheryl-P-Magisk-twrp-boot.img
fastboot reboot
download
https://drive.google.com/file/d/1VbmtVm3OGLxXYZ92YOOxsQkoyuOvi91_/view?usp=sharing
Thanks @将军和妓 Making a boot file
Click to expand...
Click to collapse
So i flashed this and i also even tried flashing twrp and magisk like normal but after i would boot, most apps would not load. Im currently reverted to 8 to figure this out. If you could help me figure out what is wrong, would be appreciated.
Guys am running android 9 on razer phone 1 and bootloader unlocked. However keep getting error write to device failed. Any advise please?
marvi0 said:
Guys am running android 9 on razer phone 1 and bootloader unlocked. However keep getting error write to device failed. Any advise please?
Click to expand...
Click to collapse
Any suggestions?
marvi0 said:
Guys am running android 9 on razer phone 1 and bootloader unlocked. However keep getting error write to device failed. Any advise please?
Click to expand...
Click to collapse
Do you have both parts of the bootloader unlocked?
iliais347 said:
Do you have both parts of the bootloader unlocked?
Click to expand...
Click to collapse
hello buddy. Aaa you might be onto something. I am afraid I don't have my phone with me now. How do I check though if I have both parts of the bootloader unlocked?
marvi0 said:
hello buddy. Aaa you might be onto something. I am afraid I don't have my phone with me now. How do I check though if I have both parts of the bootloader unlocked?
Click to expand...
Click to collapse
Try fastboot oem device-info
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
marvi0 said:
hello buddy. Aaa you might be onto something. I am afraid I don't have my phone with me now. How do I check though if I have both parts of the bootloader unlocked?
Click to expand...
Click to collapse
But fyi, the razer phone has two parts to the bootloader. One is unlocked with
"Fastboot flashing unlock"
And the other is
"Fastboot flashing unlock_critical" i believe
iliais347 said:
Try fastboot oem device-info
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
But fyi, the razer phone has two parts to the bootloader. One is unlocked with
"Fastboot flashing unlock"
And the other is
"Fastboot flashing unlock_critical" i believe
Click to expand...
Click to collapse
Oh so I need to unlock both? Thanks will check this tonight
After install can't open music file on extened memory, usb otg
iliais347 said:
Try fastboot oem device-info
---------- Post added at 03:55 AM ---------- Previous post was at 03:29 AM ----------
But fyi, the razer phone has two parts to the bootloader. One is unlocked with
"Fastboot flashing unlock"
And the other is
"Fastboot flashing unlock_critical" i believe
Click to expand...
Click to collapse
Please can someone else confirm this please before I go ahead as I don't want to risk it?
marvi0 said:
Please can someone else confirm this please before I go ahead as I don't want to risk it?
Click to expand...
Click to collapse
Yes you need to unlock both and each command will also do a factory reset so backup anything you may need on the internal storage.
This is working great for me. Thanks
Sent from my Phone using Tapatalk

Categories

Resources