Error run nandroid-mobile.sh restore via adb

error run nandroid-mobile.sh restore via adb

Prerequisites · Create a complete device backup, if possible. This is because we will have to wipe off all the data from your device via the fastboot-w command. crap my restore just failed. It said: Error: run 'nandroid-mobile.sh restore ' via adb Are my backups lost forever? I tried all of them and all gave that. when it tells me to do back up in recovery mode (step 8) i press home button and i get this error Run nandroid-mobile.sh via adb! error run nandroid-mobile.sh restore via adb

Something is: Error run nandroid-mobile.sh restore via adb

TRAUMATISMO Y TERROR TORRENT
Error run nandroid-mobile.sh restore via adb
Lineage 2 runtime error l2.bin

Status 7 error: what’s the problem with Android OTA updates and how to fix it?

The latest Nexus devices are normally sql state 22018 native error first to receive the newest Android versions. When a new firmware version is ready for release to general public, its full image is located at developers.google.com/android/nexus/images. Shortly after that, firmware starts to typeerror components.classes cid is undefined firefox distributed over the air. According to one of Google developers, Dan Morrill, error run nandroid-mobile.sh restore via adb, (goo.gl/L85mSS), the first few OTA updates are sent to 1 % of devices. It happens at random, regardless of the location or point of sale of a phone/tablet. During this time, bugs are identified allowing the updating process to be put on hold if any critical errors are registered with a large number of users.

After that over a couple of weeks, updating is provided to 25, 50, 100 % of users, i.e. at the initial stage only one device out error run nandroid-mobile.sh restore via adb a hundred stands a chance of getting an upgrade. If the update is not received, the device drops from the list, and subsequent repeated clicking on the button ‘check for updates’ automatically sends the device to the bottom of the list. When a new stage of distribution starts, clicking on the button get a 25 % chance of receiving the update. Since the device checks for updates on its own once a day (upon reboot), clicking on the button might ‘jump the gun’ before it may run its course. But whatever the outcome, only one check will be made. Subsequent clicking will not help matters. This is not a situation where ‘first press, first receive’ (first come first serve). In any error status 32512, the over the air update will be available to everyone within a couple of weeks, error run nandroid-mobile.sh restore via adb. The most impatient user could update their devices manually (some more details on that aspect are given below).

Notification of the update

Notification of the update

The updating process can be accelerated in two ways. The first one – clean data from the Google Services Framework and then reboot the device. This method is the one to be avoided [frown upon even by Google engineers] (goo.gl/ugSshF). It causes many negative effects, the worst one being is the change of GCM identity (Google Cloud Messenger). This identifier is required in all Google and many other applications using the push notification feature. And while in some programs those effects can be remedied fairly easily, while in many others implications may be far more serious. All applications will just be unavailable for GCM-based push notifications until they have been provided with a new identifier. Some applications performs checks often, some don’t. For some applications data cleaning will help. And worst affected can be those applications that use GCM ID as an identifier on their servers.

Stock recovery

Stock recovery

The second is manual updating through the recovery console. Shortly after the launch of OTA files like hash.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip appear in profiles at XDA and 4PDA with the file names featuring file hash, device brand and firmware versions involved in updating (original and updated ones). In their computers, the user has to keep a folder containing ADB and fastboot utility apps. I, for one, use the latest versions of Android SDK. The archive set the OTA-update should be placed in the same folder. Also, the user should have available properly installed drivers for devices autodesk ctrl + p error may conflict with previously installed drivers for other devices.

The device itself should be put in the recovery mode (recovery). To do that, you press the < Power + VolDown > buttons together on your deactivated device error run nandroid-mobile.sh restore via adb get access into the boot loader selecting the Recovery mode with the volume button and get into it with the Power button. The Inactive Android sign followed by the exclamation mark will show up. Don’t be afraid, it is not a bug. Short-push < Power + VolUp > on the screen to download stock recovery. There you should select the ‘apply update error run nandroid-mobile.sh restore via adb ADB’ on the menu list using the Volume buttons and validate using the Power button. Next, you hook up your phone/tablet with the computer. Let’s start the console, move over to the folder with ADB and the update archive and enter the following command (for the file above):

This will cause OTA to be installed on your phone and get it restarted.

How to download the update over the mobile network

Update notification can arrive when your device is not connected to Wi-Fi. In this case, the mark will appear that the file is available for download via Wi-Fi for a specified period (about a week), while the “Download” button itself will be disabled, error run nandroid-mobile.sh restore via adb. It is all done to save the user’s money. If you are not going to connect to Wi-Fi in the near future, then you can deceive you handset by downloading the update via 3G/4G, putting back the date in your gadget in relation to the date indicated in the notification and restarting the device.

If your boot loader is unlocked, you have customized recovery and root that actively uses various applications and various modifications have been made, then the likelihood of you failing get an update is 99 %. Even upon return of stock recovery, the Error run nandroid-mobile.sh restore via adb 7 error will be flashed if the firmware is upgraded via ADB. Customized recovery will also signal an error rejecting modified files. This problem can be resolved by recovering the factory firmware in your Smartphone, but it is not our method. Let’s deal with it by picking at the update file, pinpointing and removing the stumbling block, error run nandroid-mobile.sh restore via adb, using the largest Nexus 5 update from version 4.4.4 (KTU84P) to 5.0 (LRX21O) as an example.

Operation procedures

So, the update from 4.4.4 to 5.0 was the largest one with the archive weight reaching 491 MB. Nearly the entire code had been modified while Dalvik was replaced with ART. So what does the archive contain? As you can see in the ‘Archive Files updated to 5.0’ screen shot, the archive contains boot loader images (various sections) and META-INF directory, patch and system catalogs.

Archive files updated to 5.0

Archive files updated to 5.0

In order to minimize the amount of traffic and reduce the load on servers, as well as to cut the end-user costs the update is designed in such a fashion that files with massive changes or written from scratch are located in the system catalog and changed from the ground up. While files with a low percentage of changes by Google’s standards, rather than replaced, are patched, i.e. only parts of the code inside the file are modified. These files are located in the patch catalog and have r extension. This is clearly visible when you compare files in/system/bin and/patch/system/bin. In this case, the patch is created by bsdiff well known to UNIX geeks, allowing two binaries to be converted to delta (a file with a difference between files).

The magic is initiated by the updater script located in/META-INF/com/google/android. We’ll get a detailed view of it. The file weighs 463 Kb and contains code lines responsible for the OTA updating process (as a matter of fact, it is the scripting language Edify who interpreter is located in the same catalog and is named ‘update-binary’. – Editor’s note.). In our case, it has the following content. First, we install the section/system (fairly standard line for Linux, similar to those located in /etc/fstab):

