4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm) - Transformer TF300T Q&A, Help & Troubleshooting

I have posted this thread to hopefully sort some of the confusion around the new 4.2.1 update & the seemingly encrypted custom recoveries (twrp & cwm) in an attempt to stop some people before they brick.
In doing testing of the new 4.2.1 ota update (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader. It will not work with any custom recovery. Twrp will give password prompt and be unable to mount anything but possibly system. Same goes for cwm, minus the password prompt.
After doing a full wipe from twrp 2.4.3.0 and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted - can't mount anything.
I believe the reason why the new 4.2.1 bootloader encrypts custom recoveries or rather seems to encrypt so nothing can be mounted, is as follows:
After reading through some of the posts in the twrp thread with similar issues, it seems that twrp looks for these partitions (data, system, cache, etc) to be in a certain format, ie ext4. However if the format twrp is looking for does not exist (say the ext4 is now ext3) twrp will assume that it is encrypted and will bring up a password prompt and be unable to mount.
To confirm – the testing I have done - flashing just the new 4.2.1 bootloader and nothing else - encrypts the custom recoveries. I believe the new 4.2.1 bootloader is reformatting these partitions to some other format, making twrp & cwm assume that these partitions are now encrypted.
I have posted a method here that has worked for me twice now after a full wipe in twrp (cache, dalvik-cache, factory-reset, system, internal storage & data) and then flashing just the 4.2.1 bootloader & rebooting to find an encrypted recovery. Not sure if this will work for everyone but as I said it has worked for me twice now after unsuccessful 4.2.1 bootloader tests.
I have successfully updated to 4.2.1 and downgraded back to 4.1.1. The way that I reverted back from fully working 4.2.1 to 4.1.1 was I received an ota update notification after the 4.2.1 update to revert back to 4.1.1 (10.4.2.20). I have an unlocked device and that is why I am reluctant to reflash the 4.2.1 update again, in case I am unable to downgrade back to 4.1.1 this time.
If anyone is currently running 4.2.1, could you please let me know what format/ext your partitions are in so I can confirm this theory.
I hope this information is helpful and shows why the custom recoveries seem encrypted.

Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
I also am on 4.2.1 with unlocked bootloader. Of course haven't received and option to revert back by ota but i do have the 4.1.1 firmware downloaded just haven't attempted to apply it as for the so many issues with everyone else jist being safe for the moment. I haven't rooted the device yet but am willing to take a shot at going back to 4.1.1 since i have the unlocked bootloader if you think it may work or is it different since you've only flashed the 4.2.1 bootloader. Like said stock firmware 4.2.1 with unlocked bootloader.
Edit: In should add i have no access to fastboot because no pc at the moment. Thats why been hesitant because if brick then I'm screwed all together. I may just wait till more research done on this or definite fix or root is found.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Before doing bootloader tests I did flash the full 4.2.1 ota update, so I was running android 4.2.1 and then rebooted into fastboot and flashed twrp to find that I could not mount, rebooted and let android system load, had a play around with the new ui and new launcher and then received a notification for a system update, already running the latest update thought what's this, clicked on it and message popped up saying update to downgrade back to 10.4.2.20 (4.1.1) so that's how I got back to 4.1.1
Not sure why I got this ota downgrade being unlocked but I did not receive 4.2.1 update on device, I downloaded the us ota in the threads used that to manually update in order to do a system dump.

If your running 4.2.1 at the moment could you have a look at what format your partitions are in and post results so I can pass this on to custom recovery devs in order to get working custom recovery with 4.2.1

Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
pjc21 said:
If your running 4.2.1 at the moment could you have a look at what format your partitions are in and post results so I can pass this on to custom recovery devs in order to get working custom recovery with 4.2.1
Click to expand...
Click to collapse
Yes i could where would i look though i don't have a custom recovery its's stock let me know. Any thing to help.
Im not a total noob had many androids in the passednjust new to this one actually been out of game for about a year so jb is new to me and learning again with this.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
I typed a command to get file system info looks like it comes up ext4 but here take a look.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

FWIW in this kind of situation, the decrypt prompt from TWRP doesn't mean that the device is actually encrypted. If TWRP can't mount /data then we assume that it is encrypted. This might seem like a bad way to do it, but that's how Android does it (believe me, I've seen the code in AOSP). Anyway, no one in Team Win has a TF300, so if you want a solution you'll have to come by #twrp on freenode and be able to use things like adb in both Android and in TWRP.
I probably won't check this thread again, so posting here isn't a good way to get hold of me.

Mods, can we make this sticky? Lots of folks are trying to flash custom recoveries then root after the 4.2.1 update and it's obviously not possible yet. Could point folks here from all those other threads before we see more bricks?

aerdely said:
I typed a command to get file system info looks like it comes up ext4 but here take a look.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
If you type "mount" into the terminal it should display the system, data & cache.
On 4.1.1 system is ext4, and looks the same on 4.2.1 and this was the only partition I could mount in twrp after update.

Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
Screw this! I'm unlocked on 4.1.1 and will stay that way for now lol. Not taking this crap update.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Is this were I should watch for updates on CWM fix for 4.2.1 on the TF300T?

