Help Flashing modified 3e recovery via wirelesss ADB - Vibrant General

I am getting the e-signature verification error when trying to re-install package from stock recovery. I need clockwork recovery so i can install ROM's. I have a HW issue with my USB which prevents me from connecting to my PC. I have installed wireless ADB so i can flash a modified 3e version of the recovery manager to bypass the e-signature verification. I have a file attached with the modified 3e recovery. The install.bat file is set up for a usb connection with debugging enabled. Is there any way i can modify this batch file so i can use wireless ADB.
Sorry i did not post under development, i am under 10 posts. Every question i have ever had has been already posted until now
Thanks in advance

Having trouble with the USB on your phone? Getting the "This device has malfuctioned" error in Windows? My phone does that too, but I found that when I connect through a USB hub instead of directly to the computer, I can get my phone to work properly about one time in ten. You might also want to daisy chain hubs to get the phone further away from the computer, electronically speaking. It's worth a shot.
I just found this out the other day, and the first thing I did was to flash the modified 3e recovery, then replace it with ClockworkMod However, if I read the thread correctly, you can do it without using USB. If you open up the 3e_recovery_installer zip, you can see that there's really only one important file in there, and that's called "recovery". All the other files are just helpers. The install.bat (which you can edit in notepad) to coordinate the programs, TempRoot.exe to gain root access, adb.exe to install the "recovery" file, and two helper dll files for adb. That's it.
If I read post 9 from the original thread correctly, you can adb into your phone, get root access, then remount your /system partition as read/write with the command "mount -o rw,remount /dev/block/stl9 /system". Once you've done that, you can copy the "recovery" file from the 3e_recovery_installer zip to /system/bin. If you read through the install.bat file, you can see that's mostly all it does, anyway.
The author of post 9 mentions copying keys to /efs, but I can't find anything in the zip file or in the install.bat file about keys, so I'd probably ignore it.
Okay, so I've maybe pointed you in the right direction, now I'll give you some warning. Read everything you can. Read the original post in it's entirety, even though it's boring. Research until you know that you understand everything in that thread. Read through the install.bat file, and research until you're sure you understand everything in the batch file. Your phone's USB doesn't work correctly. You may not be able to flash back to stock. If you screw this up, mistype a command, or miss a step, you might screw up your phone to the point where you can't recover from it without a JTAG flash. Be very, very careful. Understand everything that you do, every command you type, and why you're typing it. Good luck.

Related

Flash recovery image Droid Eris How To