Next, the script checks the device model and firmware version using the system variable ro.build.fingerprint read (please note that it does not take it from the file/system/build.prop file, and requests ‘recovery’ itself, therefore updates cannot be made through a customized recovery console, although it was possible to prior to error run nandroid-mobile.sh restore via adb. Here and further on ellipsis denote abbreviated lines:

As you can see above, the update will not be successfully installed onto a non-proprietary device, but it can be reloaded onto version 5.0. The script checks to see whether the firmware is authenticated by Google’s official keys (release-keys). This is what causes many users troubles. Next, we start checking for the availability and integrity of individual files using SHA-1 hash verification. For this purpose we need two features: sha1_check() that accepts the file name and hash as arguments and apply_patch_check() that accepts three arguments: file name and two hashes. The first one is simply used to verify file integrity, while the second one checks if the file is already patched. For simplicity’s sake, coded long hashes below have been replaced with ellipses:

Only two checks have been illustrated by way of example. In reality all files to be replaced or patched-change are checked. The code shows that the update will produce an error if, for example, the file/system/app/Drive.apk has been modified or extracted. Toward the end of the check, the script examines the kernel and available space in/system and radio:

It means that it won’t error 806 vpn connection successfully installed if there is a custom kernel or a modified radio. The next step includes removal of old files from the device to be replaced with new ones and deletion of files that are redundant on the new firmware

Next, all required files are patched together with a preliminary check of SHA-1 hash. The patching process is performed by apply_patch() that accepts names of filed to be patched and several hash types: original hash, patch hash and result hash. The last argument is patch file name. As above, all hashes in the code are abbreviated to ellipses:

Kernel and RAM-disk are the last items to be patched:

The next unit transfers to the device those files that are not to be patched and are to be replaced entirely. Some of them will be subsequently relocated:

Redundant files are removed and symbol links, access rights, and flags are placed (here it is rights of access and flags that are substituted for ellipses):

Boot loader and associated sections are upgraded:

Radio /modem are patched:

The last thing to be replaced is build.prop where the new firmware version is written. It is done in this way so that when an error occurs at the very last stage, when nearly all cifs-vfs errors code are moved, the upgrading process could interrupted saving the number of the current firmware version in the device file. At that point, you can restart by clicking ‘check for update’.

At the end of the script, the section/system is re-installed, initiating a check of update application and verification of SHA-1 hash in new files and /system is dismantled:

After that, the device is reloaded into a new system.

Updater-script as it is

Updater-script as it is

Custom-made recovery

Until recently, in most cases it was possible to link the OTA-update archive (unless recovery had not been checked for replacement) from custom-made recovery, just by entering the file onto the device and selecting ‘install zip’. But starting from the script to update to 5.0, the script has changed. The previous versions used to check the file /system/build.prop:

Rather than the file, current scripts directly check the value of the system variable by requesting it from recovery:

And if you expand custom-made recovery (as applicable to TWRP version 2.8.0.0), you will see the following lines:

Version TWRP 2.8.6.1 has the following lines in the code (please note the word omni in the second row, the TWRP developer nick-named Dees Troy and also one of the active developers of OmniROM)

While the latest versions of CWM Touch and Philz written as follows:

It is those values that are returned by the validation script, interrupting the update at the very early stage and issuing an error showing the mismatch of the Android version on the device.

This is what response will be like when you try to make update 5.0.2 at Nexus 7 from custom recovery

This is what response will be like when you try to make update 5.0.2 at Nexus 7 from custom recovery

For comparative purposes, previous version updates of KTU84M to KTU84P can be provided. This update is small-size weighing as little 2.5 Mb. The update is primarily focused on improving security. If you open the archive, you will see that that only a small amount of system and radio files are patched and the script only checks them. This updated was normally installed with root, custom kernel and running Xposed Framework, as all that stuff is not checked for changes.

Updates for Nexus 6 and Nexus 9

The latest Google devices have a fundamentally different script structure. For these and (likely) future devices from Nexus Google added a unit-by-unit update to the OTA update assembly script. Rather than individual files, this update checks and updates units blocks in the file system/system. Further on in example ’66,…,524256′ – these are long lists of unit addresses:

This allowed Google engineers significantly simplify and speed up the OTA-update application for end devices and now the updater script weighs only 5 Kb. However, it has proved to be a headache for advanced users. At present, any changes to the system section will result in failure, including the presence of redundant files. Even the installation of the system as R/W will result in changing the hash in the superblock FS.

Summarizing the article, you can draw the following conclusions:

  1. The super-user’s privileges have no impact on the success of an update. What does have an impact are changes made by users and applications that have these rights. These changes cannot be frequently tracked and reversed.
  2. Whether root and changes made to the system could have an effect upon the success of an update every time depends on what is specifically changed in the system and what files are checked by the script. If the system has been changed or frozen/redundant system applications have been disabled through Titanium Backup kernel, custom recovery has been installed, Xposed Framework, Lucky Patcher, freedom, franco. Kernel updater, fashion statements for phones and all kinds of sound improvements and other boot animations, system fonts, and so on. All those things can influence the update.
  3. If you modify the system always leave the original files for backup provided that you plan to update via OTA. Copy them back to the cloud and rename in any way you like. You can make a Nandroid-backup of the section/system (read in the previous issue about Nandroid).
  4. If you remember what exactly you changed in the system, you can roll back nearly any time. Recovery always writes an error highlighted by an update. Having searched on Google the file name in the error you can sometime find which application is to be used to replace it. For example, /system/bin/thermal-engine-hh – /system/lib/power.msm8974.so replaces franco.Kernel updater and does not get it back even with firmware etched into the stock kernel and the application itself de-installed.
  5. For successful OTA application it is necessary to get back original files into the system. The most reliable way is to link the firmware to system.img, stock kernel and recovery before the application of the update (data and applications will not be lost).
  6. Well, here is the bottom line. If you are root and a lot of modifications, spare yourself any trouble and make at once a complete image of the new firmware, removing the key-w in flash-all.bat to save the data. Starting from the update to version 5.0, there remains a very slight possibility of tricking the script. Well and the next update might have a ‘block’ structure requiring only full stock for application.

A couple of the Editor’s remarks

Until recently, OTA updates in custom-made firmware (CyanogenMod, Paranoid) has always been made in the form of a zip with a full firmware version and it didn’t matter at all what changes had been made to the system before. Firmware has always been installed anew (while, of course, preserving user data and gapps). However CyanogenMod 11 introduced an Incremental Update feature which is a way simpler than the one used by Google. The update simply checks the integrity of firmware and replaces those files that was changed from the last version (normally, of nightly build) without any patches. And if you happen to miss one of updates, the following one will be traditionally available to you a full format. Simple and easy

A more exciting method is used in OmniROM. For an update it makes use of binary patches, but in the way done by Google. The first OTA update is always downloaded in full, after which it is stored on the memory card, stitched and not deleted from the card. The first OTA update is always downloaded in full, after which it is stored on the memory card, stitched and not deleted from the card. The following OTA-update comes as a binary patch, and after which the patch is superimposed on and linked to the update last saved on the memory card. The upside of this method is that the patch is not superimposed on the system, and the last update file and smartphone are linked together into firmware each time from the ground up (while retaining the data and settings). It is a nearly perfect method – saving traffic and any worries about conflicts with a modified system.

Update installation screen in CyanogenMod <b>error run nandroid-mobile.sh restore via adb</b> installation screen in CyanogenMod 12</p></div></div></div><br><h3>Leave a Reply</h3></div> <div><div><blockquote><h3>Related</h3></blockquote><div><h3>[Q] error message while restoring nandroid</h3>Hi, after i installed a new app (xposed framework) on my defy with quarx 2ndboot-nightly CM10-20130326-NIGHTLY-mb526.zip i got some problems and got stuck in a bootloop. well i had made a nandroid backup and simply wanted to restore it. but neither the actual backup nor an older are restored i always get after some time: error while restoring /system problem while restoring /system any ideas? i really do not want to set everything up from scratch again. I've had this problem a lot of times. I went to bootmenu and formatted system and data to ext4, then rebooted. After that I was somehow able to restore my backup. didn't solve it Try restoring from adb. Google it, there are many guides. EDIT - You can try this - Edit the ROM zip to delete files you don't need, flash the zip, then extract the files you changed from the system backup archive and paste in system using ES File Explorer <b>error run nandroid-mobile.sh restore via adb</b> reboot. well, in the end i installed from scratch via flashing, i also tried to restore via adb but it did not recognize the nandroid-mobile.sh restore command. google revealed that is not possible on cwm based recoverys? as far as i understood (no linux guy) nandroid is just a set of scripts, so i was missing that script? anyway i could save some time with pulling aps and data via nandroid manager when i had a working system again. still i am a bit unsecure now concerning trying out stuff, fearing that i again would not be able to restore a nandroid backup</div><div><h3>How to recover data from "adb backup --twrp" archive? Been through hell and back</h3>I have two backups I made using "adb backup --twrp" while my OnePlus one phone was in TWRP recovery 3.2.1-0 running LineageOS with a recent build (don't know exactly which one, but it was from Feb/March 2018). Each of the backups are about 6.0GB so they appear to be complete backups. I am trying to recover one app and its data (Signal/Textsecure) but the rest would be nice too. The backup files have .ab extensions. I am fairly android savvy and have been working on this for <i>error run nandroid-mobile.sh restore via adb,</i> your help is VERY MUCH APPRECIATED! I have access to Windows and Linux. I have tried the following: -"adb restore filename.ab" while in TWRP recovery. It appears to restore (progress bar goes, it reports success, etc), but no apps are restored. I have tried this both with totally wiped partitions/system/data and with a fresh install of LineageOS. As far as I can tell, <b>error run nandroid-mobile.sh restore via adb</b>, nothing happens. When doing a restore after a full wipe and trying to restart, TWRP warns that no OS is installed. -Restoring using the restore menu <i>error run nandroid-mobile.sh restore via adb</i> TWRP. Immediately upon clicking on the backup, the phone restarts and TWRP opens again. Not sure what's going on there. -Opening the backups in Titanium Backup, Nandroid manager, and a few other apps. None of them worked. Titanium backup crashes instantly in recover from ADB, doesn't recognize the backups in nandroid recovery mode. -Opening the .ab files in an archive manager, all of which report it isn't a valid tar archive. One time I was able to get a list of directories, and things looked pretty right, so I know at least some of the data should be there. Running variants of this command with different skip values, none of which produces a valid tar file dd if=file.ab bs=512 skip=1 of=test.tar Questions: - Is there a way to extract data from these backups in Linux or Windows outside of Android? From what I read, TWRP adds some stuff in the headers which makes them invalid tar files, and that doing "adb backup --twrp" is different from a regular TWRP backup. - Why is TWRP crashing? Is there a log I can look at for this and how? Maybe i can find a way to diagnose it that way. - Where does Signal store message data? I have a flat-file backup that may have this information depending on where it's stored, <i>error run nandroid-mobile.sh restore via adb</i>. - Can I somehow convert these backups to a different format that might be better-tolerated by TWRP or other apps? - Any good utilities for reading a corrupted tar file? I <a href=error loading type library dll all this utility would need to do is skip through the junk at the start.

