Related
Hi guys
Please tell me
Which version of CWM recovery is more stable than another one?
Thank you
3.1.0.1
10char
posei-don said:
Hi guys
Please tell me
Which version of CWM recovery is more stable than another one?
Thank you
Click to expand...
Click to collapse
Search clockworkmod thread.
MatDrOiD said:
Search clockworkmod thread.
Click to expand...
Click to collapse
i Search clockworkmod thread but there is a lot of version
and i dont know which one is good for use in a long time
4rm45 said:
3.1.0.1
10char
Click to expand...
Click to collapse
thank you
are u sure?
This recovery does not have a problem?
Just use latest one.
Swyped from my HTC Desire using XDA App
posei-don said:
are u sure?
This recovery does not have a problem?
Click to expand...
Click to collapse
Yep, I'm sure
Try 4.0.0.5 im using it since today and its very good, looks like all bug fixes fixed eg. mounting problem/ext wipe - it works great for me.
2.5.0.7 never had problems with this version so never seen a need to upgrade!
MatDrOiD said:
Just use latest one.
Click to expand...
Click to collapse
4rm45 said:
Yep, I'm sure
Click to expand...
Click to collapse
Thanks a lot
stringer7 said:
2.5.0.7 never had problems with this version so never seen a need to upgrade!
Click to expand...
Click to collapse
No i need another version
I have a problem with this version of CWM recovery
k3lcior said:
Try 4.0.0.5 im using it since today and its very good, looks like all bug fixes fixed eg. mounting problem/ext wipe - it works great for me.
Click to expand...
Click to collapse
Thank you
I will try this
Can i downgrade if this version have problem?
If you have s-off you can use fastboot to flash any recovery of any version, as long as you can find the img file for the particular version you want.
Hi
Please help me
I cant install recovery with android flasher ((((
PHP:
C:\androidflasher>@echo off
cd data\
taskkill /F /IM adb.exe
SUCCESS: The process "adb.exe" with PID 5636 has been terminated.
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash recovery recovery.img
What should i do???
posei-don said:
Hi
Please help me
I cant install recovery with android flasher ((((
PHP:
C:\androidflasher>@echo off
cd data\
taskkill /F /IM adb.exe
SUCCESS: The process "adb.exe" with PID 5636 has been terminated.
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash recovery recovery.img
What should i do???
Click to expand...
Click to collapse
where are you running androidflasher from cmd or exe??
is your recovery img ok..try to re-download and reflash,should work.
Exiled_SouL said:
where are you running androidflasher from cmd or exe??
is your recovery img ok..try to re-download and reflash,should work.
Click to expand...
Click to collapse
exe!
yes its ok
i redownload it but its dont work
plz help me
i need it
posei-don said:
exe!
yes its ok
i redownload it but its dont work
plz help me
i need it
Click to expand...
Click to collapse
Are you S-off?If not then androidflasher won't work as i read somewhere in the forum that it won't work with s-on device.
if you are s-off then try this
after you flash the recovery image your phone should reboot.Did it rebooted when you flashed?if not then something is wrong.
check your android usb driver and also boot into fastboot and see if your device connect with your pc then try to reflash from there.
Exiled_SouL said:
Are you S-off?If not then androidflasher won't work as i read somewhere in the forum that it won't work with s-on device.
if you are s-off then try this
after you flash the recovery image your phone should reboot.Did it rebooted when you flashed?if not then something is wrong.
check your android usb driver and also boot into fastboot and see if your device connect with your pc then try to reflash from there.
Click to expand...
Click to collapse
thank you
yes im s-off
no its not reboot
i installed android usb driver
but still its not flashe recovery
posei-don said:
thank you
yes im s-off
no its not reboot
i installed android usb driver
but still its not flashe recovery
Click to expand...
Click to collapse
then boot into fastboot,plug usb and goto your pc device manager and find out your device is listed or not?
you can also try to flash it from recovery with zip file
Exiled_SouL said:
then boot into fastboot,plug usb and goto your pc device manager and find out your device is listed or not?
Click to expand...
Click to collapse
thank you
yes its listed
can i install recovery from bootloader?
For example i rename it to PC47IMG.img
yes,That should work too.i never done that as i can flash recovery via android flasher.
I have a rooted One X, with Clockwork Mod and AHRD 6.0.0 Rom, I have a few mods (Rosie, 3-dot remover, status bar icon mods), and I haven't had a problem until tonight when I was playing with Font Installer, and I tried out a new font, and rebooted my phone, then my phone is stuck on the HTC One Beats Audio white screen, it's been about 20 minutes now, and I'm a bit nervous..
Yeah,you should do a nandroid backup because obviously it wont boot,and don't keep it on that logo to much or you will drain you'r battery.I've tryed an app that changes the fonts but also screwed up my phone so i had do to a restore.I don't know what app i can recomend that works so far.
jeyml said:
Yeah,you should do a nandroid backup because obviously it wont boot,and don't keep it on that logo to much or you will drain you'r battery.I've tryed an app that changes the fonts but also screwed up my phone so i had do to a restore.I don't know what app i can recomend that works so far.
Click to expand...
Click to collapse
Thing is, I don't have any nandroid backups to restore from, I formatted my memory card recently because of a memory loss problem and I haven't had a backup since.
blaqtea said:
Thing is, I don't have any nandroid backups to restore from, I formatted my memory card recently because of a memory loss problem and I haven't had a backup since.
Click to expand...
Click to collapse
You don't need a nandroid. Just get into boot loader and use ADB push to push any rom to your virtual SD card then you can install it through CWM recovery. Don't forget the boot.img as well.
Sent from my HTC One X using xda premium
joshnichols189 said:
You don't need a nandroid. Just get into boot loader and use ADB push to push any rom to your virtual SD card then you can install it through CWM recovery. Don't forget the boot.img as well.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I 'adb device' on the PC, it says error: device not found?
Try this, you don't need to push anything, this command will open your sdcard in windows, put your rom.zip in, close the folder and flash through recovery.
In fastboot:
fastboot boot custom-recovery.img
adb shell
echo /dev/block/mmcblk0p14 > /sys/devices/platform/fsl-tegra-udc/gadget/lun0/file
ckpv5 said:
Try this, you don't need to push anything, this command will open your sdcard in windows, put your rom.zip in, close the folder and flash through recovery.
In fastboot:
fastboot boot custom-recovery.img
adb shell
echo /dev/block/mmcblk0p14 > /sys/devices/platform/fsl-tegra-udc/gadget/lun0/file
Click to expand...
Click to collapse
I flashed the custom recovery, but I can't get past adb shell since it just tells me device not found..
blaqtea said:
I flashed the custom recovery, but I can't get past adb shell since it just tells me device not found..
Click to expand...
Click to collapse
We don't flash recovery to have a working adb, we boot recovery:
fastboot boot recovery.img
not
fastboot flash recovery recovery.img
ckpv5 said:
We don't flash recovery to have a working adb, we boot recovery:
fastboot boot recovery.img
not
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok sorry about that, yes I meant I booted the recovery, and adb shell'ed it and it still showed me no device found, something wrong with my adb?
Okay, thanks to everyone who helped, but in the end, I relocked bootloader, and installed stock rom RUU and decided to start everything from scratch phone is booted now and working again!
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?
sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250
efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.
efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.
sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.
would running terminal in windows with admin privileges help?
sent from my i9250
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".
bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?
I have same problem to...
sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250
Hi,
Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled.
This tutorial works for Beta Android O bootloop too.
You will need:
ADB + drivers installed: https://forum.xda-developers.com/showthread.php?t=2588979
Nexus toolkit: DL.- http://www.wugfresh.com/nrt/
STOCK image archive, older than you have now - https://developers.google.com/android/images#bullhead
Latest OTA image archive : https://developers.google.com/android/ota#bullhead
-------------------
Extract stock image (NOT OTA)
install Nexus toolkit and restart your phone in Bootloader mode
connect phone to pc.
In nexus toolkit click on : advanced utilities > launch
look at: fastboot flash
screen: https://postimg.org/image/kkk9h92oz/
click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache.
Copy downloaded OTA ROM archive in ADB folder.
reboot in recovery
now select apply update from adb.
open ADB
flash latest OTA package via command : adb sideload <packagename>.zip
I hope, this tutorial is useful for you, if yes, please hit thanks button.
And sorry for my english.
GREAT!!! Saved my phone. Thank you very much!
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Ins1d3r said:
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
Click to expand...
Click to collapse
You not need usb debugging enabled in system.
Communication with pc is working in fastboot and recovery.
Redmi Note 3 - Tapatalk
any idea how to do it in mac?
What do you mean with: "Copy downloaded OTA ROM archive in ADB folder."
Just sideloading doesn't work.
ADB cant find my 5x...
Thank you OP for this i am need of help and it appears your solution has found me. Im on holiday atm and my nexus 5x just got the dreaded bootloop! Alll i see is the spinning colors for android logo after pin code is inputted.
Im very anxious to backup my photos of my son and family, so want to ask is this method safe? I dont want to risk losing data.. i can get into recovery mode and my phone is boot locked and not rooted, so can someone also tell me if adb backup will allow me to backup my pictures and video reliably? I will do a full backup and then try and flash the OTA.
serving: 'bullhead.zip' (~47%) * failed to read command: No error , what im doing wrong ?
ok succeed after dozen attempts , phone booted to main desktop work for like 5 mins and then frozen , looks like it went back to bootlooping ;(
Hi guys, same situation, since yesterday I could boot with a bit of effort (like waiting 15 minutes of bootloop) but now the 5x doesn't boot at all and so neither in recovery. My phone is locked and never modded so I will send in warranty when I will be back home ( 10 days). So now I would like to fix it to use it at least in this week, but how can I do if I can't boot in recovery?
I can just boot in the bootloader so use fastboot command...if I unlock the bootloader I will get the little lock in the bottom part of the screen, when I will lock it to send it to LG will it disappear?
How exactly is this toolkit's fastboot flashing supposed to work if you have a locked bootloader?
How is using this toolkit any different from running the "flash-all.bat" that's included with factory images?
This did nothing at least in my case.
I get the feeling that the flash operations are failing and the toolkit just disregards this.
Cannot enter recovery
I completed the first step in fastboot but when i try to enter recovery it goes to bootloop again....what should i do?
Nope, not working. Rebooting again and again. Issue not resolved. Please help!
Hi I need help,
what do i choose when i click 'system' tab?
[/QUOTE]
rockhardy said:
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Click to expand...
Click to collapse
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
jcfortunato said:
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
Click to expand...
Click to collapse
It's been a while since I tried it. But as far as I remember it was due to phone not being in recovery mode. I hold the power button until the phone screen went off. And while holding the power button I instantly pressed volume down button to bring back the fastboot mode and then recovery mode.
i'm sorry but i don't see my latest build (currently running on 7.1.2)
i've tried using 'any build', it said that i have to choose one of the build listed :/
thank you
-----
edit
found them!
but it says that my OTA is out ouf date
I downloaded the latest one though (August)
where did I go wrong? :/
Anyone still doing this ha? I've just run into this issue with my wife's phone, and there are things on there she needs..
The ones with issue with the big cores causing bootloops, use this guide to unlock device then proceed with following guide
https://forum.xda-developers.com/showthread.php?t=3641199
Sent from my Nexus 5X using Tapatalk
Hello, I've done all the procedure until reboot recovery, but I've didn't find the button for select apply update from adb in NRT.
Hello,
I'm looking for solution to root my G3121 48.1.A.2.50, I've tried many guides and methods but without success, everytime only thing I get is bootloop. What's important - I have unlocked bootloader by Sony site but without TA backup. Any ideas what should I do to obtain root?
P.S.
How to get backup of boot.img?
Abbrams said:
Hello,
I'm looking for solution to root my G3121 48.1.A.2.50, I've tried many guides and methods but without success, everytime only thing I get is bootloop. What's important - I have unlocked bootloader by Sony site but without TA backup. Any ideas what should I do to obtain root?
P.S.
How to get backup of boot.img?
Click to expand...
Click to collapse
Hi
Try to download magisk and write from ADB on PC inside the folder where you downloaded magisk (assuming that the zip name is "magisk.zip"):
adb sideload "magisk.zip"
Tell me if it works :highfive:
PS: after gaining root, use TWRP builder app to create a custom TWRP and than go to backup/Boot
I guess that you didn't mean to do it in fastboot or something like that? Cause this method doesn't work for me
>adb devices
List of devices attached
* daemon not running. starting it now at tcp: 5037 *
* daemon started successfully *
RQ3007GXJ6 device
>adb sideload Magisk.zip
opening 'Magisk.zip'...
connecting...
falling back to older sideload method...
error: closed
this is what I get from command window
Abbrams said:
I guess that you didn't mean to do it in fastboot or something like that? Cause this method doesn't work for me
>adb devices
List of devices attached
* daemon not running. starting it now at tcp: 5037 *
* daemon started successfully *
RQ3007GXJ6 device
>adb sideload Magisk.zip
opening 'Magisk.zip'...
connecting...
falling back to older sideload method...
error: closed
this is what I get from command window
Click to expand...
Click to collapse
Hi
Try doing before "adb usb"
It should work!
Still nothing, tried 3 times and reply from command window was the same "restarting in USB mode"
I really have no idea what is wrong with that phone, every boot.img I flash doesn't work, once TWRP was only working but when I wanted reboot to system, I got stuck on bootloop
Service Info says that Booloader is unlocked
Has anyone similar issue?
Abbrams said:
Still nothing, tried 3 times and reply from command window was the same "restarting in USB mode"
I really have no idea what is wrong with that phone, every boot.img I flash doesn't work, once TWRP was only working but when I wanted reboot to system, I got stuck on bootloop
Service Info says that Booloader is unlocked
Has anyone similar issue?
Click to expand...
Click to collapse
How to make boot.img from kernel.sin/kernel.elf and patch it?
Abbrams said:
Still nothing, tried 3 times and reply from command window was the same "restarting in USB mode"
I really have no idea what is wrong with that phone, every boot.img I flash doesn't work, once TWRP was only working but when I wanted reboot to system, I got stuck on bootloop
Service Info says that Booloader is unlocked
Has anyone similar issue?
Click to expand...
Click to collapse
Try to install magisk doing what written here https://forum.xda-developers.com/showthread.php?t=2272731 and booting up the phone long pressing up volume + power button(or if it doesn't work do the same steps booting phone with down volume + power button
Than just follow the steps I've written you on first post, to achieve TWRP and backup boot.
This WILL work :highfive:
faby GT said:
Try to install magisk doing what written here https://forum.xda-developers.com/showthread.php?t=2272731 and booting up the phone long pressing up volume + power button(or if it doesn't work do the same steps booting phone with down volume + power button
Than just follow the steps I've written you on first post, to achieve TWRP and backup boot.
This WILL work :highfive:
Click to expand...
Click to collapse
I can't use sideload because I don't have any recovery, so method is not usable for me. Tried to update adb files but the same effect. Any other ideas? I really need stock boot.img for G3121 with TWRP, that will not fall in bootloop.
Many tries, no success, what am I doing wrong?