I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
mrwiggles727 said:
I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
Click to expand...
Click to collapse
This is literally what everyone's been talking about lately.. there's a few threads here with detailed instructions I believe .
mrwiggles727 said:
I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
Click to expand...
Click to collapse
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
tech_head said:
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
Click to expand...
Click to collapse
Right, so I can do that. However, I still have the issue of getting my phone to authorize the debugging from my computer with no touch ability. This is my big problems really. ANy idea besides that whole mouse adapter OTG?
mrwiggles727 said:
Right, so I can do that. However, I still have the issue of getting my phone to authorize the debugging from my computer with no touch ability. This is my big problems really. ANy idea besides that whole mouse adapter OTG?
Click to expand...
Click to collapse
You don't need to flash those zips or use OTG. Instructions in rooting thread, you have to use pre-patched boot.img that's linked in Notes in OP, worked for me on Sep builds: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
I too was trying to deal with the touch issues, and this was the method that worked for me.
I got the touch to work and it boots into twrp recovery but i had to flashall and it smoked the zip files on my phone. How do I push the zips from computer to internal Storage? I was having trouble getting it in with adb
mrwiggles727 said:
I got the touch to work and it boots into twrp recovery but i had to flashall and it smoked the zip files on my phone. How do I push the zips from computer to internal Storage? I was having trouble getting it in with adb
Click to expand...
Click to collapse
adb push (original location on PC) /sdcard/file.extension
mrwiggles727 said:
I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
Click to expand...
Click to collapse
I have same issue. Please help me solve it step by step. i am newbie. Thanks.
tech_head said:
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
Click to expand...
Click to collapse
Do I need to download said files to flash or just type it into fastboot command line?
jrodbrown58 said:
Do I need to download said files to flash or just type it into fastboot command line?
Click to expand...
Click to collapse
Yes, you must download the files to your PC.
Any time you are fastboot flashing a file, the file must exist on the PC in a location where fastboot can find it. Typically, the file is put in the same directory that your Fastboot executable is located so you are not dealing with providing paths to the file; you just cd to the directory with the fastboot executable and run all of your command from there.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
Yes, you must download the files to your PC.
Any time you are fastboot flashing a file, the file must exist on the PC in a location where fastboot can find it. Typically, the file is put in the same directory that your Fastboot executable is located so you are not dealing with providing paths to the file; you just cd to the directory with the fastboot executable and run all of your command from there.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
That's what I thought and I found the hyp and rpm files I believe using this reddit post
https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
But they are in a form of a zip and when I extract it there's no mbn file extension. So I don't know whether I should add that file extension or flash the zip in twrp...is there anything else I should do or know about before I try this again?
jrodbrown58 said:
That's what I thought and I found the hyp and rpm files I believe using this reddit post
https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
But they are in a form of a zip and when I extract it there's no mbn file extension. So I don't know whether I should add that file extension or flash the zip in twrp...is there anything else I should do or know about before I try this again?
Click to expand...
Click to collapse
What aren't you using the files from post #3 (that you quoted in your initial post)?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
What aren't you using the files from post #3 (that you quoted in your initial post)?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Complete stupidity and lack of sleep from working too much lol but thank you for you help
tech_head said:
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
Click to expand...
Click to collapse
Will this work on Nov patch?
I was following this guide, Guide B, since I was rooted in the AUG: https://www.reddit.com/r/essential/comments/9uhz9d/update_to_november_root_and_twrp_patched_boot/
and its made my touches unresponsive.
It works for me
mrwiggles727 said:
I got the touch to work and it boots into twrp recovery but i had to flashall and it smoked the zip files on my phone. How do I push the zips from computer to internal Storage? I was having trouble getting it in with adb
Click to expand...
Click to collapse
How did you get the touch working. Please help. I am stuck
Bitan701 said:
How did you get the touch working. Please help. I am stuck
Click to expand...
Click to collapse
If you are on the latest stock Nov. I would think the easiest way would be to download the same version from the back to stock images thread. In that will be a boot image pre patched with magisk and a working twrp. Just need to flash that boot image from fastboot.
If you don't want magisk you could still do this then flash the stock boot image within twrp and install the zip installer for twrp.
Or if you have a USB C OTG cable you can just plug in a mouse.
Related
So, you've unlocked your bootloader and are enjoying some rooted goodness on your phone. You then realise you've got an issue with the phone and forgot to make a backup of your stock ROM! Not to fear, this guide is for you! This will reset the phone back to it's out-the-box state, locked bootloader and all, running the latest ZNH2KAS3P0 build so you can return it for RMA/sell it. This also works to go back to CM13.1.2 from Oxygen OS.
It's recommended that you have adb/fastboot in your System Path. This makes it easier to run commands as you don't always have to 'in' your adb/fastboot folder to run the commands. This guide should help you with this but if you don't want to do this, please copy/extract any files into your adb/fastboot folder before continuing...
1. Download the factory image
Cyanogen released the factory image for the OPO but didn't include any batch files to automate the process. I've repackaged the images into two seperate ZIPs:
ZNH2KAS3P0 16GB: DOWNLOAD
md5: be471f6bfc707f86a0af1eb175ec9aad
ZNH2KAS3P0 64GB: DOWNLOAD
md5: c371bc0cb4ef67999d21f5275c5a587b
*** These ZIPs are not flashable so cannot be flashed via TWRP ***
2. Extract the factory image
Using your favourite file extraction program to extract the package to your Desktop (I use 7-ZIP). *** Remember, if you don't have adb/fastboot in your Path, extract the image into your adb/fastboot folder ***
3. Flash the factory image
Once you've unlocked the bootloader, and rebooted the phone, turn the phone off and back on into fastboot mode and reconnect it to the PC. You can now run the flash-all.bat (Windows) or flash-all.sh (Linux) file. These automate the flashing process. Once complete, the phone will reboot.
*** Some users have had issues using the script in Linux so in these cases extract the ZIP file and flash each IMG individually ***
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img (the filename is the same in both ZIPs so make sure you're using the right one for your device)
fastboot reboot
4. Reset the tamper flag/lock the bootloader
There is a flag/bit on the phone that is triggered when you unlock the bootloader and even relocking it won't change this flag back to standard. Luckily, @Mnt-XDA has a script that you can flash which resets these flags so OP/anyone else is none the wiser! To do this, read and follow THIS thread
5. Reboot the phone
Says it all really - you're done!
EddyOS said:
3. Unlock the bootloader on your OPO
Click to expand...
Click to collapse
And why do you need to unlock the bootloader to flash the factory image ????
RalphLauren said:
And why do you need to unlock the bootloader to flash the factory image ????
Click to expand...
Click to collapse
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
EddyOS said:
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
Click to expand...
Click to collapse
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
RalphLauren said:
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
Click to expand...
Click to collapse
I know what you mean, but it's the same with Nexus devices - you cannot flash the image unless the bootloader is unlocked
indesisiv said:
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
Click to expand...
Click to collapse
Yeah was looking to add that in at some point, this is still a work in progress as it were...I'll add it in when I get a chance
EDIT: Added
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
lemonspeakers said:
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
Click to expand...
Click to collapse
To be fair, of someone doesn't know how to do that they really shouldn't be here in the first place!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
This should be a sticky!
banjotrold said:
This should be a sticky!
Click to expand...
Click to collapse
I agree! This definitely should be a sticky.
Sent from my One using XDA Premium 4 mobile app
Which one of these files would be the kernel? I am having wifi issues and am wondering if I would be able to reflash and fix it.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock (if you wish to relock the bootloader. If not, ignore this part)
fastboot reboot
boot.img
EddyOS said:
boot.img
Click to expand...
Click to collapse
Thank you. Any reason why I can't just fast boot the boot.img file only (ala carte)? I am on CM11s rooted with TWRP.
I fastboot flashed the boot.img file sucessfully. It did not fix my wifi problem. So, I tried fastboot flashing the NON-HLOS.bin file. It appears to have an error code. Here is the result.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kevin work>cd desktop/android-sdk-windows/platform-tools
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot devices
9f66970a fastboot
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot flash mo
dem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.306s
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot reboot
< waiting for device >
^C
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>
Any idea as to why it failed?
reboot time
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Xeon_IV said:
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Click to expand...
Click to collapse
As you can see from my command prompt script mine did not want to reboot. I ended up unplugging the phone and rebooting.
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
Click to expand...
Click to collapse
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Click to expand...
Click to collapse
Is your phone the Chinese OPO or the CM OPO?
CM OPO coming from paranois android
mods delete this thread
droid.riz said:
Pre-requisites - Drivers Installed,ADB,Fastboot.
Download - cm-12.0-YNG1TAS0YL-bacon-signed-fastboot
Download - user_data(64gb variant) (also you can use cm11s one if you have it place it inside the extracted fastboot files)
-Reboot your device into Fastboot Mode (power + volume up).
-connect your phone to your PC via usb cable.
-Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
-Open CMD in that folder (Shift+Right click and open new cmd window here)
-first check the device by entering this command
Code:
fastboot devices
- Enter these commands one by one
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot flash dbi sdi.mbn
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot flash aboot emmc_appsboot.mbn
Code:
fastboot flash tz tz.mbn
Code:
fastboot flash LOGO logo.bin
Code:
fastboot flash oppostanvbk static_nvbk.bin
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
P.S This Userdata will wipe ur internal storage you can skip it if you want.
Click to expand...
Click to collapse
What the hell? You plagiarized these instructions directly from my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You've barely even bothered to change the wording.
Transmitted via Bacon
@timmaaa added credits.
droid.riz said:
@timmaaa added credits.
Click to expand...
Click to collapse
Too late for that now, the damage is done. You can't just steal someone else's work and try to pass it off as your own. I worked damn hard on my guide thread, to make sure it's accurate and safe for people to use, I didn't do all that work only to have someone steal it and claim authorship.
Transmitted via Bacon
And about userdata_64G.img from here
timmaaa said:
Too late for that now, the damage is done. You can't just steal someone else's work and try to pass it off as your own. I worked damn hard on my guide thread, to make sure it's accurate and safe for people to use, I didn't do all that work only to have someone steal it and claim authorship.
Transmitted via Bacon
Click to expand...
Click to collapse
okay great ! i am requesting mod to delete the thread.
anagramgenius said:
And about userdata_64G.img from here
Click to expand...
Click to collapse
hahah i never saw your post!
I'll just leave this here:
12. Using the work of others.
"If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you."
Thread closed
Running COS 13 -2JK and when I launch the theme chooser, all themes except the system theme are blank and transparent. Applying any of them crashes the theme chooser. A factory reset didn't cure it. The zip I flashed was straight from cyngn.com/support
Sent from my A0001 using Tapatalk
I had this almost-like problem on 1st cos13 release.after clean flash 2jk it's solved.
avijedi said:
Running COS 13 -2JK and when I launch the theme chooser, all themes except the system theme are blank and transparent. Applying any of them crashes the theme chooser. A factory reset didn't cure it. The zip I flashed was straight from cyngn.com/support
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
can you post the commands you used for flashing the firmware?
hellcat50 said:
can you post the commands you used for flashing the firmware?
Click to expand...
Click to collapse
Flashed via twrp, the signed zip
avijedi said:
Flashed via twrp, the signed zip
Click to expand...
Click to collapse
Use this zip: http://builds.cyngn.com/factory/bacon/cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip
Extract it, put the files into your adb and fastboot directory, boot into bootloader, connect device with your pc and run these commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
if you need further help with adb and fastboot, how to install und how to use, then feel free to reply.
btw what twrp version are you using?
My words may feel funny but i faced the same problem once
I uninstalled all the 12.1 themes from the phone via link2sd
and my problem get solved try this may it help you in a simple way
I'm having the same issue, my update came from OTA.
What i did to solve this, is formatting the phone, setting it up as new and the making a new cyanogen mod account. Now it works. Try it.
arshu16 said:
What i did to solve this, is formatting the phone, setting it up as new and the making a new cyanogen mod account. Now it works. Try it.
Click to expand...
Click to collapse
I did the same but it allows me to download just one theme after that the theme store hangs or becomes unbearably slow it takes 5-10 touches just to scroll the about section of theme. all other apps work perfectly. also I am not able to update any theme.
Didn't want to post because I thought I would solve the issue with a simple MiFlash restore to stock, but oh well, here I go:
Due to my excitement about the Pie update (Beta), I got a fastboot flashable zip that was posted on a thread and attempted to flash it myself, manually.
Commands I executed (one by one, not through the bat script):
Code:
fastboot flash sbl1 sbl1.img
fastboot flash sbl1bak sbl1.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img
fastboot flash tz tz.img
fastboot flash tzbak tz.img
fastboot flash devcfg devcfg.img
fastboot flash devcfgbak devcfg.img
fastboot flash dsp dsp.img
fastboot flash aboot aboot.img
fastboot flash abootbak aboot.img
fastboot flash lksecapp lksecapp.img
fastboot flash lksecappbak lksecapp.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlibbak cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cmnlib64bak cmnlib64.img
fastboot flash keymaster keymaster.img
fastboot flash keymasterbak keymaster.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot set_active a
I probably should never have flashed all this but I will explain what happened in case someone more savvy knows exactly what happened and lends a helping hand.
So all the commands passed fine, except for the fastboot flash system ones. I executed the first one and it flashed parts of 500mb or so on the partition, around 6 times. Same on the system_b.
I suppose that these flash onto the different slots (A/B), correct me if I'm wrong. Then rebooted and it would bootloop (don't blame anyone since I f'd up) and I was like "Okay then, guess I will restore with MiFlash.
Well I did. First weird thing to notice, it would only take around 213 seconds, while it would normally take around 300 seconds so I suspected I might have messed up. Note that I always restore to the April security patch to be able to enable Camera2API. Booted fine, then it was time for me to input my SIM's PIN. I do so, and a message shows up saying "SIM PIN operation failed" and after that it would close and re-open the PIN prompt, basically every time I tried to type the PIN. It basically wouldn't even let me input the PIN itself. Sometimes, if I'm fast enough I can successfully submit it but it's still messed up and doesn't work properly.
I know, I shouldn't have flashed the thing in the first place (since it's also supposed to be confidential), but I did and I regret doing so. For anyone interested, the bootloader is unlocked and I can enter fastboot mode normally. Didn't try flashing a different stock image since this is the one I always use and it works.
If anyone has got any idea about what happened here and if there's any solution, I would be really thankful.
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
michkost858 said:
Update: Also tried flashing one of the 8.1 fastboot images. It flashed without errors. While booting though, it crashed like 2 seconds after asking for my PIN.
Click to expand...
Click to collapse
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
apexashwin said:
Try booting without simcard, if you are able to boot, toggle off sim pin from settings and try booting with simcard
Click to expand...
Click to collapse
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Why flash April update? You can enable camera2api on any ota update! :/
WhatzIt2Ya said:
Why flash April update? You can enable camera2api on any ota update! :/
Click to expand...
Click to collapse
I don't think it's what matters at the moment.
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
michkost858 said:
I don't think it's what matters at the moment.
Click to expand...
Click to collapse
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
WhatzIt2Ya said:
Ugh, yes it does. You need the latest modems etc. for it to flash properly. That's why, you see in custom rom threads say, 'you must be on latest stock firmware before flashing'.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
So, before you flash pie beta update. You MUST be on latest November update for it to flash properly.
Click to expand...
Click to collapse
Just to be clear. I wasn't trying to flash any extra firmware after failing to install the Pie Beta flashable. I tried rolling back to stock.
Also, I was in the latest November update, before flashing the Pie beta flashable, so that's not what's wrong.
About the reason I flash the April update, it's just so I don't get wipes when I lock/unlock the bootloader on the process of enabling Camera2API.
Right now, I just want to get back to stock, didn't try flashing the Pie beta a second time after I failed and I won't.
Also my IMEIs are correct, if that matters in any way. I believe something got corrupted in the partitions (might be bsing) but yeah. Now whatever version I'm on (7.1,8.0,8.1) the issue still persists.
So I'd like to make a full restore, from the ground up, I suppose.
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
nitroax said:
Try install lastest stock firmware using Miflash with Mi A1 in EDL Mode (search here in the forum how to get it there). If it works, then you can flash April firmware or do whatever you want.
Click to expand...
Click to collapse
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
michkost858 said:
I guess I can try that but will that be any different than flashing the same firmware with MiFlash on fastboot?
Also, should I change something on the flash scripts of the fastboot images so that they work properly on EDL mode (saying this cause I read somewhere that they shouldn't have the 'fastboot reboot bootloader' command to prevent bricks, might be bs)?
Click to expand...
Click to collapse
I had a similar problem. Solved restoring persist and EfS backup.
sipollo said:
I had a similar problem. Solved restoring persist and EfS backup.
Click to expand...
Click to collapse
Hmm, I don't have such a backup. Is there a way to restore one?
michkost858 said:
Have tried this. Boots fine without SIM card. In fact, even with the SIM card in I can press the back button and skip the prompt but it will pop up again. But I still can't properly use the SIM
Click to expand...
Click to collapse
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
michkost858 said:
Hmm, I don't have such a backup. Is there a way to restore one?
Click to expand...
Click to collapse
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
Yes this is a known bug. This should fix pin issue
manpildo said:
I've read this is a November patch bug, apparently it works only if your system language is set to English. Try booting without SIM, change your system language to English(US) if it isn't already, remove PIN lock from your SIM-card. Then insert SIM again and see if you can boot without problems... If yes, then you have to either keep your system language English or keep SIM PIN lock disabled.
A zip with backups you can place on your internal storage and restore from TWRP is floating around in THIS thread, try looking it up. There is also extensive discussion over this problem with potential solutions.
Click to expand...
Click to collapse
.:Addicted:. said:
Yes this is a known bug. This should fix pin issue
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. Will be watching over the thread linked.
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery