Related
Hello Guyzzz!!!!!
A Great Newzz for ALL!!!!! First the recovery was not compiled by me!
But NOW I am BACK with a FULLY WORKING RECOVERY AND FULLY COMPILED BY ME :good:
We have now a FULLY WORKING CLOCKWORKMOD RECOVERY v5.0.2.8.
The CLOCKWORKMOD RECOVERY is TESTED on :-
1. LG OPTIMUS 3D MAX P725
2. LG OPTIMUS 3D MAX P720H
I HELD NO RESPONSIBILITIES FOR BRICKED PHONES. YOU MAY TRY ON P720 BUT AT YOUR OWN RISK.
Credit Goes to :-
1. I, Me and Myself ( For taking the initiative,compiling testing and removing all bugs )
2.. Cynogenmod for the SOURCES.
3. P720H tester ZOOM.
According to me, the CWM RECOVERY is fully working.
HERE ARE THE STEPS TO INSTALL THE CWM RECOVERY :-
Download the CWM RECOVeRY FINAL.zip from the link given below :
http://www.mediafire.com/?p59d9ppjlhkcp67
Copy the cwm5.0.2.8.img on the ROOT OF THE SDCARD not the External SDCARD ( Root of SDCARD means not in any folder )
The BIGGEST REQUIREMENT IS YOUR OPTIMUS 3D MAX should be ROOTED!!!
Now download ANY TERMINAL EMULATOR from the GOOGLE PLAY!!!!!
You can try this :-
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
And install it.
Type the following commands in TERMINAL EMULATOR :-
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/cwm5.0.2.8.img of=/dev/block/mmcblk0p6 bs=4096
Once complete.
Turn off your phone.
1st hold 3d key then volume down button and at last power button.
Keep holding till the LG LOGO appears and leave when it appears.
You will enter the CWM Recovery
Proof of the Recovery :-
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
lordasphyxia said:
Worked like a charm! First I couldn't get the # to appear (the phone WAS rooted) so I just used the terminal emulator you specified, and that solved it.
Click to expand...
Click to collapse
Happy to help you.
"HITTING THANKS WILL ENCOURAGE ME MORE":good:
Eklovya said:
IT TOOK MORE TIME TO DEVELOP THIS RECOVERY THAN THE TIME YOU WILL TAKE TO JUST " HIT THANKS".
Click to expand...
Click to collapse
dude you are not developed this recovery, it's created by me, you only unpacked my recovery using kitchen , that not call develop
Where did i mentioned that I DEVELOPED???
I clear mentioned that you compiled and i removed all bugs...
Sent from my LG-P725 using xda premium
Thread for this exists from original dev
http://forum.xda-developers.com/showthread.php?t=1889468
Thread closed
Edit: Thread reopened for a newly compiled version
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
TommyX235 said:
HELP!!!!
After downloading an update from LG it allways boots to recovery!!
Click to expand...
Click to collapse
Try doing a factory reset.!!!
Sent from my LG-P725 using xda premium
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
TommyX235 said:
tryed everything .. factory reset .. i have a backup from my original rom.. when i restore it i also boot into cwm.
i can start sw update mode (vol +) but either there nor in cwm i have adb access..
i tryed kdz but i don't know the dev type .. i tryed TI / 3GQCT etc. the program crashes
its breaking my heart .. i have this device the first day and now its broken!
ARRGG!!!
I still have the backup of the mmcblk0p6.backup
can i do anything with it?
maybe it is possible to install it via zip in cwm?
Click to expand...
Click to collapse
Install LG SUPPORT TOOL IN PC.
KEEP YOUR PHONE IN DOWNLOAD MODE.
CONNECT TO PC.
OPEN LG SUPPORT TOOL.
IN TOOLS SELECT RECOVER PHONE.
INPUT YOUR IMEI.
AND WAIT FOR THE RECOVEY PROCESS TO FINISH.
ALL WILL BE DONE SAFELY AND YOU WILL GET THE PHONE WORKING
Sent from my LG-P725 using xda premium
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
TommyX235 said:
this damn tool doesn't recognize my IMEI also when i enter my device type p720 & Serial a small window pops open showin my device and my serial .. when i click ok .. another popup telling .. please check your device or something.
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
also why is adb not working?
Is there a way to get it workin in CWM?
In CWM in section advanced you can do show log.
CWM-based Recovery v5.0.2.8
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=omap4430
ro.revision=7
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:checking for extendedcommand...
I:Skipping execution of extendedcommand file not found...
Does this mean something?
Also this lg Tool only worked for me when adb also was working.
Click to expand...
Click to collapse
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
TommyX235 said:
is it somehow possible to activate nable adb access in CWM 5.0.2.8?
or can i flash a zip to do this?
Again .. i can enter S/W Upgrade Mode
There i only see S/W Upgrade
Please wait
while upgrading....
(NO ADB ACCESS! But the Tool recognize the phone but won't let me start the sw upgrade.)
In CWM i can mount & unmount storage and flash zip files or backup / Restore.
BUT no ADB access and Restoring the backup i made doesnt work either)
What breaking my head is that the LG Update must had set a flag to boot into recovery after i downloaded it so mindless.
Since then i stuck in cwm bootloop. There mus be a way to reset this flag. Somehow!!!)
Its over .. i flashed CWM-Loop-DeLooper -> now i stuck @ LG Logo.. also vol+ to enter S/W Upgrade not working anymore. Now its bricked! ARGH!
Click to expand...
Click to collapse
Can you come on chat? So that i can help you!!
Sent from my LG-P725 using xda premium
can this tutorial work on ICS su870?
joseph168 said:
can this tutorial work on ICS su870?
Click to expand...
Click to collapse
Nop this will not work. As the bootloader is locked for su870
Sent from my LG-P725 using xda premium
LG P725 CWM Problem
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Andrelius1 said:
Hi guys need help, i installed this cwm recovery with no problems, when i start it i see menu, can move up and down but i can`t launch anything. I read at different sites that i should to use shutdown key or 3d key but they don`t work. Also i install newer version 6.... but there are this problem too. I have LG 3D max (P725) version o firmware v10f.
Click to expand...
Click to collapse
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
CWM problem
Eklovya said:
use volume keys to move up and down.
and capacutive keys to select
Sent from my LG-P725 using xda premium
Click to expand...
Click to collapse
Thanks a lot! Its strange that in any instruction not says this way of use CWM, i read a lot differents cwm instructions, but the always the same - use power off key ot use 3d button.
Who don`t how to use CWM menu :
"properties button" - up
"home button" - down
"back button" - back
"search button" - ENTER
Cannot select options in cwm
Hi Eklovya,
Brilliant job done!!
I have successfully rooted and installed CWM following your method.
However, when i go boot to CWM, I can use the volume buttons to highlight the options (I wanted to backup), but I am not able to select the options. i tried the power button and the 3D button, no go. What do i do?
I just exchanged my P920 and got myself this P725 today!!!
schubeir
EDIT: my bad!!! found the solution in the post just above!!!!
schubeir
(possibly long post , I will try to make a post at least a little fun to read).
Guys, I humbly come before you, kneeling and desperate, trying to solve my problem .
I've serarched XDA and a lot (!!) of others forums and comunities to revive my P720H (LG optimus 3D Max in Brazil).
I am not a complete noob in custom firmwares for Android, but this time, the LG phone gave me a hell of a headache (and almost a divorce, for the 3 days going too late to bed, trying to solve it).
I will explain what happened and what I've already tried to do and the results.
Causes:
I've tried to install ClockworkMod in my P720H because it still was in Android 2.3.6 (I think).
I've successfully rooted the phone using this thread: http://forum.xda-developers.com/showthread.php?t=1886057 with the SuperSU app on GooglePlay.
When I asked CWM app to reboot in recovery mode (to wipe things and install the .zip file on the sdcard root) things got bad.
My phone could not get passed the LG logo anymore.
So far we have a cause: CWM app did something to the phone. I am not able to boot the recovery menu nor to pass the LG logo on the screen.
Over the communities we may find that it's a common issue.
It is important to say that I am able to enter the 'S/W updating' state. When I connect the phone to the computer, holding VOL+ and placing the battery, I got the S/W screen.
What can I do? In several posts (even here in xda) we may find 3 or 4 different solutions to restore the phone. I think I've already tried everything, but I am sure that the steps became fuzzy in my read and I mixed the solutions in the end.
Drivers:
- I have already the drivers installed: When I connect the phone (with or without battery and with or without vol+ pressed) my Device Manager recognizes everything. I don't have any component marked as 'unknown device' or with exclamations points or anything. This is a good thing, I guess. I had to install more than one thing to solve every driver problem. I don't remember exactly, but I think that the LGDriver-something and the omap4430 something too.
Solutions:
- I have tried the LG Support Tool and so far it appears to be the closest to a solution that I've reached. With the phone connected (in S/W mode or no), I insert the IMEI and the software recognizes the model and starts downloading something (500mb approx.). But after decompressing, during the installation phase, it gets stuck at 4%. I waited for more than 20min and still got nothing better than 4%. It appears to be a common issue too.
- The LG_FlashTool (version 1.2) does not work either. In fact, it does not even recognizes the phone. I've changed the COMport to 41 (according to some guide) on Windows Device Manager and chose the port 1 on LGFlashTool. Even after selecting the kdz, bin and fls files, the software does not connect to the phone. I don't have a screenshot here, but I've seen here in xda that the software displays the model of the phone on the top and a READY message on port 1. Mine does not do it.
- KKDZ_FW_UPD_EN: I've tried this one but it does not even start working. The interface is not that good, so I don't know where I may be failing. I need to 'read phone information' or not? What do I have to chose on each combobox? How to proceed?
And why the hell is there so much .exe on this thing? Do I have to run a apache server to do something?!
- OMAP4BOOT: This one connects to the phone and works, I think. But I don't know its purpose. It's just to place the phone on 'S/W updating' mode? If so, it's useless, because I can enter it easily. If no, maybe I am missing something. Either way, I don't have a version for the P720H. If I remeber correctly, it proposes P999, P760, P870, ... I choose P760 to test it and it works (apparently, again).
- SmartFlashTool: I don't remember if I have already tried this one. As I said, it was too much already.
- NVFlash: I've found it only to G2X, so I didn't know if I should try forcing it to my model. I can give it a try if you help me.
Other softwares and downloads:
KDZ:
- V10B_00 and V1A_00: found today and downloaded for my model and country (will try to extract things and use it later).
- LG_P725_V10F_00: I was using this one until yesterday, because I didn't have the one to P720H
- LGP700AT-01-V10d-232-03-SEP-11-2012+0.dz : Found in an indian repository of some kind of LG data leak. Apparently is useless. DZextract gave me nothing.
DLL: LGP720_20120330_LGFLASHv1377: Needed in some of the softwares above (LG FLashTool? I don't remeber).
BIN and FLS: LGP725_LG_P725_V10F_00_AP.bin and LGP725_LG_P725_V10F_00_CP.fls, extracted from LG_P725_V10F_00.kdz. I don't know, but I should try extracting these from the V10A_00, because apparently is the correct one for my model/country (I am not in my house right now).
Well... :crying:
tl;dr version:
I am facing a LG logo boot loop in P720H. I've tried to reboot CWM in recovery mode but it didn't work. I've tried several approaches but I don't even know what is the point of each one. I found that this is the best topic to use, because is one of the fews that covers the P720H.
I have all those softwares and almost 5gb of downloaded material (kdz, img, bin, exe, ...) but I don't know what I am supposed to use.
In the end, I want my P720H in android 4.x if possible. If not, I just want the crap 2.3.6 again. :crying:
Can you help me? I am not a total noob in custom firmwares and roms, and I am willing to pass all the information that I can :fingers-crossed:
Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
does anyone enable lte bands, 4 and 28?
just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI
Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????
Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!
Does this work for s5 pro l58041?
Thanks
B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!
Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...
so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os
I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img
Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
has anyone achieved unlocking bands in this phone?
Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try
Could you plz make tutorial about getting back to stock unroot...thx
Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
#RESERVED2
Make sure you have enough space on internal storage before flashing the backup zip. You'll likely need 10GB+. this new zip now checks free storage on internal and aborts if not enough. it also now creates a flashable restore zip so now youll have the restore zip internal storage/dump/backup.zip and you can flash this zip when you get a non 9008 brick
Dumps can be done with aosp or custom roms but please try to backup only stock roms if possible. Thanks Everyone!
EDIT: NEW ZIP HAS BEEN ATTACHED.
#RESERVED3
#RESERVED4
I'll be releasing the flashable zip to dump your partitions later today!
Added a flashable backup zip. please flash in twrp and then upload Backup.zip from internal storage Dump folder somewhere and send link here. ill make a restore zip so we can make the v30 almost unbrickable :good:
LG V30 bricked
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
sicci75 said:
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
Click to expand...
Click to collapse
Your mistake was not following any of the rooting Instructions in this V30 forum. If you did, you know we don't use SuperSu, we use Magisk. That's probably what messed up your phone.
I understand you obtained an "official" bootloader unlock code from LG for your H930 -- which is not necessary now for almost a year with the WTF exploit -- but you still need to follow the rooting instructions guide.
The unlocked bootloader warning screen is normal. Ignore it, it's just a harmless annoyance. You would have learned that if you read the instructions.
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
If/when you recover, your bootloader should still be unlocked, but you'll have install TWRP again and this time use Magisk. Read the WTF instructions, but you can skip the bootloader part, as you've already done that. You can start with Section 6. Read those instructions on a web browser, not an app.
ChazzMatt said:
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
Click to expand...
Click to collapse
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
sicci75 said:
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
Click to expand...
Click to collapse
Are you able to get into Download mode?
You want the "patched" version, but be sure to read the installation instructions.
Yes, you can use that KDZ.
If for some reason your bootloader is not still unlocked, you can run your code again.
ChazzMatt said:
Are you able to get into Download mode?
Click to expand...
Click to collapse
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
sicci75 said:
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
Click to expand...
Click to collapse
Glad to help.
Sent via open market LG US998 V30/V30+
So just uploaded a new zip in post 3. this new zip now checks for free space and will abort if theres not enough to create the backup and flashable restore zip. need at least 10GB in Internal Storage. the zip will now create automatically a flashable restore zip :good: i designed this around the v30 but in theory it should be able to work on all qualcomm devices and maybe even some other SoCs as well. but this has not been tested on other devices. ive fully tested this on my ls998 and everything works great! Enjoy!
john, did i ever tell you, that i like your work and efforts? good man! :good:
Lg v30 h932 brick
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
It was a big mistake and I don't know what to do, my phone does nothing, totally dead
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 04:04 AM ---------- Previous post was at 03:26 AM ----------
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?!!!
JohnFawkes said:
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
robertojha said:
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
Click to expand...
Click to collapse
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Lg v30 h932 brick
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
From what I know, there is no fire hose for the H932.
Sent from my LG-H932 using XDA Labs
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
robertojha said:
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
Click to expand...
Click to collapse
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
From what I know, there is no fire hose for the H932.
Click to expand...
Click to collapse
Ah, yeah you're right.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
BROKEN1981 said:
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Click to expand...
Click to collapse
The T-Mobile root guide does say flash the LAF partition of the H933. But only the LAF partition. Some people do not pay attention and flash the entire H933 kdz over the T-Mobile H932 and brick their phone.
Just had a guy in the Frankenstein thread who said he followed instructions. I didn't believe, told him so, and asked him to tell me step-by-step what he did... Turns out rather than flash US998 Nougat, then Master Reset, then Oreo of choice -- he flashed 20f (Oreo), Master Reset, 20g Oreo.
I asked him why he did that. He said US998 20f was Nougat. That's like saying a banana is an apple. "10" is Nougat, "20" is Oreo. Plus, in my instructions I have specific download links to all requisite firmware, which he ignored.
He said he downloaded KDZ from LG-Firmwares website who told him US998 20f was Nougat -- which they didn't. But even if they did, who cares? You're following MY instructions, so use my download links. Once he downloaded actual Nougat from my download link -- hey that worked!
Also use the Dev Patched LGUP which I recommend. Some guy over the telegram thread said he was following my instructions, but used Uppercut. Of course that's going to fail. None of my instruction mention Uppercut and never will because it doesn't work on Oreo or later and conflicts with Dev Patched LGUP. I always include the specific version of Dev Patched LGUP you should be using. (The Dev for Uppercut is amazing, but it just doesn't work on our phones past Nougat. If it's NOT in the Instructions, don't use it.)
This isn't a recipe where you can substitute your own ingredients.
You need to read carefully and pay attention.
I'm happy to help -- but while some people's problems are quite preventable, once occurred may not be fixable.
Finally there is a TWRP capable of decrypting /data on android versions > nougat.
Big thanks @NeoArian
I haven't tested everything in detail as I mostly focused on decryption. If you experience issues or can confirm something working that's not green in the table down below, please share.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by TWRP
Code:
[B]Blocking checks[/B]
- [COLOR="green"]Correct screen/recovery size[/COLOR]
- [COLOR="green"]Working Touch, screen[/COLOR]
- [COLOR="green"]Backup to internal/microSD[/COLOR]
- Restore from internal/microSD
- [COLOR="green"]reboot to system[/COLOR]
- [COLOR="green"]ADB[/COLOR]
[B]Medium checks[/B]
- update.zip sideload
- [COLOR="green"]UI colors (red/blue inversions)[/COLOR]
- [COLOR="green"]Screen goes off (and on :))[/COLOR]
- F2FS/EXT4 Support, exFAT/NTFS where supported
- [COLOR="green"]all important partitions listed in mount/backup lists[/COLOR]
- backup/restore to/from external (USB-OTG) storage
- backup/restore to/from adb
- [COLOR="green"]decrypt /data[/COLOR]
- Correct date
[B]Minor checks[/B]
- MTP export
- [COLOR="green"]reboot to bootloader[/COLOR]
- [COLOR="green"]reboot to recovery[/COLOR]
- [COLOR="green"]poweroff[/COLOR]
- [COLOR="green"]battery level[/COLOR]
- [COLOR="green"]temperature[/COLOR]
- encrypted backups
- [COLOR="green"]input devices via USB (USB-OTG) - keyboard, mouse[/COLOR]
- USB mass storage export
- [COLOR="green"]set brightness[/COLOR]
- [COLOR="green"]vibrate[/COLOR]
- [COLOR="green"]screenshot[/COLOR]
Limitations
Following limitations are known:
none
Click to expand...
Click to collapse
prerequisites
For reboot to recovery from your android system (and OTA updates) your ROM needs the following patches 1, 2 and 3. Following ROM's currently support this:
AICP 14
AICP 15
LineageOS 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
For correct time inside TWRP your ROM needs the following patch. Following ROM's currently support this:
AICP 15
LineageOS 16
LineageOS 17
Click to expand...
Click to collapse
Download
SourceForge
AndroidFileHost
Click to expand...
Click to collapse
How to build
https://github.com/115ek/manifest#build-twrp
Click to expand...
Click to collapse
XDA:DevDB Information
[RECOVERY][Unofficial][amami] TWRP 3.4.0, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
115ek, NeoArian
Source Code: https://github.com/115ek/twrp_device_sony_amami
Version Information
Status: Beta
Created 2019-08-25
Last Updated 2020-08-22
Changelog
15.09.2020 3.4.0-1
again: fix non working OTA update in rare cases (rebooting to recovery and stucking there unable to install update automatically)
22.08.2020 3.4.0-0
latest TWRP changes
29.02.2020 3.3.1-0.4
display sony bootlogo at boot
show version number
remove TWRP app
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
05.09.2019 3.3.1-0.2
enable reboot to bootloader (fastboot mode) (you have to connect the phone via usb BEFORE rebooting)
25.08.2019 3.3.1-0.1
decrease size
allow decryption in any case of patchlevel value
25.08.2019 3.3.1-0
initial release
Reserved
Backup to microSD seems to be working fine (haven't restored anything yet):good:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
115ek said:
I uploaded a new build 3.3.1-0.1 with decreased size and a "more clean" way to allow /data decryption.
Furthermore I thought about getting this official.
BTW: You won't see the increased version number in TWRP. It's still 3.1.1-0
Click to expand...
Click to collapse
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
bananabytes said:
Hi, thank you for this build. I was waiting to try Pie on my z1 compact and I'm glad I did because the version of TWRP was blocking my use of encryption.
Sadly I didn't have luck installing the latest builds (the ones from 3 days ago and one week ago) on my Z1 Compact. I got this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
When trying to flash to recovery partition. The same command worked to flash back to 3.2.3 (not sure if necessary, done just in case). If there's any way you could look into these builds I'd appreciate it!
Click to expand...
Click to collapse
What command did you use?
Code:
fastboot flash recovery
or
Code:
fastboot flash FOTAKernel
Do you have the newest bootloader installed? So can you boot directly into recovery with VOL down and power pressed (with 3.2.3 version where flashing was successful)?
Or do you use the method with pressing VOL down when the LED lights up?
EDIT:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
What version of fastboot are you using?
I'm using fastboot installed from the packetmanager with
Code:
apt install fastboot
.
Code:
fastboot --version
gives fastboot version 1:8.1.0+r23-5~18.04.
This would mean 27.0.0 or 27.0.1 according to this scheme. I don't know why they are using different naming schema
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
115ek said:
What command did you use?.
Click to expand...
Click to collapse
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
115ek said:
By looking at your error code I get the feeling it has something to do with fastboot directly. libsparse is a build dependency of the fastboot binary.
...
However, I'd guess you're using an outdated version (or a very current one - but I don't think so).
Click to expand...
Click to collapse
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
bananabytes said:
I used fastboot flash recovery, with the newest bootloader. This time I got into recovery by selecting it in my older TWRP because I always get the up/down method mixed up, I have done it before it's just easier that way.
I am actually indeed using a very current version, 29.0.2 (so your second less likely guess was correct!) I'm on Manjaro/Arch so we get the bleeding edge updates unlike if you are on a Debian/Ubuntu system that's tied to a lot of different libraries and held back. This is exactly why I stopped using those distros but this is the first time I've had the problem in reverse. I don't know if this is a bug that was introduced into fastboot or what. I do see that the more recent versions have things to do with partitioning. This may be a bug to open with fastboot or to look into further with them? But if it's not a bug with them it would be good to have the build working on the latest fastboot.
Click to expand...
Click to collapse
Can you please verify that you also fail with the fastboot binary from here
It's also 29.0.2 and it works fine for me.
I have tried this version with LOS 16 and it worked well. Some things to improve
boot to fastboot is not possible
backup and restore of boot is not possible
good catch with encryption, I have give it up :good:
Micha_Btz said:
boot to fastboot is not possible
Click to expand...
Click to collapse
Well, I actually didn't know this was possible in earlier versions. However it should work now --> see the changelog
You have to connect usb cable before rebooting to bootloader, otherwise it won't work and just reboot the system.
Micha_Btz said:
backup and restore of boot is not possible
Click to expand...
Click to collapse
I can't confirm that. What exactly was the problem for you? Backing up or restoring? Did you got any errors?
Have had a look yesterday, Backup and restore of boot is possible (don't now what happends)
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
tramp20 said:
@115ek,
I have a mysterious problem with 3.3.1-0.0.and 3.3.1-0.1:
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
I tried the following several times:
1. reflash your twrp, clear recovery and flash again,
2. flash older versions: date and time was wrong even after reboot
The only way to get the correct date/time back in twrp was (at least for me) flash stock ROM with EMMA and after flashing twrp 3.2.3 my backup.
I do not want to repeat this as this is a lot of work incl. copying back the internal storage.
Click to expand...
Click to collapse
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again. And for me this works fine. However it takes some seconds (there's a wrong time at the beginning).
115ek said:
Can you try the latest version?
At first you have to set the right timezone in TWRP settings.
The time is stored in a real time clock (RTC) which runs even if the device is powered off. Setting and reading it's value is done by a kernel driver. If you set the right time in android system it gets stored in the RTC. Then, if you boot into TWRP, the time is read again.
Click to expand...
Click to collapse
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Generic question re: encrypting this device
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
tramp20 said:
Thank you. I know this all, I tried reset to default in TWRP and set TZ etc. but these two mentioned TWRP versions do not read the RTC time (AICP ROM).
All TWRP versions before were ok. I tried this several times.
I noticed this "bug" on my Z1c after a backup with your TWRP (Date from 1970 and a complete false time even after setting the TZ).
Even after flashing one of the older TWRP date/time are wrong (only in TWRP), after booting to Android date/time is correct until I boot to TWRP again.
As I wrote the way back to a correct date/time in TWRP was for me flashing stock ROM with EMMA.
Where is this "kernel driver"? In your TWRP version or in a hidden partition? Sorry I do not know much of these internals.
I assume you did not change in the newest version something regarding this problem.
I have not the time to try the last version for now
Click to expand...
Click to collapse
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering.
lm089 said:
Installed this twrp version and (unlike others) I don't see anything strange. Only thing I haven't tried so far is restoring a nandroid backup I created with this twrp release.
A few days back after I had installed this the first time Itried to encrypt my phone; after a while I received the message that encryption was completed.
Then upon reboot of the device I had to unlock it even before boot sequence had started. Aftter unlocking booting resumed and from then on everything appeared to be as before.
This surprised me a bit because on my other phone (OnePlus6 running stock OOS Pie) I have to unlock after boot sequence has completed. But OK, this may be the LOS 16 way.
Then I devided to unencrypt the phone (this is my secondary device and I only use it for playing around a bit, until I decide to sell it, maybe). Again, from my OP6 I'm used to the fact that if I remove any device locking pattern encryption is gone. But obviously not on my Z1c: after I had removed the security pattern (= set security to nothing) everything appeared to be normal. But after the next reboot all data were gone.
Question: is there a supported way to unencrypt this phone without losing any data?
If there isn't such a way: what happens to my Nandroid backups I took while the phone was encrypted? Are they still usable e.g. after I install a ROM update?
Click to expand...
Click to collapse
The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.
The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then?
Concerning your question:
What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.
115ek said:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with
Code:
adb pull /tmp/recovery.log
while your in TWRP and connected to a PC...
The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img
Click to expand...
Click to collapse
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.
I will try to get a log if I have enough time.
So the recovery.img = twrp.img or at least a part of it?
Thank you.
New update:
As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.
Download Currently only on sourceforge - android filehost is buggy at the moment...
19.09.2019 3.3.1-0.3
fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)
Edit:
As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag
Code:
-D_FILE_OFFSET_BITS=64
doesn't work as intended on my setup. Maybe I missed something.
tramp20 said:
@115ek,
I used all twrp versions before without problems and now your twrp did not show the correct date (1970-xx-xx) and time (7-8 hours back).
Click to expand...
Click to collapse
Have the same time/date problem with twrp-3.3.1-0.3-amami.img
recovery.log >> https://pastebin.com/rBdHAmz2
Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.
Hey guys, because there is unfortunately no fully working TWRP yet and lack of magisk patched boot.img for each rom, i decided to make a script to make things easier.
This script is based on the post https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100, which is based on thread [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
What does it do?
The script pull the boot image from your actual system and copy it to your PC.
Then you have to copy the boot image back to your device and patch it with Magisk Manager.
To prevent problems and bootloops the script will boot the patched image first, if anything went well the script will flash it subsequently.
Requirements:
unlocked bootloader
ADB/Fastboot installed
latest TWRP from here
Make sure the .bat and twrp image are in your adb/fastboot folder!!
How to use?
Download the .bat file, place it into your ADB/Fastboot directory and start it.
If windows shows a warning, then just click on "more informations" and then "run anyway".
If you trust me, dont trust the internet and check hash sum MD5 after downloading the file with:
Code:
CertUtil -hashfile <filename> MD5
MD5 checksum is: 303f338c32841ac752d24647ec6ede14
If you dont trust me there are several options:
Use the guide from https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100 and do it yourself
or use any guide from [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
check the code on github here
If you run into problems/errors:
Be sure the .bat file is located where adb.exe and fastboot.exe is
If you need urgent root, than follow the guide mentioned above
Be patient, i try to fix the problem as soon as possible
Only tested on Oneplus 7T with OxygenOS
Download from: google drive or from github
Credits:
topjohnwu - for Magisk
mauronofrio - for TWRP
gpz1100 - for his guide
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
no, but you can root again with the tool
slipnslider said:
Will I still be rooted if I take an OTA update?
Click to expand...
Click to collapse
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
oh sorry i missed the second question,
the script should boot your phone into twrp recovery, where it get's adb access to pull the boot.img. Do you named the twrp img to TWRP.img?
Yeah it was named TWRP.img but I actually had another problem going on with my device that I believe was causing this. Got it all fixed using that back to root/unbrick Msm.exe tool that someone else posted
Worked flawlessly, got a little bit lost when the prompt about magisk came out then realised that I needed to copy files over, patch on the phone with the Magisk Manager app then copy files over again.
But once that's sorted, it worked with no issues
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Radicalcokemonkey23 said:
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Click to expand...
Click to collapse
Flashing boot.img won't wipe your data. But unlocking the bootloader will reset your phone.
Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
I didn't want to update because I would loose root but I'll give your advice a go.
At 71% it says something went wrong.
imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
i think ur phone disconnect during the process, maybe try another usb cable or usb port for the process
Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
Yes, just make sure you install into INACTIVE slot after OTA, if you havent rebooted yet.
I believe one problem exists with twrp (possibly depending on the version) ... when the script tries to download the stock image, TWRP wants confirmation for write access. Unless I confirm that, the download doesn't succeed. Once confirmed, the same adb line in the script entered manually then works ...
I bought a phone advertised as factory unlocked. It has no carrier branding. It turns out to be a model HD1907, which in Wikipedia shows as T-Mobile.
I installed the OnePlus USB drivers from the phone.
I used the original cable.
In Developer Options I had set Advanced Reboot on and USB Debugging on. I tried OEM Unlocking on and off just to try.
I am getting a failure at the boot to TWRP step. The fastboot error, which I tried manually as well, is:
FAILED (remote: 'boot is not allowed in Lock State')
On the fastboot screen I do see the message:
DEVICE STATE - locked
Am I going to need to go through a bootloader unlocking process like this?
Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.*** A note for the Moderators: I am...
forum.xda-developers.com
It's a nicely done script, by the way.
I'm sorry but I'm really newbie, so please can you tell me how to activate adb access?
imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
I'm stuck in the same problem, I changed the slot but nothing changes...