Hi,
there any method to downgrade from last beta of android 13 down to last stable?
I tried to side load the old one but nothing....
Matuto1981 said:
Hi,
there any method to downgrade from last beta of android 13 down to last stable?
I tried to side load the old one but nothing....
Click to expand...
Click to collapse
You have to flash boot and vendor files and sideloaded ROM with 1,14
I tried but it doesn't work. side load fails, and up with message Side load not possible due packager is older than current build ad downgrade not allowed......
I can flash boot and vendor_boot in fast boot this is ok.
I go to recovery add side load.....but side load fails.
jb232 said:
You have to flash boot and vendor files and sideloaded ROM with 1,14
Click to expand...
Click to collapse
I tried but it doesn't work. side load fails, and up with message Side load not possible due packager is older than current build ad downgrade not allowed......
I can flash boot and vendor_boot in fast boot this is ok.
I go to recovery add side load.....but side load fails.
Matuto1981 said:
I tried but it doesn't work. side load fails, and up with message Side load not possible due packager is older than current build ad downgrade not allowed......
I can flash boot and vendor_boot in fast boot this is ok.
I go to recovery add side load.....but side load fails.
Click to expand...
Click to collapse
Weird , i flashed my phone successfully, EEA region
I had flashed 1,13 or 1,14 manually after OTA to 1,1,7
jb232 said:
I had flashed 1,13 or 1,14 manually after OTA to 1,1,7
Click to expand...
Click to collapse
I'm currently on 1.5.1
i flashed the 1.1.7 via side load but fails as it's it says downgrade not possible.
don't know what to do
Matuto1981 said:
I'm currently on 1.5.1
i flashed the 1.1.7 via side load but fails as it's it says downgrade not possible.
don't know what to do
Click to expand...
Click to collapse
Maybe the Qualcomm drivers are not correctly installed, also you can try another cable
jb232 said:
Maybe the Qualcomm drivers are not correctly installed, also you can try another cable
Click to expand...
Click to collapse
no beccasse cable it's working as it's flash rom with no problem.
ufs....any other idea?
Matuto1981 said:
no beccasse cable it's working as it's flash rom with no problem.
ufs....any other idea?
Click to expand...
Click to collapse
Try older zip with older build
Related
The phone is/was a stock VS9803AA. I finally got root to work with using the One Click Root. Next I was working on installing TWRP. I flashed the TWRP image 2.8.5 from the link on this tutorial: http://forum.xda-developers.com/showthread.php?t=2449670. After doing that, when I try to reboot into recovery, a grey screen with a Critical Error is displayed. DemiGod Crash Handler : Critical Error! Press any key to choose Dload Mode or Reboot. Rebooting the phone lets it boot up normally, but at higher brightness levels the edges of the screen sort of flash, like a bad refresh rate on a monitor. I flashed the TWRP image using dd. Any ideas on how to fix it? I am trying to get TWRP on there so I can flash CM 12.1
Installed Flashify and used that to flash TWRP 2.8.6.0 and it has the same problem. I don't think the issue is the TWRP version used, must be something else?
Oxyacetylene said:
The phone is/was a stock VS9803AA. I finally got root to work with using the One Click Root. Next I was working on installing TWRP. I flashed the TWRP image 2.8.5 from the link on this tutorial: http://forum.xda-developers.com/showthread.php?t=2449670. After doing that, when I try to reboot into recovery, a grey screen with a Critical Error is displayed. DemiGod Crash Handler : Critical Error! Press any key to choose Dload Mode or Reboot. Rebooting the phone lets it boot up normally, but at higher brightness levels the edges of the screen sort of flash, like a bad refresh rate on a monitor. I flashed the TWRP image using dd. Any ideas on how to fix it? I am trying to get TWRP on there so I can flash CM 12.1
Click to expand...
Click to collapse
Hi!
I'm having the same problem. Can't get into recovery to install custom rom.
did you fix it?
Oxyacetylene said:
The phone is/was a stock VS9803AA. I finally got root to work with using the One Click Root. Next I was working on installing TWRP. I flashed the TWRP image 2.8.5 from the link on this tutorial: http://forum.xda-developers.com/showthread.php?t=2449670. After doing that, when I try to reboot into recovery, a grey screen with a Critical Error is displayed. DemiGod Crash Handler : Critical Error! Press any key to choose Dload Mode or Reboot. Rebooting the phone lets it boot up normally, but at higher brightness levels the edges of the screen sort of flash, like a bad refresh rate on a monitor. I flashed the TWRP image using dd. Any ideas on how to fix it? I am trying to get TWRP on there so I can flash CM 12.1
Click to expand...
Click to collapse
have a look at skr tools and see if it has an option.for your problem.. and the most easiest thing would be to go back to stock rom.. and start from there
raptorddd said:
have a look at skr tools and see if it has an option.for your problem.. and the most easiest thing would be to go back to stock rom.. and start from there
Click to expand...
Click to collapse
Can i flash stock VS98039a? I am currently on VS9803aa.
SkuLL. said:
Can i flash stock VS98039a? I am currently on VS9803aa.
Click to expand...
Click to collapse
I dont know what he numbers mean.? but what are they KITKAT or LP.?
raptorddd said:
I dont know what he numbers mean.? but what are they KITKAT or LP.?
Click to expand...
Click to collapse
Lollipop
SkuLL. said:
Lollipop
Click to expand...
Click to collapse
but i do not understand whats your point.? what do you want to do , need more info..
raptorddd said:
but i do not understand whats your point.? what do you want to do , need more info..
Click to expand...
Click to collapse
I am on software version VS9803aa, can i restore it to VS98039a? I am having problem installing TWRP on 3aa.
SkuLL. said:
I am on software version VS9803aa, can i restore it to VS98039a? I am having problem installing TWRP on 3aa.
Click to expand...
Click to collapse
am not familiar with those numbers.. but if its a stock rom.. yes.. if is flashable its ok its its thru flash tools .its okey so you may fix some rom problem installation..
I tried to restored a nandroid backup which didnt work, I then tried to lock and unlock bootloader thinking recovery would reset original image and that didnt work and now its wiped. Any suggestions as I'm looping into bootloader screen and I cant even push an image using adb.
Have you tried formatting your data in TWRP?
sting5566 said:
Have you tried formatting your data in TWRP?
Click to expand...
Click to collapse
Yes. But I have no way so far to get an oxygen os rom to my internal storage so I can flash. Just keeps going to fastboot mode.
Did you try reinstalling Twrp thru fastboot?
sting5566 said:
Did you try reinstalling Twrp thru fastboot?
Click to expand...
Click to collapse
How would that help if I have nothing to flash? I can get to twrp no problem.
SysAdmNj said:
How would that help if I have nothing to flash? I can get to twrp no problem.
Click to expand...
Click to collapse
You stated it kept going back into fastboot, sorry if I misunderstood. Your PC should see the phone while in TRWP, try another port on your PC or another cable.
sting5566 said:
You stated it kept going back into fastboot, sorry if I misunderstood. Your PC should see the phone while in TRWP, try another port on your PC or another cable.
Click to expand...
Click to collapse
Yes, my phone is wiped and no OS on it either. Thats probably why its going back to fastboot. Is my only choice to unbrick? Which as I'm seeing would require me to go to hydrogen os before even being able to go to oxygen os?
SysAdmNj said:
Yes, my phone is wiped and no OS on it either. Thats probably why its going back to fastboot. Is my only choice to unbrick? Which as I'm seeing would require me to go to hydrogen os before even being able to go to oxygen os?
Click to expand...
Click to collapse
Even with it wiped, if you have TWRP installed and no OS you should still boot back into recovery, not fastboot. I would still try installing TWRP again, use the codeworkx version, seems to work best for most people.
sting5566 said:
Even with it wiped, if you have TWRP installed and no OS you should still boot back into recovery, not fastboot. I would still try installing TWRP again, use the codeworkx version, seems to work best for most people.
Click to expand...
Click to collapse
Ok so I'm definitely not understanding, once I install twrp codeworkx version then whats my next step to get my device up and running?
SysAdmNj said:
Ok so I'm definitely not understanding, once I install twrp codeworkx version then whats my next step to get my device up and running?
Click to expand...
Click to collapse
After that I would format data in TWRP, reboot back into TWRP and then copy over a rom. Your PC should see the phone plugged in booted up in TWRP.
sting5566 said:
After that I would format data in TWRP, reboot back into TWRP and then copy over a rom. Your PC should see the phone plugged in booted up in TWRP.
Click to expand...
Click to collapse
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
SysAdmNj said:
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
Click to expand...
Click to collapse
Glad it worked out for you. What rom were you trying to flash and why magisk 14, newer ones are out now.
sting5566 said:
Glad it worked out for you. What rom were you trying to flash and why magisk 14, newer ones are out now.
Click to expand...
Click to collapse
OOS 5.0.1 latest version of oreo for oneplus 5 is what I flashed and running now. Now I'm attemping to flash magisk, latest version and hopefully dont run into the black screen.
SysAdmNj said:
OOS 5.0.1 latest version of oreo for oneplus 5 is what I flashed and running now. Now I'm attemping to flash magisk, latest version and hopefully dont run into the black screen.
Click to expand...
Click to collapse
The latest xXx rom is close to stock and runs great if you want to try something custom.
SysAdmNj said:
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
Click to expand...
Click to collapse
It's a known issue. You have to use Magisk 15.2 or higher.
If you flash an older version you will get a black screen with a blue notification led.
maikvitesse said:
It's a known issue. You have to use Magisk 15.2 or higher.
If you flash an older version you will get a black screen with a blue notification led.
Click to expand...
Click to collapse
Yes, I learned the hard way
I thought I could flash 14 and just update to 15.2.
sting5566 said:
The latest xXx rom is close to stock and runs great if you want to try something custom.
Click to expand...
Click to collapse
I actually want to stay close to stock. I dont even want to use nova launcher, I"m staying with OP launcher. So far so good, Not sure upgrade was worth the trouble yet
Am trying to flash TWRP to my (SM-G935F) S7 Edge Nougat 7.0
No matter which TWRB of the 11 versions i flash it does not work
Either give me a Total RED SCREEN (The last 3 or 4 versions) or give me Recovery is not Seandroid Enforcing (Older Versions) and freeze
Am using the latest Odin v3.12
I don't know what to do please help
koshac4 said:
Am trying to flash TWRP to my (SM-G935F) S7 Edge Nougat 7.0
No matter which TWRB of the 11 versions i flash it does not work
Either give me a Total RED SCREEN (The last 3 or 4 versions) or give me Recovery is not Seandroid Enforcing (Older Versions) and freeze
Am using the latest Odin v3.12
I don't know what to do please help
Click to expand...
Click to collapse
Hello,these are my steps for obtaining TWRP.First i use cf-root and then download TWRP official app,from there you will have option to flash latest image 3.2.1.-1.Try that if you want.good luck
darksx said:
Hello,these are my steps for obtaining TWRP.First i use cf-root and then download TWRP official app,from there you will have option to flash latest image 3.2.1.-1.Try that if you want.good luck
Click to expand...
Click to collapse
hey man
i have done that
i obtained the 11 version of TWRB and tried to flash all of them from the official website but it gives me RED screen on the last 6 versions and the error message above on 2 versions and the rest the screen just freeze
What do u mean by using CF-ROOT!?
koshac4 said:
hey man
i have done that
i obtained the 11 version of TWRB and tried to flash all of them from the official website but it gives me RED screen on the last 6 versions and the error message above on 2 versions and the rest the screen just freeze
What do u mean by using CF-ROOT!?
Click to expand...
Click to collapse
As i described as above i usually use the second method.So i first root my device with cf-root package,you will find that in firmware.mobi,and then i flash twrp image with Twrp app itself or you can flash it with flashify.But in your case i don't know what's wrong.Are you using correct twrp version.
darksx said:
As i described as above i usually use the second method.So i first root my device with cf-root package,you will find that in firmware.mobi,and then i flash twrp image with Twrp app itself or you can flash it with flashify.But in your case i don't know what's wrong.Are you using correct twrp version.
Click to expand...
Click to collapse
See am not 100% which is the right TWRP version but i tried them all and no use
Yesterday it took me 6 hours to figure out the stock and flash it back to normal and now idk how to do it
I need like exact numbers and figuers and name for the versions as i tried the thread on xda but the TWRB couldn't be loaded from the boot to start with
Can u help!?
koshac4 said:
See am not 100% which is the right TWRP version but i tried them all and no use
Yesterday it took me 6 hours to figure out the stock and flash it back to normal and now idk how to do it
I need like exact numbers and figuers and name for the versions as i tried the thread on xda but the TWRB couldn't be loaded from the boot to start with
Can u help!?
Click to expand...
Click to collapse
If you have SM-G935F and i see you have but check again just to on the safe side here is the link for recovery
https://eu.dl.twrp.me/hero2lte/ .Did you flash that version.
darksx said:
If you have SM-G935F and i see you have but check again just to on the safe side here is the link for recovery
https://eu.dl.twrp.me/hero2lte/ .Did you flash that version.
Click to expand...
Click to collapse
Every single one of them
koshac4 said:
Every single one of them
Click to expand...
Click to collapse
This is really strange,yesterday i have rooted and flashed twrp without any problems.Did you maybe ticked option OEM unlock in developers option.
darksx said:
This is really strange,yesterday i have rooted and flashed twrp without any problems.
Click to expand...
Click to collapse
Which version of them though!?
I tried all the 11
The leatest 5 or 6 gives me a red screen and older ones freeze or recovery is not seandroid enforcing and also freezez
koshac4 said:
Which version of them though!?
I tried all the 11
The leatest 5 or 6 gives me a red screen and older ones freeze or recovery is not seandroid enforcing and also freezez
Click to expand...
Click to collapse
I always flash the latest,so in this case 3.2.1-1
darksx said:
I always flash the latest,so in this case 3.2.1-1
Click to expand...
Click to collapse
Nop just a very red screen that not making u able to do anything then i restart back again to download mode
I have the same problem,
My red screen problem,
I had to use odin v3.16 and old twrp version twrp-3.1.1-0-hero2lte.img.tar because of een red screen after booting with the newest odin and twrp.
After installing this old twrp, I could install, within twrp, the new image twrp-3.2.3-0-hero2lte.img, which I put already put on the sd card.
I flashed twrp on boot using fastboot instead of on recovery and was stuck in a bootloop. So I found a stock boot img online and flashed that back onto boot and now it boots but wifi won't turn on anymore.
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
Found it, will try it now thank you.
oreo27 said:
Get the fastboot rom which corresponds to your device version from here:
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
Extract the boot.img from the archive and flash it using fastboot. That should get your WiFi going again.
Click to expand...
Click to collapse
I have no idea how to go about using a python script to unpack the OTA images from the file. What should I do?
Don't download the OTA image. Download the fastboot image. Use 7-zip to extract.
There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.
racer1077 said:
There's no fastboot image for my version and I have tried a diff version from there and it boots but doesn't fix the wifi problem.
Click to expand...
Click to collapse
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.
oreo27 said:
What version are you on? I believe all the Fastboot versions are present in that thread. If you're on a newer version that 8.1.10, you'll need to flash 8.1.10 first, effectively downgrading. Then you can update to a higher version using the system's in-built updater.
Click to expand...
Click to collapse
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.
racer1077 said:
Android 8.0.0 [OPR1.170623.026.V9.5.4.0.ODHMIFA]. I'm on 8.0 still but it has a different build number. I have tried the boot.img from this one (Android 8.0.0 [OPR1.170623.026.8.1.10]) but it didnt work.
Click to expand...
Click to collapse
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".
oreo27 said:
Yup. You're on the same version as me. It does not yet have a fastboot ROM indeed. You will need to downgrade.
Flash the entire (Android 8.0.0 [OPR1.170623.026.8.1.10]) ROM in Xiaomi Flash and choose "Save user Data".
Click to expand...
Click to collapse
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.
racer1077 said:
Miflash says it flashes successfully, however it doesn't reboot and after manually rebooting it isn't flashed.
Edit: Upon checking the log there was a problem with file location and right now I'm trying to flash it again.
Edit: IT WORKED!! After flashing the entire ROM wifi now works again properly. Thank you so much for helping me through all this.
Click to expand...
Click to collapse
Mi Flash doesn't seem to accept spaces in the path of the firmware so that was probably the issue. No worries! You'll want to update to the latest version using the system updater to get back on your actual version.
Hello, i have a problem with my phone , i don t know if the screen was replaced or not because i bought it used. I had android 7 and now i have android 9 , i didnt use the phone for a long time and now i did turn it on saw updates from 7 to 8.1 and then the touch stopped working so i saw there is an update from 8.1 to 9 and did that to (with a mouse and otg) but still nothing.
Main problems:
-touch screen still not working
-bootloader binary 5(so i can t downgrade to android 7)
Any ideas how to downgrade or any fix for the touch on android 9?
Thanks
BlackMist21 said:
Hello, i have a problem with my phone , i don t know if the screen was replaced or not because i bought it used. I had android 7 and now i have android 9 , i didnt use the phone for a long time and now i did turn it on saw updates from 7 to 8.1 and then the touch stopped working so i saw there is an update from 8.1 to 9 and did that to (with a mouse and otg) but still nothing.
Main problems:
-touch screen still not working
-bootloader binary 5(so i can t downgrade to android 7)
Any ideas how to downgrade or any fix for the touch on android 9?
Thanks
Click to expand...
Click to collapse
Usually Samsung bootloaders are backwards compatible, so you may still be able to downgrade.
You could also just try using the touch screen binaries from Android 7.
ashyx said:
Usually Samsung bootloaders are backwards compatible, so you may still be able to downgrade.
You could also just try using the touch screen binaries from Android 7.
Click to expand...
Click to collapse
Tried and it always come an error of bootloader 5 and the one i try to install is 4,
I used odin usual steps is there any other way?
BlackMist21 said:
Tried and it always come an error of bootloader 5 and the one i try to install is 4,
I used odin usual steps is there any other way?
Click to expand...
Click to collapse
Which parts are you attempting to install?
Just don't flash the bootloader.
ashyx said:
Which parts are you attempting to install?
Just don't flash the bootloader.
Click to expand...
Click to collapse
So you say i should try like this
From android 9 to android 8.1 with odin i should load only ap/cp/csc and for bl ?should i let it empty or add the one from android 9?
so i tried adding cp,cp,csc with empty bl doesnt even start, i tried with cp,ap,csc from 8.1 and bl from 9 it gave me error your binary 3 and using binary 2? wth?
can you help me thkx
BlackMist21 said:
So you say i should try like this
From android 9 to android 8.1 with odin i should load only ap/cp/csc and for bl ?should i let it empty or add the one from android 9?
so i tried adding cp,cp,csc with empty bl doesnt even start, i tried with cp,ap,csc from 8.1 and bl from 9 it gave me error your binary 3 and using binary 2? wth?
can you help me thkx
Click to expand...
Click to collapse
Just flash ap only. Be aware you will also need to factory reset, so make sure you are oem unlocked.
Kernel rev check fail 3 binary 2
BlackMist21 said:
Kernel rev check fail 3 binary 2
Click to expand...
Click to collapse
All I can suggest is Install twrp and flash the kernel with that.
However you will need to pull out the boot.img from the AP tar file.
What kernel should i flash and ap? 8.1 o 7?
BlackMist21 said:
What kernel should i flash and ap? 8.1 o 7?
Click to expand...
Click to collapse
Basically you need to remove the boot.img from the AP tar archive then install the rest of the AP file without the boot.img using ODIN.
Then install twrp and flash the boot.img.
Format data and reboot.
ashyx said:
Basically you need to remove the boot.img from the AP tar archive then install the rest of the AP file without the boot.img using ODIN.
Then install twrp and flash the boot.img.
Format data and reboot.
Click to expand...
Click to collapse
i didnt tried that yet, but if i try are chances that o brick my phone?
if it will work after format and reboot i can put custom rom like prometheus and will fix my problem?
thanks and sorry for bothering you
BlackMist21 said:
i didnt tried that yet, but if i try are chances that o brick my phone?
if it will work after format and reboot i can put custom rom like prometheus and will fix my problem?
thanks and sorry for bothering you
Click to expand...
Click to collapse
There's a chance It may soft brick it. However soft bricks are fully recoverable by simply flashing the stock firmware or just restoring a backup.
thanks again for your answer i ended up tryng twrp and a custom rom the problem, i always end in bootloop.
I see very custom rom i try have the option to root but i always say no, is this the problem?
BlackMist21 said:
thanks again for your answer i ended up tryng twrp and a custom rom the problem, i always end in bootloop.
I see very custom rom i try have the option to root but i always say no, is this the problem?
Click to expand...
Click to collapse
Depends on the custom rom. If its based on stock dm-verity will need to be disabled. Rooting will accomplish this.
If its based on lineage or other aosp sources then it shouldn't be necessary.
However a format of data will be required either way.
ok managed to install clean nougat stock, problem rests still no touch, any idea?
and no network
BlackMist21 said:
ok managed to install clean nougat stock, problem rests still no touch, any idea?
and no network
Click to expand...
Click to collapse
How did you install the rom?
Does touch work in twrp?
ashyx said:
How did you install the rom?
Does touch work in twrp?
Click to expand...
Click to collapse
touch does not work in twrp
rom installed by twrp
does it means that my touch is really dead if not working in twrp?
BlackMist21 said:
touch does not work in twrp
rom installed by twrp
does it means that my touch is really dead if not working in twrp?
Click to expand...
Click to collapse
Maybe, but it depends on the twrp version you are using.
Try a build based on nougat.
This was one of my early builds before it became official.
https://forum.xda-developers.com/ga...nt/twrp-3-1-1-1-j7-pro-sm-j730f-g-gm-t3662621
ashyx said:
Maybe, but it depends on the twrp version you are using.
Try a build based on nougat.
Click to expand...
Click to collapse
i tried clean nougat stock, and notworking the touch not working and no imei
BlackMist21 said:
i tried clean nougat stock, and notworking the touch not working and no imei
Click to expand...
Click to collapse
See edit above.