[Q] "Script Failed" when using Backup add-on with Dropbox

I"m attempting to use the Backup program add-on to automatically back up my Kodi installation to my Dropbox account, but keep getting "Script failed" error messages. I've followed Rob Weber's instructions on GitHub, I created a Dropbox "app key" and "secret" and input that into Backup's settings. I've accessed my log error run nandroid-mobile.sh restore via adb to get the authorization code for Dropbox, and after going to the generated URL, Dropbox tells me "Success!" that I've connected my backup file to Dropbox. But when I go into the Backup add-on and try and do a backup, error run nandroid-mobile.sh restore via adb, I get a "Script Failed" message. When the scheduled time comes to do a backup, again, I just get a "Script Failed" message. Has anyone got the Backup add-on working successfully these days? Any advice on error run nandroid-mobile.sh restore via adb I might be going wrong? Doesn't appear to be a Dropbox-specific problem, as I was munin freebsd error code 1 to successfully connect with my Mac and designate that as the destination for the backup files. But Backup still throws up an error when initiating a backup. Is anyone having success with this program add-on? Trying to figure out if it's something with my system or the add-on has issues, error run nandroid-mobile.sh restore via adb. In case anyone in the future has this same issue, I found that unchecking the option to compress the older archives solved the issue of Backup throwing an error message. Seems to be working well now, though I get a message saying "Not all files were backed up." Not sure what that's about, but…

TWRP 2.8.6.2 Fails to Backup

