Hello, i wanted to flash my phone(Motorola One Macro) to LineageOS 17.1, but it get error at flashing and now is phone permanently restarting.... i dont know how to flash new stock firmware, or any new android.
i know i can use adb, but it doesnt work or i do it bad. :angel:
pls help, thanks.
@drobec255
You by means of ADB always can re-flash phone's Stock ROM ( it's not necessary phone's boot-loader is unlocked )
Code:
adb devices
adb reboot recovery
[i][color=red]Note: In recovery menu presented select option Apply Update From ADB and confirm it, then proceed with[/color][/i]
adb sideload <PATH_TO_STOCK_ROM_IMAGE_FILE_ZIP>
adb reboot
jwoegerbauer said:
@drobec255
You by means of ADB always can re-flash phone's Stock ROM ( it's not necessary phone's boot-loader is unlocked )
Code:
adb devices
adb reboot recovery
[i][color=red]Note: In recovery menu presented select option Apply Update From ADB and confirm it, then proceed with[/color][/i]
adb sideload <PATH_TO_STOCK_ROM_IMAGE_FILE_ZIP>
adb reboot
Click to expand...
Click to collapse
ok, i flashed it to stock ROM, phone works.
I wanna flash it to LineageOS 17.1 but file is ".img.xz" ??? how to? bootloader is unlocked
@drobec255
1st of all things is you must have a TWRP matching your phone at your fingertips.
Next thing is that you must have a Lineage OS 17.1 version that's at 100% compatible with your phone - don't think this exists. BTW: Lineage OS always is offered as a signed ZIP-file.
If these requirements are met, then to replace phone's Android 9 by Lineage OS 17.1 you run this command sequence:
Code:
adb devices
[i][color=red]next 6 cmds backup /efs & /vendor partitions[/color][/i]
adb shell "cat /efs > /data/local/temp/efs_bkup"
adb pull /data/local/temp/efs_bkup %TEMP%\EFS_BKUP
adb shell "rm /data/local/temp/efs_bkup"
adb shell "cat /vendor > /data/local/temp/vendor_bkup"
adb pull /data/local/temp/vendor_bkup %TEMP%\VENDOR_BKUP
adb shell "rm /data/local/temp/vendor_bkup"
adb reboot bootloader
fastboot devices
fastboot erase system
fastboot erase cache
fastboot erase userdata
[i][color=red]temporarily boot into TWRP[/color][/i]
fastboot boot <PATH_TO_TWRP_IMG>
[i][color=red]In TWRP's menu select option Apply update from ADB and confirm[/color][/i]
adb sideload <PATH_TO_LINEAGE_OS_ZIP>
[i][color=red]next 2 cmds restore /efs & /vendor partitions[/color][/i]
adb push %TEMP%\EFS_BKUP /efs
adb push %TEMP%\VENDOR_BKUP /vendor
adb reboot
For anyone that this may still happen too....
Use RSA to put your phone back to it's stock rom. Even if it's bricked. it'll recovery it.
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Related
Been working on a phone with the build number
2.19.605.1
CL123435 test-keys
Cannot get this to take a custom recovery, It seems to have root in ADB but when I try to flash a recovery it fails.
Any advice?
which method are you using?
I would suggest the fastboot method its a lot easier to do.
Just make sure recovery.img is in the tools directory. Then just follow these directions if you don't have windows just look for fastboot.bin and compile it in linux and it should work.
Code:
WINDOWS USERS
From your tools directory in the sdk do the following command
adb reboot bootloader
You will have FASTBOOT highlighted in red like it is here
Now on your computer do the following
Fastboot flash recovery recovery.img
you should see "sending....ok" then "writing.....ok"
on your command prompt when its done just do
fastboot reboot
that will reboot your phone and then you can either turn it off and reboot
into recovery or run
adb reboot recovery
from the command prompt.
BTW: all commands are run from command prompt.
Hope this helps.
So I'm trying to create a batch file for an automated process to install a zip, without any physical user interaction.
1.) Is it possible to reboot a phone into ClockworkMod Recovery and go straight to sideload mode using adb/fastboot?
...if that's not possible:
2.) Is it possible to to start sideload mode when in ClockworkMod Recovery, using only the command prompt and adb?
I've tried adb reboot sideload, adb reboot recovery sideload, adb reboot recovery-sideload, etc. Perhaps there's an adb shell command that can start sideload mode when in ClockworkMod Recovery?
Thanks.
beggin said:
So I'm trying to create a batch file for an automated process to install a zip, without any physical user interaction.
1.) Is it possible to reboot a phone into ClockworkMod Recovery and go straight to sideload mode using adb/fastboot?
...if that's not possible:
2.) Is it possible to to start sideload mode when in ClockworkMod Recovery, using only the command prompt and adb?
I've tried adb reboot sideload, adb reboot recovery sideload, adb reboot recovery-sideload, etc. Perhaps there's an adb shell command that can start sideload mode when in ClockworkMod Recovery?
Thanks.
Click to expand...
Click to collapse
Any ideas?
beggin said:
Any ideas?
Click to expand...
Click to collapse
Well, I have an idea!
The key you search is named OpenRecoveryScript.
Maybe its not the thing you search, but an alternative way.
Try this:
Code:
REM Reboot into Recovery
adb reboot recovery
REM Create OpenRecoveryScript
echo install /sdcard/*yourromnamehere*.zip > openrecoveryscript
REM Push Rom to /sdcard
adb push *yourromnamehere*.zip
REM Push both files to their correct Paths
adb push *yourromnamehere*.zip /sdcard/*yourromnamehere*.zip
adb push openrecoveryscript /cache/recovery
REM Reboot Recovery
adb reboot recovery
echo Done
pause
Try this Code and give feedback. I haven't included some wipe-commands!
My android (jellybean) tablet was turned off in middle of update and now is in boot loop. It was rooted with USB debugging on.
I MUST recover files (PDFs, .doc, .wav .JPEG, etc ) without erasing them.
Questions:
1 Do I use Odin and TWRP together?
2 Will Odin flash Samsung stock firmware erase files on device?
3. Will TWRP .img file erase everything?
4. Are these instructions correct?
I recommend you install TWRP recovery. It's the most feature-rich of all the recoveries I have used, and I will be assuming that is the recovery you use for the rest of this.
1. Boot into TWRP. (how? TWRP is an .img file )
2. Push your ADB public key to your device to force authentication.
____On Windows, do: adb push %UserProfile%\.android\ad
bkey.pub /data/misc/adb/adb_keys
3. Reboot into Android. Try adb shell and see if you get a shell prompt. If so, great! Exit it and run adb logcat, and read the huge error log for problems. If you didn't get the shell, well, then I think you're screwed, unless someone has cooked up a recovery zip for enabling adb.
What happens after ADB logcat?
Thank you..
Hi There
So, I normally obtain adb root by the following process:
1. Unlock the Bootloader (if required)
2. Use fastboot to OEM unlock the boot loader
3. Get the boot.img and upack it
4. Change ro.secure=0 and ro.debbugable=1 in default.prop
5. repack boot.img
6. flash boot.img to device
7. Boot up device, ensure USB debugging is enable.
8. Then use adb root, adb remount rw and I usually always get adb root this way. So I can "adb shell" and I have a # root prompt.
However I think I have always had the ENG or DEBUG builds of the OS when I did this.
So I now only have a USER build of the OS.
I follow the above procedure but it doesn't matter how many times I change the ro.secure and ro.debggable settings , they are always locked. They must be being set somewhere else?
So I heard that this is normal for USER builds, the build simply does not allow access to ro.secure=0.
My questions are:
1. Is what do I need to change in the USER build of my OS or boot.img to get ro.secure=0 working?
2. Is it even possible?
3. Failing this, can you get generic DEBUG/ENG boot.img's for MTK 6755 devices?
Hello comrades.
After 5 years, I finally got tired of being on Android 4.2.2. I thus started to look for a custom rom to maybe upgrade it to 5.1? I found nothing obviously. Except a whole bunch of problems including: my phone can't even go into recovery mode. (And Twrp and Cwm just stop working when they have to look for my phone model.)
My idea is this one: I'll dl Android Kitkat, lollipop and nougat and starting from nougat, I'll see what my phone can and can't support so at least I'll upgrade some part of my phone. I also know I'll have to bear in mind the Linux kernel and try having the best one considerning my ol' Archos. Question: do you think it's doable? That I can make it? P.S: my computer is on Windows 10.
Of course, if you happen to know a lollipop version for an archos 40ti I'll be glad to take it!
@ely_Pine
Each phone by default comes with a Recovery partition, unless it got removed by whomsoever.
Anyway, if ADB and Fastboot fully are working, you can boot phone into a Custom Recovery ( TWRP and/or CWM ) and from there flash a Custom ROM.
Of course phone's bootloader must got unlocked before - what causes a complete data loss:
Code:
adb devices
adb reboot bootloader
fastboot OEM-unlock
fastboot reboot
If the above step was successful then you can proceed booting phone into CWM recovery ( DL here )
Code:
adb devices
adb reboot bootloader
fastboot boot <FULL_PATH_TO_RECOVERY_IMAGE_ON_PC>
Again: The above Fastboot command will just boot your phone CWM. To permanently install CWM recovery, you have to run
Code:
adb devices
adb reboot bootloader
fastboot flash recovery <FULL_PATH_TO_RECOVERY_IMAGE_ON_PC>
If also this step was successful you can install any Custom ROM of your choice via CWM recovery.
Thanks for the reply!
Anyway, if ADB and Fastboot fully are working
Click to expand...
Click to collapse
They are not (which is a problem I consider for another day when my custom ROM will be done haha)
Here's the commands I tried the other day: (spent one whole day trying to install CWM/TWRP)
adb devices > worked
adb reboot bootloader > worked
fastboot OEM-unlock > nothing happened
fastboot reboot > worked
Click to expand...
Click to collapse
Nonetheless I try flashing the CMW recovery img
adb devices > worked
adb reboot bootloader > worked
fastboot flash recovery <FULL_PATH_TO_RECOVERY_IMAGE_ON_PC> > sent back an error message : "partition "recovery" not support flash"
Click to expand...
Click to collapse
Since holding volume down+button on/off could not send my phone into recovery mode (it just turned on), I used:
adb shell > worked
reboot recovery > sent back message : "reboot : Operation not permitted"
Click to expand...
Click to collapse
Anyway, there is no custom ROM for my device so I don't have any choice but to do it myself - and first, I need to find out how to get the source code of my current kernel.