Hi,
I want to install TWRP so I can Install nAOSP ROM 8.1 for Xperia S on my phone.
The phone's bootloader is unlocked and the phone is rooted. I downloaded the correct version of TWRP from here (nozomi).
I tried installing via ADB (I followed the instructions here), but the command:
Code:
fastboot flash recovery twrp-3.2.3-nozomi.img
Fails with:
Code:
Sending 'recovery' (12964 KB)
(bootloader) USB download speed was 33272kB/s
OKAY [ 0.415s]
Writing 'recovery'
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: 'Partition not found')
Finished. Total time: 0.437s
I understand that this is because Sony phones don't have separate recovery partition, and that their recovery is incorporated to the boot.img (see here).
I then tried using the dd install method as described on the project's homepage.
Code:
$ ./adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
25929+1 records in
25929+1 records out
13275872 bytes transferred in 3.747 secs (3543066 bytes/sec)
Although this seems to work (i.e. I don't get an error message), I cannot, try what I might, make the phone boot into recovery.
Can anyone tell me what I'm missing?
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
_jack said:
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
Click to expand...
Click to collapse
How exactly did u do that...i have spent over a week trying to do it.
sweetbanana said:
How exactly did u do that...i have spent over a week trying to do it.
Click to expand...
Click to collapse
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
_jack said:
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
Click to expand...
Click to collapse
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
ZebastianJV said:
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
Click to expand...
Click to collapse
Try flashtool to install twrp. twrp link: https://androidfilehost.com/?fid=1322778262904003720
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
No, it won't be a problem.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
i had the same issue i just flashed the firmware boot.img with flashtools 0.9.8.0
Extract with 7zip/winrar/winzip. Use this kernel via flashtool. has recovery. note for unlocked bootloaders only
Related
Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?
How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?
I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?
the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?
BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.
BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.
IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.
I update, my ROM from cyanogenmod ROM 10.1 m1 to 10.1 m2 ROM and know my galaxy nexus is stuck on boot loop animation! I tried, tacking out the battery and then turning it back on no luck in also tried the ( volume button and power button method) and still no luck with that. Is,there a way I could fix it?
wipe data and reflash rom.
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
Never, mind i got it working know!
mrcoleminer said:
Zepius said:
wipe data and reflash rom.[/QQ
How, do i wipe data?
Click to expand...
Click to collapse
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Zepius said:
mrcoleminer said:
in recovery, there's an option to wipe data and cache. do that.
Click to expand...
Click to collapse
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
Chamaeleon said:
Zepius said:
Hello,
I also have this problem but, moreover, I think I'm also not able to do a data/factory reset (from the recovery I can start the procedure but than the phone reboots without finishing...)
All the rest is the same:
- stucking loop after Cyanogenmod logo and rebooting from the beginning (google logo)
- the new rom I've pushed was disappeared from the folder
So now I don't know what else I can do...
Click to expand...
Click to collapse
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
Soulaysahmi said:
Chamaeleon said:
which recovery do you have? have you tried putting a new zip update package in the "folder" via usb?
Click to expand...
Click to collapse
I was using the ClockworkMod (I don't remember exactly the version number but I updated recently and it was the touch screen one). I'll try to re-install also the recovery with the very last version (6.0.4.7). Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
Chamaeleon said:
Since now I only put a new cyanogenmod rom (both cm-11-SNAPSHOT-M12 and the last stable cm-10.2.1) with adb push
Click to expand...
Click to collapse
have you tried adb sideload?
Soulaysahmi said:
have you tried adb sideload?
Click to expand...
Click to collapse
Just tried.
On the terminal after the command
adb sideload cm-11-20141115-SNAPSHOT-M12-maguro.zip
it tells me "error: closed"
I also tried to reinstall the Clockwork via bootloader but didn't change the situation (still not able to do a complete factory reset)
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Soulaysahmi said:
you first did click on "install zip from sideload" in clockworkmod to activate sideload on the phone, didn't you?
Click to expand...
Click to collapse
You are right, I didn't click "install zip from sideload" before. Now I tried in this way and, effectively, it worked: I managed to send and install the zip apparently without any problem but than after rebooting I'm still not able to turn on the phone completely. Again the same problem. I re-tried to do wipe data/factory reset both from the recovery and using adb but didn't managed to finish the process...
It seems I tried all the options since now.... but my nexus is still unusable...
did you try getting back to stock rom using any guide on this forum?
Soulaysahmi said:
did you try getting back to stock rom using any guide on this forum?
Click to expand...
Click to collapse
I tried but still with the same result. I'll try to follow the guide I found here
I mean through methods other than recovery, through fastboot mode or odin mode.
Soulaysahmi said:
I mean through methods other than recovery, through fastboot mode or odin mode.
Click to expand...
Click to collapse
I tried to Restore Galaxy Nexus to Stock (as described here) with the proper google image but in the last passage I get:
$ fastboot -w update image-takju-jwr66y.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMELC03
Baseband Version.....: xxx
Serial Number........: xxx
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
FAILED
Device version-bootloader is 'PRIMELC03'.
Update requires 'PRIMEMD04'
I put all I need in one folder and I decided to update the bootloader at the PRIMEMD04 version but apparently I didn't managed because doing again the procedure I was getting the same error
ps: I'm using linux so I don't have odin
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Soulaysahmi said:
when the phone is in fastboot mode you should find your bootloader version at the bottom left of the screen, in your case it should be:
BOOTLOADER VERSION - PRIMELC03
when you flash a new bootloader through: fastboot flash bootloader {your-bootloader.img}
you need to reboot for the changes to take effect, you can do it with: fastboot reboot-bootloader
after that you should see a different version on your screen, is that the case?
Click to expand...
Click to collapse
Yes I have BOOTLOADER VERSION - PRIMELC03
With fastboot I tried to install the PRIMELC04 bootloader
$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
OKAY [ 7.969s]
finished. total time: 8.278s
$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But than, after the reboot, on the screen it's still written BOOTLOADER VERSION - PRIMELC03
I think this is the main problem now... if it's not updated the bootloader I can not reinstall the rom probably...
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Soulaysahmi said:
you can bypass the version checking by extracting the update zip and flash each image manually
in your zip you should find 4 img files: {system,boot,recovery,userdata}.img
you can flash them on by one like the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Tried as you suggested to install the PRIMELC04 bootloader flashing each image.
Apparently is not possible also in this way. After rebooting on the screen is still written BOOTLOADER VERSION - PRIMELC03.
So I tried to install a stable cyanogenmod 10.2.1 (which should work with the bootloader 03).
I used adb sideload and after the "installing updates" message, everything stopped with the message "fixing fs_size in crypto footer". After more than 30 min I rebooted and the situation was the same as before.
Hello,
I have a big problem with my H815.
My H815 bootloader is been unlocked.
II try to install TWRP, but without success:
Code:
C:\Users\~\Downloads\G4\platform-tools>adb reboot bootloader
C:\Users\~\Downloads\G4\platform-tools>fastboot flash recovery twrp-2.8.7.0-h
815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32064 KB)...
OKAY [ 1.197s]
writing 'recovery'...
OKAY [ 0.317s]
finished. total time: 1.520s
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
For me, it's ok, but after that, my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Any idea please?
Kind regrards,
~~
Sylar
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
nfsolutions said:
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
Click to expand...
Click to collapse
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
This does not work for me. :'(
After this command : fastboot boot twrp-2.8.7.0-h815.img
My G4 boot imediatly to the System... :s
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
thanks, now it works. My mistake was that I installed directly a supersu (not this from twrp) and this messed up the boot.
After installing twrp permanently, I used this method to get root:
http://forum.xda-developers.com/g4/general/guide-root-lg-marshmallow-rom-repacked-t3265497
now I have root and twrp
Can someone help me please ?
I tried to flash the KDZ 2 times but still nothing I parobleme always the same.
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
Thank you Sir!
Got the same problem, installed TWRP but got bugdroid dead once booting recovery. Idk why TWRP isn't written.
Nothing to do I'm trying every way I could imagine. The result is always the same.
I can't find solution on any forum. Please, I need help. :'(
Kind Regards
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
rjboy11223 said:
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
Click to expand...
Click to collapse
No i'm not rooted atm. That why i wanna install a custom recovery ^.^
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
bender_007 said:
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
Click to expand...
Click to collapse
Thank you, but after that... :
Code:
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
...my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
bel57 said:
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
Click to expand...
Click to collapse
Thank you, but same problème i can't boot to TWRP after the comand "fastboot boot twrp-2.8.7.0-h815.img" my G4 reboot directly to the system.
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
bel57 said:
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
Click to expand...
Click to collapse
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Ur phone is weird lol
Sylar37 said:
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Click to expand...
Click to collapse
try first fastboot erase recovery, then fastboot flash recovery twrp....img
then fastboot reboot recovery
I downloaded the v20b kdz and flashed via LGUP.. I don't know what's wrong mate, sorry. :silly:
Hi, Guys.
I am trying to install the recovery in my phone, but without success.
I already tried some versions of twrp for our moto z play and able not to flash the trwp.
My bootloader is unlocked.
When i typed , show me the message below.
C:\Users\myuser\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY [ 0.400s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.197s]
finished. total time: 0.601s
fastboot flash recovery ( here the name of your twrp recovery).img
f1fan said:
fastboot flash recovery ( here the name of your twrp recovery).img
Click to expand...
Click to collapse
I already tried severa times and not worked.
iago1966 said:
I already tried severa times and not worked.
Click to expand...
Click to collapse
Are you sure it didn't work? The message is just a warning. The second OKAY indicates that it has been flashed sucessfully.
tomparr said:
Are you sure it didn't work? The message is just a warning. The second OKAY indicates that it has been flashed sucessfully.
Click to expand...
Click to collapse
Hi,
I'm sure that, but when show me "writing 'recovery', i think that the hour what the recovery is instaling in the device, but don't write.
When i choose the option for to go recovery, show me " no comand" and the robo of android .
iago1966 said:
Hi,
I'm sure that, but when show me "writing 'recovery', i think that the hour what the recovery is instaling in the device, but don't write.
When i choose the option for to go recovery, show me " no comand" and the robo of android .
Click to expand...
Click to collapse
What recovery are you trying to flash?
If you are flashing stock recovery , the "no command" screen with the android robot is correct.
tomparr said:
What recovery are you trying to flash?
If you are flashing stock recovery , the "no command" screen with the android robot is correct.
Click to expand...
Click to collapse
I tried recovery of Alberto97(tree versions), tried also chinese recovery, both does not worked.
Did you test the recovery you want to flash by using
fastboot boot recovery
?
It is a bad idea to directly flash an untested recovery. You may get the wrong file. Your download may be broken. Just test it at least once using fastboot boot, and if it runs you may try to flash. I am sure I don't want to flash anything that does not run. Usually I do not flash, but run using the cable if I need it. Do you really need the recovery when you're away from your computer?
I hate doing this since I've been a long time user and usually am able to figure stuff out on my own, but I'm hoping there is an easy fix. I dirty flashed the new aokp update over an older aokp version for the pixel xl and i forgot to flash the twrp image after. Now the system ui crashes upon boot (no surprise there) and I can only get into bootloader and the stock phone recovery. How do I get twrp back?
localceleb said:
I hate doing this since I've been a long time user and usually am able to figure stuff out on my own, but I'm hoping there is an easy fix. I dirty flashed the new update over an older aokp version for the pixel xl and i forgot to flash the twrp image after. Now the system ui crashes upon boot (no surprise there) and I can only get into bootloader and the stock phone recovery. How do I get twrp back?
Click to expand...
Click to collapse
You fastboot boot twrp then flash it in twrp. The same way you got it the first time.
pcriz said:
You fastboot boot twrp then flash it in twrp. The same way you got it the first time.
Click to expand...
Click to collapse
I used the toolkit last time, but I cant adb to recognize the phone in its current state
localceleb said:
I used the toolkit last time, but I cant adb to recognize the phone in its current state
Click to expand...
Click to collapse
This why I wouldn't use a toolkit, you're just kind of handicapping yourself..
You don't need adb to fastboot. either you are using adb (in the booted OS or in recovery) or you are using fastboot (in the bootloader).
You should take a gander at a few of the guides in the Guides section on how to install recovery.
TWRP Thread:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
How to Guide for Beginners (look for the portion on installing twrp):
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Good luck.
localceleb said:
I used the toolkit last time, but I cant adb to recognize the phone in its current state
Click to expand...
Click to collapse
If you are in bootloader mode when you type adb commands it will fail. You use Fastboot commands at that point.
ADB commands are for when tbe phone is booted normally.
TonikJDK said:
If you are in bootloader mode when you type adb commands it will fail. You use Fastboot commands at that point.
ADB commands are for when tbe phone is booted normally.
Click to expand...
Click to collapse
Can you mount the system and use adb commands through the stock recovery? I can't seem to get any fastboot or adb commands to work at all. Even when the system is booted up. The system ui crashes, but shouldn't adb commands still work at that point?
localceleb said:
Can you mount the system and use adb commands through the stock recovery? I can't seem to get any fastboot or adb commands to work at all. Even when the system is booted up. The system ui crashes, but shouldn't adb commands still work at that point?
Click to expand...
Click to collapse
Who knows what else crashed if the ui crashed. Power down, count to ten. Then power and vol down. Once in recovery, connect it to the computer. Not before.
Fastboot devices
If it shows flash the factory image. Modify the bat file and remove the -w to save your data.
If it doesn't connect try other usb ports. Mine won't connect to my front panel, only the rear.
And try another cable.
TonikJDK said:
Who knows what else crashed if the ui crashed. Power down, count to ten. Then power and vol down. Once in recovery, connect it to the computer. Not before.
Fastboot devices
If it shows flash the factory image. Modify the bat file and remove the -w to save your data.
If it doesn't connect try other usb ports. Mine won't connect to my front panel, only the rear.
And try another cable.
Click to expand...
Click to collapse
Well, in theory if I can get fastboot to work I would want to flash the twrp recovery image and then restore a backup, right?
localceleb said:
Well, in theory if I can get fastboot to work I would want to flash the twrp recovery image and then restore a backup, right?
Click to expand...
Click to collapse
I am not a fan of TWRP backups on the Pixels. Seen a few bricks, especially on R2.
So i have attempted to fastboot flash a twrp img and its failing.
C:\Android\TWRP>fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (26588 KB)...
OKAY [ 0.917s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.020s
Am I safe to try a factory image or am I doing something wrong trying to flash the recovery image. ADB commands don't seem to work at this point for some reason.
Thanks for any help!
localceleb said:
So i have attempted to fastboot flash a twrp img and its failing.
C:\Android\TWRP>fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (26588 KB)...
OKAY [ 0.917s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.020s
Am I safe to try a factory image or am I doing something wrong trying to flash the recovery image. ADB commands don't seem to work at this point for some reason.
Thanks for any help!
Click to expand...
Click to collapse
You are doing it wrong. You copy the TWRP zip to the phone.
Then
Fastboot BOOT twrp twrp-3.0.2-0-RC1-fastboot-marlin.img
That boots you to twrp. Then you install the twrp zip while in twrp.
You can not install twrp any other way.
TonikJDK said:
You are doing it wrong. You copy the TWRP zip to the phone.
Then
Fastboot BOOT twrp twrp-3.0.2-0-RC1-fastboot-marlin.img
That boots you to twrp. Then you install the twrp zip while in twrp.
You can not install twrp any other way.
Click to expand...
Click to collapse
I need to add that I cant boot into the system as the system ui crashes so I have no way to transfer files to the phone at this place.
localceleb said:
I need to add that I cant boot into the system as the system ui crashes so I have no way to transfer files to the phone at this place.
Click to expand...
Click to collapse
Fastboot boot to twrp as I described. TWRP has ADB in it, so then from your computer you can ADB push the twrp zip and install it.
But I still advise you to flash the factory image after removing the -w from the flashall bat file.
TonikJDK said:
Fastboot boot to twrp as I described. TWRP has ADB in it, so then from your computer you can ADB push the twrp zip and install it.
But I still advise you to flash the factory image after removing the -w from the flashall bat file.
Click to expand...
Click to collapse
He shouldn't bother removing the -w. A fresh image is what he is in need of. Wipe the phone and start over. Easy.