First of all thanks to Amon_RA for this. I had no part in creating this. I am just providing a how to flash it. There may be an eaiser way but this is what worked for me.
First let me say I am on a Mac. If you are on windows the adb commands should work fine but I can't say how to get adb working for you.
1. download flash_image Here Link updated 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download Amon_AR's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
I made an automator script the help all of you having problems getting adb working. Make sure you have the android sdk downloaded and named android-sdk Put it in your home folder and then run this script. Let me know how it works for you.
Disclaimer: I am not responsible for any damage you may do to your phone. I am only providing instructions on what worked for me. This is very beta. Good luck. Enjoy the nandroid goodness.
First link is Dead...........
ooopps Srry my bad, Its up.
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
adb push flash_image to /system/bin
Click to expand...
Click to collapse
I don't think there's a "to" in that command either. lol
testing567 said:
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
I don't think there's a "to" in that command either. lol
Click to expand...
Click to collapse
Thanks. I don't think the "to" is going to work either. I made the corrections.
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Will this put the regular android on it or keep it the same, sorry just kinda getting started with android
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
For testing567:
Do all the adb shell commands run as root against the 2.1_root install ... or maybe the above could be simplified even more by just running "adb root" first?
For Austinjs0102 (not a question)
This process only applies (at the moment) to phones with "2.1_root" - there isn't a path at present to go from "2.1_leak" to a rooted phone. Assuming that a way to roll back (or get root) for "2.1_leak" eventually is found, then the answer to your question is this: it is a process to apply a custom recovery partition to the phone that include tools that will allow you to perform complete phone backups and restore operations. This can be critical for devs who are experimenting with writing boot or system partitions to their phones - if something goes wrong with their experiments, they can "boot" their phone into recovery mode and restore back to a working configuration. To reiterate, though: this only applies to phones that are already rooted.
bftb0
Thanks a bunch that helps clear up info.
hopefully the hard working dev's here find a 2.1 leaked fix for us early people, if not then i may need to lose the phone lol.
Austinjs0102 said:
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Click to expand...
Click to collapse
I am in same boat as you...
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
DocTauri said:
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
Click to expand...
Click to collapse
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Doc,
I understand exactly what you are getting at... and also think I can explain why it's not easy.
First - what has been discovered so far was not a "root break-in", but rather an engineering ROM with root "built in". It is cryptographically signed so that a production phone will recognize the .zip file as a valid ROM. That first validation step has nothing to do with version numbers.
If the "SPL" on an unrooted phone was doing something as simple as looking at a couple of bytes in the initial file downloaded to the phone, then yes - doing what you suggest would work... just patch a few bytes using a hex editor. Unfortunately, the phone SPL is quite sophisiticated: it verifies the crypto signature on the entire zip file first, unpacks that zip, and then examines the contents of an individual file within the zip archive (and possibly even unpacks one of the YAFFS image files and then looks in a file within the YAFFS image) to read version numbers.
That means that the fundamental issue is the cryptographic signature on the .zip file. If you do anything which breaks step #1, step #2 (version # checks) are never reached. Certainly an individual file could be byte-patched, and then images and zip files could be re-assembled... but you would have no way to sign the zip with HTC's private key. Or you could even attempt to byte-patch the zip file - but then that would break the crypto signature. Either way, the crypto signature on the zip file is no longer valid.
If you have HTC's private RSA key, let us know!
bftb0
bftb0 said:
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
Click to expand...
Click to collapse
I added the reboot because. All I would get is out of memory errors. The reboot fixed that.
e.g.
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
northmendo -
That first link (that you corrected) now points to the recovery image, not "flash_image".
Note that the "flash_image" executable which Amon_RA originally included with his first recovery (.zip) is identical to the /system/bin/flash_image binary which ships on the Eris with 1.5 (1.17.605.1); the md5sum signature (of both of those files) is:
16559f2c27d08ff1ddfcaca05fbf10fb flash_image
That's also the same md5 signature as the "flash_image" file which was posted to dl.dropbox.
I don't have 2.1_root installed on my phone, but if the same binary is already on the phone after installing the 2.1_root ROM, there's no need to include those steps in your instructions. It is also possible that even if the "2.1_root" version of /system/bin/flash_image is different, it would also work.
Note that the only reason I bring it up is that your instructions might be (a) unnecessary, and (b) are encouraging folks to overwrite a binary that is already on the phone. No harm (but unneeded) if it is the same, and unknown harm if it is different.
Also (while I'm at it)
901167f6b5541b488c8e0404bceb0631 recovery-RA-eris-v1.6.2.img ***
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
[Edit]***Wow, my post was obsolete the moment I posted it - don't know how I missed Amon_RA's announcement post. Note that there appears to be several versions of "v1.6.2" floating around now - make sure to check his post if you want the most recent.
bftb0 said:
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
Click to expand...
Click to collapse
I will keep the link updated to the newest version here. Also I tried the quicker method without success. I will try it again when I get home from work.
Thanks
bftb0 said:
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Click to expand...
Click to collapse
Sorry, didn't mean to. Understood on the explaination. I didn't realize it was a different rom image, I thought the key had been broken, allowing someone to resign a modified image.
Thanks!
Doc
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
sdk issues for flashing recovery...
Hey guys,
Im a noob but here's whats going on, Ive downloaded sdk extracted it to my c drive, ive downloaded all the required packages reccomended in the forum, Ive up dated my driver and still my machine doesnt recognize my phone...
Ive also extracted the recovery image to my tools directory and added the the path in enviromentals...
So at this point Im stuck as to how to get my pc (xp) phone and sdk in sync in order to get this recovery image working...So any advice would be highly appreciated. Thanks in advance.
Chris
Spencer_Moore said:
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
Click to expand...
Click to collapse
You could try this.
If you have your phone pluged in and type in to the terminal
adb reboot recovery [hit enter]
After you phone reboots it should come up with text options to do back-ups and restores. Do you get any of that?
Anyone know the key combo to get into recovery without adb?
having issues getting adb
got the command prompts working in xp, however while trying the methods here in the forum i am getting adb not foud errors. Any suggestions?

Troubleshooting for Newbies (having a "wtf!?" moment?)

Most of this information has been repeated so many times. But I wanted to make a short list of all the silly mistakes and simple oversights I’ve made over time.
(I make mistakes constantly - there are probably some mistakes in this very post - and I usually search around and try to find my way out of them. I will edit this post whenever I run into a problem. If anyone has any input, I will gladly add it to this post.)
YOU CAN NOT COME BACK FROM UNLOCKING YOUR BOOTLOADER:
If you ever think you’ll need to or want to “relock” your bootloader, you can’t.
Alternative root method:
VISIONary
(when you launch the application, you can leave everything unchecked)
Alternative recovery option:
ROM Manager (in the market)
ALWAYS DO A NANDROID/CLOCKWORKMOD BACKUP!
It will restore everything the way you had it if you F something up.
Want to go back to original shipping, but followed this guide, downloaded the linked file and can’t find the image files?
They’re not in that file. I don’t know why. Go here and download FRG33, decompress it and use the contents to follow the tutorial
Are you getting a “verification failed” error when you try to apply an update.zip in recovery?
Mount your SD card to your computer, download whatever file you were trying to apply directly to it (don’t download it and then drag it), and rename it to “update.zip”.
If you’re using Windows, make sure “hide extensions for known file types” is unchecked in your folder options within the Control Panel. You’ll keep having problems if it’s named “update.zip.zip” and you didn’t realize it
If you're still having problems, try this download of the stock FRG83 update.
<Added 11/18> I had another facepalm moment. If you downgraded back to FRG33 and you get an "assert failed" error, flash the recovery.img from that FRG33 package you extracted. (found this solution here)
Did you flash a ROM or go back to stock, start up your phone and noticed that you’re stuck on Edge?
Go to Menu>Settings>Wireless and Networks>Mobile Networks>Network Operators>(choose your carrier), wait.
Trying to copy something from your SD Card to /system/app (for instance)?
If you use the “cat” command, DON’T FORGET THE “>” SYMBOL. Nothing awful happens as far as I know, but it’s unnerving to watch the terminal puke all over itself.
Code:
cat /sdcard/thing.apk > /system/app/thing.apk
If you’re new to Linux and/or Android and are removing apps:
BE CAREFUL with the “rm” command. Once it’s gone, it’s gone.
You can always rename (technically, "move") the files instead:
Code:
mv /system/app/thing.apk /system/app/thing.apk.bak
Switch the commands to get it back
Code:
mv /system/app/thing.apk.bak /system/app/thing.apk
And don't forget to mount /system as read and write. To do that:
Windows: (must have drivers installed, Nexus One drivers are in the SDK)
Code:
adb shell
su
Linux: (no drivers necessary)
Code:
./adb shell
su
Code:
mount -o remount,rw -t yaffs2 /dev/mtdblock3/system /system
Don't forget to mount /system as read-only when you're finished. To do that, use the same code but replace "rw" with "ro" (without quotations of course)
Having trouble connecting with adb?
In Linux, you need to be in the SDK directoy (mine is in ~/AndroidSDK/tools). In Windows, you need to have ;C:\AndroidSDK\tools in the system path, within Environmental Variables (right-click on Computer>Properties>Advanced>Environmental Variables)
Unplug the device
In Linux, cd to ~/AndroidSDK/tools (or whatever you called it) enter:
Code:
sudo ./adb kill-server
sudo ./adb start-server
Plug in the device
Code:
sudo ./adb devices
In Windows:
Code:
adb kill-server
adb start-server
Plug in the device
Code:
adb devices
Device not found?
Did you enable USB Debugging in Menu>Settings>Applications>Development?
Trying to install an .apk but it just won’t work?
Try the “adb install” method, or push the apk to /system/app. If the app force closes or doesn’t work, just remove it
Code:
rm /system/app/thing.apk
Using Ubuntu (or another Linux distro), trying to mount your SD through Amon-Ra's recovery, but it won't mount?
Disable USB-MS toggle, unplug the phone, reboot your computer, try again.
Can I kiss you?
Seriously though I really appreciate it when the guys on here take time out of their day to post helpful guides like this since it prolly took 30 min at least. Thank you very much for doing this it might have been just what I'm looking for
ap3604 said:
Can I kiss you?
Click to expand...
Click to collapse
Nope.
ap3604 said:
Seriously though I really appreciate it when the guys on here take time out of their day to post helpful guides like this since it prolly took 30 min at least. Thank you very much for doing this it might have been just what I'm looking for
Click to expand...
Click to collapse
I'm glad you appreciate it. I'm not technically one of the guys on here. I've been on XDA in different device forums for a little while but have always been absorbing the information and never giving anything back. This is my first try. I can only dream of being a developer when I grow up, and solving more serious problems.
ahorriblemess said:
Want to go back to original shipping, but followed this guide, downloaded the linked file and can’t find the image files?
They’re not in that file. I don’t know why. Go here and download FRG33, decompress it and use the contents to follow the tutorial
Click to expand...
Click to collapse
Just wondering ahorriblemess, I looked over the guide and it says:
"This will do the followings to your Nexus One:
1. Reset your system files to the original system files.
2. Reset your kernel/boot image to the original shipping boot image.
3. Reset your recovery to original recovery (if you wish)."
Since I'm a real idiot... does this guide get your baseband / radio back to original (january) shipping image as well?
I didn't see it in those 3 things and have the 5.12.00.08 version so I wanted to make sure following that guide would reset the radio baseband back to the original (january) version as well before I did it.
Now all I need to do is figure out how fastboot works and I'm gold!
ap3604 said:
Just wondering ahorriblemess, I looked over the guide and it says:
"This will do the followings to your Nexus One:
1. Reset your system files to the original system files.
2. Reset your kernel/boot image to the original shipping boot image.
3. Reset your recovery to original recovery (if you wish)."
Since I'm a real idiot... does this guide get your baseband / radio back to original shipping image as well?
I didn't see it in those 3 things and have the 5.12.00.08 version so I wanted to make sure following that guide would reset the radio baseband back to the original (january) version as well before I did it.
Now all I need to do is figure out how fastboot works and I'm gold!
Click to expand...
Click to collapse
I don't know. I'm in no way an expert at any of this. My intent with this thread was to compile all of the sort of simple things that I've overlooked in the past. Usually I've found solutions to those problems scattered all over the place, so I just thought it would be helpful to put them all in one place in case anyone ever has the same problems I've had.
I have a pretty good feeling about the answer, but I don't want to share it in case you decide to act on it and it's wrong.
Thanks a ton!

[Q] Here is a good one for ya. Yes, I need some help

Ok. So I bricked my Kindle Fire. Could not access it through ADB. Nothing. So, I followed the unbricking method with fastboot. Got me access to ADB into the kindle again.
So now, one click will not root the device to allow me to put the other images onto the device. Nor will windows 7 mount it.
One click shows that no files or folders exist for the kindle and asks me if I am sure I am running 2.0 or higher.
I can adb into it, but without root I cannot copy files into the needed directories to get it back to stock, or put CM7 on it.
When I boot, i get the kindle fire words, then a black screen. It just stays black. Its better now because at least I can ADB into it, but without root I am hosed, and one click is not working.
I turn myself over to the mercy of the Kindle gods. Any help would be greatly appreciated.
added info:
To be clear. Windows recognizes it, and ADB can connect to it and I can navigate the file structure, but it will not let me root to copy things to the file system.
When I try to use the command prompt to get to e:, a window pops up and tells me there is no disk in the drive. Please insert a disk into drive \device\Harddisk1\DR52. Then the command prompt says, The device is not ready.
With all the knowledge and information going through this forum, not even a suggestion. Pretty please......
I'm no expert sadly but do you need to root to copy over a system file? If not you could push the stockrecovery.img that you can find here (http://forum.xda-developers.com/showthread.php?t=1390773), that may be why your device isnt booting.
Where do I push that to? What location on the device? I have downloaded the image, just not sure where to put it to get it going again.
just google it how to put android etc....
I would not say I am a noob. My question is this. It will not let me mount my sdcard. So when I push update.zip to the sdcard and then try to run it from the sdcard with twrp, I get an error message saying that it cannot mount /sdcard/update.zip, so can I put update.zip somewhere else, lets say in the system folder, and run the update from there?
Not to mention, its kind of messed up that you call me a noob and point me to a video basically telling me to search the forums. Here is the problem with that. I cannot start a thread in the dev forums for the kindle fire until I post 10 times. So while you are calling me a noob and pretty much insulting me and my intelligence, I am far from a noob, I simply could not post my question in the dev forums.
lonelliott said:
Not to mention, its kind of messed up that you call me a noob and point me to a video basically telling me to search the forums. Here is the problem with that. I cannot start a thread in the dev forums for the kindle fire until I post 10 times. So while you are calling me a noob and pretty much insulting me and my intelligence, I am far from a noob, I simply could not post my question in the dev forums.
Click to expand...
Click to collapse
When you do get 10 posts and post in the Dev forum they will just tell you that you posted in the wrong forum.
Your problem has been covered many times on here if you just browse around or search you will find it.
My problem is that the sdcard will not mount, nor will it hold information. I can copy a file to it, and as soon as I reboot, it will erase that file. I have searched for ways to format the sdcard, or format everything and partition but have found no answers yet.
Just for safe measure, I did another search just now in all the kindle fire forums for "mount sdcard" and "format sdcard" and I could find no answers.
Again, when I put a file onto the sdcard, like update.zip, as soon as I run it from twrp, or even fastboot, it tells me that it cannot mount the /sdcard/update.zip file.
On top of that, when I reboot it will not keep the file, it erases it, except the twrp folder, it stays after a reboot.
I can access the system through adb, fastboot and now twrp, but cannot get it to take an update.zip file to restore it. Even though I can access it through adb and fastboot, it does not show up in my explorer window and I cannot browse the device from either a windows 7 machine or a ubuntu 11.10 machine. When I plug it in, the machine recognizes it and charges it, but wont mount it to view files.
It also returned an error saying there is no listing for the sdcard in /etc/fstab.
Not sure what to try next. Any help would be greatly appreciated.
Then you must not have read and write privlage
Sent from my Kindle Fire using Tapatalk
I dont know if it will work but it fixed mine
download this http://forum.xda-developers.com/showthread.php?t=1348782
and flash it with fastboot
fastboot flash system path\to\system.img
and you may also have to get and flash boot.img from an amazon update
asb, I do have read write, tried and verified. It is failing to mount the sdcard. Thanks Kaw. I will give that a try with fastboot.
I have twrp as the boot image. If I reflash from an update will it remove the twrp? I think it would write over it, which, if it worked, would be ok with me. I am going to try both.
When I try to flash the system.img, it tells me the remote image is to large and exits.

Kobo Arc Development

So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this
Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app
127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #
Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app
ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size
Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:
Moved to new thread and more appropriate forum - keep up the good work guys
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.​
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.​
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
​
ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.​
Still don't know what im doing though, but progress is progress ​
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything​
​
ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"
Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy
Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.

[me176c/x] [K013] Collection of ROMs and Updates

[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions
Nice work sub
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list
@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?
slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?
GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command
you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!
No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.
Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
This fixed it! That was a stupid mistake
kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.
I've had several Android devices. That was the easiest root I've ever done.
bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.

Categories

Resources