Related
I have a nandroid stock backup that I would like to restore to, however system restores but boot image is stuck at "Restoring boot image..." and goes back to the main CWM screen with reboot system now etc.
in dire need of assistance, can't get out of CWM recovery and when trying to adb the Prime now has an error exclamation mark on it. I have CWM 5.8.1.8
radici said:
I have a nandroid stock backup that I would like to restore to, however system restores but boot image is stuck at "Restoring boot image..." and goes back to the main CWM screen with reboot system now etc.
in dire need of assistance, can't get out of CWM recovery and when trying to adb the Prime now has an error exclamation mark on it. I have CWM 5.8.1.8
Click to expand...
Click to collapse
Did you make the backup in 5.8.1.8 or did you make it back in the old 5.5.0.4 version? If you made it back then, then you will not be able to restore boot as that version did not back it up in the first place.
If however you made the backup with your current version of CWM, then I am at a bit of a loss. I have had no issue whatsoever restoring any and/or all of my backups.
When you say that when trying to use ADB the Prime now has an error exclamation mark, please elaborate as to where you are seeing this exclamation mark. Is it in the terminal/command prompt?
I made the backup in the old 5.5.0.4 version. I'm using naked drivers which fixed the exclamation mark in pc's device manager however still can't push anything to Prime as adb reports "device not found"
fixed
radici said:
I made the backup in the old 5.5.0.4 version. I'm using naked drivers which fixed the exclamation mark in pc's device manager however still can't push anything to Prime as adb reports "device not found"
Click to expand...
Click to collapse
You're screwed. You have no backup.
goodintentions said:
You're screwed. You have no backup.
Click to expand...
Click to collapse
He said in the post above yours that it was fixed. He should probably add that to the Thread title and also detail how he fixed it for other folks who find themselves in a similar situation.
Please I need help with similar situation. I'm using cw 5.5.0.4 n tried installing a Rom but doesn't go past ee pad screen. I don't see my back up. How do i use the USB while in recovery?
Sent from my ADR6400L using xda premium
inspeckta_dek said:
Please I need help with similar situation. I'm using cw 5.5.0.4 n tried installing a Rom but doesn't go past ee pad screen. I don't see my back up. How do i use the USB while in recovery?
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://forum.xda-developers.com/showthread.php?t=1427008 and then come back here.
If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.
Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://forum.xda-developers.com/showthread.php?t=1576937
If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. We're almost done.
Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.
After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.
I wish you luck my friend.
Doktaphex said:
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://forum.xda-developers.com/showthread.php?t=1427008 and then come back here.
If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.
Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://forum.xda-developers.com/showthread.php?t=1576937
If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. We're almost done.
Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.
After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.
I wish you luck my friend.
Click to expand...
Click to collapse
I have a win 7 pc... When I connect the prime in device manager it comes up as all android on emulator..with yellow exclamation.
Sent from my ADR6400L using xda premium
Sent from my ADR6400L using xda premium
inspeckta_dek said:
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Have you tried the naked drivers from here http://forum.xda-developers.com/showthread.php?t=1426502
I would follow that guide, and then see if you can get it working.
Nope will check it when I get home. Is it suppose to see it in recovery? Will def try it
Sent from my ADR6400L using xda premium
Doktaphex said:
OK, we need to do a couple of things here. Number one can your computer see your device with ADB? If you are unfamiliar with using ADB read this thread http://forum.xda-developers.com/showthread.php?t=1427008 and then come back here.
If your comp can see your device, we can push a new ROM to your sdcard by making sure you have the ROM in your ADB directory on the computer, and then in a terminal/command prompt you will need to type "adb push *ROM.ZIP* /sdcard" replacing *ROM.ZIP* with the actual name of the ROM (also omit the *s) This will take a while but have patience and eventually you will have a message telling you that it completed successfully.
Now we need to get you a new CWM image onto your Prime. There are 2 methods you could use both detailed in my thread here http://forum.xda-developers.com/showthread.php?t=1576937
If you've followed all of this so far, then give yourself a pat on the back, you are no longer the noob that you were when you set out on this quest. We're almost done.
Reboot into CWM the usual way and wipe all partitions. Flash your ROM and it should flash everything including boot.
After verifying that you can get into a working OS, reboot into recovery and make a new backup immediately.
I wish you luck my friend.
Click to expand...
Click to collapse
ok i tried the new driver zip and it installed. its says asus android device and then samsung galaxy nxus.. does that mean its connected?
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Hi, have you installed adb succesfully in your pc previously?
If yes then the next thing you need is fastboot.exe file, if not then start with that first then fastboot.
You can find what you need here, also if you search in my threads (link in my signature) you can find a tutorial about how to install and use ADB.
~ Veronica
Acclaim
I have the same challenge. I have ADB working successfully (and have used Veronica's guide to repartition my NT - thanks again). Yet when I use Cyanoboot and start Fastboot my device shows up in Other Devices as Acclaim and none of the USB drivers I have pointed to get installed. It isn't mission critical that I solve this but it would be nice from a knowledge base to understand what I am missing in case I ever need to use Fastboot. It seems to be a much easier tool to change the installed Recovery image than ADB. Any help would be appreciated.
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
ShinnAsuka said:
adb works for me. i currently have cyanoboot, when i try to go to start fastboot to install a new recovery, i notice in my device manager there is an uninstalled driver called "Acclaim". Already tried the NT drivers for it and it didn't work. Any ideas? I recently flashed succulent's cm7 image which had a cwm v5.0.x and i want to flash cwm v 5.5.x. Already tried using indirect's NT recovery flasher and no go on that...
Click to expand...
Click to collapse
+1
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
bingoz said:
Can someone upload fastboot mode driver for NT for me? I turn my NT into bootloader but my PC can't "see" NT so I can't fastboot recovery.img.
Thanks.
Sorry for my bad English.
Click to expand...
Click to collapse
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
when doing fastboot do you see "acclaim" under other devices in device manager? I had to install another set of drivers in order for fastboot to work.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
bingoz said:
My PC search for driver but I can't install. Would you please send me link to "set of drivers in order for fastboot to work"? Thank you very much
Click to expand...
Click to collapse
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
you need to find the id of the nook under other devices acclaim. then you modify the android_winusb.inf file with those new id's and install the drivers
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Can you explain more or upload the file already edit for me? Thank you
bingoz said:
Can you explain more or upload the file already edit for me? Thank you
Click to expand...
Click to collapse
each product id is different so uploading the file isn't going to do you much good. sorey
Sent from my Nook Tablet CM7 BETA using xda premium app
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
I don't have windows so I won't comment on that. There is one thing that I never see mentioned when talking of adb access problems.
On custom roms (your case cm9 0.05.1) in settings, developer options, Android debugging should be checked to allow adb access. If not checked that may be your issue.
If I'm having adb issues and it was working previously I'll boot to cwm (5.5.0.4 version not 5.0.2 or whatever) and go from there.
You should get adb working properly, but to flash recovery you can use one of the flashable zip files while in cwm. They work for me!
Got a few minutes on a windows 7 pc (people should take their breaks at their desk). If you are using Veronicas thread http://forum.xda-developers.com/showpost.php?p=22049356&postcount=1 you will find a file runmefirst.bat if you run it and follow instructions about unplugging and replugging nook it will create and setup the previously mentioned file. Do not run zergy as suggested. When it pulls device manager your exclamation should say nook. Right click it, update driver software, browse my computer, let me pick, and then choose the directory with your usbdrivers, tell it yes to use them. Do not worry about anything else from runmefirst.bat including anything else to run. You just want it to set the codes for your nt and then it is of on use.
I had adb working for my nt quickly on that windows 7 pc. It had no previous adb or usb drivers installed.
Good Luck
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
nba1341 said:
I got nook tablet drivers installed and it works for adb however fastboot still has acclaim!
anyone have steps how to fix this?
fastboot has no devices
Click to expand...
Click to collapse
like i said in a previous post, right click the acclaim item under other devices and look for the product id and edit the android_winusb.inf accordingly.
after that right click acclaim, update driver software, and browse for the drivers yourself. if all goes well fastboot should work. this is how i did it. not that i ever really use fastboot but its good to have just in case.
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
mamifsidtect said:
I have looked but I cannot find anything on how to get fastboot for Nook Tablet working (and yes I do have CM9 0.05.1) and I want to flash recovery but it is not recognizing my Nook. All it has on device manager is Other Devices/ Acclaim with an exclamation point. Please help
Click to expand...
Click to collapse
Check your android_winusb.inf to see if you have the right entry for the NT -- see http://forum.xda-developers.com/showpost.php?p=35971559&postcount=13.
---------- Post added at 12:19 AM ---------- Previous post was at 12:15 AM ----------
Penguin101 said:
Is there any step-by-step tutorial on how to flash NT with fastboot? I have tried to search, but still could not get it work.
Thanks.
Click to expand...
Click to collapse
Why not flash your NT using SD-based CWM Recovery (e.g., see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31)?
The easiest way under windows, is just choose the driver on your own, use the driver from the Android SDK (sdk\extras\google), and you will be presented with a couple of options, choose Android Composite ADB Interface.
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app
Hello.
I have a problem with friend's phone.
It's HTC Desire Z (Vision). I S-OFFed how it's described on CM wiki. Latest radio.
About month ago I installed CM 10.1 AlterNdromadus.
It worked until yesterday, when it unfortunately installed some system update.
After that phone didn't booted anymore. In recovery it says, that it can't access system partition and formatting is not possible.
I tried connect the phone via fastboot in bootloader, but it also doesn't work. Under windows I have it as unknown device and when I tried manually install drivers from google, it says that they are not compatible with the HW (under ROM it worked before).
I tried also install stock RUU rom (extracted the zip and deleted H-BOOT, radio and recovery) from SD-card (PC10IMG.zip). But it also got frozen on system update.
Here you can see error from 4EXT recovery and CRC images from bootloader.
Any suggestions? :crying:
Thanks
Well, I guess I meant to keep this thread in the desire z q&a thread but this works
I wish we could know what kind of system update was flashed as it may be easier to fix this
There shouldn't have been any system update as there is no ota associated with that ROM, but we can try anyway
http://forum.xda-developers.com/showthread.php?t=2348266
Here you will find links to get you proper drivers, being your on windows try using a free program called USBDeviw, I have had to use this a lot to erase drivers and then manually install the proper ones (windows is terrible at this)
Or if you can dual boot Linux you may find life easier as once you get fastboot working you should be able to quick fix this.
Otherwise try out the aio wipe tool and or superwipe script that is linked in the guide I sent you
But really, try to get the drivers working and we should be good
Sent from my Nexus 4 using XDA Premium 4 mobile app
Tried both superwipes. Doesn't work :/
The problem with fastboot is, that windows totally doesn't recognize the device. So I'm not able to install any drivers (see attachment).
The reason why I posted it in this section is, that I found people with similar problem on other phones. But noting work to get it back...
Any recommendation for the linux?
I booted successfully SystemRescueCD. After a half hour I also went ADB but no devices were found...
The screenshot is blurry when looking at it from my phone but it looks like windows 8/8.1 which many have issues getting adb/fastboot to work right. Usually the fix involves using usb3.0 ports
Can you just dual boot a Linux distro? Ubuntu is a very simple one to work with and you will easily find guides how to get fastboot working on it, actually if you see the thread I linked you there is one on fastboot that walks you through the process
If you don't want to dual boot a live CD is fine, but you still need to get the adb/fastboot binaries installed and working from that disc
Sent from my Nexus 4 using XDA Premium 4 mobile app
Yes, it's windows 8.1. I don't have USB3.0.
I have here also one really old desktop with windows 7, I will give it a try.
Otherwise last chance is the Ubuntu (I don't want to dualboot, so I will made live USB).
I downloaded from XDA two files - ADB and fastboot for Linux.
Downloading and installing adb from SDK from google doesn't look so easy as on windows...
Also should I use drivers from HTC sync or from google SDK?
Because through ROM it worked right with the google's drivers...
although this is not what you may want as an answer but why don't you copy a ROM to SD card n flash via recovery,, it'll regenerate system,, once it is regenerated,, you can connect to your PC and carry on to what you want.
Nope. It doesn't work. I tried it as first option.
I just forgot to write it here....
seems like you might have actual physical damage/bad sector on ur device.
this is what happens in hard drives, they can't be formatted, no read/write etc.
i don't know if there's any app that can help fix you this coz you can't connect to system/OS in first place to do so,
Best option seems like to dust off the warranty papers n get it to service center for repairs as it might need physical parts replacement.
I got working fastboot (not ADB) on Windows7.
When I tried fastboot format /system I got error "Uknown command".
When I tried fastboot erase /system I got error "No partition found"
Yes, it's probably problem with bad blocks...
The issue at hand depends on what this 'update' was as the ROM that was running on the phone at the time would not have had one which means something was flashed to it that shouldn't have been.
Being the phone had security flags removed (soff) a number of things that shouldn't be allowed to flash can be, so depending on what it was will determine how fixable it is
At this point the only way to fix it or at least dertimine if it is fixable is to get phone and PC to connect via fastboot and adb
So use the windows 7 or Linux, set it up with drivers found in xda wiki or write the android rules for Linux and work on this, its doubtful you can move forward until this is done
Sent from my Nexus 4 using XDA Premium 4 mobile app
As I wrote, I got Fastboot worked.
BTW isn't possible to acces ADB only from the ROM?
I tried to get it work without success. I tried HTC and google drivers...
Must have posted while I was posting and I missed that
Fastboot only works from bootloader and adb only works in os and recovery
The commands you were using isn't correct, I suggest you read again the two fastboot links from the link I sent you for clear instructions.
For right now I would grab the latest cwm, twrp or 4ext recovery (4ext still best for this phone)
Then
fastboot erase system -
fastboot erase recovery
fastboot erase boot
Then
fastboot flash recovery nameofrecovery.img
Then if all goes well grab a known stable ROM and flash it (along with gapps if needed) from new recovery
If things don't work as planned be sure to copy and paste all input/output from cmd
Sent from my Nexus 4 using XDA Premium 4 mobile app
Q&A for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STOCK][JB 4.2.2] ASUS MeMO Pad 8 (ME180A-WW-3.1.0.42). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
hhzznn said:
My asus memo pad 8 not booting and not reach to check usb debuging...
When conecct usb fastboot mode device not found in win 8.1
Help me please
Sorry my bad english
Click to expand...
Click to collapse
Hello there,
If not using the "adbsetup" drivers or the ones off the ASUS website (sorry, couldn't find the ASUS drivers when I looked ), use one of the above. If using one and still not connecting, try the other option.
Also, check your USB ports to make sure you are not connecting via a USB 3.x standard. Android (or at least some Android devices) don't like those.
If all else fails, you may need a Linux build
Hope this provides a head start.
Sent from my LG-D520 using XDA Free mobile app
help me please
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
hhzznn said:
hello
my asus memo pad 8 not booting becuse im delete odex file in system/app after rooting..now device not booting any way!wipe data and wipe cash dont answer and not booting yet!!
in fast boot mode unlock oem not answering...
please help me ...
email :[email protected]
Click to expand...
Click to collapse
Looks you got a little further... :good:
From what I remember when I followed the guide, there was no feedback (nothing on the screen, and tablet remains black) on when you issue the unlock commands - which by the way, are:
Code:
fastboot oem unlock61646
fastboot oem unlockD696E
Then, reboot the bootloader and install CWM (first line may be substituted with rebooting into fastboot by hand):
Code:
fastboot reboot-bootloader
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
You shouldn't get a write-protect error this time around. Hope this helps.
By the way, your SKU is WW version, right? If not, my ROM may not help you (without going the long way around of instead of flashing the ROM, copying the odex files back into /system/app using CWM's ADB push command). Just a warning. If you are not WW, and insist on flashing anyway, I would highly recommend a nandroid backup (and probably copied) to MicroSD to protect your original (broken) ROM.
help me
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
hhzznn said:
my pad is sku = ww
in the fastboot mode i type fastboot oem unlock61646 and i get asnwer okey and finish but when type fastboot oem unlockD696E i get answer oem admunlock not request
help me please
Click to expand...
Click to collapse
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
The latter may have been for the 10" model - cannot remember. Try rebooting into fastboot now and see if CWM install takes.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
the code:fastboot unlock oem61646 worked but fastboot oemD696E not working
in stock recovery i cant install rom.zip
and in fastboot when install recovery cwm answer bootloader lock
any offer for me?
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
**you may need a Linux build **
i have a linux base ,, may you help me??
hhzznn said:
**you may need a Linux build **
i have a linux base ,, may you help me??
Click to expand...
Click to collapse
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
joel.maxuel said:
May not be as important now (if you got fastboot working in windows), but what distro do you have? I am familiar with Debian, Ubuntu, and their derivates.
Sent from my LG-D520 using XDA Free mobile app
Click to expand...
Click to collapse
i have ubuntu....what should i do?
hhzznn said:
i have ubuntu....what should i do?
Click to expand...
Click to collapse
In a terminal...
apt-get install android-tools-fastboot
...would be a good start. You may need to register the device vendor in your configuration, which I can research later if...
fastboot devices
...lists nothing. Hope this helps.
Sent from my LG-D520 using XDA Free mobile app
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Syncline said:
Hi...I was having issues with my ME180A (WW variant) where the OTA update would never take (I had the tablet rooted) so when I finally found this thread and the associated stock ROM install instructions I thought I would give it a go to see if I could clean up the mess that I must have made rooting and de-bloating my tablet. I got adb and fastboot install on my win 8.1 machine with no problems, got CWM (from your link) installed on my tablet with no issues but when I tried to flash your original rom onto my tablet it would get partially through the install and then I would get
set_metadata_recursive; some changes failed
error in /data/media/0/K00L_Back_To_Stock_Untouched_Orig.zip
status 7
and the install would fail. I think this has somehow screwed up my bootloader because now my tablet constantly reboots into CWM no matter what I do. When the tablet is connected to my Windows machine, the drivers don't get loaded so ADB and fastboot just sit at "waiting for device" after I try some of the different commands. I'm familiar with flashing ROMs onto my phones and have never had an issue but I have had a lot of difficulties with this tablet. Do you have any advice to solve the bootloader and ROM flashing issues?
Thanks in advance for any assistance that can be provided.
Click to expand...
Click to collapse
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
joel.maxuel said:
Hmmmm, I guess this is why I made two files, but the other may have similar problems because of this issue.
I will see if I can change the updater program. In the meantime, pop the other back-to-stock file onto MicroSD, reload CWM, and try that one. Report back to me in any case.
UPDATE:
If the above fails, try this one as well.
Click to expand...
Click to collapse
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Syncline said:
Joel,
I tried to flash the other back-to-stock file as you recommended however the end result was the same.
set_metadata_recursive: some changes failed
E:Error in /external_sd/K00L_Back_To_Stock_Re-Perm-Linked.zip
(Status 7)
Installation aborted.
Are there any other things that you can think of that I can try to get this issue fixed? And thanks for all your assistance, it is appreciated.
Click to expand...
Click to collapse
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
joel.maxuel said:
So the third file I created (in my post update) replaces the updater-binary that would be causing issues with that particular CWM.
Third times the charm... :fingers-crossed:
Click to expand...
Click to collapse
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Syncline said:
Things worked great that time with the flash working and the tablet rebooting properly however now it is asking for a password to decrypt storage and this is the first time I've ever seen this. Any thoughts?
Click to expand...
Click to collapse
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
joel.maxuel said:
Were you encrypted before?
Could do is a nandroid of the data partition and then factory reset. You will have to set your apps up by hand again, but it is better than that message.
Sent from my MeMO Pad 8"
Click to expand...
Click to collapse
No I wasn't encrypted before but from what I read it seems to involve a failure to mount the DATA partition correctly, and the Android OS erroneously assumes it's encrypted. I'm not overly concerned about setting up apps by hand, I do have a titanium backup of my apps and data. As I'm still at work, I can't do too much playing around on my tablet. I don't have access to my personal computer that has all my tools like adb, fastboot, etc. until the work day is done. I've said it a couple of times, but I truly appreciate the assistance that you've provided.
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Syncline said:
UPDATE: After booting back into CWM, doing a factory reset and a format of the /data partition seems to have done the trick. I'm back into my tablet and currently updating all the pre-installed apps that require it. One more quick question Joel, you mention that the ROM is rooted and I do have SuperSU installed, however when I run the app it tells me there is no SU binary installed and SuperSU cannot install it, can I just install the latest version of a flashable SuperSU zip with CWM to fix this?
Click to expand...
Click to collapse
That's an interesting side effect...never had that happen before.
You can try it, and let me know. Hopefully your CWM is still kicking around, or else you will have to reinstall via fastboot. Or alternatively, just re-root normally (like with Kingo).
By the way, before you do that, does /system/xbin/su exist? Or what you could answer, is you could download Voodoo OTA RootKeeper and report back which values are not checked off. I think SuperSU update.zip places the su binary, nothing else. But we shall see.
Sorry Joel, I didn't see your reply before I flashed the SuperSU zip but it did work, my tablet is rooted again.