Related
Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pEl Use 7-zip or winrar to extract the files.
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the occam-ktu85l-Modified folder to open a command window in the correct folder. ADB/FASTBOOT must be intalled on your PC.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
jd1639 said:
Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/Uql Use 7-zip or winrar to extract the files.
Mirror https://mega.co.nz/#!0Zoi3DoL!OXm5H6HBzwGd8PEPlNfTQphcSAoM4zN8MG5LX3YzK7g
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the occam-ktu85l-Modified folder to open a command window in the correct folder.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
Click to expand...
Click to collapse
folder image-occam-ktu84l.zip has recovery.img,this stock recovery?
pincher65 said:
folder image-occam-ktu84l.zip has recovery.img,this stock recovery?
Click to expand...
Click to collapse
Yes it's stock. Sorry about that it has been corrected
Sent from my Nexus 5 using XDA Free mobile app
i have error:
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
szakalq said:
i have error:
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
Click to expand...
Click to collapse
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
This worked for me! Thanks
Sent from my Nexus 4 using Tapatalk
jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
Now everything is fine, thank you
i downloaded occam-ktu84l-MODIFIED , connected Nexus 4 on my ubuntu in fastboot and ran script flash-all.sh but nothing happens , just < waiting for device > is shown.
can i install this zip it from custom recovery?
mrYogii said:
i downloaded occam-ktu84l-MODIFIED , connected Nexus 4 on my ubuntu in fastboot and ran script flash-all.sh but nothing happens, just waiting for device is shown.
can i install this zip it from custom recovery?
Click to expand...
Click to collapse
install drivers adb/fastboot, enable usb debug?http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
pincher65 said:
install drivers adb/fastboot, enable usb debug?http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
all is set , adb devices gives device id
mrYogii said:
all is set , adb devices gives device id
Click to expand...
Click to collapse
adb? You needed fastboot mode
jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
hi, this works for me also, thanks a lot, plz update OP for others also.
Flashed successful as well as new radio however flashing superuser though recovery does nothing... How to fix?
jd1639 said:
That's weird. Try this and please let me know if it works https://mega.co.nz/#!AAATiKpI!PJbBgroM6PB7tTAs_TanCOrlzAeqBq0PEupNyvU72pE
Click to expand...
Click to collapse
works great! thanks!
Worked great! all though i had to flash one-by-one cause i dont know how to use adb :cyclops:
my situation
Hello guys
I have tried to enter the adb commands into the command prompt but it says they are unrecognised and I dont know exactly why the adb will not fucntionhttp://forum.xda-developers.com/images/smilies/confused.gif. I think I may have disabled USB debuging by mistake before I had the bootloop.
BTW does this stock image work for the NEXUS 7 device
Gloftking said:
Hello guys
I have tried to enter the adb commands into the command prompt but it says they are unrecognised and I dont know exactly why the adb will not fucntionhttp://forum.xda-developers.com/images/smilies/confused.gif. I think I may have disabled USB debuging by mistake before I had the bootloop.
BTW does this stock image work for the NEXUS 7 device
Click to expand...
Click to collapse
First, it will not work on the n7. Just double click on the flash-all.bat file. Easier than entering any commands, they're fastboot commands by the way
Sent from my Nexus 5 using XDA Free mobile app
?
if it cannot work on the nexus 7 then for me there isnt much point. isnt there anything else that will be able to fix that
Gloftking said:
if it cannot work on the nexus 7 then for me there isnt much point. isnt there anything else that will be able to fix that
Click to expand...
Click to collapse
Then what are you doing in the n4 forum? Go to the n7 forum
Sent from my Nexus 5 using XDA Free mobile app
?
could you tell me were that is?
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img
rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.
Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*
rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea
faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
evan7899 said:
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
Click to expand...
Click to collapse
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
simms22 said:
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
Click to expand...
Click to collapse
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
evan7899 said:
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
Click to expand...
Click to collapse
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
simms22 said:
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
evan7899 said:
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
Click to expand...
Click to collapse
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
simms22 said:
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
Click to expand...
Click to collapse
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
evan7899 said:
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
Click to expand...
Click to collapse
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
simms22 said:
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
Click to expand...
Click to collapse
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
evan7899 said:
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
Click to expand...
Click to collapse
honestly, I wouldn't know what you need on a Mac to get it working :angel:
simms22 said:
honestly, I wouldn't know what you need on a Mac to get it working :angel:
Click to expand...
Click to collapse
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
evan7899 said:
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
Click to expand...
Click to collapse
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
You need to run sudo fastboot insertcomand on Mac. good luck.
simms22 said:
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
Thanks but we have tired that. Due to distance this has all had to be over the phone which hasnt helped either. I will update this with how we got it working when we do.
I really messed up when trying to root my phone.
I think i accidently flashed an incorrect boot.img to my phone.
Now I can't get it to boot anymore.
After this I now can't even let my XZ3 boot into twrp recovery also.
Everytime I do a fastboot boot twrp.img i get this:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
So i'm stuck and don't know how to boot it.
any ideas?
r3v0 said:
I really messed up when trying to root my phone.
I think i accidently flashed an incorrect boot.img to my phone.
Now I can't get it to boot anymore.
After this I now can't even let my XZ3 boot into twrp recovery also.
Everytime I do a fastboot boot twrp.img i get this:
So i'm stuck and don't know how to boot it.
any ideas?
Click to expand...
Click to collapse
Did you apply the vbmeta parameters?
Did you tried magisk 19.x? (19 may generate bootloops, I recommend my bundled 18.1)
You can always get the stock boot.img from the boot.sin in the stock firmware (April, the may twrp is not published).
Just unsin.exe the file (unsin.exe from XDA).
MartinX3 said:
Did you apply the vbmeta parameters?
Did you tried magisk 19.x? (19 may generate bootloops, I recommend my bundled 18.1)
You can always get the stock boot.img from the boot.sin in the stock firmware (April, the may twrp is not published).
Just unsin.exe the file (unsin.exe from XDA).
Click to expand...
Click to collapse
Where can I find the latest stock firmware?
I've been searching for it for hours now.
The unsin.exe I found already
r3v0 said:
Where can I find the latest stock firmware?
I've been searching for it for hours now.
The unsin.exe I found already
Click to expand...
Click to collapse
The latest (without twrp support, because I shared the first build on telegram for testing) is downloadable via Emma.
You could also use xperifirm and newflasher from XDA
In xperifirm you can choose the region, hopefully one region has still the April firmware.
PS: I see notifications for new posts or answers easily in my big threads, but it gets difficulty for the different device sections on XDA (in the app).
MartinX3 said:
The latest (without twrp support, because I shared the first build on telegram for testing) is downloadable via Emma.
You could also use xperifirm and newflasher from XDA
In xperifirm you can choose the region, hopefully one region has still the April firmware.
Click to expand...
Click to collapse
xperifirm I can use. But Emma won't recognize the phone obviously as it doesn't boot.
You mentioned the april release. Is that necessary?
r3v0 said:
xperifirm I can use. But Emma won't recognize the phone obviously as it doesn't boot.
You mentioned the april release. Is that necessary?
Click to expand...
Click to collapse
Just if you want to install twrp on your phone.
The April twrp may "fastboot boot twrp.img" with broken decryption but an installation would only lead into a not working twrp.
MartinX3 said:
Just if you want to install twrp on your phone.
The April twrp may "fastboot boot twrp.img" with broken decryption but an installation would only lead into a not working twrp.
Click to expand...
Click to collapse
At this moment all I want is to be able to boot it again.
But everytime I try to fastboot a boot.img to the phone I get:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
r3v0 said:
At this moment all I want is to be able to boot it again.
But everytime I try to fastboot a boot.img to the phone I get:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
Do you use the newest fastboot version?
And the xz3 twrp?
Execute
fastboot -v
Please
MartinX3 said:
Do you use the newest fastboot version?
And the xz3 twrp?
Execute
fastboot -v
Please
Click to expand...
Click to collapse
I use this version:
fastboot version 28.0.3-5475833
And I have the latest xz3 twrp
r3v0 said:
I use this version:
fastboot version 28.0.3-5475833
And I have the latest xz3 twrp
Click to expand...
Click to collapse
Oh. Maybe 28.0.2 or 28.0.1 are working better?
Did you boot the stock firmware without any modification once first?
Edit:
Interesting
28.0.3 must be so new that even google didn't publish a changelog.
MartinX3 said:
Oh. Maybe 28.0.2 or 28.0.1 are working better?
Did you boot the stock firmware without any modification once first?
Click to expand...
Click to collapse
When I got the phone I booted it.
After that I managed to unlock the bootloader.
Then I tried to root it.
And that's when I think I fastbooted the wrong boot.img.
r3v0 said:
When I got the phone I booted it.
After that I managed to unlock the bootloader.
Then I tried to root it.
And that's when I think I fastbooted the wrong boot.img.
Click to expand...
Click to collapse
Maybe yes.
I never saw this message. Hmmm.
At least one xz3 user I know from is happy with the twrp.
Weird, very weird.
I whish I could reproduce it.
MartinX3 said:
Maybe yes.
I never saw this message. Hmmm.
At least one xz3 user I know from is happy with the twrp.
Weird, very weird.
I whish I could reproduce it.
Click to expand...
Click to collapse
TWRP worked until I messed up the boot.
When I now try to fastboot flash boot boot.img I get this:
FAILED (remote: 'Error flashing partition : Volume Full')
I managed to get it to boot to twrp. I guess at some time I set-active it to b. Setting it back to a solved the not booting twrp.
Now I used the vbmeta.img from twrp to set vbmeta.
Gonna try rooting it again now.
OS not booting yet.
r3v0 said:
I managed to get it to boot to twrp. I guess at some time I set-active it to b. Setting it back to a solved the not booting twrp.
Now I used the vbmeta.img from twrp to set vbmeta.
Gonna try rooting it again now.
OS not booting yet.
Click to expand...
Click to collapse
I recommand flashing the entire firmware via newflasher.
Remove the userdata.sin so you don't wipe your phone.
MartinX3 said:
I recommand flashing the entire firmware via newflasher.
Remove the userdata.sin so you don't wipe your phone.
Click to expand...
Click to collapse
So, I just found out You're the developer of what I downloaded.
Can I flash this one:
H9436_Customized CE1_1316-3759_52.0.A.3.84_R9B.tar.gz
through newflasher?
r3v0 said:
So, I just found out You're the developer of what I downloaded.
Can I flash this one:
H9436_Customized CE1_1316-3759_52.0.A.3.84_R9B.tar.gz
through newflasher?
Click to expand...
Click to collapse
Muahahahaha [emoji14]
You mean my old uploaded firmware?
That's just the last version before Sony changed the DRM
Better you use the 52.0.A.8.25 , it is the April stock firmware and compatible with the newest twrp so far.
I hope it is still available through xperifirm.
Ok, thanks so far. You pointed me in the right direction. Hopefully I get my Xz3 running again. ??
r3v0 said:
Ok, thanks so far. You pointed me in the right direction. Hopefully I get my Xz3 running again. [emoji1303]
Click to expand...
Click to collapse
I'm optimistic, that you'll achieved success.
MartinX3 said:
I'm optimistic, that you'll achieved success.
Click to expand...
Click to collapse
In the end.
Now i'm struggling with an error with newflasher.
No usb device with vid:0x0fce pid:0xb00b
Click to expand...
Click to collapse
Oh yeah, I'm on linux. So I'll have to do all my windows stuff through a VM
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, enter bootloader do a "fastboot flash init_boot magskpatchedfile.img.
9, reboot and test,
I have removed the _a in the cmd line as it appears its not needed
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum.
Ok,, this how I flashed ,and will flash, the new updates coming out so as not to lose data ,this will NOT do a wipe plus it's faster ,,,,, I know there are multiple other ways but for now I choose this,, hth
1. Download the correct ota file here
https://developers.google.com/android/ota and copy to adb folder
2. Place phone in factory recovery and toggle to apply update from adb,,
3. Open cmd prompt in adb folder type adb sideload factoryota.zip ,,,takes 5-10 minutes to complete, reboot ,,
if rooted,
1 download correct full image zip here
https://developers.google.com/android/images. That matches ota you just flashed,
2 extract the ini.boot.img , patch with magisk and reflash in adb for root
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
Does the screen come on at all? In your other post you said it was black. If there's nothing at all on the screen, your phone is probably bricked.
JimJamer8 said:
it doesnt turn on at all
Click to expand...
Click to collapse
Have you tried a hard reset - hold the power button down for 10 seconds or so until the phone vibrates?
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You didn't try the steps I listed as I never said to flash a rooted bootloader
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You may need to disable Verity and Verification. I flashed my stock image back to the phone using the tool here: https://flash.android.com/ and checked the boxes to disable verity and verification, then followed the steps above. Important to note that booting to Bootloader tells you which slot is active, and running the command fastboot flash init_boot magisk_patched_25205_GUID.img automatically patches the active boot slot. From there you just need to run the Universal Safety net fix from KDrag0n and the latest MagiskHide and you should be good to go
hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Thank you for the help, turned out the _a was screwing me over, works great now!
mnemonical said:
Thank you for the help, turned out the _a was screwing me over, works great now!
Click to expand...
Click to collapse
I know ,,that was messing me up too, it did not work untill I put that part in,, don't ask me why! Lol
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
atom_jack said:
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
Click to expand...
Click to collapse
I'll give it a try
googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
Use the non replace version of revanced and disable stock YT
Hitman478™ said:
Use the non replace version of revanced and disable stock YT
Click to expand...
Click to collapse
Revanced Manager app is just going to black screen after install
hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
googletermsofservice said:
Revanced Manager app is just going to black screen after install
Click to expand...
Click to collapse
I've it installed and it's working without any issue
AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
Use fastboot flash init_boot "image.img" without quotes and without specific the partition, it will goes on the active one, for me it has working at first try
hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
THX, in fact the "fastboot boot" command was used a lot with OnePlus devices because it is safer to boot in the rooted os and when there is an error you can just reboot without the command...and when you install it afterwards with magisk you know it will work
Does Universal Safetynet Fix work?
Just wanted to thank OP. My Pixel 7 arrived about an hour ago, got the bootloader unlocked no problem, then actually I flashed the latest System Image first, then had Magisk patch init_boot.img, flashed that, easy peasy.
hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
It's usually used to temporarily boot a patched boot image and then you can do direct install in magisk manager