Related
Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron
I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.
Was going to ask a dumb question but I figured it out
i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.
jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..
Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?
I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?
I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?
well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
Okay, have found a lot of threads similar to this, but with key differences that are making the answers not-terribly-helpful in my particular circumstances. Not a comment on the answers, but enough that I feel the need to ask my question specifically.
I am trying to gain more control over my MyTouch 4g Slide (aka Doubleshot), obviously on T-Mobile.
It is running Android 2.3.4, and has hboot 1.45.0013. I have wiped it a few times in the process of fuxing with it, so right now I'm not worried about losing anything other than basic function (i.e., bricking it is still bad).
I have tried the zergrush exploit (it's been closed),
have managed to unlock the bootloader using the HTC unlock tool,
and have managed to flash the appropriate Clockworkmod recovery and get the blue menu to come up.
My overall goal isn't to do any major overhauls- I want to be able to allow some apps to turn my GPS on and off, clean out some bloatware, and put some new ringtones into the same folder as the stock ones. My understanding is that temporary root access is enough to do these things- go in and clean up, change some permissions on apps, then go back to being a normal user, just like with a well-managed Linux computer.
I just can't seem to get the next step to work.
My understanding is that I now somehow use Clockworkmod to install Superuser from the .zip archive. The options I get in the recovery screen are:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
My impression is that I should be using "install zip from sdcard" to install Superuser, but when I select that, the menu just disappears, and I am left looking at the logo, with no further options. I have seen it implied that there should be choices about which zip to install- those never come up.
What am I missing? My google-fu is failing me in trying to find instructions or guides for this particular combination of limitations and progress.
EDIT TO ADD: Ah- found part of my problem... the recovery menu uses the camera button, not the power button. Still somewhat at a loss to see what's next. Installing from the SD card fails. Info in a second post.
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
I am seeing in other places that HBOOT 1.45.0013 can't be rooted. I've been trying for about 9 hours to do this. . .no luck, even with a variety of methods.
bummer.
I'm in the same boat as the both of you. Spent the last two hours and enough tabs in my browser that my music player was skipping when switching between them, and my machine is nothing to be scoffed at!
There just doesn't seem to be enough clear information about how to root this device, and with only 7 pages of development threads, it's gonna be hard to be told to search!
In recovery you use the trackpad to navigate, and select....also, why not just flash a pre rooted stock rom? Follow the directions in this thread, it will work with any rom, not just ICS roms. I used the instructions in this thread to install Bulletproof on my Bf's phone which was an insurance replacement, so it had the same hboot that you guys have, and S-on. It worked flawlessly, I am not sure why so many people are having such a hard time, because it worked the first time perfectly for me.
http://forum.xda-developers.com/showthread.php?t=1508556
Edit: Which recovery are you using?
Woot! Oops...
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
If anyone has a Nandroid backup or copy of the dead-standard out-of-the-box ROM for this phone, please let me know. All I am finding is modified versions. Can't find the base that they were made from, and even the most basic version says it requires S-OFF to install. :headdesk:
Do you specifically need a nandroid backup, or would a flashable ZIP do? Pointers to the latter are available.
Flashable zip would actually be preferable, and pointers would be very much appreciated. I know they have to be out there somewhere, I'm just not finding the right search terms to locate them among all the modified versions.
Look at this post in the developer reference thread: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7
(There's lots of stuff listed there, but look for the 400 MB+ images.)
NOTE: Some ZIP tools get confused by these signed ZIPs, so they might seem corrupt. Check the MD5s to see that you got a good download. 7Zip seems to deal with them OK if you want to look inside.
I have personally flashed the 1.28 and 1.55 ZIPs without incident, but I did check the MD5s.
Well, I was not able to restore the ROMS from the links wjcarpenter linked- everything worked fine, as far as I can tell, but the phone said the "updates" were older than what was originally installed, so the installation was aborted. Not sure how to fix/handle that.
For the moment, I have one of the cleaned-up ROMs that is very similar to stock, but I would really rather it not be obvious that I rooted the phone the second you start it up (the one I found has changed the startup animations), so I will keep looking.
If it's going to be obvious that I changed the ROM, I guess I might as well start looking for the best custom ROM... any suggestions as to which is the most stable?
Firefairy said:
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
Click to expand...
Click to collapse
Just think of it as a big learning experience! The first time I rooted a phone, I messed it up so much I had to keep flashing back to stock and rerooting at least 3 or 4 times. Thankfully I had a phone that was virtually unbrickable. It was a good learning experience though, and I now feel comfortable rooting and flashing on several different devices.
Firefairy said:
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
Click to expand...
Click to collapse
download from androidsu and either save it directly to the ROOT of your sdcard, or copy and paste to the root of your sd card. i always get that same error when i install superuser from a folder in my sd card.
You can get it from here:
Fastboot + Recoveries.7z
I decided because it get's a little tad difficult to find what you might want or need for Recoveries and Fastboot, (I had a B**** of a time myself )
I'd thought it would be nice to offer my assitance, (because I haven't done a d**n thing to contribute since I bought the Q )
So here's a list of nice things I elegantly made for you (Don't ban me mods :angel: :fingers-crossed: )
*What To Do*
For A Little Assistance:
Linux: go to folder and "Right Click" Click on "Terminal/Konsole"
Type "su" (without quotes)
Then copy/paste any of the following (not anything in parentheses)
fastboot flash recovery open_recovery.img (Open Recovery's Mod) (Skrilax_CZ)
or
fastboot flash recovery cwm.img (Clockwork's Mod) (Shabby Penguin)
or
fastboot flash recovery twrp.img (Team Win Recovery Pro) (arrrghhh)
or
fastboot flash recovery recovery.img (Stock Recovery Image) (dunno)
Windows: Go to folder and press "SHIFT and Right Click" run command window (or something close to it)
Then any of the upper ones
Mac: I don't know how to use it, but hey it's here.
Oh yeah thanks to falln Saint, I have my favorite boot logo
It's an android popping it's head out on the Moto with the phone name underneath
fastboot flash logo moto.img
Hope I helped, Have fun :good:
SYKKNYZZ
P.S. I only made it easier to find the files, I didn't create them.
Real credit goes to the members on XDA who work their a** off to help us out. :highfive:
P.P.S. I don't come here often, but if there is any problems, I will answer them as fast as i can.
Why not just link to the thread, where you got the recovery? Including them all in one big .7z file doesn't make a lot of sense - if TWRP or OpenRecovery are updated, that .7z file you have is now outdated...
Just a thought - interesting to see the stock recovery tho!
True
arrrghhh said:
Why not just link to the thread, where you got the recovery? Including them all in one big .7z file doesn't make a lot of sense - if TWRP or OpenRecovery are updated, that .7z file you have is now outdated...
Just a thought - interesting to see the stock recovery tho!
Click to expand...
Click to collapse
Thanks arrrghhh, I just thought to make this simple as possible.
But I do like what is going on with the new roms, I have AOKP because Carbon kept glitching on me and deleting my savedata and setting it under a folder called 0
SykkNyzz said:
Thanks arrrghhh, I just thought to make this simple as possible.
But I do like what is going on with the new roms, I have AOKP because Carbon kept glitching on me and deleting my savedata and setting it under a folder called 0
Click to expand...
Click to collapse
This isn't a glitch, it's a "feature" with 4.2.2.... Unfortunately the more 4.2.2 ROM's you flash, the more this feature will become apparent.
arrrghhh said:
This isn't a glitch, it's a "feature" with 4.2.2.... Unfortunately the more 4.2.2 ROM's you flash, the more this feature will become apparent.
Click to expand...
Click to collapse
Yeah I realized that, but Unicorns are for Gangsters.
And I might go back to carbon, if it didn't delete my info even when I reboot normally after flashing. But thanks for your hard work.
Any way I can be a beta tester for any upcoming products?
I am staying a Q Fan until next upgrade on my contract thru sprint
Sent from my Asanti C using xda app-developers app
I had about 7 "0" folders when I browsing my phone's files looking for a cache'd boot logo...it was like one of those russian dolls with a smaller and smaller doll inside and could not figure out what the heck was going on, lol. Ended up deleting all but the first parent and didn't seem to cause any issues....free'd up a good gig or two of internal storage space! Good to know now what the cause of this was as I was experimenting with a lot of different recoveries around the time this happened. Thanks^^
Argh! I came to this thread hoping for a nice, organized place to find all the links/downloads I needed to fix my girlfriends phone.
Now I have to read, AND continue my search for the files. (mild sarcasm)
Hello,
I thought of myself as a pretty experienced user, but you never learn enough!
However, I flashed some roms (lollipop) that, probably due to my mistakes, screwed up my file system, to the point that my recovery (latest PhilZ) wasn't able to find its backup anymore. Eventually I solved the problem as I was able to find my backups and use them to revert my phone to the rom I wanted to run (Carbon 4.4.4). But I was really annoyed by the fact that my file system was a bit off and still I was having problems with the recovery. So I decided to begin investigating the possibility to restore my phone to factory default. Before going with it, I tried the soft approach, i.e. I used the soft factory reset available from the settings menu. It all seemed fine and I re-flashed a lollipop rom that suited me.
Now the problem is that, after all the ordeal, I decided to make a new backup and so I did. It appears all fine, my recovery can actually "see" it, but I cannot identify it using a root browser! It seems to have disappeared unless I open the recovery and then I see it there. It is located in a folder that I can, of course, access, but,when I do so, I can't find the file!
I tried to put on my phone an old backup (always a PhilZ one), but when I try to put it on the phone I can't find the Backup folder in the Clockworkmod folder!
Anyone has any idea of what is going on and can give me a suggestion on how to overcome the problem?
Thanks
Luca
PS An alternative would be suggesting how to do a restore from a sideload: I thought I saw a similar option, but I can't seem to find it anymore within the recovery's options! I tried also restoring via NRT, but although all seem to go fine and the software return no failure notice, I can't find the backup file that should have been pushed (successfully) on my device!
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
rootSU said:
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
Click to expand...
Click to collapse
Thanks a lot for your help.
How can I find the img. file to flash?
Would it be ok to just go ahead and start from 0 using this:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
How can fastboot flash an image file? I've never done that before! As I said, been doing this for a while, but never done this before...I think!
Luca
Alas, after reading your post on one-click toolkits, I'm afraid I'm one of those who thinks they can do things, but rely on simple tools to do them. However, I never (almost never) forgot to make a nandroid backup before flashing a new rom and, to be honest, I'm not a flashoolic. I never, ever bricked my phone (got a few bootloops). If I find a rom that suits my need, I stick with it for as long as I can.
The changes between KK and L are such that are beyond my comprehension, but I try hard to solve the problems I have without bugging everyone at the first obstacle. But now, after fidgeting with my phone for 2 days, I had to give up. With a few words, you singled out the reason why I couldn't come on top of this: things change and I was not informed of how much they did!
Luca
Problem partially solved..I think! Now I can see the folder and found my backup!!
I used the restorecon command you suggested. I couldn't make it work using terminal emulator (just did not accept the su command: why I don't really know). Then I thought about using adb shell via pc and, I really surprised myself; I was able to pull it through. I'm not totally brain damaged as I felt when I couldn't even reproduce the command you indicated. It is probably the application that doesn't work. It was my first time with adb shell, so a new thing learned.
However, now I would like to ask you: if I place in the proper folder the backup folder I saved on my pc, will I be able to restore the nandroid backup? I just need some data that I forgot (trivial things, such as text messages and a few app data, like passwords and stuff) but it would be useful.
Thanks once more for your help.
Luca