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:
Related
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.
FOR LG-H815, bought in Germany.
a) Went through the effort and unlocked the bootloader through LG's official method.
b) Confirmed, several times, that the bootloader is indeed unlocked.(via 'fastboot getvar unlocked' and verifying that the response is "unlocked: yes")
c) Tried to swap the Stock Recovery Mode with TWRP, using 'fastboot flash recovery twrp-2.8.6.0-h815.img'. The process ends in 1 sec. After booting in recovery mode, I find out it doesn't actually flash it.
d) Inside cmd: adb reboot bootloader
fastboot boot twrp-2.8.6.0-h815.img
At this point I am trying to boot TWRP for a one-time job of rooting the device.
-Install>>Select UPDATE-SuperSU-v2.46.zip>>Swipe to Install>> Reboot System
e) After reboot: PERMANENTLY STUCK, will not boot past LG's Logo. It is still possible to enter the Stock Recovery Mode, and Stock Download Mode.
I have repeated the process twice, reflashing the stock ROM, to the same effect. Any help is greatly appreciated.
You're flashing outdated versions of TWRP and SU...
I helped with this problem about 100 times now but I will do it one more time...
Firstly, reflash the stock MM ROM again.. Then download the better looking TWRP 3.0.2-0 from official twrp site -> https://dl.twrp.me/h815/twrp-3.0.2-0-h815.img.html
Now a little explanation. As far as I know in 6.0.X Google changed their policy a bit and the option to root the phone/ flash recovery is locked even though you have unlocked bootloader, and as well system root doesn't work, so instead of old SuperSU 2.46 you want to download newest systemless root zip -> http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 . Now, since there is no stock modified boot.img for G4, you have to download and unpack the custom kernel like SimpleGX and take it's boot img that you want to flash via fastboot, or you can try flashing boot.img from the Autoprime's V20D flashable zips, I didn't try that one and I will not be able to because my G4 got a bootloop issue that I recovered it of by my self but I cannot boot it up on Marshmallow stock firmware. Anyway once you flashed the modified boot img you should be able to flash recovery and boot it up normally, then flash systemless root and if you used boot.img from custom kernel, flash the full package because you did not flash all the stuff from the package what may cause software problems in the long term I suppose. I think that's all you need to do to root it on MM.
Adam Myczkowski said:
I think that's all you need to do to root it on MM.
Click to expand...
Click to collapse
And you would be correct. Although I have to wonder why guides on XDA don't even mention flashing a custom kernel like SimpleGX_KERNEL_H81520X_v1.3.2.zip
Additional steps for installing ROOT/TWRP on LG G4:
Inside CMD:
C:\adb>adb reboot bootloader
error: device '(null)' not found
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot bootloader
C:\adb>fastboot boot twrp-3.0.2-0-h815.img
downloading 'boot.img'...
OKAY [ 0.956s]
booting...
OKAY [ 0.028s]
finished. total time: 1.000s
Inside TWRP: Install>>Select SimpleGX_KERNEL_H81520X_v1.3.2.zip>>Swipe to the right>>Reboot // .zip file is ~19MB
Inside CMD:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-3.0.2-0-h815.img //now attempting to overwrite the stock recovery
target reported max download size of 536870912 bytes
sending 'recovery' (31652 KB)...
OKAY [ 0.969s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.365s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>adb devices
List of devices attached
LGH81539bf5a8e device
C:\adb>adb reboot recovery //to verify that TWRP has been installed.
Inside TWRP:
Install>>Select BETA-SuperSU-v2.71-20160331103524.zip>>Swipe to the right>> Reboot
DONE.
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
fastboot boot twrp.img
creating boot image...
creating boot image - 13133824 bytes
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
FAILED (remote: image verification failed)
Click to expand...
Click to collapse
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Have you tried flashing stock?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
xrad said:
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
Click to expand...
Click to collapse
No, meanwhile I returned it to google and got a new one. But thank you for help!
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
moinkazi said:
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
Click to expand...
Click to collapse
delete
allrockedout said:
This is stock recovery. Flash in twrp as image. Select recovery ramdisk as partition.
After flash. Reboot to recovery from twrp. That should take you to stock recovery. There you can do a factory reset.
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=sharing
If you also flashed magisk or root. You will need to flash kernel as well. I was able to flash in fastboot mode. https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=sharing
Click to expand...
Click to collapse
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
moinkazi said:
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
Click to expand...
Click to collapse
The recovery I posted before was for bl24 usa version ORRRREEEEEOOOOO ONNNNLLYYY. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
allrockedout said:
The recovery I posted before was for bl24 usa version. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
Click to expand...
Click to collapse
Thnks bro
Perfect time to find this post. I am getting the OTA update notification but it won't install on TWRP. My strategy is to return to stock (unrooted and stock recovery) to get the OTA. Once I am on that, get TWRP and Resurrection Remix.
allrockedout said:
The recovery I posted before was for bl24 usa version...
Click to expand...
Click to collapse
BND-L24 you mean?
duckredbeard said:
BND-L24 you mean?
Click to expand...
Click to collapse
Si
allrockedout said:
Si
Click to expand...
Click to collapse
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
duckredbeard said:
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
Click to expand...
Click to collapse
I tried flash recover ramdisk than kernel in twrp, rebooted to stock recovery and factory reset. But wouldn't boot, than booted to fastboot and flashed kernel, fastboot flash kernel kernel.img and it rebooted and was all good. Just my experience.
Just trying to avoid using adb.
duckredbeard said:
Just trying to avoid using adb.
Click to expand...
Click to collapse
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
allrockedout said:
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
Click to expand...
Click to collapse
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
duckredbeard said:
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk recovery_ramdis.img
allrockedout said:
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
duckredbeard said:
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
Click to expand...
Click to collapse
You can boot to fastboot from twrp than start flashing
allrockedout said:
You can boot to fastboot from twrp than start flashing
Click to expand...
Click to collapse
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
duckredbeard said:
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
Click to expand...
Click to collapse
Yeah bootloader is correct. Good luck.
allrockedout said:
Yeah bootloader is correct. Good luck.
Click to expand...
Click to collapse
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
duckredbeard said:
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
Click to expand...
Click to collapse
Is frp and bootloader unlocked when rebooting to fastboot both are red?