- WARNING -
This Guide is not failproof, if you do anything wrong with your device while following this guide, i won't be held responsible if you brick or hard damage your device. I insist about that but you must extract all of your data (Photos, Videos, Music, Apps, Accounts, Messages, ETC) Before proceeding or else you will end up with a loss of data, again i'm still not responsible if you lose all of your data without backing up. I WARNED YOU.
Well, you have a Galaxy S6 edge+ lying around and you want to get back to Lolipop? You want to downgrade? Well then you're in the right place!
So......downgrading to lolipop...... some people claimed it can be done by deleting some file in the odin .tar but that never worked for me.
If you have the sw rev check fail error upon downgrading....this is the guide for you!
This will wipe all your data including internal storage (depending on how you do it)
Confirmed working on my Galaxy S6 edge+ SM-G928F [It should work on Note5 but no promises from now on]
Advantages :
Downgrade procedure is safe, simple.
Your phone should boot faster
battery life should last longer [i said it should]
You can get the animated lock screen animations back.
Get old touchwiz back. [i like the 5.1.1 version]
disadvantages:
1. You cannot boot TWRP while on the downgraded bootloader
2. You will only have system-wide root. DO NOT flash systemless or it will not boot (but nobody cares)
3. Fingerprint is not working (still working on that)
4. You can only flash stock nougat from odin. You cannot flash lolipop, marshmallow tar,twrp tar,cf auto root tar or anything else [except if you have a combination firmware]
Ok, let's get started.
Requirements :
A laptop or home PC : At least running Windows 8/8.1 or Windows 10
Your device
Genuine Samsung charging cable [NOT SPONSERED]
Stable internet connection.
Files :
The lastest SAMSUNG Drivers which can be found here : https://developer.samsung.com/android-usb-driver
Odin3 : https://www.samsungodindownload.com/fr/download-for-windows
The firmware you want to downgrade to : I will link my ROM so u can install it.
TWRP [Newest version] : https://twrp.me/samsung/samsunggalaxys6edgeplus.html
Classy Kitchen [for bulding your rom] : https://forum.xda-developers.com/t/...kitchen-for-android-roms-development.3862584/
Now let's get started!
Let's start first by cooking the ROM! Open Classy Kitchen, and then open the ROM you want to use :
{
"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"
}
Normally the first time you open the program, there shouldn't be any project [except if you used this app before]
Next click "Create new project", "From PC (Browse for one)"
And then chose the path where you saved your firmware. After chosing your firmware, Classy Kitchen will open the firmware automaticly.
After the ROM is now open, click on "ROM utils" and then click on "Deodex ROM" After you Deodex the ROM, we will have to de-bloat it.
On Classy Kitchen, click on "Debloat / Re-Bloat ROM" to Debloat your ROM.
Last step [optional] We will have to De-Knox our ROM. (again optional) But De-Knoxing our ROM can save a lot of space in our phone storage. So i recommend you do.
After De-Knoxing our ROM, we will have to disable DM-Verity Force Encryption in order to Boot into the ROM [Otherwise if you don't your phone will never boot]
Click on "Remove DM-Verity / Force Encryption"
Next that we disabled DM-Verity, We will have to remove the "meta-inf installer"
Click on "Re-Build META-INF installer" and click on remove.
Finally once we have done the modifications on our ROM, we just have to save.
Click on "Build (system.new.dat) ROM (for recovery)"
and then we are done cooking our ROM!
But the guide is not done yet. We will have to install TWRP in the phone.
HOW-TO-PROCEED?
Step-1 Press and hold the power button on your device
Step-2 Chose "Power Off"
Wait for your device to completly Shut-Off.
Step-3 Re-Boot in download mode "odin mode"
Step-4 connect the phone to your computer
Step-5 open Odin3
In Odin, we will have to install TWRP, click on the AP box and chose your TWRP file [the one that you downloaded]
Don't forget to disable "Auto-Reboot" after installation, otherwise your phone will re-boot normal into Android.
At this point, Knox is tripped in your device meaning that your warranty is now expired. Also the Knox features are no longer usable.
On TWRP, click on wipe, "Format Data". A keyboard will pop-up, type "yes"
Type "yes"
Once Data Format is completed, hit home, reboot, recovery.
your phone will reboot into recovery again, hit wipe again, this time we won't format data. Instead we're going to wipe the phone's partitions
Chose in TWRP,
Then swipe to wipe. Then hit home again. Next hit "Install"
Install the ROM you just made with Classy Kitchen. It can be found in "Documents" - "Output" - "Your-ROM"
Transfert it to your phone
Click on the ROM / ZIP file and "swipe to confirm flash"
After the flashing procedure is complete, you will have to wipe the "cache" / Dalvik.
Hit "wipe dalvik/cache"
Then "swipe to wipe"
After you wiped the cache, hit "Reboot System" and hit "Do Not Install"
One last step before you get back to Lolipop. You will need a custom Bootloader in order to boot.
Just download my "custom Bootloader" https://drive.google.com/file/d/1207Guvk8J_L9FSJv2C9BpkeLpWkXtViQ/view?usp=drive_link
After you downloaded my "custom bootloader" you will have to install it.
so get Odin3 and install my bootloader!
After the Bootloader installation is complete, you just have to reboot your device, cross your fingers and hope it boots!
Congratuations! You are back on Lolipop! Enjoy!
1 : If you want to flash a mod in TWRP, you will have to put your phone in download mode, install the stock bootloader in BL tab, install TWRP in AP tab and then click on "start"
2 : If you want to get back into marshmallow / Nougat, you just have to flash stock firmware in Odin3
If you have any issues or any questions, you can DM me but it isn't guaranteed that i will reply.
Here are some screenshots of Lolipop :
Here the device i used.
what about system sound because on 6.1.1 (sorry 6.0.1) sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Nevermind. This comment is deleted
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Actually
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Try download downloading my bootloader again. I made it public
TheWiiGuy said:
Actually
Try download downloading my bootloader again. I made it public
Click to expand...
Click to collapse
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
iskender4444 said:
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
Click to expand...
Click to collapse
Have you downgraded to Lollipop yet?
TheWiiGuy said:
Have you downgraded to Lollipop yet?
Click to expand...
Click to collapse
i had bootloop on samsung galaxy s6 edge plus here the photo:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
iskender4444 said:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
Click to expand...
Click to collapse
Yes. This is The Good TWRP. Are you trying to get into recovery? If not then there is a problem with my bootloader
Mind if i upload the New bootloader tomorrow?
iskender4444 said:
i had bootloop on samsung galaxy s6 edge plus here the photo:
Click to expand...
Click to collapse
It looks like the phone is trying to get into stock recovery.
TheWiiGuy said:
It looks like the phone is trying to get into stock recovery.
Click to expand...
Click to collapse
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
iskender4444 said:
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
Click to expand...
Click to collapse
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
TheWiiGuy said:
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
Click to expand...
Click to collapse
Oh yes. Have you backed up all of your partitions on TWRP?
TheWiiGuy said:
Oh yes. Have you backed up all of your partitions on TWRP?
Click to expand...
Click to collapse
i solved twrp but can't boot same as issue on picture
iskender4444 said:
i solved twrp but can't boot same as issue on picture
Click to expand...
Click to collapse
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
TheWiiGuy said:
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
Click to expand...
Click to collapse
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
iskender4444 said:
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
Click to expand...
Click to collapse
Nevermind this comment is deleted
TheWiiGuy said:
What is your phone model number? I see you are installing firmware for a sm-g780f.
Click to expand...
Click to collapse
no this is for example man mine was g928c
Related
I have Vodafone IE HTC M8. I tried to upgrade to stock 5.0 (just recently arrived). As people advised, flashed stock recovery and started OTA upgrade... And got big red triangle... Have no idea why I managed to reboot (Power + VolUp). And ... Now I cannot get to recovery any more, the phone says "Software status: modified" and stays in the boot loader.
Any attempts to flash recovery fail with "signature verify fail". I tried various things: stock recovery, philz recovery. Same thing.
Any advice? I would really like to have recovery recovered...
It seems I managed to oem lock the phone again. Unlocked - and can normally flash recovery.
So, philz recovery works, once flashed. But the stock recovery... It does not work, at all. Trying to switch to it, getting back to bootloader (and I see some messages, quickly disappearing: "No image or wrong image". Still not good
1. Unlock your Bootloader
2. Load adb/fastboot (if you're to lazy to install this all, like me, use the version from the video https://www.youtube.com/watch?v=5xVl2dBTnmI)
3. Then load the latest Version of TRWP and flash it with fastboot
4. Download the right nandroid backup here http://forum.xda-developers.com/show...postcount=2960
5. Start Recovery on your Device and Make backup of boot (to see were the right place is to put in the nandroid)
6. Start Backup from the nandroid via TRWP on your device
7. Finish
(The only thing is, that you have got a branded HTC8)
This was the thing I did here. I think it should work for you too.
Here you can see my Thread with a similar Problem:
http://forum.xda-developers.com/htc-one-m8/help/bootl-loop-lollipop-update-t3016142
sudaltsov said:
I have Vodafone IE HTC M8. I tried to upgrade to stock 5.0 (just recently arrived). As people advised, flashed stock recovery and started OTA upgrade... And got big red triangle... Have no idea why I managed to reboot (Power + VolUp). And ... Now I cannot get to recovery any more, the phone says "Software status: modified" and stays in the boot loader.
Any attempts to flash recovery fail with "signature verify fail". I tried various things: stock recovery, philz recovery. Same thing.
Any advice? I would really like to have recovery recovered...
Click to expand...
Click to collapse
When you get the big red triangle, press & hold volume up and tap power button once to read the error log.
As some have same problem like yours, the problem maybe wrong stock recovery.
To ensure the right recovery image for you to proceed OTA, download OTA again, when it ask to install select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img ---this is the correct recovery image to use.
ckpv5 said:
When you get the big red triangle, press & hold volume up and tap power button once to read the error log.
As some have same problem like yours, the problem maybe wrong stock recovery.
To ensure the right recovery image for you to proceed OTA, download OTA again, when it ask to install select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img ---this is the correct recovery image to use.
Click to expand...
Click to collapse
I had the same problem. I did exactly what you said. extracted the stock recovery.img from the OTA update, flashed my M8 with this recovery, still no luck
I am on 3.28.401.9 stock rom from last OTA
unlocked
this is the error I'm getting :
{
"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"
}
snowfree52 said:
I had the same problem. I did exactly what you said. extracted the stock recovery.img from the OTA update, flashed my M8 with this recovery, still no luck
I am on 3.28.401.9
this is the error I'm getting :
Click to expand...
Click to collapse
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
ckpv5 said:
[/HIDE]
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56827142&postcount=2920
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
Click to expand...
Click to collapse
thanks for your reply. :good:
your link doesn't point to the right files I believe.
How do I flash only the system part ?
snowfree52 said:
thanks for your reply. :good:
your link doesn't point to the right files I believe.
How do I flash only the system part ?
Click to expand...
Click to collapse
Link corrected.
You don't flash, you restore with TWRP.
Read what @swedax94 wrote above and his thread
You also can read http://forum.xda-developers.com/showthread.php?t=2701376
I guided many on how to restore a backup made with TWRP
ckpv5 said:
[/HIDE]
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
Click to expand...
Click to collapse
ckpv5 said:
Link corrected.
You don't flash, you restore with TWRP.
Read what @swedax94 wrote above and his thread
You also can read http://forum.xda-developers.com/showthread.php?t=2701376
I guided many on how to restore a backup made with TWRP
Click to expand...
Click to collapse
OK I see, still downloading your nandroid.
I had a look at TWRP, just have to uncheck data then ? Am I correct ?
Thanks
snowfree52 said:
OK I see, still downloading your nandroid.
I had a look at TWRP, just have to uncheck data then ? Am I correct ?
Thanks
Click to expand...
Click to collapse
Yes .. uncheck data if you want to keep your data.
If you want everything fully stock, then check all boot, data and system.. it's your choice.
Should I also restore the boot part or only system is good ?
Thanks !
snowfree52 said:
Should I also restore the boot part or only system is good ?
Thanks !
Click to expand...
Click to collapse
Only system is good enough but selecting boot make no harm.
BTW @sudaltsov - how's thing going ?
ckpv5 said:
Only system is good enough but selecting boot make no harm.
BTW @sudaltsov - how's thing going ?
Click to expand...
Click to collapse
OK, did it !
Is it normal that it's still showing HTC boot logo after already 10 minutes ?
snowfree52 said:
OK, did it !
Is it normal that it's still showing HTC boot logo after already 5 minutes ?
Click to expand...
Click to collapse
Lets wait for 10 mins. If still not booting, go back to recovery select system & boot (I expect you have stock boot.img installed), then wipe dalvik & cache before reboot.
You have TWRP 2.8.4.0 installed right ?
If it's still fail to boot, then make a backup of your data then restore data from the downloaded nandroid. This will make you have a new set up phone.
ckpv5 said:
Lets wait for 10 mins. If still not booting, go back to recovery select system & boot (I expect you have stock boot.img installed), then wipe dalvik & cache before reboot.
Click to expand...
Click to collapse
It worked ! thank you
now what ? I replace TWRP recovery with the one from the OTA update then try again to install it ?
snowfree52 said:
It worked ! thank you
now what ? I replace TWRP recovery with the one from the OTA update then try again to install it ?
Click to expand...
Click to collapse
Yes..install the stock recovery then check OTA, download and install
And also note that after a successful update to lollipop, it will take some time for it to complete boot and optimizing ..
ckpv5 said:
Yes..install the stock recovery then check OTA, download and install
And also note that after a successful update to lollipop, it will take some time for it to complete boot and optimizing ..
Click to expand...
Click to collapse
Well didn't work again !
My M8 is european, the lockscreen from your nandroid is different than mine
edit : I see, in parameters, it now says my firmware is 1.54.401.10 ??? and android 4.4.2. How comes ???
I guess I restored an old nandroid of mine !
I see, I didn't put your nandroid in the right folder ! where should I put it ?
snowfree52 said:
Well didn't work again !
My M8 is european, the lockscreen from your nandroid is different than mine
edit : I see, in parameters, it now says my firmware is 1.54.401.10 ??? and android 4.4.2. How comes ???
I guess I restored an old nandroid of mine !
I see, I didn't put your nandroid in the right folder !
Click to expand...
Click to collapse
Never mind ... try again.
Remember when you extract the nandroid zip using extract to 3.28.401.9_ckpv5, there will be another folder inside it, use extract here then you get 3.28.401.9 folder
ckpv5 said:
Never mind ... try again.
Remember when you extract the nandroid zip using extract to 3.28.401.9_ckpv5, there will be another folder inside it, use extract here then you get 3.28.401.9 folder
Click to expand...
Click to collapse
That's what I didn't do !
restoring right now ! :good:
ckpv5 said:
extract out the recovery.img ---this is the correct recovery image to use.
Click to expand...
Click to collapse
That worked! Thank you very much!! There were some errors in the recovery, actually - but at least the installation process passed. Hurray! Thank you again!
TWRP recovery 3.0 zenwatch
How to install Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master
acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.
Ups , i fix this today ...
Sorry
hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!
Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)
itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).
Boooooo moto 360. It's sooo damn big.
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github
Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.
I need a link to the stock recovery.IMG file
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9300 and SM-G9308 Qualcomm models only! Do not flash on Exynos models!
If you have a SM-G9350 look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7china.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for heroqltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_heroqlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_heroqltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 China, Tool/Utility for the Samsung Galaxy S7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_heroqltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't boot it because of your signature enforcement (locked bootloader)! Muahahahaha!
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
xD I'm waiting for the damn bootloader's to be unlocked!
I have a Samsung Galaxy S7 SM-G930U (unlocked version) ........I currently am using this device in nigeria and i want to unlock bootloader/root/ install TWRP but it doesnt allow the TWRP install on ODIN.... MY device is using the Qualcomm/ not the EXYNOSS
phone model: SM-G930U
device type: heroqlteue
product name: heroqlteue
product code: SM-G930UZKAXAA
CSC: XAA USA/US
BOOTLOADER: G930UUEU2APG9
Hardware: qcom/msm8996
please help.
obone410 said:
I have a Samsung Galaxy S7 SM-G930U (unlocked version) ........I currently am using this device in nigeria and i want to unlock bootloader/root/ install TWRP but it doesnt allow the TWRP install on ODIN.... MY device is using the Qualcomm/ not the EXYNOSS
phone model: SM-G930U
device type: heroqlteue
product name: heroqlteue
product code: SM-G930UZKAXAA
CSC: XAA USA/US
BOOTLOADER: G930UUEU2APG9
Hardware: qcom/msm8996
please help.
Click to expand...
Click to collapse
U = USA (only SIM unlocked, still bootloader locked, it's the same as all the other USA variants)
it will never be able to use TWRP.
jcadduono said:
U = USA (only SIM unlocked, still bootloader locked, it's the same as all the other USA variants)
it will never be able to use TWRP.
Click to expand...
Click to collapse
WHY HAST THOU FORSAKEN ME!!!!
But really tho when you say never... Will I never be able to use GOV Tuner?
Also for anyone stuck in a loop after trying to flash TWRP (don't ask how I know this!) if you restart into download mode and press up you can get it to restart normally from there. FYI.
Any luck with the v variants? G935v / G930v? Could we boot a recovery and not flash it like the guys in the amazon fire forum?
G9300 APE3 root ok, but modem version unknown. modem fatal.
来自我的 Mi-4c 上的 Tapatalk
i have a s7 g9308 from china mobile, pls confirm if this will gonna work and can i install gapps aftet thid method works?
knoxgin said:
i have a s7 g9308 from china mobile, pls confirm if this will gonna work and can i install gapps aftet thid method works?
Click to expand...
Click to collapse
no idea, you should let me know. back up system in twrp and then flash your gapps package, probably "ARM64 -> 6.0 -> Nano" (it is minimal but has everything that can't be installed from play store) from opengapps.org to be safest. Any other google app can be installed from play store if that succeeds.
If it fails to work, simply restore the system backup you made and you're back to how you were!
jcadduono said:
no idea, you should let me know. back up system in twrp and then flash your gapps package, probably "ARM64 -> 6.0 -> Nano" (it is minimal but has everything that can't be installed from play store) from opengapps.org to be safest. Any other google app can be installed from play store if that succeeds.
If it fails to work, simply restore the system backup you made and you're back to how you were!
Click to expand...
Click to collapse
ok tnx sir. but this method really work? if i follow the steps? coz if i brick it , i dnt know How to flash it back to stock tru odin.
installing twrp works, but if i flash supersu only, then reboot, root works but lost my signal and if i flash no-verity-opt-encrypt zip. only then reboot, it works and has signal, and if i flash both, rooted but no signal, pls help.. also, gapps x64 6.0 nano get errors in google play services, cant download or update apps, i think the problem sir is in supersu, coz everytime i flash it i lost my signal, im glad i have my backup in twrp , pls help fix this bug, i want a rooted and working gapps, coz china mobile dnt have gapps pre installed
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Can't read!
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
KillerClaw321 said:
xD I'm waiting for the damn bootloader's to be unlocked!
Click to expand...
Click to collapse
There is always hope (Looks at Note 4)
evrycard said:
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Click to expand...
Click to collapse
So flashed this on which US S7 variant and software , 930U or ?
evrycard said:
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Click to expand...
Click to collapse
Seriously? Or troll?
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
dirtydodge said:
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
Click to expand...
Click to collapse
Joking with the OP.
dirtydodge said:
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
Click to expand...
Click to collapse
fixed the post, you can flash it but you can't boot it due to locked bootloader (signature enforcement)
Help me
i tried to flash your recovery and stock rom after that. So my mobile is starting bootloop. Can you help me to solve this problem. I think a stock recovery is a solution to solve that
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, NFC did not work for me even on stock bl locked firmware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
just flash a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
metalspider said:
just faslh a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
Click to expand...
Click to collapse
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
{
"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"
}
Free phones welcomed.
pl1992aw said:
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
Free phones welcomed.
Click to expand...
Click to collapse
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Ghostface009 said:
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Click to expand...
Click to collapse
As you wrote earlier, you had root access before MIUI update.
Once you get root, use Debloater to debloat the updater.
Code:
com.android.updater
is one of it.
Maybe there's other ones, but I don't have this phone, can't tell much about it.
Ghostface009 said:
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
Click to expand...
Click to collapse
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Issue solved after flashing unmodified boot.img, thanks all.
laid1995 said:
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Click to expand...
Click to collapse
Unfortunately it doesn't boot, I entered the fastboot command and it's just a black screen. I guess this doesn't work with MIUI 12.5.1, and that means Im stuck without root thanks to xiaomi
I also tried the adb command to remove magisk modules, didn't work, says inaccessable or not found
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Alin45 said:
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Click to expand...
Click to collapse
...But they did tho
The phone boots now, but still, I lost magisk and now I cannot install it on this update.
The phone also can't pass safetynet for some reason, despite having stock boot.img restored and leaving no trace of magisk.
All that could've been avoided if the device just did as it was told to, not to automatically update itself.
reg66 said:
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Click to expand...
Click to collapse
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Ghostface009 said:
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Click to expand...
Click to collapse
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Alin45 said:
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Click to expand...
Click to collapse
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Ghostface009 said:
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Click to expand...
Click to collapse
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Alin45 said:
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Click to expand...
Click to collapse
Maybe due to the difference between global and eu roms
Ik you gave all you can but what would you suggest to do for my situation in order to root this phone and pass safetynet again?
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Download the TWRP again.
Follow the guide with pictures: https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs steps up to step 13. Ignore step 8, 9 and the flash part of 12.
If this way still can't get you TWRP, then you might want to try latest MIUI by Xiaomi.eu. Read somewhere it has built in TWRP, so once flashed, you have TWRP. Verify yourself by reading in other posts though.
Remember
EEA (official) is different from Xiaomi.eu (custom ROM)
Click to expand...
Click to collapse
reg66 said:
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Click to expand...
Click to collapse
yep, the one I used was '2' version. I double checked for corruption and downloaded the same twrp again with same result :/
pl1992aw said:
Do Clean Flash custom ROMs
Click to expand...
Click to collapse
So my only way to get magisk again is flashing custom roms? it is how it is? :/
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
EDIT
I bought USB OTG adapter and can flash from usb stick, only problem is that i can't transfer files from PC to phone while in twrp.
Debeciak said:
I unlocked phone as normal and flashed twrp to slots A and B but in twrp it shows no internal storage, I tried every solution, but nothing worked. Only thing that worked was flashing xiaomi.eu stable via fastboot. When I enter twrp with xiaomi.eu flashed all files are shown, but i can't boot back into system (after restart it comes back to twrp). I don't really know what to do I can stick to stable xiaomi.eu, but I can't update it, I can't install any other custom rom, and MiFlash as always throws errors left and right. It's my first dual slot phone, before I didn't have any problems with other Xiaomi devices. I hope someone can help, things I tried:
-wipe everything
-change file format
-relock bootloader
-reflash twrp
-flashing different twrp
Thanks in advence if someone manage to help.
Click to expand...
Click to collapse
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
pl1992aw said:
You relock the bootloader, with Xiaomi.eu ??
Are you able to get to TWRP?
If you are not able to use TWRP, find Xiaomi repair center to revive your device.
Click to expand...
Click to collapse
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
TWRP is in alpha
Debeciak said:
I relocked and unlocked bootloader while there was no rom installed
I can enter twrp but i can't flash roms because internal storage is 0mb and on pc it's show unknow storage amount.
Click to expand...
Click to collapse
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
{
"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"
}
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
pl1992aw said:
Go into fastboot and boot twrp
Code:
fastboot boot twrp_file_name.img
Then format data
After it's done, reboot to fastboot and run the above command again to get to TWRP.
See if this help.
Click to expand...
Click to collapse
As I said I tried to wipe everything (including format data), pretty much everything that is on forum i tried it.
Robert314 said:
TWRP is in alpha
Click to expand...
Click to collapse
So it is twrp fault? And if it is will it maybe work in future?
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
Post screenshots what error it's showing to you, so people know what it means.
pl1992aw said:
Then MiFlash is your hope.
Use the 20210226 version.
Do not lock bootloader in MiFlash.
View attachment 5345137
Post screenshots what error it's showing to you, so people know what it means.
Click to expand...
Click to collapse
Phone is stuck on POCO screen right now. I used offical eea rom.
Debeciak said:
Phone is stuck on POCO screen right now. I used offical eea rom.
Click to expand...
Click to collapse
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
pl1992aw said:
Same as this:
https://forum.xda-developers.com/t/4284821/page-2#post-85174225
The answer to that problem from user:
https://forum.xda-developers.com/t/4284821/post-85174245
Click to expand...
Click to collapse
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Debeciak said:
But my phone didn't reboot into setup, it's stuck on logo and isn't starting.
Click to expand...
Click to collapse
Wait for it.
It takes some time for first booting. (wait 10 minutes)
pl1992aw said:
Wait for it.
It takes some time for first booting.
Click to expand...
Click to collapse
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Debeciak said:
I waited for like 15 minutes and I'm pretty sure the phone vibrates from time to time.
Click to expand...
Click to collapse
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Debeciak said:
I also am trying to download latest official rom but server is very bad and it's pretty slow.
Click to expand...
Click to collapse
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Then use the built-in updater to update. Hope this work.
pl1992aw said:
You said your phone works if flashing xiaomi.eu stable via fastboot.
Maybe try Xiaomi.eu again, at least getting a working phone.
Click to expand...
Click to collapse
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Debeciak said:
I guess that's my only option but it's not ideal and I can only flash the one stable version that is avaible via fastboot. Thanks for trying to help if latest official won't work with MiFlash im gonna use xiaomi.eu. Maybe in the future twrp update will solve that issue.
Click to expand...
Click to collapse
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
pl1992aw said:
Try the built-in updater to update.
I read somewhere here saying you can flash update zip through built-in updater. (Tap the MIUI 12 icon a few times)
Read from Xiaomi.eu tutorial to update:
https://xiaomi.eu/community/threads...all-xiaomi-eu-rom-for-xiaomi-redmi-k40.60379/
If following their tutorial but you still cannot update, you can ask them how to, or read some replies there to see if there's similar cases.
Click to expand...
Click to collapse
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
I went through something like this as well.
As long as you can boot into fastboot. Then no worries. Just Flash the official stockrom. If something goes wrong. Reboot into fastboot (everytime you do something through fastboot. If you keep doing multiple processes, you'll keep having errors, always. Well that's what I went through. Rebooting into fastboot fixed my problem)
But your last pic declares that it was successfully flashed though.
Debeciak said:
The tutorial is how to update in case rom is fastboot variant since twrp is avaible xiaomi.eu roms are twrp only. It's working fine I will wait for new twrp version and then try.
Worst thing is that I can't go back to stock rom.
Click to expand...
Click to collapse
When u flash xiaomi.eu, u set up the pin/pattern code in order to decrypt the internal storage in twrp?
Idk what's happening there.
It's just, flash xiaomi.eu via fastboot, boot it and set up pin/pattern code, fastboot boot twrp.img, go to twrp, insert the pin or pattern to decrypt internal storage and flash the latest update from xiaomi eu, simple as that..
And I don't get what's the A or B slot thing, I didn't had to chose or touch any of that, I saw that thing in twrp but didn't touched it..