Hi all,
Well, this is my point*: I have got a rooted and unlocked TF201 running Asus FW build US_epad-9.4.2.28. I'd like to switch to CyanogenMod and I therefore installed ClocworkMod 5.8.3.4 using ADB.
I have got an issue trying to wipe data and perform the factory reset 'cause CWM can not mount /data. I tried mounting by hand, using both advanced CWM tools and ADB command lines but without any success so far.
I guess it is because my personal data are encrypted (I did it using the Asus inbuilt tool). And /data folder is not available (=decrypted and mounted by the system) before I input my secret pass. Am I right ?
I also tried to install Cyano using Rom Manager, ROM toolbox or others GUI without any success (same thing happens : personal data are not wiped out) and install failed.
I looked for solutions on XDA forums and googled for quite a long time now without finding a solution (but I may have miss looking). Any help would be welcome.
Try using newest TWRP, maybe it could help - there are many problems with CWM on Prime. Don't forget to install version for ICS bootloader(as you are runnign ICS rom)
Sent from my Transformer Prime TF201 using Tapatalk HD
qery said:
Try using newest TWRP, maybe it could help - there are many problems with CWM on Prime. Don't forget to install version for ICS bootloader(as you are runnign ICS rom)
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
That is correct. I just did this last night. TWRP will let you wipe encrypted data.
Thanks for the tip. I'll have a try and let you know results
Well, it's a bit more complicated than expected...
Running CWM v 5.8.3.4, I'm able to start on recovery mode (hopefuly...) but there is absolutely no way to get a correct fastboot connection!!!
I end up with a "connection refused" message (My ADB settings are corrects as I am abble to "play" with my TF201, once up and runing). I am therefore unable to install NVFlash, TWRP or any other tool :-/
I guess my only chance left is to follow the below instructions from TWRP website:
Download - ADB / Terminal method (not recommended):
Download the corresponding .blob file above. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob.Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
But I'll have to change the code above (as my /sdcard is crypted...) for something like :
Code:
su dd if=/twrp/twrp.blob of=/dev/block/mmcblk0p4
with /twrp a brand new (and readable by all users) folder containing the Blob file.
This is my only clue so far... Any other idea? I may just brick my Prime running a wrong command or tool
This start to be a pain in the ...
I can't even create a folder or copy files on the root folder (using ADBr Rom ToolBo Pro). They are automaticaly removed once I shutdown/restart the device or permission is recused ("read-only filesystem")
Wondering if I'll find a way :crying:
singinglarvae said:
Well, it's a bit more complicated than expected...
Running CWM v 5.8.3.4, I'm able to start on recovery mode (hopefuly...) but there is absolutely no way to get a correct fastboot connection!!!
I end up with a "connection refused" message (My ADB settings are corrects as I am abble to "play" with my TF201, once up and runing). I am therefore unable to install NVFlash, TWRP or any other tool :-/
I guess my only chance left is to follow the below instructions from TWRP website:
But I'll have to change the code above (as my /sdcard is crypted...) for something like :
Code:
su dd if=/twrp/twrp.blob of=/dev/block/mmcblk0p4
with /twrp a brand new (and readable by all users) folder containing the Blob file.
This is my only clue so far... Any other idea? I may just brick my Prime running a wrong command or tool
Click to expand...
Click to collapse
You are not able to access /sdcard from Terminal Emulator (not adb) while you are normally booted?
Sent from my Transformer Prime TF201 using Tapatalk 2
qery said:
You are not able to access /sdcard from Terminal Emulator (not adb) while you are normally booted?
Click to expand...
Click to collapse
I am abble to. But I won't be abble to read this folder once on recovery mod (as Clockwork Mod can't open this crypted folder)
singinglarvae said:
I am abble to. But I won't be abble to read this folder once on recovery mod (as Clockwork Mod can't open this crypted folder)
Click to expand...
Click to collapse
That's fine. I think you should run the dd command while normally booted, it copies the twrp.img into recoveryand it should work. Hopefully.
Sent from my Transformer Prime TF201 using Tapatalk 2
Thanks, the above code did the job after copying TWRP on my SDCard!
Code:
su dd if=/twrp/twrp.blob of=/dev/block/mmcblk0p4
So far, my TF201 is now running CM 9 and everything is now rolling!
@qery, thanks a lot for the help!
Now it's time to do NVFlash
Sent from my Transformer Prime TF201 using Tapatalk 2
Related
I'm trying to run the "unofficial alpha 3" rom again but think that I need to do the following but can't figure out how. I have the Thunderg recovery rom and from reading the text below I think it means to boot into the recovery console, mount the /system partition and format it but I don't see how to get to a shell prompt from there,
Sometimes Recovery can't format /system so you must remove all files before flashing zip (bug still here):
1. Mount /system in recovery.
2. adb shell rm -rf /system/*
You get 1 error. This is ok.
Will update if I found this bug.
Can someone help ?
Cheers
Keith
You have to use ADB. Read here on how to get ADB installed and working: http://forum.xda-developers.com/showpost.php?p=10372531&postcount=3
Can I do that using ONLY my mobile phone? for example using a terminal emulator? If so, how?
Thank you
On void I installed cm 7 a2 just with the simple procedure of flashing in recovery. Then updated to cm7 a3 easily. Then I went back to void to check the audio quality. Found the quality same and also realized equalizer app didn't install on void. So tried to flash back cm7a3. But bootloop occurred. Fortunately I had a nand backup of cm7a2. So restored it and updated to a3 flawlessly.
So two learnings:
1. Sometimes direct install of cm fails. Sometimes it works.
2. Nand backup is a very good thing.
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?
Hello guys.
I know there's no way to make CWM work with encrypted memory and SD and also there's no way to decrypt.
So, any other encryption solution that allows backups?
Using android's encryption feature, what to do in case of problems?
Any way to recover?
What happens if the system bricks and a recovery is needed?
What happens flashing a non disruptive update? Is a wipe needed?
Thank you so much!
Flashing to an encrypted ICS gs2/i9100
ultradj83 said:
Hello guys.
I know there's no way to make CWM work with encrypted memory and SD and also there's no way to decrypt.
So, any other encryption solution that allows backups?
Using android's encryption feature, what to do in case of problems?
Any way to recover?
What happens if the system bricks and a recovery is needed?
What happens flashing a non disruptive update? Is a wipe needed?
Thank you so much!
Click to expand...
Click to collapse
There are two options I've found that will work for flashing encrypted ICS, one is TWRP, which you would use instead of CWM, which would allow you to enter your password & flash what ever ROM you wanted like you were working with an unencrypted phone. But it's not (yet?) available for gs2/i9100.
The other option (original post here ) outlines how to do this from the command line of a computer with the Android SDK installed. I've spelled it out to include Android SDK installation since I didn't have that installed already when I had to do this.
Download, Install & configure Android SDK
Run SDK Manager
install "Android SDK Platform-tools"
Add <whatever>/android-sdk/platform-tools/ to path
in a command prompt / terminal window type "abd" to Check that your path includes the correct folders in the SDK (I had to do this manually on Win7)
On Phone
Reboot phone into Recovery mode
in CWM format cache partition
from your PC use adb to mount /sdcard as tmpfs:
Code:
adb shell mount -t tmpfs none /sdcard
put your ROM on the (fake) sdcard
Code:
adb push <your rom> /sdcard
Use the recovery to flesh the ROM as usual
Once you reboot the device will ask for you password as normal then finish the app installation/configuration after reboot. I was able to do this upgrading from CM9.0.0 RC1 to CM9.1. All data was preserved. Phone seems to be behaving itself but I only did this an hour ago so still too soon to tell.
Props to orcruin for sharing this. :highfive:
Ed
Hello everyone. Let's see if anybody can help me, because I'm pretty stuck with this.
Note: I've already searched high and low for solutions to the "Signature verification failed", but they either don't work or don't apply here.
I've tried to install the following ROM from xda-developers in a Sanei N10:
Unofficial CyanogenMod 10 for many AllWinner A10 tablets
I've installed it following the usual procedure:
- Press Vol+ and Power to get the Recovery menu
- Select Wipe data/factory reset
- Select Wipe cache
- Install the three ZIP files: "cm10_a10_20120913.zip", "gapps-jb-20120726-signed.zip" & "n10_compatibility_1.2.1.zip"
The problem is, even though the first ZIP with the ROM installs successfully, the second one (the one with Google's apps) refuses to install, showing instead the message "signature verification failed". The same happens with the third ZIP (N10 compatibility).
So the installation doesn't actually finish. If I reboot the tablet, it runs Cyanogenmod 10, but the touchscreen doesn't work (I have to plug a USB mouse to interact with the operating system).
So what do I do to avoid the dreaded "signature verification failed" message? Just in case if it's of any help to identify the problem, I'll mention that I can see the Android bot laying down with a red triangle with an exclamation when entering the Recovery menu.
I've tried to use the ROM Manager which is preinstalled with Cyanogenmod 10, but when choosing "Flash ClockworkMod Recovery" it says that "The SD Card needs to be mounted to use ROM Manager". Of course my MicroSD is properly mounted (I can see its files in the card from console, from the "Terminal Emulator"). I think this happens because the MicroSD is mounted in /storage/sdcard1 instead of in /storage/sdcard0, but I can't change that. I can't download APKs from the browser, either, because it also says something similar about not being able to access the SD (even though it's correctly mounted and can see it mounted from Settings > Storage).
I've also tried the CyanogenMod A10 ROM available in this page, which is more recent (October instead of September):
http://www.slatedroid.com/topic/3870...mod-10-tweaks/
But the same happens.
I've even tried installing the CWM Recovery ROM, but it doesn't let me installing that from the Recovery either (same message about the "signature"), and with Odin3 it doesn't work either because I don't know how to reach the "download mode", which is needed for Odin3. Pressing Vol+ and Power I get the Recovery, but not the Download mode. Does anyone know how do I get to the download mode in the Sanei N10?
Any idea about how to solve this? Right now I have a tablet with no touchscreen and not even Google applications (so I don't even have the Play Store), so it's practically worthless (at least the WiFi works). How can I get this tablet back to being usable?
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
benny6812 said:
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
Click to expand...
Click to collapse
No, unfortunately I still couldn't fix it
There's nobody here in xda-developers who can help me? Surely somebody must know enough to help me find a solution.
I've tried creating a symbolic link from /storage/sdcard1 to /storage/sdcard (it doesn't exist right now), but it just says "link failed Read-only file system" (I was root, by typing "su" and clicking "Allow" in the Superuser window). So, I can't create symbolic links even while being root user? I need this link so ROM Manager can detect my SD Card (it says it's not mounted but it really is, but in "/storage/sdcard1").
Also, the gapps package linked in the ROM page above seems not to be properly signed, even though it has that "-signed" suffix in its name. I always get that "signature verification failed" error message. But now I've tried downloading a more recent gapps package (gapps-jb-20121011-signed.zip) and that package finally worked! BUT, even though it apparently installed successfully, I still can't see any Play Store icon, nor any other Google app (Gmail, etc.). Why? Those icons should appear after installing gapps, shouldn't they? Maybe this newer "gapps" package is somehow incompatible with this tablet? (is this even possible?).
Also, even though I can now install the newer "gapps" package, I still can't install the "n10_compatibility_1.2.1.zip" file (I still get "signature verification failed" for that ZIP), which, I guess, contains the drivers needed for the N10 so the touchscreen works (currently it doesn't, and I have to use a USB mouse to use Android in this tablet). Any ideas? I'm getting tired of trying 9485738489754935627 things with no good result . I guess Android is showing here its Linux roots...
I think the key here is managing to install a new Recovery ROM that doesn't care about signing, but how do I do that? I can't install through ROM Manager because I get that error about the SDCard needing to be mounted to use it (and it's really mounted), and then I can't create the /storage/sdcard symbolic link because I get that "link failed Read-only file system" error. Also, I can't use Odin3 because I can't manage to put this tablet in Download Mode. Aaaargh! There's no good solution
Any ideas?
Bump!
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Yojimbojpr said:
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Click to expand...
Click to collapse
Thanks for replying. If we could find some way to install a new Recovery, then we'd probably by able to get the N10 Compatibility file working. This can't be that hard to do, but I've tried lots of things, and none of them worked...
Anyone?
Please, someone help!
Bump!
No ideas?
Please, I'm getting desperate
sanei
OMA2k said:
No ideas?
Click to expand...
Click to collapse
same problem here....
jamjamjan said:
same problem here....
Click to expand...
Click to collapse
Please let me know if you find a solution to this. Thanks!
I'm having the same issue with [ROM][CM10/10.1][21 Dec] Codename Lungo
Well, at last I could finally solve the problem thanks to chris5s from this forum.
These are the steps that worked for me:
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/showthread.php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I hope this helps somebody else!
hey i just registered because i have been having the same exact problem i read that you fixed it but how can i get in to the tablet if im not able to do any movements after it boots ???
please any help would be appreciated
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i did i just dont know how to get in to the terminal app
ok so im in the terminal app but what do you mean by modify the install sh file ???
Hello "lesanei"
I just noticed your posts. Let's see if I can help you...
The touchscreen doesn't work because the appropriate drivers were not installed (because of the "signature verification failed" issue). So you need to connect a USB mouse (and preferably a keyboard too) to the tablet. The Sanei N10 should come with a USB to micro-USB adapter. If you don't have it, you can buy it for cheap here.
Since there is only the one USB input in the tablet, you can't connect two USB devices at the same time. What I did use is a wireless mouse+keyboard combo which only needed one USB dongle for reception. If you don't have that, you can just connect a USB mouse and type with the on-screen-keyboard using the mouse. It's annoying, but it works
When I say "modify the install-recovery.sh file", I mean the file inside "cwm_recovery_6.0.1.2_a10.zip". You can modify it from your PC if you prefer. You don't have to do it in the tablet if you don't know how to use the "vi" editor (command line editor). Just open the "install-recovery.sh" file in Wordpad (do not use the Notepad, because it doesn't support Unix line endings so it shows the file incorrectly) and replace all instances of "/sdcard" with "/mnt/extsd". So the file contents should look like this:
#!/system/bin/sh
if busybox test ! -f /mnt/extsd/recovery.img; then
echo no /mnt/extsd/recovery.img
exit 1
fi
cat /mnt/extsd/recovery.img > /dev/block/nandg
sync; sync; sync
echo done
Click to expand...
Click to collapse
Then place all three files ("recovery.img", "install-recovery.sh" and "reboot-recovery.sh") into your MicroSD card. Then safely extract it from your PC, insert it in the tablet and type this from the Terminal:
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
Click to expand...
Click to collapse
Then follow the regular steps to install Cyanogenmod and this time all files should install sucessfully, so when rebooting, touchscreen and everything else will work.
Let me know if it works for you.
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
jamesh1979 said:
Hello all. hdx 7 was running the original version of safestrap and gapps on the very first firmware. accidently wiped internal and now can only boot to safestrap no abd so bricked or not and by the way i already read like damm near all the threrads i could find so dont accuse me of being a lazy no good non reasearching az mf thanx
Click to expand...
Click to collapse
Ok, if I understand you correctly, you wiped internal storage of your sdcard, so no backups to restore for safestrap.
But when wiping happened, you were on activated extra rom slot? So now safestrap cant boot there, because with internal storage you deleted image files for rom slots...
If you can boot into safestrap, can you switch to stock rom? And boot into it? If yes, and Fireos start normally, then nothing is lost, reinstall safestrap, you should have adb access, and do whatever you want to do next...
Did you disabled OTA updates on stock rom? If not, turn off wifi as fast as you can, when you boot into Fireos, so it cant update to nonrootable FW.
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
jamesh1979 said:
thats whats wierd i was on rom slot one but it wiped even my stock img as far as i can tell because it wont let me switch to it , and yes disabled ota with toolkit like a year ago and all was fine?
Click to expand...
Click to collapse
Well, I installed safestrap on my working kindle, so I can check what else was deleted in the wiping, unfortunately there was a little config file where safestrap stored which slot was last active. This file no longer exist, so safestrap dont know from what to switch where.
The only thing we can try (AFAIK) requires working adb connection and it must be working from safestrap, so you can use adb sideload feature - so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve this, we can try with sideloading, if not I am sorry, dont know what else to do - actually there is one thing you can try - with working adb access you can recreate directory structure needed for safestrap config file and push it there (I will attach it later), then restart and see if it boot to stock rom
edit:
I was able connect through adb from windows to running safestrap, so it is possible (at least kindle is recognized in "adb devices")
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
jamesh1979 said:
ok guys i got the pc to see the kindle in recovery via adb!!! so what now push a rom to internal storage and flash it and then reinstall safestrap to get stock slot available or what????
Click to expand...
Click to collapse
Great!
Now download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device, especially this post (shows similar symptoms as your current problem)
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is "only" TWRP based, I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
C. You can consider also recreating deleted folder containing slot config file for Safestrap (active_slot file attached below (file is in archive, you need extract it)) through adb shell:
0. connect kindle to pc/laptop
1. enter Safestrap
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX recovery
3. type adb shell
4. type mkdir -p data/media/safestrap/rom-slot1
5. type exit
6. type adb push active_slot data/media/safestrap
7. reboot/reboot into recovery and see if you can switch/boot to stock rom (which is still there, otherwise safestrap will not be accessible)
C variant is a really long-shot, but relatively harmless (or maybe not who knows, I am not expert)
OK fingers crossed, I hope something will work, but things can go wrong, unfortunatelly from my side all above is just a theory, adb commands should works, I tested them all (except sideload), works on my side...
Thanx a lot guys I got I t back in action thanx for all the help
jamesh1979 said:
Thanx a lot guys I got I t back in action thanx for all the help
Click to expand...
Click to collapse
Care to share which method you use to recover your kindle?
anyone here? lol