SGSIII EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows:
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
{
"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"
}
For Linux
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
On the basis of the findings made on the basis of the loss of IMEI and serial numbers, decided to update the backup tool for those who have not lost ...
He will be in addition to backing up and restoring an image backup and recover efs is also a copy of the current modema.
I'm tried only backup, restore me unnecessarily!
Only I9300!!!
DOWNLOAD
SAMSUNG_I9300_EFS_BACKUP_RESTORE_AUTOMATIC
Instructions:
! Need for backup Root access and debugging USB
1. Extract from the zip and run. Bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file. Tar.md5,
* raw.img
* Tar.gz archive
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore
DOWNLOAD
Thanks to:
shoma_81, tester99,
For help and assist in the creation of tool
as i9000 said:
SGSIII EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
* Extract from the archive, connect the device to the USB debugging mode and run your. Bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
For Windows:
http://forum.xda-developers.com/attachment.php?attachmentid=1347629&stc=1&d=1348399433
Click to expand...
Click to collapse
What mode do you need to be in? I guess ADB debugging is also required.
Kangburra said:
What mode do you need to be in? I guess ADB debugging is also required.
Click to expand...
Click to collapse
System settings/Developer options/USB debugging, is all it takes...
Hi, I have tried this but it does not seem to be working for me:
For Windows:
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
Click to expand...
Click to collapse
I have I9300, it is rooted with USB debugging enabled
When I click on Backup_EFS,bat file I get the following message:
Backup EFS
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
The script closes when I press to continue - no efs.img file
Please tell me what I am doing wrong
Thanks
mmrc01 said:
Hi, I have tried this but it does not seem to be working for me:
I have I9300, it is rooted with USB debugging enabled
When I click on Backup_EFS,bat file I get the following message:
Backup EFS
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Press any key to continue . . .
The script closes when I press to continue - no efs.img file
Please tell me what I am doing wrong
Thanks
Click to expand...
Click to collapse
1 didn't install samsung driver
2 haven't root
3 putn't debug usb...
as i9000 said:
SGSIII EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows:
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
http://forum.xda-developers.com/attachment.php?attachmentid=1347629&stc=1&d=1348399433
For Linux
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
http://forum.xda-developers.com/attachment.php?attachmentid=1347726&stc=1&d=1348403575
Click to expand...
Click to collapse
Thanks.
But a lot of apps which use adb to run "dd if=/of=" and pull the backup image in a folder are already release and work fine. What is new in this batch script ? Thank you anyway. It works correctly.
lelinuxien52 said:
Thanks.
But a lot of apps which use adb to run "dd if=/of=" and pull the backup image in a folder are already release and work fine. What is new in this batch script ? Thank you anyway. It works correctly.
Click to expand...
Click to collapse
Nothing, except that, it's pull image to pc and back, and there is no excess, only backup and restore efs partition
as i9000 said:
1 didn't install samsung driver
2 haven't root
3 putn't debug usb...
Click to expand...
Click to collapse
4 Script is wrong, last 2 adb commands not prefixed by files\
also adb pull will fail on later adb versions since no destination specified, so you need to add . on end, e.g.
files\adb pull /sdcard/efs.img .
Odia said:
4 Script is wrong, last 2 adb commands not prefixed by files\
also adb pull will fail on later adb versions since no destination specified, so you need to add . on end, e.g.
files\adb pull /sdcard/efs.img .
Click to expand...
Click to collapse
fixed, but before it was worked...
as i9000 said:
fixed, but before it was worked...
Click to expand...
Click to collapse
Maybe before when you tested abd was in your PATH and was older revision, anyway nice work, more EFS backup solutions the better.
Odia said:
Maybe before when you tested abd was in your PATH and was older revision, anyway nice work, more EFS backup solutions the better.
Click to expand...
Click to collapse
perhaps...
thanx...
as i9000 said:
perhaps...
thanx...
Click to expand...
Click to collapse
Hi. I located efs.img in my sd card(internal) Nothing on the laptop . Is that were its supposed to be? One more question.....For restoring you are sating to retain the img it must be in the same folder as restore.back...must i copy the efs.img and paste to the same folder were restore.back is on the computer?
Odia said:
Maybe before when you tested abd was in your PATH and was older revision, anyway nice work, more EFS backup solutions the better.
Click to expand...
Click to collapse
None yet, the first time was right - the first version back
art_arev said:
Hi. I located efs.img in my sd card(internal) Nothing on the laptop . Is that were its supposed to be? One more question.....For restoring you are sating to retain the img it must be in the same folder as restore.back...must i copy the efs.img and paste to the same folder were restore.back is on the computer?
Click to expand...
Click to collapse
Download new...
as i9000 said:
Download new...
Click to expand...
Click to collapse
Hi Downloaded new...The old version at least was backing in sdcard. The new download says adb not recognised external or internal command.
I have root,debuging on, and all the samsung drivers ....but.........its failing
art_arev said:
Hi Downloaded new...The old version at least was backing in sdcard. The new download says adb not recognised external or internal command.
I have root,debuging on, and all the samsung drivers ....but.........its failing
Click to expand...
Click to collapse
Connect device and run command console and paste
Code:
adb shell
What happend?
as i9000 said:
Connect device and run command console and paste
Code:
adb shell
What happend?
Click to expand...
Click to collapse
exactly the same in command prompt: adb not recognised..blabla....( I hope we are talking about Windows version the rar download)
art_arev said:
exactly the same in command prompt: adb not recognised..blabla....( I hope we are talking about Windows version the rar download)
Click to expand...
Click to collapse
I make tool with new ADB
Dowload...
Mast work
as i9000 said:
I make tool with new ADB
Dowload...
Mast work
Click to expand...
Click to collapse
Works like a charm:good::good::good::good::laugh: Tks your a Star. Spasibo bolshoye
art_arev said:
Works like a charm:good::good::good::good::laugh: Tks your a Star
Click to expand...
Click to collapse
My pleasure!
Related
Nandroid Restore
UPDATE: XDA member Cyanogen has put together a new recovery image that has a Nandroid restore mode built right in. This allows Nandroid to be totally selfcontained on the device. My (and Markazah) program still is good for easy restores if you keep multiple backups because Cyanogen's only restores the latest backup (within the Recovery image GUI anyway.)
Here is a link to his "Pimped out recovery image with new features"
http://forum.xda-developers.com/showthread.php?t=523558
Awsome Cyanogen!
{
"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"
}
Nandroid, created through the efforts of Infernix and Brainaid, is a great tool for backing up your phone. The NANDROID backup process itself is easy to use; however, some folks are not so sure about how to restore these backups back to their phone.
Solution: Nandroid Restore and Nandroid Restore GUI
What it does:
Automates the FASTBOOT portion of the restore.
Nandroid Restore will use FASTBOOT to wipe and then restore the boot, system, userdata and recovery partitions from your phone.
When these tasks are completed, the script then reboots your phone.
What you should expect:
You should end up with a clean restore and all of your data just as you had it when you made your NANDROID backup. EASY!
Directions:
Get your phone into the Secondary Boot Loader (SPL):
Plug your phone into your computer with the USB cable
Take your NANDROID backup off of your SD card and place it in a directory on your PC with a copy of both fastboot.exe and AdbWinApi.dll.
Enter the Secondary Boot Loader (SPL) of your phone by powering down your phone and then powering it back up while holding both the <END> button and the <CAMERA> button.
Restore using NANDrest.bat from the command line:
On your PC, drop to a command prompt and navigate to the directory that you placed your NANDROID backup and fastboot.exe files.
Execute the program "nandrest.bat".
(It is also possible to simpily run this script from the folder without using the command prompt. We all have our preferences after all.)
Restore using Nandroid Restore GUI: (GUI written courtesy of XDA user Markazeh)
Make sure that the 4 Nandroid Restore GUI files are in the same folder as your NANDROID backups.
The GUI will make sure that all required files (the *.img files and Nandrest scripts.)
(See the included pictures)
Reference knowledge:
NANDROID is included with JesusFreke's testkeys modded recovery image. If you have a JF ROM then you probably already have this recovery image and NANDROID.
You must have the Engineering SPL or HardSPL to use FASTBOOT.
Fastboot.exe and AdbWinApi.dll are found in the "tools" folder of the SDK files.
FASTBOOT requires drivers to be loaded into your Windows Operating System. These drivers are in "usb_driver" folder of the SDK files.
Conclusion:
Sure, it's pretty simple and I use it to save time and automate the repair of my latest screw-up and now you can too!
Thank you to Infernix, Brainaid, JesusFreke, Haykuro, TheDudeOfLife, Google and all others that have given their skills and time to the Android community (and subsequently introduced the necessity for NANDROID. )
And thank you to XDA member Markazeh for providing the GUI for Nandrest.bat.
NANDROID post:
http://forum.xda-developers.com/showthread.php?t=459830
Secondary Boot Loader (SPL) post:
http://forum.xda-developers.com/showthread.php?t=455860
will try this, thanks.
Thank you for this.
where is nandrest.bat?
@Sandshrimp: The nandrest.bat file is inside of the nandrest.zip file. You must first unzip nandrest.zip before you will be able to access nandrest.bat.
How is this script working for the rest of you?
Hey nicksen,
i was bored this evening, so i decided to write a little GUI for your Script...
How it works:
- First off, i deleted the ":AREYOUSURE" part in your script, cause a security check is
in the GUI.
- When you start the GUI, it checks if no file is missing and shows missing files
graphically.
- You can only press the "Flash" Button, when every file is in the folder...
I renamed the "nandrest.bat" to "nandrest", that no one can accindently flash the phone by clicking the nandrest.bat. When you click "Flash" the Programm renames the script to "nandrest.bat", that Windows can open it and after your Script has finished it renames it back to "nandrest".
Hope you like it!
Greetings
Markazeh
Markazeh said:
Hey nicksen,
i was bored this evening, so i decided to write a little GUI for your Script...
How it works:
- First off, i deleted the ":AREYOUSURE" part, cause this security check is
handled in the GUI.
- When you start the GUI, it checks if no file is missing and shows missing files
graphically.
- You can only press the "Flash" Button, when every file is in the folder...
I renamed the "nandrest.bat" to "nandrest", that no one can accindently flash the phone by clicking the nandrest.bat, cause i deleted the security check in it... When you click "Flash" the Programm rename the script to "nandrest.bat", that Windows can open it. After your Script is finished it renames it to "nandrest".
Hope you like it!
Greetings
Markazeh
Click to expand...
Click to collapse
nicksen782: Thanks a bunch for the script!
Markazeh: Thanks even more for making a user friendly GUI for it!
This is amazing work, I love this community for this sort of collaborations.
I'll send people this way for easy restore.
@Markazeh -
Thanks! I like the GUI! This is technically my first contribution so I'm pretty tickled that it has been useful so soon. May I suggest that your GUI also check for the presence of AdbWinApi.dll and Fastboot.exe? Oh, and maybe throw my name on your GUI for the script portion? I can rewrite the first post of this thread to include the new GUI.
THANKS!
Yeh, I'm gonna put your name also on the GUI.
I CAN check for the other files, but some people have these files in the win dir....
I have to think about that....
I'll upload the GUI with your name in it in a few hours
May you can give a suggestion on how to handle the problem with the files....
Greets
This works great, thanks guys! Nice job!
Wow! What a great idea. We have all been needing this, IMHO.
How difficult would it be to make it possible to restore only one or more portions of the backup? For example, I did a wipe on the last flash of 1.5, and I want to restore my /data, but not the rest. If you could add that capability, this app would be perfect.
Thanks for your work.
agreed
stellarman said:
Wow! What a great idea. We have all been needing this, IMHO.
How difficult would it be to make it possible to restore only one or more portions of the backup? For example, I did a wipe on the last flash of 1.5, and I want to restore my /data, but not the rest. If you could add that capability, this app would be perfect.
Thanks for your work.
Click to expand...
Click to collapse
I'd prefer not to restore the recovery partition every time for example (it doesn't change too much in my experience outside of flashing to an "official" build). That would be a great tweak!
Ok, ill discuss with nicksen...
Markazeh said:
Ok, ill discuss with nicksen...
Click to expand...
Click to collapse
Thanks. I will keep an eye open for your answer.
Another idea: Could this script, or one like it, possibly be added to 'recovery' so that it shows in recovery mode along with the backup command? It would be really sweet if we could do an 'alt + r' (or whatever) and restore the most recent nandroid backup. I know it is asking alot. But, "to g-e-t, you have to a-s-k." Right?
stellarman said:
Thanks. I will keep an eye open for your answer.
Another idea: Could this script, or one like it, possibly be added to 'recovery' so that it shows in recovery mode along with the backup command? It would be really sweet if we could do an 'alt + r' (or whatever) and restore the most recent nandroid backup. I know it is asking alot. But, "to g-e-t, you have to a-s-k." Right?
Click to expand...
Click to collapse
Well, it should be possible in a way, but we cant do it, cause this script is for windows and android/recovery is linux based...
GUI looks good, another suggestion would be to allow user selection of what is flashed. E.g. Data.img only or just Boot.img and System.img
@ markazeh: There have been some good suggestions. Perhaps checkboxes next to the "found/not found" labels? These checkboxes could default to all checked or all checked except recovery. You could also give the user the option of flashing or not flashing individual images via these checkboxes. Maybe 3 radio buttons at the top labeled: Restore EVERYTHING, Restore ONLY data, Restore EVERYTHING except recovery. Something to that effect. How can I help further?
I personally would really like a NANDROID restore to be available via something like alt+r in the recovery mode such as stellarman has suggested. My assumption is that the recovery mode loads in some of these partitions that we would be trying to restore and that would cause a problem. However, if it were possible to safely unmount these partitions and then restore using flash_image then it might work. The flash_image program however is on the system partition so a ramdrive or other temporary solution would need to be created first. I figure that this is why this hasn't already been done.
Can anybody confirm any of this?
Well the problem is, that i have to split your script in these parts: data flashing, recovery flashing, system flashing and boot flashing, cause i cant go to a part in the script, i can only run a bat.... So im going to split your script in these parts.
Then we have 4 small scripts....
Im going to put 4 Buttons to Flash System, Boot, Data and Recovery.
Should be done Tomorrow.
Version 1.1 here...
All you need is in first post!
Note: I give no guarantee if your phone will brick... But if you use our program properly it wont brick!
awesome
Markazeh said:
Version 1.1 here...
All you need is in first post!
Note: I give no guarantee if your phone will brick... But if you use our program properly it wont brick!
Click to expand...
Click to collapse
You guys rock, thanks!
Credits/Disclaimer
Code:
[U][B]
This is not my guide, you dont have to thank me for this.
Thanks to Ocnbrze over at AndroidForums for this.
we are not responsible if your device(s) cause(s) a nuclear war[/B][/U]
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Please read thru this guide once or twice before actually taking steps !
Your phone MUST be on a stock sense rom so go get that installed now !
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Before you do anything else, your phone MUST be on a stock sense rom !
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
{
"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"
}
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
XenonV said:
First things first- Not my guide, You are fully responsible for whatever happens. It is not XDA's fault, its not my fault, its all on you.
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Now lets begin
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
Click to expand...
Click to collapse
I've actually been dealing with this most of the day trying to unroot and go back 100% stock and have had no success. It was suggested elsewhere that I need to be on a stock rom? I'm dl'ing one now to try as I am currently on an ics rom.
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
XenonV said:
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
Click to expand...
Click to collapse
Perhaps a good bit of info to add to the op
Relentless D said:
Perhaps a good bit of info to add to the op
Click to expand...
Click to collapse
already on it, thanks
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Captain_Throwback said:
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Click to expand...
Click to collapse
i dont know who the original writer is, which is why. if i know then i always list that info :good:
XenonV said:
i dont know who the original writer is, which is why. if i know then i always list that info :good:
Click to expand...
Click to collapse
Where did you get it from, then?
It looks strikingly similar to this guide:
http://androidforums.com/evo-4g-all-things-root/526575-guide-unrooting-gingerbread-2-3-5-a.html
In fact, the inordinate number of exclamation points and the use of my command prompt screenshot makes me think it originated over there.
Captain_Throwback said:
Where did you get it from, then?
Click to expand...
Click to collapse
somebody PM'd me the guide on another website (the tech game) , just the text, no link
XenonV said:
somebody PM'd me the guide on another website (the tech game) , just the text, no link
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Relentless D said:
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Click to expand...
Click to collapse
problem solved thanks :good:
and yes this is my guide. however, you do not need to be on stock sense, just not on ics roms for this to work. just throwing that out there.
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
Are you running a rooted ROM? You need to have root access for this to work. Try typing "su" at the prompt and see if it changed to a #.
thanks
Can this be done using a Mac?
XenonV said:
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
Click to expand...
Click to collapse
i have tried that and it still doesnt work, any help!?
im running a brand new computer like seriously out of the box, windows 7 ultimate and it wont give the #
Chirpout said:
Can this be done using a Mac?
Click to expand...
Click to collapse
yes, i believe the guide states something about that..not exactly sure, you can also use google for more help
Hi, I know this is really out of date, but I have to send my phone back because the screen is cracked (inner touch screen) and I wanted the phone to be completely stock. I never rooted the phone. I only unlocked the bootloader. I found this thread hoping I could relock the bootloader to make it look like I never unlocked it in the first place. Of course once I reached Step 7, I don't get the # sign. I get the $ sign and I don't know what to do :/
{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
Hi guys,
I present here with small tutorial to backup your sdcard and your applications with their data. For this you'll required to know adb commands which I've posted in Moto G Index thread which can be found here. (I've too referred it and learnt about this process. Even you can create many more if you are crazy like me )
Backing up sdcard and your applications with their data is essentially process to keep them safe in case something goes wrong with your phone and need to be wiped.
I know that there are lot of other third party apps like Titanium Backup, Helium etc which are available in Google Play Store which can do this task.
But this method is safe, easy, reliable and works on stock and rooted devices.
Before starting, you need to download the zip which is attached in this post or you can also download Android SDK and install it on you PC and work on this commands.
Now, Go to Settings --> Developer options --> Check "usb debugging".
Connect your device to pc.
Backup & Restore sdcard
Backup :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb pull /sdcard/ /sdcard/
This command will pull your sdcard (not move or cut) to "c" directory under "sdcard" folder.
This process may take time depending upon the size of your sdcard. Please don't abort it until finishing.
Restore :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb push sdcard /sdcard/
This command will push the "sdcard" to your device.
This process may take time depending upon the size of your sdcard. Please don't abort it until finishing.
Hit thanks if you find this useful.
Backup & Restore Applications and Their Data
Backup :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb backup -apk -noshared -all -nosystem
Now look at your device and accept backup process. (You can continue without entering the password)
Wait until finishing.
This will backup your apps and their data to the PC (a "backup.ab" file will be created in the same folder).
Restore :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb restore backup.ab
Now look at your device and accept restore process. (If you entered the password while backing up, you need to enter it while restoring)
Wait until finishing.
This will restore your applications and their data to device.
Hit thanks if you find this useful.
It will be useful to change rom and not lose the progress of the games and some configurations?
Excuse my bad English.
Ivan!
Leproso_Ivan said:
It will be useful to change rom and not lose the progress of the games and some configurations?
Excuse my bad English.
Ivan!
Click to expand...
Click to collapse
AFAIK, some of the app's data is not properly restored. (Experienced this when my device was not rooted)
Mr hOaX said:
AFAIK, some of the app's data is not properly restored. (Experienced this when my device was not rooted)
Click to expand...
Click to collapse
I will try when I change the rom.
Iván!
{
"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"
}
took a long time and that was only backing up SD card lol. but I can say it can successfully backup
bublz654 said:
took a long time and that was only backing up SD card lol. but I can say it can successfully backup
Click to expand...
Click to collapse
It depends upon your SD Card size
Good job for uploading screenshot for others
Credits given
Mr hOaX said:
It depends upon your SD Card size
Good job for uploading screenshot for others
Credits given
Click to expand...
Click to collapse
I had 7.18 GB on my SD card lol. no problem for screen shot I'll try n backup app+data soon
please help, I'm trying to do backup the fourth time now and I keep getting that, I rebooted phone deleted. c:/sdcard directory its not working. what can I do ?
never mind I got 5th time lucky
I finished backing up my apk + data it didn't show any successful pop-up but I guess it works
where the backup.ab file ?
wouldn't pulling the whole data partition do the same job in one shabang?
meangreenie said:
wouldn't pulling the whole data partition do the same job in one shabang?
Click to expand...
Click to collapse
don't think so, in just trying to find where the backup. an file is for my backed up apps and their data
bublz654 said:
don't think so, in just trying to find where the backup. an file is for my backed up apps and their data
Click to expand...
Click to collapse
Sorry for late reply mate.
But your backup file is saved where you adb and fastboot files are present!
It's in the directory where you had launch adb cmds to start the backup process.
If you don't find it still search it in C:\ drive or else your backup process was aborted because of failure.
It works for me, and you usually get prompts on your device to start the backup process and also get the prompts to restore the backup.
If you are facing more issues, PM me
Mr hOaX said:
Sorry for late reply mate.
But your backup file is saved where you adb and fastboot files are present!
It's in the directory where you had launch adb cmds to start the backup process.
If you don't find it still search it in C:\ drive or else your backup process was aborted because of failure.
It works for me, and you usually get prompts on your device to start the backup process and also get the prompts to restore the backup.
If you are facing more issues, PM me
Click to expand...
Click to collapse
Ok man thanks for explaining, i will look for the backup.ab wheres the adb n fastboot files tomorrow. This guide is great
Sent from my iPod touch using Tapatalk
Hello! Does it work if I do a backup on a motoG Lte then I restore it in another one motoG Lte? Becouse I have to send it back to where I've bought it and they're shipping me a new one
Thanks in advance!
is that the backup.ab folder ? (6th file from top )
bublz654 said:
is that the backup.ab folder ? (6th file from top )
Click to expand...
Click to collapse
Yes mate. I'm extremely sorry for late reply. I was unavailable these days.
If you are not able to restore that *.ab file, then it is "corrupted" due to incomplete process of backup!
bazuzu666 said:
Hello! Does it work if I do a backup on a motoG Lte then I restore it in another one motoG Lte? Becouse I have to send it back to where I've bought it and they're shipping me a new one
Thanks in advance!
Click to expand...
Click to collapse
Yes mate
Mr hOaX said:
Yes mate. I'm extremely sorry for late reply. I was unavailable these days.
If you are not able to restore that *.ab file, then it is "corrupted" due to incomplete process of backup!
Yes mate
Click to expand...
Click to collapse
The .an file worked when restoring. When trying to restore SD card it says could not find SD card folder. So I had to move everything manually
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
Installing an OTA.zip Update with ADB Sideload
- 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
In this thread you will find different ways to install an OTA update :
Via ADB SIDELOAD (this post) - Via Recovery Mode - Via Local Upgrade
I am writing this tutorial on ADB Sideload, one more on this topic, in order to be able to push an OTA Zip update, which for some reason could not be done properly.
Sometimes manufacturers allow users to make links or zip files of OTA updates available to other users. Once you have downloaded the OTA zip file, you will need this tutorial to proceed with the installation.
I borrowed the first two screenshots from the web so that I could explain clearly with pictures.
In the end it is very simple and requires little command line knowledge. But you will need to check some things:
- Firmware stock
- Unmodified system partition
- Third party apps like Magisk, Xposed Framework, and as a precaution TWRP Recovery should not be installed on your smartphone
Before starting, here is the list of prerequisites to perform the sideloading of the OTA package.
1. Have a backup of your data, even if theoretically performing a sideload will not erase your data,
2. Download the USB Drivers from the manufacturer, or the latest one from Google ( Link )
3. If you haven't already done so, you must download and install Android SDK Platform-tools (platform-tools_r33.0.2-windows.zip)
4. Don't forget to push on this folder "platform-tools" the file named "Global full Nothing OS 1.1.0.zip" - for example- that you need
4. And finally you will have to activate the USB debugging of your Phone(1) : to do so, you have to go to : Settings => System => Advanced => Type 7 times on the build number => once done, a pop-up will appear and will tell you that you have become a "Developer" => On some devices you will have to type in the Pin code.
5. Once you have become a developer => go back to System => Developer Options => Enable the USB Debug toggle
6. That's it if you are ready to do a Sideload, but also other operations!
{
"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"
}
These prerequisites are essential for this and a number of other operations.
You are ready, the tension is rising! You will succeed!
To do this, you must reboot your Phone(1) into the standard recovery system and you have 2 ways to reboot into Recovery.
1. You can use the hardware key combination specific to your smartphone.
2. Or use the ADB command
Booting into Recovery Stock mode with the ADB command
You go to the start screen of your PC and in the search bar you type:
Code:
cmd
and then press Enter. The command prompt starts.
Depending on where you have placed your "Platform-tools" folder you type:
Code:
C:\WINDOWS\system32>cd c:\platform-tools
and you should see on your command line screen
Code:
c:\platform-tools>
Once you are in your Platform-tools folder, connect your smartphone to your PC, making sure that USb debugging is effective.
Type the following command: adb devices and you should see the identification of your smartphone
When you run an ADB command, you should see an RSA key prompt on your smartphone screen asking you to allow USB debugging. Press OK to allow it.
Type the following command: adb reboot recovery
Then the command: adb sideload "file name".zip - For the example, I typed the full name of the file, but you can rename the file shorter like "nothing_ota".zip
That's it, normally the installation is started and you just have to wait for the update to be installed on your device. Once the installation is successful, you can restart your device.
I hope this tutorial has helped you to push an OTA.zip update.
Go ahead now
Installation via recovery mode
The recovery mode of the Phone(1) is similar to that of the Google Pixel. This allows you to easily sideload the update packages via the recovery interface.
To perform this process, here are the steps and requirements:
Have downloaded the .zip file of the update to your computer
Your Phone(1) must be recognised by the ADB command on your computer
The Process:
Go to your Shell terminal, then run the recognition command:
Code:
adb devices
then the command :
Code:
adb reboot recovery
On your Phone(1) screen, you should see this "No command"
While pressing the Power button, press the Volume Up button then release both buttons quickly. The Android recovery menu should be visible.
Nothing Phone 1 recovery mode
On your Phone(1) screen, select the option: Apply update from ADB.
On your computer, run the command:
Code:
adb devices
This should return the serial number of the device with the 'sideload' next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:
Code:
adb sideload "filename".zip
The "filename" part should be replaced with the full path, followed by the name of the file downloaded in step 1.
The update will be installed on your phone.
Once the installation is complete, select "Reboot system now" on your phone to reboot into the new version.
Well done, you have installed the new update of Nothing OS to your Phone(1) with success
To date I still haven't received my phone(1). Once I have it in my hands, I will make screenshots about this tutorial.
Install OTA using Local Upgrade method
Create a folder named “ota” (without the quotes) at the root of the internal storage. Meaning outside every folder.
Copy the OTA update ZIP file from above to that folder.
Open the phone app and Dial ##682##
This should launch an offline update tool.
The tool will scan for an OTA file from internal storage and install it.
If that fails, you can manually browse for the OTA package.
After selecting the OTA file, the wizard will apply the update.
Reboot the device and you are on the latest firmware.
Reserved 3
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Pho3nX said:
I think also after update, reboot, redo the step and sideload also Magisk for keep root
Click to expand...
Click to collapse
Yes I agree, but those tutos are for everyone, and everyone doesn't rooted his smartphone like us
So I won't confuse them
hello, thanks for the guide, when I do all the steps without any problems and reboot, it opens with the old version, where could I be doing wrong?
This will work to downgrade the phone also?
pankspoo said:
This will work to downgrade the phone also?
Click to expand...
Click to collapse
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
sh4tteredd said:
no, np1 has a very strict anti rollback check. I don't suggest to downgrade this phone
Click to expand...
Click to collapse
So we can use your Windows tool to downgrade ?
pankspoo said:
So we can use your Windows tool to downgrade ?
Click to expand...
Click to collapse
I won't downgrade this phone at all. Btw maybe I'm wrong and it can work but I'm not sure and I don't suggest to do it
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
demiii said:
Hi, I am currently trying to update from Nothing OS 1.1.3 to 1.1.4 but i keep receiving this error even though i have uninstalled magisk, didn't modify my system partition and have a stock firmware. The phone is still able to boot correctly after this failed installation but i cannot flash the new update.
View attachment 5716899
Click to expand...
Click to collapse
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Sib64 said:
Which version of ADB Sideload do you use ?
Post 1 or Post 2
Click to expand...
Click to collapse
What I did was reboot to recovery, navigate to Apply Update via Sideload through the recovery interface and from there entered the command adb sideload filename.zip so i guess it is the method in post 2
UPDATE:
I have tried the method in Post 1 and this error shows up:
UPDATE 2:
I have tried revoking USB DEBUGGING authorization, adb kill-server, adb start-server and authorizing again
I have tried deleting adbkey and adbkey.pub files in C:Users/$Name/.android
I have tried following suggestions about solving this error both from this and this StackOverflow thread
Nothing worked for me.
You don't need to use ADB to sideload an OTA, the nothing phone contains an OTA updater In the phones os already, the only thing you need the computer for is to move the OTA to the phone
Here is what someone on the nothing discord said to do and it worked
dont sideload
Create a folder named “ota” (without the quotes) at the root of the internal storage of your phone. Then copy the update ZIP file to that folder.
Dial `*#*#682#*#* `to open up the offline update tool.
You can also use an activity launcher app to locate and execute the “OfflineOTAUpgrade” tool. The package name of the tool is com.nothing.OfflineOTAUpgradeApp.
Hi, I have just tried your method but an error window pops up:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Ky0sHiR0 said:
Hello, can I normally use in built in recovery updater to upgrade to 1.1.4 if I'm rooted and have Nacisk installed?
Click to expand...
Click to collapse
You can only upgrade not downgrade
demiii said:
Hi, I have just tried your method but an error window pops up:
View attachment 5717197
Click to expand...
Click to collapse
If you go on nothing discord and put that error maybe they can help