So I got a new Samsung Galaxy S5 today (SM-G900F). I've rooted plenty of devices before and never really had any issues. I found this thread: http://forum.xda-developers.com/showthread.php?t=2696537 explaining how to root my particular device. Odin says it succeeded in rooting, but my phone wont boot up. I can still get into download mode (Power+Home+Volume Down) and repeat the process, but no matter how many times I do it and it says "Succeeded" on Odin, it doesn't work. I'm heartbroken, thinking I've already bricked it beyond repair. It wont even show me the Samsung boot logo.
This is what it says when I boot into download mode:
http://imgur.com/seCETPj
This is what it says when I try to boot the phone normally, after this screen with the message in the top left corner it just turns black and stays black:
http://imgur.com/yQeAVvq
(Sorry for the blurry picture, it's only there for a second)
Anyone... Anyone at all that can give me some advice on how to fix this?
Flash a stock ROM from sammobile .com to it using ODIN again
Root by flashing TWRP 2.8.7.0 with ODIN, and then SuperSU from TWRP recovery if you can't root with CF
*Detection* said:
Flash a stock ROM from sammobile .com to it using ODIN again
Root by flashing TWRP 2.8.7.0 with ODIN, and then SuperSU from TWRP recovery if you can't root with CF
Click to expand...
Click to collapse
Thanks a bunch, I'll try this!
How do I know which firmware I should download from sammobile? Are all of them (listed under SM-G900F) compatible?
Also; when flashing TWRP is it the .img.tar file I flash, or do I extract it so it's just .img before I flash? Such confused.
RowBan said:
Thanks a bunch, I'll try this!
How do I know which firmware I should download from sammobile? Are all of them (listed under SM-G900F) compatible?
Click to expand...
Click to collapse
Some of the variants have the same partition table. So you can root it if your phone is a variant of G900F or G900F itself.
This is the partition table of G900F and it is also same partition table for G900FQ so all variants of G900F have the same partition table:
Code:
lrwxrwxrwx root root 2014-02-05 02:43 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-02-05 02:43 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-02-05 02:43 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-02-05 02:43 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-02-05 02:43 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-02-05 02:43 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-02-05 02:43 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-02-05 02:43 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-02-05 02:43 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-02-05 02:43 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-02-05 02:43 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-02-05 02:43 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-02-05 02:43 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-02-05 02:43 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-02-05 02:43 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-02-05 02:43 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-02-05 02:43 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-02-05 02:43 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-02-05 02:43 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-02-05 02:43 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-02-05 02:43 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-02-05 02:43 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-02-05 02:43 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-02-05 02:43 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-02-05 02:43 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-02-05 02:43 userdata -> /dev/block/mmcblk0p26
undercontr said:
Some of the variants have the same partition table. So you can root it if your phone is a variant of G900F or G900F itself.
This is the partition table of G900F and it is also same partition table for G900FQ so all variants of G900F have the same partition table:
Code:
lrwxrwxrwx root root 2014-02-05 02:43 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-02-05 02:43 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-02-05 02:43 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-02-05 02:43 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-02-05 02:43 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-02-05 02:43 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-02-05 02:43 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-02-05 02:43 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-02-05 02:43 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-02-05 02:43 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-02-05 02:43 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-02-05 02:43 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-02-05 02:43 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-02-05 02:43 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-02-05 02:43 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-02-05 02:43 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-02-05 02:43 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-02-05 02:43 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-02-05 02:43 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-02-05 02:43 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-02-05 02:43 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-02-05 02:43 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-02-05 02:43 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-02-05 02:43 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-02-05 02:43 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-02-05 02:43 userdata -> /dev/block/mmcblk0p26
Click to expand...
Click to collapse
I thank you for your effort, but this is way too technical for me. I have no idea what any of the stuff you said means
I did check the model number in "About Device" before I tried though, and it most definitely said "SM-G900F". I also most definitely followed and downloaded the CF-Auto Root for the SM-G900F. I wouldn't mess up on that I think it got bricked because the firmware on my SM-G900F was 5.x.x and the CF-Auto Root was made for 4.4, but nowhere in the guide did it say this would be an issue
RowBan said:
I thank you for your effort, but this is way too technical for me. I have no idea what any of the stuff you said means
Click to expand...
Click to collapse
Okay then I'll keep it simple. ODIN is a good way to flash stock rom or another files but I suggest you to use Kies3 itself. Use "Firmware Upgrade and Initialisation" under Tools section. It will ask your Model Name and S/N which means Serial Number. It can be found in a sticker which sticked to phone under battery. You can use this method to install stock ROM.
undercontr said:
Okay then I'll keep it simple. ODIN is a good way to flash stock rom or another files but I suggest you to use Kies3 itself. Use "Firmware Upgrade and Initialisation" under Tools section. It will ask your Model Name and S/N which means Serial Number. It can be found in a sticker which sticked to phone under battery. You can use this method to install stock ROM.
Click to expand...
Click to collapse
I'll give Kies3 a go first then
RowBan said:
I thank you for your effort, but this is way too technical for me. I have no idea what any of the stuff you said means
I did check the model number in "About Device" before I tried though, and it most definitely said "SM-G900F". I also most definitely followed and downloaded the CF-Auto Root for the SM-G900F. I wouldn't mess up on that I think it got bricked because the firmware on my SM-G900F was 5.x.x and the CF-Auto Root was made for 4.4, but nowhere in the guide did it say this would be an issue
Click to expand...
Click to collapse
Are you sure it was this file: "CF-Auto-Root-klte-kltedx-smg900f.zip" ? or it was "CF-Auto-Root-klte-kltexx-smg900f.zip". kltedx is for 5.0 and kltexx is for 4.4.2. Try and root again with kltedx.
undercontr said:
Are you sure it was this file: "CF-Auto-Root-klte-kltedx-smg900f.zip" ? or it was "CF-Auto-Root-klte-kltexx-smg900f.zip". kltedx is for 5.0 and kltexx is for 4.4.2. Try and root again with kltedx.
Click to expand...
Click to collapse
It was, as you mentioned, the kltexx file that is for 4.4.2. I didn't realize they had updated it on their website but not reflected this in the guide I was following. Thank you enormously for discovering this. I will try rooting with the updated one!
Still doesn't seem to work, but now it just stucks at this screen instead of going entirely black:
http://imgur.com/yQeAVvq
RowBan said:
It was, as you mentioned, the kltexx file that is for 4.4.2. I didn't realize they had updated it on their website but not reflected this in the guide I was following. Thank you enormously for discovering this. I will try rooting with the updated one!
Still doesn't seem to work, but now it just stucks at this screen instead of going entirely black:
http://imgur.com/yQeAVvq
Click to expand...
Click to collapse
I'm sorry to hear that. So you have to return stock ROM then install CF-Auto-Root with kltedx version. Hopefully it will work. Actually I would downgrade my phone to 4.4.2, root it and install CyanogenMod with Android 6.0 Marshmellow. But that's your choice of course.
undercontr said:
I'm sorry to hear that. So you have to return stock ROM then install CF-Auto-Root with kltedx version. Hopefully it will work. Actually I would downgrade my phone to 4.4.2, root it and install CyanogenMod with Android 6.0 Marshmellow. But that's your choice of course.
Click to expand...
Click to collapse
Will attempt to do that via Kies3 as you suggested.
Can't I just flash TWRP via Odin right now, and then flash CyanogenMod? My endgame with this is to get CyanogenMod
RowBan said:
Thanks a bunch, I'll try this!
How do I know which firmware I should download from sammobile? Are all of them (listed under SM-G900F) compatible?
Also; when flashing TWRP is it the .img.tar file I flash, or do I extract it so it's just .img before I flash? Such confused.
Click to expand...
Click to collapse
Just pick G900F and then your region from the dropdown, and choose any you like, the ones at the top are the newest (Lollipop)
And yes, flash the .TAR with ODIN, from the PDA or AP section
That's it (Might need to boot into recovery and factory reset / Wipe DATA to get it to boot)
---------- Post added at 23:26 ---------- Previous post was at 23:25 ----------
RowBan said:
Will attempt to do that via Kies3 as you suggested.
Can't I just flash TWRP via Odin right now, and then flash CyanogenMod? My endgame with this is to get CyanogenMod
Click to expand...
Click to collapse
Yea you probably could, once you are in TWRP, wipe and format everything (Not the external SD where the CyanogenMod ROM is though)
Then flash away
*Detection* said:
Just pick G900F and then your region from the dropdown, and choose any you like, the ones at the top are the newest (Lollipop)
And yes, flash the .TAR with ODIN, from the PDA or AP section
That's it (Might need to boot into recovery and factory reset / Wipe DATA to get it to boot)
---------- Post added at 23:26 ---------- Previous post was at 23:25 ----------
Yea you probably could, once you are in TWRP, wipe and format everything (Not the external SD where the CyanogenMod ROM is though)
Then flash away
Click to expand...
Click to collapse
I'll just have to try all available things until I find something that works then. Currently trying to reset original rom with Kies3 as undercontr suggested I do. It takes time though, my internet is super slow and Kies3 is weird. Having to have my phone plugged in in download mode WHILE it downloads the ROM :'( Does it take charge from the USB while in Download Mode? Afraid it'll run out of battery
RowBan said:
I'll just have to try all available things until I find something that works then. Currently trying to reset original rom with Kies3 as undercontr suggested I do. It takes time though, my internet is super slow and Kies3 is weird. Having to have my phone plugged in in download mode WHILE it downloads the ROM :'( Does it take charge from the USB while in Download Mode? Afraid it'll run out of battery
Click to expand...
Click to collapse
KIES is a useless PoS, I'd get rid of it, and also uninstall it for using ODIN, as it can cause problems
Yea it will likely be charging while in download mode, or any mode, as long as it's connected to USB
If it hasn't started the flashing yet, I'd just quit KIES and go straight for the ODIN / TWRP option
10x quicker and 10x more reliable
*Detection* said:
KIES is a useless PoS, I'd get rid of it, and also uninstall it for using ODIN, as it can cause problems
Yea it will likely be charging while in download mode, or any mode, as long as it's connected to USB
If it hasn't started the flashing yet, I'd just quit KIES and go straight for the ODIN / TWRP option
10x quicker and 10x more reliable
Click to expand...
Click to collapse
I ended up letting Kies3 restore my original ROM, flashed TWRP and SuperSU after that.
Undercontr, there seems to be a lot of issues with the CyanogenMod 6.0 marshmallow! Not sure I want to give it a go
Anyway! A huge thanks to the both of you! I would've fixed this myself eventually, but I panicked. Having the support of fellas like you just makes it all a lot easier to handle.
Related
Hi all,
After trying to flash the new 016s for x829 on my x820, I noticed that after the wipes, the rom would not install. The failure of /cust cannot be mounted appears and the rom installation doesn't go any futher.
The 015s TeamSpain Pure Edition it's installing by the way without any problem, although "Failed to mount /cust (invalid argument) is shown as well. Now I'm kind of stuck on this ROM (luckily I have a ROM).
Any suggestions or solution?
Regards,
Vali
Edit: looks like the stock 015s also fails to install now.
Same problem here, i cant update to x829 version.
Miyagi said:
Same problem here, i cant update to x829 version.
Click to expand...
Click to collapse
So finally as other users suggested, it's due to the chinese version of TWRP. Try to install the TWRP 5.8 by TeaMSpaiN and it will work. Today I have installed 016s for x829 and it is working very well.
All in all, the /cust mounting problem is due to the chinese version of recovery that searches for this folder but it doesn't find it because it doesn't exist. With a modified TWRP, you won't have this problem.
Dear,
I have the same problem my phone bootloop with lineage and is waiting start.
I try to push TWRP 5.8 TeaMSpaiN with sideload function in TWRP but doesn't works.
Could you help me ?
Ludovicbzh said:
Dear,
I have the same problem my phone bootloop with lineage and is waiting start.
I try to push TWRP 5.8 TeaMSpaiN with sideload function in TWRP but doesn't works.
Could you help me ?
Click to expand...
Click to collapse
enter fastboot then look at:
https://forum.xda-developers.com/showthread.php?p=71553770
post #100
Gesendet von meinem LEX820 mit Tapatalk
Hello Everyone When I Flash Any Custom Recovery In My Phone It Shows Failed To Mount Cust And Failed To Mount persist Please Help Me What I Can Do In That Situation otherwise I Lost My Phone conpletely
Vinitkumar98 said:
Hello Everyone When I Flash Any Custom Recovery In My Phone It Shows Failed To Mount Cust And Failed To Mount persist Please Help Me What I Can Do In That Situation??? otherwise I Lost My Phone conpletely
Click to expand...
Click to collapse
Try to flash the official one. I don't believe that "any custom recovery" does that.
Heyyo, err @Vinitkumar98, I don't think x2 even hast a "cust" partition...
Code:
le_x2:/dev/block/platform/soc/624000.ufshc/by-name # ls
aboot cmnlibbak fsg letvsecure pmicbak system
abootbak ddr fsg_gap mdtp recovery tz
apdp devcfg hyp misc recoveryconfig tzbak
bluetooth devcfgbak hypbak modem reserve userdata
boot devinfo kernellog modemst1 rootconfig vendor
bootconfig dip keymaster modemst1_gap rpm xbl
cache dpo keymasterbak modemst2 rpmbak xblbak
cdt dsp keystore modemst2_gap sec
cmnlib factory letvconfig msadp splash
cmnlib64 frp letveui persist ssd
cmnlib64bak fsc letvreserve pmic sti
As you can see, it doesn't appear on our partition table.
Can you please provide more information as to why you wanted to access a cust partition?
Hey guys,
just a few hours ago i restarted my Moto G4 Plus to update my Xposed. The screen turned black and nothing happened. Now just the led flashes when its connected to the computer. It was detected as qhsusb_bulk in device manager, I installed some drivers, now i got it to Qualcomm HS-USB QDLoader 9008.
Anyone has experienced this yet and found solutions which dosent refer to the service center?
Thanks for your help
Edit:
Solved it by flashing the blankflash.bat and then holding Power + Vol Down for more than 60 seconds. Now my logo.bin seems to be lost (bootloader unlocked warning appears). Dont know why it works again but well...
http://www.allfreeperks.in/2015/09/unbrick-how-to-unbrick-and-repair-moto.html?m=1
Try to grab instructions from above link. I had this situation and got it fixed with blankflash.bat however that command ended with error. But still it fixed my bootloader.
You need to run blankflash.bat file. There after put your phone on AC charger. If it starts showing battery charging led then your bootloader is fixed.
Flashed it, it flashed something and ended in an error as you said. But when i put it on the original AC-Charger nothing happens except the white led is blinking about once a second
Edit: I tried to flash it a second time, i'm getting different results but the bootloader still seems to be broke, the led is still blinking once a second
First result:
Code:
C:\Users\Admin\Downloads\blankflash\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.007s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.007s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.006s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.007s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Second result:
Code:
C:\Users\Admin\Downloads\blankflash\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM11
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0xXXXXXXX
...chip-id = 0xXXX
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.005s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.004s]
validating files
OKAY [ 0.001s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.003s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
Unbrick said:
Hey guys,
just a few hours ago i restarted my Moto G4 Plus to update my Xposed. The screen turned black and nothing happened. Now just the led flashes when its connected to the computer. It was detected as qhsusb_bulk in device manager, I installed some drivers, now i got it to Qualcomm HS-USB QDLoader 9008.
Anyone has experienced this yet and found solutions which dosent refer to the service center?
Thanks for your help
Click to expand...
Click to collapse
Did you try flash xposed-disabler?
http://dl-xda.xposed.info/framework/uninstaller/
Did you try flash xposed-disabler?
http://dl-xda.xposed.info/framework/uninstaller/
Click to expand...
Click to collapse
The phone isnt booting, nor recovery neither download mode
Unzip that blankflash.zip and execute qboot.exe. There after Put on charger for about 20-30mins. Unplug and try to power on.
==vj== said:
Unzip that blankflash.zip and execute qboot.exe. There after Put on charger for about 20-30mins. Unplug and try to power on.
Click to expand...
Click to collapse
Just running the qboot itself only displays the help. When i execute it with the param "qboot.exe blank-flash" it flashes something, the result can be seen in post 3. Flashed it again, now my phone is on charger. Lets wait.
Well, nothing happened. While the phone is on AC-charger the led still blinks white about once a second but it doesent boot up. Also the screen isnt turning on.
Wish I only get to the boot loader...
Unbrick said:
Hey guys,
just a few hours ago i restarted my Moto G4 Plus to update my Xposed. The screen turned black and nothing happened. Now just the led flashes when its connected to the computer. It was detected as qhsusb_bulk in device manager, I installed some drivers, now i got it to Qualcomm HS-USB QDLoader 9008.
Anyone has experienced this yet and found solutions which dosent refer to the service center?
Thanks for your help
Edit:
Solved it by flashing the blankflash.bat and then holding Power + Vol Down for more than 60 seconds. Now my logo.bin seems to be lost (bootloader unlocked warning appears). Dont know why it works again but well...
Click to expand...
Click to collapse
I tried blankflash, and I only get the first output you showed that downloads nothing, greetings only and ends with packet read error. I then tried pressing power + vol_down for more than 60 seconds but nothing happens!
Any help will be so much appreciated. Attached is how my Windows 8.1 sees XT1642.
MK+2017 said:
I tried blankflash, and I only get the first output you showed that downloads nothing, greetings only and ends with packet read error. I then tried pressing power + vol_down for more than 60 seconds but nothing happens!
Any help will be so much appreciated. Attached is how my Windows 8.1 sees XT1642.
Click to expand...
Click to collapse
Might be worth having a look at this post by ICrD512 https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 and the subsequent posts in this thread, see if they'd get your device recognised. Good luck
echo92 said:
Might be worth having a look at this post by ICrD512 https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 and the subsequent posts in this thread, see if they'd get your device recognised. Good luck
Click to expand...
Click to collapse
Can't tell how much I want to thank you! Into hell and back. I was just looking for that one singleimage.bin.
Only now I'm back to my original problem I technically screwed up my SIM slot because I have knowledge (yes believe it!), I was following instructions on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and Motorola says you need to flash motoboot.img, which was not present in the downloaded stock archive.
Since I know people commit typos, I corrected that for them and screwed my SIM: I flashed the bootloader.img of MPJ24.139-64 which caused my SIM die. To add disaster to malfunction (I did not instantly notice SIM died), I went into a flashing frenzy which locked me right now with the GPT.bin of NPJ25.93-14!
My SIM is still dead. If there is anyway out of it, I can't be more thankful!
MK+2017 said:
Can't tell how much I want to thank you! Into hell and back. I was just looking for that one singleimage.bin.
Only now I'm back to my original problem I technically screwed up my SIM slot because I have knowledge (yes believe it!), I was following instructions on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and Motorola says you need to flash motoboot.img, which was not present in the downloaded stock archive.
Since I know people commit typos, I corrected that for them and screwed my SIM: I flashed the bootloader.img of MPJ24.139-64 which caused my SIM die. To add disaster to malfunction (I did not instantly notice SIM died), I went into a flashing frenzy which locked me right now with the GPT.bin of NPJ25.93-14!
My SIM is still dead. If there is anyway out of it, I can't be more thankful!
Click to expand...
Click to collapse
Oof, that's a tricky combo. If you go into your bootloader, what version has it ended up on? If I've read your post right, you flashed the NPJ24.139-64 build (think that's the US build), does your device still see a baseband version reported under Settings>About Phone?
I wonder if a full flash of a stock ROM might restore your SIM. This MPJ24.139-63/64 MM ROM (https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695) flashes successfully on my XT 1642 and updated to Nougat okay (i'm in the UK though, I've read that it's flashed on EU XT 1642 devices okay, not sure about other territorities), but you'd want to omit the commands 'fastboot flash partition gpt.bin' and 'fastboot flash bootloader bootloader.img' especially if you're downgrading from a Nougat flash.
Alternatively, as you've updated your GPT partition to Nougat, you could look into flashing the NPJ25.93-14 stock Nougat ROM, see if the firmware might be able to restore your SIM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Those are a few things I can think of, maybe someone else will have more of an idea? Good luck either way!
echo92 said:
Oof, that's a tricky combo. If you go into your bootloader, what version has it ended up on? If I've read your post right, you flashed the NPJ24.139-64 build (think that's the US build), does your device still see a baseband version reported under Settings>About Phone?
I wonder if a full flash of a stock ROM might restore your SIM. This MPJ24.139-63/64 MM ROM (https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695) flashes successfully on my XT 1642 and updated to Nougat okay (i'm in the UK though, I've read that it's flashed on EU XT 1642 devices okay, not sure about other territorities), but you'd want to omit the commands 'fastboot flash partition gpt.bin' and 'fastboot flash bootloader bootloader.img' especially if you're downgrading from a Nougat flash.
Alternatively, as you've updated your GPT partition to Nougat, you could look into flashing the NPJ25.93-14 stock Nougat ROM, see if the firmware might be able to restore your SIM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Those are a few things I can think of, maybe someone else will have more of an idea? Good luck either way!
Click to expand...
Click to collapse
Thank you for the reply. Maybe I can add to your information when I tell you that despite I have the GPT.bin of NPJ25.93-14, I can still flash older bootloaders, and they do boot, without issues!
And yes, you are right. Baseband changes whenever I flash a new bootloader. Right now it is something_EMEA_DSDS_Cust, and that is the bootloader of NPJ25.93-14.
I have tried many backward flashing, without GPT.bin and without bootloader. None helped. I even tried TWRP flashable radio files of user Q9Nap (removed now since others complained) but none helped.
At this very moment, I went on and flashed the very first build I got from factory: MPJ24.139-23.4. I will try later to capture the OTA I'm downloading and see if I can play with it to beat SIM.
Thank you all the way
MK+2017 said:
Thank you for the reply. Maybe I can add to your information when I tell you that despite I have the GPT.bin of NPJ25.93-14, I can still flash older bootloaders, and they do boot, without issues!
And yes, you are right. Baseband changes whenever I flash a new bootloader. Right now it is something_EMEA_DSDS_Cust, and that is the bootloader of NPJ25.93-14.
I have tried many backward flashing, without GPT.bin and without bootloader. None helped. I even tried TWRP flashable radio files of user Q9Nap (removed now since others complained) but none helped.
At this very moment, I went on and flashed the very first build I got from factory: MPJ24.139-23.4. I will try later to capture the OTA I'm downloading and see if I can play with it to beat SIM.
Thank you all the way
Click to expand...
Click to collapse
All failed. The OTA I captured is that for US. It even went up to Nougat. But still no SIM. When I read the version on my phone's package, it reads: XT1642.RETAIL.WHT.MOTO G Plus.EGYPT.16GB.DS
So, I'm just guessing, what I really need is the bootloader of an EGYPTIAN phone!!
Anyone from Egypt?
@echo92: I just made sure of the reason; I lost IMEI numbers. I was using the wrong code, instead of *#06# to get the IMEI pop-up which says IMEI 0.
I'm now sure it is only up to IMEI change/restore, and I read about that somewhere but I can't recall the thread/URL/Location.
Any clue?
MK+2017 said:
@echo92: I just made sure of the reason; I lost IMEI numbers. I was using the wrong code, instead of *#06# to get the IMEI pop-up which says IMEI 0.
I'm now sure it is only up to IMEI change/restore, and I read about that somewhere but I can't recall the thread/URL/Location.
Any clue?
Click to expand...
Click to collapse
Was it this thread by any chance: https://forum.xda-developers.com/moto-g4-plus/help/imei-0-t3476876/
I saw this post about reflashing your modem, which might be useful. https://forum.xda-developers.com/showpost.php?p=69082823&postcount=24 I imagine you'd have to pull a NON-HLOS.bin from a EMEA ROM (perhaps the MM or Nougat ROMs) and flash to restore your IMEI?
echo92 said:
Was it this thread by any chance: https://forum.xda-developers.com/moto-g4-plus/help/imei-0-t3476876/
I saw this post about reflashing your modem, which might be useful. https://forum.xda-developers.com/showpost.php?p=69082823&postcount=24 I imagine you'd have to pull a NON-HLOS.bin from a EMEA ROM (perhaps the MM or Nougat ROMs) and flash to restore your IMEI?
Click to expand...
Click to collapse
I fee defeated. I also feel sorry for myself. I also feel angry. I wish I had the chance to dd every single partition on this phone and post the files everywhere I'm able to just to get even with Motorola. This is humiliation.
I called their support. They have no service centers in Egypt. The vendor that imported the device is having it supported by unknown subsidiaries. Motorola's support said I would need to ship the phone to UK (only for board replacement, not flashing).
Hell, no. I can only resort to hardware-smacking this thing. The price tag here is Egypt is ~ 15 USD, and I was promised by one shop that they can fix IMEI for me.
I have to tell you, I scarcely slept yesterday. I was flashing and reflashing MPJ24.23-4 just to be able to install Xposed, then Xposed IMEI Changer. SIM worked for few dreamy seconds before it vaporized just as I hit Cellular Networks settings section! Such a waste of time and effort.
About your question, the thread is not mine, and it looks so much similar to what I have. No fun though. Thank you for being here for me.
MK+2017 said:
I fee defeated. I also feel sorry for myself. I also feel angry. I wish I had the chance to dd every single partition on this phone and post the files everywhere I'm able to just to get even with Motorola. This is humiliation.
I called their support. They have no service centers in Egypt. The vendor that imported the device is having it supported by unknown subsidiaries. Motorola's support said I would need to ship the phone to UK (only for board replacement, not flashing).
Hell, no. I can only resort to hardware-smacking this thing. The price tag here is Egypt is ~ 15 USD, and I was promised by one shop that they can fix IMEI for me.
I have to tell you, I scarcely slept yesterday. I was flashing and reflashing MPJ24.23-4 just to be able to install Xposed, then Xposed IMEI Changer. SIM worked for few dreamy seconds before it vaporized just as I hit Cellular Networks settings section! Such a waste of time and effort.
About your question, the thread is not mine, and it looks so much similar to what I have. No fun though. Thank you for being here for me.
Click to expand...
Click to collapse
That's annoying, I'd have thought Motorola would have a regional service centre closer to you rather than requesting you send all the way over to the UK...
Any luck with the shop?
Ahh, my apologies for the confusion - I meant it was a thread that looked similar to yours (and very recently a new one turned up similar to yours https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-xt1644-imei-0-stock-flash-t3579697)
I'm wondering if flashing either of these stock ROMS (XT 1642, MPJ24.139-48) might work? http://www.filefactory.com/file/5dr...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
Good luck either way - I can only imagine how frustrating this is
echo92 said:
That's annoying, I'd have thought Motorola would have a regional service centre closer to you rather than requesting you send all the way over to the UK...
Any luck with the shop?
Ahh, my apologies for the confusion - I meant it was a thread that looked similar to yours (and very recently a new one turned up similar to yours https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-xt1644-imei-0-stock-flash-t3579697)
I'm wondering if flashing either of these stock ROMS (XT 1642, MPJ24.139-48) might work? http://www.filefactory.com/file/5dr...PJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
Good luck either way - I can only imagine how frustrating this is
Click to expand...
Click to collapse
Thank you once again. The firmware MPJ24.139-48 that has links around did not help before. I tired it.
About the shop, I just went today for repair. While waiting, I felt I had to get a sneak look on the technicians monitor to see which tool he is using. Please, no laughing, I found him browsing XDA Forums for stock images :laugh:
I told him that I have been roaming here crazy for like a week. He asked when you know more than I do, why did you bring me the phone? I told him I thought he had a tool box
Anyway, since the place is smartphone mall, I asked at other shops. i found the best one, which had "many toolboxes" and promised to fix my phone. I left the phone with them. Still trying!
Now, in case all my efforts end fruitless, if I go for this idea:
1- buy a new phone of the same model, from the same shop where I bought my first.
2- Unlock bootloader.
3- Boot TWRP on the fly (without flashing)
4- dd every single partition on the phone.
5- copy dd images to PC.
6- get my IMEI-dead set and... you see the picture!
Questions:
1- Would that work first place?
2- If it works, would the 2 sets be sharing the same dual IMEIs?
3- Apart from IMEI, which partitions do I really need/need not to flash to get away with this?
All comments are welcome!
---------- Post added at 10:44 PM ---------- Previous post was at 10:32 PM ----------
This might help with the cloning idea!
Original partition listing of *my* working XT1642:
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 aboot -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 abootbak -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 boot -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 cache -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 cid -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 clogo -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 cmnlib -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 config -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 customize -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 devcfg -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 dip -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 frp -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 hw -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 keymaster -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 kpan -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 limits -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 logo -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 logs -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 metadata -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 mota -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 oem -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 padC -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 persist -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 sp -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 syscfg -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 system -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-17 09:44 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 userdata -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 utags -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-17 09:44 utagsBackup -> /dev/block/mmcblk0p22
And, now I notice something from the TWRP backup log (attached, the backup that I took before messing up all things up, which had only bootloader unlocked, TWRP flashed and LineageOS installed and running):
- TWRP is naming the MODEM partition FIRMWARE. Does this have any possible side effects?
- I do not have the set now since I left it at repair shop, but I think I recall seeing a new FIRMWARE partition when I list partitions, one that did not exist before as outlined above?
Bump!
---------- Post added at 11:33 PM ---------- Previous post was at 11:14 PM ----------
/firmware | /dev/block/mmcblk0p1 | Size: 94MB Used: 69MB Free: 24MB Backup Size: 69MB
Flags: Can_Be_Mounted Can_Be_Wiped IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: firmware
Storage_Name: firmware
Backup_Path: /firmware
Backup_Name: firmware
Backup_Display_Name: firmware
Storage_Path: /firmware
Current_File_System: ext4
Fstab_File_System: vfat
Backup_Method: files
Since I know from partition listing that /dev/block/mmcblk0p1 is the MODEM partition, does this mean I have a copy of my original modem in my TWRP backup? Does it mean anything to my sought fix?
I have reasons to suspect one or more partitions on my 6p might be corrupted. It'd be really helpful if you could provide the md5 checksums of aboot hyp rpm sbl1 tz modem vendor partitions on your 6p.
These partitions are not device-specific, and it'd help me to confirm if mine are corrupted. I'm currently on latest bootloader (03.68), radio (03.81), and vendor (N2G48B). Thank you!
To produce the checksums (your devices needs to be rooted):
Code:
adb shell
su
cd /dev/block/platform/soc.0/f9824900.sdhci/by-name
md5sum aboot hyp rpm sbl1 tz modem vendor
Sample output:
Code:
40a124cf7639f2df76177caa928dcab8 aboot
ad078da30c62fa381d3ff4c4f2c777f2 hyp
dc89c49770ce82bd0f7c386502aeca65 rpm
616be46fc4194d7514ef7fb94df03cd5 sbl1
907f3159c87d7e90535cc6d8787678b8 tz
55593fba034c00fa9eafb110e5f240e1 modem
5f94e55262a83775ff0b5c8816d96e53 vendor
AncientDeveloper said:
I have reasons to suspect one or more partitions on my 6p might be corrupted. It'd be really helpful if you could provide the md5 checksums of aboot hyp rpm sbl1 tz modem vendor partitions on your 6p.
These partitions are not device-specific, and it'd help me to confirm if mine are corrupted. I'm currently on latest bootloader (03.68), radio (03.81), and vendor (N2G48B). Thank you!
To produce the checksums (your devices needs to be rooted):
Sample output:
Click to expand...
Click to collapse
dad3ecd226eb518d9b45a1613b0eedbf aboot
5d8af3eebdcf78916a2f38057d88531f hyp
efd09b18ba26d419228fb8d784223e84 rpm
1ddbbe3dbe4056595b4536237b3f2bd5 sbl1
31df78276a97b9e82b443ec83fb96c71 tz
18c647f962e81227439fba0130222b04 modem
43c5d48654c8f3a3f82c96d022610f67 vendor
DEVILOPS 007 said:
dad3ecd226eb518d9b45a1613b0eedbf aboot
5d8af3eebdcf78916a2f38057d88531f hyp
efd09b18ba26d419228fb8d784223e84 rpm
1ddbbe3dbe4056595b4536237b3f2bd5 sbl1
31df78276a97b9e82b443ec83fb96c71 tz
18c647f962e81227439fba0130222b04 modem
43c5d48654c8f3a3f82c96d022610f67 vendor
Click to expand...
Click to collapse
Thank you. Are you also on latest bootloader/radio/vendor?
AncientDeveloper said:
Thank you. Are you also on latest bootloader/radio/vendor?
Click to expand...
Click to collapse
I'm on the latest vendor but only just noticed the radio and bootloader updated to 3.84 and 3.73. I'm at work currently but once I get I home I'll fastboot flash them and get you an updated output.
DEVILOPS 007 said:
I'm on the latest vendor but only just noticed the radio and bootloader updated to 3.84 and 3.73. I'm at work currently but once I get I home I'll fastboot flash them and get you an updated output.
Click to expand...
Click to collapse
I just double checked the latest N2G48B factory image; the bootloader is still at 3.68, and radio is also still at 3.81. Are you on Nougat or O?
AncientDeveloper said:
I just double checked the latest N2G48B factory image; the bootloader is still at 3.68, and radio is also still at 3.81. Are you on Nougat or O?
Click to expand...
Click to collapse
Hey there I'm back. Sorry I've been really really busy. The most recent version of radio and bootloader is what I said. Type angler on androidfilehost and you'll see them. Also, I am on nougat. Here's my output from the newest available radio and bootloader.
10bf3cbfbedac4ba96c95b10b5920690 aboot
430c00ce1533d1ac4be7177ba99eac5f hyp
44653559a47bbe7e31979315c4f8a9eb rpm
2037924490d44cc5bd6bb437b22034bf sbl1
778cd737c4cd16950314b1ee3c9c774d tz
f5e413a7a13e3ac46984c7de763e25df modem
a6f4d11c37e34fe6678738a54aeb5434 vendor
I am new to LG devices... this is the first lg device for me.
I am on ZVA latest software version.
I want to have root in my phone or unlock the bootloader to install lineagos roms.
Could I do these two things without any risks to hard brick the phone?
I am familiar with adb and fastboot instructions.
Thank you.
If you can find out what ARB version you are on (I hear that Sprint pulled access to that hidden menu), and it is still 0, then maybe.
I am working to find a model that has a KDZ that is close enough to the LS997 that it will boot. If it will boot, then it can be rooted, and the proper firmware flashed back onto the phone.
-- Brian
The apk in first post of this thread may give you access to hidden menu. Let us know if it worked please
https://forum.xda-developers.com/v20/help/lg-v20-cdma-to-lte-gsm-switch-via-t3602409
loopytee said:
The apk in first post of this thread may give you access to hidden menu. Let us know if it worked please
https://forum.xda-developers.com/v20/help/lg-v20-cdma-to-lte-gsm-switch-via-t3602409
Click to expand...
Click to collapse
I think you are talking about unlock CDMA or GSM service.
But I am talking about unlocking bootloader and root.
I think this app doesn't work anymore since the production and lab menu couldn't be accessed.
But as I understand the main problem is how to return to the stock after root?
runningnak3d said:
If you can find out what ARB version you are on (I hear that Sprint pulled access to that hidden menu), and it is still 0, then maybe.
I am working to find a model that has a KDZ that is close enough to the LS997 that it will boot. If it will boot, then it can be rooted, and the proper firmware flashed back onto the phone.
-- Brian
Click to expand...
Click to collapse
What is ARB stands for?
Got it
Anti Rollback=1
anees02 said:
What is ARB stands for?
And how to obtain it?
I have came from Samsung world so don't know a lot about LG.
Click to expand...
Click to collapse
Anti roll back---Arb
In hidden menu. (if you can access it)
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.
loopytee said:
Anti roll back---Arb
In hidden menu. (if you can access it)
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.
Click to expand...
Click to collapse
Yes Got it
In my case ARB=1
What does that mean?
Couldn't flash old firmware?
anees02 said:
I think you are talking about unlock CDMA or GSM service.
But I am talking about unlocking bootloader and root.
I think this app doesn't work anymore since the production and lab menu couldn't be accessed.
But as I understand the main problem is how to return to the stock after root?
Click to expand...
Click to collapse
I am only referring to the apk linked in the first post. I realize that thread is not what you are looking for.
Did the apk work for you to access hidden menu? What zv# are you on?
loopytee said:
I am only referring to the apk linked in the first post. I realize that thread is not what you are looking for.
Did the apk work for you to access hidden menu? What zv# are you on?
Click to expand...
Click to collapse
Yes the app works and it said
ARB=1
And I am on ZVA software version.
Unfortunately there isn't any firmware out there that is ARB version 1 AND December 2016 security patch or older, so no, you can't root at this time.
I am guessing ZVA incremented ARB because ZV9 is still ARB 0.
-- Brian
anees02 said:
Yes the app works and it said
ARB=1
And I am on ZVA software version.
Click to expand...
Click to collapse
Ok thanks
Here is the current info about Arb and whats being worked on. As far as I know if your Arb is anything other then 0 then you can't root yet. I say yet because there is some great work being do with alot of hope for all.
Here are some links to whats going on currently
https://forum.xda-developers.com/v20/help/want-help-rooting-security-patches-t3680397
https://forum.xda-developers.com/v20/how-to/laf-download-mode-how-root-t3676011
runningnak3d said:
Unfortunately there isn't any firmware out there that is ARB version 1 AND December 2016 security patch or older, so no, you can't root at this time.
I am guessing ZVA incremented ARB because ZV9 is still ARB 0.
-- Brian
Click to expand...
Click to collapse
I think so. ARB
On ZV9 it was 0.
On ZVA it's 1.
So I have to wait until there's a method that doesn't matter about ARB value.
You could still do a really awesome thing for the people that are already rooted, or are about to be rooted -- dump your phone so that they can't have the latest firmware.
If you wouldn't mind, grab a copy of the patched LG UP, and use the dump function. This can not harm your phone in ANY way. What it does is reads the partitions on your phone, and saves them out to files.
We need:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
You can leave the rest unchecked. They are either not needed, or unique to your phone.
-- Brian
runningnak3d said:
You could still do a really awesome thing for the people that are already rooted, or are about to be rooted -- dump your phone so that they can't have the latest firmware.
If you wouldn't mind, grab a copy of the patched LG UP, and use the dump function. This can not harm your phone in ANY way. What it does is reads the partitions on your phone, and saves them out to files.
We need:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
You can leave the rest unchecked. They are either not needed, or unique to your phone.
-- Brian
Click to expand...
Click to collapse
Ok.
I will search for the patched version of LG UP.
And I hope that I find a time to charge my laptop and dump these partitions.
Some quick instructions for you:
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
Pick the one that says DUMP and click Start. You will be asked what partitions to dump, please check all the partitions listed above.
runningnak3d said:
Some quick instructions for you:
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
Pick the one that says DUMP and click Start. You will be asked what partitions to dump, please check all the partitions listed above.
Click to expand...
Click to collapse
I already dump the required partitions but LG UP recognized my software version ZV6 and it is really ZVA as shown on the attatched pic.
The size of the folder before compression is 5.88 GB. after compression 2.53 GB.
What about the difference in version between LG UP and the real version?
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
runningnak3d said:
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
Click to expand...
Click to collapse
Yes I am now uploading the zip file but the internet is very slow that before 4 hours I have started the uploading,until now it only upload 750 MB of 2.53 GB.
So if the uploading process finished successfully I will pm the link to your inbox.
This is from about phone>>software version
runningnak3d said:
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
Click to expand...
Click to collapse
PM sent to you.
Has anyone on a pure stock h910 taken the latest update that has been pushed out today? I was wondering if anyone could check the ARB version.
*#546368#*910# on the dialer to enter hidden menu then select svc menu and then version info. Scroll to the bottom and you will see antirollback and a number listed. I just want to know what that number is. Thanks ahead of time!
Just updated. Antirollback number is 0.
Expertize said:
Just updated. Antirollback number is 0.
Click to expand...
Click to collapse
Really appreciate taking the time to report back! Thanks again
@Expertize Would you mind grabbing the patched LG UP and dumping it? If so, I can send you full details on which partitions to dump.
Also, what version is it now?
Thanks,
-- Brian
@runningnak3d @toastyp I figured i'd be brave and did the update myself. I'm confirming @Expertize 's post. Software vers. H91010q. Build is still NRD90M, Kernel 3.18.31, Security patch level 10/1/2017, Android 7.0, ARB 0.
I've got my laptop here at work and can do the LG up of what you need, though the upload will have to be later tonight when I get home (my portable hotspot is super slow to be uploading gigs lol).
And I just sent a request to LG for the 10p kernel source code, now I have to get 10q -- UGH! /sarcasm
@crackness Thanks very much dude! I forget, do you need the list of what partitions to dump, or are you good?
-- Brian
@runningnak3d Yeah, let me know what partitions you want me to dump. Do you need me to do a wipe first?
Yea, you need to factory reset before dumping so you have a clean system partition.
Code:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
Thanks again dude!
-- Brian
No problem. Will do tonight (around 11-12 Eastern).
Im using the h910 on another carrier so I cant receive updates. Can I use this dump to update my phone using LG Up?
@runningnak3d I've sent you a PM with a question.
You can ignore my PM, uninstalling then reinstalling fixed the issue.
Here's the zip of the 37 files you requested from my freshly factory reset 10q phone.
Let me know if you have any issues accessing.
Thanks.
@crackness Thanks very much!
@prismk You can use these to upgrade your firmware, but not with LG UP. You either have to flash them manually with dd, or wait for the TWRP flashable zip.
runningnak3d said:
@prismk You can use these to upgrade your firmware, but not with LG UP. You either have to flash them manually with dd, or wait for the TWRP flashable zip.
Click to expand...
Click to collapse
Can I flash with fastboot or dd all partitions except the recovery to not loosing TWRP?
If you are currently rooted, then yes, you can use fastboot to flash each file. The ones you don't want to flash in addition to recovery are:
Code:
aboot
abootbak
recovery
recoverybak
I only had him dump those in case someone wanted to return to stock.
Something you need to know ... the 10p and 10q firmware do not work with older boot(kernel) and system images. So if you flash this, you will have to use the kernel and system as well -- no *current* custom ROMs work with 10p or 10q. Also, since you have to use the stock kernel, you will have the static issue where you have to cover the prox sensor after every reboot. If none of that is a problem for you, flash away.
The good news is that 10q is still ARB 0, so if you don't like it, you can go back to 10m.
-- Brian
Ok! Thank you!
I just did a check, and mine says it's up to date, now, this may be because mine in unlocked on Cricket
I entered on fastboot mode and flashed the partitions. Worked like a charm
Is anyone planning to make a twrp flash able 10q? I'm on WETA, but since that's not being worked on anymore, I just assume go with the newer patch level and be rooted.
You're really not going to like the answer...it is..... 42
Just kidding, for real it says 0
Hope this is helpful.
prismk said:
I entered on fastboot mode and flashed the partitions. Worked like a charm
Click to expand...
Click to collapse
My front camera has stopped working unless I tap (not bang but tap) on the phone near the camera. I need to flash back to stock, including recovery. Can I do so in fastboot? If so, mind posting a quick little "how you did it"?
I know the commands for fastboot, but just want to make sure I do this correctly. Don't want to go into the AT&T store with a completely bricked phone...
Also, do I need to flash all partitions, or can I just flash recovery and kernel partitions and boot into ROM since I'm already on stock? That's really all I need to change, that and unroot the phone...