Related
I have a problem with the Nexus S. After unlocking and rooting I waited a few days and decided to put a custom rom on it. The device is a few days old.
I installed rom manager and clockwork, just installed through there for ease of use.
Anyways, it started, but just booted into recovery not wanting to boot phone, stuck at the google-splash.
I deleted everything, to no avail. Flashing roms from recovery brings up a bunch of error messages "aborting installation" "status 7" and "cannon't read xxx.zip". I tried installing a few different roms to see if the files were corrupt, but that didn't work either. So I formatted the sd card from my computer, thinking the "sd-card" might be bad, then it refused to read or mount it any other ways than "usb-storage". So i just booted and left it thinking the device was probably lost until I figured out how to restore via ADB.
I moved it and it was at the login screen for Axura (one of the roms) I logged in and thinking great, wanting to flash something else, did it again, and back to stuck at splash.
Anyway, what I really need is some sort of idiots guide to using adb, I'm on OS X and the terminal there drives me nuts - so, anyways, any of the above sounds familiar, I'd appreciated any help.
Trying to install it says:
Extract: Recovery
Extract: System
Symlink: Toolbox
Symlink: Iwulticall
Symlink: Busybox
Set: Permissions
Flash: Kernel
assert failed: write_raw_image (2/tmp/boot.img"-"boot")
E:Error in /sdcard/Axura....zip (status 7)
Installation aborted.
I've tried flashing from adb it just tells me "remote: write fail"
First things first, have you tried doing a factory reset/wipe of the phone? If so have you tried one of the ODIN tools to return it completely to stock and get rid of everything you've done?
If you haven't tried those things, I would start there. ADB isn't what you need to fix your phone. Also, what method did you use to root?
Haven't tried Odin yet, but pulled my work wintel-laptop from the dock and brought it home, so will probably try that.
So no, odin is not tried yet.
I rooted with "Superboot"-thing (the name should probably have been a tip off...)
The root however seemed to be a bit, well, not quite rooted, i couldn't really make it backup, it wrote one eventually, and then I tried installing a new mod and then all went down the toilet.
BTW - I think I need drivers for the pc to recognize the Nexus S but I can't find any...?
InvaderPastulio said:
Haven't tried Odin yet, but pulled my work wintel-laptop from the dock and brought it home, so will probably try that.
So no, odin is not tried yet.
I rooted with "Superboot"-thing (the name should probably have been a tip off...)
The root however seemed to be a bit, well, not quite rooted, i couldn't really make it backup, it wrote one eventually, and then I tried installing a new mod and then all went down the toilet.
BTW - I think I need drivers for the pc to recognize the Nexus S but I can't find any...?
Click to expand...
Click to collapse
You do indeed need drivers which you can find by clicking the root link in my sig and going to the link in the top of my thread (also, once all is said and done you can use my guide to root. You need to download one zip file and run a few commands and you're rooted). There are drivers for Windows there.
Derp, sorry, downloading them...
Thanks for your help, hoping it'll work. Only got the Nexus S because some bastard stole the Desire I was quite happy with.
...
Edit:
getting this: sending 'recovey' (3980 KB)... OKAY
writing 'recovey'... FAILED (remote: Unknown Partition)
InvaderPastulio said:
Derp, sorry, downloading them...
Thanks for your help, hoping it'll work. Only got the Nexus S because some bastard stole the Desire I was quite happy with.
...
Edit:
getting this: sending 'recovey' (3980 KB)... OKAY
writing 'recovey'... FAILED (remote: Unknown Partition)
Click to expand...
Click to collapse
reflash Clockwork Recovery via Fastboot.
Are you Nandroid backups working?
No backups are working, I've tried, I'm beginning to think the internal storage is damaged somehow.
edit: sending 'recovey' (3980 KB)... OKAY
writing 'recovey'... FAILED (remote: Unknown Partition)
Wat, it worked, I now have installed the su-2.3.6.1-ef-signed.zip
Steps from here? Should I attempt flashing a rom?
InvaderPastulio said:
No backups are working, I've tried, I'm beginning to think the internal storage is damaged somehow.
Click to expand...
Click to collapse
Try flashing a previous version of Clockwork Recovery (3.0.0.0 or greater; just not 3.0.0.5) via Fastboot.
zephiK said:
Try flashing a previous version of Clockwork Recovery (3.0.0.0 or greater; just not 3.0.0.5) via Fastboot.
Click to expand...
Click to collapse
So, flashed 3.0.0.0 trying GRI40-2.3.3 stock, but get error
Code:
E:Can't find misc
Finding update package...
Opening update package...
installing update
Update aborted
Edit:
If I try to mount either CACHE or sd-ext I get an error
InvaderPastulio said:
No backups are working, I've tried, I'm beginning to think the internal storage is damaged somehow.
edit: sending 'recovey' (3980 KB)... OKAY
writing 'recovey'... FAILED (remote: Unknown Partition)
Wat, it worked, I now have installed the su-2.3.6.1-ef-signed.zip
Steps from here? Should I attempt flashing a rom?
Click to expand...
Click to collapse
InvaderPastulio said:
So, flashed 3.0.0.0 trying GRI40-2.3.3 stock, but get error
Code:
E:Can't find misc
Finding update package...
Opening update package...
installing update
Update aborted
Edit:
If I try to mount either CACHE or sd-ext I get an error
Click to expand...
Click to collapse
If I understand correctly, you were able to flash the su file in 3.0.0.5, correct? Before you reverted to an older clockwork, did you try flashing a rom by any chance?
Whoops - double post, sorry about that.
kenvan19 said:
If I understand correctly, you were able to flash the su file in 3.0.0.5, correct? Before you reverted to an older clockwork, did you try flashing a rom by any chance?
Click to expand...
Click to collapse
Yes, I tried flashing several roms before writing the op and before reverting to 3.0.0.0. One worked eventhough the install told me it was aborted.
I've reformatted the "SD-card" several times.
Just now it gave me a write fail
Code:
T850:adb-fastboot user$ /Users/user/Desktop/adb-fastboot/fastboot flash boot /Users/usere/Desktop/GRI40-2.3.3-stock.zip
sending 'boot' (91238 KB)... OKAY
writing 'boot'... FAILED (remote: Write Fail)
T850:adb-fastboot user$
Edit:
Now it's telling me
Code:
Exceed blocks 0x00000165 > 0x0000001e
when attempting to fastboot flash the device.
Now it's telling me when I try to boot (instead of hanging at splash screen):
No boot or recovery img
I'm also unable to format any of the partitions from Recovery.
Seems the phone is bricked, no one seems to know what the partitions do and how you can restore them. I've pretty much been through every.
The phones memory is either ****ed or I'm just out of luck.
Get ur phone to download mode and try to flash a stock 2.3.1 rom. From the sgs i know that with the baserom and odin ur able to repartition ur phone. Havent used odin for ns yet but i could imagine that it works the same way. Hope u get it to work
Sent from my Nexus S using Tapatalk
shrooms90 said:
Get ur phone to download mode and try to flash a stock 2.3.1 rom. From the sgs i know that with the baserom and odin ur able to repartition ur phone. Havent used odin for ns yet but i could imagine that it works the same way. Hope u get it to work
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I've tried flashing a base rom, the problem is, that the memory/partitions are broken/do not exist, nothing can be flashed to it, "write error" and "Exceed blocks" is what I get when I try to flash anything. The internal memory is broken, I guess, I don't know, doesn't work, at any rate.
Wait a few minutes im gonna move my lazy a** to the computer and get odin for ns to check it out. Im really familiar to it and im gonna report if i find anything that could help u.
Sent from my Nexus S using Tapatalk
shrooms90 said:
Wait a few minutes im gonna move my lazy a** to the computer and get odin for ns to check it out. Im really familiar to it and im gonna report if i find anything that could help u.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Would be much appreciated, I tried, but the drivers for odin and stuff didn't make much sense to me, neither did the files I was supposed to download and load into it.
I'd appreciate it greatly, can't stand it not working,
ok im on the pc now. so as i understand u couldnt use odin cause the drivers wouldnt install?
Im gonna look for the download link to get odin.Meanwhile i found following threat, there u can see witch firmware u should download and how u should setup odin. look at post 8 and 9
http://forum.xda-developers.com/showthread.php?t=974337
Edit: do u have one of those http://forum.xda-developers.com/showthread.php?t=819551 ? couldnt find any other way to boot ns to download mode. u could try adb reboot download but somehow it didnt work for me but i can confirm that the resistor works.
Edit2: Sent u a pm
I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I
xnosajx said:
I am currently running the CMB r2c1
I am attempting to move to the stock rom (deodexed and rooted http://forum.xda-developers.com/showthread.php?t=2608129), but I am having issues getting the stock rom from asus to flash using twrp.
tried the WW and the US version along with the SD version. I've tried the full zip and unzipping as well. All fail.
Anyone have any suggestions on how to flash the stock rom? I
Click to expand...
Click to collapse
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Edit: http://droidbasement.com/db-blog/?p=3210
Sent from my DROID4 using Tapatalk
berndblb said:
Asus seems to sign the stock firmware zips this time around and CWM, and now it seems also TWRP can't flash it anymore. Which TWRP version did you try it with?
Why do you want to flash stock? To get to the 4.3 bootloader?
Right now the only solution seems to be to flash the stock revovery in fastboot, apply the update to 4.3, flash custom recovery again and install rom.
I look for the link to the stock recovery and post it in an edit.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.
xnosajx said:
Thanks for the help.
I do want to get to the 4.3 bootloader so that I can get to a different Rom. I will try the steps you have listed and let you know.
Click to expand...
Click to collapse
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason
berndblb said:
Just for future reference - because this is going to come up again and again - you did follow proper procedure:
Unzipped the downloaded firmware once and then tried to flash the resulting zip in TWRP?
And please: Which TWRP version?
Hint: There's a "Thanks" button at the bottom of each post for a reason
Click to expand...
Click to collapse
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.
xnosajx said:
I tried both zips: once without unzipping and once with. I am unsure of the twrp version I was using, because I flashed CWM right after I posted the original question. Going through my bookmarks that I created when I first went to CMB rom, it looks like it was 2.6.
I am still attempting to get the stock recovery flashed with no success. I tried the fastboot method, and it seems to work except that when I reboot, it still comes up with CWM. It also stops blinking on the RCK icon when it installs (kinda hangs). I tried fastboot devices and it shows me the following:
???????????? fastboot
I may have to come back and try again in the morning. I am falling asleep while typing.
Click to expand...
Click to collapse
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....
Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.
berndblb said:
Yep - good idea to quit if you are tired!
The return you get on 'fastboot devices' means your fastboot drivers are not working/incorrect.
If you issue the command
Code:
fastboot devices
the return has to be a long string of numbers and letters. Anything else, especially ???????, and no fastboot command will have any effect.
Depending on the PC you are using, find the correct drivers, which may be the Google Universal Naked drivers, install them and troubleshoot until you get a working fastboot connection.
Everything after that should be a breeze.....
Click to expand...
Click to collapse
I should have been more specific. Before I attempt the install of the recovery, I get this when I do fast boot devices:
Code:
C:\>fastboot devices
###d2bbce61c### fastboot
The #'s are actual numbers.
After I try to install the recovery image here is the output:
Code:
C:\>fastboot flash recovey recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 3.588s]
writing 'recovery'...
OKAY [ 3.182s]
finished. total time: 6.770s
C:\>fastboot devices
???????????? fastboot
c:\>
And the green flashing (around the icons) stops and hangs.
I have to hold down power to reboot after that.
sbdags said:
Looks to me like you have tried to flash a TF701 ROM onto the TF700.
Try CROMi-X 5.3 instead.
Click to expand...
Click to collapse
I'm an idiot...thanks. I'll try the CROMi-X 5.3
Hi I just bought a XT1039 today and it came with the new 5.1 build out of the bos.
I've been reading the forums and it seems like there's no sure way to root and/or flash TWRP on Lollipop?
Does anyone know how I can do that? Or do I have to roll back to Kit Kat or something? Please help!
spencerchong said:
Hi I just bought a XT1039 today and it came with the new 5.1 build out of the bos.
I've been reading the forums and it seems like there's no sure way to root and/or flash TWRP on Lollipop?
Does anyone know how I can do that? Or do I have to roll back to Kit Kat or something? Please help!
Click to expand...
Click to collapse
I have the xt1045 and I'm in the same boat. If I find a solution, I'll let you know.
Okay, CF-Auto-Root worked! The batch file says a red android will show up.. never did, but it worked anyway.
http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406
I have twrp for xt1039 & superuser 2.48
Sent from my XT1039 using Tapatalk
---------- Post added at 10:51 AM ---------- Previous post was at 10:50 AM ----------
5.1 with twrp 2.8.7.0
Sent from my XT1039 using Tapatalk
This one works with 5.1.. I would install after rooting with the above method.
http://forum.xda-developers.com/moto-g/4g-development/collection-somcom3xs-experimental-corner-t2996266
Hey there, can anyone tell me whether or not I can just use the TWRP version that can be downloaded on twrp.me?
I have the XT1039 with a unlocked bootloader and I am aiming to install TWRP and later CM/ResurrectionRemix if possible onto the device.
But first things first - TWRP is the thing that is missing. Anyone still using the phone?
cyrrel said:
Hey there, can anyone tell me whether or not I can just use the TWRP version that can be downloaded on twrp.me?
I have the XT1039 with a unlocked bootloader and I am aiming to install TWRP and later CM/ResurrectionRemix if possible onto the device.
But first things first - TWRP is the thing that is missing. Anyone still using the phone?
Click to expand...
Click to collapse
TWRP for peregrine is available on twrp.me and it works fine - not sure what you mean with "missing".
Missing just personally on my phone
Alright thx will have a closer look!
I need to bother you again.
I have downloaded the latest twrp for the device but seem to be unable to get it up and running.
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (8374 KB)...
OKAY [ 0.293s]
writing 'recovery'...
OKAY [ 0.301s]
finished. total time: 0.596s
fastboot reboot
rebooting...
finished. total time: 0.004s
Looking good, but after that - when I press vol - & power on I get into the fastboot menu. When choosing "recovery" in there, the screen goes black and nothing happens.
Any idea?
edit: I get a "mismatched partition size (recovery)" within fastboot... didn't notice until now. Any input on that?
cyrrel said:
Looking good, but after that - when I press vol - & power on I get into the fastboot menu. When choosing "recovery" in there, the screen goes black and nothing happens.
Any idea?
Click to expand...
Click to collapse
No idea. It works fine on my XT1039. Try "fastboot boot twrp.img" to see if it starts that way. If it does, you could try copying twrp.img to the phone using adb push or mtp, then flash it to the recovery partition from twrp's "install image" feature.
cyrrel said:
edit: I get a "mismatched partition size (recovery)" within fastboot... didn't notice until now. Any input on that?
Click to expand...
Click to collapse
Yes, that's normal. Ignore it.
Thx but somehow I wasn't able to get into recovery but every time in the system itself. Recovery was overwritten, I think. After 20 or so tries I finally managed to get it running.
Thx for your help
cyrrel said:
Thx but somehow I wasn't able to get into recovery but every time in the system itself. Recovery was overwritten, I think. After 20 or so tries I finally managed to get it running.
Thx for your help
Click to expand...
Click to collapse
Hi
Do you have any links for the process you used on your phone
I also have a xt1039 that's stock and am looking around for a guide for my phone.
Cheers
Sent from my SHIELD Tablet K1 using Tapatalk
Hey there, basically this was a good base for me: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine
cyrrel said:
Hey there, basically this was a good base for me: https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine
Click to expand...
Click to collapse
Thanks for that yeah that's got everything I need gonna have a go tonight...
Nothing much wrong with my stock rom just sick of it saying low storage so hoping marshmallow will sort that with using the sd card for internal storage
complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) then power off your device
4) go to fastboot mode
( by pressing vol- + power buttons simultaneously)
5) then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :
#reserved
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Thank you very much!!!! Was looking for this in a pretty long time!!!
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.
camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool
[EDIT:] I actually ended up solving this, as mentioned in the lower post, but I'm still having a bit of trouble with the part below where trying to flash twrp gives the error "FAILED (remote: Not allowed to flash (recovery))" so I'd still like help with that if possible. Thanks!
Hello,
I have a Pixel 3 that I got when it first came out, there was only one custom rom for it which I installed with TWRP, but the rom was kind of broken, so i just used the phone as a media player for a couple years, until I thought to check for new roms, and there are lots now. So I'm following the PixelDust installation instructions which say I absolutely must start by reverting stock rom. On my Samsung I used Odin, but there's nothing like that for this, except sources pointing to Android Flash Tool website, but after I tried flashing with that site, it just went into bootloader and said "no valid slots to boot", so it evidently failed. So my next thought was to flash it manually, so I downloaded the latest Blueline image from here. I'm using this guide, but it says to extract the zip and use the flash-all command, but when I extract this image I only get these files (see screenshot attachment). Another guide says there will be a file in that folder that I should extract that too but the only one that makes any sense is payload.bin and 7zip doesn't recognize that. And I haven't been able to get anything really comprehensible through Google searches. So I'm at a dead end. :/
So basically I'm hoping someone can give me a step-by-step instruction how to flash this rom. I'm not really a tech guy but I have a basic understanding, I've used ADB and fastboot before, following instructions though. If you can take the time to give me an idiot-proof instruction I'd really appreciate it because at the moment the phone's useless
Thanks!
EDIT:
I actually tried to at least flash TWRP so I could try to restore my nandroid of the other rom, but when I tried, I got the error:
Code:
D:\D Backup\Misc\nandroid\adbfastboot samsung a5>fastboot flash recovery
twrp-3.4.0-0-twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (4560 KB)...
OKAY [ 0.255s]
writing 'recovery'...
[B]FAILED (remote: Not allowed to flash (recovery))[/B]
finished. total time: 0.317s
And searches on that said it was because the bootloader is locked... but it's not. So I don't know why I can't even do that. :/ I'd like to at least get to something functional. >.< So I'd appreciate any help. Thanks!
Okay, well good news, I figured the main thing out by accident. I didn't realize there was a difference between factory image and ota image and I guess I got the ota, not the factory, which was when I unzipped it it just had meta-inf and not flash-all. But I also discovered how to sideload that ota and i did that, and now the phone is back to stock, hooray!
But I'm still having trouble getting TWRP back on it for the same reason listed above, so can you guys help me with that part?
lol thanks ^^;
PistolSlap said:
Hello,
I have a Pixel 3 that I got when it first came out, there was only one custom rom for it which I installed with TWRP, but the rom was kind of broken, so i just used the phone as a media player for a couple years, until I thought to check for new roms, and there are lots now. So I'm following the PixelDust installation instructions which say I absolutely must start by reverting stock rom. On my Samsung I used Odin, but there's nothing like that for this, except sources pointing to Android Flash Tool website, but after I tried flashing with that site, it just went into bootloader and said "no valid slots to boot", so it evidently failed. So my next thought was to flash it manually, so I downloaded the latest Blueline image from here. I'm using this guide, but it says to extract the zip and use the flash-all command, but when I extract this image I only get these files (see screenshot attachment). Another guide says there will be a file in that folder that I should extract that too but the only one that makes any sense is payload.bin and 7zip doesn't recognize that. And I haven't been able to get anything really comprehensible through Google searches. So I'm at a dead end. :/
So basically I'm hoping someone can give me a step-by-step instruction how to flash this rom. I'm not really a tech guy but I have a basic understanding, I've used ADB and fastboot before, following instructions though. If you can take the time to give me an idiot-proof instruction I'd really appreciate it because at the moment the phone's useless
Thanks!
EDIT:
I actually tried to at least flash TWRP so I could try to restore my nandroid of the other rom, but when I tried, I got the error:
Code:
D:\D Backup\Misc\nandroid\adbfastboot samsung a5>fastboot flash recovery
twrp-3.4.0-0-twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (4560 KB)...
OKAY [ 0.255s]
writing 'recovery'...
[B]FAILED (remote: Not allowed to flash (recovery))[/B]
finished. total time: 0.317s
And searches on that said it was because the bootloader is locked... but it's not. So I don't know why I can't even do that. :/ I'd like to at least get to something functional. >.< So I'd appreciate any help. Thanks!
Click to expand...
Click to collapse
PistolSlap said:
Okay, well good news, I figured the main thing out by accident. I didn't realize there was a difference between factory image and ota image and I guess I got the ota, not the factory, which was when I unzipped it it just had meta-inf and not flash-all. But I also discovered how to sideload that ota and i did that, and now the phone is back to stock, hooray!
But I'm still having trouble getting TWRP back on it for the same reason listed above, so can you guys help me with that part?
lol thanks ^^;
Click to expand...
Click to collapse
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
dcarvil said:
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
Click to expand...
Click to collapse
THIS! theres no functional twrp and it looks like there may not be one at all. i recently reverted to android 10 so that i could go back to DirtyUnicors. i recommend waiting awhile longer for stable R ROMs.
Ok but this happened with Android 8. I didn't flash the latest image but actually the earliest. And come to think of it it happened even before the flash when there wasn't even an OS at that point. (The phone was wiped but no OS was installed.) so I tried it both then and after I got Android 8 installed and same disallowed error.
dcarvil said:
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
Click to expand...
Click to collapse
PistolSlap said:
Ok but this happened with Android 8. I didn't flash the latest image but actually the earliest. And come to think of it it happened even before the flash when there wasn't even an OS at that point. (The phone was wiped but no OS was installed.) so I tried it both then and after I got Android 8 installed and same disallowed error.
Click to expand...
Click to collapse
Are you sure you are on Android 8? The Pixel 3 shipped with Android 9. There is no Android 8 for the Pixel 3 listed in the link you gave in your original post.
If you really are on Android 8, or even Android 9, try the instructions on the Pixel 3 TWRP website at https://twrp.me/google/googlepixel3.html. The instructions you listed in your original post are for a Nexus 6, not a Pixel 3.
dcarvil said:
Are you sure you are on Android 8? The Pixel 3 shipped with Android 9. There is no Android 8 for the Pixel 3 listed in the link you gave in your original post.
If you really are on Android 8, or even Android 9, try the instructions on the Pixel 3 TWRP website at https://twrp.me/google/googlepixel3.html. The instructions you listed in your original post are for a Nexus 6, not a Pixel 3.
Click to expand...
Click to collapse
Ah sorry I meant Android 9.
Okay, cool I followed those instructions and it worked. Thanks! I'm not sure what I did wrong before.
One other question: My older phone is a Samsung Galaxy A5, which doesn't have A/B slots, and I've looked into it but I'm still not exactly sure how they work. Is it correct that they're both system images? So if I have stock in slot A can I install a custom rom in slot B and switch between them? Or have I got that wrong?
Also, when I was first flashing a rom onto this Pixel 3, I tried to do a nandroid backup, which for some reason failed to restore properly, and someone mentioned it was because it was a slot device? So does that mean nandroid backups don't work on the PIxel 3?
Thanks for your help. I'm not a compsci guy or android dev, so this stuff takes a bit more for me to quite understand. :")
PistolSlap said:
Ah sorry I meant Android 9.
Okay, cool I followed those instructions and it worked. Thanks! I'm not sure what I did wrong before.
One other question: My older phone is a Samsung Galaxy A5, which doesn't have A/B slots, and I've looked into it but I'm still not exactly sure how they work. Is it correct that they're both system images? So if I have stock in slot A can I install a custom rom in slot B and switch between them? Or have I got that wrong?
Also, when I was first flashing a rom onto this Pixel 3, I tried to do a nandroid backup, which for some reason failed to restore properly, and someone mentioned it was because it was a slot device? So does that mean nandroid backups don't work on the PIxel 3?
Thanks for your help. I'm not a compsci guy or android dev, so this stuff takes a bit more for me to quite understand. :")
Click to expand...
Click to collapse
I have no experience with TWRP on a Pixel 3, so I can't answer your question about nandroid backups. Perhaps someone else can answer. The question on the A5 should be asked in a different forum.
The difference in the instructions for the Nexus 6 and Pixel 3, is that you boot TWRP, then install from TWRP for the Pixel 3.