Related
I'm going to try and encapsulate everything that's going on into this initial thread but I'm sure I'll miss something.
Basically, I undertook to root my phone last night. I followed all the steps in the root thread, and I thought it worked, but then when I went to the root checker to see if I was successful. The test couldn't get a result the first time, and then failed the second time. I've known my phone to be a little temperamental when it comes to stuff like that, so I shrugged it off. Then, everything started running with so much lag that my only option was a reboot. It came back up just fine, but then, apps wouldn't open anymore. Since a reboot fixes everything, I rebooted AGAIN... except no I didn't, because I couldn't move past the white splash screen.
After some time hacking around with TWRP, system restoring my phone and the like, I finally managed to actually load the OS again. I think the phone was rooted at that time, but I don't know for sure, because this was the drawback: I couldn't install ANYTHING. My idea is that the system was rebooted into read-only mode. I tried everything I could think of to revert the system to rewriteable again, but nothing ever panned out. There was just one thing that stood out to me: "Your phone worked properly when it wasn't rooted." So, I got the brilliant idea to use SuperSU to unroot my phone. Stupid, stupid move, because now my phone can't boot past the white splash screen again. As a last ditch effort, I decided that it was time to flash the stock system to the phone. Except I probably did it wrong.
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery system.img
Code:
fastboot flash recovery boot.img
And where I stand now is that my phone will not boot past the white splash screen, and I can no longer access either TWRP or Fastboot.
Is my phone fooked, or can anyone save this?
#1 You can't flash system image via fastboot - it's semi-locked.
#2 You can't use 'flash recovery' command for boot and system images.
#3 For restoring your phone use SP Flash Tool - there's a thread in the General section called 'How to unbrick'.
Try it and let us know.
Cheers
Yeah, I realized afterward that if I were trying to flash the image of the system, I should not have used the "flash recovery" command because I disabled access to the other recoveries, lol. I have tried to use the SP Flash Tool in the past few days, but I could never get any download progress. I think my computer isn't making the VCOM drivers accessible to be able to flash those things to my phone. Do you have any advice on that end? Because I have seen that thread and tried those steps but I'm just not successful.
You should also read all replies to this thread - there are people who solved their problems with SPFT in their own way, that's how I've revived my phone from hardbrick.
Make sure you're phone is disconnected when you start the flash. AFTER you hit the download button in SPFT... then connect your phone...
Fantastic advice from both of you. I'm ready to revive my phone!
Okay, I think I'm making good progress on recovering my phone. I have managed to get back the stock recovery onto my phone, which I then used to install TWRP. But I'm not out of the woods yet. I used fastboot to flash the boot image onto my phone also, but when it came to the system image, I'm having a lot of trouble. The only ROM I can find for the Blu Pure XL is a 7z file. Now, I know how those work, I have 7zip and I extracted it for the system image. When fastboot was available to me, I couldn't push the system image to the phone. Now that I have TWRP and I have no more access to fastboot, I've tried to load the system file onto my phone through my SD card in four different ways:
As a .img file
As a .7z file
As a .zip file that I created by zipping up the image file
As a .zip file that was .7z, but I changed the extension
None of those methods worked. The Blu development thread doesn't point me to a zipped ROM file. One person there said that they had a backup of their files and provided a link, but those images seem to have been removed.
I'm so close, I can see this phone working again in the near future, I just need your help to get me there. Please! :'(
Edit: Also, keep in mind, I'm dumb. I don't think I really did anything super wrong, but I may be missing something ultra obvious. So if you could just keep your answers dumb for me, it would help even more.
I would stop trying to use all of the methods you are using I believe you are slightly confused by them at this time..
At this point what you have done with the random image flashing is get damaged partitions..
Get SPFT. Turn off you phone completely.
Download the full Scatter file for you phone. (put it aside).
Download a file called ALL MTK driver install. ( or something to that effect). Search for it on Google. You will find it. Run it and then reboot your PC completely.. (if you have windows 8 or higher look online on how to install unsigned drivers) --THIS IS THR BIGGEST PROBLEM PEOPLE HAVE--
Extract your full downloaded scatter image to a directory.. (you can download the Gionee E8 image if you want) it is what I am running on my Blu..
Run SPFD read the thread that they pointed out to you. Find the scatter and point SPFD.. Once it is loaded on the program UNCHECK the PRELOADER check box.. (if not you can cause problems) ..
click download and after 10 seconds or so plug in (you completely powered off) phone into the computer..
.Then wait..... and wait... It will tell you it's progress..
Keep trying it, it WILL work.. and ALWAYS unchecked preloaded when flashing with spdf...
I did follow all the steps in the original guide, and I followed the steps that you gave me too, down to using the advanced device manager to remove any MediaTek drivers from the computer and restarting the computer with disabling the driver signature verification, but when I click download, wait, and plug my phone into the computer, just nothing happens. The computer says it's an unrecognized device, and the download never progresses.
I see also that you said keep trying, but every time I try the SPFT, it never sends anything to my phone. And I don't even know how to tell if I'm missing some important step.
OK this happens sometimes. plug the phone in with device manager open.. plug the phone in when it is off..
When it says unrecognized device double click on it really fast( it will disappear fast, try it a couple of times if you don't get it the first time) then hit update driver.. point it to the MTK drivers folder (unzip the MTK drivers folder). It will pick the proper driver. on some computers it loads up so fast it has no time to recognize the driver..
After you load the drivers power off your phone again and follow the instruction I gave.. After you do this once it will load the drivers right after this..
When I double click on the unrecognized device button, it just brings up a notification that my device wasn't recognized because it malfunctioned. I don't have an option to install any drivers.
My problem is finally solved. After starting up SPFT and clicking download, I held Vol - and Power and then connected it, and that pushed the download forward. I got to the Blu animation screen, and it stayed up FOREVER, but then the next time I looked over, it was on the initial setup screen. Good as new.
Thank you guys for all your help. This forum really is an amazing place.
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal
zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?
zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?
zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\
hi,
this is a guide for real helpless people, that got a V20 H918 T-Mobile out of the box and have no idea
what to do, to get TWRP and root. and since on this phone its a REAL hard odyssee if youre not a pro,
and you dont want to spend days and weeks to pick up countless small puzzlepieces to finally get all together up and running, i decided to write this guide. im no pro myself, but with countless hours of reading and try and error, misery, headaches and brainpain, i managed to get this thing running all right with working downloadmode,
newest TWRP-version and 20H oreo 8.0
so far, everything seems working good. ill play around with this version and if i encounter some crap, i will edit this guide later. sadly most "newbie-guides" here, are from pros for advanced users with decent knowledge. so when u start from zero, you dont understand half of what is written. thats why i will keep this guide as simple as possible, with some side explanations. its a lot to read and a lot to do, but this way works!
what we have before starting:
a V20 H918 t-mobile 20H oreo 8.0 with bootloader locked. simply a crippled standard phone.
what we will have after this guide:
a V20 H918 t-mobile 20H oreo 8.0 rooted, with unlocked bootloader, working downloadmode,
and newest TWRP-version.
with twrp u can backup your whole system "as it is", means u fukk up your phone, simply go to twrp-recovery, restore your backup and you have your phone up and running 100% as before all went down the drain. simply and easy. just like a new installation of win10, but in 5 minutes. u can flash custom roms, kernels etc., install all kind of stuff, no need to pay for apps anymore, get rid of obnoxious bloatware, just 100% freedom and the full potential with the V20 (which is the last phone of its kind with exchangable battery, which is why i got myself 3pcs of it )
sidenote: get yourself some extra protection foils so u can change from time to time.
also get yourself 1 or 2 10000mah powerbatterys from aliexpress (perfine) with protective rubbercase, of course, they dont have the printed-on mah, but at least a considerable amount, so that your phone will last at least 3-6 days. my V10 lastet 11 days normal usage with zerolemon powerbattery. unfortunately, these retards refuse to send to europe, and as far as i know, theyre not producing for LG phones anymore, so aliexpress/perfine is whats left.
the rubbercase gives the phone a superior protection, adds a serious amount of weight and will stick in your hand like glue. it is by far less likely to drop out of your hand like these glass-phones for imbeciles. and if it drops, the rubbercase grants excellent protection. my V10 dropped countless times, still working perfect.
but lets get to the guide now.
at first, we will unlock the bootloader. without it, you wont be able to do anything.
unfortunately, LG produces great phones (with great audio!) but terrorizes the users with their strict anti-root attitude. it seems it gets harder everytime to root and unlock the bootloader. i remember back in the days old samsung devices, had been rooted in no time. this one here cost me about 2 weeks.
on this phone, u simply cant hook it up to the pc, and unlock the bootloader with adb. it will be recognized by the pc, but as soon as u enter fastboot, nothing will happen, no command works.
the solution is a FWUL (forget windows use linux) usb-bootstick, with that u boot your
pc into a custom linux (i think) only here u have full access to your phone via fastboot and can unlock the bootloader in no time. it will not work on win10 !
- first, get rufus, a win10 tool, with that u can create boot-usb-sticks.
https://rufus.akeo.ie/
- then get the linux FWUL image (only 15GB version is still up)
https://androidfilehost.com/?w=files&flid=214529
- unzip the linux image to your c drive or your desktop.
- start rufus and select your usb-stick (it should be 30gb+ in size)
be carefull not to chose any other drive or stick (it will get erased completely), better double check.
- select the image you just unziped. (i use 7zip for unzipping)
- leave all other options as they are, press start. when dialog-box pops up, chose DD-mode !
- now waste some time, as it takes a long time to create the bootstick (in my case about 30min)
- when the stick is ready, in my case it couldnt be recognized anymore in win10, its just a raw-drive, that cant be
opened. thats allright. dont worry
- now close down all applications running and insert the created bootstick. (at this time u might consider using a
separate laptop, so you can follow this guide here at pc and use the laptop with linux running, thats what i did)
restart your pc, hit F2 or F8 oder DEL or whatever to enter bios.
select the created stick as bootpriority nr1. so that the system will use this stick as
the first bootmedium to boot from.
- u get to a screen with 9 bootoptions to chose from. chose the first one. it should now boot into linux.
when password request pops up, enter: linux
- u reach the "desktop"
connect your LG V20 H918 20H via usb-c to the pc, which has linux running, make sure that
developer options are unlocked, OEM-unlock and USB-debugging is enabled and u chose picture transfer protocol
(PTP) as transfer-protocol (also in developer options). if PTP doesnt work, try media transfer protocol.
watch your V20, at some point it will ask for confirmation of connection , click OK.
in linux, click on the up-arrow in the most downleft corner and chose "terminal emulator", which is
a pendant to windows shell/command-line.
- here you can execute the adb commands.
first, check if your V20 has been recognized by your pc with linux running.
type: adb devices
it should appear a message like:
* daemon started successfully *
LGH9182bfblablabla device
that means, that your V20 has been recognized correctly. now you can reboot it in fastboot mode.
type: adb reboot bootloader
your V20 screen goes black and seconds after, it restarts in bootloader mode ready for unlocking.
you might get a red warning that your warranty is void if bootloader is unlocked. cool.
type: fastboot oem unlock
wait for response, your bootloader is now unlocked.
u can check by typing: fastboot getvar unlocked
it should say: yes.
the bootloader is now unlocked.
now we will replace the standard recovery with twrp on the phone.
this step will be a little confusing and complicate, just follow the steps, and it will work.
since we cant flash twrp with adb, we have to use the linux bootstick again.
but before, we have to downgrade the 20H version to 10P, bcuz the next stepp will not work with 20H !
so you get the following:
DOWNLOAD H91810P KDZ FILE
https://androidfilehost.com/?w=files&flid=282709
after that, download LGUP (the LG tool for downgrading from 20H to 10P)
and uppercut (dont know what uppercut is for, i just used it instead of running LGUP directly and it worked. its supposed to recognize the phone/driver automatically)
http://downloads.codefi.re/autoprime...sh_Tools/LGUP/
and download the recent LG-usb drivers.
http://tool.cdn.gdms.lge.com/dn/down...=UW00120120425
install LGUP, uppercut and usb-drivers.
connect ur phone to pc in download mode.
turn of phone, press and hold vol.UP button and connect usb cable, small message appears, phone is now in download-mode and waiting.
now run uppercut and hope, that ur phone will be recognized. if not, think about, what kind of restrictions u did to ur system, like OnO-shutup or xpantispy (both great programs to keep win10 from calling home to scum gates) or whatever. in my case, it ONLY worked, after i reset the OnOshutup settings to recommended. so the phone get recognized correctly in LGUP (if not, try laptop or different pc), select upgrade and select the downloaded 10p KDZ file. press start or go, and wait until the procedure is finished.
now your phone is downgraded to 10p.
now we go back to linux, we connect the phone in downloadmode with the pc/laptop where linux is running,
(turn phone off, hold volUP, connect usb-c-cable with linux-pc/laptop, phone will start in download-mode.)
make sure, your laptop/pc has internetaccess.
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode. why? i dont know, thats the way it worked for me.
we dont want twrp onto downloadmode, since twrp is a recovery. so the next step is, to flash the newest twrp version for H918 to recovery. at first, we will gather all neccessary downloads, after that, we will flash them one by one. that way, you dont have to get your micro-sd card out of your phone again and again. we put all together on the card, put the card in your phone and we are almost done. for now, have your micro-sdcard connected
with your pc and download the following:
twrp-3.4.0-1-h918.img
from
https://dl.twrp.me/h918/twrp-3.4.0-1-h918.img.html
and put this .img file on micro-sd card.
then download (and put on sd-card):
MAGISK ZIP DOWNLOAD (for root)
https://github.com/topjohnwu/Magisk/...gisk-v16.0.zip
then download original 20H firmware(and put on sd-card)
H918 20H
https://androidfilehost.com/?fid=11410963190603864639
you remember, we have now twrp on downloadmode
for restoring download-mode, download (keep on desktop or c):
H91820h_00_1115.kdz
https://lg-firmwares.com/downloads-file/17076/H91820h_00_1115
then download the firmware extractor:
https://forum.xda-developers.com/attachment.php?attachmentid=3975633&d=1482337024
ok, lets see what we have now:
we have the phone bootloader unlocked and twrp on downloadmode. we can access twrp when we start the phone in downloadmode (hold volUP, and connect usbcable, phone will start now in twrp.)
we dont want twrp on downloadmode, we want twrp as recovery. and we want to restore the original downloadmode. for that we do the following:
unfortunately, the neccessary file for flashing orignal downloadmode is not online anymore, so we have to extract it from the 20H firmware with the firmware extractor (thanks to logical gamer for his guide)
https://forum.xda-developers.com/v20/how-to/guide-h918-restore-laf-partition-t3804728
Extract WindowsLGFirmwareExtract vx.x.x.x. to your desktop, and open it up (preferably in it's own folder).
u might have to install framework 3.5 for it to run.
Select Open across from KDZ/TOT file, and browse to your KDZ (H91820h_00_1115.kdz)
you download previously and double click.
After it loads the kdz check H91820h00.dz, and click Extract KDZ.
Close and re open the program this time Click open across from DZ File in the folder where you placed WindowsLGFirmwareExtract you should see a file called H91820h00.dz Double click to open it.
Check laf_6.bin then click Extract DZ.
put this laf_6.bin on your micro-sdcard. thats your original downloadmode we will flash now.
ok, now we have our micro-sdcard with twrp, magisk, laf_6.bin and H91820h.zip.
put this mirco-sdcard in your phone. start the phone in downloadmode.
it will start in an older twrp-version. in twrp, go to install and select install img
select the twrp 3.4.0.1. img and on the following screen select "recovery"
swipe
this will flash the 3.4.0.1 version of twrp onto recovery.
then go to reboot into recovery. it will now boot into the newly flashed recovery.
then go to wipe, advanced, and select everything EXCEPT micro-sdcard!
this will totally wipe your phone (except twrp), so u can flash the 20H firmware onto a clean phone.
then, go to install, select H91820h.zip. this will flash your original oreo 8.0 firmware.
after that, go to reboot into recovery.
go to install, select magisk. install.
this will root your phone.
after that, reboot into recovery, go to install, select install img, select the laf_6.bin, and select "download"
now the original downloadmode has been restored.
now you can reboot into system, your phone will start as on day1, with new twrp on recovery and root.
i did a complete backup in twrp, so i can get back to a day0 clean install whenever needed. i will do a second backup with twrp with all the stuff installed and working ok and place this on my sd-card. so when things go bad, i always can go back to this state in no time.
congrats, your done. and me too . gonna get a cold one now.
hope this guide will help someone. in case, just drop a like/thanks/or just a short note.
its a long guide, and im no pro, if i made some mistake pls. tell here and i will correct.
thx to all the pro-guys for helping the helpless.
Hi
Im on v20 H918 firmware 10p with bootloader unlocked.
I tried with dirty cow but not works with lafsploit i have a Problem with rufus for create a bootable Linux.
Pendrive is 32 GB i followed your setting but my PC boot only in windows 7.
I succesfully unlocked a h990ds with dirty santa but for this model is not supported.
Can you help me
hi
i tried with dirtycow also, didnt work.
thats why i eventually came to the method i described.
teling by your short description, your next step would be to create a bootable linux-usb-stick, and to find a pc where it will boot correctly. the stick didnt boot on my main pc ( i dont know why, it just canceled with an error),
thats why i had to use the laptop where it worked.
Thanks for the guide man! Very funny and fun to read. I can't wait to turn mine into a 4-day brick like yours. #lastphonewithbatteryrevolution
Sadly I got the dreaded encrypted error at the end though when booting. Everything else worked fine.
After the encrypted error though I formatted and flashed LineageOS 17.1 and then magisk and still keep getting error 1. Even tried Lineage recovery and still same. I think maybe a problem with Magisk 16 itself.
Anyway it works fine just no root.
Edit: Had to flash Magisk 21 and it worked
Thanks for this tutorial. I was able to get my V20 rooted with minimal trouble. The only major trouble was finding a computer that will fully boot into Linux and the only minor issue was locating the UPPERCUT but I was able to find it. Link below.
It's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
UPPERCUT link: UPPERCUT: Add Any LG Device to LGUP for TOT/KDZ Flashing (G4|G5|G6|V10|V20|MORE???) | XDA Developers Forums (xda-developers.com)
MAGISK link: Releases · topjohnwu/Magisk · GitHub
cool, glad this guide helped at least a little bit. my v20 still works great, no issues so far. as a side phone for unwanted persons, i still use my v10 with powerakku and rubbercase "brickstyle" every time i hold a regular phone from other people, it feels weird since these phones weigh like nothing, and i have to focus not to slip it out of my hand. i love my bricks
and by now, about 4 month later, reading this whole guide, to me its still strange and hard to follow. there is no way to get through this without reading everything possible about it and become familiar with all the technical terms.
I have a h918 with an unlocked bootloader and it's downgraded to 10p. The shell script fails everytime to a hash check. I've run it 4 separate times with the hashes being the same every time. So it looks like the file has been updated but the hash hasn't.
I'm coming late to the game and it seems most of the guides are out of date. I'd appreciate any help I can get.
Update: It works fine. This is by far the easiest guide to follow that I've found. Many thanks! I did have to follow xstahsie's tip.
xstahsieIt's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
I followed the guide after I rooted and installed Lineage OS 18.1. I had to remove LineageOS because it was bad with response, couldn't see hidden wifi, and just ran hot. So I followed your guide and I am in a logo bootloop and get the reminder to lock the bootloader everytime it starts. Any suggestions for getting past the bootloop?
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
memnon79 said:
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
Click to expand...
Click to collapse
You're stuck with it, it's just the way it will be from now on.
memnon79 said:
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
Click to expand...
Click to collapse
I don't remember seeing that. I probably didn't care if it did show up since it was a new install from scratch anyway.
Does encrypting the phone work after following this guide?
hey there, cant help u with the encryption thing cuz thats far beyond my knowledge. some weeks ago my phone dropped, and a tiny crack on the edge appeared. what i didnt know was that this crack is the beginning of the end of the V20. heres the story short: small crack over time leads to a bigger crack, bigger crack multiplies and u have some more cracks covering the whole screen. also the screen can pop off and hanging loose a little. in my case 4-6 weeks and i have to get out phone 2/3 which i am setting up using this guide now. fortunately i left myself a huge pyle of information on how to do this when starting at 0. over time u forget EVERYTHING u have done, so having these infos is hammering.
lucky me did i save my internal memory of phone 1/3 bcuz 30min later the screen was totally fuqqed up, no access no chance of backupping internal memory.
so heres my recommendation:
DONT drop your phone. even in my case with rubber battery case from aliexpress
(perfine "10000"mah) a 50cm drop cracked the edge of the screen. if that happens, backup your internal memory !!! (just do this on a regular base)
when ur screen gets damaged and u cant enter information or cant see anything anymore on the screen ur internal data is lost. so always have ur internal memory backuped!
and great job LG for producing such a huge pyle of ****. one small drop, screen cracked, bravo, last time i ever bought anything from lg. my V10 dropped like a 1000times, nothing, still up and running. v20, drop, 6weeks later, dead. thanks LG the customers all over the world couldnt wait to use these bull**** crackable glass-screens. great job, -1 customer.
I've tried this on two different computers with two different cables in every USB port on the machines but can't get by the Windows portion. I am using UPPERCUT as the windows box/LGUP reports no device found without it...
Of course UPPERCUT drives windows security mad as it's reported as doing bad things but as I'm using an extra win laptop that will be wiped I disable all of that....
I have three different sourced KDZ files as the one linked wasn't initially reporting any mirrors. Eventually a mirror did pop up for it but by then I had downloaded two others -- all were the same size and one of the three reported from LGUP was bad. Every attempt with the other two failed. Invalid Command response came up a few times... sometimes it just failed at around 80+ percent from the PC side which was 99% on the phone's downloader mode progress bar.
It's very frustrating.... I would like to blame windows but there seem to me plenty here with success... any other ideas?
Also... since it got so far, rebooting at this point just goes to the download mode so I might be hosed... I can force it to the fastboot mode and it is still unlocked so I've been trying to install TWRP onto recovery using the linux/android machine but when I type
fastboot flash recovery twrp.img from the directory where twrp was downloaded I get this:
sending recovery --- okay
writing recovery --- failed remote: unknown command
So... any thoughts?
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
dikkbutt said:
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
Click to expand...
Click to collapse
The phone is recognized by the PC, no problem. I do have to use UPPERCUT to get LGUP to recognize it though. The step I'm stuck at is applying the downgrade. It gets to various percentages of done-ness and fails. It got far enough that now my only options on the phone are Download mode or fastboot mode. Problem is, I can't seem to get anything to push to recovery so I assume that it's still not properly downgraded.
I've tried a few different cables and keep in mind the cable I used in the linux adb bootloader step worked fine. I don't entirely know what difference there is between a charging and data cable but I do know the main differences in the steps are a> Windows and b> size of transfer.
weird. since im no pro myself, my ideas are limited on this one. there might be some kind of loose contact at the charging port,
that when the phone is moved just a little it looses connection for a second and reconnects again, had that in the past, so try not to touch the phone at all. did u use the 10p kdz file mentioned before? did u make sure it has been downloaded correctly?
if an error occured and there are some % missing... its like faulty ram, hard to detect.
assuming, u did or did not downgrade to 10p, did u try to continue with the linux-step? ---->
---------------------------
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode
-----------------------------
maybe uppercut/lgup displayed an error message for no reason, and the downgrade itself went through without a problem in the background.
pcs sometimes do weird things.
if nothing works, try setting up win10 and try on a virgin system. in my case, OnOshutup prevented win10 from recognizing the phone,
or try using a 3rd pc from a friend.
i was able to setup my phone 2/3 using this guide in 30min, no problems at all. (i hope i wrote down, how i solved that simlock issue.....)
no matter what causes the problemin ur case , id be interested to hear what it was.
Thanks! Rooted and Unlocked thanks to this guide!
I tried following other guides using UPPERCUT and it fails to downgrade due to Anti Roll Back. How does this relate to this guide since the last thing I want is for (by design) for it to brick the phone. I have yet to find anything specific saying an unlocked bootloader will bypass the anti rollback check.
Hi As a noob does this keep VoLTE? I have followed this guide and backgrade to 10p was perfect! VoLTE working on a phone that was "new" from china. VoLTE did not work on the 20p rom it had. Also does anyone prefer Phoenix591's h918-20g-prerooted rom to the stock one? I have read a lot but am somewhat confused by varying instruction threads. I want to use this as a daily driver. Thanks
If I'd prefer not to purchase a new phone, is there much risk a rootkit is installed? Or, is this certainly random device corruption that doesn't seem to be harming anything?
Is there anything I can do to fix the problem? (Yes, I could turn dm-verity off through adb, but that hides the error without fixing it.)
TL;DR
I have an Asus Zenfone V Verizon edition, which is the V520KL A006.
When I was using my phone a few days ago, it suddenly rebooted and since then shows:
Your device is corrupt. It can't be
trusted and may not work properly.
Visit this link on another device:
g.co/ABH
If power key is not pressed:
Your device will poweroff in 30 seconds
Click to expand...
Click to collapse
Fastboot shows:
TARGET PROJECT : V520KL
IMAGE VERSION : V5.6.0
BUILD VARIANT : USER
SECURE BOOT : enabled
DEVICE STATE : locked
Software status : Official
Click to expand...
Click to collapse
After a few days, I finally tried the power button, and it boots up just fine, and seems perfectly stable. I performed complete backups, and for what it's worth, I ran a bunch of droid virus/malware/rootkit scanners, and they found nothing. (Obviously, a good rootkit will hide itself.)
I eventually did a factory reset. This went well, but the red error message remains. So, I believe the corruption must be in a partition that a reset doesn't replace.
MORE DETAILS
I've never unlocked, rooted, or installed a custom ROM onto this phone. The only "beyond typical user" thing I'd previously done is to install adb sourced directly from Google, to be able to run Genymobile's scrcpy, which is an extremely fast open source program that allows me to remotely control my phone from my linux PC, via USB or wireless. I've been using this for many months without any issues.
This appears to mean dm-verity is detecting corruption, and is the "red" version of it which many have described as the death of their device. I believe this means the phone is able to verify the signature on the bootloader and it's able to verify the signature on the kernel, but that the kernel is finding an invalid block(s) on one of the many partitions being read right at turning on (detected because the hash for the block is not as expected.) When this happens, an I/O error is given indicating the block cannot be read.
I have been quite concerned if this might indicate a rootkit had been installed. I haven't done anything that I would suspect could let one in. After spending a lot of time learning about adb, fastboot, TWRP, and having the ultimate goal of discovering which partition has an unexpected hash, determining if this meant a rootkit or file corruption, and fixing the error, I've hit many brick walls.
For a day or two, I avoided seeing if the power button would allow it to boot, because if there was a rootkit, I didn't want it to run. I was disappointed to learn that through fastboot (specifically, I mean the fastboot PC program that connects to the droid when in fastboot mode), there is no way to do something like a full bitwise image of the internal storage, and analyze the situation in linux. Or, any type of backup whatsoever. I was frustrated to learn from another XDA thread about a lot of problems others have had rooting and/or installing TWRP on this device. I was frustrated to see there is no prebuilt version of TWRP for my device. (There is an image for the Asus ZenFone 5z 2018 ZS620KL which is very different than my Zenfone V520KL V.)
I realized with my particular device, I think, the only way I was going to take any next step required hitting the power button. (As I mentioned way above, that's when I found it appears to work fine, and I eventually did a factory reset.)
I attempted using the TWRP recovery.img posted by game #1 in that XDA thread about my device, but like he encountered, fastboot boot recovery.img doesn't work, and just reboots instead.
Without being able to extract the original recovery.img, I'm not sure that I'm willing to install his and see if it works for me. I was frustrated to find there appears to be no way to extract the original recovery.img without first having root access. All non-root methods I later found to do this didn't work. Notably, su can't run anymore through adb, and adb root can't run with a user build.
I've looked a bit at custom compiling TWRP myself, but haven't done that yet. In part, because if my version doesn't work through fastboot boot recovery.img, I'd have the same concern about overwriting the original one before getting some feedback here. Also in part, because I haven't looked enough to find how someone goes about making a BoardConfig.mk and the device tree from scratch.
Hey. I tried installing TRWP on my device, Asus Zenfone 5Z (ZS620KL) but I also got the same message. "This phone is corrupted and cannot be trusted." It also said it won't boot. Now I am stuck in Fastboot mode.
I tried installing a stock rom. Downloaded the firmware. i even downloaded python so I can extract the payload.bin file. Followed the steps but still to no avail.
Is there anyone who could help me?
If you could attach the files that I would be needing, that would be a great help.
Thanks.
This restore process is intended for the AT&T V60 (lmv600am) model and will WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to original factory state for the AT&T v60 v20q build (a11). I’ve dumped all the required partitions from a new replacement phone sent to me by LG. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently unable to boot or who just can’t access AT&T ota services and wishes to upgrade their lmv600am to a newer a11 build. I have only tried this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from a Android 10 rom but I haven’t tried it.
This process will not fix your erased or damage imei number problem.
Steps
Download “Lmv600am v20q Restore Partitions.7z” file from ??? and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.
try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA
Why super.bin so big? 20GB stucking at flashing super every time
peterwode said:
try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA
Click to expand...
Click to collapse
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.
peterwode said:
Why super.bin so big? 20GB stucking at flashing super every time
Click to expand...
Click to collapse
The size of the super.bin (partitions system_a and system_b) is what it is. It's not like you have a choice. Hopefully, you do realize you're restoring both sides of the phone, slot a/slot b.
hooutoo said:
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.
Click to expand...
Click to collapse
Everything is changed, but the problem is the same, just stucked, progress no move forward, no error message , is the configuaration setting's problem? I am using the same configuaration with the crossflash guide
Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help
peterwode said:
Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help
Click to expand...
Click to collapse
You're welcome.
sorry for my mistake, not update , it is downgrade to 2.0.2.3, with 2.0.3.5 showing zero disk reading of qfil progress in the task manager, with 2.0.2.3 you can see qfil reading data from disk from computer , i don't know if it is bug or just a showing problem.
report one issue, cann't boot when changed to slot_a
did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT
chamilun said:
did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT
Click to expand...
Click to collapse
If you're seeing any boot logo and then getting stuck it usually means that the phone is trying to get to userdata. This restore does not include userdata for obvious reasons. My guess is you needs to reformat/wipe userdata.
The easiest way is probably by entering restore mode and selecting "reset to factory" which both reformats and wipes userdata.
As for the cricket logo, no telling where that's coming from or where your phone's been. But as per the Op description, these are 100% AT&T a11 v20q partitions.
phone wont get into the android boot screen for wiping cache/userdata/etc. kinda odd...
something tells me I need to write something additional. because my ATT model was crossflashed to the EU firmware
to bypass the fingerprint bug. however, they are shutting off 3G networks on the 22nd so cant keep using.
anyone else have any idea what I need to do?
Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.
hooutoo said:
eng abl img
Click to expand...
Click to collapse
hooutoo said:
Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.
Click to expand...
Click to collapse
all done. loaded eng abl. erased userdata in fastboot. still is on cricket startup screen and just stays there booting forever
does yours say "cricket wireless" when booting? so odd how this thing is behaving
got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!
Did you follow the steps, recovery mode and factory reset? Did it complete?
chamilun said:
got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!
Click to expand...
Click to collapse
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.
hooutoo said:
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.
Click to expand...
Click to collapse
everything worked but something is odd. its showing as cricket boot up, LG in settings. not ATT. and the NT error.
also the hidden code menu isnt working.
somehow Ive got a frankenstein phone now. was a pure ATT phone before I crossflashed. somehow I need to figure out
what to write to the phone to get proper version back. I do have the old backup. just need to figure out how we
did the crossflashing and kind of undo