Related
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.
Hi,
i don't know if it's the correct section but i need a big help.I rebooted my phone this morning but when it comes to write the system pin it says it's wrong.
I can't belive i forgot my pin or i wrote it uncorrect during the configuration.
Now my phone is unable to boot, unable to recovery because of the enrcyption end my pc can't find any device in fastboot, even with the last Motorola drivers.
It's running XPerience Beta 12.0.0.
What can i do if i can't wipe data in any way?
callaghandroid said:
Hi,
i don't know if it's the correct section but i need a big help.I rebooted my phone this morning but when it comes to write the system pin it says it's wrong.
I can't belive i forgot my pin or i wrote it uncorrect during the configuration.
Now my phone is unable to boot, unable to recovery because of the enrcyption end my pc can't find any device in fastboot, even with the last Motorola drivers.
It's running XPerience Beta 12.0.0.
What can i do if i can't wipe data in any way?
Click to expand...
Click to collapse
what were you using before? i mean pattern or pin?
callaghandroid said:
Hi,
i don't know if it's the correct section but i need a big help.I rebooted my phone this morning but when it comes to write the system pin it says it's wrong.
I can't belive i forgot my pin or i wrote it uncorrect during the configuration.
Now my phone is unable to boot, unable to recovery because of the enrcyption end my pc can't find any device in fastboot, even with the last Motorola drivers.
It's running XPerience Beta 12.0.0.
What can i do if i can't wipe data in any way?
Click to expand...
Click to collapse
If you installed experience you should have twrp. Boot to twrp, use file explorer -> /data/system delete locksettings.db
callaghandroid said:
Hi,
i don't know if it's the correct section but i need a big help.I rebooted my phone this morning but when it comes to write the system pin it says it's wrong.
I can't belive i forgot my pin or i wrote it uncorrect during the configuration.
Now my phone is unable to boot, unable to recovery because of the enrcyption end my pc can't find any device in fastboot, even with the last Motorola drivers.
It's running XPerience Beta 12.0.0.
What can i do if i can't wipe data in any way?
Click to expand...
Click to collapse
Why can't you boot into TWRP? If it asks for a password just click "cancel". Then, navigate to Wipe>Format Data and you should be fine.
catsruul said:
Why can't you boot into TWRP? If it asks for a password just click "cancel". Then, navigate to Wipe>Format Data and you should be fine.
Click to expand...
Click to collapse
I came to this solution like ten minutes after i poted this. Trust me that i treid everything. Thank you for the reply.
Hi!
Does Magisk (including root, etc.) work flawlessly on a Pixel C with Android 8.1? Or is better to stay with 8.0 and wait a little bit?
Thanks in advance and kind regards,
star3141.
It works, initially it would force close but now seems stable. I used v14.5 beta.
On the other hand super su by chainfire does not work. Would flash but app missing. Downloading from play store and updating binaries through app causes boot loop.
v14.5 works perfectly here, no problems at all.
Hi!
Thanks for the replies. Maybe I will give it a try at Christmas or alternatively wait for the first update of 8.1 in January.
Hello!
Today, I gave it a try but unfortunately faced some kind of total reflection.
1. I downloaded and flashed the latest android factory image (ryu-opm1.171019.016 = 8.1 from Feb. 2018) from Google.
2. I downloaded and booted (without installing) twrp-3.2.1-0-dragon by means of "fastboot boot twrp-3.2.1-0-dragon.img"
3. In TWRP I mounted the system partition rw
However, after mounting the system partition rw, android won't boot into the system anymore. I am alway getting the green android guy laying on its back with "No command". When I boot into TWRP and mount /system in ro-mode, then will boot afterwards without any problems. So the problem must be related to mounting /system in rw-mode by TWRP.
I have also tried twrp-3.0.0-0-dragon-ryu-02112016-1.img, which worked on my previous 8.0 installation, but it won't work in this 8.1 release anymore.
Any ideas how to get rid of this problem?
Thanks in advance and kind regards,
star3141.
Hello!
I found a solution!
If someone else suffers from similar problems then try the following which hopefully will fix everything: :fingers-crossed:
1. Download and flash the latest (in my case Android 8.1 from Feb. 2018) android factory image from Google.
2. Complete the standard android setup procedure and, when the system is up and running, enable "USB debugging" in the "Developer Options".
3. Restart your device in bootloader mode by "adb reboot bootloader".
4. Format your /data partition by "fastboot format userdata" to remove the filesystem encryption.
5. Download the latest TWRP (in my case "twrp-3.2.1-0-dragon.img") and start it by "fastboot boot twrp-3.2.1-0-dragon.img".
6. In TWRP mount /system in rw-mode and just to be sure check if the /data partition can be accessed. If not, just wipe/format it as ext4 again.
7. Download the latest Magisk (in my case "Magisk-v15.3.zip") and sideload it by "adb sideload Magisk-v15.3.zip" in TWRP.
8. Reboot into the android system and install the Magisk app (in my case "MagiskManager-v5.5.5.apk")
9 Viola! Enjoy a working and rooted android 8.1. :victory:
Kind regards,
star3141.
didn't have any problems with magisk 15.3 on 8.1 but with 16.0 the pixel won't boot anymore (stays at the google logo, not even reaching the bootaniamtion). anyone else having this issue? after flashing boot-image and reinstalling magisk 15.3 it works fine again...
For me as well, get 16.0 not to run, Bootloop
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
m+a+r+k said:
Yep, same here, then I bricked it restoring a nandroid backup where it destroyed system, then I couldn't get past encryption password in TWRP. So it's been one of those days...
Click to expand...
Click to collapse
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
doumer said:
did you already try "default_password" (without quotes of course)? had this issue too some time ago after restoring a nandroid – reflashing twrp via fastboot and decrypting with default_password helped
Click to expand...
Click to collapse
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
m+a+r+k said:
Yes, tried that as well. I think I just corrupted the system, wiped data and system in trying to get around the Magisk problem.
Click to expand...
Click to collapse
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
doumer said:
Hm, as long as you still have fastboot access, I would try to manually flash partiotions (system, vendor etc), flash twrp, install masgisk 15.3, start from scratch and restore the apps with titanium backup (hopfully you have a backup!). as long as its not a hard brick, it's all fixable
Click to expand...
Click to collapse
Oh, I'm back to normal now. I couldn't get it to connect to PC as all I had was fastboot and recovery. I discovered the only way to get adb/fastboot connection from PC was to go into TWRP and ADB Sideload. Once that was established it made the connection and I installed 8.1 from the command line with the flash-all.bat.
Then I could restore the nandroid. All is well now, thanks.
good to hear!
Same problem here with 16.0. Seems to be either a bug or some kind of incompatibility with the pixel c.
Magisk 16 and Pixel C
Any word on resolution of the boot loop issue?
Reflash + downgrade to 15.3 seems the only working solution at the moment.
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
mightywhites29111971 said:
I have re-rooted using Magisk 15.3 from SuperSu. Am I OK updating to 16.0 through Magisk, or should I try 16.3?
Click to expand...
Click to collapse
16.0 causes a boot loop. Somebody else had an issue with 16.3. I'd stay with 15.3. Just turn off update notifications and Magisk won't bother you.
Cheers
phone encrypted.
all started one day, i was 0% battery, phone shut down itself, charged, turned on, the first password of encryption is ok, the OS password of the lockscreen GIVES ME ERROR.
i wonder, WHY? i thought i can use the twrp fix to erase the password inside the OS, ok, i try:
1) removed the 5 files with the twrp file manager, rebooted, NOTHING, after the first password accepted the boot logo is FOREVER going.... stuck.
2) tried to dirty flash the same rom i have ( a resurrection remix 5.8.5 by pranay) , nothing, same result
3) tried to format wiping data, cache, dalvik, nothing.
ok so i said myself UPGRATE TO OREO ROM, i boot into twrp ( twrp asks me the password, i enter it.. and WORKS! i don't know why the SAME password no more works into the OS) and with the MTP i transfer all mi video and pictures. ok!
i flashed the NEW twrp 3.2.1 for oreo ( i had 3.1.1.), i download some custom rom oreo, 2 resurrection remix and AEX, i wipe as usual, i install the aex and all works but i do not see the option to add the FINGERPRINT, mmmhhh in the telegram group someone told me that i "need to encrypt" to make the fingerprint option APPEAR into the OS..... ok no problem, i CAN do it! i WANT to do it! i can't live without encryption for privacy reasons. i charge the phone, press on encrypt and it reboots, i see the RR logo, 10 seconds later i am int othe OS. yes... but STILL UNENCRYPTED
i try to change the rom, new formats, new roms, SAME PROBLEM. i discovered that maybe the data partition was ruined, ok i did several "repair", i did several changes to f2fs and return to ext4 .... but sometimes i got some strange errors when trying to change the filesystem TO f2fs.
then i tried to flash the STOCK ROM follwing this guide
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914
i made it all correct, now i am on stock s244 rom, in this rom i can use fingerprint but the encryption password bug is STILL PRESENT, it simply does not encrypt my phone if i press to encrypt! made a lot of tests, repair, change file system of data..... NOTHING HELPED ME. ah yes...... at a precise point into the OS i see that my phone is encrypted. WHAT?
so i boot into twrp and it asks me the password i enter it, but it is WRONG. wrong? NOT POSSIBLE it is the same....the same! i tried a lot of password like password.... default_password, 123456,0000,000000 ........
to recover my twrp i used the command "fastoboot erase userdata", it worked, now i am without a "fake" encryption. i continue to do tests, sometimes my file system showed into the twrp in the wipe menu... is showed as "auto", sometimes as "emmc" ........ MMHHHHH never seen these kind of file systems! so i changed them every time to ext4!
then i tried to flash back my "old" rr rom nougat 5.8.5 , it works, in this rom i see the FINGERPRINT OPTION, but the same bug of impossible encryption at reboot.
- so i think i can try to flash the old twrp 3.1.1 because maybe the latest one is BUGGED! maybe! i flash it....keeping the OREO rom, and still can't encrypt.
- so i try to also flash the 3.1.1 twrp... and another clean instlall of RR nougat, i do all wipes every time, all precise, no dirty flash.... and with rr nougat i CAN use fingerprint but NO encryption.
i wonder ......... i use the SAME twrp image i used for months! same file! my file.
i use the SAME ROM ZIP rr 5.8.5, why in this moment i have a "different" configuration than before? filesystem is the same ext4.... but the phone still does not want to let me encrypt it! and someone must show me the REASON WHY with all oreo roms the user cannot use the fingerprint scanner ( there is no option into the os!) without to use the encryption?
I HAVE ALWAYS USED FINGERPRINT ON OTHER PHONES WITHOUT ENCRYPTION.....
now i have 2 solutions:
1) keep the RR nougat, unencrypted BUT AT LEAST with fingerprint unlock.
2) use the RR ( or any other oreo) rom but unencrypted, and WITHOUT the possibility to unlock with my finger! grrrr!!
please give me your advice, your opinion how is it possible i tested so much different configurations, mxed different twrp, different roms, changed data file system from ext4 to f2fs and the opposite, tried to "repair" file system....... appeared random ENCRYPTED twrp but with an "impossible to know" password.... i also flashed the stock rom with the fastboot command following the guide on xda i posted at the link, i feel really empty and without possibilities to fix this problem.
but as i can remember all started with the phone shut down at 0% battery! from that point my password has never been accepted anymore!!! i was LOCKED OUT from my phone, to be precise not my full phone because the password WORKED to unlock the encryption! ( i recoveredall my files!) but the OS refuses to accept the "same" password i used to unlock the encryption... it is very strange!
First of all, my deep condolences.
Second, dude, you have done so many wrong turns..but let's get to fixing.
First of all, download this: https://androidfilehost.com/?fid=817550096634780916
It's a one click Firmware Rescue Folder, with our oldest Firmware( 6.0 MM).
This tool can always be used, no matter if you're unlocked or locked. So it's your last key to get on Stock Rom. Even if your phone is stuck at bootloop, etc. .
Turn your phone off and open up "flashall - stock reco.bat".
Let it do it's job and do not under any circumstance remove the cable.
Your phone will reboot on its own after it's done.
Once your phone is started, you can either keep on using Stock and setup as usual , OR you skip Google Login, complete the Setup Wizard. And then login into WIFI manually through Quick Settings.
From there tap on the "System Update is avaibable" Message. And so all of the ota updates. Also while you're waiting for the download to complete, enable Developer Options (Tap 5xTimes on Build Number), then enable USB Debugging.
While it is still downloading on your phone, go ahead and download https://dl.twrp.me/kuntao_row/ to your computer, the latest version.
- - - After all ota Updates are done, you should be on S251, ADB Debugging enabled, Google Account still not setup - - -
Okay, open up CMD from your adb-platform tools folder, if you don't have it, download it from its official source here.
Rename the "twrp-3.2.1-0-kuntao_row.img" to "r.img" and put it into the extracted platform tools folder.
Connect your phone to your pc. Open up cmd and navigate to your platform tools folder.
The Commands for CMD are:
cd Downloads
Click to expand...
Click to collapse
C:\Downloads\platform-tools
Click to expand...
Click to collapse
Could be somewhat different, depends on where you have your Downloads folder.
adb devices
Click to expand...
Click to collapse
Tick the one tickable option on the new poped up prompt on your phone. Accept it.
Now, use:
adb kill-server
Click to expand...
Click to collapse
adb reboot bootloader
Click to expand...
Click to collapse
Now, use:
fastboot oem unlock
Click to expand...
Click to collapse
after this, either your phone reboots on its own, or it doesn't. If it doesn't, don't worry, it's fine.
Now, use
fastboot flash recovery r.img
Click to expand...
Click to collapse
fastboot boot r.img
Click to expand...
Click to collapse
in TWRP First Time Pop Up Message. Just tick the one small box, and use the slider.
Go into "Reboot" Menu, and chose recovery
Click to expand...
Click to collapse
No questions asked, just do it.
Wait for Twrp to boot back into twrp. Once you're back in your menu.
Go into "Wipe" ,chose "Factory Reset", then go back and chose "Advanced Wipe", now select the data partition, and chose to change the file system. Chose "f2fs"
Click to expand...
Click to collapse
Now, go back and into the Reboot menu, Chose Recovery again.
Go into "Wipe" again, "Advanced Wipe" -> Select Data Partition only -> Chose Change File System-> Chose ext4-> Go Back into Main menu
Click to expand...
Click to collapse
Chose "Reboot"-> Chose Recovery again.
Click to expand...
Click to collapse
Wait till it boots to twp again. Tap on the right button on your navigation bar, now the logs will show up. Look for anything red; there shouldn't be any errors now.
Go into "Wipe" Menu again -> Chose "Format Data"-> Type yes and accept.
Click to expand...
Click to collapse
Do not reboot under any circumstance.
Now, that this is done, go ahead and reboot back into Recovery.
Main Menu>Reboot>Recovery
Click to expand...
Click to collapse
Go back into the Wipe Menu->Advanced Wipe-> Select data Partition-> change file system->Chose ext4
Click to expand...
Click to collapse
Go back to Reboot menu and once again chose recovery. Wait for it to boot back into Twrp.
Check for any erros on your log. (right button on your navigation bar. Tap again to go back into the Main menu)
Go to Advanced Wipe->Select System Partition-> wipe it.-> Back to the Main menu
Click to expand...
Click to collapse
Now it's time to flash Stuff!
- Flash your Rom
- Depending on what Android Version you're on, flash your desired Custom Kernel which should be compatible with your Rom.
- Flash Gapps, if desired.
- Flash Magisk or SuperSu for Root, if desired.
- Wipe Dalvik and cache. Now go and reboot
Click to expand...
Click to collapse
thank u, i will test it within a few days!
just a doubt.... when u say to put the recovery image here C:\Downloads\platform-tools
i simply generally put the files i want to flash into the folder called "minimal adb and fastboot" becuase i use that way, is it ok?
and i wonder why to use this command "adb kill-server", i've never used it... and why to priorly use "adb devices" ....jus to see if the phone is read by the pc?
ok.. but i suppose the command "adb reboot bootloader" does not require to kill the adb server.... i've never read to do it.
and last thing.... how do you think that this method would save me? it seems just another option to flash the stock rom.. but i already did it followinf the guide i linked, and i also upgraded at the last OTA within the OS....
sm00th4f3 said:
Now it's time to flash Stuff!
Click to expand...
Click to collapse
thank u bro! u are MY ANGEL now it works!! u solved my problem!
realista87 said:
thank u bro! u are MY ANGEL now it works!! u solved my problem!
Click to expand...
Click to collapse
You're welcome. I had to learn how to solve this the hard way....glad that i could help you!
Rocking RR Nougat+Magma Kernel= Best Combo for now
https://forum.xda-developers.com/lenovo-p2/development/rom-resurrection-remix-v6-0-0-t3792929
why not this OREO rom by PriyeshP? i had nougat rr but battery life was not perfect... i had to mad a lot of tweaks with greenify and bocking some services within the options of the RR just to achieve a good battery life, but not perfect idle battery
realista87 said:
https://forum.xda-developers.com/lenovo-p2/development/rom-resurrection-remix-v6-0-0-t3792929
why not this OREO rom by PriyeshP? i had nougat rr but battery life was not perfect... i had to mad a lot of tweaks with greenify and bocking some services within the options of the RR just to achieve a good battery life, but not perfect idle battery
Click to expand...
Click to collapse
Some options aren't working and are still present in the rom.
Battery life on Nougat was pretty good for me. 13hours of sot daily under heavy usage.
sm00th4f3 said:
First of all, my deep condolences.
Second, dude, you have done so many wrong turns..but let's get to fixing.
First of all, download this: https://androidfilehost.com/?fid=817550096634780916
It's a one click Firmware Rescue Folder, with our oldest Firmware( 6.0 MM).
This tool can always be used, no matter if you're unlocked or locked. So it's your last key to get on Stock Rom. Even if your phone is stuck at bootloop, etc. .
Turn your phone off and open up "flashall - stock reco.bat".
Let it do it's job and do not under any circumstance remove the cable.
Your phone will reboot on its own after it's done.
Once your phone is started, you can either keep on using Stock and setup as usual , OR you skip Google Login, complete the Setup Wizard. And then login into WIFI manually through Quick Settings.
From there tap on the "System Update is avaibable" Message. And so all of the ota updates. Also while you're waiting for the download to complete, enable Developer Options (Tap 5xTimes on Build Number), then enable USB Debugging.
While it is still downloading on your phone, go ahead and download https://dl.twrp.me/kuntao_row/ to your computer, the latest version.
- - - After all ota Updates are done, you should be on S251, ADB Debugging enabled, Google Account still not setup - - -
Okay, open up CMD from your adb-platform tools folder, if you don't have it, download it from its official source here.
Rename the "twrp-3.2.1-0-kuntao_row.img" to "r.img" and put it into the extracted platform tools folder.
Connect your phone to your pc. Open up cmd and navigate to your platform tools folder.
The Commands for CMD are:
Could be somewhat different, depends on where you have your Downloads folder.
Tick the one tickable option on the new poped up prompt on your phone. Accept it.
Now, use:
Now, use:
after this, either your phone reboots on its own, or it doesn't. If it doesn't, don't worry, it's fine.
Now, use
in TWRP First Time Pop Up Message. Just tick the one small box, and use the slider.
No questions asked, just do it.
Wait for Twrp to boot back into twrp. Once you're back in your menu.
Now, go back and into the Reboot menu, Chose Recovery again.
Wait till it boots to twp again. Tap on the right button on your navigation bar, now the logs will show up. Look for anything red; there shouldn't be any errors now.
Do not reboot under any circumstance.
Now, that this is done, go ahead and reboot back into Recovery.
Go back to Reboot menu and once again chose recovery. Wait for it to boot back into Twrp.
Check for any erros on your log. (right button on your navigation bar. Tap again to go back into the Main menu)
Now it's time to flash Stuff!
Click to expand...
Click to collapse
The file is not available anymore - do you know where I may be able to find it?
my phone shows "encrypted" but there is no "fingerprint" option in security settings. currently on stock s244 deodexed i tried los 15.1 n stock but cant find fingerprint in settings. can u guide me how to get fingerprint option back pleaseee
fingerprint not showing
Lavesh05 said:
my phone shows "encrypted" but there is no "fingerprint" option in security settings. currently on stock s244 deodexed i tried los 15.1 n stock but cant find fingerprint in settings. can u guide me how to get fingerprint option back pleaseee
Click to expand...
Click to collapse
did you find a solution , I'm having the same problem
Same problem for me.... and nothing works.....
Today i installed LR recovery and rooted my phone then i installed Viper 4 android... everything went well.. at last i uninstalled xiamo sim activation apk because it bothered me every time i reboot my phone... but after uninstalling that my phone is no longer booting up.. it boots to fastboot mode only.. I can manually boot to twrp but my files are also corrupted...
anyway to recover my data? MIUI 11 indonesian rom
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
wang1chung said:
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
Click to expand...
Click to collapse
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
n70shan said:
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
antony.ps said:
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
Click to expand...
Click to collapse
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.7 and it opens now, will see what it does
n70shan said:
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.4 , and the problem is it opens and closes immediately.. what should i do now?
Click to expand...
Click to collapse
I'm using Linux right now, and it only runs on Java 11, maybe it's java version problem? Try to use Oracle Java 11 if Redhat or other OpenJDK distribution doesn't work.
n70shan said:
.......
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
wang1chung said:
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
Click to expand...
Click to collapse
Oh my bad i forget that.. been out of Android from months..
Anyways issues are resolved now with data lost ?
Thanks
Moderators can close the thread