I installed TWRP 2.8.6.2 from the link in the first post of the Lollipop thread (http://forum.xda-developers.com/phot.ton-q-t3073781 ). I assume this is the latest/correct version for PQ? I want to backup data so I can reformat data as f2fs and be able to use latest kernel. I've tried backing up just data, or all four selections, with and without compression. Everything I've tried fails with error 255. The log shows /data/data/com.skype.radier failed. So I deleted error run nandroid-mobile.sh restore via adb cache, data, then uninstalled. Retried backup again error run nandroid-mobile.sh restore via adb still fail. Tried to manually delete folder, it won't delete nor will any of the subfolders (error 39 from es explorer). Tried to delete using TWRP's file manager, still won't delete (ERROR=1)/ a piece of TWRP log where it shows the errors. I:addFile '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94 F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' including root: 1 E:Error adding file '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94 F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' to '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q//data.f2fs.win000' I:ERROR tarList for thread ID 0 E:Error creating backup, error run nandroid-mobile.sh restore via adb. I:InfoManager saving '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q/data.info' E:createTarFork() process ended with ERROR=255 Backup Failed. Well just great. I wanted to backup but instead deleted everything. After posting I kept searching and trying ways to be able to delete that. Finally came to something that suggested using fcsk to check/repair the filesystem. Said to boot to recovery, adb shell, unmount and then run it. That didnt work cuz there was no unmount command in adb shell that I could find. Then I found in the TWRP menu there was a repair filesystem command, thought that was great! Ran it. And it wiped my data folder completely. Not very happy right now. I had the same problem as you when trying to convert to F2FS, and lost many hours of work as well! In my case the backup actually worked when using compression, so I thought all was good even though I never could get it to restore. I was able to get some of the data back by untarring the backup files themselves though, error run nandroid-mobile.sh restore via adb, so you could maybe even look at the unsuccessful backup files if you had something important to recover. In post 161 of this thread http://forum.xda-developers.com/phot.1/post64064173 a developer has compiled TWRP 2.8.7.0 for the Photon Q and it appears backup works. Error run nandroid-mobile.sh restore via adb never have tried it myself though as I hadn't seen the post in time. I just ended up using titanium backup. Well I'm in an even worse situation now. I tried restoring from the failed backup and now my phone crashes and reboots a minute or two after booting. So I figured I better reinstall gapps. However, I can't get into recovery anymore. Just sits forever of the TeamWin screen. Reloaded recovery thru adb fastboot and it still does the same thing. So I can't even get into recovery to try flashing gapps again or if it came to it wipe data and start clean. I'm phoneless. RSD Lite back to stock.

[Q] Recover apps from TWRP backup using TitaniumBackup does not work

When I try to recover my apps using Titanium Backup's "Extract from Nandroid" feature, it says "Could not find any data in this TWRP backup" The files in my TWRP backup folder are data.ext4.win000 data.ext4.win001 data.ext4.win002 md5 for the above recover.log Any help would be appreciated Yup, same problem here. Im on a Galaxy Nexus running XenonHD and TWRP. I've tried unpacking them on my pc, so i could use an emulator and run my phone through there. That kinda works, and using Titanium Backup, it seems to extract it without an error. But afterwards, the app is very glitchy. Im guessing Titanium Backup doesnt really do well on TWRP as i had no error run nandroid-mobile.sh restore via adb using clockworkmod. I'm experiencing the same problem running Marshmallow trying to restore apps from a TWRP backup (Galaxy S4). At first, Titanium backup just refused to even see the backup files (although it accepts the containing folder as a backup location). Once it finally and magically accepted to see the backups it now tells me that it cant find any data in them. Has anyone solved this yet?
07-25-2010 08:28 PM

tools

  1. lunchbox88's Avatar

    I'm not sure when it happened, but error run nandroid-mobile.sh restore via adb after I flashed Kool-Aid Sugar Free (this is what my one good backup restores to), I can't get a good back up.

    If I try to create a backup, it appears to work, but if I try to restore it, it fails with the error "Error : run nandroid-mobile.sh restore via adb."

    Sometimes when I try to do a backup (I think it's only if I select nandroid + ext), I get the error "Error : run nandroid-mobile.sh from adb"

    Now, I haven't tried running anything from adb yet, so I don't know what results that will yield

    Any ideas? I'm tired of having to restore from a backup from 6/15 and then reload everything.

    Thanks!

    07-13-2010 06:54 AM

    Like0

  2. Fazulka's Avatar

    This happens when revocery mode determines your battery is low. Charge the phone fully and it should work again.

    07-13-2010 08:24 AM

    Like0

  3. chompy's Avatar

    or if your mem card is full. Each nandroid BU can be 300MB!

    07-13-2010 10:18 AM

    Like0

  4. lunchbox88's Avatar

    My mem card isn't even half full, so I don't think that's it. I'm charging now, but I think the last time I tried, my battery was above 85%. I could be wrong on that though. I'll let you know what I find.

    Thanks for the responses!

    07-13-2010 10:46 AM

    Like0

  5. Thrifter.com
  6. beezy's Avatar

    Which version of recovery do you have? Also do like stated full charge and maybe try just a nadroid backup without ext.

    07-13-2010 10:52 AM

    Like0

  7. voghan's Avatar

    I will get this on occasion as well. I normally flash the rom I originally made the nandroid off of then go and restore my nandroid. I've had this happen just recently when going from Fresh 2.3.3 to the CM rom. I think it might have to do with restoring over an ASOP roms.

    07-13-2010 10:55 AM

    Like0

  8. The Mac's Avatar

    ive restored/backed up over several of CMs froyo asop roms and never had a problem.

    what recovery version are you using? im using RA 1.6.2, i think allot of people are usuing 1.5.2

    also, there is no EXT on earlier CM 6 Froyo roms, it was using JIT instead of dalvik and wouldnt even see the EXT partition, error run nandroid-mobile.sh restore via adb, so it could be being difficult if you arent using the latest beta.

    07-13-2010 11:47 AM

    Like0

  9. lunchbox88's Avatar

    I'm using RA 1.5.2.

    I just did a backup without the ext, and it error run nandroid-mobile.sh restore via adb it worked. Is there a way to test it? Like, can I try restoring that new backup even though it's exactly what I have now?

    07-13-2010 11:54 AM

    Like0

  10. The Mac's Avatar

    id push 1.6.2, its less buggy. I know people say you should use 1.5.2, but ive never had any of the problems people claim to have with 1.5.2 with it, and have had zero compatibility issues.

    07-13-2010 11:58 AM

    Like0

  11. voghan's Avatar

    I'm using 1.5.2 on my Hero. I have an EXT setup so maybe that was the issue.

    07-13-2010 01:35 PM

    Like0

  12. beezy's Avatar

    Originally Posted by voghan

    I'm using 1.5.2 on my Hero. I have an EXT setup so maybe that was the issue.

    I have 1.5.2 on my personal everyday hero and i never had this problem,but i also have a dummy/test hero that just got not to long ago and it has 1.6.2 and i still see a couple bugs but i like it better cause it lets you shut down the phone.
    Keep in mind tho i've probably made about 10 nadroid total.I quite making them and if something goes wrong i just wipe and flash a differnet rom i have on my sd card.lol

    Edit., error run nandroid-mobile.sh restore via adb. I also get wipe error on both recoverys,maybe it just me and i flash to much,both are great to use,which ever floats your boat.

    07-13-2010 02:15 PM

    Like0

  13. voghan's Avatar

    It's the battery. Had it happen today. Plugged it in then tried again and it worked. Must have some internal check to make sure battery is not low.

    07-14-2010 11:43 PM

    Like0

  14. RethX's Avatar

    good to know. I always wondered what would happen if the battery died mid backup or restore.

    07-15-2010 01:12 AM

    Like0

  15. flipfone's Avatar

    07-15-2010 01:45 AM

    Like0

  16. lunchbox88's Avatar

    Mine appears to be backing up OK (as long as I don't select nand + ext), but if I try to restore, I get the error "Error : run 'nandroid-mobile.sh restore' via adb!"

    07-15-2010 07:23 AM

    Like0

  17. lunchbox88's Avatar

    OK, it's not backing up OK.

    I just created a new backup. Here's a list of the files that it created:
    boot.img
    misc.img
    recovery.img
    system.img

    When I look at one of the backups that will actually restore, it shows these files:
    boot.img
    cache.img
    data.img
    misc.img
    nandroid.md5
    recovery.img
    system.img

    Any idea why this is happening?

    07-20-2010 10:58 AM

    Like0

  18. lunchbox88's Avatar

    I've flashed 1.6.2, and I still have the problem.

    Last time I tried, the battery was at 97%, and the SD card had 2.7 GB free. I've tried copying everything off the SD Card, formatting it, and then trying to make a nandroid backup, and it does the same thing.

    Any ideas?

    07-25-2010 09:51 AM

    Like0

  19. lunchbox88's Avatar

    It's something weird with my SD Card. I found the 2 GB that came with the phone, put it in, and successfully created a back up. I guess I'll have a card that only has backup files on it, and on for everything else. Could be worse, I guess.

    07-25-2010 07:35 PM

    Like0

  20. flipfone's Avatar

    When you get a chance try copying everything off your sdcard. then reformat it in your phone, using recovery. then try again. it could be that you formatted with the pc. or another recovery and a partition is ext4.

    07-25-2010 08:28 PM

    Like0

LINK TO POST COPIED TO CLIPBOARD

What is ADB? ADB is short for Android Debug Bridge, a versatile command-line tool that lets you communicate with a device. It was mainly for developers to debug apps, but now basic users can also use it to perform many useful activities between computer and their Android smartphones. In this article, we are going to show you how to install ADB in Windows computer and how to use ADB to do something interesting to Android mobile phone.

Part 1. Install ADB on Windows

It is quite easy to install and set up ADB in Windows computer. Actually, the size of the tool is merely 4.51MB, so it won’t take up much space on your computer. Here we Windows 10 as example.

  • Step 1. Download Platform Tools for Windows. Confirm to download on the new window and save the zip file to a folder on your PC.
  • Step 2. Extract the zip file after download.
  • Step 3. Press Shift key and right click within the extracted folder, error run nandroid-mobile.sh restore via adb, then choose Open PowerShell window here (or Open command window here on some computers)
    install-use-adb-windows
  • Step 4. A command prompt should appear.

This means that ADB is set up on your Windows computer. In order to communicate with your Android phone, however, you also need to enable USB debugging on your handset.

Part 2. Enable USB Debugging on Your Mobile Phone

USB debugging must be turned on in order to use ADB. The steps to turn on USB debugging are varied on different versions of Android OS, error run nandroid-mobile.sh restore via adb, but the instruction below should work for most Android smartphones used nowadays.

  • Step 1. Go to Settings > About phone.
  • Step 2. Scroll down to find and tap Build number for 7 times.
  • Step 3. Back to Settings, then find and tap Developer options.
  • Step 4. Within Developer options, enable USB debugging. Confirm your choice.
  • Step 5. Connect your phone to PC.
  • Step 6. Choose Allow when “Allow USB debugging?” window pops up on your phone screen.
    Enable USB Debugging on Your Mobile Phone

Note: It is suggested that tick Always allow this computer if you are using a trusted computer in order to get smooth experience with ADB and in case of accidents when you need to rescue data but unable to operate on the phone, like Android broken screen data recovery.

Part 3. Test ADB

Once you have finished the above preparing work, you can test if ADB works.

  • Step 1. Run ADB command window as described on Part 1.
  • Step 2, error run nandroid-mobile.sh restore via adb. Connect your phone to PC, and type adb devices in command window and hit Enter.
    Test ADB

If everything goes right, a result will return as above (with different series code). If nothing appears, then you should check if the driver for your phone is properly installed. A straight indication of functional driver is that your phone should be recognized by the computer.

Part 4. Useful Things You Can Do with ADB

Once ADB is correctly installed on your Windows computer, you can do many useful things with ADB. The following is just a small portion of all the things it can do. You will find that lots of tools can do the same thing in normal environment, but ADB can do it easily and may play important role on some occasions.
USB debugging must be turned on!

Option 1. Backup and Restore Android with ADB

Backup is not necessarily the most frequently used function for Android users, error run nandroid-mobile.sh restore via adb, but it should be the very first thing whenever we try anything new or danger. In case of accidents, a backup of mobile phone will work like a saver to our life. ADB can help you make backups for your Android smartphone with no need of root or custom recovery.

adb backup -all -f <path/filename.ab>
adb restore <path/filename.ab>
The path should be a location on your computer system drive. For example,
adb backup -all -f /Backup/backup1.ab

Notes:

  • The backups are saved to computer instead of phone memory or SD card.
  • You’ll need to unlock your phone to allow the backup to start.
  • The backup mainly contains documents and media files on your phone. For a literarily full backup of phone data and whole system, refer how to make a Nandroid backup in custom recovery.

Option 2. Install APK for Android from Computer

There are already lots of methods to install apps to Android phone, including installing apk files on mobile phone, but occasionally you may need to install APK to Android phone from computer. This is especially useful if you know that the installation is completely silent with no need of operation on phone screen.

adb install <path to the apk on your computer>
The path should be a location on your computer system drive, error run nandroid-mobile.sh restore via adb. Please move the apk file to the system drive if it is not. For example,
adb install /MyDownloads/TitaniumBackup.apk

Notes:

  • No need to operate on phone screen.
  • No prompt of permissions from the app.
  • No need to enable Unknown source on mobile phone.
  • Be care of apk files containing malware.

This function may work magically when you want to install an app to your phone but unable to control the device, lets terrorise the terrorists due to broken or black screen.

Option 3. Reboot Phone to Recovery Mode and Bootloader

In recovery mode, people can clear cache and data, factory reset or backup mobile phone. In bootloader (or Download mode for Samsung), people can flash ROMs to handset. If you don’t know anything about recovery mode and gta iv .exe application error, please make sure you know it clearly and need it first.

adb reboot recovery
adb reboot bootloader

Notes:

  • No need to press key/button groups on phone body.
  • Occasionally, you may need to reboot manually or even remove battery when the command fails.
  • After every reboot, you’ll need to reconnect the phone in order to let ADB work

Option 4. Convert SD Card as Internal Storage with ADB

Since Android Marshmallow, users can format SD card as internal storage, which effectively reduces insufficient storage problem. The conversion is easy to do on Settings > Storage if your phone is supported for the feature. However, some manufacturers intentionally hide this function from users even if their smartphones error run nandroid-mobile.sh restore via adb upgraded to Android 6.0 or newer. With ADB, we can convert SD card as internal storage when the option is invisible.

Warning: Please move or back up SD files card first. After the conversion, the SD card won’t be recognized by other mobile phones or computers. Once your phone is reset or dead, you may find the SD card inaccessible by any device.

  • Step 1. Launch ADB command window.
  • Step 2. Connect the phone inserted with SD card to computer.
  • Step 3. Type the following commands and hit enter after each:
    adb shell
    sm list-disks
    sm partition disk:179,64 private
  • Step 4. Go to Settings > Storage to check your storage status.

Note: If there is no change in phone storage, error run nandroid-mobile.sh restore via adb, then you may reboot error run nandroid-mobile.sh restore via adb and check the storage again.

The above are 4 useful things that Android users may like or need to do with ADB. If you have more ideas or questions about what we can do with ADB, please kindly share with us.

How to Unbrick Your Android Phone: 4 Methods for Recovery

So you've bricked your phone. You flashed a ROM, installed a mod, tweaked a system file, or did something else---and now your phone won't boot.

Don't panic! It's almost certainly fixable. Here's how to unbrick an Android phone.

What Do the Terms 'Bricking' or a 'Bricked Phone' Mean?

'Bricking' your phone essentially means that your once useful device is now only as useful as a brick. A 'bricked phone' is usually unresponsive, won't power on, and doesn't function normally.

How Is Your Phone Bricked?

The steps for how to unbrick a phone depend on how it's bricked in the first place. There are two categories of bricked phones:

  • The soft brick. The phone freezes on the Android boot screen, gets stuck in a boot loop, or just goes straight to recovery, error run nandroid-mobile.sh restore via adb. So long as something happens when you press the power button, it's soft bricked. The good news is these are pretty easy to fix.
  • The hard brick. You push the power button, and nothing happens. Hard bricks can be caused by issues like attempting to flash an incompatible ROM or kernel, and there's normally no software solution for them. Hard bricks are terrible news, but fortunately, they're quite rare.

Most likely, you're soft bricked, and you'll see something like the image above. While the differences in how various devices work make it hard to come up with a catch-all solution to unbrick Android, there are four common tricks you can try to get yourself back on track:

  • Wipe the data, error run nandroid-mobile.sh restore via adb, then re-flash a custom ROM
  • Disable Xposed mods through recovery
  • Restore a Nandroid backup
  • Flash a factory image

Before you get started, make sure your phone and computer are set up and ready with the proper tools.

What You Need to Unbrick an Android Phone

Chances are, you already have most of the tools you need to unbrick your phone. They're the same tools you used to root your device and flash ROMs, so you should already be familiar with how they work. Even so, double-check before you begin.

Most important is a custom recovery. You likely installed this when you rooted your phone, error run nandroid-mobile.sh restore via adb, but it can sometimes get overwritten by the stock recovery or wiped entirely. If you do need to reinstall it, we recommend going with TWRP. It's a fully-featured custom recovery that's too easy to use and has builds for most popular devices.

Next, you might need Fastboot and ADB. These are commonly used for rooting and flashing system mods, and you can get both from the Android Developers website. Check our primer on how to use Fastboot and ADB if you aren't familiar with them.

And finally, some manufacturers use special software to flash factory images. Hopefully, you can error run nandroid-mobile.sh restore via adb doing this, but if you need to, you can use Odin for Samsung, the LG Flash Tool for LG devices, or the ZTE Unbrick Tool if you've got a ZTE device. Just make sure that they support your specific model of device.

Most of these tools will let you fix a bricked Android phone using a PC. However, you can often do the job directly on the phone itself.

1. Wipe Data and Re-Flash a Custom ROM

Try this method if: You error run nandroid-mobile.sh restore via adb a ROM, and now Android won't boot.

One of the most likely causes error create handle ip_queue soft bricking your phone is when you have problems when flashing a new custom ROM. The culprit here is often that you didn't wipe your data first.

This is referred to as a "dirty flash," and occurs when you choose to forego the inconvenience of having to restore your apps and data by flashing a new ROM on top of your old one. As a general rule, you can get away with it if you're flashing a newer version of your existing ROM, but you must always wipe your data whenever you flash a different ROM.

Fortunately, it's easy to fix---as long as you've backed up your phone properly. Error run nandroid-mobile.sh restore via adb you haven't, well, you've learned an important lesson the hard way. Follow these steps:

  1. Boot into your custom recovery.
  2. Navigate to the Wipe option and choose Advanced Wipe.
  3. Check the box marked Data (you can wipe the system, ART cache, error run nandroid-mobile.sh restore via adb, and cache again, too), then hit Confirm.
  4. Re-flash your custom ROM.

[gallery columns="2" sysfader iexplore exe error application ids="875484,875485"]

Wiping your data effectively performs a factory reset, but it shouldn't clear your internal storage or SD card (although, error run nandroid-mobile.sh restore via adb, again, you should back it up just to be safe). When you restart your phone, you'll see the Android setup screen. After entering your Google account information, your apps should begin reinstalling automatically.

If you need to, you can restore your data from your Nandroid backup. See the Restore a Nandroid Backup section below.

2. Disable Xposed Modules in Recovery

Try this method if: You get boot loops after installing a new Xposed module.

The Xposed Framework isn't as common as it once was, but it's still a simple way to mod your phone, and also one of the most dangerous.

The best Xposed modules are so easy to install---many of them are available in the Play Store---that they lull you into a false sense of security, error run nandroid-mobile.sh restore via adb. It's unlikely anyone makes a Nandroid backup before installing a new Xposed module, even though they can brick your phone.

Use ADB Push to Install the Xposed Uninstaller

The best way to deal with these problems is with the Xposed Uninstaller, if it's available for your version of Android. This is a small flashable ZIP that you can install through the recovery to remove Xposed from your device.

If you don't already have it on your phone, you can put it on an SD card, or you might be able to copy it over using the ADB push method:

  1. Download the Xposed Uninstaller to your desktop.
  2. Connect your phone to your computer via USB and boot into recovery.
  3. Launch the command prompt (Windows) or Terminal (Mac) and use the cd command to change the directory to where you have adb installed.
  4. Type adb push [full path to xposed uninstaller.zip] [full path to destination]. On Mac and Linux, error run nandroid-mobile.sh restore via adb, precede error run nandroid-mobile.sh restore via adb command with ./ (such as ./adb).
  5. When the file finishes copying, flash it through the recovery.

How to Disable Xposed Modules in Recovery

If you can't use ADB push and the Xposed Uninstaller, try either of these solutions.

This method lets you disable Xposed through recovery:

  1. Boot into recovery, then navigate to Advanced > Terminal command.
  2. Create a file called /data/data/de.robv.android.xposed.installer/conf/disabled
  3. Reboot your phone.

This method prevents Xposed modules from starting:

  1. Boot into recovery and select File Manager.
  2. Navigate to the folder /data/data/de.robv.android.xposed.installer/conf/ then delete the file modules.list
  3. Reboot your phone.

None of these solutions will undo any changes the modules have made to your system. If these changes caused your phone to brick, you will have to restore your Nandroid backup.

3. Restore a Nandroid Backup

Try this method if: You need to remove other system mods, replace a tweaked system file, or if the methods above didn't work.

The Nandroid backup is the safety net for Android mods and tweaks. It's a complete snapshot of your phone---not just your data and apps, but of the operating system itself. So long as you can access your custom recovery and have a Nandroid backup, you will be able to get your soft bricked device up and running. To do so:

  1. Boot into recovery and navigate to Restore.
  2. Select your backup from the list, confirm, and wait while it's restored.
  3. Reboot your phone.

Nandroid backups are a bit of a pain to make. They take a while and cannot be done in the background. But they're worth it: they're the simplest way to unbrick your phone.

Recover Data From a Nandroid Backup

A Nandroid backup can also save the day if you had to wipe your data and didn't back it error run nandroid-mobile.sh restore via adb in an easily restorable form. It's possible to extract specific parts of a Nandroid, so you can restore your apps and data without needing to restore the operating system as well.

Here are the instructions for this:

  1. Boot into Android and install Titanium Backup from the Play Store. While this app hasn't been updated for a while, it's still one of the best options for this task.
  2. Tap the menu button and navigate to Special Backup/Restore > Extract from Nandroid Backup.
  3. Select your backup from the list.
  4. Choose whether to restore apps, data, or both, and select them (or hit Select All).
  5. Tap the green tick icon to start the restore process.

4. Flash a Factory Image

Try this method if: None of the other options work.

If your attempts at unbricking Android have failed so far, error run nandroid-mobile.sh restore via adb, the nuclear option is to re-flash a factory image. This restores the phone to its original state and will wipe your internal storage as well as everything else, error run nandroid-mobile.sh restore via adb. It'll also unroot your phone.

Because it wipes everything, you might be better off trying to flash a stock ROM first. OnePlus actually offers flashable ROMs for recovery rather than factory images, and you'll find similar for virtually every device at xda-developers.com. In many cases, you'll be able to flash a pre-rooted stock ROM for added convenience.

Where flashing a factory image differs from flashing a ROM is that it happens over a connection to your desktop computer rather than through recovery. Some devices use the Fastboot tool from the Android SDK, error run nandroid-mobile.sh restore via adb, but others use custom software. Samsung uses the Odin tool, for instance.

Because of the different methods used, the instructions for flashing a factory image differ for each device. And not all manufacturers make their firmware publicly available, so you have to error run nandroid-mobile.sh restore via adb them from unofficial sources.

Here's where to find factory images for some popular Android brands:

What About Hard Bricks?

Hard bricked phones are notoriously more difficult to fix, but thankfully they're also much rarer.

How to Unbrick a Hard Bricked Android Phone

First, make sure the phone really is bricked---plug it in and leave it charging for a while. Attempt to reset it by holding the power button down for 10-15 seconds (or pulling your battery if you've got an older device). You may also want to try plugging it into your computer, you can be pretty sure that your phone is hard bricked if it is not detected by your PC.

If it is definitely hard bricked, then you may be out of luck. A few phones can be revived with a USB Jig, a tiny device that plugs into the USB port and puts the phone into Download Mode to reinstall the stock firmware.

You can find USB Jigs for hard bricked phones for cheap on eBay, but only for a very small number of old devices. Even then, there's no guarantee that they'll work.

Beyond that, you may need to send your phone in for repair (though rooting it might have voided your warranty) or seek out a local phone repair person. But you most likely will end up needing to buy a new device.

Tweak Android Safely

Hopefully, this guide has helped you to unbrick your Android phone. And hopefully, your experience hasn't put you off rooting and hacking Android altogether.

But if you'd rather play it safe in future, you can still have a lot of fun with your phone. Take a look at our guide to the best Android tweaks you can make without rooting for some amazing ideas.

Do you want to revert Android phone back to stock ROM just for selling it out or doing a warranty claim?

Besides this, many users want to restore Android phone back to stock ROM for reasons like installing system updates, or bringing their phone back to the normal state because it is installed with so many mods and tweaks, etc.

Well whatever the reason is, the important above all this is to know how to revert any Android back to stock ROM. If you are not having any idea about this, then don’t get tense…!

This post will help you get knowledge of it. So, go through this article to know how to install stock ROM on android.

What Does A Stock ROM Mean?

When you purchase a new phone the OS that runs on it, is the stock ROM. Stock means one which the OEM has preloaded and designed into phones.

Stock ROMs are mainly based on several versions of Android OS. In devices such as Google Pixel, stock ROM completely runs on Vanilla or pure Android.

Why Stock ROM Is Important?

Stock ROM has the biggest advantage over custom ROMs. When a phone is purchased, error run nandroid-mobile.sh restore via adb, in the starting period the stock ROM works very smoothly and even if it has some bugs then it can be fixed easily.

On the other hand, for installing the custom ROM your device needs to be rooted. Nor can you use any banking app on your custom ROM device. Other than this, you will encounter issues like bugs and crashes with custom ROMs.

How To Revert Android Device Back To Stock ROM?

Let’s check the requirements which your device must have before starting with the instructions guideline.

Prerequisites:

  1. It’s compulsory that your device is installed with TWRP. Users who have flashed the GSI ROM through the fastboot command. At first, they also need to flash the TWRP.
  2. On your PC make easy downloading and installation of Android SDK and Platform Tools.
  1. After this, on your device download the stock firmware.
  1. Keep complete backup of entire Android device data. You can also save entire files in internal storage.

It’s time to follow the error run nandroid-mobile.sh restore via adb steps to revert any Android device back to stock ROM.

1: Restore A Nandroid Backup

Using Nandroid Backup is the easiest way to revert back any Android phone to stock ROM.

Nandroid backup is a complete system backup that gets created within the recovery. It’s important to create one backup copy every time you install any new type of mod or flash a new ROM.

Actually Nandroid backup takes snapshots of the phone such as its data, OS, apps, and everything. So by restoring Nandroid Backup, ROM will also get restored.

Having a backup meanwhile using the stock ROM is all that you need.

Nandroid backup is one short-term option to go back to Stock Android from a Custom ROM, error run nandroid-mobile.sh restore via adb. The backup will restore the old data and apps, which means uninstalled apps, will appear again but the text message you have received will disappear.

  • First, you need to boot up your device in the TWRP Recovery mode.  For this either you need to make use of hardware key combinations or ADB commands. Before doing this, error run nandroid-mobile.sh restore via adb, you need to enable both the Developer Options and the USB Debugging.
  • Apart from this, installation of Android SDK & Platform Tools is needed.
  • After this, connect the device with your PC through a USB cable. Now move towards the folder of platform tools and then type cmd. After that type the following command for booting up your device into TWRP Recovery mode.

adb reboot recovery

  • Now within this TWRP recovery mode, move to wipe >advanced wipe option. After that select data, System, cache, and Dalvik.

revert any Android phone back to stock ROM

  • Do a right side swipe to clear all the partitions which were selected.
  • After completing all this, move to the TWRP Recovery mode.
  • Now you have two options to go with: one is applicable when your Nandroid backup and the other one is when you don’t have such backup.
  • If you are having the Nandroid backup then hit the Restore” option and choose the recent backup. After that make a right side swipe for easy restoration.

Revert Android Phone Back To Stock ROM

  • When you don’t have the backup go towards the Reboot screen and choose Bootloader. Doing this will boot up your device in very fastboot mode.
  • Once the device gets booted in the Fastboot/Bootloader mode, just connect the device with your PC through USB. After that carefully follow the instructions as per the device for flashing up mysql error 1045 stock firmware.
  • Wait until the whole process gets over. Once it’s done, you will notice that your device will automatically boot up to the Android OS, error run nandroid-mobile.sh restore via adb. If this won’t happen, reboot the device by using the fastboot reboot command or hardware key.

2: Flash a Stock ROM

If in your case, restoring the Nandroid backup is not a valid option then another next solution that you must try to revert Android phone back to Stock ROM is flashing a stock ROM.

But this method has negative points too, that is you need to do factory reset mainly these methods. So it will be better if you keep the proper backup of your Android data.

Well switching from custom ROM to the stock ROM has also some benefits. Like you can easily find a ROM’s pre-rooted version and flashing the ROM also gets too easy to be done.

If you are a user of some less popular android devices then searching for the Stock ROM is quite a trickier task to perform.

If you are a user of a OnePlus device then you can easily download the flashable stock ROM from the OnePlus website.

Steps To Flash A Stock ROM

Follow the below-given steps to flash stock ROM.

  • Search the stock ROM for your Android phone. If you have no knowledge about your stock ROM then visit the XDA developers forum. As it is seen that stock ROMs are often present at the top of the development board.
  • Download ROM on your phone.
  • Back up the entire data.
  • Boot up into the recovery mode.
  • Choose the Wipe option for factory resetting your phone. To start the wipe process, swipe the bar.

This option is completely optional because if you don’t do it chances are high that you may encounter bugs or be stuck into a bootloop.

  • Now from the recovery home screen, go towards your downloaded stock ROM, and then install it.
  • Move the bar to start the installation process.
  • Swipe the bar to begin the installation. You can reboot your phone when it’s finished.

If you have downloaded some pre-rooted stock ROM then you don’t pawn error undefined symbol to do anything.  But if you are using a non-rooted ROM and willing to revert it back to stock ROM. In that case, you need to re-lock the bootloader. Note: this method will wipe out your android phone data.

3: Flash a Factory Image

Another alternative method to revert Android phone back to stock ROM is by flashing a factory image. This method will take your phone to the state just like the way when you have unboxed it for the first time.

All you have to do is lock the Bootloader and then your device is factory fresh. If you want to completely reset your device then flash factory image is one of the best options to go with.

Steps to Flash a Factory Image

The process of flashing a factory image may vary for different devices. For the pixel you can use these steps:

  • Download and install the ADB and Fastboot tools.
  • After that from the android website, you have to download the factory image. Now unzip the download over your desktop.
  • Using the USB cable connects your Android phone and boots into the Fastboot mode.
  • Open the Terminal app or Command Prompt.
  • In the opened command prompt window, execute flash-all.sh on macOS or Linux or flash-all.bat on Windows.
  • Once the whole process gets over, just reboot your device.

This will take you to the stock, unrooted ROM along with the stock recovery. You need to lock the bootloader, in order to get back to the normal state.

Note: Flashing the factory image may also have a chance to completely wipe out your phone’s data.

4: Stock Firmware Image i/o error 3ds max back to stock firmware adopts a similar type of technique which is used for installing ROMs and mods in 1st place.

After downloading the original software or getting the appropriate backup the whole process will only take a few minutes to get over.

Note: executing stock firmware for the phone is quite different from simply running any stock Android.

Conclusion:

Here I have provided ample information on how to revert any Android phone back to stock ROM.

Now, it’s time to apply the above-given methods. I hope you liked this article and it turns out to be helpful for you in resolving your issue.

If you are having any queries or questions regarding this article then feel free to share with us on our Facebookpage.

James Leak

James Leak

James Leak is a technology expert and lives in New York. Previously, he was working on Symbian OS and was trying to solve many issues related to it. From childhood, he was very much interested in technology field and loves to write blogs related to Android and other OS. So he maintained that and currently, James is working for androiddata-recovery.com where he contribute several articles about errors/issues or data loss situation related to Android. He keeps daily updates on news or rumors or what is happening in this new technology world. Apart from blogging, he loves to travel, play games and reading books.

Categories Android Data RecoveryTags Go Back to Stock Android From a Custom ROM, restore Android phone back to stock ROM, Revert Android Phone Back To Stock ROM, revert any Android phone back to stock ROM

How To: Root the Motorola Milestone

I. Before You Begin

1. This ONLY works on the Motorola Milestone, NOT the Motorola Droid (you must have a GSM Motorola Milestone).

II. Setup ADB and ADBRecovery

1. Do our How To Setup ADB

How To Setup ADB

2. Once you have done that, come back to this procedure and download ADBRecovery.

ADBRecovery

3. Extract it’s contents to somewhere on your computer.

4. Plug your phone in normally and mount the SD card (so we can transfer files to it from our computer).

5. Copy the just the update.zip file and the folder named “recovery” from inside the ADBRecovery > in_sd_root folder that we extracted earlier to the root of the SD card in your phone (NOT in any folders on the sd card just on the sd card itself).

6. Turn off your phone.

7. Turn the phone back on while holding the Camera button down until the ! screen comes up.

8. Once the ! comes up, let go of the Camera button and then hold down Volume Up and press the Camera button until a menu appears.

9. Choose apply sdcard:update.zip and wait for it to flash the update.

III. Performing a Nandroid Backup Through ADB

1. Leaving your phone in recovery mode after it flashes the update.zip, plug it in to your computer via USB cable.

2. On your computer, open the command prompt (Start >Type in cmd and hit enter).

3. In the command prompt type the following with hitting enter at the end of each line:

cd\
cd AndroidSDK\tools\
adb shell
nandroid-mobile.sh –backup

*the — in the last line above is actually two hyphens side by side

4. Once it is done with the backup, error run nandroid-mobile.sh restore via adb, type the following and hit enter:

reboot

5. Let the phone reboot into normal mode.

IV. Load the Custom Android 2.1 ROM w/ Root via Nandroid

1. Plug your phone into the computer via USB cable and mount the SD card (so we can acm driver error fix files to it).

2. Search your SD card for the folder “nandroid” and copy it to somewhere on your computer (this is so error1606 autocad 2008 can copy it back to your SD card later to unroot if you want).

3. Download the Android 2.1 Nandroid Backup here and save it to your computer.

Android 2.1 Nandroid Backup (EU version)

4. Extract the contents of the Milestone-Android 2.1 w Root .zip file you downloaded above somewhere on your computer. Then copy all the files from inside the extracted folder (just the files like “system.img” “boot.img” etc. NOT the folder itself) into the nandroid > console=ttyS2,115200n8 > Milestone-BbCcDMRS-20100329-2033 folder (your exact names of the folders may be different) on your SD card.  Then hit yes to Copy and Replace on all the files.

5. Unplug the phone once it has finished transferring the files over.

6. Turn off your phone.

7. Turn the phone back on while holding the Camera button down until the ! screen comes up.

8. Once the ! comes up, let go of the Camera button and then hold down Volume Up and press the Camera button until a menu appears.

9. Choose apply sdcard:update.zip and wait for it to flash the update and then plug the phone in to your computer via USB cable.

10. Open the command prompt again and type the following with hitting enter at the end of each line:

cd\
cd AndroidSDK\tools\
adb shell
nandroid-mobile.sh –restore

*the — in the last line above is actually two hyphens side by side

10. Once it is done with the restore, type the following and hit enter:

reboot

11. DONE!

VII. (Optional) Load a Custom ROM via Nandroid

1. Head to our How To Load a Custom ROM on the Motorola Milestone to load a custom ROM on the phone with the nexus launcher, wifi tethering and other features!

Thanks to Expansys!

If you enjoyed this, please consider sharing it

0 Comments

Leave a Comment