Hi all.
I've just installed some app that broke down my S3 stock OS.
The OS was rooted, and I gave the crappy app superuser access...
It was supposed to change the DPI setting, but now it's boot-looping over the Samsung logo.
Now I'd like to recover my data, photos and stuff...
CWM Recovery 5.5.0.4 is installed.
I can start a backup, but it won't complete since I don't have a large enough SD card at hand (it's a 32 GB SGS3 with a bunch of large videos...).
I don't care about the movies, just the photos, but there's no option for a selective backup...
I also tried updating CWM to a more recent release with Odin (downloaded .img and tar'ed it...), but it won't go further than SetupConnection.
I've not tried a factory reset of anything else yet...
Is there a way I can still recover my data, or should I just get over it and try to flash the whole thing back with Odin?
Thanks for your help.
Adb backup?
maybe reinstalling the ROM can fix it ?
The other thing you can try is adb pull /build prop, edit LCD density back to 320 and adb push it back
Thanks for your answers.
adb looks like the way to go, but I never managed to get it working on my computers.
"adb devices" won't list any, "adb shell" returns "error: device not found".
USB debugging was enabled in the OS.
Is the phone supposed to be in recovery mode or download mode? None works... (Also tried with the OS running before it started crashing)
Is there a setup guide somewhere?
Actually, working with Android on Windows (XP x64) has been a total nightmare so far.
On my main computer, Device Manager loops forever on device detection / driver installation, and successive driver installation/uninstallation/reinstallation mangled WMP10 completely (and since it's tied to Windows, I can't reinstall it).
On other computers, driver installation went fine, I hardly managed to copy movies to the phone through MTP / WMP, and never managed to copy anything back.
I only ever managed to move files over wifi, but that's at wifi speed, not USB2 speed...
And now that I gave Kies a try (stayed away from it so far), it keeps eating 100% CPU whenever I run it.
I had that adb problem then I installed android command centre, and bam, it worked! Will try and find link for you....brb
Finally managed to run adb on the computer with Kies installed.
I'll look into this.
Here go
http://forum.xda-developers.com/showthread.php?p=36671130
Can't use adb pull/push anymore: in a previous attempt to reduce the nandroid backup size, I formated the system and cache partitions.
Then I managed to run a full backup with CWM Recovery, but can't find my files in there.
The backup files only contains application data, but the sdcard folder is totally missing.
Well, it appears the problem indeed was in build.prop.
My backup has 2 files: build.prop.bak and buid.prop.temp.
.bak has the old density, .temp has the new value.
Somehow the app failed to rename build.prop.temp to build.prop, and made the system unbootable.
adb backup won't work either: it's waiting for a confirmation on the phone, and doesn't seem to work in recovery mode.
Now browsing /data/media with adb shell !
I had to mount /data manually (in recovery), I guess the same is true for a recovery backup, and that's why I couldn't find my files.
Think I'll manage to get it all back now.
Thanks a lot slaphead20.
I was just about to wipe away all these family pictures!
Nico57m said:
Now browsing /data/media with adb shell !
I had to mount /data manually (in recovery), I guess the same is true for a recovery backup, and that's why I couldn't find my files.
Think I'll manage to get it all back now.
Thanks a lot slaphead20.
I was just about to wipe away all these family pictures!
Click to expand...
Click to collapse
FYI TWRP will not wipe ur sd when u do factory reset
but ur problem not with data its with system and u can fix it simply by reflashing the u r using without any wipe
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
Hi,
Hope someone can help, about this problem. But I think all it's comes down to now is getting ADB access via Amon_RA recovery rom, as I've tried everything I can do... link to previous post here: http://forum.xda-developers.com/showthread.php?t=642468
I'm running Window 7 Pro x64, previously the ADB was working, but after setting up some ext partition option accidentaly, (I think that it's linked to that), i've tried all options I know of by trying to manually install the drivers and removing them completely etc...
Main points, I can still access recovery image, and also the bootloader. I've succesfully flashed custom roms etc... before. And phone does not boot to rom(that's because I think it didn't install correctly, not sure)
So, i'm sort of lost now, just wondering if any developers here would kindly help or put me out my misery!
re partition your ext(2/3 for Eris base rom) ext4 might not work on Eris.
if you still facing problem remove the swap & only remain the ext partition for A2SD.
edit: and please update to v1.6.2 for the recovery***
Thanks for you response but I can't do anything within the recovery image, some options keep saying please use adb to carry out the process, but I can't get adb to detect on the phone anymore. Also I can't update the latest recovery image, as i'd need adb access....
I can't see why this is happening... perhaps its the SD card that's messed up? I could repartiotion using linux using gparted or something, but I don't know how the Hero set's up the partion.
When I try to recover using nandroid I get messages like unable to mount E:SDCARD etc...
Any clues?
did you do a dalvik wipe? y not try remove the ext partition & try restore previous nandroid?
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
Click to expand...
Click to collapse
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
no adb does not see my device but i can access the internal sd card
Swiftks said:
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
spencerj2001 said:
no adb does not see my device but i can access the internal sd card
Click to expand...
Click to collapse
If you can access the internal card, its weird that adb can't see your device... oh well... try reverting to a earlier/different firmware via a blob. See thread in dev section.
Sent from my CM7 Atrix 4G
i did exactly the same mistake: i uninstalled some system apps (the asus preinstalled apps, with titanium) without unlocking the bootloader, and after a wipe from the stock recovery i'm not able to go beyond setup configuration, it always stops. but i can see and use internal and external memory from my computer. did you find a solution?
alright i have this problem and i am quite panicking now.
i will set everything straight , i hope someone reading the forums can help me asap !
- have a sgs2 unbranded (hk)
- has ICS 4.0.3 stock rom, rooted.
- i don't remember if usb debug mode was enabled
- i messed up in some way with the file /system/build.prop but there is a backup in /system/ called build.prop.bak
- phone doesn't boot anymore as it's stuck at the logo
- recovery and download modes work however
#need a way to delete the build.prop and replace the bloody file with the one backupped. I would like to avoid having to format the phone as i do not remember when was my last kies backup...
what i tried:
-adb shell: it doesn't work. for some stupid reasons the drivers won't be recognized (i have download android sdk and usb drivers), but when i plug the phone in recovery windows just says Device Unknown and even if i update drivers manually it would say that current ones are functioning so no need to update.
if i connect the phone to usb while it's stuck at boot logo, it would recognize the device through samsung drivers (except MTP of course, that would give error).
in both cases adb shell doesn't list any connected device: even if i kill-server and start-server it still doesn't list anything.
-tried using droid explorer in both frozenboot mode and recovery mode, doesn't see anything.
-tried using that other program called SuperOneClick or something like that, that has a "check drivers" button in advanced: if the phone is in recovery pressing the button doesn't do anyhing; if the phone is in frozenboot it asks to download and install some drivers but when i press yes a message appears with " no more data is available " !
i tried this procedure on both win7x64 and winXPx86: same results. reading around , someone says that adb shell will never work if usb debug is de-actived, like i said i cannot remember if that's the case.
-zip package: i created a package to try and overwrite the file with a custom working one i got. i put the package in the root of the micro sd , put the sd in the phone and booted in recovery.
but when i am in recovery the bloody CWM 5.0.2.7 says error to mount /sdcard, or E: could not mount /sdcard , same if i try to mount/unmount /sdcard. if i go to mount external usb card or whatever it says that a file or a lib (cant remember the exact message) was not found.
i have no more ideas of how to solve this, please be patient :<
edit: is there a way to soft format the system folder so that i don't have to properly wipe all my user data and it only affects the system without other contents?
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
bala_gamer said:
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
can you expand on this?
give any suggestion/example?
isn't there a soft temp rom for emergencies like this that you can just start, make modifies to fix and reboot (similar to the process to boot ubuntu on windows, fix issues and then restart normal windows? )
i would so like to make adb work.. but how.!!!
probebly will not work but try backing up of your ROM from CWM working or not..then just back up current one...
you can restore apps & data lateron from nandroid backup with some application like titanium backup donated version.
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
-marco- said:
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
Click to expand...
Click to collapse
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
zaheedahmed said:
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Click to expand...
Click to collapse
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
mljjlm said:
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
Click to expand...
Click to collapse
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
-marco- said:
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
Click to expand...
Click to collapse
you try to reflash once more CF-Root (.TAR)only from odin
then check "E: cant mout...error" is rectified or not.... also check booting or not,
still no hope...you flash the same firmware again and Cf-root, your SD card data will be there for sure as far as our expereicne till now..
first part of your comment: i tried reflashing the kernel; no changes. same errors
second part: shall i try using the same firmware from my previous post then?? not other roms? after that i will put the root and check if internal memory is still there. if it is i will copy it on my hd and restore.
if it is not there anymore..............
so the end of the story.
thanks to anyone who helped.
the resolution was much easier than everything else.
opened odin, pda loaded my same firmware which was the HK stock update to ICS and reflashed.
what it did was apparently and overhaul of the system folder, that's it.
any data was still there, as well as the backup that i did and all my apps etc etc etc.
however especially at first it looked a bit unstable, with processes failing randomly. now it seems it has stabilized a bit, but still when i try to run a Kies backup, the phone kies process dies and the backup gets stopped.
i still don't know how to fix this, but i'll be looking into it.
so, the morale out of this was at least for me: if there is some **** up within the system folder just reflash the same rom installed. i feel so stupid now for having made such a fuss when the solution was so easy and straightforward
NICE that you finaly came across and able to boot , now you make the Titanium back of your all apps and data transfer to PC....forget the system data.
and move to a nice stable ROM
"Unfortunately, wssyncmlnps has stopped"
anybody knows about this?
Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!