Database Info

Bricked XT1032

So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.

Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!

No one? :/

Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.

NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one

Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img

NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery

Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?

NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect

Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.

NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang

Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.

NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that

You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​

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

My OnePlus 7 Pro is bricked.

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.

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

One plus 7 pro (Gm1910) stuck in Qualcomm crashdump mode.

So my problem began after updating my phone, I was using the official build. Not the beta. 2 days later my phone crashed while using reddit. I forced it to reboot, it didn't boot back up, it was getting stuck after the one plus logo screen, I took it to a repair shop and they tried to flash it but screwed it up, they gave me back my phone with a new error message-
QUALCOMM crashdump mode
Attempted to kill iniT
Exit code -0x000000b.
I didn't root or had the bootloader unlocked, My phone does boot into fastboot mode but I don't know what to do.
Is my phone past the point of no return?

Have you tried the msm tool?

Yes I tried msm it did not work

Shomoyy said:
Yes I tried msm it did not work
Click to expand...
Click to collapse
When in fastboot mode have you tried adb commands? First I would try fastboot devices and see if your device is listed. Then oem unlock. If that is successful try fastboot boot recover.img with the recovery of your choice. I suggest pitch black recovery.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also what happens you you tried to use msm tool.

Bastafari said:
When in fastboot mode have you tried adb commands? First I would try fastboot devices and see if your device is listed. Then oem unlock. If that is successful try fastboot boot recover.img with the recovery of your choice. I suggest pitch black recovery.
Yes I have but when i type adb devices my phone is not showing up. heres the message in cmd-
C:\>adb reboot bootloader
error: device '(null)' not found
C:\>fastboot oem unlock-go
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.010s
Also what happens you you tried to use msm tool.
Click to expand...
Click to collapse
It flashes successfully but still gets stuck on Crashdump mode.
also apologies for late replay.

Ok so when youre, in recovery, try erasing data (type yes). Then reboot to fastboot and fastboot recovery again. Fish a rom and recovery again then reboot to system. But tell me what happens with msm tool. I've used it once or twice and if you don't do something correctly it doesn't work.