Related
This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.
thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...
thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.
I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.
this is great info to have. great work.
???
has anyone actually tried this? because my pc dosent recognize phone when i try
bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first
??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks
i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process
I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.
theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.
Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App
I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx
If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App
Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.
SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
adrunkenmess1 said:
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
MrSteelX said:
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
Click to expand...
Click to collapse
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
adrunkenmess1 said:
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
Click to expand...
Click to collapse
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
MrSteelX said:
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
Click to expand...
Click to collapse
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
adrunkenmess1 said:
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Click to expand...
Click to collapse
amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I was able to get it to flash successfully. I used the files from the tmobile to international conversion since it required a hacked MSM tool. I'm a complete Noob at phone flashing and really spent a LOT of time reading tonight to figure it out. Phone flashed successfully but said the battery was now too low to turn on. At least it says something!
I'm charging it up now and hopefully it works after this!
amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I use a USB 3.0 and USB c port on my computer and no issues
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
jamescable said:
I use a USB 3.0 and USB c port on my computer and no issues
Click to expand...
Click to collapse
Really, I couldn't get the phone to come up on the MSM tool in the Qualcomm mode on USB 3 port. But when I connected the cable to the USB port, it appeared there.
adrunkenmess1 said:
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
Click to expand...
Click to collapse
MSM phone, unlock bootloader and flash twrp. Use twrp to flash system update and see if it works
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
Hello everyone.
I need some help i think. I bought a used OP7 Pro to try my hands at installing crDroid and changing this over to my work phone without any Google installed. I have successfully flashed ROM's on about 6-7 different phones successfully before - but not this time it seems.
I think I have introduced corrupted boot partitions (both a and b) and the phone is now barely alive.
I have it plugged in on the charger, but when trying to turn it on (using volume up and power) it says that power is low and that I should leave it plugged inn a while before booting up. Doing so leaves the phone to boot, but after the initial "warning" screen about the unlocked bootloader the phone dies and I have to try to turn it on again.
To make matters worse - i do not have a Windows machine to use to try to fix it. My personal one is Linux based (I used this for the failed flash attampt). I planned on following this guide:
How to Unbrick or Restore Back to Stock ROM on all OnePlus using this Tool
From this comprehensive post, you could unbrick your OnePlus device and restore it to the Stock ROM. We will be using the MSM Download Tool for the said
www.getdroidtips.com
This required a Windows machine in Test mode.
Any other tips or guide for me to follow that you recommened?
Thank you very much!
Condition
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SolomonMT said:
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
View attachment 5731647
Click to expand...
Click to collapse
You seem to have a driver issue. Install libusb and try again. The battery should not be required for any of the steps as long as the usb is plugged in properly.
OK, it got unbricked, Im guessing Ill brick it again once I try installing ArrowOS for the second time, but for now, Ill try and sumarize what Ive done since I had the phone on OFW.
To get the phone hard-bricked:
I unloacked bootloader and installed Orange fox succesfully then I bricked my phone while trying to flash Global MIUI (as the first step to install ArrowOS but notice it is totally unrelated to ArrowOS), there is a detailed explanation of how I did it here
[ROM] A11 ArrowOS [Garden] 29-12-2021 UNOFFICIAL
I'm not responsible for damage made to your device About: ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end...
forum.xda-developers.com
Trying SPFlash Tool to unbrick my device
My xiaomi redmi 9A was bricked at this point, I described it as:
"the phone just vibrates after a while holding the power button and the screen doesnt even turn on, it isnt recognized by the computer, and if I try to boot into recovery the same happens but the screen turns on for a fraction of a second whith the redmi logo then turn off again, It is not recognized by the computer in this state either"
after gaining some experience with it, I think adecuate to say that the phone still vibrated when holding the power button, but at least the screen did not turn on and as I said; "it wasnt recognized", but just to be clear, what I mean by that is that the PC did absolutely nothing when I pluged the phone in, later after some failed attempts at fixing it, this changed, now the computer prompted me a message explicitly saying, "this device is not recognized" if it was actually recognized before or not is above me.
anyway, back to the moment right after hardbricking my phone in the first place:
I tried using SP flashing tool with this video
but the video is old and after some links died not all the files where provided, (it did however provide a functioning method to disable protection)
so what I did was mix and match different files from diferent sources, and try different methods from diferent videos using SPFlash tool, wich was admitedly a bad idea, the main issue with it was that it symply stayed long periods of time on "download da 100%" with no error message prompting, so i could only stop it change the files and try again, sometimes disconecting the phone, bypassing security with (vol+ vol-) and repeating.
but at one point, the phone did nothing (from now on by nothing I mean not even vibration), the vol+ vol- security did not work, then I tried:
power button alone; noting
power vol+; nothing
power vol-; nothing
and when connected to the PC it told me "this device is not recognized" so the device was totally unresponsive, total brick.
at this point I had already halfly gave up, I enjoy the process, but it was just so unsatisfactory to fail again and again that I just didnt want anymore.
It fixed itself (still hard-bricked but responding).
Now how this got fixed, I actually dont know, I thought maybe if I wait for a while it will respond again, so after two hours it was still the same, I thought maybe if I charge it, after a while with it charging, let it discharge for a while (some odd days), fully charge it (another day or so), and all of those did nothing.
Then I just left it on my desk for like another day when I decided to just try to turn it on one final time and it responded (I dont know what happened I dont know what worked I have several charger boxes and cables plus the pc usb ports, maybe one of them was defective, maybe the one I used lastly was just better, I dont know, but something worked) maybe it just needed around 5 days to work again, i think when it worked for the first time it was plugged to an outlet, Im sorry I cant be more helpful)
now the phone just vibrated after any of the regular button combos, but it no longer displayed anything on the screen if I tried to boot into recovery, but, the PC no longer prompted me that the phone was not recognized, so I could try again.
What actually completely un-bricked my phone.
(This first step is a substitute to the OP requiremeents 5 and 6 used on steps 1 8 9 10 11, this didnt work for me on windows 10, maybe it was just me , but it didnt work)
I installed the Python3.9.1, MTK driver and libUSB I left this files attached as "extra installs", and did it according to how its done on this video
The video is in spanish so if you need extra assistance you can ask me about it or search how to install libUSB wich is the only one I think needs special attention on how to install it (also MTK gave me an error but apparently always does, I tried putting adb on the install folder but Im pretty sure this did nothing as it just gave me a different error)
then, you extract what I left on "ByPass OFF", and run broom.bat a cmd will open up telling you its waiting for a device
(from now on you cant unplug your phone, if you do you have to restart from here)
You plug your bricked phone, and press both vol+ and vol- at the same time until the cmd tells you something like this
then you go to SPFlash tool latest version, (I used SP_Flash_Tool_v5.1924_Win but im pretty sure any one will work)
youll need the ROM that OP provided, its this one.
its 4.22 GB so download it with time, its not a quick page to download from even tho I have "good" internet (around half an hour to a full hour)
you extract it (i recomend using winrar)
and put the scatter file youll use, on the extracted ROM folder, in the image folder, you can download the three scatter files that are for 12.5.4.0 RCDMIXM from the page OP provided and try them all, i left down here the one that worked for me anyway but I dont know what will work for you.
after that I launched the SP Flash tool, and selected the "no auth .bin" provide by OP as Download agent.
(it is posible you get this error
fix it and try again)
as Scatter file you go to the extracted ROM\image and selecth the Scatter file you want to use (again, I left the one I used down here, I have no idea if its the same one that comes with the ROM, also its important it is on the right folder in the extracted ROM)
leave auth blank
I did not select UART port, It didnt work for me, auto USB worked better for me.
you change the dropdown menu to Firmware update
and finally start the program by pressing the download button.
this should work and youll get a prompt like this.
after it had finished I had to unplug my phone and plug it on an outlet for it to let me turn it on, I tried like 3 times before with it still pluged to the PC but it didnt work for some reason, I did not try with it just umpluged so who knows) it turned on to logo, and in around 10 minutes, it asked me to set up the phone as first start like when its brand new, (it was however different to how it used to be, so I know I at least installed a different ROM, do with that info what you will)
Whatts next?
I havent checked if I still have the orange fox recovery installed, tho I doubt it. and also how do I install ArrowOS now? can I do it from spflash tool? thatd be great, is there a better Custom ROM?
Thanks
Also thanks to OP: Yuarian that even if it didnt work for me as is, it still ended providing me with most if not all the tools I needed to unbrick it, and Im pretty sure the ones that didnt work failed becasue I had residual trash files from previous attempts that screwed over his.
anyway see you around.
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
M2006C3LG
SolomonMT said:
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
View attachment 5765891
M2006C3LG
Click to expand...
Click to collapse
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
I have the exact same model, but I dont know how common is that model number, maybe ones made in china and other places have the smae model, I have a 32 Gb version with a single SIM but I can tell it was planed at some point to have it be dualSIM it also has 2 IMEIs
This post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
About your phone in particular, I have three questions.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Ivan.Adriazola said:
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
About your phone in particular, I have four questions.
Its a redmi 9A right? this post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
View attachment 5767183
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Click to expand...
Click to collapse
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
yeah
SolomonMT said:
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
Click to expand...
Click to collapse
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Ivan.Adriazola said:
yeah
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Click to expand...
Click to collapse
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
SolomonMT said:
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
Click to expand...
Click to collapse
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Ivan.Adriazola said:
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Click to expand...
Click to collapse
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Something to be noted for ArrowOS is that you cannot install it on a phone running MIUI 12.5, as far as I can tell.
To install ArrowOS you need to install a custom recovery, and there is no custom recovery for MIUI 12.5.
Moreover, Xiaomi prevents you from flashing an older version of the stock ROM, so there is no way to rollback to a version supported by a custom recovery.
Hence, I am stuck running MIUI 12.5 for the foreseeable future.
SolomonMT said:
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Click to expand...
Click to collapse
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Ivan.Adriazola said:
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Click to expand...
Click to collapse
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad. Thanks.
SolomonMT said:
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad.
Click to expand...
Click to collapse
youre welcome
I managed to flash the rom and revive my phone thanks to this guide. It booted, works perfectly
First unplugged battery. Then.
I used MTKClient on Linux, installed following instructions, https://github.com/bkerler/mtkclient
And ran command
sudo mtk payload
(then left Vol up and Vol down pressed together and plugged usb cable to unlock the SLA Authorization)
The tool runs a generic payload to the CPU, mt6765 in this case, and puts the phone on BROM mode
(This will unlock SLA authorization, allowing the Rom to be flashed)
(A message appears saying " Successfully sent payload " along with Hardware/Port info)
From there immediately used SP Flash Tool-V5-1916
sudo ./flashtool
Used DA_6765_6785_6768_6873_6885_6853.bin as DA
Used MT6765_Android_scatter--V12.5.4.0.RCDMIXM--boundary_false.txt as Scatter file.
And flashed the whole Firmware/Rom 12.5.4.0.RCDMIXM Global with UART Connection Setting.
Thank you for the guide master. God bless you.
(Its important to be patient)
(Bypass utility didn't work for me, i think it works better in Windows or Debian/Ubuntu, but not other distros)
Yuarian said:
Condition
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
Click to expand...
Click to collapse
hi i have a redmi k50 pro whit dimensity 9000 MT6983 can you healpe me? pllleasee
Hi, I was trying these steps with no success, maybe something was missing (this was in Windows). However, I found another way to do it with Linux where you don't need to install drivers as the system comes ready to use.
I detailed what I did to unbrick my Redmi 10A here:
Unbrick or Recover Xiaomi Redmi 10A and other MTK devices
Unbrick Xiaomi Redmi 10A and other MTK devices.
runakay.blogspot.com