Hello,
I developed a guide and software package to boot a phone with a fried emmc.
The trick is to use modified kernel files and mount all partitions to image files on SD card - however, kernel files and software are different from phone to phone.
My guide already works nice for HTC Desire Z / G2:
http://forum.xda-developers.com/showthread.php?t=1572924
To port that guide and the linked package to HTC Desire Z I need a tester with a custom rom (ClockworkMod recovery, 3Ext ...). For porting the package I need someone with a full working phone. For testing later someone with a fried emmc would be helpful.
If you want to support me then send me a private message on XDA or visit me on freenode IRC channel #G2ROOT (web interface: http://webchat.freenode.net - channel #G2ROOT)
Best regards,
Catherall
Excellent idea !
If you need tester with fully working phone - I'm in .
Especially as we can use this as some sort of dual boot on working phones to test new roms without installing it
R.
Hello,
I have fried emmc on htc desire s. I sent my phone about 10 days ago to local service. I will get my phone soon. If they don't succeed I will be your tester.
I had a call with service man 2 days ago and he said to me that they can repair it and repair will cost 15€. He said that they will reprogram emmc or something like that and they are waiting to receive 1 file for phone software and when it comes phone will be repaired.
If you need aditional info PM me.
How about the progress on porting to desire s?. I´m available if you look for a tester with a fried chip
All is working as I can say. But not sure if I can post needed files... Lets wait for catherall answer .
R.
He is offline since 23. april so if anyone know to make this work do it
Ok, all credits going to catheral. I'm tested this with working desire s and phone is booting from recovery without any problems. You just need to extract downloaded files to sdcard root and apply update.zip from recovery ...
https://www.dropbox.com/s/e5nusi7ojg65q8e/Saga_recovery_boot.rar
R.
Great! Thank you. This is big thing for desire s now because emmc problem is now fixed.
One question: When I restart or turn off phone do I need to do update in recovery again or this will be permanent ?
So im confused what does this do? Is there anyway to port it to the htc incredible s?
Sent from my Incredible S using XDA
first thanks for the great work which catherall has done.
Just put this on my sdcard and booted from recovery via update.zip. I can confirm that this rom is booting on my desire s with fried emmc. Overall the performance is pretty fast but there are few limitations:
Wlan doesn´t work
Each time when an app is trying to acess the internal memory, it crashes(since there is no internal memory due emmc brick)
Working (tested):
phone calls
text messages
acessing internet via HDSPA,Umts,...
everything which doesn´t need access to internal storage
app installs
Great!
Rolf can you fix wlan ?
Hey catherall.
I was just thinking when reading your thread..i don't have a fried emmc but it might help you or someone else develop a permanent fix for this issue.
If you can boot the phone from the sdcard via this "temp fix" which is brilliant btw (hats off to you)..i guess that you could try to do this natively.
Bear with me as i am no expert in android or any other programming development but i do have a technical inclination.
To my understanding the emmc holds these partitions: /system; /data; /cache
Also, the partition layout is dictated by the HBOOT (am i right?).
Thus, if HBOOT is functional after frying the emmc can't the hboot be reprogrammed so as to allocate the /system; /data; /cache to the sdcard thus natively run them on the sd and by this fixing the current issues? I'm thinking yes because if the rom is installed with the mentioned partitions being on the sd it will not try to access the emmc thus no failures, issues, kernel oops or panics.
Keep in mind that i'm not properly educated in this domain of expertise and what i wrote might just be a huge load of *$#& and that what i said is purely a principle based on what i understand about the android platform.. no idea how to code or reprogram HBOOT so i might be wrong.
P.S. sorry about cloning posts..
Hands up to the original Dev of this great project. this will help a lot of people. who are having problems with their fried chip. however once this ROM is stable you wont be able to upgrade it or anything so you will be stuck with this Rom. now. you can replace your chip for very little cash. you just need the brains to replace it with the old 1. Is this rom even good enough. i mean in eyes of people who are serial flasher's they are going to want to flash a new rom lol. and 2 is there any way we could just have a new development section that is FOCUSED on development with fried chip roms like this 1. i think this could be extended. i think if this can be done with cyanogen then it can be done with stock Rom also. im very intrested in asking the mod to set up a dev section for this so we can develope roms that are aimed at peple with fried chips. as this will help a lot of people. we could develope or mod the roms out at the moment for the people with fried chips. if anyone else agree's with me then please reply if enough peole on this forum want it done i say we get on it now
hey Paul.
Im with you 100% but i think that there needn't be specific emmc-fried roms (the rom components can be extracted and installed to the sd manually by each user if a guide is made). The problem i believe are the kernels as they are the subsystem that communicate to the hardware, not the rom itself.. if my previous post is right though, then i believe that the roms can be flashed normally and be directed to new partitions on the SD automatically.
xxmorph3u5xx said:
hey Paul.
Im with you 100% but i think that there needn't be specific emmc-fried roms (the rom components can be extracted and installed to the sd manually by each user if a guide is made). The problem i believe are the kernels as they are the subsystem that communicate to the hardware, not the rom itself.. if my previous post is right though, then i believe that the roms can be flashed normally and be directed to new partitions on the SD automatically.
Click to expand...
Click to collapse
in that case there would have to be a new kernel with every rom made for this. im my experience i would say that i wouldnt go ahead as ask for a dev section for this to be opend. i will infact tho test this out and see if the rom itself can be installed to a new partition on the sdcard. i will let you know if the rom is able to install onto the sdcard later tonight. i very much dont think it will tho. but worth a shot. if it does work then does that mean we could get this more stable and without crashes ?
The rom will definetly not boot if you just install it to sd..no need to test that.. The partition table needs to be rewritten for this to work (the partition layout being stored in the HBOOT to my knowledge). This is why i suggested rewriting the HBOOT, because if i am right the recovery will flash every rom and kernel to the new partitions on the "fake" emmc (SD that is).
xxmorph3u5xx said:
The rom will definetly not boot if you just install it to sd..no need to test that.. The partition table needs to be rewritten for this to work (the partition layout being stored in the HBOOT to my knowledge). This is why i suggested rewriting the HBOOT, because if i am right the recovery will flash every rom and kernel to the new partitions on the "fake" emmc (SD that is).
Click to expand...
Click to collapse
hmmmmm im curious about this. but then again would anyone with a fried emmc chip be willing to flash a re written hboot that has a chance or 50% bricking there phone lol ? too messy for me im going to stick to making my sense tablet rom for now
Hboot 0.98.00000 and 0.980002
Mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.eamobile.nfsshift_na_wf-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.fridgecat.android.atilt-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/pl.idreams.skyforcereloaded-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.ArtInGames.AirAttackHD-1 vfat ro,dirsync,nosuid,no
dev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
HBOOT 2.xxxxx
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Hehe, good luck with your port..i really like your ICS tab_mod!
As for the "who would risk bricking their phone"...i don't think that with a fried emmc there's anything else to brick.
Anyway, on a serious note though, i have no idea how hard rewriting a HBOOT would be, nor if it will actually work..i am no experienced programmer, this is why i recommended the "method" to a more experienced user in hope that the emmc damaged guys could catch a break.
Sure, as you said, replacing the emmc is a waaaay better solution but hardware modifications are not that easy and should be done only by specialized personnel which can be $$$.
xxmorph3u5xx said:
Hehe, good luck with your port..i really like your ICS tab_mod!
As for the "who would risk bricking their phone"...i don't think that with a fried emmc there's anything else to brick.
Anyway, on a serious note though, i have no idea how hard rewriting a HBOOT would be, nor if it will actually work..i am no experienced programmer, this is why i recommended the "method" to a more experienced user in hope that the emmc damaged guys could catch a break.
Sure, as you said, replacing the emmc is a waaaay better solution but hardware modifications are not that easy and should be done only by specialized personnel which can be $$$.
Click to expand...
Click to collapse
above is the mount info from desire s hboot 0.98.0000 and below is for hboot 2.xxxxx.
Thanks my rom is nice lol . im making the same rom but with sense its going well just need to port rosie from flyer then its done
This information is available in this sticky
http://forum.xda-developers.com/showthread.php?t=1180513
Looking forward to sense tablet version
Sent from my HTC Desire S using xda premium
Related
After a sleepy ODIN flash, using SPICA ops with G3 firmware => STUPID??? NO, not done yet , next ODIN flash segment, accidentally stick clear phone EFS via Debug options (DOUBLE CRAZY!!!) NOW i lost the precious IMEI and /efs partitions corrupted as well.
i've got the fixed nv_data.bin and both stl4.img and bml4.img from [email protected] (attached). Thanks for his kindness and supportive to the community!
But even with those i still can't fix the issue!!!! /efs did not mounted via mount command...
as in a GOOD G3, mount command result will be as below:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/stl6 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
[B]/dev/block/stl4 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0[/B]
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0702,dmask=0602,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
in my case the bold line just missing... so this is must be the problem.
I tried to do the same as SPICA's method as below:
Code:
$su
#dd if=/sdcard/bml4.img of=/dev/block/bml4
#reboot
It's OK then but...
Code:
$su
#dd if=/sdcard/stl4.img of=/dev/block/stl4
/dev/block/stl4: cannot open for write: Invalid agrument
With this error my /efs cannot be mount... and still missing from the mount command. I'm just a linux noob so pls help me out. How can i restore the stl4 partition properly???
My girlfriend now really mad at me due to she don't have her beloved phone this christmas already. OMG!!!!!
and to all rooted i580x user Pls kindly help compare your "good" /efs folder... maybe mine missing something???? due to one time Erase Phone EFS using Odin Debug Options.
Mine /efs now as below:
Code:
/efs/nv_data.bin
/efs/imei/.nvmac.info
/efs/.files/.dm33 (empty folder)
/efs/.files/.dx1 (empty folder)
/efs/.files/.mp301 (empty folder)
And if you can do adb shell, it'll be very kind of you by sharing your good backup stl4 and bml4 - for research purpose (those partitions did not content any of yours personal data - so PLS HELP!!!). Pls do the backup partions as below and share your img here if possible.
Code:
$su
#cat /dev/block/stl4 > /sdcard/efs_dev-block-stl4.img
#cat /dev/block/bml4 > /sdcard/efs_dev-block-bml4.img
TIA and Best Regards
P/S: when do the ls /dev/block/stl* the stl4 is there but cannot restore using the backup img. it's weird...
Code:
#ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
same for bml4...
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Szaby59 said:
I suggest you remove the images.zip
This contains your IMEI, so anyone can clone it.
Click to expand...
Click to collapse
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
kenblat said:
This zip only bml4.img and stl4.img, the fixed nv_data.bin still inside the phone @ SAMSUNG SC . Now they still can not redo IMEI yet so i must find someway else.
Click to expand...
Click to collapse
fixed ur phone yet? noob idea: can u try flashing but this time with the right ops?
were you able solve the problem? I am facing exactly same problem.
Trying to get Dexter's native ext2 support working.
I pulled my SD card (8gb) and using GParted within Ubuntu, deleted my FAT32 partition, created 1st partition FAT32 ~7gb, 2nd partition ext2 (1gb), 3rd partition SWAP (64mb)
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Under memory/sd card sotrage, phone is reading ~6.9GB as expected of the FAT32 partition.
Am I missing a step? Nothing ever gets moved from the phone to the card's ext2 partition.
ext2,3 problem on dexters rom
Sorry first post noob, hopefully im doing this right
I used mini tool partition wizard... i tried ext2 then ext3, made them logical and primary, with the swap partition. (do we need that swap ..i haven't tried it without it).
And the entire memory card wouldn't be recognised/mount at all when turning on the phone. I had to remove the partitions to be able to use the memory card in the normal manner.
is there another step? i was hoping all i had to do was make the partition and it would be done.
help!
did u guys set the ext partition to active?
I did not mark any partition active (none of the many guides on the net say anything about setting partition flags). My layout (per parted) looks like this:
Code:
Number Start End Size Type File system Flags
1 1049kB 6818MB 6817MB primary fat32
2 6818MB 7892MB 1074MB primary ext2
3 7892MB 7959MB 67.1MB primary linux-swap
Which matches every screenshot I have seen of parted/Gparted in any formatting guide.
I did find one that had fat32 marked as lba, but that makes no difference.
R-D said:
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Click to expand...
Click to collapse
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
I realised what i did wrong ..I tried to make the ext2 partition after I 'installed/flashed' dexters rom ...this messed everything up for me.
So I re-did the entire process but made my ext2 partition first. Now its allgood
Don't know if that helps
Sent from my XT720 using XDA App
kousik said:
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
Click to expand...
Click to collapse
Here's the default mount output:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
tmpfs /skttmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock7 /system/lw yaffs2 ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
When I try and mount it manually, which device name is preferred? I found the partitions (1 = fat32, 2 = ext2, 3 = swap) as these names:
/dev/block/vold/179:1
/dev/block/mmcblk0p1
/dev/block/vold/179:2
/dev/block/mmcblk0p2
/dev/block/vold/179:3
/dev/block/mmcblk0p3
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Thanks for your help.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
R-D said:
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
Click to expand...
Click to collapse
"No such device" is indication that the kernel module is not loaded properly.
You may have to insmod ext2.ko yourself to get it to work. If you do not have the .ko files, you can download from http://dateno1.egloos.com/27191 yourself and copy to /system/lib/modules. Also you can see this thread http://forum.xda-developers.com/showthread.php?t=929871 for reference.
Okay, mystery solved!
I am missing these modules as I grabbed the "original" 1.1b update (1.1a-update.zip). This original file was missing these modules and had an incorrect overclock module.
I just re-downloaded 1.1b again, and found that if I look in the ZIP file, it has the missing modules I didnt initially get.
In speaking with Dexter, it seems that he updated the 1.1b (1.1a-update.zip) file twice, but kept the same file and version name. So the 1.1b everyone else is using, is newer than the 1.1b I downloaded, as I downloaded it right after it was first posted and missed the next update as it had the same filename.
Essentially, what amounted to 1.1c was also released as 1.1b ...
So lesson is, either redownload and apply the 1.1b update, or update to 1.2 (or newer as they come).
Thanks for your help.
Oh ! Confusing this 1.1a/b/c !
is it nid to do it manually? 1.1b did detect my ext2.. but in 1.2 did not detect.. i try put ext2 and ext4 ald..
Anyone found anything that cleanly reboots the system (normal reboot/into recovery)? Must have tried at least 20 of these things and all result in overclocking not applied after reboot due to unclean shutdown...
Is this an Android bug or what? Power off/power on via the HW button works correctly.
(Froyo 2.2.2 here, other details - see signature.)
C'mon, folks, second thread I have posted and once again am I talking to myself...
simmer down now - i've always used and had recommended to me Quick Boot.
its always kept my cpu settings afterboot.
question is if your HW button reboot doesnt reset cpu, why do you want an app?
jessehclark said:
question is if your HW button reboot doesnt reset cpu, why do you want an app?
Click to expand...
Click to collapse
Hmmm? Well, it is obviously more convenient? Or because it can boot to recovery and other modes as well without breaking your fingers trying to press the required buttons combo?
Why not root and get cyanogenmod or set cpu overcpock
Sent from my U20i using XDA Premium App
daproman said:
Why not root and get cyanogenmod or set cpu overcpock
Click to expand...
Click to collapse
I am rooted.
SetCPU or No-Frills does not matter, exactly the same problem since they both check for unclean shutdown and no not overclock automatically after reboot (feature, not a bug).
Again, the problem here is unclean shutdown, not SetCPU or anything else really.
I would say the issue is this: http://forum.androidcentral.com/899945-post5.html - except that it does not quite make sense why does a power off / power on cycle work cleanly and reboot does not.
I have seen many people having the same problem on different ROMs, so - I am seeking a technical explanation and solution, not workarounds.
Code:
# cat /system/etc/vold.fstab
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.1/mmc_host/mmc0
# vdc volume list
110 sdcard /mnt/sdcard 4
200 Volumes listed.
# mount
rootfs / rootfs ro,noatime,nodiratime 0 0
tmpfs /dev tmpfs rw,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
/dev/block/mtdblock1 /system yaffs2 ro,noatime,nodiratime 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock3 /lgdrm yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/vold/179:2 /data/sdext2 ext4 rw,noatime,nodiratime,barrier=0,data=ordered 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,a
llow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0
702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Technical explaination(1): there is no public API to ask for a phone reboot.
Quick rebooting apps just call the command "reboot" (from a "hidden" terminal, let me put it this way for simplicity's sake) which reboots the phone without "shutting down" the Android UI layer.
(1): call it guesswork, really. I haven't checked CyanogenMod's source to see what they do in the power-poweroff button.
hrk said:
Technical explaination(1): there is no public API to ask for a phone reboot.
Quick rebooting apps just call the command "reboot" (from a "hidden" terminal, let me put it this way for simplicity's sake) which reboots the phone without "shutting down" the Android UI layer.
(1): call it guesswork, really. I haven't checked CyanogenMod's source to see what they do in the power-poweroff button.
Click to expand...
Click to collapse
Good, moving in the right direction. I guess I should have posted this in the development section in the first place... meh.
This version of ClockworkMod recovery has been produced by Milaq
There's currently a github repository for the device/lenovo/a1 folder in the Cyanogenmod Android tree at https://github.com/gmarkall/android_device_ideapad_a1
Current status: CWM v6.0.1.2 by Milaq
Download: http://milaq.exnet.me/downloads/android/a107/cwm-6.0.1.2-ideapad-a1.zip
What appears to work: backing up, erasing and restoring /system, /data, /cache and /sd-ext. Installing zips from internal and external SD cards. Touchscreen calibration. Partitioning the external SD card. Installing OTA packages also works, but they will wipe out this recovery
What's not supported: backup/restore of the x-loader, u-boot, kernel or ramdisks.
Installation of 6.0.1.2 from the stock recovery
WARNING/DISCLAIMER: Although the recovery has now been tested by several people and there have been no problems reported, there is still a small risk of damage or problems due to unforeseen issues. The unlikely worst case scenario is that your A1 will be bricked. In the event that something goes wrong, I will do my best to help recover the situation, but I am not liable for any damage incurred. It is up to you to decide if you want to take this risk. If you are not comfortable with the risk, then do not attempt to install the recovery!
Now that's out of the way, and if you're willing to take the risk, the following steps should be taken to install the recovery:
1. Download the file "cwm-6.0.1.2-ideapad-a1.zip" from the hosting page.
2. Copy this file to the root of the internal SD card and rename it to update.zip (so the full path should be /sdcard/update.zip)
3. Power down the Ideapad.
4. Hold down volume down and turn the power back on, keeping volume down held until the tablet boots up to an image of an arrow out of a box with an android (this is the stock recovery).
5. Wait whilst Clockworkmod recovery installs. The progress bar should fill up.
6. Once the installation has finished, you should see a green tick in a green triangle and the ideapad will power down.
7. You can now power on as normal to get back to Android, or power on with volume down held to get into Clockworkmod recovery
8. Please post your experiences, and any issues you encounter in responses to this thread - feedback will be really helpful to smooth out any issues, and/or to gain confidence that the recovery is working properly.
Installation from an older version of Clockworkmod
If you have installed a previously released version of of this CWM, you can install the latest version in the usual way in which zips are installed in CWM.
Going back to stock
You can install the stock-a1-recovery.zip file using Clockworkmod to go back to the stock recovery.
IRC Channel
#ideapad-a1 on irc.freenode.net
Thanks to
Milaq, who built the recovery
Henge, for providing me with information before I got my Ideapad
Spiegeleixxl, for information about the bootloader and how to produce a bootable SD card
Imritechere, Otti17, and Mikerizzo97 for testing out the recovery
Xbdesign, for translating installation instructions into German, and testing the 5.0.2.8 recovery and MBR
Kryszan, for translating installation instructions into Polish
Monsefito, for Spanish translation of instructions
Great job. Thank you in advance for your hard work
Gesendet von meinem A1_07 mit Tapatalk
Yes! All the best for your endeavor!
Hmm, let's see...
Code:
$ cat /proc/emmc
/proc/emmc: No such file or directory
Maybe this helps...?
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 292969 mmcblk0p1
179 2 195312 mmcblk0p2
179 3 1953125 mmcblk0p3
179 4 34180 mmcblk0p4
179 5 12856445 mmcblk0p5
179 16 3872768 mmcblk1
179 17 3872737 mmcblk1p1
Hi Henge,
Thanks for that! I didn't realise there would be no /proc/emmc - perhaps it had a /proc/mtd instead...
Would you be able to show me the output of the mount command as well please? Then I should be able to figure out which of those partitions is which of system, data, etc..
Many thanks for your help!
No, no /proc/mtd either.
Here's the output of mount:
Code:
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p1 /system ext3 ro,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p2 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /.secure ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
debugfs /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p5 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/sdcard/removable_sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/removable_sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Hey.
with cat /proc/mtd is the same
Henge,
Thanks for this - I'll put together a recovery.fstab based on this for now!
Glad if I could help!
Nice to see someone working on this. Thank you! There is a somewhat active community of users at this link on XDA that I'm sure are going to be pleased to see this thread.
Keep us updated on your efforts please and thanks a ton in advance! Looking forward to your progress!
Gesendet von meinem A1_07 mit Tapatalk
I updated the recovery.fstab according to the information that Henge provided and rebuilt the recovery. I think one piece of information that I'm currently missing is the erasesize for the emmc, but I'm not sure what command should be used to find out what it is since there was not /proc/emmc or /proc/mtd.
I've also been examining the OTA update to see how it flashes partitions. It appears as if there is a utility included called "fuse" that writes partition images. It looks as though the fuse binary isn't on the system partition in the OTA, but my present thinking is that it might still work for flashing the recovery ramdisk. I've made the fuse binary available on the download page linked from the github repository, but I'd still recommend against trying to flash the recovery unless you're really sure you know what you're doing, as I haven't been able to test it yet.
Happy to help when you get to the CM stage. Post or PM if there's anything I can do. At the moment, I've got the ear of a Lenovo customer advocate who is working on getting the code properly published. I'll ping him after the holiday and report back.
Hi Sinanju,
Thanks! When I posted the message on the Lenovo forum I mentioned that I was personally after the Linux kernel sources - however, subsequently I noticed that the tablet also uses the u-boot bootloader, which I believe is also GPLed and the sources may be helpful - have you heard any mention about this?
I have not. When I ping the Lenovo guy I'll add it to the list of source they'll need to release.
Update: Email sent.
This CWM has been a long time comming thanks for the effort. Keep us informed
The Nook Color uses almost the same hardware (but no gps and camera).
It has a really good working CM7 build. So maybe this would be a good starting point.
It also uses u-boot and has a includes a modified one in CM7 (booting from sd or internal).
Thank you for this effort!
Hi TDO,
Thanks - I had noticed the CM7 for the Nook Color - I've been using it to guide me so far in building the recovery. I had also seen that it includes the modified u-boot but I wasn't sure what the purpose of it was.
Edit: Apologies, I misunderstood your post at first. Re-reading it, I understand that the purpose of the modified u-boot is to allow booting from the internal or external SD card.
Since I'm not a new user anymore, I can now post links to the repository and hosting for the built recovery:
Repository: https://github.com/gmarkall/android_device_ideapad_a1
Hosting: http://www.doc.ic.ac.uk/~grm08/ideapad/
(I still wouldn't recommend attempting to try out the recovery yet, but it's there if anyone has any other purpose for it).
FYI - rumor, fake or truth, who knows - but there's a youtube video showing ICS on an Ideapad A1 which is said to have been leaked on a chinese website and that there's news from Lenovo they will release Android 4.0 for A1 later.
So I recently got a Lenovo A2010, and I've been looking for ways to root it in as to have better access to settings and features it currently doesn't offer (like making the Mass Storage mode available when connecting to a PC, instead of the annoying MTP, grr). Searcing around the 'net has insofar been useless finding only a thread here on XDA that's for a different model from Lenovo (A6000 Plus, the thread is here), and it recommends using a app which I wouldn't trust, and which bricked some people's phones. So I wanted to ask you guys if there's any (other) way of rooting this phone, preferably with the ability to update the OS. The phone itself has Mediatek MT6735M as chipset and runs on Android version 5.1.
Also I wanted to ask you guys (and I hope I'm not rude for asking this...) if you could assess whether or not it would be worth the time to build a CM rom for this phone. Are there any similar phones to this one that could ease the task? Again, searching around for the chipset's "compatibility" with CM (as advised by the starting guide for building CM on the wiki) didn't turn up much. I'm not much of a developer, I know only rudimentary stuff, like compiling source codes on linux, but if building the ROM for this phone isn't that complicated (as the wiki suggested it might be in some cases), I would like to try.
*bump*...
+1
Reason, why I want it too is, that I also own a Lenovo A2010-a (notice the "a", but I personally don't think that there are any differences). Having AT LEAST Android Open Source Project (AOSP) ROM would be nice.
I am also giving sourcecode for the phone: Lenovo A2010-a.
I hope that someone will start the project. Personally, I tried to do at least hardware mod. My intention was to swap cameras for more convenient QR code scanning.
Therefore I wanted to open a category for it, but I am not a developer.
Mine's with an "-a" at the end too in the manual.
The problem is that nobody is interested in low-end phones. I think that A2010-a can run Marshallow too, just what we need is CWM and how to set & pack ROM.
I have managed to perform cat cpuinfo, so I am posting it here.
Code:
Processor : ARMv7 Processor rev 4 (v7l)
processor : 0
BogoMIPS : 7.24
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : MT6735M
Revision : 0000
Serial : 0000000000000000
Also, same for /proc/mounts:
Code:
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=755,uid=1000,gid=1000 0 0
tmpfs /storage/usbotg tmpfs rw,seclabel,relatime,mode=755,uid=1000,gid=1000 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/nvdata /nvdata ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:129 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:129 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I will try to work futher to get more information about this device. I hope that someone will be interested in this device, tell me what to do and I will try to gather more data.
@kossieh: Did you root your phone?
And similarly to kossieh, if anyone needs any intel on the phone, I'd be happy to provide it.
Ok, just a major update:
I have downloaded some files from this website and it seems that this file has some kind of script, that could be used to make bootable ROM.
Actually, it is a updater-script, which (AFAIK) is also used anywhere else. According to my cat /proc/cpuinfo, the only thing that needs to be done is to compile "su" binary for the platform and then it could be used to flash the SU (understand it as create a ROOT and UNROOT zips to do the job). Then install some kind of root app (SuperSU or Superuser, depends - probably) and then it could be done.
Question is about CWM, if the bootloader permits to load a tempovary CWM (as I did on my S5830i - just a note) and then install any, now modded, ROM into device.
I presume that managing partitions and filesystems would be tricky, so I WOULD LIKE to ask anyone, who is interested in futher developing. I would like to also contribute, because it makes sense. Maybe we'll be good enough to create CyanogenMod 12 (or 13?) - just to match Marshallow. Or, we can stick to 5.1 (which is good anyway) and make a clean Android ROM (personally I would appreciate that).
As promised, here is updater-script for information:
Code:
getprop("ro.product.device") == "A2010-a" || abort("This package is for \"A2010-a\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));
assert(package_extract_file("mobicore.bin", "/tmp/tee1.img"),
write_raw_image("/tmp/tee1.img", "tee1"),
delete("/tmp/tee1.img"));
show_progress(0.200000, 10);
apply_sig(package_extract_file("sig/boot.sig"), "bootimg");
I was also surprised that this is for Lenovo A2010-a. Maybe there is only device, just A2010-a.
Also, I'm posting a "scatter.txt", I don't understand clearly, what it is, probably a flashing tool specific config? Or is it a map for the device storage?
My opinion is, that it could be a map of the device storage system, including intervals, where the storage ends and partitioning.
Code:
preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
lk 0x1c80000
para 0x1d00000
boot 0x1d80000
recovery 0x2d80000
logo 0x3d80000
expdb 0x4580000
seccfg 0x4f80000
oemkeystore 0x5000000
secro 0x5200000
keystore 0x5800000
tee1 0x6000000
tee2 0x6500000
frp 0x6a00000
nvdata 0x6b00000
metadata 0x8b00000
system 0xb000000
cache 0xab000000
userdata 0xc4000000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004
The last is "type.txt", which has just one thing inside, and that is just "1". To be correct regarding to xda dev forums, also in code:
Code:
1
The package itself also contains 2 extra files (i digged directly from update.zip!) and they're:
Credits.txt
How to flash OTA file.txt
...where "How to flash OTA file.txt" contains just a description:
Code:
Copy the update.zip file to the phone SD and flash it through the stock recovery mode.
Or
Copy the update.zip file to the phone SD and flash it through the Settings > About > Check Update (only if your device support this method).
Instruction by androidxda.com.
I also downloaded all files (3 gigs in total) and I will investigate when I will have time. My wish is to call for someone who would help us with development. As stated before, I am ready to help, as well as I am sure that original author of this thread (andoruB) probably wants too...
here is something in russia.
hxxp://4pda.ru/forum/lofiversion/index.php?t688416.html
Isn't that the original stock ROM?
Also... *bump* in hope that someone gets interested in porting CM or to give any of us build instructions.
Another A2010-a owner here, would be really interested in having more control and making USB OTG work on the phone (seems there is some support reported, but no drivers get loaded when I connect a mouse or a pendrive).
Also, in the Developer options, there is an "OEM unlocking" option with the description "Allow the bootloader to be unlocked." Contrary to what I've read in forums, where unlocking and then locking again would brick phones, I turned it on and off again (between reboots) and nothing bad happened.
What does that feature actually do?
andoruB said:
What does that feature actually do?
Click to expand...
Click to collapse
According to step 9 in http://www.droid-life.com/2013/11/04/how-to-unlock-the-nexus-5-bootloader/ , where they unlock the bootloader of the Nexus 5:
"9. Your bootloader is now unlocked and ready for root, ROMs, recovery, etc."
However, they go on to say that:
" 11. During reboot, your phone will go through a factory reset."
And I remember reading somewhere that unlocking the bootloader of an Android phone can break future system updates because of some checksum failure, thus bricking the phone, but this might be a bug (or a feature) of a particular model, don't know...
Seeing as there aren't any proper custom ROMs for this device, any idea how to root the phone?
andoruB said:
Seeing as there aren't any proper custom ROMs for this device, any idea how to root the phone?
Click to expand...
Click to collapse
This is taken from the Russian forum, the link to which was given in post #9 above.
I'll try to explain the procedure here in English:
1. Download the file UPDATE-SuperSU-v2.46.zip from here: yadi.sk/d/TFXtd56Ekx5Yi and copy it to the SD card in your phone (or download it directly with the phone).
2. Download a custom Recovery like TWRP: yadi.sk/d/0WaK6e4Mkx5cx and the program SP Flash Tool: yadi.sk/d/9xDmAavuiX4Ce.
Run SP Flash Tool to install the custom Recovery.
(at least in my case, there was no need to toggle the "OEM unlock" option in "Developer Options", the bootloader seems to be unlocked anyway)
3. Reboot to Recovery by holding the Volume Up button pressed while the phone is booting.
In the boot menu that appears, move the selection cursor to the [Recovery Mode] option, by using the Volume Up button, then press the Volume Down button to select that option.
You should now get into TWRP Recovery, that you flashed in step 2.
4. From TWRP Recovery, install the previously downloaded file (UPDATE-SuperSU-v2.46.zip).
5. Reboot. Your phone is now rooted.
Ohhhh? Is this working? I am scared to brick my phone. Can someone test this one?
Executable000 said:
Ohhhh? Is this working? I am scared to brick my phone. Can someone test this one?
Click to expand...
Click to collapse
I tested it the next day after I got the phone and it's working. A lot of other people rooted their phone by this method too, so far I haven't heard of anyone bricking their phone.
At the moment, as far as I know, this is the only working method for rooting Lenovo A2010.
...
By the way, besides the files in my first post above, if you are using Windows, you obviously need to have the proper MTK drivers installed too, so that SP Flash Tool can connect to the phone.
If you are a Linux user, see this post http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
W60 said:
I tested it the next day after I got the phone and it's working. A lot of other people rooted their phone by this method too, so far I haven't heard of anyone bricking their phone.
At the moment, as far as I know, this is the only working method for rooting Lenovo A2010.
...
By the way, besides the files in my first post above, if you are using Windows, you obviously need to have the proper MTK drivers installed too, so that SP Flash Tool can connect to the phone.
If you are a Linux user, see this post http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
Click to expand...
Click to collapse
Thank you very much for your response. My lenovo has an -a at the end. Hope this one will work. I'll try it later. I am just new with android smart phones.
Can I send you a pm anytime when I am having a trouble rooting this phone?
Executable000 said:
My lenovo has an -a at the end.
Click to expand...
Click to collapse
Mine too.
Executable000 said:
Can I send you a pm?
Click to expand...
Click to collapse
Yes.
Thanks. Searching for the proper MTK driver but failed. Where can I find them?
--
Ot. Anyone who also experienced this? Lenovo a2010 has 8gb phone storage. But after applying an update, it became 4.02gb in the file manager. The other 4gb were consumed by the system files.