Related
Hello XDA-Developers!
I want to install Back Track 5 ARM in my AllWinner A10 based tablet, I followed the lesson for Galaxy and I downloaded the boot script for Galaxy and the bt5.img(3.25G). I changed some of the codes to launch BT5 in external sdcard and suit my ROM,then launched it, only to find some errors. Well, the source code of the boot script(modified by myself to suit my device) like this:
perm=$(id|busybox cut -b 5)
if [ "$perm" != "0" ];then echo "This Script Needs Root! Type : su";exit;fi
mount -o remount,rw /dev/block/mmcblk0p1 /system
export kit=/mnt/extsd/BT5
export bin=/system/bin
export mnt=/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/
if [ -b /dev/loop2 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop2 b 7 0
fi
busybox mount -o loop,noatime -t extsd $kit/bt5.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $/etc/hosts
busybox chroot $/bin/bash
echo "Shutting down BackTrack ARM For Xoom"
umount $/dev/pts
umount $/proc
umount $/sys
umount $mnt
when I launch the script(bootbtV) in Terminal Emulator, only to find some errors like this:
[email protected]:/ $ su
[email protected]:/ # cd mnt/extsd/BT5
[email protected]:/mnt/extsd/BT5 # sh bootbtV
Loop device exists
mount: mounting /dev/loop8 on /mnt failed: No such device
mount: mounting /dev/pts on /mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /mnt/proc failed: No such file or directory
mount: mounting /sys on /mnt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
bootbtV[23]: can't create $/etc/resolv.conf: No such file or directory
bootbtV[24]: can't create $/etc/hosts: No such file or directory
chroot: can't change root directory to $/bin/bash: No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/mnt/extsd/BT5 #
Well, In my opinion, according to the errors "No such file or directory", I think it is the difference between my device and Galaxy that causes the errors. In my device, the file structure is different from what the boot script means, such is the file structure of my device's root directory:
drwxr-xr-x root root 2013-01-16 11:22 acct
drwxrwx--- system cache 2013-01-16 09:51 cache
dr-x------ root root 2013-01-16 11:22 config
lrwxrwxrwx root root 2013-01-16 11:22 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-13 17:14 data
-rw-r--r-- root root 116 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-01-16 11:27 dev
lrwxrwxrwx root root 2013-01-16 11:22 etc -> /system/etc
-rwxr-x--- root root 105268 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 19030 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2644 1970-01-01 08:00 init.sun4i.rc
-rwxr-x--- root root 2230 1970-01-01 08:00 init.sun4i.usb.rc
-rwxr-x--- root root 1637 1970-01-01 08:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 08:00 init.usb.rc
-rwxr-x--- root root 1536000 1970-01-01 08:00 initlogo.rle
drwxrwxr-x root system 2013-01-16 11:22 mnt
-rw-r--r-- root root 782728 1970-01-01 08:00 nand.ko
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwx------ root root 2012-10-11 13:57 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-01-16 11:22 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-16 11:22 sys
drwxr-xr-x root root 2013-01-13 17:59 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 3879 1970-01-01 08:00 ueventd.rc
-rw-r--r-- root root 1313 1970-01-01 08:00 ueventd.sun4i.rc
lrwxrwxrwx root root 2013-01-16 11:22 vendor -> /system/vendor
I think, the only way to launch BT5 in my device successfully is to modify the boot script so that it can suit my device, especially the file structure. But I am a green hand in Linux, I don't know what does some of the codes mean, if you are good at Linux script, would you please give me some advice?
Thank you very much!
So normally, nexus devices have easy partition names... For example, the /dev/block/platform/by-name directory contains things like system, boot, recovery, data, modem, efs, etc.. Well here is the result of "ls -al" of the partition directory on my nexus 9.
[email protected]_lte:/ # ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-12-30 12:10 APP -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2014-12-30 12:10 CAC -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2014-12-30 12:10 CDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-12-30 12:10 DIA -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-30 12:10 DTB -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-30 12:10 EF1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-30 12:10 EF2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-12-30 12:10 EKS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-30 12:10 EXT -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-30 12:10 FST -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-30 12:10 GPT -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2014-12-30 12:10 KEY -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-30 12:10 LNX -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-30 12:10 MD1 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-12-30 12:10 MD2 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-12-30 12:10 MFG -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-12-30 12:10 MSC -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-30 12:10 NCT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-30 12:10 OTA -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2014-12-30 12:10 PG1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-30 12:10 PST -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2014-12-30 12:10 RCA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-30 12:10 RV1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-30 12:10 RV2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-30 12:10 RV3 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2014-12-30 12:10 SER -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-30 12:10 SOS -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-30 12:10 SP1 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-30 12:10 TOS -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-30 12:10 UDA -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2014-12-30 12:10 VNR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-12-30 12:10 WB0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-30 12:10 WDM -> /dev/block/mmcblk0p7
My question is, which is which? How can i tell which is the recovery block, system block, recovery and so on? Is there a list of translations for these partition names? Thanks
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
peterk-1 said:
Not sure what need you are trying to fulfill but read this http://www.all-things-android.com/content/review-android-partition-layout as a starter.
Click to expand...
Click to collapse
For example, nexus 5 has a symlinks like /dev/block/platform/msm_sdcc.1/by-name/boot that is linked to /dev/block/mmcblk0p19. Clearly this is the kernel block. Because its called "boot". Right? So, the nexus 9 is different from most other nexus devices. The by-name folder has 3 character names that dont really translate to "boot" or "system" or "recovery". It has names like "dia" and "vnr". I know that the "vnr" is the Vendor block. So which one is the "boot" block, is it "dia", or is it"svn". Do you understand what im asking? How in the heck is one supposed to figure out which block device is which???
bynarie said:
How in the heck is one supposed to figure out which block device is which???
Click to expand...
Click to collapse
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
thanks!
peterk-1 said:
The "clever ****" reply is "google" but I've found that many pages go silent on the key issue and and others are way over my head.
Some pointers:
Reboot your device and look at the dmesg log and :
Search "target=" (6 hits in 1 file)
\\CORSAIR\CorsairG\junk\dmesg.txt (6 hits)
Line 1077: <14>[ 5.168004] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/APP,target=/system,type=ext4)=0
Line 1080: <14>[ 5.172727] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/VNR,target=/vendor,type=ext4)=0
Line 1114: <14>[ 5.507472] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/CAC,target=/cache,type=ext4)=0
Line 1127: <14>[ 5.527126] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=f2fs)=-1
Line 1145: <14>[ 5.550663] fs_mgr: __mount(source=/dev/block/platform/sdhci-tegra.3/by-name/UDA,target=/data,type=ext4)=-1
Line 1488: <14>[ 111.676664] fs_mgr: __mount(source=/dev/block/dm-0,target=/data,type=f2fs)=0
http://newandroidbook.com/Articles/Nexus9.html - note "tegra" names and Nvidia Shield.
https://android.googlesource.com/device/htc/flounder/+/android-5.0.2_r1/fstab.flounder
Click to expand...
Click to collapse
Thanks!! That fstab flounder page is a really good starting list of exactly what i was looking for. {{Presses Thanks Button}}
Is it possible to delete some partitions like system image and resize data partition?
wizzardsk said:
Is it possible to delete some partitions like system image and resize data partition?
Click to expand...
Click to collapse
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Vartom said:
No, system image system is a partition with android system. Other partitions are too small for redesigning to make sense.
Click to expand...
Click to collapse
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
wizzardsk said:
I am not sure about the name, but there are 2 system partitions on nexus 9 that i have not seen on other devices.
Click to expand...
Click to collapse
you are mistaken, he has one system partitions (APP).
What is this?
wizzardsk said:
What is this?
Click to expand...
Click to collapse
Same thing. One is a regular backup, one is to backup as an image (system.img) pick the way you want to backup.
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
wizzardsk said:
So both system partitions are necessary?
Edit: i understand, so there is only 1 system partition
Click to expand...
Click to collapse
Yes there is only 1 system partition. TWRP is offering 2 ways to make a system backup, either a standard backup, or backup as an image.
This partition apparently holds the IMEI (well on the Moto G 2013 it does) but I don't even see that it exists on this phone (xt1527). I can't seem to make a backup of it but the phone works so, is it even there or have they changed how it works?
bump, same issue
seems a bunch of us have this issue.
sad there seems to be no answer anywhere..
edit:
here is what i got listing partitions.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]_umts:/ $ su
[email protected]_umts:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-06-10 11:47 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-06-10 11:47 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-06-10 11:47 abootBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-06-10 11:47 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-06-10 11:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-06-10 11:47 carrier -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-06-10 11:47 cid -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-06-10 11:47 clogo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-06-10 11:47 dhob -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-06-10 11:47 factorytune1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-06-10 11:47 factorytune2 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-06-10 11:47 frp -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-06-10 11:47 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-06-10 11:47 fsg -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-06-10 11:47 hob -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-06-10 11:47 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-06-10 11:47 hypBackup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-06-10 11:47 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-06-10 11:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-06-10 11:47 logo -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-06-10 11:47 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-06-10 11:47 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-06-10 11:47 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-06-10 11:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-06-10 11:47 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-06-10 11:47 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-06-10 11:47 oem -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-06-10 11:47 padA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-06-10 11:47 padB -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-06-10 11:47 padC -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-06-10 11:47 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-06-10 11:47 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-06-10 11:47 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-06-10 11:47 rpmBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-06-10 11:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-06-10 11:47 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-06-10 11:47 sp -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-06-10 11:47 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-06-10 11:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-06-10 11:47 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-06-10 11:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-06-10 11:47 userdata -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-06-10 11:47 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-06-10 11:47 utagsBackup -> /dev/block/mmcblk0p17
[email protected]_umts:/ #
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
conductive said:
Not up to speed on this device yet but it seems to me that if you know where the PDS partition is from a terminal you should be able to use a form like:
dd if=/dev/block/mmcblk??? of=pds.img
provided your current working directory has enough room in it to hold the .img file
Click to expand...
Click to collapse
on another phone it's mmcblk12 (i have been doing a LOT of searching on this)
i looked at the root folder on my phone and i see a shortcut to "pds"
when i open it it's empty.
i have some experience with Linux but i am no pro and it's been a while for my nix activity.
and i have almost no experience with Android.
i am good with computer stuff though. cracking, coding reversing, graphics etc.
i love modding everything i can.
i say that to give a bit of context to this..
if anyone else has any idea or leads on what i can do or where to look i am all ears.
i posted that partition command because i found it on Google
and i remember using it (ls) before trouble shooting driver issues on Linux in the past.
you guys will notice the console log i posted does not list a pds partition by-name..
is it because it's not mounted maybe ? or is it using a different name on this phone ?
i'd love to try and update to 5.1 (from 5.0..2) on my Telus XT1527 but i think it's time i make a PDS backup before i carry on any further.. so far i have installed a custom kernel and TWRP + root.
So i can't continue until i figure out a way to back that stuff up (irresponsible otherwise i think)
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
conductive said:
Based on this post http://forum.xda-developers.com/showthread.php?t=1138220 the OS uses /dev/block/mmcblk0p3 and it was dumped to the /tmp directory.
from here you can use dd to flash it to an sd card where you can read it to see if it has pds information. You can also use (mount -a) to mount all partitions and do another ls -l
Click to expand...
Click to collapse
That says Atrix though and on another posting i found it was mmcblk0p12
If you look at the log i posted earlier that number mmcblk0p3 is mapped to DDR
I have been dumping the partitions and checking them (if the file size is roughly correct)
I heard it was suppose to be about 8mb as an .img on another device.
and i have one downloaded as an image and extracted (some other guys data)
so if i find the files on my phone i think i can match them to my downloaded files.
i also got a windows tool to extract the images ready..
One last thing i said i seen a shortcut to "pds" on the filesystem of my Telus XT1527
so i take it that it's there just that i can't see it or something.
I'm basically poking around in the dark LOL
edit:
oh and i seen on other phones that pds partition can be backed up with TWRP.
The TWRP i have installed does not show it for me (i am using Squid's TWRP)
The partitions are probably associated with the OS version and not the hardware so you should probably compare your version to a similar version.
If you can find fstab file you should be able to (cat fstab) and see what the partitions are mounted as.
The partition should be mounted or else your device will not work.
I've modded fstab on linux before but i am not finding it i think on the XT1527
found a couple with "fstab" in the title and it don't say much..
just one line about mounting the sdcard.
Thanks but i am lost.. i wonder how it's created because it's prob not files in the Firmware package right ?
So then i'd have to assume the contents of PDS would be created on the phones first boot maybe.
i don't know what else to do really i am going around in circles ..i might just say screw it and give up.
too bad guys here who DO have the ability to find it can't help
100% of Moto-E users seem to carry on flashing their phones with out it
so i take it backing up the PDS is pointless ?
Just kind of dumb i see tutorials on how to do it all over but no one can claim it actually works LOL
If you google it you will see what i am saying (people tell you to you to do it becuase it's sooooo important..
then it doesn't work ahahaha
thanks for your help conductive.
edit:
Oh and guys.. i tried to do this because... Q13:
http://forum.xda-developers.com/moto-e-2015/help/faq-frequently-questions-moto-e-2015-t3044929
The stickied topic here tells us all how to do it.
..but did anyone at all bother to verify it actually works ?
Ok so i think i got it.. sort of.
I installed "Root Explorer Pro" and when i opened it this time it showed files/folders.
I then selected .zip it up and copied it manually to my sdcard then to my PC.
I have been hex viewing the contents with UltraEdit and the files contain data.
I also compared to a pds dump from an Atrix and they are some what similar.
I did see a reference in one of the root config files about the pds partition though..
I can't recall which file it was but it said something about
setting the dummy directory "pds" as persistent.
I don't know what is going on but i got the content off the phone i think.
edit:
Here is what the root of that folder looked like (folder names)
Code:
.bt_nv.bin
batt_health
bt
camera
data
factory
lost+found
public
security
WCNSS_wlan_dictionary.dat
wifi
wmdrm
This is my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the phone I just bought for my mother:
Bought less than a week from each other. Same phone, different android versions- mine Android 4.4.4 and hers is Android 5.1.
How can I upgrade mine to 5.1? Upgrade button in the settings menu returns the server is unreachable.
bump
bump
BUMP
Do you have a data connection on your phone (mobile data or WiFi)? Same carrier?
augie7107 said:
Do you have a data connection on your phone (mobile data or WiFi)? Same carrier?
Click to expand...
Click to collapse
Yes. Everything is the same.
Both purchased at Walmart.
Both on Straight Talk.
Both used Mobile and WiFi without any problems.
BUMP
Bump
There is no way to update via pc. Look up ZTE USA service number and give them a call. They will connect you with tech support to get it sorted.
Did you ever get this sorted out? I just bought the same phone and it came with 4.4.4. Called ZTE and they said there's no update for this phone yet
Ive got a zte z936l I can obtain a temp root on it with king root but I think its unstabe can't seem to flash a custom
If you want to root this phone, you need to obtain temp root and dump your entire ROM to a safe place, like a computer. Then SWAP boot and recovery. And boot the ROM via recovery buttons. This will give you full root but when youre done using it you newd to switch boot and recovery back. ZTE is known for their system lockdown and this way circumvents it. If you can obtain the 5.1.1 bootstack from your moms phone via temp root and using dd commands to dump we can ALL have 5.1. All we will need is a twrp build.
bichofelix said:
If you want to root this phone, you need to obtain temp root and dump your entire ROM to a safe place, like a computer. Then SWAP boot and recovery. And boot the ROM via recovery buttons. This will give you full root but when youre done using it you newd to switch boot and recovery back. ZTE is known for their system lockdown and this way circumvents it. If you can obtain the 5.1.1 bootstack from your moms phone via temp root and using dd commands to dump we can ALL have 5.1. All we will need is a twrp build.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63578570&postcount=11
I seen this above post. Full root can be gained if instructions are followed. Can you confirm this? I may just email them and pit in the request for both of the zte lever phones here in the house.
As for following your instructions, I'd have no issue doing as you say and providing 5.1 for xda. I'd prefer some more detailed instructions and possibly a irc/messaging platform for instant communication.
After temp root, open terminal and dump everything in "dev/block/bootdevice/by-name/" with dd commands onto your sdcard or PC. (dd if=/path/to/partition of=/dump/location/filename)
From there we decompile the candidates for boot and recovery and once we know which is which, they can be swapped. Then you reboot and obtain temp root again, which this time it should give you full root. When you're done using it, just swap them back and reboot.
I'm not sure about that guy saying you can just unlock bootloader because even with twrp the system will have ro lock on it unless boot and recovery are swapped. Look at the zmax if you're curious how it works.
bichofelix said:
After temp root, open terminal and dump everything in "dev/block/bootdevice/by-name/" with dd commands onto your sdcard or PC. (dd if=/path/to/partition of=/dump/location/filename)
From there we decompile the candidates for boot and recovery and once we know which is which, they can be swapped. Then you reboot and obtain temp root again, which this time it should give you full root. When you're done using it, just swap them back and reboot.
I'm not sure about that guy saying you can just unlock bootloader because even with twrp the system will have ro lock on it unless boot and recovery are swapped. Look at the zmax if you're curious how it works.
Click to expand...
Click to collapse
ZMAX?
I am installing ADB now and will follow these instructions the best I can.
Team Win Recovery Project (TWRP), they do not show my device so which one is it that I need? That link I posted about root and boot loader codes, he shows 2.8.70 and the closest device I see is the ZTE Blade.
The fella you replied to said he could get temp root with king root.
bichofelix said:
After temp root, open terminal and dump everything in "dev/block/bootdevice/by-name/" with dd commands onto your sdcard or PC. (dd if=/path/to/partition of=/dump/location/filename)
Click to expand...
Click to collapse
I have done it.
Now to do the rest. I am not sure what file types I should name them all though.
Humphrey1989 said:
I have done it.
Now to do the rest. I am not sure what file types I should name them all though.
Click to expand...
Click to collapse
They are all .img files except a few. You may simply leave them blank.
As for twrp, somebody has to actually build it for our device. We currently have none.
Once the partitions are all dumped, please zip them and link me.
There should also be a fastboot mode we have access to, if we do, we can all simply flash the lollipop bootstack.
bichofelix said:
There should also be a fastboot mode we have access to, if we do, we can all simply flash the lollipop bootstack.
Click to expand...
Click to collapse
I tried >fastboot devices and it didn't show any.
I have restarted my phone once or twice after kingroot and it seems that I have perm root if I read the below right.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # su
/system/bin/sh: su: not found
127|[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:shell:s0
[email protected]:/ #
This is what I have and while be making copies of:
Code:
[email protected]:/dev/block/bootdevice/by-name # ls -l
lrwxrwxrwx root root 1970-04-01 08:25 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-01 08:25 aboot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-01 08:25 abootbak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-01 08:25 boot -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-01 08:25 cache -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-04-01 08:25 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-01 08:25 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-01 08:25 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-01 08:25 hyp -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-01 08:25 hypbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-01 08:25 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-01 08:25 misc -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-01 08:25 modem -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-01 08:25 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-01 08:25 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-01 08:25 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-04-01 08:25 pad -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-01 08:25 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-01 08:25 recovery -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-01 08:25 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-01 08:25 rpmbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-01 08:25 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-01 08:25 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-01 08:25 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-01 08:25 splash -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-01 08:25 ssd -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-01 08:25 system -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-04-01 08:25 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-01 08:25 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-01 08:25 userdata -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-04-01 08:25 ztecfg -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-01 08:25 ztelk -> /dev/block/mmcblk0p11
[email protected]:/dev/block/bootdevice/by-name #
Humphrey1989 said:
I tried >fastboot devices and it didn't show any.
I have restarted my phone once or twice after kingroot and it seems that I have perm root if I read the below right.
This is what I have and while be making copies of:
Click to expand...
Click to collapse
Oh **** yeah they're named. Zte has been known to only use /by-num/.
For fastboot to work you will need the fastboot drivers installed. Not sure if it uses the standard fastboot drivers or its own so Google might help. Try the ones in the zmax forum. You're the guy with lollipop, right?
bichofelix said:
You're the guy with lollipop, right?
Click to expand...
Click to collapse
lollipop? As in Android 5.1 on a ZTE LEVER LTE? Yes I am that guy. Right now I am doing all this on my phone which is 4.4.4 and then I will perform the same on the 5.1 ZTE LEVER LTE.
STOCK FIRMWARE FOR E2303 FLASHABLE ZIP
UPDATE: Uploading because this time IT WORK! Thanks to @TheVektor for updater-script! But this isn't pre-rooted, because it not flash SuperSU. But it's still awesome because if you have problems with flashmode or other you can flash this as a recovery zip! Tested on E2303 with TWRP. Made with PRFCreator
alby_var said:
STOCK PRE-ROOTED FIRMWARE FOR E2303 FLASHABLE ZIP
Hey guys! I had a problem entering flashmode and the only way for unbrick my phone was enter into recovery/flash a zip or fastboot flash.
For this, i made a pre-rooted firmware with PRFcreator. Now I am testing it. It will not install a recovery because xzdualrecovery is not compatible with our device. That means you have to flash it manually before start installing this.
STATUS: RECOVERY NOT INSTALL ZIP FILE....
Download: testing and uploading...
Click to expand...
Click to collapse
Hey! I'm interested in this ROM, my device has a locked bootloader and I think this would solve out the issue of rooting without unlocking the bootloader. I can test the ROM. My model is: E2306
Do you have any finished projects?
Quien mucho abarca poco aprieta
rascayus said:
Quien mucho abarca poco aprieta
Click to expand...
Click to collapse
English please
Don'te bite more than you can chew
I think every thread you have created is pointless. "Uploading"... yeah great.
Maybe get something uploaded first, then create a thread instead of having multiple threads that are pointless...
I respect your efforts but still
Guys, the rom are completed, the problem is that we haven't a working updater-script file. It is needed for flash roms, and I am working to make one that work. I can upload the rom and give you the link, but if it not flash, where is the sense in that?
Code:
if
run_program("/tmp/busybox", "ls", "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896") != "0"
then
abort("Error: UUID link to system partition does not exist");
endif;
assert(package_extract_file("system.ext4", "/dev/block/platform/msm_sdcc.1/by-uuid/F9CDF7BA-B834-A72A-F1C9-D6E0C0983896"));
M4 Aqua (E2303) does not have "msm_sdcc.1" and "by-uuid" folders or whatever is it....
We have MMC device partitions:
Code:
lrwxrwxrwx root root 1970-02-06 11:48 DDR -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-02-06 11:48 FOTAKernel -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-02-06 11:48 LTALabel -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-02-06 11:48 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-02-06 11:48 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-02-06 11:48 alt_aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-02-06 11:48 alt_hyp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-02-06 11:48 alt_rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-02-06 11:48 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-02-06 11:48 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-02-06 11:48 alt_tz -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-02-06 11:48 apps_log -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-02-06 11:48 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-02-06 11:48 cache -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-02-06 11:48 config -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-02-06 11:48 fsg -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-02-06 11:48 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-02-06 11:48 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-02-06 11:48 modemst1 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-02-06 11:48 modemst2 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-02-06 11:48 oem -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-02-06 11:48 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-02-06 11:48 rdimage -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-02-06 11:48 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-02-06 11:48 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-02-06 11:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-02-06 11:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-02-06 11:48 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-02-06 11:48 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-02-06 11:48 userdata -> /dev/block/mmcblk0p29
So we need create updater-script using similar formats:
Code:
run_program("/tmp/busybox", "ls", "/dev/block/mmcblk0p30") != "0"
AND
assert(package_extract_file("system.ext4", "/dev/block/mmcblk0p30"));
Im not 100% sure this is the problem, but i hope it can help for you.
Edit:
OK! zip flashing finished (system flashed!), but supersu not installed by updater-script... idk why.
My updater-script: http://pastebin.com/8Lg7UseV
Ohh! Really Really Really thank you!! Now i can unbrick my phone and finally complete the roms!
alby_var said:
STOCK FIRMWARE FOR E2303 FLASHABLE ZIP
UPDATE: Uploading because this time IT WORK! Thanks to @TheVektor for updater-script! But this isn't pre-rooted, because it not flash SuperSU. But it's still awesome because if you have problems with flashmode or other you can flash this as a recovery zip! Tested on E2303 with TWRP. Made with PRFCreator
Click to expand...
Click to collapse
Its flashable zip too... not important pre-rooted or not after flashing is done, simple you can install supersu.zip too. :good:
But You try to build pre rooted Rom?
Wysłane z mojego E2303 przy użyciu Tapatalka
Later I will try to make a flashable working prerooted, tomorrow i will upload it ( i tried today but still at 60% uploading) but for now I will complete de-bloated and other projects....
Ok, I uploaded to Mediafire but it not give me the link.... I am uploading again to Mega and its at 30%
alby_var said:
Ok, I uploaded to Mediafire but it not give me the link.... I am uploading again to Mega and its at 30%
Click to expand...
Click to collapse
And ?? Can you upload pre rooted Rom ?
I not successfully can upload it. All hosting websites stop uploading or still for 2-3 days and i have to shut down pc.
Upload it to google drive and share link,ty
Stock firmware for e2303 flashable zip
Link?
26.1.a.2.167/r12a
Can someone explain what means R12A in 26.1.A.2.167/R12A ?
so, does anybody have this flashable stock rom? I could really use it right now...