Related
With the new OTA being released many are asking how to restore stock recovery. I think that the original /system/etc/install-recovery.sh file is required, unfortunately I did not make a backup. Does anyone have a copy of the original version of this file? Please post it here if you have it and anyone who knows how to restore stock recovery please post any helpful instructions here. If I get the file and proper instructions I will update the OP accordingly. Thanks.
I made a backup but have no idea how to extract that file.
You have to write which TPT you have.
US or....?
16, 32 or 64GB?
toenail_flicker said:
I made a backup but have no idea how to extract that file.
Click to expand...
Click to collapse
What did you backup with? If you backed it up after installing CWM then it was probably already gone (which is why I don't have it).
In the ROW instructions they cleverly added this line to the install instructions:
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
which creates a backup of the file in /system/etc/
If you did this then you should be able to copy the file install-recovery.sh.backup from /system/etc/ using root explorer or adb.
I have the US 32GB version, I'm not sure if the files are the same but I would guess that they are. Anyway if you can get the file that would be great.
I have 183827U 64GB. Yes, I made a Nandroid backup after installing CMW. I also have Titanium and MyBackup saves, but have no idea if they save the file. I'll go looking for it with RE and let you know what I find.
---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------
Seems I have install-recovery.sh but the date is recent, so I guess it's from when I rooted. No backup of the same name.
Mine is:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:0a48c18ee1ca32bba5a785d8ea8b6976fc0a190e; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p2:3170304:fa229b8ff37128302094316ea4ced3d68ad5edcf EMMC:/dev/block/mmcblk0p1 53a249cd150c483f9255eba03adccdf6e7c014a6 3524608 fa229b8ff37128302094316ea4ced3d68ad5edcf:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
WE-TPT-64GB
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
windraver said:
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
Click to expand...
Click to collapse
You will need a different kernel to work with a 5.1 or 5.0 system image. We cannot flash a kernel with this method yet just system images.
Right, so the only thing we can do are modified "roms" based on stock. Can't flash recovery or kernel since those are on separate partitions.
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
timmyk465 said:
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
Click to expand...
Click to collapse
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Ekkoria said:
Not going to work. You need to mount an ext4 image. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
I'd definitely be interested in a guide. I just wish there was a tool for windows that would work.
You can do it on windows but it's way easier on Linux.
I'm gonna get Linux back up and running and see what I can cook up.
Ekkoria said:
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
ntxct said:
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
Click to expand...
Click to collapse
Open your file manager as root, then open the file.
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
I wrote up and posted a quick guide (which probably sucks) for this purpose.
This is just a translation of the Windows Binaries to run on Linux.
So if you need some specific help, this is a better place
So, I will quote the original thread.
Backup TA for Sony Xperia
Backup TA can backup and restore the TA partition of the device. When you create a backup before unlocking for the first time, then you will be able to restore to full factory state (including a locked bootloader). This means all DRM keys intact, Bravia Engine working in Album and last but not least your warranty when needed
NOTE: When you did create a backup of your device's TA with another tool or Backup TA v4 or earlier, you are able to convert it to a valid Backup TA package by choosing 'Convert TA.img' from the menu. When you've done this you are able to restore it safely.
Downloads/Source
ChangeLog/Commits
Compatibles Devices
The list is in the original Thread, but is outdated, give it a try.
GUIDE
1. Download the latest version of Backup TA.
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.sh
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
FAQ's and Others
Go to the original thread
Thanks to:
@DevShaft (for creating the tool)
@luminoso (for support and testing)
to the other Dev's that contributed to the original tool.
thanks a lot backed up ta xperia z ultra on ubuntu using ur tool . Thanks a lot and this tool is amazing
NABENDU1 said:
thanks a lot backed up ta xperia z ultra on ubuntu using ur tool . Thanks a lot and this tool is amazing
Click to expand...
Click to collapse
How do you get it to run? All I get is a script, don't know how to run it
Edit* I'm using Linux mint, would I be better with a different distro?
---------- Post added at 04:33 PM ---------- Previous post was at 04:16 PM ----------
zezadas said:
This is just a translation of the Windows Binaries to run on Linux.
So if you need some specific help, this is a better place
So, I will quote the original thread.
Backup TA for Sony Xperia
Backup TA can backup and restore the TA partition of the device. When you create a backup before unlocking for the first time, then you will be able to restore to full factory state (including a locked bootloader). This means all DRM keys intact, Bravia Engine working in Album and last but not least your warranty when needed
NOTE: When you did create a backup of your device's TA with another tool or Backup TA v4 or earlier, you are able to convert it to a valid Backup TA package by choosing 'Convert TA.img' from the menu. When you've done this you are able to restore it safely.
Downloads/Source
ChangeLog/Commits
Compatibles Devices
The list is in the original Thread, but is outdated, give it a try.
GUIDE
1. Download the latest version of Backup TA.
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.sh
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
FAQ's and Others
Go to the original thread
Thanks to:
@DevShaft (for creating the tool)
@luminoso (for support and testing)
to the other Dev's that contributed to the original tool.
Click to expand...
Click to collapse
What distro is recommended to run this? I tried Linux mint but couldn't get it to run
brooker88 said:
How do you get it to run? All I get is a script, don't know how to run it
Edit* I'm using Linux mint, would I be better with a different distro?
---------- Post added at 04:33 PM ---------- Previous post was at 04:16 PM ----------
What distro is recommended to run this? I tried Linux mint but couldn't get it to run
Click to expand...
Click to collapse
You need set the Script as exec and run on terminal "sh . /Scriptname.sh"
Date: 2015.08.12
Bootloader: unlock method unknown
Custom recovery: none
Hi,
I've modified original system.img file by adding su binaries and SuperSU apk.
I't the S118 ROM from this link, all the procedures are exactly the same as described here by mr.mrcn:
http://forum.xda-developers.com/android/general/lenovo-z90-7-vibe-shot-international-t3148018
Link for rooted ROM
After start just run the SuperSU application to update su binaries.
Enjoy!
okencjusz said:
Date: 2015.08.12
Bootloader: unlock method unknown
Custom recovery: none
Hi,
I've modified original system.img file by adding su binaries and SuperSU apk.
I't the S118 ROM from this link, all the procedures are exactly the same as described here by mr.mrcn:
http://forum.xda-developers.com/android/general/lenovo-z90-7-vibe-shot-international-t3148018
Link for rooted ROM
After start just run the SuperSU application to update su binaries.
Enjoy!
Click to expand...
Click to collapse
Hi. Does the ROM have Norwegian (Norsk (bokmål)) language?
okencjusz said:
date: 2015.08.12
bootloader: Unlock method unknown
custom recovery: None
hi,
i've modified original system.img file by adding su binaries and supersu apk.
I't the s118 rom from this link, all the procedures are exactly the same as described here by mr.mrcn:
http://forum.xda-developers.com/android/general/lenovo-z90-7-vibe-shot-international-t3148018
link for rooted rom
after start just run the supersu application to update su binaries.
Enjoy!
Click to expand...
Click to collapse
very useful!! Thanks
Hi All!
Who immediately flashed the phone from the Chinese version (VIBEUI_V2.5_1518_5.169.1_ST_Z90-7)
on
Lenovo Z90-7 (VIBE SHOT) - International (ROW) ROM, multilanguage, GAPPS, ROOT?
What is the method used by the firmware (Miflash, QFIL, etc)?
They did a factory reset before flashing or not?
The firmware was successful or not?
There were problems with the installation or not?
Are you satisfied with your phone with this firmware!
PLS, write review!
Thx!
Hi thank you, i need a root alot(im root oriented person)
Thanks!
help
okencjusz said:
Date: 2015.08.12
Bootloader: unlock method unknown
Custom recovery: none
Hi,
I've modified original system.img file by adding su binaries and SuperSU apk.
I't the S118 ROM from this link, all the procedures are exactly the same as described here by mr.mrcn:
http://forum.xda-developers.com/android/general/lenovo-z90-7-vibe-shot-international-t3148018
Link for rooted ROM
After start just run the SuperSU application to update su binaries.
Enjoy!
Click to expand...
Click to collapse
HI
so on top of your rooted one can i do this one? Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull. zip
thanks
mato.kado said:
HI
so on top of your rooted one can i do this one? Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull. zip
thanks
Click to expand...
Click to collapse
Hi, i have already uploaded S208 rooted on my google drive.
okencjusz said:
Hi, i have already uploaded S208 rooted on my google drive.
Click to expand...
Click to collapse
ah,so i just install your S208 version and thats it right? following mr.mrcn step by step
By the way i've downloaded already
dzenkuje
mato.kado said:
ah,so i just install your S208 version and thats it right? following mr.mrcn step by step
By the way i've downloaded already
dzenkuje
Click to expand...
Click to collapse
Yes, exactly. But if you are on S207 now you have to enter download mode by adb command "adb reboot edl", and remember to remove microsd card
okencjusz said:
Hi, i have already uploaded S208 rooted on my google drive.
Click to expand...
Click to collapse
this one is the rooted S208 version mate?
Z90a40_ROW_qpst_rooted_Okencjusz.zip
tha
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
okencjusz said:
Yes, exactly. But if you are on S207 now you have to enter download mode by adb command "adb reboot edl", and remember to remove microsd card
Click to expand...
Click to collapse
me again ))
i got this version VIBEUI_V2.5_1522_5.310.1_ST_Z90-7 ,if i follow mr.mrcn step by step be ok or u got any advice.
tha
mato.kado said:
this one is the rooted S208 version mate?
Z90a40_ROW_qpst_rooted_Okencjusz.zip
tha
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
me again ))
i got this version VIBEUI_V2.5_1522_5.310.1_ST_Z90-7 ,if i follow mr.mrcn step by step be ok or u got any advice.
tha
Click to expand...
Click to collapse
I think that this VIBEUI is chinese version, so mr.mrcn steps are fine.
Z90a40_ROW_qpst_S208_rooted_Okencjusz.zip - link to S208 rooted you will find on my post on needrom, i don't know why i cannot post this link here.
okencjusz said:
I think that this VIBEUI is chinese version, so mr.mrcn steps are fine.
Z90a40_ROW_qpst_S208_rooted_Okencjusz.zip - link to S208 rooted you will find on my post on needrom, i don't know why i cannot post this link here.
Click to expand...
Click to collapse
am gonna try,let u know how its work
thanks
---------- Post added at 07:43 PM ---------- Previous post was at 06:53 PM ----------
okencjusz said:
I think that this VIBEUI is chinese version, so mr.mrcn steps are fine.
Z90a40_ROW_qpst_S208_rooted_Okencjusz.zip - link to S208 rooted you will find on my post on needrom, i don't know why i cannot post this link here.
Click to expand...
Click to collapse
hmm,i am getting this message
The requested resources is in use. (0x800700aa: Open serial port"\\.\COM3")
i tried Disable Driver Signature Enforcement but doesnt work.
i am running W7 64bit
UPDATE:
i didnt have Debbuging mode on
i tried to flash and now i get this message
Reach the end of the file.)0x8070026: Receiving hello packet
UPDATE:
after i install WINDOWS 10 i flash without problem
everything running good now
okencjusz sir, im a little bit confused.. my vibe is on stock rom ( chinese ver.) can i flash your rooted S208 rom directly by doing these steps....
- download file Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull. zip, rename it to 'update.zip'
- copy to phone memory or SD card
- reboot to recovery (turn off the phone, hit vol +- and hit power)
- install update package (it will take some time), reboot (first start will take few minutes)
anjirru said:
okencjusz sir, im a little bit confused.. my vibe is on stock rom ( chinese ver.) can i flash your rooted S208 rom directly by doing these steps....
- download file Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull. zip, rename it to 'update.zip'
- copy to phone memory or SD card
- reboot to recovery (turn off the phone, hit vol +- and hit power)
- install update package (it will take some time), reboot (first start will take few minutes)
Click to expand...
Click to collapse
No, this way you cannot do it. Update from sd card is possible only with original update files which are digitally signed by lenovo. If something is modified (added root in this case) in such package the update is not possible. But you can still flash it with miflash application.
Hi. Do you have the one for 218 rom? Thanks
---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------
Can I flash the 208 ROM while I am having the 218 latest? Thanks.
engineer000 said:
Hi. Do you have the one for 218 rom? Thanks
Click to expand...
Click to collapse
No, i think that it's available only via OTA update, so it's without root so it can't be downloaded from the phone for rooting purposes.
Besides my Z90-z is bricked now so i'm not able to work on it.
okencjusz said:
No, i think that it's available only via OTA update, so it's without root so it can't be downloaded from the phone for rooting purposes.
Besides my Z90-z is bricked now so i'm not able to work on it.
Click to expand...
Click to collapse
Sad story Hope you will be able to revive it.
Can I flash the 208 ROM while I am having the 218 latest? Thanks. Do you have a guide to root a ROM so that I can try to do it? Thanks again.
engineer000 said:
Sad story Hope you will be able to revive it.
Can I flash the 208 ROM while I am having the 218 latest? Thanks. Do you have a guide to root a ROM so that I can try to do it? Thanks again.
Click to expand...
Click to collapse
I was basing on this book: http://eu.wiley.com/WileyCDA/WileyTitle/productCd-111860864X.html
And chinese rooted ROM.
The problem was to join this system_1.img system_2.img and so on files into one correct system.img file to be mounted as ext4 filesystem under linux.
There is a file rawprogram0.xml with addresses of each splitted files, but you cannot join them directly - between them there is some unused space. You can figure out how many "unused" blocks are needed between particular files from rawprogram0.xml file.
okencjusz said:
I was basing on this book: http://eu.wiley.com/WileyCDA/WileyTitle/productCd-111860864X.html
And chinese rooted ROM.
The problem was to join this system_1.img system_2.img and so on files into one correct system.img file to be mounted as ext4 filesystem under linux.
There is a file rawprogram0.xml with addresses of each splitted files, but you cannot join them directly - between them there is some unused space. You can figure out how many "unused" blocks are needed between particular files from rawprogram0.xml file.
Click to expand...
Click to collapse
Thank you. I'll check that. I hope I can do it. Thanks again
okencjusz said:
I was basing on this book: http://eu.wiley.com/WileyCDA/WileyTitle/productCd-111860864X.html
And chinese rooted ROM.
The problem was to join this system_1.img system_2.img and so on files into one correct system.img file to be mounted as ext4 filesystem under linux.
There is a file rawprogram0.xml with addresses of each splitted files, but you cannot join them directly - between them there is some unused space. You can figure out how many "unused" blocks are needed between particular files from rawprogram0.xml file.
Click to expand...
Click to collapse
This comes with full rom. Is there a way you can help us root this?
http://lenovo-forums.ru/topic/13972-lenovo-vibe-shot-прошивка-z90a40-s218-150908-row/
Please Thanks
Hopefully there is a kind soul out there that has an H910 and doesn't mind doing a factory reset.
Over the weekend, I was testing an unbrick method if the H910 ended up losing download mode (Qualcomm HS-USB QDLoader 9008 mode).
I came across this thread: https://forum.xda-developers.com/att-g4/general/att-h810-qualcomm-hs-usb-qdloader-9008-t3539554
It just so happened that I had a spare LG G4 laying around that I wasn't worried about bricking, so I made a dump, and then flashed a broken boot loader and viola -- 9008 mode.
I then proceeded to create the SD card, and flash the phone. What do you know -- it worked.
So then I made a dump of my H910. What I didn't know at the time was that I either had a bad USB cable, or bad USB port, and I wasn't paying attention. The image file that I got was WAY too small (corrupt). So now I have an H910 in 9008 mode that I have no way to recover.
So, if one of you with a rooted H910 doesn't mind doing these steps:
* Do a full factory reset from CWM TWRP or any recovery
* Now open ADB shell
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=8192
That will give me a full dump, and then I can figure out the offset, and size (seek= / size=) since I highly doubt that it is the same for H810 and H910
Bonus if you can give me the partition layout...
Thanks,
-- Brian
I need this too
I have an H910 with the 9008 message only, too. I would also like it if someone can provide this system dump in order for me to get my phone running again.
@alanwid I have given up on the hopes that someone will be willing to provide the dump, so I have sent the phone for repair. When I get it back *IF* it still has rootable firmware, then I will create the image for you to try.
I wish I could hang on to the phone a little while longer, because I did a lot of research on Qualcomm 9008 (EDL - Emergency DownLoad mode). At one time it was possible to send a command to go from 9008 to 9006. In 9006 mode, you can see the individual partitions, and as long as you have the images -- flash back to a working phone. For that matter, if we had newer version of QPST that supported the msm8996 (Snapdragon 820) we could recover our phones in 9008 mode without having to resort to an SDCard.
Unfortunately, it looks like Qualcomm has changed the protocol, and I don't have time to try and putz with it.
EDIT: it is STILL possible to go into 9006 by shorting test pins, but I don't want to open this phone and void the warranty.
Thanks!! Would this link have the image that would work with your method? https://forum.xda-developers.com/v20/development/rom-natf-1-00-test-5-debloated-stock-t3509750
and this link says they have a boot img https://forum.xda-developers.com/v20/development/devs-h910-v10l-rom-boot-img-included-t3579011
runningnak3d said:
Hopefully there is a kind soul out there that has an H910 and doesn't mind doing a factory reset.
Over the weekend, I was testing an unbrick method if the H910 ended up losing download mode (Qualcomm HS-USB QDLoader 9008 mode).
I came across this thread: https://forum.xda-developers.com/att-g4/general/att-h810-qualcomm-hs-usb-qdloader-9008-t3539554
It just so happened that I had a spare LG G4 laying around that I wasn't worried about bricking, so I made a dump, and then flashed a broken boot loader and viola -- 9008 mode.
I then proceeded to create the SD card, and flash the phone. What do you know -- it worked.
So then I made a dump of my H910. What I didn't know at the time was that I either had a bad USB cable, or bad USB port, and I wasn't paying attention. The image file that I got was WAY too small (corrupt). So now I have an H910 in 9008 mode that I have no way to recover.
So, if one of you with a rooted H910 doesn't mind doing these steps:
* Do a full factory reset from CWM TWRP or any recovery
* Now open ADB shell
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=8192
That will give me a full dump, and then I can figure out the offset, and size (seek= / size=) since I highly doubt that it is the same for H810 and H910
Bonus if you can give me the partition layout...
Thanks,
-- Brian
Click to expand...
Click to collapse
Can anyone get this dump? I am trying to use either MiFlash or Qfil to unbrick my phone with the 8996.mbn or .elf and xml files. I'm not sure which ones v20s use. My phone is in the 9008 mode.
Anyone try this method?
No one is willing to make a dump? It can be from a H915 or H910 -- going to have to flash the 915 KDZ anyway since we don't have a 910 KDZ (yes, it has been verified that they are identical hardware).
So little effort to do this, and you would be helping several people out...
EDIT: In case anyone thinks this would just be a waste of time, I just recovered an H901 (LG V10) using this method. I bought a used v10 off Ebay when I bricked my v20 to use until it came back from repair.
I had the v10 all of 10 minutes, and bricked it. Yep -- didn't pay attention to the version of MM that was on it, and flashed the wrong bootstack while I was rooting it. It turns out that the folks over in the v10 forum already had an image. Wrote the SDcard, and viola, the phone booted all the way to the OS. That got me looking at more info concerning 9008. In the event that the Qualcomm XXX chip can't find a boot partition on the eMMC, then it looks at the SDcard. As long as the SDcard has a valid partition, it will boot from the SDcard. You can have the entire OS on the SDcard if you want, but it will attempt to jump to the eMMC at every point in the boot process. So, if you blow up your boot loader -- write one to the SDcard and viola -- you are back in business. Problem is, you need those images because all of the current KDZ extractors that I can find can't make a decent image
OK -- I rambled enough for an edit. Bottom line, some kind soul please make an image. 9008 errors will be a thing of the past.
Hate replying to myself, but I think I did enough editing in that last post
OK, I futtzed around until I got a good extraction. The only thing I need now is for someone that has an H910 or 915 to run this:
Code:
adb shell "/sbin/fdisk -l /dev/block/mmcblk0"
And paste the output in here. With the partitions I have extracted, and that little piece of info, I can make an image that will finally fix our freaking phones. Please. This command is non-intrusive, and if you have adb setup already (which I would hope) then it will take you 10 seconds
I have a H910 rooted with dirty santa. I have the TWRP backup from stock (rooted). I'll be installing a custom room soon but if I can do anything before that'll help let me know
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
runningnak3d said:
Hate replying to myself, but I think I did enough editing in that last post
OK, I futtzed around until I got a good extraction. The only thing I need now is for someone that has an H910 or 915 to run this:
Code:
adb shell "/sbin/fdisk -l /dev/block/mmcblk0"
And paste the output in here. With the partitions I have extracted, and that little piece of info, I can make an image that will finally fix our freaking phones. Please. This command is non-intrusive, and if you have adb setup already (which I would hope) then it will take you 10 seconds
Click to expand...
Click to collapse
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\platform-tools
C:\platform-tools>adb devices
List of devices attached
LGUS9966cc96e9f device
C:\platform-tools>adb shell
elsa:/ $ /sbin/fdisk -l /dev/block/mmcblk0
/system/bin/sh: /sbin/fdisk: not found
127|elsa:/ $
---------- Post added at 12:43 AM ---------- Previous post was at 12:40 AM ----------
staplerz said:
I have a H910 rooted with dirty santa. I have the TWRP backup from stock (rooted). I'll be installing a custom room soon but if I can do anything before that'll help let me know
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
Hate replying to myself, but I think I did enough editing in that last post
OK, I futtzed around until I got a good extraction. The only thing I need now is for someone that has an H910 or 915 to run this:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\platform-tools
C:\platform-tools>adb devices
List of devices attached
LGUS9966cc96e9f device
C:\platform-tools>adb shell
elsa:/ $ /sbin/fdisk -l /dev/block/mmcblk0
/system/bin/sh: /sbin/fdisk: not found
127|elsa:/ $
Click to expand...
Click to collapse
Sorry I'm a noob but would like to help
It would be very awesome if you are willing to help.
The first and most important will be an image dump of your entire eMMC -- that is the command in the first post:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/path-to-your-external-sdcard/backup.img bs=8192
Let me know if you need help finding the correct path. It must be your external SD card because you are dumping your internal, and that would be a bit of a loop
As for the fdisk command, Dunno why, but maybe the Windows adb command is different. Try this:
Code:
adb shell
fdisk -l /dev/block/mmcblk0
Just an FYI. That first one dumps your entire internal storage, so don't do it if you have anything you wouldn't want me to see -- or like I said in my first post, do a backup and then wipe your data partition.
I know this seems like a lot, but you will really be helping a few people (that I know of) out of a jam.
runningnak3d said:
It would be very awesome if you are willing to help.
The first and most important will be an image dump of your entire eMMC -- that is the command in the first post:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/path-to-your-external-sdcard/backup.img bs=8192
Let me know if you need help finding the correct path. It must be your external SD card because you are dumping your internal, and that would be a bit of a loop
As for the fdisk command, Dunno why, but maybe the Windows adb command is different. Try this:
Code:
adb shell
fdisk -l /dev/block/mmcblk0
Just an FYI. That first one dumps your entire internal storage, so don't do it if you have anything you wouldn't want me to see -- or like I said in my first post, do a backup and then wipe your data partition.
I know this seems like a lot, but you will really be helping a few people (that I know of) out of a jam.
Click to expand...
Click to collapse
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\platform-tools
C:\platform-tools>adb devices
List of devices attached
LGUS9966cc96e9f recovery
C:\platform-tools>adb shell
~ # ←[6n
~ # ←[6nfdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 63.8 GB, 63864569856 bytes
256 heads, 63 sectors/track, 7734 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 7735 62366720 7 HPFS/NTFS
~ # ←[6n
---------- Post added at 05:32 PM ---------- Previous post was at 05:27 PM ----------
If I make a backup in TWRP of my current setup, "Factory Reset" in TWRP and then make the eMMC back up. I will have to dirtysanta again and then can I restore my backup via TWRP?
I'm more concerned with time. I need my phone for work tomorrow.
---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------
****. Well I was in TWRP and forgot I was under factory reset. I thought it was "Slide to Unlock"... I just factory reset via TWRP (didnt have any important data). Please advise
Sorry about that dude.
If you don't mind throwing in a 64gig SD card and doing the dump it would be awesome. If you don't have a 64 gig card, I can figure something else out.
No worries. I was able to boot into TWRP and am currently making a backup (stock non rooted). I have a 64gb sd card but it's probably 30% full. Do i need to backup my sd card and format it? How big of a dump are we talking about here (-;
EDIT: Also need help finding sd path
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
runningnak3d said:
Sorry about that dude.
If you don't mind throwing in a 64gig SD card and doing the dump it would be awesome. If you don't have a 64 gig card, I can figure something else out.
Click to expand...
Click to collapse
adb shell
su su: not found
also need to figure out my sdcard location
Sorry but I had to restore back... If you really need it let me know but its hard to believe there isn't a h910 system dump floating around
Totally understandable. Having a full dump would be nice, but at this point I would just settle for the partition layout so I can make the image myself.
You need to be rooted, and have busybox installed for these commands to work.
Not sure what happened when you tried to run it the last time, but could you try running again:
Code:
adb shell
su
fdisk -l /dev/block/mmcblk0
You should get a list of partitions with their start, end, and size. With that info, I can partition an SD card, and then dump the images that I extracted from the KDZ. Once I have a bootable SD card with the proper partitions -- it should work and I shouldn't need a dump from a running phone. Although at the end of the day, it is MUCH easier to just take a dump from a running phone. Far less room for error
I appreciate you working with me on this, and I know it can be frustrating when you are trying to use your phone to get work done
I think I got stuck in 9008 mode this weekend while testing my kernel, but was able to boot to recovery manually, reinstalled a known good kernel, and all was fine. But to be honest, the text was so small, I couldn't read it very well. It took several attempts to get it to boot into recovery, but I eventually got it.
Disconnect from computer and pull battery
Wait a few seconds to ensure everything has powered down
Hold Vol - and Power button
When LG splash appears while still holding Vol -, release power button and immediately press it again. You should get a white screen telling you that if you proceed it will wipe data, scroll to yes, then it will ask if you're sure, select yes again. Then you should boot back into TWRP, flash a known good kernel (for me, I used my previous kernel build as I knew it was booting, but I have also used schwifty kernel).
I have to tell you, that this phone is very picky on manually booting to recovery. You have to hold the Vol - firmly and when you release and press the power button, make sure you firmly press it. Like me, it may take you a few tries.
In your case, because of what you were doing, I'm not sure just flashing a kernel and/or rom would fix things for you, but maybe you can make a flashable bootloader (not sure if there are any for this phone atm as I have not researched it). Either way, if you still get the LG splash screen, and have TWRP, you should be able to boot to recovery and fix your phone.
I can assure you that you did not brick your phone into 9008 mode. In 9008 mode the phone will not power on -- no lights, nothing. The fact that you were able to get an LG logo means your boot partition was fine.
The first thing a Qualcomm chip does is look for a valid boot partition on the eMMC. If it can't find one there, it looks for it on the SDcard (which is why I will never buy a phone that doesn't have an SDcard slot ).
-- Brian
elsa:/ $ adb shell
/system/bin/sh: adb: not found
127|elsa:/ $ su
elsa:/ # adb shell
sush: adb: not found
127|elsa:/ # shell
sush: shell: not found
127|elsa:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 59 GB, 63864569856 bytes, 124735488 sectors
7734 cylinders, 256 heads, 63 sectors/track
Units: cylinders of 16128 * 512 = 8257536 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/block/mmcblk0p1 * 1023,255,63 1023,255,63 2048 124735487 124733440 59.4G 7 HPFS/NTFS
elsa:/ #
I am freaking blind, or just flat out wasn't paying attention the first time you posted that output. Sometime between MM 6.0 and N 7.0 they switch from using an MBR partition table to a GPT partition table. Hence fdisk works for me (T-Mobile hasn't released 7.x for the V10 yet, so I am on MM 6.0), but not for you. I can't find a good source to download gdisk (fdisk that works with GPT), so I am compiling it. As soon as I have it built, I will post a link.
Again, thanks for working with me on this. Do have to point out that an image dump would be far far easier *nudge* *hint*
-- Brian
Lol no worries i thought i was doing something wrong. If i can finess my simcard into my g3 ill be able to get to it sooner.
Just a heads up guys. if you do this theres a good chance that your EFS and userdata will be shared with him(which is a nono).