I've bought an Italian TIM branded H815, got root access through send_command.exe exploit, and within the root shell I got, I've made a backup of the system and "cust" (the branding) partitions; then downloaded the image, injected root and used dd to overwrite the sytem partition with the rooted one.
After that, I've disabled OTAs, installed ssh server (dropbear), removed TIM branding and put back the stock unbranded stuff, removed all the bloatware, changed the dialer with the one shipped with the lollipop nexus 5 and everything works very nicely.
That's when, while exploring the partitions, I've found that the recovery seems to be in /dev/block/mmcblk0p39.
Being the bootloader still locked (and I'd like to keep it that way), I was pretty sure I couldn't write to the partition, BUT I've run dd to fetch the first bytes of the partition, wrote that to a file, and flashed the file back, overwriting what was there. *So, it was possible*.
Here's what I've done:
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery bs=1 count=70 of=/sdcard/recovery.partial.img
dd of=/dev/block/platform/f9824900.sdhci/by-name/recovery if=/sdcard/recovery.partial.img
Now here're the questions:
- What would happen if I would just write TWRP through dd over the partition from the running system? (ex.: dd if=/sdcard/twrp.img bs=8192 of=/dev/block/mmcblk0p39)... it seems I wouldn't be blocked by anything in doing so!
- Can you see my very same partitions inside the directory /dev/block/platform/f9824900.sdhci/by-name/ ? (at the end of the post the node listing) -- in case you can't, I've tought they could be useful to you to determine where they are in first place: I've read of people that couldn't find the node "recovery", thus couldn't write to it. Anyway, in that case, there are some tools to explore drive images in GPT form like testdisk and they could be used to find the location of that partition and write over it through dd using the "seek=" parameter.
- In case you already know all that, I presume there is a protection system that runs a checksum of the recovery partition on boot and would argue "hey, what's that? here, eat this bootloop!", otherwise I really can't imagine why I can't change the bootloader.
Thanks in advance!
Alessio
PS, here are the GPT partitions:
Code:
lrwxrwxrwx 1 root root 21 Jan 4 2015 DDR -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 Jan 4 2015 aboot -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 4 2015 abootbak -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 4 2015 apdp -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 4 2015 boot -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Jan 4 2015 cache -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 Jan 4 2015 cust -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Jan 4 2015 devinfo -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 4 2015 dpo -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 4 2015 drm -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Jan 4 2015 eksst -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Jan 4 2015 encrypt -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Jan 4 2015 factory -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Jan 4 2015 fota -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Jan 4 2015 fsc -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 4 2015 fsg -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 4 2015 grow -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 20 Jan 4 2015 hyp -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 4 2015 hypbak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 4 2015 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 4 2015 laf -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Jan 4 2015 limits -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 4 2015 misc -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jan 4 2015 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 4 2015 modemst1 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 4 2015 modemst2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 4 2015 mpt -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Jan 4 2015 msadp -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 4 2015 persist -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 4 2015 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 20 Jan 4 2015 pmic -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 4 2015 pmicbak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 4 2015 raw_resources -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Jan 4 2015 raw_resourcesbak -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Jan 4 2015 rct -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jan 4 2015 recovery -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 20 Jan 4 2015 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 4 2015 rpmbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 4 2015 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 4 2015 sbl1bak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 4 2015 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 4 2015 sdibak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 4 2015 sec -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jan 4 2015 sns -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Jan 4 2015 spare1 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 4 2015 spare2 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Jan 4 2015 ssd -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 4 2015 system -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 20 Jan 4 2015 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 4 2015 tzbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 4 2015 userdata -> /dev/block/mmcblk0p50
you can write to any partition.. bootloader locked or not.. as long as you have root. but that doesn't mean the newly written partition will actually boot afterwards.
locked bootloader = bootloader checking for valid boot/recovery partition signatures.
if you do not have LG's signing key to sign TWRP or custom boot.img.. then whatever custom image you write to recovery or boot partition will not boot.
Oh, I see, so there's a sort of DRM; nevermind, thanks for your clarification by the way
One last question: do you know if after the bootloader unlock any partition changes? I wonder if I could just change my whole firmware with an unlocked one, but I guess it's IMEI-dependent and an internal cryptochip would notice it and refuse to boot, right?
autoprime said:
you can write to any partition.. bootloader locked or not.. as long as you have root. but that doesn't mean the newly written partition will actually boot afterwards.
locked bootloader = bootloader checking for valid boot/recovery partition signatures.
if you do not have LG's signing key to sign TWRP or custom boot.img.. then whatever custom image you write to recovery or boot partition will not boot.
Click to expand...
Click to collapse
do you think it would work modifying the boot.img ( adding gov , overclocking, etc) using the any kernel method which extracts the img and modify the boot.img and then repacks it..or would that mess with the lg signing
autoprime said:
you can write to any partition.. bootloader locked or not.. as long as you have root. but that doesn't mean the newly written partition will actually boot afterwards.
locked bootloader = bootloader checking for valid boot/recovery partition signatures.
if you do not have LG's signing key to sign TWRP or custom boot.img.. then whatever custom image you write to recovery or boot partition will not boot.
Click to expand...
Click to collapse
What's stopping you from writing to the bootloader partition? Is it encrypted or something?
bigalex said:
... After that, I've disabled OTAs, installed ssh server (dropbear), removed TIM branding and put back the stock unbranded stuff, removed all the bloatware, changed the dialer with the one shipped with the lollipop nexus 5 and everything works very nicely.
Click to expand...
Click to collapse
Could you please outline the steps necessary to exchange the dialer?
Thanks in advance.
@dogroll: The bootloader is signed, so tampering with it will cause a bootloop, or brick the device anyway.
@Google~Android: Yeah, tampering with about anything will cause the kernel to know your device has been tampered, and it will complain about it in ways I just don't want to know (probably will surprise you with a nice brick).
@Jens1969: Yeah, and very happy to have been asked it: you can just install the Nexus 5 "Dialer.apk" you can get from any n5 firmware into the /system partition (it can't be installed into /data).
Doing so will cause, however, logcat messages about "hey, I can't find com.google.android.dialer.support library!".
So, you will also need the library, and you can find it in any gapps flashable package (I've used this one for example: CyanogenMod hxxp://d-h.st/dGPA).
The library is called com.google.android.dialer.support.jar and must be placed into /system/framework.
You also need to put the /system/etc/permissions/com.google.android.dialer.support.xml file in place. Once I have a minute, I will make a package for it
bigalex said:
@dogroll: The bootloader is signed, so tampering with it will cause a bootloop, or brick the device anyway.
@Google~Android: Yeah, tampering with about anything will cause the kernel to know your device has been tampered, and it will complain about it in ways I just don't want to know (probably will surprise you with a nice brick).
@Jens1969: Yeah, and very happy to have been asked it: you can just install the Nexus 5 "Dialer.apk" you can get from any n5 firmware into the /system partition (it can't be installed into /data).
Doing so will cause, however, logcat messages about "hey, I can't find com.google.android.dialer.support library!".
So, you will also need the library, and you can find it in any gapps flashable package (I've used this one for example: CyanogenMod hxxp://d-h.st/dGPA).
The library is called com.google.android.dialer.support.jar and must be placed into /system/framework.
You also need to put the /system/etc/permissions/com.google.android.dialer.support.xml file in place. Once I have a minute, I will make a package for it
Click to expand...
Click to collapse
I tried the method found here. But my Google Phone FCs and I can't use it for incoming calls. Since my Bootloader is still locked (don't want to void my warranty), I can't use a Zip package. But I could extract the contents and simply copy files and change permissions.
Jens1969 said:
I tried the method found here. But my Google Phone FCs and I can't use it for incoming calls. Since my Bootloader is still locked (don't want to void my warranty), I can't use a Zip package. But I could extract the contents and simply copy files and change permissions.
Click to expand...
Click to collapse
Yep, that's exactly what I did (and I forgot to mention the permissions thing that caused it to crash).
Did you check logcat to see why was it causing FC?
My bootloder is locked too, but still I was able to replace the dialer, so don't worry!
Just, remember to disable the LG dialer, and since you're there, debloat everything! (first line in the code below)
LG G4 debloat :
Code:
pm disable com.android.contacts;
pm disable com.android.LGSetupWizard;
pm disable com.lge.sizechangable.weather.platform;
pm disable com.lge.launcher2.theme.tim;
pm disable com.lge.cloudhub;
pm disable com.lge.remote.lgairdrive;
pm disable com.lge.eltest;
pm disable com.android.browser;
pm disable com.lge.bioitplatform.sdservice.service;
pm disable com.lge.sizechangable.favoritecontacts;
pm disable com.lge.wapservice;
pm disable com.lge.wfds.service.v3;
pm disable com.lge.gcuv;
pm disable com.lge.sync;
pm disable com.lge.livewallpaper.multiphoto;
pm disable com.lge.concierge;
pm disable com.lge.musicshare;
pm disable com.lge.pcsyncui;
pm disable com.lge.updatecenter;
pm disable com.lge.lgfota.permission;
pm disable com.lge.mlt;
pm disable com.lge.appwidget.dualsimstatus;
pm disable com.lge.sizechangable.musicwidget.widget;
pm disable com.lge.cic.eden.service;
pm disable com.lge.music;
pm disable com.lge.hiddenpersomenu;
autoprime said:
you can write to any partition.. bootloader locked or not.. as long as you have root. but that doesn't mean the newly written partition will actually boot afterwards.
locked bootloader = bootloader checking for valid boot/recovery partition signatures.
if you do not have LG's signing key to sign TWRP or custom boot.img.. then whatever custom image you write to recovery or boot partition will not boot.
Click to expand...
Click to collapse
I had the same question, as I'm sure many others have too, so I'm glad I found this post. So taking this a little further would it be possible to pull the bootloader from an unlocked device and overwrite the bootloader on a locked device? I'm a little unclear on the boot sequence so perhaps this question doesn't make sense. I'm running on the thought that the bootloader is "boot -> /dev/block/mmcblk0p38", or is it actually buried a bit deeper and not part of the file system at all?
Apologies if this has already been discussed in another thread (can be difficult to think of the right magic search phrase)
EDIT: actually it looks like the bootloader is "aboot -> /dev/block/mmcblk0p8"
Related
I do fastboot erase data, and get
erasing 'data'... FAILED (remote: Partition table doesn't exist)
Background: N-7 works on several roms. Now running stock KOT49H ota, all of them fairly reliable but after 4.4 I get stuck in the splash screen on reboot/power on. I've had to wipe data etc to get it to reboot at all. Have not tried to go back to pure stock.
Plan was/is to wipe data partition and restore data from computer through fastboot (has worked before on other 4.3+ roms/devices), but fastboot is seeing something it does not like. With recovery I can see that
dev/block/mmcblk0p30 on /data type ext4 (rw,seclabel,relatime,data=ordered)but of course that does not mean there -is- a data partition. I can't find any reference to partitioning an N7, etc. So - stuck. Any insight appreciated.
Is it possible that the new bootloader has changed the name of the partition to maybe userdata? But i doubt it. You can try
fastboot erase -w
This may work for you
Otherwise a wipe from recovery should give similar results - also in recovery you should be able to grab a log and check ftab to see partition table or you can access adb shell and check from there
ls -a -l /dev/block/platform/msm_sdcc.1/by-name
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Is it possible that the new bootloader has changed the name of the partition to maybe userdata? But i doubt it. You can try
fastboot erase -w
This may work for you
Otherwise a wipe from recovery should give similar results - also in recovery you should be able to grab a log and check ftab to see partition table or you can access adb shell and check from there
ls -a -l /dev/block/platform/msm_sdcc.1/by-name
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
Oooh - did not know about how to see the /dev stuff - nice.
~ # ls -a -l /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
drwxr-xr-x 2 root root 640 Dec 16 16:18 .
drwxr-xr-x 4 root root 700 Dec 16 16:18 ..
lrwxrwxrwx 1 root root 21 Dec 16 16:18 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Dec 16 16:18 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Dec 16 16:18 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Dec 16 16:18 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Dec 16 16:18 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Dec 16 16:18 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Dec 16 16:18 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Dec 16 16:18 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Dec 16 16:18 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Dec 16 16:18 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Dec 16 16:18 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Dec 16 16:18 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Dec 16 16:18 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Dec 16 16:18 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Dec 16 16:18 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Dec 16 16:18 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 16 16:18 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Dec 16 16:18 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Dec 16 16:18 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Dec 16 16:18 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Dec 16 16:18 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Dec 16 16:18 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Dec 16 16:18 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Dec 16 16:18 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Dec 16 16:18 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 16 16:18 tzb -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Dec 16 16:18 userdata -> /dev/block/mmcblk0p30Look like data is now userdata!
Using TWRP, data is mounted on mmcblk0p30 but earlier I flashed the latest CWM recovery and now using adb shell, it shows
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type ext4 (rw,seclabel,nodev,noatime,nodiratime,data=ordered)
Thought I semi-understood what was going on in the partition/mounting world. Clearly not.
Anyway, thanks! Maybe I can move forward with this now.
Was it ever named "data"? Since my first-gen N7, if memory serves, it was always "userdata" that I'd erase with fastboot.
Pandae said:
Was it ever named "data"? Since my first-gen N7, if memory serves, it was always "userdata" that I'd erase with fastboot.
Click to expand...
Click to collapse
Actually great to know that. All prev. phones etc I've used had "data". Thnx!
SOLVED
--------------------------------------------------------------------------------------------------------------
Pls somone upload flashable pack (via recovery) of kitkat rom, on xda i found only kdz files but i cant plugin my tab via usb.
--------------------------------------------------------------------------------------------------------------
So story is i get in loop of TWRP after update rom via OTA (from 4.4.2 to 5.0.2) and i cant plugin my tab via usb so i must flash zip via recovery but i cant find that kind of rom (only kdz files), but with the help came roirraW "edor" ehT and make flashable rom for lg v490 LG G PAD 8.0 V490 4.4.2 v10b Greek so i got back to stock rom but still be in TWRP loop.
And the solve of this was to enter in recovery > Advanced > Aroma filemanager > Open terminal emulator and tap this:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
and type
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
In my case i got some error about "no space left on device" but i reboot tab and it back to life from twrp loop.
---------------------------------------------------------------------------------------------------------------
Downloading and installing rom via recovery
1 Download:
A) The latest SuperSU
B) Advanced Download Manager from the Play Store, useful especially for downloading larger files like ROMs.
C) LG G PAD 8.0 V490 4.4.2 v10b Greek rom.
2 Check the MD5 Hash of the ROM zip:
A) Copy (to the clipboard) the MD5 hash that is in the filename of the ROM zip you downloaded in step 1.
B) Install AFV File Verifier for Android from the Play Store.
C) Run the AFV app.
D) Choose "Input checksum for comparison".
E) Paste the MD5 hash previously copied to the clipboard in step 2A above.
F) Choose "Select File".
G) Navigate to where you have the ROM zip.
H) Long-press on the ROM zip and choose "Calc MD5 Checksum".
I) When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.
3. Reboot to TWRP.
4. Wipe Cache, Data and Dalvik.
5. Flash the ROM zip.
6. Flash the SuperSU.zip.
7. Reboot.
You have TWRP for the V490? If so, give me a link to the KDZ and I'll make you a flashable ROM zip out of it. Warning that I don't have this device so I can't test it myself, so you'd be a guinea pig, which would be particularly dangerous if you can't use a KDZ via USB to return to a known good ROM.
Yes i root my tab and install twrp on kitkat, about 10 days ago i want to upgrade it to lollipop so i download update via ota and confirm it, tab turn off and turn on but it stock on a twrp. i give tab to somone else to check it but comp dont see it on lg flash tool, lg mobile support tool, download mode, (i frozen lg pc suite apps). so it is the last hope to get it back to life.
Sorry for that kind of link but i cant post normal links yet.
STOCK ROM:
Android 4.4.2 [v10b]
GR: goo. gl/ Hb7Qn6
pan_droid said:
Yes i root my tab and install twrp on kitkat, about 10 days ago i want to upgrade it to lollipop so i download update via ota and confirm it, tab turn off and turn on but it stock on a twrp. i give tab to somone else to check it but comp dont see it on lg flash tool, lg mobile support tool, download mode, (i frozen lg pc suite apps). so it is the last hope to get it back to life.
Sorry for that kind of link but i cant post normal links yet.
STOCK ROM:
Android 4.4.2 [v10b]
GR: goo. gl/ Hb7Qn6
Click to expand...
Click to collapse
I'll try to check this out tomorrow. I'll PM you a link to try when I can.
Install a terminal emulator app from the Play Store, launch it, give it superuser permissions and list all the partitions with the following code:
Code:
su
ls -l /dev/block/platform/msm_sdcc.1/by-name/
Press enter after each command. Confirm giving it root permissions when it asks after you enter the SU command.
Then at least in the terminal emulator I use, long press anywhere and choose Copy All. Paste the result in a reply to this, please.
roirraW "edor" ehT said:
Install a terminal emulator app from the Play Store, launch it, give it superuser permissions and list all the partitions with the following code:
Code:
su
ls -l /dev/block/platform/msm_sdcc.1/by-name/
Press enter after each command. Confirm giving it root permissions when it asks after you enter the SU command.
Then at least in the terminal emulator I use, long press anywhere and choose Copy All. Paste the result in a reply to this, please.
Click to expand...
Click to collapse
lrwxrwxrwx 1 root root 21 Apr 26 19:29 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 Apr 26 19:29 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Apr 26 19:29 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Apr 26 19:29 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Apr 26 19:29 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Apr 26 19:29 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Apr 26 19:29 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Apr 26 19:29 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Apr 26 19:29 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Apr 26 19:29 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Apr 26 19:29 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Apr 26 19:29 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Apr 26 19:29 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Apr 26 19:29 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Apr 26 19:29 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Apr 26 19:29 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 Apr 26 19:29 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Apr 26 19:29 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Apr 26 19:29 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Apr 26 19:29 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Apr 26 19:29 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Apr 26 19:29 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Apr 26 19:29 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Apr 26 19:29 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Apr 26 19:29 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Apr 26 19:29 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Apr 26 19:29 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Apr 26 19:29 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Apr 26 19:29 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Apr 26 19:29 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Apr 26 19:29 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Apr 26 19:29 system -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 Apr 26 19:29 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Apr 26 19:29 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Apr 26 19:29 userdata -> /dev/block/mmcblk0p34
Are you SURE you want to risk flashing this since you can't use the USB port on your PC to restore via KDZ in case anything goes wrong? You understand I won't be able to help because I don't even own a V490 to test on or have any experience with?
Also, to confirm, this is the Greek version of the stock ROM, correct?
You'll need to "follow" me on https://www.androidfilehost.com/ so that I can add you to a private group so that you (and only you) have access to download the zip, once it's done uploading.
Do you happen to know what the "codename" is for the V490? As in, the codename for my VK810 is "altev". I can't find it anywhere for the V490.
roirraW "edor" ehT said:
Are you SURE you want to risk flashing this since you can't use the USB port on your PC to restore via KDZ in case anything goes wrong? You understand I won't be able to help because I don't even own a V490 to test on or have any experience with?
Also, to confirm, this is the Greek version of the stock ROM, correct?
You'll need to "follow" me on so that I can add you to a private group so that you (and only you) have access to download the zip, once it's done uploading.
Do you happen to know what the "codename" is for the V490? As in, the codename for my VK810 is "altev". I can't find it anywhere for the V490.
Click to expand...
Click to collapse
yes this is greek version.
i dont know codename :/ is it necessary to rom work?
bdjwoxhjdhf
codename is e8lte
Link
pan_droid said:
yes this is greek version.
i dont know codename :/ is it necessary to rom work?
Click to expand...
Click to collapse
pan_droid said:
codename is e8lte
link tera-wurfl.co m/explore/?action=wurfl_id&id=lg_v490_ver1
Click to expand...
Click to collapse
No it's not necessary, I just like to make sure and indicate all details in the file name. Thanks! I'll PM you when it's uploaded for you to test.
PM sent.
roirraW "edor" ehT said:
PM sent.
Click to expand...
Click to collapse
Thank You
3 more
Sorry for that spam but i need to have 10 posts to add link to another site and on another site is rom for v490
pan_droid said:
Thank You
Click to expand...
Click to collapse
You're welcome! Glad I could help, and that I didn't brick your tablet.
roirraW "edor" ehT said:
You're welcome! Glad I could help, and that I didn't brick your tablet.
Click to expand...
Click to collapse
im so lucky ;D
.
And that will be the end
roirraW "edor" ehT said:
You're welcome! Glad I could help, and that I didn't brick your tablet.
Click to expand...
Click to collapse
Hi @roirraW"edor"ehT
I saw what you have wrote here and I have a request, if you want or have time to help me. I compiled cm12 for LG g PAD 8.0 v490 e8lte without errors, but after flash, which made without problems, the device don't boot up. Remains in LG LOGO and reboot after a few seconds. Enter in bootloop. Can you help me?
I follow you on that site you working but u don't
have contact listed. If you can or want give some help I'll be glad.
Thank you very much.
MAROCANU said:
Hi @roirraW"edor"ehT
I saw what you have wrote here and I have a request, if you want or have time to help me. I compiled cm12 for LG g PAD 8.0 v490 e8lte without errors, but after flash, which made without problems, the device don't boot up. Remains in LG LOGO and reboot after a few seconds. Enter in bootloop. Can you help me?
I follow you on that site you working but u don't
have contact listed. If you can or want give some help I'll be glad.
Thank you very much.
Click to expand...
Click to collapse
Can you get into custom recovery? If so, flash the ROM I made that @pan_droid posted in the Development section.
Otherwise, you'll have to return to stock using Download mode with LG Flash Tool 2014 and a KDZ made for your device.
I don't have this device so I can't advise with specifics. Maybe @pan_droid or anyone else with this device can help further.
Yes, I have custom recovery and yes, I can boot in. My problem is: I want to make it boot. I think the problem is in boot.img which was compiled from cyanogen source. I tried to replace the ramdisk but in that case a message apears at boot which says boot verification error. If you know how can I do to make it boot properly.
Thank you for answering me.
title
@MAROCANU plese look at this thread, working cm12 for v480.
User @jpjust made it work. http://forum.cyanogenmod.org/topic/110817-cm121-for-lg-g-pad-8-v490-v480/
Hello.
So, as I described here, I success got root on this device. Now, I want a full backup in case things going bad. And obvious, a way to restore this backup.
I was searching for days for a ROM, but it simply don't exist (yet). This model have an identification (alps l1 mp6 v2 gxq6580 weg l p69) wich is used in some other devices (includings Samsung clones), so, I checked all the ROMs I found looking into /system partition on my device and comparing with /system image of the ROMs (I used SuperR's Kitchen), and none of them are equal, I mean, a lot of files (includind build.prop) are different, so there is a great chance to brick my phone if I use it.
Even if it is found, I can't restore with SP Flash Tools, because it don't work with this phone. I tried to readback, but it recognizes but never start. As the phone is a MT6580 based SoC, maybe is compatability issue also. MTK Droid Tools don't work also. It recognizes, but can't do anything (don't generate scatter, don't root, don't nothing), again maybe a compatibility also.
The stock recovery have no option to backup, and I'm afraid to flash a CWM or TWRP, because I don't know much about porting these things, and I don't have much information about partitions and these things yet. ADB while in recovery give me an unauthorized device, by the way.
The phone accept fastboot commands, but don't accept the 'fastboot boot image.img", to try a temporary recovery, it only accept the 'fastboot flash image.img'. As sayed on the thread above, the bootloader is now unlocked, by the way.
So... this the situation... Can't have backup for now. If it help you to help me, there is the result of ls -all /dev/block/platform/mtk-msdc.0/by-name/ command in adb shell:
Code:
1|[email protected]_weg_l:/ # ls -all /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-03-30 00:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-30 00:16 cache -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-30 00:16 expdb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-30 00:16 flashinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-30 00:16 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-30 00:16 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-30 00:16 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-30 00:16 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-30 00:16 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-30 00:16 nvdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-30 00:16 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-30 00:16 oemkeystore -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-30 00:16 para -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-30 00:16 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-30 00:16 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-30 00:16 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-30 00:16 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-30 00:16 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-30 00:16 secro -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-30 00:16 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-30 00:16 userdata -> /dev/block/mmcblk0p20
[email protected]_weg_l:/ #
I sucessfully (I think) dump a boot image with dd command (dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img), but I'm not sure it is 100% perfect and if it can be safely used to restore (and how to restore... maybe 'fastboot flash'?). Maybe I can dump some other images, but I don't tried yet.
If you need any other information, I reply in almost same time.
Thanks in advice.
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
romulocarlos said:
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
Click to expand...
Click to collapse
Hello, i have recently posted a complete ROM on needrom. https://www.needrom.com/download/sony-xperia-c6-clone-mt6580/
i guess that is the one your are looking for. Good luck and sorry for my bad englich.
Help
Rom is corrupted, is not it? It's working? tell me how to download, I thank you
Problem: My beloved 32GB Pixel XL froze while I was typing the other night and I hard reset it. It froze during the boot animation, then rebooted, and then froze during the boot animation again. Done this ~30 times with no joy. It's just over a year old so no warranty.
Background: Bootloader unlocked. Stock rom v 7.1 (build NPF26J). Rooted.
What I've tried:
Clearing Dalvik/cache in TWRP
Factory reset through recovery (both TWRP and stock)
Begging it to work
Flashing factory images for 7.1 and 8.1
locking and unlocking the bootloader multiple times before flashing above factory images
Formatting Data and doing an Advanced Wipe in TWRP to recreate partitions then flashing both of the above factory stock images
At this point, it won't even go to the boot animation. It just goes to black after the white screen that says, "Google" then reboots. If it's rebooting for the first time after a factory image flash, it reboots into stock recovery.
Tried running e2fsck -cfv on userdata and system. This is the output:
userdata:
Code:
e2fsck 1.43.3 (04-Sep-2016)
sh: badblocks: not found
userdata: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
userdata: ***** FILE SYSTEM WAS MODIFIED *****
172 inodes used (0.01%, out of 1630208)
2 non-contiguous files (1.2%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 165
146606 blocks used (2.25%, out of 6509568)
0 bad blocks
1 large file
21 regular files
141 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
------------
163 files
system:
Code:
/dev/block/platform/soc/624000.ufshc/by-name # [6n[Je2fsck -cfv system
e2fsck 1.43.3 (04-Sep-2016)
sh: badblocks: not found
/: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
2517 inodes used (1.95%, out of 129024)
13 non-contiguous files (0.5%)
4 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2310/7
472130 blocks used (91.48%, out of 516099)
0 bad blocks
1 large file
2043 regular files
273 directories
0 character device files
0 block device files
0 fifos
0 links
192 symbolic links (192 fast symbolic links)
0 sockets
------------
2508 files
Noticed something very odd about the partition table--there's no /cache! Gonna try to create it somehow.
Code:
/dev/block/platform/soc/624000.ufshc/by-name # [6nls -al
total 0
drwxr-xr-x 2 root root 1340 1970-01-01 02:09 .
drwxr-xr-x 4 root root 1440 1970-01-01 02:09 ..
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 aboot_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 aboot_b -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 apdp_a -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 apdp_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 36 1970-01-01 02:09 boot -> /dev/block/bootdevice/by-name/boot_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 boot_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 boot_b -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 bootlocker_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 bootlocker_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cdt -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib32_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib32_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib64_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib64_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 ddr -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 devcfg_a -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 devcfg_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 devinfo -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 devinfobak -> /dev/block/sdd5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 dip -> /dev/block/sdd7
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 dpo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 frp -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 fsc -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hosd_a -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hosd_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hyp_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hyp_b -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 keymaster_a -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 keymaster_b -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 metadata -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 misc -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modem_a -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modem_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 modemst1 -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modemst2 -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 msadp_a -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 msadp_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 persist -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pg1fs -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pg2fs -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pmic_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 pmic_b -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 ramdump -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 reserve0 -> /dev/block/sda36
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 reserve3 -> /dev/block/sdd13
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 reserve4 -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 reserve5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 rpm_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 rpm_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 sec -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 ssd -> /dev/block/sdd2
lrwxrwxrwx 1 root root 38 1970-01-01 02:09 system -> /dev/block/bootdevice/by-name/system_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 system_a -> /dev/block/sda33
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 system_b -> /dev/block/sda34
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 tz_a -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 tz_b -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 userdata -> /dev/block/sda35
lrwxrwxrwx 1 root root 38 1970-01-01 02:09 vendor -> /dev/block/bootdevice/by-name/vendor_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 vendor_a -> /dev/block/sda31
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 vendor_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 xbl_b -> /dev/block/sdc1
Edit: NVM. Looks like the /cache partition is gone for the Pixel XL.
Do you work for the FBI?
I should also mention that I haven't been able to flash TWRP permenantly, either. I can get it to boot temporarily through fastboot but when flashing the zip in TWRP, it hangs and reboots at "Running boot image patcher on slot A". Not sure if that's because I haven't been able to get into Android and set a pin, though.
nabbed said:
Do you work for the FBI?
Click to expand...
Click to collapse
lol wut
Have you tried the Skipsoft Unified Android Toolkit? I have no association with the dev whatsoever, but I purchased the pro version, or whatever you call it, and it works flawlessly to update, install, backup, flash, etc. my Pixel.
https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my SM-G955U using Tapatalk
Edit: double-post.
I tried that out earlier today. Tried out flashing just the recovery and a 8.0 stock ROM. No joy. Doesn't even get to boot animation. Is there a particular option I should try in the pro version?
RT Wolf said:
I tried that out earlier today. Tried out flashing just the recovery and a 8.0 stock ROM. No joy. Doesn't even get to boot animation. Is there a particular option I should try in the pro version?
Click to expand...
Click to collapse
Have you tried to install factory update, using flash-all and edit flash-all by removing the -w
Make sure you open cmd and type fastboot reboot bootloader. Then just double click flash-all, a new cmd will open and just let it run, it will stop for a few minutes, let it sit, it will start again.
I know this is pretty old but im curious as to if anyone has had this problem and fixed it. Believe it or not Ive had this exact problem for a week now. This may seem like a joke when i say this but i actually fixed this by banging the phone against my knee out of frustration. I tried everything...diff boot slots, every factory image from 7 to 10, flash anything and everything in TWRP. TWRP would freeze anytime a ROM was flashed almost immediately. Factory images would never get passed the white screen with the single "G" on the sreen. Then one time i tapped the screen and the phone booted further. So i banged it against my knee and finshed the setup and made it to stock 8.1 with the bootloader locked *shrugs*
This kind of behavior looks like UFS failure. It's mostly caused by either condensation, liquid damage, or moisture. It can be none of these, and naturally happen with just time. The least you could try is putting it to a heat gun where the UFS chip is. If you live in US you can take it to a uBreakiFix center to repair, they know how to do chipset repair. If you dont, try to take a look around for shop, ask them if they know how to do chip repair.
Hey everybody,
I skimmed the threads and it seems nobody tried to extract the boot.img from a device that´s been updated to November firmware.
So at the moment there´s no easy way to root devices where users took the november firmware update already, since factory images are only available for October firmware.
TLDR: Attached to this post are boot.img and vbmeta.img of November firmware that will allow you to root your pixel 6 pro running the updated firmware.
If you´re interested how these were obtained here´s a rough guideline:
Starting point is being a Pixel 6 pro on October firmware rooted.
Taking OTA will fail as boot and vbmeta partitions are altered due to the rooted installation.
Solution: restore those partitions to stock while the device is running, take the OTA but don´t reboot (this will flash OTA to the inactive slot), backup the now updated but still inactive partitions again.
I´ll write a quick mockup how this works, but it´s for advanced users only. So if you´re not comfortable with this I´d suggest to not attempt this.
I was on slot B with October firmware as starting point.
So the goal is to restore original B partitions while the OS is running, apply OTA (which would fail if you´re running altered partitions, boot/vbmeta) and backup updated inactive slot, in my case A.
First problem: Partitions to restore while OS is running need to be unblocked via the command:
Code:
blockdev --setrw <block>
Otherwise you get this error:
Code:
1|raven:/ # dd if=/data/local/tmp/boot.img of=/dev/block/by-name/boot_b
dd: /dev/block/by-name/boot_b: write error: Operation not permitted
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.002125 s, 0 B/s
To determine which partition you need to unblock run:
Code:
126|raven:/ # cd dev/block/platform/14700000.ufs/by-name/
raven:/dev/block/platform/14700000.ufs/by-name # ls -al
total 0
drwxr-xr-x 2 root root 1020 2021-10-28 21:58 .
drwxr-xr-x 3 root root 1120 2021-10-28 21:58 ..
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 abl_a -> /dev/block/sdb5
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 abl_b -> /dev/block/sdc5
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 bl1_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 bl1_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 bl2_a -> /dev/block/sdb3
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 bl2_b -> /dev/block/sdc3
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 bl31_a -> /dev/block/sdb6
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 bl31_b -> /dev/block/sdc6
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 boot_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 boot_b -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 devinfo -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 dpm_a -> /dev/block/sdb10
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 dpm_b -> /dev/block/sdc10
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 dram_train_a -> /dev/block/sdb4
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 dram_train_b -> /dev/block/sdc4
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 dtbo_a -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 dtbo_b -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 efs -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 efs_backup -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 fips -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 frp -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 gsa_a -> /dev/block/sdb8
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 gsa_b -> /dev/block/sdc8
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 klog -> /dev/block/sda2
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 ldfw_a -> /dev/block/sdb9
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 ldfw_b -> /dev/block/sdc9
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 metadata -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 mfg_data -> /dev/block/sdd2
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 modem_a -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 modem_b -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 modem_userdata -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 pbl_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 pbl_b -> /dev/block/sdc2
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 persist -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 pvmfw_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 pvmfw_b -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 super -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 tzsw_a -> /dev/block/sdb7
lrwxrwxrwx 1 root root 15 2021-10-28 21:58 tzsw_b -> /dev/block/sdc7
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 userdata -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vbmeta_a -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vbmeta_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vbmeta_system_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vbmeta_system_b -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vbmeta_vendor_a -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vbmeta_vendor_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vendor_boot_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 2021-10-28 21:58 vendor_boot_b -> /dev/block/sda19
Example how to restore changed partitions: (if you flashed a modified boot.img and vbmeta.img to root, you need to restore those two while the device is running otherwise the OTA will fail.)
Code:
raven:/ # blockdev --setrw /dev/block/sda21
raven:/ # dd if=/data/local/tmp/boot.img of=/dev/block/by-name/boot_b
131072+0 records in
131072+0 records out
67108864 bytes (64 M) copied, 8.790461 s, 7.2 M/s
This will restore boot_b to the original one so that partition won´t fail to apply the incremental OTA to.
After the OTA was successfully flashed we want to backup the updated boot slot. That would be boot_a in my case.
Command for doing so:
Code:
dd if=/dev/block/bootdevice/by-name/boot_a of=/storage/emulated/0/boot_a.img
I backed up november boot.img and vbmeta.img that way. Please note that I had to flash vbmeta again and disable verity to obtain those imgs. OTA won´t flash if partitions are altered in any way. This wiped my device.
Attached to this post are completely stock boot.img and vbmeta.img from the November build I´m on.
This will allow people to root their devices on November firmware if they took the OTA.
Please note that those boot.imgs are from build SD1A.210817.036.
It´s a european Pixel 6 pro. I don´t think there should be a difference to the factory images from the other carriers like verizon etc regarding the boot.img. If you want to be absolutely sure, somebody on a different firmware needs to follow this process or we just wait for the factory images with nov security patch to drop.
That's the firmware I'm currently running.
I can confirm it works with the provided November vbmeta / boot images.
Thank you !!
Thibale said:
I can confirm it works with the provided November vbmeta / boot images.
Thank you !!
Click to expand...
Click to collapse
thanks for reporting back
So you had to wipe data to Root the October stock firmware and then wipe again to upgrade to November firmware?
Nekromantik said:
So you had to wipe data to Root the October stock firmware and then wipe again to upgrade to November firmware?
Click to expand...
Click to collapse
Yes, but due to the process I used to obtain boot.img and vbmeta.img if you read through the first post.
Pixel 5 process for updating, once full OTA/factory images are available like usual, will make that redundant.
(after initial vbmeta wipe)
Great job @Freak07 nice to see you've joined us
Thanks for this tutorial. But its also very annoying that you can't update the system while rooted lol
So it there's no way to update once rooted without wiping?
I used to download factory images and do flash all bat minus the -w flag.
Cares said:
So it there's no way to update once rooted without wiping?
I used to download factory images and do flash all bat minus the -w flag.
Click to expand...
Click to collapse
No confirmed way for this phone yet. When the new factory images (likely .036 or maybe another one) are released on Monday, people who are currently rooted on .015 can update and see if the manual OTA installation method works without having to wipe. I guess there have been mixed results with this method on the Pixel 5.
Man having to wipe every update might be a deal breaker for me. Might resort to locking bootloader if that's the case.
Cares said:
Man having to wipe every update might be a deal breaker for me. Might resort to locking bootloader if that's the case.
Click to expand...
Click to collapse
Yeah, sad to say it might be for me too. I'm unrooted at the moment (had already set up on the 26th so didn't want to wipe and do it all over again) so we'll see how long I can stand it.
Can't believe I'm actually saying this
Cares said:
Man having to wipe every update might be a deal breaker for me. Might resort to locking bootloader if that's the case.
Click to expand...
Click to collapse
Unfortunately the same for me. I have been going back and forth between unlocking or not. Even if the work around can be used on the P6 it is really more involved than I want it to be and not something I really want to do every month. Really disappointing Google has made it such a pain.
I don't mind any amount of workaround, as long as it's stable, consistent, and doesn't require wiping every time.
roirraW edor ehT said:
I don't mind any amount of workaround, as long as it's stable, consistent, and doesn't require wiping every time.
Click to expand...
Click to collapse
Yeah, flashing OTAs & factory images with the -w removed, disabling dm-verity, patching boot images, etc., I don't mind at all. I like doing that stuff. But I don't like having to wipe and set up anew every month. That just might break this old man's back
Agree, wiping all the time is not my idea of ota update fun!
galaxys said:
Agree, wiping all the time is not my idea of ota update fun!
Click to expand...
Click to collapse
I got so used to it with the S21 Ultra. Backups restore pretty quick (google backups)
You got the phone...Nice!
Hope all is well buddy!
Ok, time for a dumb question. If I unlock my bootloader, but don't root, my device will still break the basic integrity of safety net, correct?
mkhcb said:
Ok, time for a dumb question. If I unlock my bootloader, but don't root, my device will still break the basic integrity of safety net, correct?
Click to expand...
Click to collapse
Yes