I root my coolpad 3320A and added a custom boot animation and now it won't load past the animation is just shuts off. I can access the System Recovery menu but I need the stock rom to get it working again. Can someone help me please?
I'm bricked.
Softbricked my Coolpad Rogue 3320a with SuperSU.
My only options to fix are:
1. Finding someone with a 3320a who is willing to dump their working system.img and upload it for me, so I can download it and fastboot flash the working system.img, to overwrite my corrupted system.
2. Waiting for stock rom to be released.
3. Smashing it with a Hammer.
Someone please be kind/Knowledgeable enough to help.
I'm also in need of a stock rom for this phone!
I ordered a new one from Amazon yesterday,will upload some dumps if someone can help me through the process. Still waiting on mail though.
Update: Phone arrived 5 minutes ago!!!.
Uploading System.img (easily relflashable with fastboot)
ZepyhrHD said:
I root my coolpad 3320A and added a custom boot animation and now it won't load past the animation is just shuts off. I can access the System Recovery menu but I need the stock rom to get it working again. Can someone help me please?
Click to expand...
Click to collapse
You MAY be able to fix this without the entire stock ROM,you should be able to connect it to a pc via fastboot cable,and reflash whatever IMG you corrupted via adb/fastboot in CMD... Once I get the new phone in the mail,I will post a download link here in this thread. (May also include some instructions on the process for future rogue users)
Here ya go XDA,maybe this will help some of you.
(Might upload other partitions later,but not today)
Download System.IMG here:
http://ow.ly/Gx8t3042SMg
Instructions Included (Requires a basic understanding of adb)
Hi everyone.
Stock +KingRoot'ed Partition Dump as well as the OTA UPDATE zip available here:
https://www.androidfilehost.com/?w=files&flid=126528
(this is rooted w/KingRoot, if you want to tinker you may need to grab the stock install-recovery.sh (as trying to install update fails for this file among other things, just a side-effect of using KingRoot to root.
Another thing to work out for that could brick you - Kingroot does a chattr +ia on install-recovery.sh - If you try to install the update and immutable attributes are present the update will fail and you may be left with a boot loop.
Since there's no custom recovery, and I couldn't get this thing to goto fastboot (didn't try very hard though), may be out of luck if you get bricked...
I strongly recommend NOT taking/using the OTA, but I have provided it here since I know some people may want to inspect/manually install it. If you do want updated apps I'd pull them from the update manually...
I returned this phone after I did the dump, so I'll be of no further use with it... but I hope this helps.
-tronik
Guide please
Can you please guide me how to reflash stock image? My coolpad rogue is stuck at ''Download package'' And whenever I press the c=volume down button to ''cancel'' it restarts phone and goes right back to it
I'm having toubles flashing the system.img. I tried doing this:
fastboot flash system system.img
I get this error: target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
and just hangs there and does nothing more
I had tried to redownload the file and re flashing but keep getting this error. If anyone is on please assist me on how to fix this if possible. I don't know if its the phone or fastboot that is having troubles.
*UPDATE* It sent its just takes a few minutes to send the system:cowboy
BIG BIG thanks to ApatheticEuphoria for the system.img i got my phone unbricked and working again
Phone
AustinGarrick1818 said:
I'm having toubles flashing the system.img. I tried doing this:
fastboot flash system system.img
I get this error: target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
and just hangs there and does nothing more
I had tried to redownload the file and re flashing but keep getting this error. If anyone is on please assist me on how to fix this if possible. I don't know if its the phone or fastboot that is having troubles.
*UPDATE* It sent its just takes a few minutes to send the system:cowboy
BIG BIG thanks to ApatheticEuphoria for the system.img i got my phone unbricked and working again
Click to expand...
Click to collapse
How did you get yours to work? -VON
coolpad road 3320A sistema arruinado
Alguien que me pueda ayudar ise root en mi telefono, y luego actualize el software y se me arruino solo enciende en modo recovery ayudemme a ver si ago algo mal al poner la imagen por medio de fastboot ya que solo me aparece asi
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
4348a67b fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
error: cannot load 'system.img'
C:\Program Files\Minimal ADB and Fastboot>fastboot update system.img
W/ ( 1276): Unable to open 'system.img': No such file or directory
error: failed to open zip file 'system.img': I/O Error
bigguccivon said:
How did you get yours to work? -VON
Click to expand...
Click to collapse
Just download the system.img file and reboot to fastboot mode (it will show on screen information mode or similar) and run:
fastboot erase system
fastboot flash system system.img
jose1914 said:
Alguien que me pueda ayudar ise root en mi telefono, y luego actualize el software y se me arruino solo enciende en modo recovery ayudemme a ver si ago algo mal al poner la imagen por medio de fastboot ya que solo me aparece asi
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
4348a67b fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
error: cannot load 'system.img'
C:\Program Files\Minimal ADB and Fastboot>fastboot update system.img
W/ ( 1276): Unable to open 'system.img': No such file or directory
error: failed to open zip file 'system.img': I/O Error
Click to expand...
Click to collapse
Or do you have the system.img avalable ??
Related
I see that the development right now is focused on D620, D618, etc.
Here in Uruguay we have the D625 version -I think in Brazil, Chile, Mexico and Russia too- , I want to know if anybodie is working on this device, porting the work of Zaaap or something like this
Thank you in advance
Post your boot.img at @Zaaap72 's thread and he should be able to port CWM, TWRP and PhilZ to your device.
Sent from my D620R [Stock 4.4.2]
Thank you for your answer. I don't know the procedure to obtain that file but i am reading and trying to learn
EDIT: should Iobtain the boot.img from the .kdz file or directly from the device? could you suggest any good tutorial?
Thank you very much.
Sent from my GT-P5100 using XDA Free mobile app
You will need:
1. Root
2. Working adb (if you want to do this from your PC)
3. LG United drivers installed (Windows only)
Run the following (# are notes):
Code:
adb devices
#Make sure your device is in the list
adb shell
su
#Accept the prompt [b]on your device[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
exit
exit
#Yes, twice
Now, your boot.img is at your device's internal sd.
Sent from my D620R [Stock 4.4.2]
Thank you very much, i'm going to try next weekend
Vagelis1608 said:
You will need:
1. Root
2. Working adb (if you want to do this from your PC)
3. LG United drivers installed (Windows only)
Run the following (# are notes):
Code:
adb devices
#Make sure your device is in the list
adb shell
su
#Accept the prompt [b]on your device[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
exit
exit
#Yes, twice
Now, your boot.img is at your device's internal sd.
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I'm having an error with this command:
Code:
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.
img
cc.1/by-name/boot of=/sdcard/boot.img <
/dev/block/platform/msm_sdcc.1/by-name/boot: cannot open for read: No such file
or directory
As I can see in root explorer, I don't have that directory. Instead I have "/dev/block/platform/sdhci-tegra.3/by-name/" and in this folder I have some archives: APP, CAC, CST, DRM, DTB, FOT, LAF, LNX, MDA, MDM, MOS, MPT, MSC, PST, RCT, SEP, SNS, SOS, UDA, USP (somehow, this files have somekind of second name, like mmcblk0p8 in stuffs like that).
As you can see, I'm not close to be a developer so I really need help with this lol
cripii5 said:
I'm having an error with this command:
Code:
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.
img
cc.1/by-name/boot of=/sdcard/boot.img <
/dev/block/platform/msm_sdcc.1/by-name/boot: cannot open for read: No such file
or directory
As I can see in root explorer, I don't have that directory. Instead I have "/dev/block/platform/sdhci-tegra.3/by-name/" and in this folder I have some archives: APP, CAC, CST, DRM, DTB, FOT, LAF, LNX, MDA, MDM, MOS, MPT, MSC, PST, RCT, SEP, SNS, SOS, UDA, USP (somehow, this files have somekind of second name, like mmcblk0p8 in stuffs like that).
As you can see, I'm not close to be a developer so I really need help with this lol
Click to expand...
Click to collapse
Sorry but I don't have your device so I don't know which one of these is the kernel. If there is a BOOT file, then thats it
The mmcblk0p* are the actual files, the files in /by-name/ are symlinks to those files
Well I found in another forum a way to obtain boot.img
Code:
dd if=dev/block/mmcblk0p5 of=/mnt/sdcard/boot.img
I did it and now I have a boot.img
https://www.dropbox.com/s/ws3rye41sierzq6/boot.img?dl=0
but I don't know if is the right one. I can't see a way to know how get it right for myself
Hi!
Did you have a unbanded firmware for our phone?
Mine is "VIVO" branded, i live in Brasil...
And the room is too laggy...
Thanks!
Sent from my LG-D625 using XDA Free mobile app
Its on lg's website, its posted around the forum also, i recommend you to root
it and take the crap apps out
Did you have the donwload link?
I've searched but dont found!
Thanks!
Sent from my LG-D625 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?p=55169575
vileladelima said:
Did you have the donwload link?
I've searched but dont found!
Thanks!
Sent from my LG-D625 using XDA Free mobile app
Click to expand...
Click to collapse
Take a look here http://forum.xda-developers.com/showpost.php?p=55804110&postcount=12
I'm using on my D625 VIvo.
joaolevysa said:
Take a look here http://forum.xda-developers.com/showpost.php?p=55804110&postcount=12
I'm using on my D625 VIvo.
Click to expand...
Click to collapse
What flsh totorial did you follow?
I tryed two, but none works!
Thanks
Que tutrial vc usou amigo?
Ja tentei dois, e outros não tive coragem de tentar (to meio azarado com celular esses dias e não quis arricar!).
Foi um q tem aqui no xda?
Flashear SAMSUNG é mais facil q LG viu! kkkkk
Valeu...
Obrigado!
joaolevysa said:
Take a look here http://forum.xda-developers.com/showpost.php?p=55804110&postcount=12
I'm using on my D625 VIvo.
Click to expand...
Click to collapse
Man, 4G working with this rom? I'm brazilian and i'm using vivo rom too. There are many unnecessary apps. which tutorial you followed for flashing? Thank you!
Cara, a conexão 4g está funcionando com essa rom? Eu uso a rom da VIVO também. São muitos apps desnecessários. Qual tutorial você seguiu para flashear? Aliás, depois que fazer root o aparelho não atualiza mais né? Basta flashear essa rom novamente caso saia alguma atualização importante? Obrigado!
anyone knows about the lollipop update for the d625?? I'm getting hopeless :crying::crying::crying:
I'm trying to flash stock and official firmware for my phone (axon7). I boot into the stock recovery where I select the option "ADB sideload".
My phone then says on the screen: "Usage: adb sideload <filename>".
When I run 'adb devices' the phone is recognized. There is only one phone connected to the computer so it's that one. However, when I try to sideload the update.zip file I get the really annoying message: Cannot read zip file.
ADB simply won't load the zip file and send it to the phone.
I run Windows 10 and use the minimalistic ADB tools. I've been trying for a few days now to get adb to work. Because my bootloader is locked and my phone is in bootloop. This means I can only sideload official zips that have the ZTE keys, or are signed by ZTE.
What I've tried:
- different adb drivers. (naked/google/universal etc...)
- different pc (also win10).
- renaming the file, putting file in same folder as adb.exe, trying 'update.zip.zip'.
- 'unblock' zip file in Richt-click -> properties of the file.
- drag and dropping the file into the command prompt.
- Elevated command prompt.
I really have no clue why this will not load the zip file. I must've done it a 100 times on my Oppo Find 7a, same way: right-clock to open CMD. 'adb devices', 'adb sideload update.zip'.
Online there are numerous topics about this dating from 2013 to about yesterday. No one seems to know the solution (for me). I'm hoping anyone here does.
Thanks in advance.
Eu tentei muitas coisa quebrei muito a cabeça tentando de tudo então renomeei o arquivo para rom.zip e depois iniciei o adb então digitei "adb devices " depois "adb sideload rom.zip.zip e deu certo :laugh:
Hello people. After a long time searching and trying, I finally get this model rooted. The problem was, basicly, the bootloader. After unlock it, I was able to root the device. I'll tell you the steps, but be warned:
UNLOCK BOOT LOADER IS RICKY, AND YOU MAY KILL THIS DEVICE. FOR NOW WE DON'T HAVE ANY ROM FOR DOWNLOAD, SO WE CAN'T UNBRICK IT WITH SP FLASH TOOLS.
YOU MAY LOOSE ALL YOUR DATA AFTER BOOTLOADER UNLOCKED!! TAKE A BACKUP!!
ME AND/OR XDA CANNOT BE RESPONSABLE FOR ANY BRICK TO YOUR DEVICE.
YOUR ARRANTY WILL BE VOID.
THIS METHOD IS SOMEHOW FAIL. MAYBE YOU MAY HAVE TO DO IT AFTER A RESTART.
YOU WAS WARNED!!
This sayed, you will need the USB drivers, adb, fastboot. I made the hardwork for you, and the files I used are attached bellow. Unpack it to a folder, let's use C:\C6 to be easyer. You need also Kingo Root For PC (not King Root), you can download from https://www.kingoapp.com/. Install it, but don't run. Make sure you have enought battery, as the process can take a long time (for me, all procedures taked 30 eternal and nervous minutes). The process I made was on Windows 10 64bits, so, some steps maybe differ if you use a different system.
Once prepared, let's go again.
Phase 1: Preparing the field:
Set screen timeout to 30min, and remove any PIN, password or secure lock screen settings.
If USB Debug is disable, you must go to Settings > About Phone > Tap Build Number until "You are a developer" appears.
Now, go Settings > Developer Options > Check USB Debugging. Accept the warning.
Now, go Settings > Security > Check OEM Unlocking. Accept the warning.
Now, connect the phone with PC
It will install the drivers. If it don't install, go to Device Manager, look for "Android MT65XX" or something similar, and update the drivers with the ones I give to you. FOR NOW ON, DON'T REMOVE THE CABLE FROM PHONE OR PC.
If all are correct, the phone will ask for a confirmation after installing the drivers. Check "Always allow", and tap OK. To re-confirm everything is ok, open a command prompt as administrator, and type the following commands (remember to hit ENTER on PC keyboard for each command for now on):
Code:
cd\c6
cd "adb fastboot"
adb devices
You MUST see something like:
Code:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
XXXXXXXXXXXXXXXXXXXX device
Where 'X' is the device serial number. If you don't see this, the drivers don't work for your device. You must search and find another somewhere. If everything is correct, keep fingers of one hand crossed and let's continue.
Phase 2: Unlock the bootloader:
In the same command prompt, type the following:
Code:
adb reboot bootloader
The phone will reboot, more drivers are installed, and you are presented with a black screen with "FASTBOOT mode" at bottom. To test if the drivers are ok, type:
Code:
fastboot devices
You MUST see something like this:
Code:
XXXXXXXXXXXXXXXX fastboot
Again, if you don't see, you must browse internet and find the drivers. If everithing is OK, type:
Code:
fastboot oem unlock
Go to the phone, you will see a warning. Accept it by hiting VOL+ key. The phone will change the screen, and your command prompt will confirm the unlock. CHECK TO SEE THE CONFIRMATION. Now, type:
Code:
fastboot reboot
The phone will reboot again, will appear "Erase data" (you lost your data here), and reboot again, new as hard reset. Let's confirm it is unlocked. Repeat the steps 1 to 3 from phase 1, and type:
Code:
adb reboot bootloader
Wait for the phone's black screen and type:
Code:
fastboot getvar all
In the results, search for "(bootloader) unlocked: yes". If you not find, or appears "no", stop reading now, and don't try anything else: this tutorial will not help you.
If you find, congratulations! You can now uncross your fingers and go to final phase! First, we need to reboot again. Type:
Code:
fastboot reboot
And wait the phone bootup.
Phase 3: Root!
Open Kingo Root as administrator
UNCKED install suggested apps
Click "ROOT"
Some seconds after, the phone will present a "Kingo Link" error. Just tap ok, and you can now go drink coffee or watter if your prefer. It will take a time, don't touch the phone.
If everything was OK, Kingo Root will present "Root Success" both on phone and PC. On the PC, you have a donate button. Why not?
Well, thats it. You can now disconnect your phone, close command prompt and use your root powers, but be warned: DON'T MESS WITH SYSTEM TOO MUCH, AS WE DON'T HAVE A ROM DOWNLOAD FOR NOW. UNINSTALL OR INTEGRATE MAY BE RISCKY, AS WELL DELETING FILES.
OBS.: Don't get fired, configure on the alarm NOW!
Don't forget to hit thanks if I help you.
MODS: Move this topic to the right section, please!
After root, I freezed the following, without any issues until now:
Android Live Wallpapers (I don't use)
arProcess (The annoyng move to page in settings. Disable it before freeze, as it comes with error after freeze)
Backup and Restore (I have my own backup)
Bagan keyboard (????)
Black Hole
Bubbles
Calculator (I have my own app)
Calendar (I have my own app)
cam.android.wallpaper.holospiral (I don't use)
DeskClock (I don't use)
Email (I don't use)
Exchange Services (I don't use)
Facebook (Know as memory drainer)
FWUpgrade (As this model hardly will have updates, I freeze it)
Google App (Know as memory drainer)
Internet (I prefer Chrome)
Maps (I don't use)
Music (I don't use)
MusicFX (I made some tests, and it is buggy or don't work. Disable audio enhancements in settings before freeze)
Phase Beam
Photo Screensavers
PicoTTS
Search (You may have to unfreeze, restart, and freeze again if your Google account desappears)
System Software Updates (Same as FWUpgrade above)
Todo (I don't use)
Updater (Same as FWUpgrade above)
Videos (I don't use)
Voice Recorder (I don't use)
Me dê uma ajuda por favor
Oi, sou brasileira e acredito que você também, então vou mandar essa mensagem em português.
Eu tenho um aparelho
Modelo: C6 Ultra
Fabricante: Sony
Dispositivo: gxq6580_weg_l
Hardware: mt6580
Quero muito instalar uma ROM pra ver se corrijo um erro que eu acabei cometendo, ele está funcionando normalmente, exceto o meu acesso ao Google Play e ao Google Play Service que acabei excluindo sem querer, tentei baixar os dois normalmente por arquivos apk jogados no celular e de nada adiantou.
Queria saber se tem e se é possível instalar uma ROM nova e se você poderia explicar o procedimento, se não, se tem algum jeito de baixar os gapps pro meu aparelho. Obrigada.
Project abandoned. Full development ongoing for Orangefox where I have obtained full userdata decryption
installing this will wipe my device, right?
i'm currently using the stock a11 rom rooted with magisk and it's going great, but - if in the future my phone can't boot for whatever reason, can PBRP then be installed to restore?
or is it too late then, does it need to be installed before a major problem like that happens?
Once I have decryption working, it will become alot more beneficial.
Those benefits are only available without encrypted userdata currently.
(this would indeed involve formatting data and flashing no verity zip to prevent encryption)
The recovery is simply the ramdisk of the boot.img so can still be installed without causing any issue with your current setup, at present its good for getting a backup of your device
However I'd suggest holding out for decryption
and installing Magisk Bootloop Protector module from Fox's Magisk Module Manager
CFKod said:
installing Magisk Bootloop Protector module from Fox's Magisk Module Manager
Click to expand...
Click to collapse
thanks! just installed it. it looked like the same version was listed twice from two different repos, so i went with the one with the higher download count. do i need to adjust any settings, or is it just install and that's it?
trevtdogg said:
thanks! just installed it. it looked like the same version was listed twice from two different repos, so i went with the one with the higher download count. do i need to adjust any settings, or is it just install and that's it?
Click to expand...
Click to collapse
Yea that's the one. No settings.. It cleverly detects when you have problems booting and disables all modules.
It has saved me a few times..
updated links to pbrp specific repo
V1.0.3 released - removed binary and lib files that are called after mounting of vendor/system - taking up space in ramdisk un-necessarily - decryption of userdata still not working.
I think I may have bricked my phone.
I flashed boot.img to slot b
I set slot b as active
I went into recovery mode and loaded PitchBlack
I couldn't find how to copy the zip to internal storage within the PitchBlack environment and I pressed reboot.
Now device seems dead. Only the led lights up when I connect it to the pc.
Anything to do?
xvivo said:
I think I may have bricked my phone.
I flashed boot.img to slot b
I set slot b as active
I went into recovery mode and loaded PitchBlack
I couldn't find how to copy the zip to internal storage within the PitchBlack environment and I pressed reboot.
Now device seems dead. Only the led lights up when I connect it to the pc.
Anything to do?
Click to expand...
Click to collapse
Manually load bootloader
I've updated the procedure ... Switching slots is not required anymore as PBRP sits nicely within the boot partition.
I was actually a hard brick. Motorola service came through.
xvivo said:
I was actually a had brick. Motorola service came through.
Click to expand...
Click to collapse
Wow... Strange one that ... Not sure why that would even happen?
Thankfully , scrapping all the of the inactive slot advice
Glad Moto came the rescue for you - however you probably could have rescued using blankflash
CFKod said:
Wow... Strange one that ... Not sure why that would even happen?
Thankfully , scrapping all the of the inactive slot advice
Glad Moto came the rescue for you - however you probably could have rescued using blankflash
Click to expand...
Click to collapse
Screen did not turn on at any key combination, only power led flashed instantly. It was not showing as a device in windows or in fastboot.
An explanation I found possible is that slot b was completely empty when I tried. Most will not reproduce same fault as system updates will fill the slot.
good news Decryption of Userdata now works (without a passcode)
It may work with a passcode - but my initial tests I had to remove passcode and then reboot back to bootloader > recovery
Releases · forforksake/android_device_motorola_kyoto-pbrp
recovery tree for Motorola Edge 20 Lite 5G - mt6853 - kyoto - forforksake/android_device_motorola_kyoto-pbrp
github.com
warning: remember to patch your vbmeta (obtained from your firmware zip)
Code:
fastboot flash vbmeta --disable-verification --disable-verity vbmeta.img
CFKod said:
warning: remember to patch your vbmeta (obtained from your firmware zip)
Code:
fastboot flash vbmeta_a --disable-verification --disable-verity vbmeta.img
Click to expand...
Click to collapse
hola amigo, tengo una duda, tengo un moto edge 20 lite y quiero instalar PBRP pero no puedo hacerlo, cuando pongo el codigo que compartes para parchear vbmeta me sale el siguiente error:
C:\adb>fastboot flash vbmeta_a --disable-verification --disable-verity vbmeta.img
fastboot: unknown option -- disable-verification
Isn't that the command or why does this problem happen to me?
Ahh are you booted
paz16kevin said:
hola amigo, tengo una duda, tengo un moto edge 20 lite y quiero instalar PBRP pero no puedo hacerlo, cuando pongo el codigo que compartes para parchear vbmeta me sale el siguiente error:
C:\adb>fastboot flash vbmeta_a --disable-verification --disable-verity vbmeta.img
fastboot: unknown option -- disable-verification
Isn't that the command or why does this problem happen to me?
Click to expand...
Click to collapse
Perhaps you have booted into fastbootd
No need to enter fastbootd, the flashing of vbmeta and boot work from the bootloader screen (the page on the pic in OP)
Vbmeta args don't work from fastbootd.
The annoying thing about this device, is we can't fastboot boot boot.img
Only allows fastboot flash boot.img
Ignore
I patched the boot.img - I patched it.
I flashed TWRP.img and installed TWRP from a zip file.
Rebooted from recovery to fastboot.
Command C:\adb>fastboot flash vbmeta_a --disable-verification --disable-verity vbmeta.img
fastboot: unknown option -- disable-verification.
astboot flash vbmeta_a ----do you need an A?
vbmeta stock, from the stock firmware.
Maybe you need a patched vbmeta?????
Where to get or how to patch yourself?
CFKod said:
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3 6.2x
PitchBlack version: 3.2.0
For device: Motorola Edge 20 Lite 5G
Maintainer/Authors build: CFKod / ForForkSake
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/forforksake/android_device_motorola_kyoto-pbrp
Kernel: stock KYOTO_RETAIL_RRKS31.Q3-19-97-12
unlocked bootloader and patched vbmeta required
use the vbmeta from your firmware.zip - reboot to bootloader
Code:
fastboot flash vbmeta --disable-verification --disable-verity vbmeta.img
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
Flash magisk (if required)
Enjoy
From PC
Download Boot.img & PitchBlack Recovery flashable zip from my GitHub
Save them to PC and to external SD
Download magisk APK and remame to magisk.zip, copy this to external SD too.
reboot to bootloader
Flash the pbrp boot.img - fastboot flash boot boot.img
use vol up / vol down to select recovery mode
TAKE A FULL BACKUP OF YOUR DEVICE - NOW
If you aren't on the same version ( KYOTO_RETAIL_RRKS31.Q3-19-97-15 ) follow next step, else move on to flashing the PBRP zip
Install your stock boot.img , do not reboot
Flash the PBRP.zip
Flash Magisk.zip (if required)
Enjoy
PBRP sits nicely wiithin your boot image, so no longer need to switch slots
View attachment 5635431
Changelog
PBRP Side Changelog
v3.2.0
- Bump to 3.2.0
- Based on TWRP 3.6.2-x
Device Side Changelog
Android 11
Bugs
Decryption now works (with passcode removed)
Flashlight / Torch not yet working
Downloads
Releases · forforksake/android_device_motorola_kyoto-pbrp
recovery tree for Motorola Edge 20 Lite 5G - mt6853 - kyoto - forforksake/android_device_motorola_kyoto-pbrp
github.com
Click to expand...
Click to collapse
Any plans to add support to Motorola Edge 20 Fusion (XT2139-2) ?
puh63 said:
Rebooted from recovery to fastboot.
Click to expand...
Click to collapse
This is where you are going wrong.
To flash vbmeta you have to be at the bootloader
Reboot to bootloader
Does anyone know if the Motorola edge 2022 can be rooted?
Can edge plus 2020 can be root on Android 12???
1. Unlock bootloader
Sign in to Motorola - Motorola Mobility LLC
Sign in to Motorola
accounts.motorola.com
2 Drivers
Where can I download the USB drivers for my device?| Motorola Support IT
Visita la pagina di supporto clienti di motorola edge+ per visualizzare le guide utente, le FAQ, l'abbinamento Bluetooth, i download di software, i driver, i tutorial e per ottenere informazioni sulle riparazioni e sui contatti. Where can I download the USB drivers for my device?
it-it.support.motorola.com
3. Install latest ADB PlatformTools Install
4. Install latest Magisk on Moto
5. Extract boot.img from the latest rom that is mounted, move to the phone, start Magisk and patch boot.img. Patched file is located in the download folder. Now let's move the patched file to the PC in the Platform tools folder.
6. Start the phone in fastboot and connect it to the computer. Open the platform tools folder and in the folder address type cmd now in adb comando
fastboot flash boot magisk_patched ........img
7. Start system
fastboot reboot