Well this sucks. I tried TWRP 2.2.05 and 2.5 as well as like 5 flavors of CWM and nothing... does anyone know if there is anything similar for the Tf101 and Tf700? Sometimes they have the same issues. This really sucks as I cannot root... any ideas???

Most likely not. Try using TWRP 4.2.1, look for it for the TF300t. Not sure if CWM is even going to be released anytime soon considering its mainly developed for the TF101.. Cheers. Going to try TWRP myself and see if it works.
PS: If you do try to flash TWRP, make sure you flash the right version as others can potentially brick your device due to the new bootloader (My guess is the same applies to CWM)
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

pjc21 said:
If your running 4.2.1 at the moment could you have a look at what format your partitions are in and post results so I can pass this on to custom recovery devs in order to get working custom recovery with 4.2.1
Click to expand...
Click to collapse
Hello,
I think I am having the same kind of problem.
Nice thing, I can still boot the stock 4.2.1 presumably flashed from stock WW_epad-10_6_1_27_1-UpdateLauncher.zip.
So, with this sequence:
tab start directly to recovery
adb -d reboot-bootloader
select android guy, and start
adb -d shell once I the second ASUS logo
I can now do a:
$ mount
With the following result:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Problem for me is that the tab boots, then reboots after 30 / 40 seconds of inactivity. :-/

le.jhe said:
Hello,
I think I am having the same kind of problem.
Nice thing, I can still boot the stock 4.2.1 presumably flashed from stock WW_epad-10_6_1_27_1-UpdateLauncher.zip.
So, with this sequence:
tab start directly to recovery
adb -d reboot-bootloader
select android guy, and start
adb -d shell once I the second ASUS logo
I can now do a:
$ mount
With the following result:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Problem for me is that the tab boots, then reboots after 30 / 40 seconds of inactivity. :-/
Click to expand...
Click to collapse
Reflash stock ROM!

das chaos said:
Reflash stock ROM!
Click to expand...
Click to collapse
I'm just cautious about my next move. In between, I have reflashed the stock 4.2.1 bootloader and I'm out of the boot loop.
I think that the definitive move to get out of the boot loop was :
fastboot wipe misc
Just after that, the tab was booting back to the OS. The problem is that OS still reboots.
I might try to reflash the stock 4.2.1 , but I'm a bit afraid of not beeing able to install any custom recovery or other rom after that.
Can someone confirm / infirm that when back to stock 4.2.1 (), it is still possible to use a custom recovery (CWM, TWRP,...) ?

le.jhe said:
I'm just cautious about my next move. In between, I have reflashed the stock 4.2.1 bootloader and I'm out of the boot loop.
I think that the definitive move to get out of the boot loop was :
fastboot wipe misc
Just after that, the tab was booting back to the OS. The problem is that OS still reboots.
I might try to reflash the stock 4.2.1 , but I'm a bit afraid of not beeing able to install any custom recovery or other rom after that.
Can someone confirm / infirm that when back to stock 4.2.1 (), it is still possible to use a custom recovery (CWM, TWRP,...) ?
Click to expand...
Click to collapse
When you flash stock ROM you can of course flash custom recovery. Newest TWRP is 2.8.5.0.
First I would try to wipe cache and dalvik and flash a new kernel. If that fails, you can go back to stock.

das chaos said:
When you flash stock ROM you can of course flash custom recovery. Newest TWRP is 2.8.5.0.
First I would try to wipe cache and dalvik and flash a new kernel. If that fails, you can go back to stock.
Click to expand...
Click to collapse
In the meantime, with the bootlop-to-system tab healed itself . It now boots to stock 4.2.1 in a stable way (with /data wiped, but I asked that at some point..). I will try to go with twrp. The stock 4.2.1 recovery is still broken but Start+Vol-down still works. Thank's for the info.

le.jhe said:
In the meantime, with the bootlop-to-system tab healed itself . It now boots to stock 4.2.1 in a stable way (with /data wiped, but I asked that at some point..). I will try to go with twrp. The stock 4.2.1 recovery is still broken but Start+Vol-down still works. Thank's for the info.
Click to expand...
Click to collapse
Stock ROMs don't have a recovery - at least not one we would call so. On power + vol down + vol up there will be shown dead android with rudimentary functions. That's why it is better to flash custom ROM.

Related

Rooting the LG Optimus 2x (P999) Wind Mobile

