Related
Okay, I know this is a stupid question but how do I run nandroid in preparation to flash a new ROM on my epic 4g? I don't know what it is, I don't know how to use it, can someone link a tutorial or something? ^,^"
Well we've all been a noob at one point so ill help you. Do you have clockworkmod installed? If you do then go to backup and restore in it and hit backup and waitabout five mins and it will be saved to your sd and you can restore it any time you mess up.
THE FROYO EPIC EXPERIENCE
went to ROM manager>Backup ROM and it reboots into recovery, then says
Code:
-- Install from package . . .
Finding update package . . .
Opening update package . . .
Verifying update package . . .
E:failed to verify whole-file signiature
E:signiature verification failed
Installation aborted
Obviously either I did something wrong or clockwork's broken, so...
help D:
Nevermind I'm an idiot, sorry.
-,-
Figured it out.
K then. I see your new here,dont be like everyone else in these forums there all douche bags to noobs.
THE FROYO EPIC EXPERIENCE
deano0714 said:
K then. I see your new here,dont be like everyone else in these forums there all douche bags to noobs.
THE FROYO EPIC EXPERIENCE
Click to expand...
Click to collapse
Don't worry, I won't. I'm just getting used to android because I used to have an iPhone 3GS & iPhone 4 and as such I'm used to jailbreaking/developing for those devices. One I get the hang of android I shouldn't be too much of a burden
And btw, I have another (admittedly noobish) question:
After I backed up, it said no sd-ext found. What's that mean and will it affect the backup? And it saved as 2004-12-31, what's that about?
Me to I came from an ipod touch. The sdcard ext is a place for apps on the sd card and you don't have any on there s its fine it won't efec anything. But idk about the name usually itjust states the date you backedup but it looks wrong but I'm shure it won't efect the file so your all good.
THE FROYO EPIC EXPERIENCE
Yal make me feel like a baby lol. I was a pro windows 6.5 well it was alot easier to hack as well. But guess we all got to start from somewhere.
Yeah man thats where it all starts. Im a fast learner so already know a lot of stuff about android for the 3 months ive had this phone.
THE FROYO EPIC EXPERIENCE
Hi, I installed version 1.4 dexter, now no longer works USB and SD, I could help. I have to install the previous version to solve the problem?. Thanks.
Same here...by the way try to read some of the posts under development tab....
Regards
personally, it's worked great for me.
Really...could you do me a favor and let me know what the folders name are that refer to usb and sdcard....mnt/sdcard/sdcard0-disk0 and usb0-disk0 or just sdcard-usb and usb-disk...
Regards
location: /mnt/sdcard
names are
usb0-disk
sdcard-disk
create with IOFilemanager..
btw, version 1.41 fixes it (just tested removing sdcard-disk folder)
Have fc on the market and a few other apps I wiped and reset any ideas?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
no sorry.. ive not seen such an issue, except if you havent wipe'd signatures can be a problem.. but otherwise its not know why..
you might check the 1.41 update im posting now
Hey dex thanks I thought I had wiped but I didn't reinstalled and followed your direction and everything great donation comming yr way . Hey on a personal note I'm looking to buy another 7 inch what would you suggested. The new HTC or the new acre just wanting yr professional input
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nthknd said:
Hey dex thanks I thought I had wiped but I didn't reinstalled and followed your direction and everything great donation comming yr way . Hey on a personal note I'm looking to buy another 7 inch what would you suggested. The new HTC or the new acre just wanting yr professional input
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
HTC Flyer!!! (im getting it!)
Dexter_nlb said:
HTC Flyer!!! (im getting it!)
Click to expand...
Click to collapse
I So want a HTC Flyer, don't think they are bringing them to the US though.
Its called internet purchase
Man that was it...as soon as I removed that "0" from the sdcard folder name it got recognised by the system...did the same thing with usb folder but it did not help there...hope that mod 1.41 will do the job with usb stick
Thanks Dexter for the clue...
Regards
Hey Dex and Net just read the flyers coming stateside this spring but with 2,2 not 3,0 kinda bummed about that but still looking to get one ( or the Acer iconia a100) just read sprint will be releasing it as there HTC tab. Still no price just yet.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nthknd said:
Hey Dex and Neo just read the flyers coming stateside this spring but with 2,2 not 3,0 kinda bummed about that but still looking to get one ( or the Acer a100)
Click to expand...
Click to collapse
so thats less good news.. was hoping to see a new HTC Sense 3.x for android 3.0 especially on a Tegra platform :-( maybe ill reconsider and going for samsung 10" or simply XOOM
Great minds think alike Dex. All I want is a tab that has it all 3.0 cameras, market,tegra 2 great screen SD slot, good form factor.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nthknd said:
Hey Dex and Net just read the flyers coming stateside this spring but with 2,2 not 3,0 kinda bummed about that but still looking to get one ( or the Acer iconia a100) just read sprint will be releasing it as there HTC tab. Still no price just yet.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
That is weird. I had read that the reason for delaying UK release was to work out bugs between Sense and Honeycomb. Doesn't make sense to me to do all the work for Honeycomb just to release it with Froyo in a different market.
Dexter_nlb said:
so thats less good news.. was hoping to see a new HTC Sense 3.x for android 3.0 especially on a Tegra platform :-( maybe ill reconsider and going for samsung 10" or simply XOOM
Click to expand...
Click to collapse
Sense 3.0? I thought the new release was going to be Sense 2.0. (Ok, I checked, wow am I behind the times lol )
I hope someone here can tell me what I'm doing wrong, since I have been unsuccessful in downloading Dexter's updates and thus haven't been able to fully utilize my tablet! I've been trying to look through all the pages but haven't seen information to help this situation. Hope I don't end up feeling foolish because I've overlooked one simple thing...
This is what's happening:
(A comment: I had to download file from Dexter's site; for some reason, even when I give permission to download the blocked file from here, I just get an "about.blank" page on two different computers!)
I copy the file to my micro sd card (not an sdhc, since it seems that's not relevant). Each time, there is a folder called "LOST.DIR", along with the folder I saved as "update" (I don't add the .zip since it already recognizes it as a zip file.). The "lost" always has a time several hours later than the “zip” file. (Note: I had no problem updating the firmware with the same SD card.)
Since the first time I tried to apply the 1.3 update, and now with the 1.41, I can't install it as directed on p. 1--I can't get into the recovery area because it powers off. Instead, I follow directions found on YouTube: settings, about device, system updates, update device, do it, ok.
“Detect recovery flag, booting update kernel” flashes quickly
"loading" bar is under box with arrow and android avatar for a couple of minutes (the YouTube said it would take about five minutes), then it stops.
I hit home and in blue it says:
Android system recovery <1e>
Android system recovery utility
Reboot system now
Apply update.zip
Wipe data/factory reset
Wipe cache partition
Under the blue line in yellow, it says:
E:Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds
Installation time out.
Installation aborted
Formatting MISC:…
Selecting any of the blue options now does nothing except go back to the box, arrow and android. A couple of times, one took me to a screen that had a list of “no”s with a “yes” option to do something I don’t remember but I didn’t think it was a good idea.
Clearly, I need help!
arrkaycee said:
I hope someone here can tell me what I'm doing wrong, since I have been unsuccessful in downloading Dexter's updates and thus haven't been able to fully utilize my tablet! I've been trying to look through all the pages but haven't seen information to help this situation. Hope I don't end up feeling foolish because I've overlooked one simple thing...
This is what's happening:
(A comment: I had to download file from Dexter's site; for some reason, even when I give permission to download the blocked file from here, I just get an "about.blank" page on two different computers!)
I copy the file to my micro sd card (not an sdhc, since it seems that's not relevant). Each time, there is a folder called "LOST.DIR", along with the folder I saved as "update" (I don't add the .zip since it already recognizes it as a zip file.). The "lost" always has a time several hours later than the “zip” file. (Note: I had no problem updating the firmware with the same SD card.)
Since the first time I tried to apply the 1.3 update, and now with the 1.41, I can't install it as directed on p. 1--I can't get into the recovery area because it powers off. Instead, I follow directions found on YouTube: settings, about device, system updates, update device, do it, ok.
“Detect recovery flag, booting update kernel” flashes quickly
"loading" bar is under box with arrow and android avatar for a couple of minutes (the YouTube said it would take about five minutes), then it stops.
I hit home and in blue it says:
Android system recovery <1e>
Android system recovery utility
Reboot system now
Apply update.zip
Wipe data/factory reset
Wipe cache partition
Under the blue line in yellow, it says:
E:Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds.
Finding update package…
Opening update package…
E: Can't open /sdcard/update.zip
(bad)
Wait for five seconds
Installation time out.
Installation aborted
Formatting MISC:…
Selecting any of the blue options now does nothing except go back to the box, arrow and android. A couple of times, one took me to a screen that had a list of “no”s with a “yes” option to do something I don’t remember but I didn’t think it was a good idea.
Clearly, I need help!
Click to expand...
Click to collapse
Info on your PC setup please. Mac? PC? Linux?
Also, I noticed this "along with the folder I saved as "update"" in your post. you are not creating an actual folder on the MicroSD are you?
Assuming your SD card reader is drive F: (assuming also Windows machine) then your ROM's complete path should be F:\Update.zip
Just trying to avoid confusion that maybe you are creating F:\update\ElocityMod141.zip or something similar
Here is instructions on how to show extensions for known file types http://forum.xda-developers.com/showthread.php?p=11745552#post11745552
As for
Since the first time I tried to apply the 1.3 update, and now with the 1.41, I can't install it as directed on p. 1--I can't get into the recovery area because it powers off.
Click to expand...
Click to collapse
I think the trick might just be to let go sooner...
Start from the device being completely powered down (not just in sleep mode)
Hold power button for 2 (or 3) seconds
Let go for just a split second and hold it down again.
The screen will come on and you will see something along the lines of "to boot into kernel recovery continue to hold for 5 seconds"
Keep holding it until you see something like "booting into recovery" (I can't remember the exact wording)
AS SOON AS YOU SEE THAT LET GO.
Bam, recovery mode.
I think when you get the update you just save one over the other replacing the file this gave me errors IE bad update everytime. Download the 1.41 leave the name it has the same. Delete the update off your sd and cop the newly downloaded one to it after. Once its on card rename it.
netstat_EVO said:
Info on your PC setup please. Mac? PC? Linux?
Also, I noticed this "along with the folder I saved as "update"" in your post. you are not creating an actual folder on the MicroSD are you?
Assuming your SD card reader is drive F: (assuming also Windows machine) then your ROM's complete path should be F:\Update.zip
Just trying to avoid confusion that maybe you are creating F:\update\ElocityMod141.zip or something similar
Here is instructions on how to show extensions for known file types http://forum.xda-developers.com/showthread.php?p=11745552#post11745552
As for
I think the trick might just be to let go sooner...
Start from the device being completely powered down (not just in sleep mode)
Hold power button for 2 (or 3) seconds
Let go for just a split second and hold it down again.
The screen will come on and you will see something along the lines of "to boot into kernel recovery continue to hold for 5 seconds"
Keep holding it until you see something like "booting into rsucecovery" (I can't remember the exact wording)
AS SOON AS YOU SEE THAT LET GO.
Bam, recovery mode.
Click to expand...
Click to collapse
Thanks for such a quick reply!
I'm using Windows 7 Home Premium on a Samsung N150 Plus.
I saved the file as "update" blank SD card. Deleted files each time before attempting a fresh download. Each time have the two files as listed: lost.dir as a file folder and update.zip as a compressed (zipped) file, currently 1,427 kb.
The powered down sequence still does the same, trying it a few times--goes right to device bootup. I remember that from the firmware update (which went without a hitch!) but it's not working now
Aha...progress! May have held down too long but now see in blue
Android system recovery <1e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
(followed by several rows of "no"s and a yes
Beneath that in yellow:
E:recovery.c Can't open /cache/recovery/command
Formatting MISC:...
Have been here before; not sure how I got out!
Is there a possibility for getting root and CWM recovery on this device? i have achieved to get into E3 Recovery, Bootloader mode, and some other test screen.. i posted pics and a description on how to do it. i would really like to get root on this device, i can can help anyone in all ways possible.. p.m. me.
Link to video is in a text file..
I wait for S2109 root too...
I want buy this devise, but without root its difficult use it...
I wait for S2109 root too...
you can find on support.lenovo.com Open Source Code:
fih_uboot_0618.tar.gz 10.7MB
kernel_s2109.tar 445MB
how to obtain these files
Hey how do I find the files u are talking about? Like a link?
nevermind got em
Maybe someone can start developing on the uboot.bin and the system image to obtain some root access
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
WOO!!!
polakko said:
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
Click to expand...
Click to collapse
Awesome! thank you so much! the CWM root worked perfectly. However, the driver from the SDK folder wasn't recognized so I just used the Lenovo ADB driver that came shipped with the device and that worked just fine. Took me about 20 minutes to complete - that includes resolving the driver issue.
Niiice
OK, so the CWM method worked great on my S2109. I had the 4.0.4 update.
Two things:
1) The Lenovo drivers are at Lenovo's support website. Just search for "adb interface driver"
2) In step 3 of el_fuego's instructions, he says "add following to both the [Google.NTx86] and [Google.NTamd64] sections:", add this instead:
Code:
;Lenovo S2109
%SingleBootLoaderInterface% = USB_Install, USB\VID_17EF&PID_748B&REV_0100
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&REV_0216&MI_02
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_74CC&REV_0216
How easy is this root? I'm not really familiar with the process and don't want to brick the device, which I'm concerned about as I don't quite understand the directions.
Lenovo s2109 rooted
@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.
@all: As I imply above the rooting process was free of problems and I have successfully installed CWM. However, after rooting I've run into some other problems:
First:
I rooted before performing a Software update (i.e. I still have the original version 4.0.3). I was planning to make a backup of the system after CWM installation and then update to 4.0.4.
When I try to backup the system using CWM everything works fine until the step "Backing up data..." I get the following messages:
- No /sdcard/.android_secure found. Skipping backup of applications on external storage.
- Backing up cache...
- No sd-ext found. Skipping backup of sd-ext.
- Generating md5 sum...
- Backup complete!
After backing up, I find in the internal sd card 4 files (in total 500K) and a directory called "blobs" with several subdirectories. In total about 2000 files. Is that the backup?
Furthermore, when I try to update to 4.0.4 using CWM, I get the following:
- Finding update package...
- Opening update package...
- Installing update...
- Mount partition
- Verifying current system...
- assert failed: apply_patch_check("/system/app/Launcher2.apk", .....
- E:Error in /sdcard/update.zip
- (Status 7)
- Installation aborted.
If I try to update from the normal system (i.e. outside CWM), CWM stops the update upon reboot.
Any ideas of how to update to 4.0.4 after CWM has been installed?
Second:
I have installed Super Manager from the market. When I try to enable ROOT, I get a message telling that ROOT functions are nor supported in my device. As it could be expected, Superuser does not inform that there is an app trying to get root priviliges, and Super Manager does not appear listed in the superuser's app list.
Third:
It appears that in newer Android builds, it is not possible for third party apps (apps that were not preloaded on the device, but you manually installed or downloaded from Android Market / Google Play) to gain write access to the external SD card. This was not an issue on Android 2.x but it became a problem on Android 3.x.
The implications of this (at least in my cse) is that I can not create folders, copy files or move apps to the external sd card. That even happens with the preinstalled ES Explorer. The solution to this problem is easy if root access is available. One just needs to add the line <group gid="media_rw" /> within the WRITE_EXTERNAL_STORAGE section of the file /system/etc/permissions/platform.xml.
I have pulled the file platform.xml with adb and updated it accordingly. However, I can not push it back because the directory /system/etc/permissions is read only. Any ideas of how to circumvent this problem?
Cheers,
Pisuke
pisuke2012 said:
@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.
Click to expand...
Click to collapse
Thanks, I'll see about giving it a shot.
The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
Jittery Jim said:
Thanks, I'll see about giving it a shot.
The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
Click to expand...
Click to collapse
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.
If there is no JB that will work on this I really have no point in rooting, I guess.
Jittery Jim said:
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.
If there is no JB that will work on this I really have no point in rooting, I guess.
Click to expand...
Click to collapse
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.
Did the tab with JB boot at all? or you had to restore factory defaults with CWM?
Did you update to 4.0.4 before rooting?
Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?
Cheers,
Pisuke
pisuke2012 said:
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.
Did the tab with JB boot at all? or you had to restore factory defaults with CWM?
Did you update to 4.0.4 before rooting?
Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?
Cheers,
Pisuke
Click to expand...
Click to collapse
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access.
The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
Bricked my s2109
Jittery Jim said:
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access.
The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
Click to expand...
Click to collapse
Well, me like the previous people and Jittery Jim above, being too ambitius after rooting s2109 tried JB customs rom's. I did try to flash JB because I have installe CWM V.6.0.1.0 and did make a back up. I used that back-up to restore my ideatab s2109 and it worked fine!
Now after trying to flash JB, which failed :crying:, I can not make a succesfull nandroid back up using CWM . I tried advanced restore and I can restore succesfully : boot , system, cashe, sd-ext, but I can not restore data.
Now my S2109 just boot loop :crying:
Also, I did try the factory reset and it is not working. The same result as boot loop...
Any help available?:angel:
Jeje I have a reboot-loop too.
I've installed CWM and gained root access with this useful guide.
However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.
I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?
At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.
--
Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
luckyjay said:
OK, so the CWM method worked great on my S2109. I had the 4.0.4 update.
Two things:
1) The Lenovo drivers are at Lenovo's support website. Just search for "adb interface driver"
Click to expand...
Click to collapse
All I can find is the adb interface driver for the thinkpad tablet, is that the same as the ideapad?
Also, I downloaded the SDK tools but there wasn't an option for Android 4.04 , just 4.0 (API 14) and 4.03 (API 15). Will it go ahead and install the revision for 4.04? (I assume that I'm supposed to install the SDK tools on my Windows 7 Pro 64bit device, though the instructions just say to download them.)
Thanks.
---------- Post added at 02:55 AM ---------- Previous post was at 02:05 AM ----------
polakko said:
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
Click to expand...
Click to collapse
I downloaded the Android-SDK that was on their site and installed it, but I'll be darned if I can find the files that your instructions say to modify. There's no such directory anywhere on my system. I finally used the exe to install SDK tools thinking that would place the files in the appropriate place but there aren't any. Perhaps the instructions are for downloading the German version? Could you provide a link to the appropriate download site?
Update: I have now downloaded and installed the ADT package and have run the SDK installation standalone (not sure why I need to do both of these steps, but what the heck). I found the correct inf file and did the modifications. However, I did get an error when installing the adb driver so assume I have to install a different fdriver. I have a win7Pro x64 box and am trying to root an S2109 with Android 4.04 installed. I've set the developer tools to enable debugging mode when connected to usb. But is there another adb driver I should download? Is there a driver located on the device itself that might be more appropriate? Again, couldn't find a lenovo s2109 tabet driver, just the thinkpad tablet driver, and it's files don't look right.
Update2: Took a few educated guesses and it worked! I installed the thinkpad tablet adb files after modifying them, by just overwriting the files that were already there. Worked perfectly when it came time to define the drivers and after that it even identified the right device name (rather than Blaze). The rest of it went pretty smoothly. Thanks for updating the instructions on the German site, that was helpful.
Anyone Making progress with CM on S2109?
Or happen to know where there is an active forum discussing the S2109. I also have an HP touchpad running CM9 and it performs much better than my 2109. I'd really love to get CM working on the 2109.
Did this get uploaded?
Otamay said:
Jeje I have a reboot-loop too.
I've installed CWM and gained root access with this useful guide.
However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.
I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?
At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.
--
Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
Click to expand...
Click to collapse
I'm needing a clean copy of this. I bought a display unit that was monkeyed with and the rom is corrupt on it.
If you would be willing to share it with me please contact me at [email protected].
Thanks.
Has there been any work on getting a Jelly Bean Rom for this tablet? Would be nice if we could get CM10.2.
I am having the "Encryption Unsuccessful" message and cannot break through to a solution. I saw the post above where the user seems to have gotten past the error by formatting the data partition via ADB. Can someone tell me how that was done exactly? I am getting a device not found error when I try to use ADB (from the screen entitled (Encryption Unsuccessful) and I cannot for the of me (or google) figure out how to issue the mke2fs and tune2fs commands!
Thanks to anyone who can help!!!
<<<Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...
sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98
Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.
'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...
glad that you able to solve the booting prob...
pls update the roms status after u done with your testing
I'm NOT the developer/creator of this app/method. Chenxiaolong is. Here's the link to the official thread: http://forum.xda-developers.com/showthread.php?t=2447534
Credits: @chenxiaolong - This guy is just great. Our device required many additional hacks and changes to work because of its crappy closed-source update-binary and closed-source Mediatek sources. This awesome dev had to work a lot to get this work fully on our device. Yes, he did. Debug builds, logs, debugging, reworking and all, and he never stopped. That's just amazing. So, I want to thank him wherever you see his post and if you can PLEASE donate as your token of appreciation. :good::fingers-crossed:
@911-Future_Maker Some help and tips in the initial stages.
@FeyoMx Initial helps since my phone wasn't rooted then.
Me. No I'm not exaggerating. I did my fair share of work in testing debug builds and providing logs and testing again. So, press thanks if this worked for you :victory:
Disclaimer:
Neither I nor the dev is responsible for any damage this app does to your device.
You MUST have a nandroid backup in case something bad happens.
Only do something after the whole thread a few times.
Yes, this is true multibooting. Install as many ROMs as our internal storage allows. I can't install more than 3 ROMs (on extsd-slot) as I have a lot of apps.
Here's the procedure:
1- Download the latest version of the app from https://snapshots.noobdev.io and the DualBootUtilities.zip (https://snapshots.noobdev.io/DualBootUtilities-8.0.0.r2162.gc717564.zip)
Note: Only version 8.0.0.r2157.g7d47ab8 and newer completely supports our device.
2- Select ROMs from the navigation drawer of the app on the left
3- Grant supersuser/root rights when it asks
4- Click "Set kernel" if it is asked.
5- Click the three-dot menu on the first ROM, which will be your current ROM.
6- Scroll down and click update ramdisk
7- Reboot
8- Select "Patch Zip file" from the navigation drawer
9- Press the + button and select the zip of the ROM you want to install.
10- Select the slot to which you want to install the ROM.
Take either a data-slot or an extsd-slot.
I recommend using an extsd-slot because the internal memory gets full very fast. Even if you install to extsd-slot, only /system/ is stored on the SD card because having data and cache as image files on the SD card shortens its lifespan by almost a week.
11- Patch the GApps, Xposed or any other zip you want to install to this ROM the same way giving the extsd-slot number you gave for the ROM.
12- Install the patched zip. There are two ways:
I) in recovery (highly recommended)
II) through the built-in zip flasher. Click on the circle in the ROMs page. Add the zips with the plus button. Click the tick.
13- Reboot. It'll automatically reboot the new ROM if it was installed successfully.
14- Voila!! You are now multibooting!
To switch between ROMs, you need the Dual Boot Patcher app on that ROM. Navigate to ROMs, and click you ROM you want to switch. A tick will appear.
Reboot.
EDIT: Forgot about app sharing. Here it is
App Sharing:
Yes, this feature allows you to share the data of your apps across the ROMs. That means you'll have your Chrome tabs open as you left it in the other ROM. Cool !
Instructions:
1- Navigate to App Sharing settings in the navigation drawer.
2- Select "Share individual apps" and reboot.
3- Select the apps you want to share in "Manage shared apps" and select "Use shared data".
4- Reboot to the same ROM. This is very important. If you switch ROMs, you'll lose your data and you will have uncheck "Use shared data" to get it back.
5- Reboot to the ROM with which you want to share data.
6- Install the app if it isn't installed.
7- Do the same as steps 2, 3 and 4 in that ROM. Yes, rebooting to another ROM there can also result in data loss.
8- You will now have the same data across all those ROMs :victory:
I've tried sharing WhatsApp, Google Chrome, a game and Tapatalk and all these work perfectly fine.
Bugs:
I haven't seen any (of the app, do NOT report ROM bugs here)
If you find any, provide logs. If it was while installing provide the recovery.log from TWRP>Settings>Copy logs to SD
If ROM not booting, flash GetLogs.zip from the website (link: https://snapshots.noobdev.io/misc/getlogs/GetLogs-20160120.zip)
If a ROM is not booting, don't worry, reboot to recovery, and flash the DualBootUtilities.zip and switch to primary ROM.
N.B.: The touch screen doesn't work in AROMA on our device. So, navigate using volume buttons. It's a bit weird, but you'll get you used to it.
Yes, it's risky. That's why you should have a nandroid backup.
I'll try to help you as much as I can, but I'm not a dev. So, if you provide logs, I'll see and if it is something new, I'll tell the dev. He is usually busy.
N.B.: This whole post was written on my phone, so it's bad, I know. I'll edit it when I get time.
Please press thanks if I have helped you.
Good guide but if the roms support sdcard as default storage then its worth dual booting
Congrats for this great tutorial my friend! I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits.
---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------
sandeep.sethi said:
Good guide but if the roms support sdcard as default storage then its worth dual booting
Click to expand...
Click to collapse
Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed. Btw @sandeep.sethi I'm having problems trying to dualboot your latest AICP rom. :laugh: 5 fast vibrations and back to recovery.
911-Future_Maker said:
Congrats for this great tutorial my friend! I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits.
---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------
Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed.
Click to expand...
Click to collapse
4 roms ? are they all vibeui based ??
whats ur internal memory space left
---------- Post added at 10:10 PM ---------- Previous post was at 10:06 PM ----------
911-Future_Maker said:
@sandeep.sethi I'm having problems trying to dualboot your latest AICP rom. :laugh: 5 fast vibrations and back to recovery.
Click to expand...
Click to collapse
i dont know bro maybe space is interferring it
sandeep.sethi said:
4 roms ? are they all vibeui based ??
whats ur internal memory space left
Click to expand...
Click to collapse
Of course, screenshot attached. Unfortunately only around 500MB free internal storage.
911-Future_Maker said:
Of course, screenshot attached. Unfortunately only around 500MB free internal storage.
Click to expand...
Click to collapse
its the problem
internal space will be less available
sandeep.sethi said:
its the problem
internal space will be less available
Click to expand...
Click to collapse
Wait! That was an old shot my bad. The one attached below is representing my current usage. I'm using BlissPop, it's a monster.
Interestingly enough I'm same person with the guy who's using the niklabs username @needrom. lol Nice to meet you mate.:highfive:
To be honest 4 roms are overkill, 3 roms can serve me just fine.
sandeep.sethi said:
Good guide but if the roms support sdcard as default storage then its worth dual booting
Click to expand...
Click to collapse
Thanks.
911-Future_Maker said:
Congrats for this great tutorial my friend! I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits. [emoji14]
---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------
Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed. Btw @sandeep.sethi I'm having problems trying to dualboot your latest AICP rom. [emoji23] 5 fast vibrations and back to recovery.
Click to expand...
Click to collapse
Thanks. You are welcome [emoji6]
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
911-Future_Maker said:
Wait! That was an old shot my bad. The one attached below is representing my current usage. I'm using BlissPop, it's a monster.
Interestingly enough I'm same person with the guy who's using the niklabs username @needrom. lol Nice to meet you mate.:highfive:
To be honest 4 roms are overkill, 3 roms can serve me just fine.
Click to expand...
Click to collapse
nice to meet you too
failed to flash zip
Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
Pradeepnegi said:
Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
Click to expand...
Click to collapse
Which is your ROM??
It's because of the ro.build.product of your build.prop
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Pradeepnegi said:
Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
Click to expand...
Click to collapse
This is easy. I'll guess you're installing MIUI or CM right? Because these roms usually contains this limitation about "hermes" only devices. Just open the updater-script which can be found in META-INF/com/google/android path, open it as text via some root file manager and edit it removing the following lines:
Code:
getprop("ro.product.device") == "hermes" || abort("This package is for \"hermes\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Success.
Hey @Salman A. bro I have a little update on your question about that can we install a VibeUI on extsd-slot or in any other slot different than primary. Good news - it works like a charm, screen attached from last night when I was again playing with flashing roms on my phone lol.
Installed VibeUI_1604_ST on extsd-slot all working, I just edited the updater-script to prevent boring errors like that one above removing these line:
Code:
getprop("ro.product.model") == "Lenovo K50-t5" || abort("This package is for \"Lenovo K50-t5\" devices; this is a \"" + getprop("ro.product.model") + "\".");
So now running VibeUI from my extsd card lol, I flashed it just to confirm it's possible, but I think I'll wipe it and flash it again as primary because I mostly play games on VibeUI and I don't want to run a heavy game from my extsd while the entire phone system is also running from the card. It will slow down the things.
Meanwhile I still can't make the AICP rom by sandeep a multiboot ready. Sometimes it hangs at the logo, sometimes vibrates 5 times and reboots back to recovery. I posted at the dualboot thread and really hope that Chen will help me.
911-Future_Maker said:
Hey @Salman A. bro I have a little update on your question about that can we install a VibeUI on extsd-slot or in any other slot different than primary. Good news - it works like a charm, screen attached from last night when I was again playing with flashing roms on my phone lol.
Installed VibeUI_1604_ST on extsd-slot all working, I just edited the updater-script to prevent boring errors like that one above removing these line:
Code:
getprop("ro.product.model") == "Lenovo K50-t5" || abort("This package is for \"Lenovo K50-t5\" devices; this is a \"" + getprop("ro.product.model") + "\".");
So now running VibeUI from my extsd card lol, I flashed it just to confirm it's possible, but I think I'll wipe it and flash it again as primary because I mostly play games on VibeUI and I don't want to run a heavy game from my extsd while the entire phone system is also running from the card. It will slow down the things.
Meanwhile I still can't make the AICP rom by sandeep a multiboot ready. Sometimes it hangs at the logo, sometimes and vibrates 5 times and reboot back to recovery. I posted at the dualboot thread and really hope that Chen will help me.
Click to expand...
Click to collapse
That's great! I'll try out the MM ROM then.
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Salman A. said:
That's great! I'll try out the MM ROM then.
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Click to expand...
Click to collapse
Wait! I forgot to mention that I also tried VibeUI_1606 from needrom and it while it had instaled fine it doesn't boot! Got stucked at the logo... I don't know for the other MM roms, you may want to try 1605 as I already tried 1606 and as you can see without success. So may be no multiboot for MM for now...if you have enouh space on internal you may try and report. So the bottom line:
VIBEUI_1604_ST Android 5.1 is working
VIBEUI_1606_DEV Android 6.0 won't boot.
Phone: Lenovo K3 Note
ROM: 04_K3_NOTE_5.1_1604_STABLE_ROW_004_CUOCO92
Kenrnel fix successful but in primary ROM While updating ram disk it gave error
log file attached
Please help
Using the latest Dualboot 2162 build with the VibeUI_3.1_1606 - can't update the ramdisk and also not indicating that the primary rom is the currently running.
I still can switch to other rom via the utilities zip so for now it's a compromise that I chose to make.
Salman A. said:
Which is your ROM??
It's because of the ro.build.product of your build.prop
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Click to expand...
Click to collapse
Now I have installed k3 note mm 6.0 ui 3.5 dev 1605 row cuoco92 as the primary ROM.
And again same error I m having. But now it is saying this device is aio otfp m. Please help. Even I m not able to update ramdisk.
911-Future_Maker said:
This is easy. I'll guess you're installing MIUI or CM right? Because these roms usually contains this limitation about "hermes" only devices. Just open the updater-script which can be found in META-INF/com/google/android path, open it as text via some root file manager and edit it removing the following lines:
Code:
getprop("ro.product.device") == "hermes" || abort("This package is for \"hermes\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Success.
Click to expand...
Click to collapse
Sir where to find this folder meta inf
Pradeepnegi said:
Sir where to find this folder meta inf
Click to expand...
Click to collapse
In the ROM zip.
Pradeepnegi said:
Now I have installed k3 note mm 6.0 ui 3.5 dev 1605 row cuoco92 as the primary ROM.
And again same error I m having. But now it is saying this device is aio otfp m. Please help. Even I m not able to update ramdisk.
Click to expand...
Click to collapse
You have to change ro.build.product to aio_otfp without _m in your build.prop. If you are still trying that zip, you will still have to edit the updater-script. My advice, don't use it. That's very old. Try the new CM 12.1 Beta 3
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk