Related
This is gonna be a lengthy tutorial, I'll be very clear and specific in my details and requirements, you are entirely responsible for what you do to your device, I can confirm here works and the end result is a completely stock device which is updateable, etc, any mistakes, missed steps and any other user error is your fault, so read and follow instructions carefully, that is all. Links for files, requirements, etc will be provided at the end of this tutorial.
Let's begin:
Requirements:
1. Nandroid backup of T-Mobile stock 1.27 rom, since we have no ruu to work with, link provided. (credit to whomever uploaded it)
2. CWM recovery along with ROM manager from the playstore, I may or may not make a flashable zip of the nandroid, depends on when I get time to do so.
3. Root and s-off
4. revone s-off tool (bin file to be specific)
5. a pc or some other way of unzipping the nandroid backup, do not use your device to unzip it, it may or may not unzip correctly, chances are you'll waste your time unzipping over and over pointlessly.
6. adb toolkit (mini kit at the end)
7. knowledge on how to use adb, etc is a plus.
8. KNOW HOW TO READ
9. An HTC one that's at least rooted.
10. Patience
Steps:
1. Gather all your required files, take the all in one toolkit I link which contains revone, adb, stock recovery and cwm. You can placed the downloaded nandroid wherever you want to.
2. Unzip the nandroid backup and place it on the internal memory of the device in the "sdcard/clockworkmod/backup/" folder, do not rename the unzipped file.
3. Run the cwm flash script to replace your recovery with cwm touch recovery, device needs to be in android, not fastboot, device will reboot to android upon successfully flashing cwm recovery.
4. Open rom manager and select "Manage and Restore Backups", it should detect the nandroid, select it and choose to restore, let the device reboot and restore the nandroid.
5. Once complete, do a factory reset(optional) and reboot
6. Next step would be to flash the stock recovery by using the script provided followed by the stock hboot, if hboot flashing fails look at the bottom for the step to fix this.
7. now that's we're on stock recovery and stock rom, our next step would be to lock the bootloader and put the device to s-on, this is where it get's technical:
Lock bootloader using revone:
1. open a command prompt then cd to the folder of your mini sdk, example: cd C:/Users/Random Name/Downloads/mini-sdk
2. In the command prompt window push the revone bin file via "adb push revone /data/local/tmp"
3. Open adb shell: adb shell
4. then: cd /data/local/tmp
5. followed by: chmod 755 revone
6. then: ./revone -P
7. once it reports success it should say whether it requires reboot or not: ./revone -s 0 -l (this changes the bootloader status to **Locked**, -t to remove tamper, -u to **Unlocked** and S-Off, -r for **Relocked**, use as required)
8. Bootloader is now back to locked status, type: reboot bootloader
S-On
Device will be in fastboot mode where you should see **Locked** follow below it by S-Off
1. To change it to s-on, in the command prompt type: fastboot oem writesecureflag 3
2. then fastboot reboot
3. Device will boot into android, you will be prompted by a software update, which you can do at your own leisure whether you'd like to or not, your call.
Voila, you're back on Official stock, completely untouched device.
Optional steps, if needed.
Back to Stock CID:
While in fastboot use the command: fastboot oem writecid T-MOB010 (this needs to be done before you s-off) (script provided)
Flashing stock firmware package
Now flashing this package may fail, it is to be done while you're s-off.
You may flash the firmware.zip package via command line by the following commands:
1. fastboot oem rebootRUU
2. fastboot flash zip firmware.zip (this is named tmo.zip in the package)
3. fastboot reboot-bootloader
(was it a success?, if yes, proceed to locking the bootloader and s-on)
IF flashing the firmware package fails, flash the hboot manually via the command below (hboot provided in a separate zip in case of this):
1. fastboot oem rebootRUU
2. fastboot flash zip boot.zip
3. fastboot reboot-bootloader
should this fail as well, run the super cid script, re-do the above steps, then run the stock tmo cid script.
Then proceed with s-on/lock bootloader. There are a few kinks to be worked out, sadly I have not the time to do this at the moment.
Nandroid backup: https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM (credit to uploader, I'll look for the correct screen name as soon as I can)
In case of no signal: which shouldn't be flash a radio: http://forum.xda-developers.com/showthread.php?t=2245615
Mini sdk with scripts: http://d-h.st/z8c
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
NOTE: Video coming soon, credits whomever until I give it accordingly, this was put together in a rush, so didn't get the chance to look see at all the screenies, screenshots and video to come.
dark nightmare said:
this is gonna be a lengthy tutorial, i'll be very clear and specific in my details and requirements, you are entirely responsible for what you do to your device, i can confirm here works and the end result is a completely stock device which is updateable, etc, any mistakes, missed steps and any other user error is your fault, so read and follow instructions carefully, that is all. Links for files, requirements, etc will be provided at the end of this tutorial.
Let's begin:
Requirements:
1. Nandroid backup of t-mobile stock 1.27 rom, since we have no ruu to work with, link provided. (credit to whomever uploaded it)
2. Cwm recovery along with rom manager from the playstore, i may or may not make a flashable zip of the nandroid, depends on when i get time to do so.
3. Root and s-off
4. Revone s-off tool (bin file to be specific)
5. A pc or some other way of unzipping the nandroid backup, do not use your device to unzip it, it may or may not unzip correctly, chances are you'll waste your time unzipping over and over pointlessly.
6. Adb toolkit (mini kit at the end)
7. Knowledge on how to use adb, etc is a plus.
8. Know how to read
9. An htc one that's at least rooted.
10. Patience
steps:
1. Gather all your required files, take the all in one toolkit i link which contains revone, adb, stock recovery and cwm. You can placed the downloaded nandroid wherever you want to.
2. Unzip the nandroid backup and place it on the internal memory of the device in the "sdcard/clockworkmod/backup/" folder, do not rename the unzipped file.
3. Run the cwm flash script to replace your recovery with cwm touch recovery, device needs to be in android, not fastboot, device will reboot to android upon successfully flashing cwm recovery.
4. Open rom manager and select "manage and restore backups", it should detect the nandroid, select it and choose to restore, let the device reboot and restore the nandroid.
5. Once complete, do a factory reset(optional) and reboot
6. Next step would be to flash the stock recovery by using the script provided followed by the stock hboot, if hboot flashing fails look at the bottom for the step to fix this.
7. Now that's we're on stock recovery and stock rom, our next step would be to lock the bootloader and put the device to s-on, this is where it get's technical:
Lock bootloader using revone:
1. Open a command prompt then cd to the folder of your mini sdk, example: Cd c:/users/random name/downloads/mini-sdk
2. In the command prompt window push the revone bin file via "adb push revone /data/local/tmp"
3. Open adb shell: Adb shell
4. Then: Cd /data/local/tmp
5. Followed by: Chmod 755 revone
6. Then: ./revone -p
7. Once it reports success it should say whether it requires reboot or not: ./revone -s 0 -l (this changes the bootloader status to **locked**, -t to remove tamper, -u to **unlocked** and s-off, -r for **relocked**, use as required)
8. Bootloader is now back to locked status, type: Reboot bootloader
s-on
device will be in fastboot mode where you should see **locked** follow below it by s-off
1. To change it to s-on, in the command prompt type: Fastboot oem writesecureflag 3
2. Then fastboot reboot
3. Device will boot into android, you will be prompted by a software update, which you can do at your own leisure whether you'd like to or not, your call.
Voila, you're back on official stock, completely untouched device.
Optional steps, if needed.
Back to stock cid:
While in fastboot use the command: Fastboot oem writecid t-mob010 (this needs to be done before you s-off) (script provided)
flashing stock firmware package
now flashing this package may fail, it is to be done while you're s-off.
You may flash the firmware.zip package via command line by the following commands:
1. Fastboot oem rebootruu
2. Fastboot flash zip firmware.zip (this is named tmo.zip in the package)
3. Fastboot reboot-bootloader
(was it a success?, if yes, proceed to locking the bootloader and s-on)
if flashing the firmware package fails, flash the hboot manually via the command below (hboot provided in a separate zip in case of this):
1. Fastboot oem rebootruu
2. Fastboot flash zip boot.zip
3. Fastboot reboot-bootloader
should this fail as well, run the super cid script, re-do the above steps, then run the stock tmo cid script.
Then proceed with s-on/lock bootloader. There are a few kinks to be worked out, sadly i have not the time to do this at the moment.
Nandroid backup: https://mega.co.nz/#!gpifgr7l!c5o74ex6k3wkvlwkwgsrjbrgushtjhxeb6yqpmoqamm (credit to uploader, i'll look for the correct screen name as soon as i can)
in case of no signal: Which shouldn't be flash a radio: http://forum.xda-developers.com/showthread.php?t=2245615
mini sdk with scripts: http://d-h.st/z8c
revone: http://forum.xda-developers.com/showthread.php?t=2314582
note: Video coming soon, credits whomever until i give it accordingly, this was put together in a rush, so didn't get the chance to look see at all the screenies, screenshots and video to come.
Click to expand...
Click to collapse
you the best! Thanks
I assume if i replace the at&t nandroid with a bell nandroid one i can restore to bell following the rest of the steps?
redzone321 said:
I assume if i replace the at&t nandroid with a bell nandroid one i can restore to bell following the rest of the steps?
Click to expand...
Click to collapse
Yup, you just need to know what the bell cid is, in case you changed to super cid.
I'm getting an MD5 mismatch in CWM...should I just try downloading again
mcdsmaster8824 said:
I'm getting an MD5 mismatch in CWM...should I just try downloading again
Click to expand...
Click to collapse
You can try unzipping via computer and not your phone, if you absolutely have to use your phone, you can try zarchiver, otherwise, may be a bad download.
Hi,
Great that we have this thread.
Should flashing back to stock t-mobile firmware be a step in case someone flashed another firmware package during their many travels of flashing their device? I'm thinking some people may have tried out latest firmware packages like 2.17 or 2.24 and I'm thinking flashing a 1.27.531.x nandroid may not work on a higher firmware package?
http://forum.xda-developers.com/showthread.php?t=2355814
TMOUS Custom Firmware Package - 1.27.531.8
Sent from my HTC One using Tapatalk 2
gustav30 said:
Hi,
Great that we have this thread.
Should flashing back to stock t-mobile firmware be a step in case someone flashed another firmware package during their many travels of flashing their device? I'm thinking some people may have tried out latest firmware packages like 2.17 or 2.24 and I'm thinking flashing a 1.27.531.x nandroid may not work on a higher firmware package?
http://forum.xda-developers.com/showthread.php?t=2355814
TMOUS Custom Firmware Package - 1.27.531.8
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I already thought of that, hence the firmware package in the bottom notes.
My bad for not reading all the way through! Glad we have this.
Sent from my HTC One using Tapatalk 4 Beta
Thanks for this great guide!
Would it be possible to add a section for restoring to the stock bootloader for anyone like me who flashed to Google Edition RUU (which replaces boot/recovery/ROM)?
dozybolox13 said:
Thanks for this great guide!
Would it be possible to add a section for restoring to the stock bootloader for anyone like me who flashed to Google Edition RUU (which replaces boot/recovery/ROM)?
Click to expand...
Click to collapse
Bootloader/recovery/stock rom are all a part of this guide buddy, the hboot section is your bootloader, there's the recovery section right there as well (last step before s-on/locked status) and the nandroid that you'll be restoring is the stock rom, once I get time tonight, I'll work on making the nandroid a flashable rom instead to make things easier.
Worked perfectly, thanks!
thank you!
Nandroid backup is "temporary unavailable" on mega - can you post a mirror?
Thanks
Edit: Was able to finally download with megadownloader and restore my device - your guide worked brilliantly, thanks!
I have a problem
Dark Nightmare said:
This is gonna be a lengthy tutorial, I'll be very clear and specific in my details and requirements, you are entirely responsible for what you do to your device, I can confirm here works and the end result is a completely stock device which is updateable, etc, any mistakes, missed steps and any other user error is your fault, so read and follow instructions carefully, that is all. Links for files, requirements, etc will be provided at the end of this tutorial.
Let's begin:
Requirements:
1. Nandroid backup of T-Mobile stock 1.27 rom, since we have no ruu to work with, link provided. (credit to whomever uploaded it)
2. CWM recovery along with ROM manager from the playstore, I may or may not make a flashable zip of the nandroid, depends on when I get time to do so.
3. Root and s-off
4. revone s-off tool (bin file to be specific)
5. a pc or some other way of unzipping the nandroid backup, do not use your device to unzip it, it may or may not unzip correctly, chances are you'll waste your time unzipping over and over pointlessly.
6. adb toolkit (mini kit at the end)
7. knowledge on how to use adb, etc is a plus.
8. KNOW HOW TO READ
9. An HTC one that's at least rooted.
10. Patience
Steps:
1. Gather all your required files, take the all in one toolkit I link which contains revone, adb, stock recovery and cwm. You can placed the downloaded nandroid wherever you want to.
2. Unzip the nandroid backup and place it on the internal memory of the device in the "sdcard/clockworkmod/backup/" folder, do not rename the unzipped file.
3. Run the cwm flash script to replace your recovery with cwm touch recovery, device needs to be in android, not fastboot, device will reboot to android upon successfully flashing cwm recovery.
4. Open rom manager and select "Manage and Restore Backups", it should detect the nandroid, select it and choose to restore, let the device reboot and restore the nandroid.
5. Once complete, do a factory reset(optional) and reboot
6. Next step would be to flash the stock recovery by using the script provided followed by the stock hboot, if hboot flashing fails look at the bottom for the step to fix this.
7. now that's we're on stock recovery and stock rom, our next step would be to lock the bootloader and put the device to s-on, this is where it get's technical:
Lock bootloader using revone:
1. open a command prompt then cd to the folder of your mini sdk, example: cd C:/Users/Random Name/Downloads/mini-sdk
2. In the command prompt window push the revone bin file via "adb push revone /data/local/tmp"
3. Open adb shell: adb shell
4. then: cd /data/local/tmp
5. followed by: chmod 755 revone
6. then: ./revone -P
7. once it reports success it should say whether it requires reboot or not: ./revone -s 0 -l (this changes the bootloader status to **Locked**, -t to remove tamper, -u to **Unlocked** and S-Off, -r for **Relocked**, use as required)
8. Bootloader is now back to locked status, type: reboot bootloader
S-On
Device will be in fastboot mode where you should see **Locked** follow below it by S-Off
1. To change it to s-on, in the command prompt type: fastboot oem writesecureflag 3
2. then fastboot reboot
3. Device will boot into android, you will be prompted by a software update, which you can do at your own leisure whether you'd like to or not, your call.
Voila, you're back on Official stock, completely untouched device.
Optional steps, if needed.
Back to Stock CID:
While in fastboot use the command: fastboot oem writecid T-MOB010 (this needs to be done before you s-off) (script provided)
Flashing stock firmware package
Now flashing this package may fail, it is to be done while you're s-off.
You may flash the firmware.zip package via command line by the following commands:
1. fastboot oem rebootRUU
2. fastboot flash zip firmware.zip (this is named tmo.zip in the package)
3. fastboot reboot-bootloader
(was it a success?, if yes, proceed to locking the bootloader and s-on)
IF flashing the firmware package fails, flash the hboot manually via the command below (hboot provided in a separate zip in case of this):
1. fastboot oem rebootRUU
2. fastboot flash zip boot.zip
3. fastboot reboot-bootloader
should this fail as well, run the super cid script, re-do the above steps, then run the stock tmo cid script.
Then proceed with s-on/lock bootloader. There are a few kinks to be worked out, sadly I have not the time to do this at the moment.
Nandroid backup: https://mega.co.nz/#!gpIFGR7L!c5o74Ex6k3wkVlWKWgSrJBrguShtjHXeB6YQPmoqAmM (credit to uploader, I'll look for the correct screen name as soon as I can)
In case of no signal: which shouldn't be flash a radio: http://forum.xda-developers.com/showthread.php?t=2245615
Mini sdk with scripts: http://d-h.st/z8c
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
NOTE: Video coming soon, credits whomever until I give it accordingly, this was put together in a rush, so didn't get the chance to look see at all the screenies, screenshots and video to come.
Click to expand...
Click to collapse
I tried this on my Htc one and it didn't work. i accidentally formatted my data and when i try to reboot it says no os installed. I tried side loading it, and tried flash zip, but i still could load into any rom. Please help.
ro34po43 said:
I tried this on my Htc one and it didn't work. i accidentally formatted my data and when i try to reboot it says no os installed. I tried side loading it, and tried flash zip, but i still could load into any rom. Please help.
Click to expand...
Click to collapse
What recovery are you using and what rom are you trying to sideload with? If you're gonna safely sideload, use twrp and a stock rom.
Thank you so much for this!
Just out of curiosity, have you had time to upload any screenshots or a video of the process yet?
idonthavetimeforthis said:
Thank you so much for this!
Just out of curiosity, have you had time to upload any screenshots or a video of the process yet?
Click to expand...
Click to collapse
Like your name he doesn't have time for it
thank you
thank you very much for writing this organized tutorial - there could be a little more detail about how to flash the recovery's for those that don't use windows (easy enough to open the bat scripts), but very good and very convenient to have all the files in one place
thanks again
I didn't bother reading the entire thread, so if there's a link I apologize, but I'm another sad soul who took the T-Mobile 1.27.531.11 update. Whomp whomp. Well anywho. In my many attempts to S-Off, I've become well versed in restoring back to stock. So if you're stuck and don't know what to do, PM me and I shall help thee! I will provide links to stock/custom recoveries, the .11 RUU, and walk ya through it
Sent from my HTC One using xda app-developers app
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
New device new rules/tricks
The main purpose for this thread is to post info that doesn't real justify it's own thread.
Most of what is posted is what interests me, usually in no particular order.
If you think something is missing, please share (include links or as much info you can)
General Info
Index
Have a question? Please consider asking in the
Help Thread
How to Check if you have a Verizon or Google Model from CID info
Custom Recovery info
FAQs
USB Drivers
Using ADB and Fastboot commands
Unlocking the Bootloader
Rooting
WiFi Tether
Installing new security update with fastboot.exe for a bootloader-unlocked Pixel
[GUIDE] Restore to stock after soft BRICKED Written for XL version, but a good reference
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
[Re]Activate Google Voice on Pixel
46 Google Pixel XL & Google Pixel Tips and Tricks (www.droidviews.com)
https://www.androidpit.com/google-pixel-tips-and-tricks
USB Drivers for using ADB/Fastboot commands
If using Mac or Linux drivers should not be an issue.
If using Windows 10 correct drivers should already be installed but you likely will need to select them in Device manager
If drivers are correct the Pixel should be listed in Device Manager as
Android Phone
adb composite interface
An easy way to install correct drivers on a Windows PC is using
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05
Official Google Drivers
Unlocking the Bootloader - 06 Nov 2016
If it's a pure Google device just run
Code:
fastboot oem unlock
If you bought the Pixel from Verizon, Best Buy.... dePixel8 method will be required to unlock the bootloader
Note: Verizon, Build Version NDE63X, Nov 2016 can be unlocked,Builds after that cannot.
Using dePixel8
Be sure Drivers are correct
Change screen timeout to 30 mins in settings/display options
Enable Developer Options
In Settings/About Phone >Tap build version until it says "you are developer"
go back to main Settings screen
Open Developer Options
Enable ADB Debugging (in Developer Options)
Be sure ADB and Fastboot commands are working
Download dePixel8
Run in Command prompt
Code:
adb push dePixel8 /data/local/tmp
Code:
adb shell chmod 755 /data/local/tmp/dePixel8
then
Code:
adb shell /data/local/tmp/dePixel8
when you see
Code:
[+] getting there, about 20 more seconds please
open the Chrome app on the phone
then you should see
Code:
[+] done
[+] rebooting your device to bootloader mode
[+] run "fastboot oem unlock" to unlock your bootloader
[+] P.S. Pixel is made by HTC, and dePixel8 was made by beaups
[+] cheers jcase - copyright Streamlined Mobile Solutions, LLC
Discussion Thread: BL unlock for Verizon Pixel just released by murryrulz
Do not relock the bootloader
[PSA] Read before relocking your bootloader by jcase
Rooting
Requires Unlocked Bootloader
[ROOT] SuperSU by Chainfire
Hotspot/WiFi Tether
Hotspot should work out of the box for most data plans except Unlimited Data plans
Verizon Unlimited Data Plans
Rooted method
Make sure your bootloader is unlocked and you are rooted.
Instal a Root File Manager (Root Browser / ES File Explorer)
enable root access in File Manager (it's off by default in some)
browse to /System > Long press build.prop > Open in Text Editor
Scroll all the way to the bottom. Type in "
Code:
net.tethering.noprovisioning=true
.. Then save and exit. Reboot the phone and you're good to go.
Discussion Thread: Pixel Hotspot by polo2883
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Non Root method
Verizon native tether subscription bypass A Pixel XL thread
Sprint WiFi Tethering Thread
[ROOT/Guide] Native Hotspot Working by stuntnmore A Pixel XL thread
Setting up and Using ADB/Fastboot (Android Debugging Bridge)
For Mac or Linux: see Can ADB/Fastboot be used on Linux and Mac?
Setting up ADB/Fastboot (Windows)
[Index] Setting up and Using ADB/Fastboot
Using ADB/Fastboot
adb commands are used in normal boot/OS or in Recovery
fastboot commands are used in fastboot/bootloader mode
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
Code:
Fastboot set_active _a
Code:
Fastboot set_active _b
Installing new security update with fastboot for a bootloader-unlocked Pixel.
Note: This is a work in progress, but it should be correct.
Even if it works for the Nov update, it may need to be written for future updates
Problem:
If you have modified the stock firmware (hosts file, root, kernel, etc.), the OTA update likely will fail
Solution:
This does not factory reset, user apps and data are not removed.
This will remove your custom kernel/root/hosts/recovery...
Install Verify Drivers
see post #2
Setup ADB.exe see
[Index] Setting up and Using ADB/Fastboot
[INFO] How I restored to stock after soft bricking, then flashed new kernel & rooted by CZ Eddie
Download the system image for Sailfish (Pixel) from google
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
Unzip the file
Unzip xxxxxxnde63v.zip from inside the new directory/folder
Copy files to same folder as adb.exe files (unnecessary if adb is setup as global)
Open open Command Prompt (with same directory path as firmware files)
Reboot into bootloader
Code:
adb reboot bootloader
or
Power off, Hold volume down button, power on
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Execute fastboot commands
Code:
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Custom Kernel, Root, and other mods will need to be reflashed
Credit
[GUIDE] Update with fastboot by @firewave
Custom Recovery
Twrp links
TWRP RC1 for Pixel Devices
https://plus.google.com/+DeesTroy
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
GeekMcLeod said:
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
Click to expand...
Click to collapse
Thanks, hope it helps.
It is linked in the index
sd_shadow said:
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Click to expand...
Click to collapse
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
sturmeh said:
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
Click to expand...
Click to collapse
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
GeekMcLeod said:
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
Click to expand...
Click to collapse
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
the Pixel has 2 system slots/partitions,
in theory you could have 2 different roms to choose from, that maybe an option in a future version of twrp
Sent from my XT1254 using XDA Labs
sd_shadow said:
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
No, my bootloader still says my bootslot is a.
GeekMcLeod said:
No, my bootloader still says my bootslot is a.
Click to expand...
Click to collapse
thanks, sounds good
Sent from my XT1254 using XDA Labs
new
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Sent from my sailfish using XDA Labs
I just tried reverting to stock and my phone is stuck in a bootloop and then eventually gets stuck on dead android with No command text. I followed all directions to the dot and I'm on boot slot b. Any ideas?
---------- Post added at 11:04 AM ---------- Previous post was at 10:43 AM ----------
Ok so I followed GeekMcLeod's advice about flashing system-other to the opposite partition. Since I was on boot_b I change the line in the OP to flash system_a and now my phone is booting. @sd_shadow I'm not sure if this is the case for everyone.
Just a short story about my experience so far with the Pixel.
When i first got my device it wanted to update. I let it update (OTA) and rebooted. Once that was done, I unlocked the bootloader, booted TWRP flashed it, rebooted TWRP and then flashed root. All was awesome, I went to reboot and noticed that TWRP shows which boot slot you're in (I was in B). I rebooted anyway and everything works as expected.
I was curious, so I booted back into TWRP, went to reboot and changed the boot slot to A, got an error but checked it again and it shows I was in fact in boot slot A. So i rebooted... it booted into non rooted, pre update android... so it looks to me that this seamless update system applies the update the opposite partition that your in. So if you're in A and take an OTA it applies it to B and then reboots into B (updated) and the opposite will happen if you take the OTA while in B. All apps and data you've collected is shared with either system partition.
So, in theory we could take the OTA as long as we flash the recovery and (possibly) boot images before downloading and applying it. We would only have to flash TWRP and root again.
And I agree, it looks like we should be able to dual boot two different ROMS, maybe even kernels without too much messing around.
I'm sure this is not new news but I just wanted to share and maybe someone will correct me or learn from it.
thanks for the replies, good stuff
Sent from my sailfish using XDA Labs
Hi world Here I bring you a mini tutorial on how to solve this problem, in the way that I solved it and it worked for me, it's very easy and I hope it works for you.
I DO NOT MAKE ANY RESPONSIBILITY FOR THE RISK INVOLVED BY TRYING THIS.
Prerequisites:
adb fastboot minimal
Hboot M9_4.30.617.12
RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12.exe
first of all, the first thing I did was to update the HBOOT to the latest version of the unlocked / developer model
Step-By-Step:
1. If device is booted into Android, reboot into download mode by running:
Code:
adb reboot download
2. Now place the Firmware_xx.zip into your adb/fastboot folder (which will be C:\Program Files (x86)\Minimal ADB and Fastboot" if you use my Batch Tool).
2a.
Code:
fastboot oem rebootRUU
3. Followed by:
Code:
fastboot flash zip M9_4.30.617.12_NoWipe_TWRP3100.zip
(IF you encounter any errors which are not “FAIL90”, have a look into Post #3 or ask in the thread! DO NOT REBOOT THE DEVICE!)
View attachment 4607611
Flash the file again and done.
View attachment 4607612
After this simple step, just install your ruu and your phone will be ready.
ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL
Hey everyone,
It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.
You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Click to expand...
Click to collapse
How to bootloader unlock and root the Nothing Phone 1After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:
Step 1: Unlock the Nothing Phone 1’s bootloader
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.3) binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
[NOT A MANDATORY TO UNLOCK CRITICAL, IT'S FOR ME BETTER TO NOT USE THIS COMMAND, THIS COMMAND COULD BE THE REASON SOME PEOPLE HAVE BRICK OR NOT WHEN GO BACK STOCK NOS]
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Step 2 - Rooting your Nothing Phone 1 with MagiskWith an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
Depending of your model, you have Global or EEA (European) firmware availables.
You can download the latest full OTA firmware package here.
Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
Download and install the Magisk app on the Nothing Phone 1.
Open the Magisk app and tap on the Install button.
Choose Select and Patch a File. A file manager will pop up.
Select the boot image that you pushed earlier and let Magisk patch it.
Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
Reboot the Phone 1 into the bootloader: adb reboot bootloader
Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
Reboot the phone: fastboot reboot
Open the Magisk app and your Nothing Phone 1 should be rooted.
Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.
-=o#0#o=-
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.
Spoiler: Relock the bootloader of your Phone(1)
menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
#root #nothingphone
Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Click to expand...
Click to collapse
Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding
STEP 1: What you need and read before the process.
It’s really important for a process without problems
Install Android SDK and the Platform-tools folder
Download the Nothing OS version you need (see this post)
Extract the "payload bin" file from the rom
Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
Unlock the bootloader of your Phone(1) (see this tutorial)
STEP 2: Boot the bricked phone 1 into Fastboot mode
Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.
Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.
In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.
STEP 3: Format the device via Fastboot
1.Go to the platform-tools folder where the extracted ROM is located.
2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
3.Now run the following command to perform a factory reset (optional but recommended)
Code:
fastboot -w
STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
Don't forget to check your command line before validating it, because often a small error blocks you!
Spoiler: Command Lines
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
flash fastboot dsp dsp.img
flash fastboot dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img fastboot
fastboot flash product product.img
fastboot flash qupfw qupfw.img
flash fastboot shrm shrm.img
flash fastboot system system.img
flash fastboot system_ext system_ext.img
flash fastboot tz tz.img
flash fastboot uefisecapp uefisecapp.img
flash fastboot vbmeta vbmeta.img
flash fastboot vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash vendor_boot vendor_boot.img
flash fastboot xbl xbl.img
fastboot flash xbl_config xbl_config.img
Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
Code:
fastboot reboot
Well done , you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands.
I hope this tutorial has helped you find your Phone(1).
Thanks
Reserved
FILES FOR NOTHING OS - (stock-boot, etc. )
UPDATE 15/12/2022
Stock_Boot for Nothing OS here
Be carefull, be sure to select the good Stock Boot "Global" or "EEA" for your device.
Extract Payload.bin via Payload Dumper Go
To start, download the payload-dumper-go 1.0.0 from Github [Credits: XDA Member @ssssut].
Then extract it to any convenient location on your PC. The file name will be something like payload-dumper-go_1.0.0_windows_amd64.
Rename it to payload-dumper-go.
Next, download the liblzma-5.dll file and transfer it to the same folder where the payload-dumper-go.exe file is located.
After that, transfer the payload.bin file to this folder as well.
So, from now on, you should have the 3 files payload-dumper-go.exe, payload.bin and liblzma-5.dll in one folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to the address bar of that folder, type "cmd" and press Enter. This will launch the command prompt window.
Type the command below to extract the payload.bin file:
Code:
payload-dumper-go payload.bin
The extraction process will now begin and will only take a few seconds.
Once this is done, all extracted files will be placed in a folder named extract_date_time which is created in this directory like this name : extracted_20220731_145751
The process is very simple and very fast. Anyone can do it. So don't hesitate, you have everything you need to do this yourself.
it's up to you now
If this has helped you, and if you appreciate my help.
Thanks
Is it possible to relock the bootloader?
Is it possible to relock the bootloader on an third party ROM?
@Sib64 does the device keep Widevine L1 when the bootloader has been unlocked?
Krullendhaar said:
Is it possible to relock the bootloader?
Click to expand...
Click to collapse
Yes.
Krullendhaar said:
Is it possible to relock the bootloader on an third party ROM?
Click to expand...
Click to collapse
No.
Could you also do a tutorial on how to update the OS when you're rooted?
I hope to find an EDL QPST full rom... better to stay safe and restore It in any case...
Mod is coming...
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Is rooting success with 1.1.0 Rom?
Naveenakash said:
Is rooting success with 1.1.0 Rom?
Click to expand...
Click to collapse
I didn't try it with an actual app, but it was showing properly in Magisk. But bootloader needs to stay unlocked.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Did you fix that issue?
Naveenakash said:
Did you fix that issue?
Click to expand...
Click to collapse
I didn't. I'm trying to factory reset the phone, but I can't seem to flash the ROM from bootloader.
ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
No matter from which partition (A/B)
lba810701 said:
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
Click to expand...
Click to collapse
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
And what if you flash back the original bootloader to over the unlocked one, and after it you close it, not the modded one?
ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
Also, doing a factory reset from recovery doesn't relock the bootloader either.
I've tried now to sideload the .zip but it seems that even the supposed 1.1.0 full OTA zip available in the other post is older than my current ROM, so it can't be flashed like that. I'll have to wait for the next update.