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..
Related
Here is a batch file I have made to do a couple things for an HTC EVO 3D through adb. NO NEED TO INSTALL ADB!!!
It gives you three choices, either reboot to fastboot, which can supply you with a command prompt, reboot to recovery through fastboot, (YES, HBOOT 1.5 USERS CAN USE THIS TO FLASH TO THE BOOT PARTITION, THIS INCLUDES KERNELS, AND RECOVERIES). Or to just ADB reboot (comes in handy for Freezes or Lockups).
To avoid any frustration, I have included adb and fastboot in the folder (NO ADB INSTALL).
I have not included a recovery image, so you will have to download one of your choice, place it in the folder, and rename it to "Recovery.img" (NO Quotation Marks). If a recovery doesn't boot, no worries, this doesn't flash it, just places the recovery in a temporary partition to boot, your current recovery will stay intact
DON'T WORRY, IT SOUNDS MORE DIFFICULT THAN IT IS, YOU GET USED TO IT.
1. Unzip to any folder on your computer
2. Copy your choice of recovery (Recovery.img) to folder
3. Run "Reboot.bat"
4. Make your choice of Fastboot, Recovery, or Reboot
a) If you choose Fastboot, you have the choice of opening a prompt for manual fastboot commands. Choose yes (Y) or no (N).
b1) If you choose Recovery, your phone will reboot into Fastboot
I CAN NOT STRESS ENOUGH, TO WAIT UNTIL THE PHONE HAS ENTERED FASTBOOT, BEFORE CONTINUING TO RECOVERY. No harm will be done to your phone, but it wont boot recovery unless "fastboot" gets the dang command...
b2) Press any button, AFTER your phone has entered fastboot. This will send the command to your phone to boot the recovery you placed in the folder, not the one flashed on your phone. (Good Way To Test Recoveries Before Flashing).
c) If you choose Reboot... UM??? Your phone will reboot...
5. YOU ARE DONE!!!
IF ANYONE WOULD LIKE TO OPEN THE BATCH TO EXAMINE IT, YOU ARE MORE THAN WELCOME. I JUST ASK THAT YOU DO NOT MODIFY OR COPY IT WITHOUT MY PERMISSION.
I am currently in the process of making a batch that will flash the recovery as well.
MD5:603E2B5009E97350E922A49AFCBAAA78
New recovery flashing capabilities
I have added a recovery flashing capability to the batch, it has a lot of warnings, but it needs them... It just flashes the previously stated recovery.img, instead of booting a temporary recovery through fastboot...
MD5:5494B0BD03179332F9EBCA28D389A8A7
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 device is stuck in bootloop with no backup and is not showing up in adb for me to push rom to phone? suggestions????
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
NasaGeek said:
Reboot into recovery, find the adb sideload option, activate it. Run adb sideload romname.zip on your computer where romname.zip is the ROM you want to flash. Sometimes it will take a number of minutes for your computer to recognize your device once it is in sideload mode. Just keep trying. I've had more luck doing this with TWRP than with CWM. We really should sticky some sort of sideload instructions...
Click to expand...
Click to collapse
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
jizang said:
What Version of adb do you have and which recovery are you using
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
1.0.31 and tried both twrp and cwm
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
NasaGeek said:
have you waited a few minutes and tried executing the adb sideload command on your computer multiple times when trying to sideload with TWRP?
Click to expand...
Click to collapse
yea ridiculous amount times
I had the same problem i could not adb sideload a Rom,in the end i had to flash stock ruu to save my phone
Sent from my HTC One X+ using xda premium
indie12 said:
got error device not found using twrp recovery and * failed to write data 'protocol fault (no status)' * with cwm don't know what's wrong, Not rooted phone since my nexus one when i used to always root but with that could just whip the sd card out...
Click to expand...
Click to collapse
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
reaper90 said:
Install TWRP instead of CWM! AFAIK adb sideload does not work on CWM recovery, had the same problem when i needed to use this command for the first time.
Click to expand...
Click to collapse
doesn't work with twrp either,
also forgot to mention is odd that adb doesn't find device since i can flash new recovery / kernal via fastboot?
adb discovering my device in sideload now but not allowing the sideload? how can i push the rom to sdcard via adb?
indie12 said:
doesn't work with twrp either
Click to expand...
Click to collapse
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
reaper90 said:
It has to work, believe me. Are you on latest TWRP 2.5.0.0? If not, you should probably update. Erasing cache in fastboot ("fastboot erase cache") may help sometimes. Did you wait long enough for adb to recognize your phone in sideload mode (may take some minutes)?
If not:
1. Boot your phone in recovery, connect it to your computer and start sideload mode in recovery.
2. Open command line, navigate to the folder where your adb/fastboot files are (you must also copy the desired rom.zip file into this folder)
3. Type "adb start-server" and now wait some minutes.
4. Type "adb devices", your device should now be listed there in sideload mode. If not, wait some more time and try again
(10 min should be enough, if not, there's probably something wrong with the driver or adb files on your computer)
5. Now you can type "adb sideload name_of_your_rom.zip"
It should work now. when it's finished, the rom.zip file is saved on your phones internal memory as "sideload.zip"
If not, there must be something wrong with your driver and/or adb/fastboot files. Try reinstalling them then.
Click to expand...
Click to collapse
its just worked, transfering the rom now, no idea what caused it to work this time but it is so thanks
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img
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