kk i am very desperate for help
i have been seeking help regarding rooting my optimus 2x for 2 months
heres the story:
i rooted my phone using superoneclick and everything worked out fine
then i flashed MIUI on my phone and it worked fine except the GPS was very slow
then i had flashed a recovery rom to go back to the stock Froyo
then i flashed Cyanogenmod 7.1 and it worked fine
i saw that MIUI had some new updates and that it was much better than Cyanogenmod in my opinion
So i went to ROM Manager and tried to reboot my phone into recovery but nothing happened at all
I've tried every way to boot into recovery but it goes to the stock recovery
I downloaded a root checker and it tells me my device is not rooted
now when i try to use superoneclick i get stuck
can any1 please help me
i've been posting in the superoneclick forum and no1 has been able to help me for 2 months
lol, use NVflash one click and flash CWM, you dont even need root, flash it then flash another rom.
if that doesnt work: factory reset, unroot, then re-root
Help me too!
I know this is going to sound incredibly dumb (and thats because i barley know anything about all of this stuff)
I've been trying to root my LG G2x for a couple days now, but it just wont work.
Ive followed all the steps to use superoneclick to root my device and the program works as far as i can tell. It finishes step 7 and gives me this message: "Killing ADB and restarting as root... enjoy!"
Unfortunately before i can even use my phone more messages start flowing out. I have absolutely no idea what any of it means, but the program and my phone both crash until i hard boot both so i would really appreciate any help!
This is the message i get: "$
$ export TEMPRANDOM=29169;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount -o rw,remount /system
mount: permission denied (are you root?)
END:29169export PS1=""
export TEMPRANDOM=92557;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /system type ext3 (ro,noatime,data=ordered)
/dev/block/mmcblk0p7 on /data type ext3 (rw,relatime,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,nosuid,nodev,noatime,data=ordered)
tmpfs on /mnt/extasec type tmpfs (rw,noatime,mode=755,gid=1000)
/dev/block/mmcblk0p6 on /nvdb type ext3 (rw,nosuid,nodev,relatime,data=ordered)
/dev/block/vold/179:8 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:8 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/sdcard/_ExternalSD type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:17 on /mnt/extsecure/extasec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/_ExternalSD/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
END:92557export PS1=""
"
Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
Sent from my LG-P999 using XDA Premium App
chipis said:
Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
can u tell me exactly what u did? like step by step?
nydmt said:
can u tell me exactly what u did? like step by step?
Click to expand...
Click to collapse
Go to the root thread in my signature and then in that thread there is a link to the One Click Recovery Flasher using NVFlash. That thread is detailed, step by step and even has a link to a video. Not to be a smartass, but if you cannot follow that thread to install recovery on the phone then you should not be flashing roms on your phone. This is basic stuff you need to know and understand first or you are going to royally screw up your phone.

[DEV] Unofficial Clockworkmod recovery for Lenovo Ideapad A1

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.

Tester needed: Porting Guide to boot phone with fried emmc

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

Lenovo A2010 - Rooting / Building CM

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.

Stuck on screen with android and polyhedron spinning

Hi,
I tried flashing CM on my TF700 but failed. Now it's stuck on a screen with an android and a polyhedron spinning in its belly. I can access adb but not fastboot. "adb reboot bootloader" does nothing - it gets stuck there until I ^C it. Rebooting with the volume button just brings me to that screen again (I know how it works, I've done it in the past, but now it's broken). Do I have a very expensive paperweight?
Well, what did you do?
That screen is the stock recovery spinning it's wheels most likely. Did you flash a custom recovery? If so which one?
What bootloader are you running and what exactly did you do to get into this pickle?
You have adb in recovery?? Post a picture of your cmd window with 'adb devices'
I tried following this guide here:
https://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
but I first accidentally tried flashing the zip from an older version of Clockwork Recovery that I had installed, and that gave errors. Then I realised what happened, flashed the newer recovery, and then tried flashing the zip. That was giving some errors about /cache but otherwise seemed to work. Then I rebooted and it was stuck in this state. Some other problem might be that I tried flashing without gapps - didn't want any gapps in my tablet, so I thought that flashing without those would have been fine.
Code:
> adb devices
List of devices attached
015d2d431f201e09 device
I even managed to get into adb shell:
Code:
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
I can dd from /dev/zero into a file on / , but trying to dd anything from/to /dev/block/mmcblk0pX freezes until I reboot the tablet. I even tried to run "fdisk /dev/block/mmcblk0" but that also freezes. For /dev/block/mmcblk1 (my external microSD, I assume), fdisk works.
Ok, try this to kick the tablet back into the bootloader :
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
And then please give up on CWM recovery and CM as rom. They suck and are completely outdated.
Go for any of the Katkiss roms, latest version is Nougatella, and TWRP as recovery.
In between you may want to fastboot flash the stock blob just to get the tablet back to a known and working state, but that's up to you.
Thanks for your suggestion!
Bad news: it didn't work It rebooted to a state where the screen is off, "adb devices" and "fastboot devices" both detect nothing, but "lsusb" detects this:
Code:
Bus 001 Device 051: ID 0955:7030 NVidia Corp. Tegra 3 (recovery mode)
Any other ideas?
Also thanks for your suggestion regarding CWM/CM. As you can probably understand I've been out of touch for a few years (since I got my Fairphone, which comes Google-free), and now that I tried resurrecting the TF700, I went back to what I knew back then.
Sounds as if you killed it. Sorry.
You would have mentioned if you had generated your device specific nvflash blobs at some point to make it brick proof. If you didn't now is too late. RIP

Categories

Resources