Related
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.
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
Those of you who are trying to root the NEC Terrain, I've slapped together an ADB driver from the NEC NE-103T to help you out. Basically, I just modified the INF file. Really, we're supposed to use driver version number NA002 with the Terrain but I could only find NA001. It works though and you can get ADB shell etc. Despite the ADB access, I was unsuccessful at rooting the NEC Terrain with SuperOneClick and Root_with_Restore_by_Bin4ry etc. Hopefully, posting these drivers here will help someone else in cyberspace develop a feasible root method.
Here's what the zip file contains:
Obviously the modified ADB driver for NEC Terrain use
Not sure if this is correct but I also applied the ADB driver to the CDC Serial Driver and Windows didn't have a problem.
Here's what I need:
Root Method
Default Recovery Password - NEC password protected recovery mode. :-/
(Sigh), they weren't kidding when they said this phone was secure! I know this is not going to be a popular phone but dang it, I love blackberry keyboard-style Android phones and I really need a decent rooted phone to replace my aging Motorola Pro/Pro+.
tl;dr - I'm providing the missing drivers for the NEC Terrain. Someone please find a way to root it cause I've tried everything! Also, I'm looking for the default password to use Android Recovery 3e.
Hello, Is there anyway we can have help from other people to root this device?
I have tried with SuperOneclick also and with UnlockRoot and it didn't work.
Let me know. I am willing to do anything to make this work except of course stupid stuff.
Thanks Danik
Good news:
I found an exploit over here that gains a root shell (binary attached).
Bad news:
Unfortunately, even from there, running "mount -o remount,rw /system" fails.
Similarly, since /data is marked nosuid, you can't use any su command you install in there.
So...
I am able to remount / as rw and then drop an su command in /sbin. I also set up busybox in /data/local/tmp/xbin and mounted it over /system/xbin and included a link to /sbin/su in there. Of course, that gets overwritten on reboot but it's simple enough to do all this in a script and seems to be enough to get SuperSU and TiBu to run.
The next step is to figure out how to patch boot.img to disable ro.secure, etc. Extracting it should be easy now that we have root. We just need to find the right partition. There seem to be plenty of tools around for working with these images. Then we need someone brave enough to flash it back and try it.
Good news
This is good news...
One problem now, is that there is A LOT of partitions (+30).. It will take some time to get through them...
But it's a step in the right direction... great work...
/Martin
justDave said:
Good news:
I found an exploit over here that gains a root shell (binary attached).
Bad news:
Unfortunately, even from there, running "mount -o remount,rw /system" fails.
Similarly, since /data is marked nosuid, you can't use any su command you install in there.
So...
I am able to remount / as rw and then drop an su command in /sbin. I also set up busybox in /data/local/tmp/xbin and mounted it over /system/xbin and included a link to /sbin/su in there. Of course, that gets overwritten on reboot but it's simple enough to do all this in a script and seems to be enough to get SuperSU and TiBu to run.
The next step is to figure out how to patch boot.img to disable ro.secure, etc. Extracting it should be easy now that we have root. We just need to find the right partition. There seem to be plenty of tools around for working with these images. Then we need someone brave enough to flash it back and try it.
Click to expand...
Click to collapse
MrMEEE said:
This is good news...
One problem now, is that there is A LOT of partitions (+30).. It will take some time to get through them...
But it's a step in the right direction... great work...
/Martin
Click to expand...
Click to collapse
Look at 9 and 11.
justDave said:
Look at 9 and 11.
Click to expand...
Click to collapse
You are right.. There are some boot stuff (kernel and init's) on parts 9 and 11..
I have changed the ro.secure in the inits.. but I'm not able to reflash the two partitions..
I don't get any errors from dd, but got the following messages in dmesg:
<<mmc_write emmc lock write error 0x00097800 : 11
Besides from that, a lot of I/O errors.. so seems like the phone is EMMC locked as well..
hey folks, I managed to get an unlocked terrain. No joke, really unlocked! I just got it from ebay and I am using it on the Telus network in Canada. If it helps your effort to unlock it, let me know if there is any files or even the rom from this phone that you want to see. I just need instructions. On the side note, IMO, the phone is actually quite decent despite that it's running on slower CPU. It's more than capable of running all the most common apps on the market. My only problem is that the "system storage" only has 787M, while the "phone storage" has 4.34G. I can't install apps directly to the phone storage and that 787M is not enough for my use. It would be nice if I can re-partiion all the space and allocate all 4.5G to system.
Please let me know what I can do to help. Would love to see this phone root as well.
Cheers
MrMEEE said:
You are right.. There are some boot stuff (kernel and init's) on parts 9 and 11..
I have changed the ro.secure in the inits.. but I'm not able to reflash the two partitions..
I don't get any errors from dd, but got the following messages in dmesg:
<<mmc_write emmc lock write error 0x00097800 : 11
Besides from that, a lot of I/O errors.. so seems like the phone is EMMC locked as well..
Click to expand...
Click to collapse
Hey folks, so as I said in my previous post, my Terrain is unlocked, so I am just poking around and see if I can gain root to it. Looks like the ROM that my phone is using is the new one from NEC and maybe that's why it's already unlocked. Anyway, I need some help trying to root it. Looks like it's pretty lock down, I can't even access /data/local to put that run_root_shell in it, and so I put it to /sdcard but no good there neither, it won't let me run there.
[email protected]:/sdcard $ ls -la
ls -la
drwxrwxr-x system sdcard_rw 2014-04-29 23:50 .estrongs
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 Android
drwxrwxr-x system sdcard_rw 2014-04-29 22:58 Download
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 LOST.DIR
drwxrwxr-x system sdcard_rw 1980-01-01 00:00 Notifications
drwxrwxr-x system sdcard_rw 2014-04-29 23:49 backups
-rwxrwxr-x system sdcard_rw 89968 2013-12-06 08:54 run_root_shell
[email protected]:/sdcard $ ./run_root_shell
./run_root_shell
/system/bin/sh: ./run_root_shell: cannot execute - Permission denied
126|[email protected]:/sdcard $
Also, there aren't 30+ partitions anymore....or I could be looking at this wrong.
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 327M 76K 327M 4096
/mnt/asec 327M 0K 327M 4096
/mnt/obb 327M 0K 327M 4096
/system 1G 480M 558M 4096
/data 787M 347M 439M 4096
/persist 7M 4M 3M 4096
/cache 354M 24M 330M 4096
/tombstones 68M 4M 64M 4096
/firmware 127M 39M 88M 16384
/data/camera_socket 327M 0K 327M 4096
/data/secure/data 327M 0K 327M 4096
/mnt/sdcard 4G 3M 4G 32768
[email protected]:/ $
Any idea and help would be appreciated. And let me know if you need me to upload any files from it that can help people here to unlock theirs.
cheers
aluminumx said:
Hey folks, so as I said in my previous post, my Terrain is unlocked, so I am just poking around and see if I can gain root to it. Looks like the ROM that my phone is using is the new one from NEC and maybe that's why it's already unlocked. Anyway, I need some help trying to root it. Looks like it's pretty lock down, I can't even access /data/local to put that run_root_shell in it, and so I put it to /sdcard but no good there neither, it won't let me run there.
Click to expand...
Click to collapse
Same thing here, also unlocked device
Code:
[email protected]:/data/local $ ls
ls
opendir failed, Permission denied
Code:
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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /data/camera_socket tmpfs rw,relatime,mode=775,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,nosuid,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:14 /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
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device works just fine - except for the fact that neither WIFI tethering works nor syncing with Gmail App (although sync works once I connect to a WIFI Hotspot). Has anyone experienced something similar?
Have a look on my postings list or search for El Grande Partition List (if I remember that right ) by @E.V.A. there's tools for reading partition info
Bashing away at my HTC Desire C
Has anyone seen this yet? Do you think we can use it? http://i.imgur.com/TXKDpOI.png
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
I'm not sure how to install these drivers (it's not an executable so I've got no idea ). Where do I copy the files? to the ADB folder?
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.
I am sharing a full stock ROM for SGP BP2 (Blackphone 2) which I got directly from Silent Circle support.
This ROM is not rooted because it's original, would be awesome if someone will be able to root it before i do that
Kernel: 3.10.49-gc6cf2ab
OS: Silent OS 2.0.8 RC4
Based on: Android Lollipop 5.1.1 (r1) and contains some Cyanogenmod files.
AOSP build: LMY47V
AOSP branch: android-5.1.1_r1
Here is a Google Drive folder with ROM files: https://drive.google.com/open?id=0BybUUdJE1dSZeUkxbE8wZUEtcHc
Folder contents:
BP2-OTA-2.0.8-RC4-candidate-ROW-1460729363.zip
This is a full stock ROM for models that contain letters 'RW' in their model name.
Example: BP2H001RW1 - letters "RW" indicate you should use that .zip
RW (ROW) means 'Rest of World'.
build.prop contents: http://paste.debian.net/901606/
BP2-OTA-2.0.8-RC4-candidate-NA-1460729363.zip
This is a full stock ROM for models that contain letters 'NA' and 'AM' in their model name.
Example: BP2H001AM1 - letters "AM" indicate you should use that .zip
NA means 'North America', AM means 'America'; probably the models being sold in that region are slightly different.
build.prop contents: http://paste.debian.net/901680/
boot.img
I've extracted 'boot.img' from the .zip and uploaded aside, in case someone is looking only for kernel and initrd.
boot.img is same in both NA and ROW roms.
recovery.img
It's a stock android recovery image, I've got it with dd after flashing the BP2-OTA-2.0.8-RC4-candidate-ROW-1460729363.zip
md5sum:
Code:
afb4c7a26608d113b1b54da167fc0255 BP2-OTA-2.0.8-RC4-candidate-NA-1460729363.zip
180021957910afc484c76f4a2246c491 BP2-OTA-2.0.8-RC4-candidate-ROW-1460729363.zip
9e42e33b39244e8bfa6f250424c15270 boot.img
9c872f08f69a2b6cad93214c1089b03d recovery.img
sha1sum:
Code:
8164772318414d49389168495f732afb46467c1c BP2-OTA-2.0.8-RC4-candidate-NA-1460729363.zip
14010e518725146a8ebe52caf4723be4c69c3c9a BP2-OTA-2.0.8-RC4-candidate-ROW-1460729363.zip
a9bf9ce0a6f5b31860e228464fd3abbd9f232a57 boot.img
c76ea5c0ca330bf6dc2191d9db0bead1cac6d4c7 recovery.img
Known issues
Device name case mismatch ('bp2' vs 'BP2')
I wasn't able to reflash my device without modifying one file in a .zip
It may give you this error when you start updating:
Code:
This package is for "BP2" devices; this is a "bp2".
In that case you need to:
1) unpack a .zip file
2) find the file updater-script in the META-INF/com/google/android/ folder, which looks like:
PHP:
get_device_compatible("BP2") == "OK" || abort("This package is for \"BP2\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
3) change the letters 'BP2' to 'bp2', so the first line will look like this:
PHP:
get_device_compatible("bp2") == "OK" || abort("This package is for \"BP2\" devices; this is a \"" + getprop("ro.product.device") + "\".");
4) Pack everything back into a .zip file
5) Apply the update using a new .zip file using stock recovery.
System image format
If you have a TWRP recovery instead of stock, you won't be able to flash the ROM from .zip (for some unknown reason it just doesn't flash a system partition)
You will need to extract the ROM .zip and use sdat2img tool to convert lollipop's system.new.dat format to system.img (raw format), after that you can flash system.img directly using TWRP or dd.
Follow this manual for Linux: http://forum.xda-developers.com/showpost.php?p=57635842&postcount=2
For Windows: http://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Alternatively, you can flash stock recovery.img that I listed above, boot it and flash .zip from it directly.
Mounting /system with read-write using TWRP causes a bootloop
Thread: http://forum.xda-developers.com/android/help/blackphone-2-bootloop-rw-mount-using-t3516862
Security vulnerabilities
This ROM is vulnerable for these attacks according to QuadRooter Scanner:
CVE-2016-2059 - "QuadRooter"
CVE-2016-2504 - Elevation of privilege vulnerability in Qualcomm GPU driver
You may need to upgrade to the latest Silent OS version using OTA updater in order to mitigate these.
On the other hand, you may root your device using one of these vulns before upgrading, whether there is a root method that using QuadRooter exploit (I believe there will be one soon).
Oh c'mon Silent Circle, you made it annoying, just let us use root privileges peacefully, we are aware of damn risks!
Useful information
/proc/mounts
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1481408k,nr_inodes=182626,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 /var tmpfs rw,seclabel,relatime,size=1481408k,nr_inodes=182626,mode=770,gid=1000 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1481408k,nr_inodes=182626,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1481408k,nr_inodes=182626,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1481408k,nr_inodes=182626,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/dm-0 /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=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
/dev/block/dm-1 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 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 /mnt/shell/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/proc/partitions
Code:
major minor #blocks name
179 0 30539776 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1 mmcblk0p15
179 16 8 mmcblk0p16
179 17 10240 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 32 mmcblk0p20
179 21 65536 mmcblk0p21
179 22 1536 mmcblk0p22
179 23 16 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 1966080 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 917504 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 512 mmcblk0p30
179 31 512 mmcblk0p31
259 0 32 mmcblk0p32
259 1 27162575 mmcblk0p33
179 32 4096 mmcblk0rpmb
179 64 3855360 mmcblk1
179 65 3851264 mmcblk1p1
254 0 1950564 dm-0
254 1 27162575 dm-1
This is great
drivers for blackphone 2
I recently purchased a blackphone2. IT had TWRP recovery installed and some version of lollypop and the phone was not rooted. I tried to install the stock rom which the silent circle supplied. But while flashing through TWRP it always generated error 6 or 7. I even tried OS 1 and 2 all gave the same error. Then I saw the info from your thread. I flashed the stock recovery and was successful in flashing it however the stock rom installation always get stuck at "patching system image unconditionally". One more thing my blackphone is not recognized by any PC. May be I do not have the drivers. I think I had to flash the boot.image file also which I missed . Now stuck in the stock recovery how can I flash the boot image file, whereas I dont have the usb drivers also. Please help.
mansoor
cmegmhi said:
[...]
I flashed the stock recovery and was successful in flashing it however the stock rom installation always get stuck at "patching system image unconditionally".
Click to expand...
Click to collapse
A "patching system image unconditionally" step may take some time because it's extracting a big image.
Can you try flashing one of .zip's from the google folder I published in this thread using a stock recovery?
Also, make sure you do "wipe data/factory reset" and "wipe cache partition" before flashing the .zip
Also, you can use a 'reboot to bootloader' option and boot or flash any image using fastboot
In order to get your phone recognized via USB, you need adb and fastboot installed on your computer and the appropriate drivers, search this forum to get HOW-TO's on that, there are many.
polartux said:
A "patching system image unconditionally" step may take some time because it's extracting a big image.
Can you try flashing one of .zip's from the google folder I published in this thread using a stock recovery?
Also, make sure you do "wipe data/factory reset" and "wipe cache partition" before flashing the .zip
Also, you can use a 'reboot to bootloader' option and boot or flash any image using fastboot
In order to get your phone recognized via USB, you need adb and fastboot installed on your computer and the appropriate drivers, search this forum to get HOW-TO's on that, there are many.
Click to expand...
Click to collapse
I have flashed the boot image as well as the recovery image from the above mentioned links. However from the recovery as I said earlier system flashing using the zip file does not complete and stuck for ever. I can boot to bootloader through recovery but how to flash the image file of rom as I have the zip file. How can I convert the zip file to image file. Any idea
A bundle of thanks for the help
cmegmhi said:
I have flashed the boot image as well as the recovery image from the above mentioned links. However from the recovery as I said earlier system flashing using the zip file does not complete and stuck for ever. I can boot to bootloader through recovery but how to flash the image file of rom as I have the zip file. How can I convert the zip file to image file. Any idea
A bundle of thanks for the help
Click to expand...
Click to collapse
The ROM posted above occupies more than 1.7 GB in the system partition, whereas the system partition I got on my phone is around 1.48 GB. Could this be the reason for the phone to get stuck during the rom installation "patching the system image unconditionally". If so the way out could be the resizing of the system partition. Based on this idea I have been looking around on the internet for a system resizing app for blackphone 2 without any success. Please guide me in this matter
Thanks in advance
How to Verifty Which One is letters "RW" Or 'NA' and 'AM'
I have unlocked bootloader and phone in bootloop no way to rescue it? bootloader and recovery works)
I have twrp and unlocked bootloader
how I do this? "sdat2img tool to convert lollipop's system.new.dat format to system.img"
How to root this phone and remove google apps? Many thanks
You probably should just flash a new rom and start over?
Silent OS 3.0.8 update disables cellular network in Blackphone 2 (unlicensed device)
Blackphone 2 not bought from Silent Circle or an approved vendor of Silent Circle will become an unlicensed device
after installation of Silent OS 3.0.8.
I bought my phone from coolicool.com. Cellular network connections didn't work after the update.
I contacted Silent Circle's support but they didn't want to help me because the phone was bought from
a non-approved vendor.
This Android 5.1.1 ROM re-enabled the cellular connectivity in my phone. Thank you!
Silent Circle will become an unlicensed device
I'm in the same case as you. At least I have a phone again, although the version of android is older.
Thanks!!!
akikoo said:
Blackphone 2 not bought from Silent Circle or an approved vendor of Silent Circle will become an unlicensed device
after installation of Silent OS 3.0.8.
I bought my phone from coolicool.com. Cellular network connections didn't work after the update.
I contacted Silent Circle's support but they didn't want to help me because the phone was bought from
a non-approved vendor.
This Android 5.1.1 ROM re-enabled the cellular connectivity in my phone. Thank you!
Click to expand...
Click to collapse
akikoo said:
Blackphone 2 not bought from Silent Circle or an approved vendor of Silent Circle will become an unlicensed device
after installation of Silent OS 3.0.8.
I bought my phone from coolicool.com. Cellular network connections didn't work after the update.
I contacted Silent Circle's support but they didn't want to help me because the phone was bought from
a non-approved vendor.
This Android 5.1.1 ROM re-enabled the cellular connectivity in my phone. Thank you!
Click to expand...
Click to collapse
Yeah me too, bought from an online store in Malaysia. Not only they disabled the SIM module, also ALL GOOGLE SERVICES as well..
This sucks so bad....
Silent Circle support's reply
Here's the reply I got from Silent Circle's support. I sent them the serial number and IMEI of the phone.
Like the online shop would be able to do anything for the f*cking OTA update...
------------------------------------------------------------------------------------------------------------------------------------------
Hello,
Upon review of the IMEI number (XXXXXXXXXXXXXXX) you provided, it has been determined this device
is not a genuine Silent Circle Blackphone2. This device was not sold by Silent Circle or
an approved vendor of Silent Circle and therefore we are unable to provide any further assistance.
We recommend you contact the original vendor directly for further assistance.
To purchase a Silent Circle genuine device please visit the following URL:
Sincerely,
Silent Circle Technical Support
------------------------------------------------------------------------------------------------------------------------------------------
Hello, I bought this phone from myefox and I'm waiting. So if I followed the upgrade I lose all network functionality ?. Or the phone can still work?
bastard81 said:
Hello, I bought this phone from myefox and I'm waiting. So if I followed the upgrade I lose all network functionality ?. Or the phone can still work?
Click to expand...
Click to collapse
When I first received the phone, OTA upgraded the phone to Silent OS 3.0.7, everything works fine.
Just don't go to 3.0.8
---------- Post added at 01:52 PM ---------- Previous post was at 01:27 PM ----------
akikoo said:
Here's the reply I got from Silent Circle's support. I sent them the serial number and IMEI of the phone.
Like the online shop would be able to do anything for the f*cking OTA update...
------------------------------------------------------------------------------------------------------------------------------------------
Hello,
Upon review of the IMEI number (XXXXXXXXXXXXXXX) you provided, it has been determined this device
is not a genuine Silent Circle Blackphone2. This device was not sold by Silent Circle or
an approved vendor of Silent Circle and therefore we are unable to provide any further assistance.
We recommend you contact the original vendor directly for further assistance.
To purchase a Silent Circle genuine device please visit the following URL:
Sincerely,
Silent Circle Technical Support
------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
It's kinda sad and frustrating that this kind of attitude exist, I mean, c'mon.. How can you say it's not genuine???
It's obviously GENUINE SILENT CIRCLE BLACK PHONE 2! It's just that it someone else got their hands on the stock and sell it!
PLUS, I bet Silent Circle themself leaked out the so-called "unlicensed" devices to test the market.
That explains why there weren't any "license checking" prior to version 3.0.8!!
Good thing there's the stock ROM, and I bought the phone cheap around USD 130.
Any idiot would know! how can an original blackphone listed on their SC's website at $600 still, be sold at $130? furthermore, this is through chinese website, sending you from china.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
Btw, coolicool and efox. they are the same owner from china!
...
...
akikoo said:
Blackphone 2 not bought from Silent Circle or an approved vendor of Silent Circle will become an unlicensed device
after installation of Silent OS 3.0.8.
I bought my phone from coolicool.com. Cellular network connections didn't work after the update.
I contacted Silent Circle's support but they didn't want to help me because the phone was bought from
a non-approved vendor.
This Android 5.1.1 ROM re-enabled the cellular connectivity in my phone. Thank you!
Click to expand...
Click to collapse
That's what i went so... I bought my phone from antelife.com.
How to install this ROM? Someone please describe step by step! Thanks!
How to install the Android 5.1 update rom from this thread
kovikee said:
That's what i went so... I bought my phone from antelife.com.
How to install this ROM? Someone please describe step by step! Thanks!
Click to expand...
Click to collapse
Copy the zip file BP2-OTA-2.0.8-RC4-candidate-ROW-1460729363.zip from the first post to your sd card. I renamed it to update.zip.
Power off your phone.
Put the sd card into the sd card/sim card tray.
Press volume up and power button until your phone turns on. Keep the volume up button pressed down until you land in the recovery menu. From there you can select the menu entry that says something like apply update from sd card.