Related
Cool! I got a myTouch 4G Slide!
Not cool! No ClockworkMod recovery!
Solution! Make my own.
You must have a 'S-OFF' device to install this recovery image!
Here is my unofficial MoDaCo build of ClockworkMod for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. In order to flash this recovery, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the ClockworkMod image file from here
Copy the file to /data/local ('adb push doubleshot.clockworkmod.4.0.0.9.modaco.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21')
Do a recovery reboot to test ('adb reboot recovery').
That's it!
P
paulobrien said:
Cool! I got a myTouch 4G Slide!
Not cool! No ClockworkMod recovery!
Solution! Make my own.
You must have a 'S-OFF' device to install this recovery image!
Here is my unofficial MoDaCo build of ClockworkMod for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. In order to flash this recovery, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the ClockworkMod image file from here
Copy the file to /data/local ('adb push doubleshot.clockworkmod.4.0.0.9.modaco.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21')
Do a recovery reboot to test ('adb reboot recovery').
That's it!
P
Click to expand...
Click to collapse
Thanks for this! Man I wish I had mine in my hands already! I'm gonna give this a shot as soon as it arrives
Sent from my demonSPEED Glacier
Mine is S-ON :O
raycaster3 said:
Thanks for this! Man I wish I had mine in my hands already! I'm gonna give this a shot as soon as it arrives
Sent from my demonSPEED Glacier
Click to expand...
Click to collapse
Revolution said:
Mine is S-ON :O
Click to expand...
Click to collapse
Boo! Damn
Sent from my HTC Glacier
So what does hboot do to /dev/block/mmcblk0p21 after the phone is turned back on if you temp root and dd it?
thank you!
paulobrien said:
Cool! I got a myTouch 4G Slide!
Not cool! No ClockworkMod recovery!
Solution! Make my own.
You must have a 'S-OFF' device to install this recovery image!
Here is my unofficial MoDaCo build of ClockworkMod for the T-Mobile myTouch 4G Slide / aka HTC Doubleshot. In order to flash this recovery, you need to have temproot or permanent root via Fr3evo (grab from here, push to /data/local, run via ADB then reconnect after it drops your connection for root access). If you need ADB, you can grab it here.
You use this image at your own risk! Proceed with caution!
To install, simply...
Download the ClockworkMod image file from here
Copy the file to /data/local ('adb push doubleshot.clockworkmod.4.0.0.9.modaco.img /data/local')
Write the image to the recovery partition ('dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21')
Do a recovery reboot to test ('adb reboot recovery').
That's it!
P
Click to expand...
Click to collapse
what does this means 'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21'
That line of code just copies the recovery image from a directory on the phone to the special place where a recovey image is supposed to be.
Sent from my myTouch_4G_Slide using XDA App
michaelmab88 said:
That line of code just copies the recovery image from a directory on the phone to the special place where a recovey image is supposed to be.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
My device is ship s-off can't use this methods.so i used sdcard flash succeeded. Thanks!
Crossing my fingers that someone finds a way to get S-off on these. I'm too spoiled with CM7, I forgot what it's like to have a "stock" phone that you can't delete unwanted apps, overclock, tweak, etc.
I think I might just box up the MTS4G and continue to use my G2 until true root is available.
Can we get an hboot dump from someone with S-off? Just curious if it's possible to flash that to hboot with temp root?
masker2011 said:
what does this means 'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21'
Click to expand...
Click to collapse
Specifically this command is a raw linux command that would work on almost any machine. It's telling the dd utility to copy the img file to the /dev/ mount in the specific block mmcblk0p21.
Every partition is grouped into blocks. Usually 512kbytes but it could be something else.
Akujin said:
Can we get an hboot dump from someone with S-off? Just curious if it's possible to flash that to hboot with temp root?
Click to expand...
Click to collapse
Nope. See the 'Bounties!' thread.
cberbes said:
Crossing my fingers that someone finds a way to get S-off on these. I'm too spoiled with CM7, I forgot what it's like to have a "stock" phone that you can't delete unwanted apps, overclock, tweak, etc.
I think I might just box up the MTS4G and continue to use my G2 until true root is available.
Click to expand...
Click to collapse
Are you forgetting the fact that the MT4GS is also a Sense phone? While I like Sense, the option to use regular old Android should always be there (I'm looking at YOU, Motorola).
In the bounty thread it had been noted that that there is no on board charging circuit on the phone and that if certain factors do not exist in recovery then the phone can not charge.
I was wondering if this has affected you, out you have already compensated for this. If you have that issue resolved it may be of help to nbetcher and others looking to give us s-off.
Sent from my myTouch_4G_Slide using XDA Premium App
I can't use the command dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21
Whats the fix for that?
electro_chef said:
I can't use the command dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21
Whats the fix for that?
Click to expand...
Click to collapse
Did you elevate yourself to root first?
If you're not sure. At the android prompt type su [enter]
Now you're root and can run anything.
masker2011 said:
what does this means 'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21'
Click to expand...
Click to collapse
This line isn't working.
Is there a missing "ADB" or "ADB SHELL" that's supposed to go in front of the dd?
Or is this command supposed to be executed on the device itself?
jdmarko said:
This line isn't working.
Is there a missing "ADB" or "ADB SHELL" that's supposed to go in front of the dd?
Or is this command supposed to be executed on the device itself?
Click to expand...
Click to collapse
I believe its suppose to be executed on the device, however if the device doesn't have root, than its useless.
You can use fastboot to flash it.
I'm getting the same charging issue as everyone else.
If the phone is off, and you plug the charger in, the LED will light up. But the phone will not charge, it will freeze, and you must do a battery pull to get it to boot from that point.
Any idea for the fix?
I got Samsung Galaxy S Blaze 4G SGH-T769 (it comes with Gingerbread). My goal is to get Cyanogen Mod there, so first I planned to root it and use CWM to install a CM. But I need to do it on Linux, so all the instructions found around suggesting using Odin don't help. So far I found Heimdall and installed it on Debian x86_64.
But I'm not sure what else is needed to actually root it. I found some examples with some "one click" methods, but that's not helpful (since they are for other models). Any advice?
Thanks.
shmerl said:
I got Samsung Galaxy S Blaze 4G SGH-T769 (it comes with Gingerbread). My goal is to get Cyanogen Mod there, so first I planned to root it and use CWM to install a CM. But I need to do it on Linux, so all the instructions found around suggesting using Odin don't help. So far I found Heimdall and installed it on Debian x86_64.
But I'm not sure what else is needed to actually root it. I found some examples with some "one click" methods, but that's not helpful (since they are for other models). Any advice?
Thanks.
Click to expand...
Click to collapse
Hate to be a hater, but the KISS rule applies here. Just do it on a windows machine, your Linux friends won't know. Don't have one? Borrow a friends, it shouldn't take you long.
Cirkustanz said:
Hate to be a hater, but the KISS rule applies here. Just do it on a windows machine, your Linux friends won't know. Don't have one? Borrow a friends, it shouldn't take you long.
Click to expand...
Click to collapse
That's an option, but I won't have an access to one until somewhat later. Just tried to figure out a way to do it on Linux now. But if that's going to be a huge hassle - I'll wait until I'll access Windows to do it. On the other hand I'd still prefer to know how to do it on Linux, in case I'll need to do it again. Heimdall is supposed to work (disregarding potential bugs, like one I got there when trying to extract a PIT file with failed interface), but I'm not sure where to get all the needed components for it (like rooted firmware and what not).
shmerl said:
That's an option, but I won't have an access to one until somewhat later. Just tried to figure out a way to do it on Linux now. But if that's going to be a huge hassle - I'll wait until I'll access Windows to do it. On the other hand I'd still prefer to know how to do it on Linux, in case I'll need to do it again. Heimdall is supposed to work (disregarding potential bugs, like one I got there when trying to extract a PIT file with failed interface), but I'm not sure where to get all the needed components for it (like rooted firmware and what not).
Click to expand...
Click to collapse
Go into the blaze dev section and checkout the blaze Bible by nick. Its a one stop for everything you need.
jbats said:
Go into the blaze dev section and checkout the blaze Bible by nick. Its a one stop for everything you need.
Click to expand...
Click to collapse
I looked there, so far I only saw: In The Beginning There was Root.ROOT!(Via Odin) CWM Vr-5.5.0.4(Via ODIN). As I wrote above, this doesn't help me, since method with Odin to unlock the bootloader is for Windows only. Unless I missed something (that page does look confusing enough for a newcomer).
Btw, that rooted kernel (tar file) mentioned on the Odin method, doesn't work with Heimdall. So unless you succeeded doing it somehow, I'm not sure how exactly that would help me.
shmerl said:
I looked there, so far I only saw: In The Beginning There was Root.ROOT!(Via Odin) CWM Vr-5.5.0.4(Via ODIN). As I wrote above, this doesn't help me, since method with Odin to unlock the bootloader is for Windows only. Unless I missed something (that page does look confusing enough for a newcomer).
Btw, that rooted kernel (tar file) mentioned on the Odin method, doesn't work with Heimdall. So unless you succeeded doing it somehow, I'm not sure how exactly that would help me.
Click to expand...
Click to collapse
I was pointing you in that direction for if and when you got near a computer using windows. Unfortunately you'll have to root that way. Once rooted you can stay away from win afterwards and just download and flash zips in recovery. I dual boot win 7 and Ubuntu 12.10.
Why has nobody suggested Android SDK? Odin is not the only way to do it (although the easiest, perhaps).
OP, are you trying to root the stock GB? If so, you should install Android SDK for linux (google it), and then use command adb from {android SDK install dir}/platform-tools/ directory. Please refer to http://wiki.rootzwiki.com/Android_SDK for detailed instructions.
The usage is the following:
Code:
$ adb push boot.img /sdcard/external_sd
Where boot.img is the rooted boot image for GB.
Code:
$ adb shell dd if=/sdcard/external_sd/boot.img of=/dev/block/mmcblk0p8
Then, you can also copy CWM or TWRP. to the sd card and flash in the same way:
Code:
$ adb push recovery.img /sdcard/external_sd
Code:
$ adb shell dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p22
I think for rooted GB, you can download superuser app from the Google Play, or maybe, you will need to push it to /system/app through ADB.
Got a friend with a rooted phone? Got a otg cable? Use root transmission XDA link
There are a lot of rooting apps as well, but I wouldnt trust anything not found on XDA or the play store.
E107946 said:
Why has nobody suggested Android SDK? Odin is not the only way to do it (although the easiest, perhaps).
OP, are you trying to root the stock GB? If so, you should install Android SDK for linux (google it), and then use command adb from {android SDK install dir}/platform-tools/ directory. Please refer to http://wiki.rootzwiki.com/Android_SDK for detailed instructions.
The usage is the following:
Code:
$ adb push boot.img /sdcard/external_sd
Where boot.img is the rooted boot image for GB.
Code:
$ adb shell dd if=/sdcard/external_sd/boot.img of=/dev/block/mmcblk0p8
Then, you can also copy CWM or TWRP. to the sd card and flash in the same way:
Code:
$ adb push recovery.img /sdcard/external_sd
Code:
$ adb shell dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p22
I think for rooted GB, you can download superuser app from the Google Play, or maybe, you will need to push it to /system/app through ADB.
Click to expand...
Click to collapse
Thanks. I have a fastboot and adb tools, from Android Platform Tools (it's a smaller package than a whole SDK: dl.google.com/android/repository/platform-tools_r16-linux.zip ). But will writing the rooted image unlock the bootloader? I'm a bit confused here. I thought the locked bootlader that was a main barrier for writing new images like CM with recover tools, and Odin/Heimdall actually unlock bootloader as a prerequisite for the rest. So will adb achieve the same? And if it does, what rooted image I should use for Blaze. One of these?
hotfile.com/dl/163659712/8fd8b1d/SGH-T769_UVLB7_Rooted_Deodexed_ROM.zip.html
hotfile.com/dl/163658008/35fc621/SGH-T769_UVLF4_Rooted_Deodexed_ROM.zip.html
OK, I managed to write a rooted kernel using Odin in the end. But that doesn't seem to help to write Cyanogen Mod to the device. I installed CWM (from Google's store) and rebooted into recovery. Now whey trying to apply an update using a CM image from download.cyanogenmod.org/?device=t769&type=
I'm getting the same signature verification error:
E: failed to verify whole-file signature
E: signature verification failed.
Does it mean that I still need to get another bootloader to flash it as well somehow?
UPDATE: OK, I figured it out. I flashed CWM from the CWM application itself, and then rebooted into recovery, which brought up CWM recovery. From there writing Cyanogen Mod worked without any issues.
Well, since you flashed boot image from Odin, you could just flash CWM with Odin as well. It would save you some time. But you figured everything out in the end anyway..
As a suggestion, I would recommend trying AOKP Beta. It is more stable than CM10 and works flawlessly with USB storage. It is my daily driver for over 2 weeks now.
I have successfully built ClockworkMod for our HP Slate 7. I have been successful in backup and restore to and from internal SD and external SD. This is confirmed working on 2800 series and 4600 series tablets.
Prerequisites
You must have root to install this.
- Download ROOT install tool http://www.sjroot.com
- After tablet is rooted, install SuperSU from the market and update the su binary
- Verify root access with Root Checker or equivilent
Updates
-Confirmed working on 2800 series by user Joshua11007! Thanks!
-Confirmed working on 4600 series by goodguy25. Thanks!
-Added download link to stock recovery
Install at your own risk. I or anyone else am not responsible for the damage caused to your tablet or breaking warranty.
Issues
If you go into key test the only way out is to reboot is to hold the power button until tablet resets, but i think this normal.
Install from Windows *** Updated installer
If your tablet isn't rooted, please root it first. You must also have ADB working in Windows. This installer will not work from Linux, but I will provide steps below to flash from linux too.
Download attached zip file and extract on Windows PC.
Follow back-up procedure below if you want to backup your factory recovery first. (This can be skipped but you won't have your factory recovery image anymore if you skip it).
Run the Batch file labeled "Install-CWM.bat"
Done! The script will automatically reboot the tablet into recovery when complete.
Install from Linux
Ensure tablet is rooted
Download attached file and unzip it
Code:
adb push recovery.img /sdcard/
Code:
adb shell dd if=/sdcard/recovery.img of=/dev/block/mtd/by-name/recovery
Code:
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
Done! You have copied the recovery image to the internal SD, copied it to the recovery partition, and moved the factory recovery image so it doesn't over-write CWM the next time you reboot.
Backup Procedure
From your computer with ADB working
Code:
adb shell dd if=/dev/block/mtd/by-name/recovery of=/sdcard/factory-recovery.img
Code:
adb pull /sdcard/factory-recovery.img
You have copied the recovery partition to your internal SD and copied it to your computer.
Download Link
CWM 6.0.3.3
http://goo.gl/GDbDyc - Mega (Link Fixed 11/13/2014)
Stock Recovery
http://goo.gl/cGtlt1 - Mega
Reserved
Please can you upload a stock recovery backup? Thanks!!
rjwil1086 said:
I have successfully built ClockworkMod for our HP Slate 7. I have only tested this on my Slate, which is a 2800. I have been successful in backup and restore to and from internal SD and external SD. I don't have a ROM to test with yet but once I do, I will verify ROM installation works as well.
I hope this goes without saying, but I am the only person that has tested this, so install at your own risk. I or anyone else am not responsible for the damage caused to your tablet or breaking warranty.
Issues
None that I am aware of. Please let me know otherwise.
Install from Windows
If your tablet isn't rooted, please root it first. You must also have ADB working in Windows. This installer will not work from Linux, but I will provide steps below to flash from linux too.
Download attached zip file and extract on Windows PC.
Follow back-up procedure below if you want to backup your factory recovery first. (This can be skipped but you won't have your factory recovery image anymore if you skip it).
Run the Batch file labeled "Install-CWM.bat"
Done! The script will automatically reboot the tablet into recovery when complete.
Install from Linux
Ensure tablet is rooted
Download attached file and unzip it
Code:
adb push recovery.img /sdcard/
Code:
adb shell dd if=/sdcard/recovery.img of=/dev/block/mtd/by-name/recovery
Code:
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
Done! You have copied the recovery image to the internal SD, copied it to the recovery partition, and moved the factory recovery image so it doesn't over-write CWM the next time you reboot.
Backup Procedure
From your computer with ADB working
Code:
adb shell dd if=/dev/block/mtd/by-name/recovery of=/sdcard/factory-recovery.img
Code:
adb pull /sdcard/factory-recovery.img
You have copied the recovery partition to your internal SD and copied it to your computer.
Download Link
http://goo.gl/aGjiij - Mega
Click to expand...
Click to collapse
Please can you upload a stock recovery.img backup? Thanks!! :good:
J001E said:
Please can you upload a stock recovery.img backup? Thanks!! :good:
Click to expand...
Click to collapse
I have added a link to the op. Thanks.
Just tested, I can confirm it works.
Most easy way to install on linux :
Use this rkflashkit
Also works across 4600 models. Just don't use key test as you'll trap yourself inside and have to power off manually.
Sent from my HP Slate 7 using Tapatalk
how to flash stock recovery?
preferably from CWM
Just so you guys know I got a request to port my custom ROM for the Slate 7 Plus to the Slate 7 and worst case scenario I can get a build out Monday.
Sent from my Sero 7 Pro using Tapatalk
gless said:
how to flash stock recovery?
preferably from CWM
Click to expand...
Click to collapse
You can flash the stock recovery via Flashify if you're rooted.
Sent from my Sero 7 Pro using Tapatalk
I tried to install this by it comes up with an error:
/dev/block/mtd/by-name/recovery: cannot open for write: Permission denied
Click to expand...
Click to collapse
Any advice? Thanks!
Python. said:
I tried to install this by it comes up with an error:
Any advice? Thanks!
Click to expand...
Click to collapse
Are you rooted?
Sent from my HP Slate 7 using Tapatalk
goodguy25 said:
Are you rooted?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
Yep. That was the first thing I checked. Confirmed it with Root Checker...
Edit: For extra information, I have the HP Slate 7 2801 (Same as the 2800 version)
Python. said:
Yep. That was the first thing I checked. Confirmed it with Root Checker...
Click to expand...
Click to collapse
If I were you, I would get the Cwm recovery on to the tablet, then using terminal emulator to backup the stock recovery and install the Cwm one.
Sent from my HP Slate 7 using Tapatalk
goodguy25 said:
If I were you, I would get the Cwm recovery on to the tablet, then using terminal emulator to backup the stock recovery and install the Cwm one.
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
Could you clarify that? How would I get CWM recovery on to the tablet? I'm getting the error message when running the Batch file 'Install-CWM.bat'. The cmd console has that message about permission being denied and then it says installation complete and press to reboot. When rebooting, it goes to the stock recovery...
Python. said:
Could you clarify that? How would I get CWM recovery on to the tablet? I'm getting the error message when running the Batch file 'Install-CWM.bat'. The cmd console has that message about permission being denied and then it says installation complete and press to reboot. When rebooting, it goes to the stock recovery...
Click to expand...
Click to collapse
Try taking the CWM .IMG file and flashing it via Flashify.
Sent from my Sero 7 Pro using Tapatalk
I looked through my batch script. I think I need to modify it because it's not executing as root. Use the steps I created for Linux except from Windows command prompt. That's all the batch file is doing.
Sent from my LG-E970 using XDA Premium 4 mobile app
jerbear294 said:
Try taking the CWM .IMG file and flashing it via Flashify.
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
I tried this but when I open Flashify, it says 'You don't have root/superuser access'. But, Root Checker says that I have root and SuperSU is working...
rjwil1086 said:
I looked through my batch script. I think I need to modify it because it's not executing as root. Use the steps I created for Linux except from Windows command prompt. That's all the batch file is doing.
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried doing that but there's an error on Step 2:
rjwil1086 said:
adb shell dd if=/sdcard/recovery.img of=/dev/block/mtd/by-name/recovery
Click to expand...
Click to collapse
It states that:
Code:
/dev/block/mtd/by-name/recovery: cannot open for write: Permission denied
Python. said:
I tried this but when I open Flashify, it says 'You don't have root/superuser access'. But, Root Checker says that I have root and SuperSU is working...
I tried doing that but there's an error on Step 2:
It states that:
Code:
/dev/block/mtd/by-name/recovery: cannot open for write: Permission denied
Click to expand...
Click to collapse
Strange. Try rerooting, both issues are connected to root. It could be the SU binary as well, does SuperSU want you to update?
Sent from my Sero 7 Pro using Tapatalk
jerbear294 said:
Strange. Try rerooting, both issues are connected to root. It could be the SU binary as well, does SuperSU want you to update?
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
I've tried rebooting several times, SuperSU doesn't need an update but it's still not working...
I'll need a bit more time to make the ROM. Sorry guys, I've been trying to tackle an issue with porting CWM to the Slate 7 Plus. I will definitely have a ROM for you guys by the time Saturday rolls around.
Sent from my Sero 7 Pro using Tapatalk
Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks
eReader Fan said:
Hi. I have to flash a TWRP backup and can't do it thorugh custom recovery due I have a Yotaphone (the phone with a LCD screen by one side and a eInk screen by the other side) and the LCD screen is broken, so I have to use fastboot or adb (as far I know). I cannot even install a ROM because it needs the LCD screen for the first start.
The question if I can do it, cause I know it could be problems with formats.
(I asked this on Yotaphone specific xda forum but no one answered)
Thanks
Click to expand...
Click to collapse
You would probably have better luck flashing the stock firmware or have someone with the same device create an adb backup then restore it via adb.
Or if you know which individual .img files you need, have them pull a copy of whichever individual .img files you need(for example: system, boot, etc) then fastboot flash them or use adb shell to dd the .imgs back onto your device in the partitions they belong in.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?
eReader Fan said:
@Droidriven ,you are right about it would be easy to fash a stock rom, but the LCD screen is necessary for that due the first boot. Maybe I am a little lucky 'cause I live with person who has the same device as me.
I tried the adb backup -all but it seems to just make a backup of the personal data.
Making a dd backup patition would be the better, but for some reason my device isn't recognized as a MTP device and can only connect in PTP. Tried to change the configuration on the phone but still only works with PTP, and I think in PTP mode doesn't have a mounted folder where I can make this stuff.
What I don't know how to do is the dd within the adb shell. It will work connected in PTP mode?
Click to expand...
Click to collapse
Is USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Yes, debuggind mode is on. In PTP mode, adb sees my device correctly, in MTP mode appears like ???????
I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!
eReader Fan said:
I think maybe the answer is where that you mentioned about "adb shell". As long as I can't see the phone mounted in MTP mode it's the only way I see. Now I am searching for the way on pointing the dd output file outside the adb shell. So the process is:
BACKUP:
-adb shell > dd partitions saving them outside the phone
FLASHING:
-fastboot partition by partition
Another problem I have is to know which partion is each, 'cause with "mount" I don't get so much information and with "cat /proc/partitions" only have 13 partitions with their size and no more info. I am looking what to "adb push" that can help me. Maybe install busybox.
Trying to backup&restore without MTP, without access to the recovery nor SDcard... Harder is impossible!!!
Click to expand...
Click to collapse
This command in adb shell or Terminal Emulator should give you your partitions and names(obviously you'd type "su" then press enter then run this command)
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The part with "msm.sdcc.1" might be different for your device. If that command doesn't work I'll help you find what needs to go in that part of the command for your device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
su is not found inside the adb shell, and I found this is cause is not rooted. I have to do it through TWRP in android 6.
As I said, I have two devices of my model so I hope I find time tomorrow for doing it. I also hope to can flashing it to the other device in fastboot mode or some way it doesn't need the main screen (remember I have a LCD screen and a eInk)
I will say something when I do the root. Thanks
Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?
eReader Fan said:
Finally did it!
It appears each partitions clearly with the "ls" command you give to me. The question now is how to dd outside the phone. Have I to mount the pc inside the shell or what?
Click to expand...
Click to collapse
adb shell should work to dd, you just need to make absolutely certain that you are dd-ing the correct .img to the correct partition(mmcblk0xx), the partition number would go where the xx is.
For example, my recovery.img would be flashed to mmcblk018(the number of my recovery partition.
If you dd an .img to the wrong partition, you'll brick the device, the command has to be exactly correct, no margin for error or easy fix if you get it wrong.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I know all this stuff, but first I need to make the .img of each partition, and I though with adb shell I could do a dd to outside the phone. The TWRP backup I have isn't .img files, they are .win files.
I searched again if its possible to do that and all I found is the xda thread about doing a workaround with adb forward and busybox. If there is no more options I will do that.
What I thought to do is create a backup of the needed partitions and save them in the userdata free space. I think this have to be possible, but as I cannot use the LCD screen I have to do the backup where I do not have to pass thorugh the first boot configuration, cause it is did in the LCD screen. Which partitions have I to backup? Only system and boot? Or there is another tool for creating .img backups?
EDIT: Also found the twrp adb possibilities (http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html) but have the same problems than with dd
I frequently modify boot and recovery partitions from within terminal app. Here's what I do to grab the boot partition for example(you likely want BusyBox installed first)
cat /dev/block/bootdevice/by-name/boot >boot.img
or
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Make changes, then reverse the commands to write back. I think cat gives you a more verbatim copy for initially cloning a partition. I have had success with both.
The question that brought me here is what happens if i flash all partitions from a firmware archive and attempt to upgrade a whole system this way from twrp recovery.....
If you just don't want root, or your need to sell your phone, or whatever, you can use this to return your phone to stock v10q:
Flash this zip from TWRP. This is every piece of the v10q firmware: h910_10q_full_stock.zip
SHA1: 720f122605dda361b8d8de1abaa8a56326416056
Wipe Cache/Dalvik Cache
Format data
Reboot
That is it. Your phone will be bone stock v10q.
If you want to root again after you flash this, use this procedure.
-- Brian
I flashed the system that went well when I flash the return to stock zip it ends with Error 1
Sent from my LG-H910 using Tapatalk
What version of TWRP? I tested this on 3.1.1
I also have 3.1.1 .... I tried flashing from internal storage and SD card I did also check the SHA1's to make sure they match and they do. So what's the SHA1 out of the system image itself just to make sure it's correct once it's unzipped (considering I don't have a computer so I'm using my phone to extract the image)
Sent from my LG-H910 using Tapatalk
I'm also getting error 1 trying to install the zip. TWRP 3.1
Unzip failed. Aborting...
Updater process ended with ERROR: 1
Error installing zip ...
Updating partition details...
...done
Would a log from TWRP of the failed flash help I can go try and Flash again and then copy the log if that will help
Sent from my LG-H910 using Tapatalk
Well crap -- it must be a bad upload. I will upload a new copy in a bit.
Thanks @deadguyperez for the exact error: Unzip failed -- that means it is a bad zip.
-- Brian
Please don't forget to fix this I'm running WETA and it's fan-****ing-tastic so I'll probably never go back to stock but just in case I need to.... would be nice to have the files. Thanks boss! Stay safe.
Yea, dealing with the damage from Irma, but I should be back in shape by Wednesday.
-- Brian
status??
runningnak3d said:
Yea, dealing with the damage from Irma, but I should be back in shape by Wednesday.
-- Brian
Click to expand...
Click to collapse
@op have you had the chance to work on this any more? I'm excited to get back to full stock if possible so I can warranty out my phone. Front Camera and Accelerometer both don't work anymore...
Does this relock the bootloader as well?
jetracer said:
Does this relock the bootloader as well?
Click to expand...
Click to collapse
It will yes
Sent from my LG-H910 using Tapatalk
First post updated with HOPEFULLY fixed zips. Since my H910 is currently my test bed for LAF research, it is bone stock so I can't test these. The worst that will happen is that you get an error. If so, PM me, or @ mention me in this thread so I can work with you to find out what is wrong.
-- Brian
runningnak3d said:
First post updated with HOPEFULLY fixed zips. Since my H910 is currently my test bed for LAF research, it is bone stock so I can't test these. The worst that will happen is that you get an error. If so, PM me, or @ mention me in this thread so I can work with you to find out what is wrong.
-- Brian
Click to expand...
Click to collapse
@runningnak3d I got this error: Updater process ended with ERROR: 1. Error installing zip file /sdcard/download/v10m_return_to_stock.zip
Any ideas?
Also - The 5GB system.img file loads extremely quick. Seems sketchy to me, but maybe that's normal?
EDIT - I'm running TWRP 3.0.2-1 and it does say that the system image flashed properly. That much has been completed.
sirslipzalot said:
@runningnak3d I got this error: Updater process ended with ERROR: 1. Error installing zip file /sdcard/download/v10m_return_to_stock.zip
Any ideas?
Also - The 5GB system.img file loads extremely quick. Seems sketchy to me, but maybe that's normal?
EDIT - I'm running TWRP 3.0.2-1 and it does say that the system image flashed properly. That much has been completed.
Click to expand...
Click to collapse
Got past the error and booted into Android by using ADB to flash all the files in the return_to_stock zip. It was tedious, but I typed out the list for anyone who just wants to copy and paste each line into their CLI.
dd if=aboot of=/dev/block/bootdevice/by-name/aboot
dd if=abootbak of=/dev/block/bootdevice/by-name/abootbak
dd if=apdp of=/dev/block/bootdevice/by-name/apdp
dd if=boot of=/dev/block/bootdevice/by-name/boot
dd if=cmnlib of=/dev/block/bootdevice/by-name/cmnlib
dd if=cmnlib64 of=/dev/block/bootdevice/by-name/cmnlib64
dd if=cmnlib64bak of=/dev/block/bootdevice/by-name/cmnlib64bak
dd if=cmnlibbak of=/dev/block/bootdevice/by-name/cmnlibbak
dd if=devcfg of=/dev/block/bootdevice/by-name/devcfg
dd if=devcfgbak of=/dev/block/bootdevice/by-name/devcfgbak
dd if=factory of=/dev/block/bootdevice/by-name/factory
dd if=hyp of=/dev/block/bootdevice/by-name/hyp
dd if=hypbak of=/dev/block/bootdevice/by-name/hypbak
dd if=keymaster of=/dev/block/bootdevice/by-name/keymaster
dd if=keymasterbak of=/dev/block/bootdevice/by-name/keymasterbak
dd if=laf of=/dev/block/bootdevice/by-name/laf
dd if=lafbak of=/dev/block/bootdevice/by-name/lafbak
dd if=modem of=/dev/block/bootdevice/by-name/modem
dd if=msadp of=/dev/block/bootdevice/by-name/msadp
dd if=persist of=/dev/block/bootdevice/by-name/persist
dd if=pmic of=/dev/block/bootdevice/by-name/pmic
dd if=pmicbak of=/dev/block/bootdevice/by-name/pmicbak
dd if=raw_resources of=/dev/block/bootdevice/by-name/raw_resources
dd if=raw_resourcesbak of=/dev/block/bootdevice/by-name/raw_resourcesbak
dd if=rct of=/dev/block/bootdevice/by-name/rct
dd if=recovery of=/dev/block/bootdevice/by-name/recovery
dd if=recoverybak of=/dev/block/bootdevice/by-name/recoverybak
dd if=rpm of=/dev/block/bootdevice/by-name/rpm
dd if=rpmbak of=/dev/block/bootdevice/by-name/rpmbak
dd if=sec of=/dev/block/bootdevice/by-name/sec
dd if=tz of=/dev/block/bootdevice/by-name/tz
dd if=tzbak of=/dev/block/bootdevice/by-name/tzbak
dd if=xbl of=/dev/block/bootdevice/by-name/xbl
dd if=xbl2 of=/dev/block/bootdevice/by-name/xbl2
dd if=xbl2bak of=/dev/block/bootdevice/by-name/xbl2bak
dd if=xblbak of=/dev/block/bootdevice/by-name/xblbak
Crap. There must not have been a problem with the zip, but a typo in the Edify script.
Sorry about that, I probably missed a ; some place.
Obviously I'm lost so maybe someone can help me
1) 1st LG android phone and so far I'm worried. Phone is beautiful I got it for a $100 due to the camera lens glass being shattered.
2) I'm looking for which variant I have. I own the at&t v20 which number is that?
3) I'm looking for how to root the phone and boot loader. Is it currently possible? Which method can/should I use because the entire V20 section isn't broken down like the galaxy note.
Really appreciate all your time
About to give this a try so....
Step 1 flash System Image
Step 2 Flash Return to stock
Step 3 Reboot and Profit?
Overgloc said:
About to give this a try so....
Step 1 flash System Image
Step 2 Flash Return to stock
Step 3 Reboot and Profit?
Click to expand...
Click to collapse
That's the way to do it. Someone earlier tried but the return to stock zip errored out in twrp. Possibly a broken script.