First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Permanent root suggestion
Hi, guys, after this great achievement, permanent root might be desirable.
I'll tell you a story...I've always loved qwerty phones and one of the rare phones I've always wanted is NEC Terrain (distributed by AT&T). Unfortunately AT&T has locked it to its network and I found no working solution for unlocking it for other SIM cards (please let me know if you know of a working SIM unlock service!), BUT I've always wanted to gain permanent root privileges for this device. The story of NEC Terrain is very similar to Palm Phone PVG100 (Pepito):
NEC Terrain was released by AT&T and the bootloader locked, while Palm Phone PVG100 (Pepito) was released by Verizon and the bootloader locked...
NEC company is not on the market anymore and Palm company is in a similar condition, which makes contacts with the company difficult and the hope of updates to be released unlikely...
Code for NEC Terrain was developed by enthusiasts (https://github.com/android-rooting-tools/android_run_root_shell) similar to arpruss code for Palm Phone PVG100 (Pepito) (https://github.com/arpruss/cve2019-2215-3.18)...
Temporary root solution for NEC Terrain was achieved (https://github.com/x29a/nec_terrain_root) like root solution for Palm Phone PVG100 (Pepito) was achieved (https://github.com/arpruss/cve2019-2215-3.18/tree/master/release)...
For NEC Terrain a creative permanent root solution was developed by x29a (https://github.com/x29a/nec_terrain_root/blob/master/terroot/README.md) and now my suggestion is that we might want to follow his steps for Palm Phone PVG100 (Pepito)!
Here are the details of "HOW ALEX-KAS DID IT"!:
https://forum.xda-developers.com/showpost.php?p=61542922&postcount=186
Does anyone of you find this path convincing?
greatjack1 said:
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Click to expand...
Click to collapse
Hi there, please have a look at the attached pictures and let me know what might be wrong...I mean, what is the app-release.apk file you added to your post supposed to be doing?
And what exactly does the "Install on boot" optional tickbox do?
StormSeeker1 said:
Hi there, please have a look at the attached pictures and let me know what might be wrong...I mean, what is the app-release.apk file you added to your post supposed to be doing?
And what exactly does the "Install on boot" optional tickbox do?
Click to expand...
Click to collapse
Really wierd, it worked for me. Let me look a little deeper
greatjack1 said:
Really wierd, it worked for me. Let me look a little deeper
Click to expand...
Click to collapse
Do I have to run or install that .apk AFTER having spawned the root privileged shell or in substitution for it?
What is it supposed to be doing?
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
greatjack1 said:
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Click to expand...
Click to collapse
May I ask you to please put the list of the commands needed for spawning the root privileged shell back in your tutorial? I think it helps people a lot
Oh, and, people, do you know why, when I have the root shell, I'm not able to get the following command executed?
setprop sys.usb.config diag,adb
I get the following response:
setprop: failed to set property 'sys.usb.config' to 'diag,adb'
Why is there three threads about this?
Mattzees said:
Why is there three threads about this?
Click to expand...
Click to collapse
People started them independently and each one is on a specific thing, but all things are connected (there are interconnections and it's not always clear if rooting helps unlocking bootloader or if unlocking bootloader helps permanently rooting or if for compiling custom recoveries (TWRP) one needs root or bootloader unlocking), so these threads have a reason to exist and there are overlaps, but feel free to let people know if you want to merge something!
StormSeeker1 said:
Do I have to run or install that .apk AFTER having spawned the root privileged shell or in substitution for it?
What is it supposed to be doing?
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
May I ask you to please put the list of the commands needed for spawning the root privileged shell back in your tutorial? I think it helps people a lot
Oh, and, people, do you know why, when I have the root shell, I'm not able to get the following command executed?
setprop sys.usb.config diag,adb
I get the following response:
setprop: failed to set property 'sys.usb.config' to 'diag,adb'
Click to expand...
Click to collapse
try dial this code
Code:
###2324#
freezex said:
try dial this code
Code:
###2324#
Click to expand...
Click to collapse
IT WORKS! WHERE DID YOU FIND THIS CODE (AND OTHERS), freezex?! (I had tried lots of them from other phones with no success)
StormSeeker1 said:
IT WORKS! WHERE DID YOU FIND THIS CODE (AND OTHERS), freezex?! (I had tried lots of them from other phones with no success)
Click to expand...
Click to collapse
Guys, I was finally able to read Non-Volatile memory values using freezex's secret code for enable debugging, installing the USB drivers that popup when you choose on the phone the USB option "Drivers CD-ROM" after connecting it to the PC, using "QPST Configuration" tool and "QXDM" tool.
I tried to replace the initial value "2251799813754906" with "68787503589", which, according to my understanding, should cover all Italian LTE bands (please confirm and let me know if there is a way to reverse lookup code 2251799813754906 to see what bands are included inside of it).
The value I entered persisted after reboot and I was able to read the new value with QXDM.
Unfortunately I'm still seeing only a 3G icon on the notification bar...any idea on the cause of this behavior, guys?
A lot of values are there, can you please let me know if changing any of those values might help unlocking the bootloader?
PAY ATTENTION: After having enabled Diagnostic Mode (with freezex's secret code), Windows Device Manager recognizes the phone as "ALCATEL HS-USB Diagnostics 903A (COM6)"; does the fact that it comes from Alcatel give us any hint on what to do?
Also, people, do you find any free space not used by any partition to try NEC Terrain trick?
Here's some information I took from my PVG100:
127|Pepito:/data/local/tmp # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1358904 2764 1356140 1% /
tmpfs 1439680 752 1438928 1% /dev
/dev/block/dm-0 2999516 2218028 781488 74% /system
/dev/block/dm-1 1499760 881984 617776 59% /vendor
tmpfs 1439680 0 1439680 0% /mnt
/dev/block/mmcblk0p52 1998672 6156 1992516 1% /fotadata
/dev/block/mmcblk0p29 237536 400 237136 1% /cache
/dev/block/mmcblk0p12 12016 8448 3568 71% /dsp
/dev/block/mmcblk0p1 85968 81600 4368 95% /firmware
/dev/block/mmcblk0p30 28144 480 27664 2% /persist
/dev/block/dm-2 21667804 7631300 14036504 36% /data
/data/media 21667804 7631300 14036504 36% /mnt/runtime/default/emulated
See also this output:
Pepito:/dev/block/platform/soc/7824900.sdhci/by-name # ls -l
total 0
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 aboot -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 abootbak -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 apdp -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlib -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlib64 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlib64bak -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 cmnlibbak -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 config -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 devinfo -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 dip -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 dpo -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 fotadata -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 keymaster -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 keymasterbak -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 keystore -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 limits -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 logdump -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 mcfg -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 mdtp -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 mota -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 msadp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 oem -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 persist -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 redbend -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 simlock -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 splash -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 syscfg -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 system -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 traceability -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 tunning -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-02 06:36 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 userdata -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-02 06:36 vendor -> /dev/block/mmcblk0p28
I was able to push the "parted" utility to the phone, after having found a version already compiled for ARMv8 processors (and the Qualcomm SnapDragon 435 inside the PVG100 is an ARMv8).
This is the output I get:
127|Pepito:/data/local/tmp # ./parted /dev/block/mmcblk0 print
Model: MMC GD6BMB (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 67.1MB 155MB 88.1MB fat16 modem msftdata
2 201MB 201MB 1024B fsc
3 201MB 201MB 8192B ssd
4 201MB 202MB 524kB sbl1
5 202MB 202MB 524kB sbl1bak msftdata
6 202MB 203MB 524kB rpm
7 203MB 203MB 524kB rpmbak msftdata
8 203MB 206MB 2097kB tz
9 206MB 208MB 2097kB tzbak msftdata
10 208MB 208MB 262kB devcfg
11 208MB 208MB 262kB devcfgbak
12 208MB 225MB 16.8MB ext4 dsp msftdata
13 225MB 227MB 1573kB modemst1
14 227MB 228MB 1573kB modemst2
15 268MB 268MB 32.8kB DDR
16 268MB 270MB 1573kB fsg
17 270MB 270MB 16.4kB sec
18 270MB 272MB 1573kB tunning
19 272MB 273MB 1049kB traceability
20 336MB 337MB 1049kB simlock
21 337MB 340MB 3170kB redbend msftdata
22 340MB 351MB 11.5MB splash
23 403MB 404MB 1049kB aboot
24 404MB 405MB 1049kB abootbak msftdata
25 405MB 472MB 67.1MB boot
26 472MB 539MB 67.1MB recovery
27 539MB 3760MB 3221MB ext4 system
28 3760MB 5371MB 1611MB ext4 vendor
29 5436MB 5704MB 268MB ext4 cache
30 5704MB 5738MB 33.6MB ext4 persist
31 5771MB 5772MB 1049kB devinfo
32 5838MB 5840MB 1049kB misc
33 5840MB 5840MB 524kB keystore
34 5840MB 5840MB 32.8kB config
35 5840MB 6109MB 268MB oem
36 6174MB 6174MB 32.8kB limits
37 6241MB 6242MB 524kB mota msftdata
38 6242MB 6243MB 1049kB dip
39 6243MB 6276MB 33.6MB mdtp
40 6276MB 6277MB 524kB syscfg
41 6277MB 6281MB 4194kB mcfg msftdata
42 6308MB 6309MB 1049kB cmnlib
43 6309MB 6310MB 1049kB cmnlibbak
44 6310MB 6311MB 1049kB cmnlib64
45 6311MB 6312MB 1049kB cmnlib64bak
46 6312MB 6313MB 1049kB keymaster
47 6313MB 6315MB 1049kB keymasterbak
48 6375MB 6376MB 262kB apdp
49 6376MB 6376MB 262kB msadp
50 6376MB 6376MB 8192B dpo
51 6376MB 6443MB 67.1MB logdump
52 6443MB 8590MB 2147MB ext4 fotadata msftdata
53 8590MB 31.3GB 22.7GB userdata
StormSeeker1 said:
Do I have to run or install that .apk AFTER having spawned the root privileged shell or in substitution for it?
What is it supposed to be doing?
---------- Post added at 11:14 PM ---------- Previous post was at 11:11 PM ----------
May I ask you to please put the list of the commands needed for spawning the root privileged shell back in your tutorial? I think it helps people a lot
Oh, and, people, do you know why, when I have the root shell, I'm not able to get the following command executed?
setprop sys.usb.config diag,adb
I get the following response:
setprop: failed to set property 'sys.usb.config' to 'diag,adb'
Click to expand...
Click to collapse
StormSeeker1 said:
IT WORKS! WHERE DID YOU FIND THIS CODE (AND OTHERS), freezex?! (I had tried lots of them from other phones with no success)
Click to expand...
Click to collapse
I was googling something like "alcatel diagnostic code",and found it in this funny page. LoL
http://huaweisolarinverter.com/q16el/zav.php?juc=alcatel-6055u
freezex said:
I was googling something like "alcatel diagnostic code",and found it in this funny page. LoL
http://huaweisolarinverter.com/q16el/zav.php?juc=alcatel-6055u
Click to expand...
Click to collapse
Well...congratulations
Folks, might this be helpful?
https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html
https://www.emergingdefense.com/blog/2019/5/20/how-to-put-a-qualcomm-phone-into-edl-mode
People, I had an idea! Look here:
https://www.verizonwireless.com/support/knowledge-base-200052/
From the previous page, it looks like Verizon allows for enabling fastboot!
I tried chatting with them or getting a contact, but it looks like they require you to be their customer to listen to you. Can you find a way to contact them and kindly ask for a fastboot enable solution for Palm PVG100? Is there any user of this forum able to help us (possibly somebody who is currently using Verizon as a provider)?
https://www.verizonwireless.com/support/contact-us/
All those GitHub links are dead. Please advise.
Also what is the root.zip with a file names root in it? Is that the APK or something else (no extension).
Thanks again. Very exciting stuff.
greatjack1 said:
First of all credit for this goes to arpruss - https://github.com/arpruss/cve2019-2215-3.18.
Just download and install the apk from here https://github.com/arpruss/cve2019-2215-3.18/raw/master/release/app-release.apk
Then open the app and click install. You are done
WARNING: once you have a root shell do not modify system files as that will result in a bricked system until we figure out a way to unlock the bootloader.
Click to expand...
Click to collapse
bensdeals said:
All those GitHub links are dead. Please advise.
Also what is the root.zip with a file names root in it? Is that the APK or something else (no extension).
Thanks again. Very exciting stuff.
Click to expand...
Click to collapse
Hi, bensdeals
unfortunately arpruss removed his repository from github:
https://forum.xda-developers.com/showpost.php?p=80702567&postcount=164
Luckily another user, which I thank a lot (ilikenwf) has a mirror of what has been done so far:
https://forum.xda-developers.com/showpost.php?p=80702567&postcount=167
The root.zip file contains a file with no extension, which is not an apk package, but an executable compiled for the architecture of the CPU and for the operating system that PVG100 has.
Here's how to run the "root" file inside the package:
On windows open a CMD shell in the folder where "adb.exe" and "root" files are, then:
adb push root /data/local/tmp
adb shell
chmod +x /data/local/tmp/root
cd /data/local/tmp
./root
See below what you get (notice the # sign, meaning root user as opposed to the $, meaning regular user):
adb shell
Pepito:/ $ chmod +x /data/local/tmp/root
Pepito:/ $ cd /data/local/tmp
Pepito:/data/local/tmp $ ./root
MAIN: detected kernel version 3
MAIN: starting exploit for devices with waitqueue at 0x98
PARENT: soon will be calling WRITEV
CHILD: Doing EPOLL_CTL_DEL.
CHILD: Finished EPOLL_CTL_DEL.
CHILD: initial portion length 0x12000
CHILD: task_struct_ptr = 0xffffffc059c51980
CHILD: clobbering with extra leak structures
PARENT: clobbering at 0xffffffc03d8db4a0
CHILD: Doing EPOLL_CTL_DEL.
CHILD: Finished EPOLL_CTL_DEL.
CHILD: wrote 69688
PARENT: readv returns 69688, expected 69688
PARENT: clobbering test passed
CHILD: clobbered
PARENT: writev() returns 0x13008
PARENT: Reading leaked data
CHILD: task_struct_ptr = 0xffffffc066664000
CHILD: Finished write to FIFO.
PARENT: leaking successful
MAIN: task_struct_ptr = ffffffc059c51980
MAIN: stack = ffffffc066664000
MAIN: Clobbering addr_limit
PARENT: clobbering at 0xffffffc066664008
CHILD: Doing EPOLL_CTL_DEL.
CHILD: Finished EPOLL_CTL_DEL.
CHILD: wrote 69648
PARENT: readv returns 69648, expected 69648
PARENT: clobbering test passed
MAIN: thread_info = 0xffffffc066664000
MAIN: should have stable kernel R/W now
MAIN: searching for cred offset in task_struct
MAIN: search_base = ffffffc000000000
MAIN: searching for selinux_enforcing
MAIN: setting root credentials with cred offset 670
MAIN: UID = 0
MAIN: enabling capabilities
MAIN: SECCOMP status 0
MAIN: disabled selinux enforcing
MAIN: no whitelist, so all callers are welcome
MAIN: root privileges ready
MAIN: popping out root shell
Pepito:/data/local/tmp #
Does this help?
Thanks, that does work in achieving root. Question, you indicated modifying any system files would brick the device. Without an app to grant root access to other apps (supersu), then there isn't much we can do. Have you attempted to do anything else besides running this script?
... About your unlocking bands via editing nv data. Once you have root you can use the Network Signal Guru app to see if you have unlocked the bands. This doesn't necessarily mean those bands will work.
bensdeals said:
Thanks, that does work in achieving root. Question, you indicated modifying any system files would brick the device. Without an app to grant root access to other apps (supersu), then there isn't much we can do. Have you attempted to do anything else besides running this script?
... About your unlocking bands via editing nv data. Once you have root you can use the Network Signal Guru app to see if you have unlocked the bands. This doesn't necessarily mean those bands will work.
Click to expand...
Click to collapse
I'll have a look at the Network Signal Guru app, thanks. About that warning, it wasn't me writing it...and I'm a bit worried of trying modifying the system without having any ROM to reflash in case of brick (nor a working way to perform the flashing)...is there anyone who can help us with this?
I've just installed the Network Signal Guru app...but it looks like it requires root privileges, do you confirm? Also, how should I use it to get the LTE bands I'm using? Is it part of the free functionalities? What are paid functionalities?
It gives you the ability to disable active bands.. what it will do for you is tell you if you did successfully unlock and enable a band. You can then disable all the other bands with th tool. All via the free version with root.
Not sure if you can run it after rooting from the adb shell with root or what is consider problematic towards bricking your device.
StormSeeker1 said:
I'll have a look at the Network Signal Guru app, thanks. About that warning, it wasn't me writing it...and I'm a bit worried of trying modifying the system without having any ROM to reflash in case of brick (nor a working way to perform the flashing)...is there anyone who can help us with this?
I've just installed the Network Signal Guru app...but it looks like it requires root privileges, do you confirm? Also, how should I use it to get the LTE bands I'm using? Is it part of the free functionalities? What are paid functionalities?
Click to expand...
Click to collapse
StormSeeker1 said:
Well...congratulations
Folks, might this be helpful?
https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html
https://www.emergingdefense.com/blog/2019/5/20/how-to-put-a-qualcomm-phone-into-edl-mode
People, I had an idea! Look here:
https://www.verizonwireless.com/support/knowledge-base-200052/
From the previous page, it looks like Verizon allows for enabling fastboot!
I tried chatting with them or getting a contact, but it looks like they require you to be their customer to listen to you. Can you find a way to contact them and kindly ask for a fastboot enable solution for Palm PVG100? Is there any user of this forum able to help us (possibly somebody who is currently using Verizon as a provider)?
https://www.verizonwireless.com/support/contact-us/
Click to expand...
Click to collapse
The context of that fast boot was an older Qualcomm feature which put your phone into a hibernation state so that it would boot quicker it isn't releated to the bootloader fastboot. Also to answer your question about the alcatel driver that is just what windows picks the driver to be by default when it sees one of the many qualcomm debug modes..
deadman96385 said:
The context of that fast boot was an older Qualcomm feature which put your phone into a hibernation state so that it would boot quicker it isn't releated to the bootloader fastboot. Also to answer your question about the alcatel driver that is just what windows picks the driver to be by default when it sees one of the many qualcomm debug modes..
Click to expand...
Click to collapse
Thank you for clarifying; anyway, about the drivers, when you set the USB mode on the phone after connecting it to the PC, you have the option to connect it as a virtual CD drive, containing the drivers, so drivers (I don't know which ones) come from the phone itself (maybe this is unusual, but that read-only emulated CD partition exists on this phone).
StormSeeker1 said:
Thank you for clarifying; anyway, about the drivers, when you set the USB mode on the phone after connecting it to the PC, you have the option to connect it as a virtual CD drive, containing the drivers, so drivers (I don't know which ones) come from the phone itself (maybe this is unusual, but that read-only emulated CD partition exists on this phone).
Click to expand...
Click to collapse
That is used fairly often normally it's a setup exe to install them. Which depending on if it contains a driver for the mode your in it would override the Alcatel branded one which in reality is just there because both Alcatel and palm are TCL brands now.
Related
Is it possible to restore a damaged device partition (eg. from below list) (eg : /dev/block/mmcblk0p8) using a backup from another working phone ?
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
is the content of the partition different on each s2 phone ?
If we create a backup with following command :
[dd if=/dev/block/mmcblk0p8 of=/sdcard/phonebackup/mmcblk0p8.img bs=4096]
and restore in similar way,is there a risk of bricking the phone ?
saw some rom require TZ/RPM? what are they ?
optimusv45 said:
saw some rom require TZ/RPM? what are they ?
Click to expand...
Click to collapse
Those are partitions, TZ=trust zone RPM=something power management. Short of it is they need to be updated to the official jellybean ones for 4.2 or 4.3 to work. If you got 4.1 ota, or used lgnpst with 20j or Teenybin files they will be up to date.
adfurgerson said:
Those are partitions, TZ=trust zone RPM=something power management. Short of it is they need to be updated to the official jellybean ones for 4.2 or 4.3 to work. If you got 4.1 ota, or used lgnpst with 20j or Teenybin files they will be up to date.
Click to expand...
Click to collapse
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
optimusv45 said:
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
Click to expand...
Click to collapse
All of the current Roms require it, the earliest cfx and possibly cm10.1 could run without it. I wouldn't recommend those as daily drivers compared to what's availible now.
optimusv45 said:
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
Click to expand...
Click to collapse
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for catching my mistake @Shelnutt2. So I am clear, those can be flashed because they use LG based kernel? Also if you are saying you could make a zip to update partitions, that would be an awesome thing to have.
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Flashable zip would be awesome. I looked at the lgnpst thing a bit , it reminds me of RUU for my HTC phone. If I could I would rather not go back to 100 % stock and do everything all over again.
Shelnutt2 u mentioned you have cm 10.2 I couldnt find it in the development
optimusv45 said:
Shelnutt2 u mentioned you have cm 10.2 I couldnt find it in the development
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2411406
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
shelnutt2, can you put up a flashable zip for the TZ/RPM update ? i hope to have the capability to use all the available roms without having to learn lgnpst and teenybin. thanks.
http://webchat.freenode.net/?channels=lg-optimus-g
Spoke with Shelnutt2 on irc and he needs someone with updated rpm/tz to get md5 sums using adb or terminal emulator, then he can make the flashable zip. I tried but the WiFi I was on on wouldn't stay connected. If anyone wants to help out here is link for irc.
A flash able zip would be awesome, I'm not sure if it would help me or not but I believe my rpm/tz partitions are messed up
Sent from my LG Optimus G using Tapatalk 4
anyone with internet can help ?...
If you use teenybin you don't have to go back to stock
Sent from my Optimus G using Xparent BlueTapatalk 2
pcexpress said:
If you use teenybin you don't have to go back to stock
Sent from my Optimus G using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I understand there is teenybin. Flashable zip is just an easy way for people like me who don't want to learn LGNPST
adfurgerson said:
http://webchat.freenode.net/?channels=lg-optimus-g
Spoke with Shelnutt2 on irc and he needs someone with updated rpm/tz to get md5 sums using adb or terminal emulator, then he can make the flashable zip. I tried but the WiFi I was on on wouldn't stay connected. If anyone wants to help out here is link for irc.
Click to expand...
Click to collapse
I'd be glad to, my adb is my best friend when I keep recompiling and breaking roms, what comands give an md5 of the actual partitions?
or just an md5 of the contents? I'll screw around rq and edit this if it's a no brainer.
random results, if this counts:
Code:
/dev/block/platform/msm_sdcc.1/by-name # ll
ll
drwxr-xr-x 2 root root 740 Sep 15 09:35 ./
drwxr-xr-x 4 root root 800 Sep 15 09:35 ../
lrwxrwxrwx 1 root root 21 Sep 15 09:35 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 Sep 15 09:35 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Sep 15 09:35 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Sep 15 09:35 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Sep 15 09:35 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Sep 15 09:35 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Sep 15 09:35 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Sep 15 09:35 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Sep 15 09:35 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Sep 15 09:35 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Sep 15 09:35 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Sep 15 09:35 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Sep 15 09:35 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Sep 15 09:35 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Sep 15 09:35 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Sep 15 09:35 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 Sep 15 09:35 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Sep 15 09:35 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Sep 15 09:35 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Sep 15 09:35 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 20 Sep 15 09:35 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Sep 15 09:35 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Sep 15 09:35 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Sep 15 09:35 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Sep 15 09:35 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Sep 15 09:35 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 Sep 15 09:35 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Sep 15 09:35 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Sep 15 09:35 userdata -> /dev/block/mmcblk0p24
/dev/block/platform/msm_sdcc.1/by-name # cd rpm
cd rpm
/sbin/sh: cd: can't cd to rpm
/dev/block/platform/msm_sdcc.1/by-name # md5sum rpm
md5sum rpm
b1fa2c29e99349abb7104ea87ee9c0e1 rpm
/dev/block/platform/msm_sdcc.1/by-name # md5sum tz
md5sum tz
9913d95fb8bc67e2942bcd491fd07af3 tz
/dev/block/platform/msm_sdcc.1/by-name #
And just to be sure, cat > both to a file for sanity sake and md5 on windows, same results.
Code:
C:\android\md5sums-1.2>md5sums rpm.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\android\md5sums-1.2\]
rpm.img b1fa2c29e99349abb7104ea87ee9c0e1
C:\android\md5sums-1.2>md5sums tz.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\android\md5sums-1.2\]
tz.img 9913d95fb8bc67e2942bcd491fd07af3
C:\android\md5sums-1.2>
files attached:
View attachment rpm.img
View attachment tz.img
In case some of you hadn't noticed, this is a Q&A, Help and Troubleshooting thread...
If you've got nothing constructive to contribute, I suggest you move along and troll somewhere else.
bump
optimusv45 said:
bump
Click to expand...
Click to collapse
If you want to update with lgnpst I will help you do it. It really isn't that hard, if you managed to root your phone you should be capable of doing it. It could even be done in real time on irc channel, we would just need to set a time.
adfurgerson said:
If you want to update with lgnpst I will help you do it. It really isn't that hard, if you managed to root your phone you should be capable of doing it. It could even be done in real time on irc channel, we would just need to set a time.
Click to expand...
Click to collapse
4.4 lured me into updating using teenybins. you were right, its not bad
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
dkanas said:
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
Click to expand...
Click to collapse
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
blueether said:
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
Click to expand...
Click to collapse
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
dkanas said:
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
Click to expand...
Click to collapse
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
blueether said:
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
Click to expand...
Click to collapse
Yes, i know. But I don't know if the partitions in this prototype match the production models partitions, there could be a difference, like in the gpe model. I don't want to brick this device, it's worth a half of the usual monthly salary in my country Does someone know what exactly is the difference between the regular and the gpe editions?
Update: I think I pulled out the partition layout from my prototype:
Code:
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
What further information can I provide you?
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
dkanas said:
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
Click to expand...
Click to collapse
I cant see that the partition layout would have changed can uou use adb shell to list the partitions?
Code:
adb shell
su
fdisk -l /dev/block/platform/msm_sdcc.1/mmcblk0
output should be:
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 25 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 5375 512K 0700 sbl1
3 5376 5887 256K 0700 s1sbl
4 5888 6015 65536 0700 dbi
5 6016 7039 512K 0700 aboot
6 7040 8063 512K 0700 rpm
7 8064 9087 512K 0700 tz
8 9088 10111 512K 0700 alt_sbl1
9 10112 10623 256K 0700 alt_s1sbl
10 10624 10751 65536 0700 alt_dbi
11 10752 11775 512K 0700 alt_aboot
12 11776 12799 512K 0700 alt_rpm
13 12800 13823 512K 0700 alt_tz
14 13824 54783 20.0M 0700 boot
15 54784 75263 10.0M 0700 ramdump
16 75264 108031 16.0M 0700 FOTAKernel
17 108032 108095 32768 0700 DDR
18 114688 147455 16.0M 0700 LTALabel
19 147456 150527 1536K 0700 modemst1
20 155648 158719 1536K 0700 modemst2
21 163840 166911 1536K 0700 fsg
22 172032 188415 8192K 0700 apps_log
23 188416 4947967 2324M 0700 system
24 4947968 5357567 200M 0700 cache
25 5357568 30535646 12.0G 0700 userdata
[email protected]:/ #
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
dkanas said:
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
Click to expand...
Click to collapse
not sure on the effect of EFi vs MBR
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
{
"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"
}
dkanas said:
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
Click to expand...
Click to collapse
@blueether
I flashed the newest FTF and it's working! I'll be grateful to death!
for partitions you can also use parted
Code:
adb shell
cd /dev/block
# you can use
Code:
ls
if you want to see which partitions are in this folder. mmcblk0 is the one were everyting in is stored, mmcblk1 is your sdcard.
Code:
parted mmcblk0
print
.
now you see your partitions, with parted you can also adjust them (Don't do that, you'll brick when you make a mistake)
for commando options in parted use
Code:
help
or
Code:
parted
(i forgot)
Anyway good that you fixed your phone, just wanted to share
Can brown devices receive OTA updates? Ever since I have my prototype XZL, I never received a single update from sony, the only updates I receive are those from apps installed via the playstore.
Hello XDA i"):, I am running into issues putting the LG Optimus F7 (US780) together the way I would like to. I have Stock Android 4.1.2, Baseband Version M8960A----, Kernel Version 3.4.0.freedom, Build JZO54K, Software US78011a, PRI version 01. I wanted to get to Android 7.0/8.0/9.0 Nougat/Oreo/Pie for this phone model (API 21+?), and options to other versions of firmware. I am not sure how.
I currently have the Stock Firmware, flashed Philz Recovery, and flashed the Freedom Kernel per these link directions i");
Download mode (hold "volume up" then plug-in usb, when phone is off, do not use the power button.)
Recovery mode (hold "volume down" and "Power button" then follow on screen instructions.)
**I used "2nd init" recovery (CWM) to initiate this process, and it is still currently in there, it opens sometimes...2 recoveries? (volume down and plug in usb?? or initiate from within system while phone is on.)
1.) https://androidforums.com/threads/root-recovery-touch-non-touch-optimus-f7-fx1.829374/
In recovery flash i");
2.) https://intechgeek.com/lg-optimus-f7-kernel/#more-297
or (potentially)
2.a.) https://androidforums.com/threads/kernel-lg870-freedom-kernel-updated-9-14-14.810988/
In recovery, I flashed Root 2.82 SR5 to update Root 1.99 with these instructions i");
3.) https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
!");
Code:
s"):
18
1986
1001
1100
The above is a good system but:
(I wanted the "international unlocked/open features" ) :
1.a.) I thought the boost mobile was international/unlocked https://lg-firmwares.com/lg-870-firmwares/firmwares/
I have the backup of my working system (How to attach files?). It has Android 4.1.2 Freedom Kernel 3.4.0. Root 2.82 RS5, Philz Recovery.
I considered flashing Root 2.82 SR5 "System Mode" but I was unsure what "System Mode" meant or was for. (option)
3.a.) https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Then, I wanted to do a few things and have changed my mind along the way a few times. I wanted to deodex and found it inherently difficult. I wanted to modify where necessary to open various features. I then found non-stock roms for the device:
4.) http://guideroot.net/lg-optimus-f7-download-firmware-android-8-0-o/
For some reason what I am running into is a phone that disconnects and reconnects while in download mode, and does not show as a device when I try to use "fastboot devices". I tried the registry edit in this fashion:
5.) https://community.acer.com/en/discussion/367018/android-usb-devices-keep-connecting-and-disconnecting-on-r7
I looked here and I tried the dial code and the linked Power Saving options to no avail:
6.) https://androidforums.com/threads/rapid-usb-connecting-disconnecting-problem-wtf.886075/
Is there a way I can make the Android 7.0/8.0/9.0 Nougat/Oreo/Pie into a flashable .zip or restore from recovery?
Do I just need to put the MD5 checksum file in the .zip folder? (Answer: NO, there is more to it, see points A-G below)
This would be the easiest solution if it works..does anyone have a flashable backup or .zip of Android 7/8/9?
I was switching through recoveries available (stock, Philz, CWM, and I tried various versions of TWRP (didn't work/ not ported to phone?))
and flashing as a recovery by changing the md5 checksum. I was thinking one could easily switch through several different "systems" in the same sense.
I.e. nandroid.md5
Code:
1206d938f5134e91b6d665963a3b6d83 boot.img
10cfbc80f2f32cb2695a1b5252bdaddd recovery.img
f99466ea6669a62d391e3529bc6ff3e3 system.ext4.tar.a
c536ef897fbc5463c5bc490af6331bc6 system.ext4.tar.b
d41d8cd98f00b204e9800998ecf8427e system.ext4.tar
d30337df9e8fcb7fa8d62d56bbd0f908 recovery.img Stock
c268160e7fe0c7eb6eb227d6127b5311 recovery.img TWRP 2.8.6 (didn't work)
7b1e3ac64571fe467aed602acc661a7b recovery.img TWRP 3.0.0 (didn't work)
6117790563a47026be46aca6265994b7 recovery.img TWRP 3.1.1 (didn't work)
10cfbc80f2f32cb2695a1b5252bdaddd recovery.img PHILZ
( Through different systems (Android 8) by using adb shell (at recovery) or terminal emulator (phone), df, ls -al /dev/block/*/, et al, and dd if=/starage/sdcard1/inputfile(system).img of=/dev/block/mmcblk0pIE
Misaligned (at one point working)
dd if=/external_sd/clockworkmod/ROM/system.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p15
dd if=/external_sd/clockworkmod/ROM/system_other.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p14
dd if=/external_sd/clockworkmod/ROM/vendor.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p17
dd if=/external_sd/clockworkmod/ROM/radio.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p18
dd if=/external_sd/clockworkmod/ROM/modem.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p1
dd if=/external_sd/clockworkmod/ROM/bootloader.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p27
dd if=/external_sd/clockworkmod/ROM/boot.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p23
dd if=/external_sd/clockworkmod/ROM/hosd.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p24
dd if=/external_sd/clockworkmod/ROM/aboot.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p22
dd if=/external_sd/clockworkmod/ROM/xbl.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p12
dd if=/external_sd/clockworkmod/ROM/tz.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p16
dd if=/external_sd/clockworkmod/ROM/keymaster.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p26
dd if=/external_sd/clockworkmod/ROM/hyp.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p25
dd if=/external_sd/clockworkmod/ROM/cmnlib64.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p28
dd if=/external_sd/clockworkmod/ROM/rpm.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p8
dd if=/external_sd/clockworkmod/ROM/bootlocker.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p2
dd if=/external_sd/clockworkmod/ROM/devcfg.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p3
dd if=/external_sd/clockworkmod/ROM/pmic.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p5
dd if=/external_sd/clockworkmod/ROM/apdp.img of=/dev/block/platform/msm_sdcc.1/mmcblk0p6
I.e. for updater script: package_extract_file("system.img", "/dev/block/platform/msm_sdcc.1/mmcblk0p15")
I flashed this image to the cache, it worked, then I tried flashing the rest of it, cleared the cache.. looking at BrickJig:
https://forum.xda-developers.com/ga...oUye9j5KTJ0uwSkqSLvTvOBhn3x1R_iW438kEzksGMS9c
https://www.instructables.com/id/US...8evS5RdqBoQv0bImE2XLhPxMx41vtsR5_sIrBjXU9EuyM
)
Original "PIT" drwxr-xr-x root root 2018-11-16 04:21 by-name
drwxr-xr-x root root 2018-11-16 04:21 by-num
lrwxrwxrwx root root >100823040 bytes 2018-11-16 04:21 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 12582912 bytes 2018-11-16 04:21 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root >100823040 bytes 2018-11-16 04:21 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 8388608 bytes 2018-11-16 04:21 drm -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 encrypt -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 33554432 bytes 2018-11-16 04:21 fota -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 3145728 bytes 2018-11-16 04:21 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root >100823040 bytes 2018-11-16 04:21 grow -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 52428800 bytes 2018-11-16 04:21 lgipa -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1677216 bytes 2018-11-16 04:21 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 67108864 bytes 2018-11-16 04:21 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 3145728 bytes 2018-11-16 04:21 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 3145728 bytes 2018-11-16 04:21 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 33554432 bytes 2018-11-16 04:21 mpt -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1024 bytes 2018-11-16 04:21 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 8388608 bytes 2018-11-16 04:21 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 8192 bytes 2018-11-16 04:21 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 12582912 bytes 2018-11-16 04:21 recovery -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 rpmbak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1048576 bytes 2018-11-16 04:21 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 8388608 bytes 2018-11-16 04:21 sns -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 8192 bytes 2018-11-16 04:21 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root >100823040 bytes 2018-11-16 04:21 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 75497472 bytes 2018-11-16 04:21 tombstones -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 tzbak -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 524288 bytes 2018-11-16 04:21 userdata -> /dev/block/mmcblk0p15
drwxr-xr-x root root 2018-11-16 04:21 by-num
lrwxrwxrwx root root >100823040 bytes 2018-11-16 04:21 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root >100823040 bytes 2018-11-16 04:21 mmcblk1p1 -> /dev/block/mmcblk1p1
Is Android 7/8/9 even compatible with this phone? I am going to maybe try to build a .tar file from the systems .img's of Android 7/8/9 and go from there or when I get some time follow through A-G below.
For some reason that is where I am stuck for now. It seems a little bit unnatural that it would work for the original firmware flash but now it is troubling with this disconnect/reconnect issue. I am considering starting from the top except that the disconnect issue still exists.
If you have any ideas please feel free to suggest a solution.
A few more things I am interested in but am unable to build into without a reasonable grounding/base (Android 7/8/9). I was looking to make firmware upgrades more streamlined for after market, such that Linux, has Grub, and finds, at least some , of the firmware.
A.) Dissecting 3g/4g modems https://hackaday.com/2017/02/20/33c3-dissecting-3g4g-phone-modems/
B.) Complete Rom development https://forum.xda-developers.com/showthread.php?t=1661770
C.) What Should I know for Rom Devel? https://www.quora.com/What-should-I-learn-for-Android-ROM-development
D.) a.) Android Development https://forum.xda-developers.com/chef-central/android/guide-one-android-development-t3175121
b.) Android Development https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
E.) Create Personalized ROM http://en.miui.com/thread-21539-1-1.html
F.) Embedded Android Development https://www.slideshare.net/amraldo/android-booting-scenarios
G.) Linux Boot Sequence http://learnlinuxconcepts.blogspot.com/2014/02/android-boot-sequence.html
H.) Tools needed https://elitcan.com/tools-to-build-custom-rom-for-android.html?fbclid=IwAR2OXQut5yzL2dFR52s19GwGoqBT4umZx06YxEaNsaCi39xrOC8Fdngrtaw
I.) Android Open Source https://source.android.com/?fbclid=IwAR0BE_l15Y2TfHhr1Jglpbx8fsLMjWn7YVRc-RA2bglODmkz-YueH9-kvOs
J.) Previous Source https://github.com/android?fbclid=IwAR18FI9PTLbj2J-KLXrJE65Tb0zaXkarbUiibuZTKu1JM7knJQV9qUF51Pc
K.) Learn X Language in Y minutes https://learnxinyminutes.com/?fbclid=IwAR1vRPkuW3yLVjG4a9Z42GvZlFyyhdfJODbT1a-QxOoHMYAgZ0cDfVO4k-s
L.) platform_system_core/adb/ https://github.com/aosp-mirror/platform_system_core/tree/master/adb?fbclid=IwAR3XJ2arevlqOsHoFxXRuH4H3KDtsqcghTdZr1yr5I0uLcoJ5sS3H1rXmLU
M.) Guide to make FLASHABLE ZIP https://forum.xda-developers.com/android/software-hacking/framework-guide-to-make-flashable-zip-t3196490
for APK: https://www.maketecheasier.com/create-android-apps-recovery-zip/
https://www.guidingtech.com/49814/create-flashable-zips-custom-recovery/
https://androidforums.com/threads/tutorial-how-to-make-a-flashable-zip.828952/
CPU ASIC/DESIGN
A.) Reverse Engineering/Software Exploit (Video Lecture/PDF Slides)
https://plus.google.com/113611061190453317839
B.) Fritzing http://fritzing.org/home/
C.) Quite Universal Circuit Simulator http://qucs.sourceforge.net/
D.)How to become an embedded software developer? https://electronics.stackexchange.com/questions/3343/how-to-become-an-embedded-software-developer
BIOMEDICAL DEVICES
Robotic Eye https://www.designnews.com/electronics-test/artificial-eye-sensor-can-see-dark/94572894645119
Prosthetic Eye http://www.extremetech.com/extreme/...ic-eye-that-speaks-the-language-of-your-brain
IO > DNA > IO https://www.decodedscience.org/comparing-genetic-code-dna-binary-code/55476
Oxy Sensor https://en.wikipedia.org/wiki/Oxygen_sensor
I have more links and I planned to read through but I am running into some of these stops.
Lg Optimus F7 Links
https://www.gogorapid.com/flash-stock-rom-lg-optimus-f7-lg870/
http://blog.recovery-android.com/how-to-remove-bootstrap-recovery-on-android/
http://guideroot.net/lg-optimus-f7-download-firmware-android-8-0-o/
https://medium.com/@currentb4b/how-to-develop-stock-rom-for-android-mobile-59e7b3adeaa6
https://forum.xda-developers.com/showthread.php?t=1353903
https://forum.xda-developers.com/showthread.php?t=2320007
https://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
https://github.com/omnirom/android_bootable_recovery/tree/android-7.1
https://github.com/shine911/Android_Device_lge_Fx1
https://github.com/chevanlol360/device_lge_fx1
https://www.frequencycheck.com/models/ARMNG/lg-optimus-f7-us780
https://www.frequencycheck.com/bands/lte-band-12-700-ac
https://lg-firmwares.com/lg-phone-firmwares-region-description/
https://lg-firmwares.com/lg-870-firmwares/firmwares/
https://lg-firmwares.com/lg-us780-firmwares/firmwares/
https://intechgeek.com/lg-optimus-f7-kernel/#more-297
https://boycracked.com/android-tuto...y-lg-android-devices-using-kdz-updater-tools/
https://boycracked.com/android-stock-rom/offcial-lg-optimus-f7-stock-rom-firmware/
https://androidforums.com/threads/guide-unbrick-unroot-lg-optimus-f7-us780-us-cellular.843446/
https://androidforums.com/threads/kernel-lg870-freedom-kernel-updated-9-14-14.810988/
https://androidforums.com/threads/root-recovery-touch-non-touch-optimus-f7-fx1.829374/
https://androidforums.com/threads/r...very-for-the-lg-optimus-f7-lg870-fx1s.785165/
https://androidforums.com/threads/optimus-f7-all-things-root-guide.691538/
Android Custom ROM Links
https://hackaday.com/2017/02/20/33c3-dissecting-3g4g-phone-modems/
https://sourceforge.net/directory/os:windows/?q=android+rom+maker
https://source.android.com/setup/build/building
https://forum.xda-developers.com/showthread.php?t=1767392
https://forum.xda-developers.com/showthread.php?t=633246
http://learnlinuxconcepts.blogspot.com/2014/02/android-boot-sequence.html
https://forum.xda-developers.com/showthread.php?t=2771411
https://forum.xda-developers.com/showthread.php?t=2195858
https://www.slideshare.net/amraldo/android-booting-scenarios
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
https://forum.xda-developers.com/chef-central/android/guide-one-android-development-t3175121
https://circleci.com/build-environm...i&utm_content=Display-quora-Eng-ni-AndroidDev
https://www.quora.com/What-should-I-learn-for-Android-ROM-development
https://www.androidauthority.com/build-custom-android-rom-720453/
https://forum.xda-developers.com/showthread.php?t=1661770
[i"):]=A joke between friends until it works like that.
Flash Magisk instead of that root 2.82 thing
Peak.Krittin said:
Flash Magisk instead of that root 2.82 thing
Click to expand...
Click to collapse
Unfortunately, Magisk is for Android 5 Lollipop (21+) and above... I am stuck at Android 4.1.2.
Thank you for showing me the option for future/other phones.
https://www.xda-developers.com/how-to-install-magisk/
https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hopefully, good developer got the phone and make great rom for your device!
also ...
Welcome to XDA.
I've spent so much time on this forum and learned so much that I thought this is best place to go for my last resort. I really need to root this phone. I want to be able to use some rooted apps and especially be able to get more apps on my SD Card. My phone is unlockable (In fact Cricket said all their current phones are) I have no fastboot, no proper recovery mode and not even a bootloader mode. When I type adb reboot bootloader it only reboots the phone. I've looked into flashing a new boot, but I don't completely understand how to make or how to get all the any of the Qualcomm flash tools required files. I'll need help with that if it comes to it. I can't even flash a different models stock, because all LG stock I can find is ARB00 and right now I'm ARB03 it doesn't matter if it's even a higher version stock like Pie or even a it's LG G7 ThinQ unless it's ARB03 or higher I can't flash it and of course I can't downgrade. Which would save me a lot of headaches because the Nougat version at least still has fastboot and is ARB00. Something I can work with.
I am about to go to Walmart and just buy it again, because their version is still Nougat. That's what I'll do if I find no answer here, but I want to give this phone another chance. I read this phone can be rooted with Magisk, but with no recovery and no fastboot unless there's another option I don't know if that's even an option. Is there any way to dd install Magisk? If so please let me know. I've also been told it needs to be manually rooted, but I don't know where to get started doing that. I know it's get the right su files in the right places, and busybox but how do I do that with no root to start with, and being unable to mount the system? Is there a way?
I'm seriously willing to try anything at this point even if it will brick my phone. I have insurance on it that will replace it no matter how much damage I cause it and like I said am willing to re-buy the phone at Walmart which might be the better option since getting it from Cricket will most likely just take me back to where I started with an 8.1 phone that I can't do anything with. I don't care much about custom roms or that sort of thing. There isn't any for this phone anyway. I just want it rooted! please if you can think of anything, anything at all please let me know!
I have Windows 10 and Ubuntu
Also If these will help
Partitions:
HTML:
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 DDR -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 aboot -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 abootbak -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 apdp -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 boot -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cache -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64bak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlibbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dpo -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 drm -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dsp -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 eksst -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 encrypt -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 factory -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fota -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ftm -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 grow -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymaster -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keystore -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 laf -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 lafbak -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mcfg -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mpt -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 msadp -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persistent -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resources -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resourcesbak -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 rct -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recovery -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recoverybak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpmbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sec -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sns -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare3 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare4 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare5 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 srtc -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 system -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tzbak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 userdata -> /dev/block/mmcblk0p59
Nothing?
Okay from the lack of any reply I'm guessing there isn't a current way to root this device or nothing anybody knows. So I guess I'll get the Nougat version then, and see if I have better luck with it or wait until I save up enough money for another phone that I can unlock and root. If anybody thinks of anything I'm still willing to try, but I'm getting it's about time to give up and just never buy directly from cricket again.
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Thanks!
jwoegerbauer said:
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Click to expand...
Click to collapse
Thanks this is gave me some hope! I got a 1 so I guess it is unlockable! I can't use fastboot though. If I can figure a way to enable it maybe I can unlock and root it. The Nougat version still has fastboot enabled so that's why I wanted it, but it would be nice to find a way to unlock this one.
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
{
"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"
}
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Rebooting recovery gives me the little green guy passed out with a triangle with exclamation mark as a heart and says no command. I clicked the buttons you're supposed to click with that error to get the recovery options, but it just reboots. Sometimes though very randomly I do get to a place to wipe data and reset the phone. So I say the recovery works about .05% of the time. Unfortunately I can't flash new partitions with dd without root so no changing the boot.img or recovery.img like I had hoped either. Thank you! I haven't saw that tool before, I'm on Linux right now, but will download it as soon as I get back on Windows. I'll update after I try it.
Still need to try
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Sorry I haven't got this tried yet. I was trying to set up my Linux when it messed up and I had to restart the process. I'm keeping backups this time, but anyway just finishing that because I had to stop when I got a concussion. On the picture, it says to get in fastboot mode. I can't do that only download mode. So I don't think it will work, but I'll still try. I decided I'm going to rebuy the phone from Walmart that has Nougat and fastboot still enabled. That seems my only hope to unlock a phone and root it. The Nougat version is also ARB00 so I can flash firmware of a variant on that one if I need to as well. I know it sounds crazy to buy the same phone, but it's really all I can afford at this time. I'm saving up money for a better phone though, and my nephew has a really bad phone right now. So I can just give this one to him. He doesn't need root or anything so he'll like it.