[Q] TWRP from Terminal emulator... - Nexus 5 Q&A, Help & Troubleshooting

hi
I have this file downloaded...
Code:
-rw-rw-r-- 1 root root 11956224 Nov 14 09:42 openrecovery-twrp-2.6.3.2-hammerhead.img
766b2361daf816eb168df37c55edb709 openrecovery-twrp-2.6.3.2-hammerhead.img
The md5 matches the one on goo.im...
Can I install this "safely" from a Android terminal emulator with the following commands...
Code:
#> su -
#> dd if=./openrecovery-twrp-2.6.3.2-hammerhead.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
and then would booting into recovery mode, would start TWRP ?
NOTE: THIS IS A QUESTION... ?
I wish goomanager has option of installing downloaded file... the site is giving 403 Forbidden...

ANYONE ???

Flash the img with fastboot. That's the safest way imo.
Sent using xda-developers app

yep i would flash using fastboot. permissions and stuff might get whacked if not done that way. Not sure just guessing.

Chromium_ said:
Flash the img with fastboot. That's the safest way imo.
Sent using xda-developers app
Click to expand...
Click to collapse
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.

TheDudeAbides said:
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
Click to expand...
Click to collapse
Fastboot flash recovery nameofrecoveryfile.img
Not difficult at all
Sent from my Nexus 5

TheDudeAbides said:
If i knew how to do that, I'd totally do it. lol
My Goo.im app ain't dl'ing twrp.
Click to expand...
Click to collapse
If you go to goo.im it shows that the file has been downloaded over 12071 times!!!
Code:
openrecovery-twrp-2.6.3.2-hammerhead.img
766b2361daf816eb168df37c55edb709
Size: 11.4 MB
MD5: 766b2361daf816eb168df37c55edb709
Link: http://www.goo.im/devs/OpenRecovery/hammerhead//openrecovery-twrp-2.6.3.2-hammerhead.img
Short Link:
(view file changelog)
2013-11-05 14:14:08 PST 12071
Yet every-time I try I get a 403-Forbidden...
My main issue is my Windows is dozing, and am on RedHat most of the time... My ubuntu desktop is in storage so I cant get to
any sort of fastboot...
anyways... I just managed to install the adt on my LMDE (LinuxMintDebianEdition) and am now playing with
udev files... and reading about how to get fastboot working..!
I felt dd was fairly native... and would not cause any permission problems...
anyways.. I will flash the image with fastboot, and then dump the recovery device with dd and check the md5sum..
if it matches, I will try to erase and load it again with dd and see if this method can work..
G
UPDATE
THE dd METHOD WILL NOT WORK
I got fastboot working, loaded the twrp image and rebooted to recovery and it works...
next I dumped the "/dev/block/platform/msm_sdcc.1/by-name/recovery" and checked its md5sum
and it does not match the twrp recovery... so I bet it will not work...
JUST USE fastboot...
MOD: We can close this thread... its answered (by myself)
Click to expand...
Click to collapse

Related

NS4G Recovery Question

So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
DigitalDementia said:
So I just rooted via Pete's instructions, I'm on CWM 3.1.0.1 or something but I see some people are on 4.x.x.x what should I be on? Rom manager only lists the 3.1.0.1 thanks in advance.
Click to expand...
Click to collapse
you should upgrade to the latest, 4.x.x.x.
Im not really finding a link to that CWM version, if I flash one of the kernels will it give me the newest recovery? I know that's how people did it on the fascinate.
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Wow thanks for being so helpful! I'll do that ASAP.
Your welcome.
kijp15 said:
Going into the nexus s developement thread and look for cwm 4.x.x.x section posted by j_r0dd. The latest should be 4.0.1.4. Grab that .img file and put it into your C:\AndroidSDK\tools folder or wherever you have it located.
1. Open cmd,
cd C:\whateveryounamedit\tools
2. Boot into bootloader
3. Plug in usb and type: fastboot devices, your devices # should pop up, sometimes if its blank its still connected.
4. Type: fastboot flash recovery nameofrecovery.img
I would give a link, but im on the app.
Sorry.
EDIT: oh and be sure you grab the one for ns4g devices.
Click to expand...
Click to collapse
adb doesn't seem to recognize fastboot as a command? I'm in the bootloader though.
Anyone have a zip of the cwm 4.x.x.x recovery?
Did you install android sdk on your computer? If not, you should do that before you proceed.
EDIT: or did you put adb to your path on your computer
I'm on W7 so I just went to platform-tools and typed cmd in the address bar. However fastboot isn't in platform-tools?
So I went to tools but got another error trying to flash.
Sorry for all the questions I've never had to use fastboot.
Or just put the .img file on the root of your sdcard.
Open terminal
type flash_image recovery /sdcard/nameofrecovery.img
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Hit enter, it should now read the .img file
After that type reboot recovery to check it. Hope this helps.
kijp15 said:
Download android terminal
su
flash_image recovery /sdcard/nameofrecovery.img
Click to expand...
Click to collapse
If it says no image found?
DigitalDementia said:
If it says no image found?
Click to expand...
Click to collapse
Are you doing correctly?
I've done it a tons of time and it never gave me that msg.
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Positive. I renamed it cwm4.img for ease of use and I type:
su
flash_image recovery /sdcard/cwm4.img
Then it says flash_image: not found
kijp15 said:
When downloaded it, did it say .txt at the end, if it did change it from
.txt to .img.
And try again.
Click to expand...
Click to collapse
Still an image file.
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
kijp15 said:
Is your img file in any folders?
If it is your doing something wrong that I don't know about. Ha. If it is take out and out it on the root of your sdcard.
I've just flashed a img wit this same exact process and it went threw.
Click to expand...
Click to collapse
Ugh... frustrating! It's not in a folder, it's right on the root mocking me. Okay just so I know I'm doing it right I do it like this:
su
flash_image recovery /sdcard/cwm4.img
Right? With the spaces between recovery and /sdcard/ ?
Hmmm... that is right.. is your terminal a black or blue background?
If its black your have the wrong terminal.

[RECOVERY]Clockwork Touch Recovery 5.8.2.1 by JvS CoRp V5 TF101\G

ClockworkMod Touch Recovery 5.8.2.1 by JvS CoRp V5
ChangeLog
V1
Installation Error Fixed
V2
Reboot Loop Fixed
Internal memory install only
V3
Minor Fixes for improve performance
Still Internal Memory
V4
New Version 5.8.1.9
Improve performance
V5
New Version 5.8.2.1
LINK Removed
Work on it
Installation:
Just flash the attached zip from internal memory with 5.5.0.4 .
Tested on TF101G B80 con CM9
For change CWM download and install Recovery Installer APK and run.
Thanks Button is not cost nothing Use it
Usual disclaimer applies: if you brick your tablet, it's not my problem!
Thanks all Android Community.
jvscorp said:
ClockworkMod Recovery touch 5.8.1.8 for TF101 \G by JvS CoRp Original
Installation:
Just flash the attached zip from CWM.
Usual disclaimer applies: if you brick your tablet, it's not my problem!
Click to expand...
Click to collapse
I see you have been lurking around here for 4 years lol.. does this cwm allow flashing from both internal and external sd? great work and thanks. haven't tried it though.
I'm looking forward to trying this.
Kept getting parse error and wouldn't install (STATUS 6). Redownloading and will report back.
Edit: Booted back to CWM with a few fresh d/ls. Same error. Line 1 of 56 is BAD.
Sent from my Transformer TF101 using xda premium
gunz.jones said:
Kept getting parse error and wouldn't install (STATUS 6). Redownloading and will report back.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Me too...
10x
gunz.jones said:
Kept getting parse error and wouldn't install (STATUS 6). Redownloading and will report back.
Edit: Booted back to CWM with a few fresh d/ls. Same error. Line 1 of 56 is BAD.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Same here...
kay_kiat88 said:
I see you have been lurking around here for 4 years lol..
Click to expand...
Click to collapse
4yrs, 7 posts
But,... this looks interesting
kay_kiat88 said:
I see you have been lurking around here for 4 years lol.. does this cwm allow flashing from both internal and external sd? great work and thanks. haven't tried it though.
Click to expand...
Click to collapse
if it does both, and the install issues get resolved, then I'll flash it. Very interested...
same issue as the last official cloclwork release. will not reboot. always bqck to recovery. roach please work ur magic. thnx in advance
jefbal99 said:
if it does both, and the install issues get resolved, then I'll flash it. Very interested...
Click to expand...
Click to collapse
It only read from internal.
Right now I'm getting problems of rebooting back into recovery
baseballfanz said:
It only read from internal.
Right now I'm getting problems of rebooting back into recovery
Click to expand...
Click to collapse
Same here. I have everything stored and backed up to my external SD. Thanks to the OP for our first touch recovery. It does need some fine tuning though. Going back to Rogue for now.
Well you know what's wrong just want to say good work
Running fine now. It would be great if it had the micro SD support...
---------- Post added at 06:25 PM ---------- Previous post was at 06:08 PM ----------
Spoke too soon... It's rebooting into recovery...
I have Rogue CWM in the system memory and i tried to install over this one and didn't work... it goes back again into recovery. Anybody as any idea on how i can get in the OS? or copy Roach CWM in to the system memory?
Any help would be appreciated...
Since people are so interested in touch recovery and especially any recovery with MicroSD support and /sdcard support, then I wonder if anyone has based their take on this on the working MicroSD/Internal version (as linked to by this):
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly
I am guessing that if you know how to add the touch logic to recovery then you might be able to add very similar logic (nothing is ever the same) to this working version I linked to.
It seems odd that people are developing without using both internal and external storage but all work is appreciated.
Managed to get in the OS but i tried to install Roach and Rogue CWM over this one and it doesn't install... always comes up the same...
Any ideas?
SWEagle said:
Managed to get in the OS but i tried to install Roach and Rogue CWM over this one and it doesn't install... always comes up the same...
Any ideas?
Click to expand...
Click to collapse
After you have flash a different recovery DO NOT use the Boot into system.
Instead cold boot into the OS and use Terminal Emulator to type in the following command.
Type : su (give permission if ask, choose YES). You should get a #
Type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Type : exit
Type : reboot
Note: Hit "Enter" after each line
baseballfanz said:
After you have flash a different recovery DO NOT use the Boot into system.
Instead cold boot into the OS and use Terminal Emulator to type in the following command.
Type : su (give permission if ask, choose YES). You should get a #
Type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Type : exit
Type : reboot
Note: Hit "Enter" after each line
Click to expand...
Click to collapse
Thanks you very much for you response...
Me and a friend of mine use this adb command to stop the bootloot and with this it reach the point of the CWM instalation... now it's working fine...
Type: adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
isnt touch recovery available through rom manager now? Is that any better?
Tazzaras said:
isnt touch recovery available through rom manager now? Is that any better?
Click to expand...
Click to collapse
Not for the Transformer. The CWM available through ROM Manager doesn't work either.
how do you get out of recorvery. need help

[Q] ClockworkModRecovery (Only wants to wipe data) [SOLVED - Read / Scroll Down]

Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself (Power and vol.down), and the only options I have in the Clockwork Boot Menu are as follows:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
If I go back one page the only options I have are as follows:
Android system recovery <3e>
Android system recovery utility
reboot system now
wipe data/factory reset
wipe cache partition
wipe cache partition and package recovery
wipe nv dynamic partition
Click to expand...
Click to collapse
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Loopy Frog said:
Ok, so i have a fresh new stock of 21e flashed onto my phone. Rooted with no errors, and I have Clockwork ROM Manager installed.
If I use the app to boot into recovery my phone just automatically Wipes all data then loads back up as if a fresh install was done, so I thought I would check the problem out myself, and the only options I have in the Clockwork Boot Menu are as follows:
If I go back one page the only options I have are as follows:
I can not go back any further, they are my only options in boot recovery of which I find extremely odd. (Until this is sorted I can not install a new ROM/Kernel and fix my network)
Any help would be much appreciated.
Kind Regards.
Click to expand...
Click to collapse
That's not ClockworkMod.
That's the stock Android recovery.
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
Regards
Loopy Frog said:
ah lol (embarrassing)
Thanks though... ok so it seems that my problem is that the copious amount of things that I try to install clockwork boot, it just wont happen. Any ideas?
I am just about to see if I can do something with the LGDP2 V36 UMTS.
Regards
Click to expand...
Click to collapse
You can flash ClockworkMod Recovery with this.
[GUIDES/TOOLS]Making Developing/Flashing/Returning to Stock Easier
The Dark Lestat said:
1. Recovery Manager
This is a flashing tool that will let you install:
Stock Recovery
ClockworkMod Recovery
Touch ClockworkMod Recovery
Requirement:
You'll need to have the LG Thrill / Optimus 3D
You'll need to be rooted.
Superuser and SU have to be updated to the latest app and binary
Update Superuser in the market
Open Superuser app and go to the options
Scroll to the bottom and click "Su binary"
DOWNLOAD LINK: Recovery Manager - 18 MB
How To Use:
Extract the files with WinRar or 7zip
Launch "Recovery Manager.bat"
Make sure your phone is in "USB Debugging Mode" and is plugged in
Choose your option
Wait for the screen to refresh
Boot into recovery to verify it was flashed successfully
Click to expand...
Click to collapse
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Loopy Frog said:
No Luck :-(
Did your guide word for word, all went successfully.
However.... I can use root applications on the device etc...
Though it appears I can no longer get the clockwork boot anymore?
Click to expand...
Click to collapse
You can also use the ROM Manager app to boot into recovery.
p-vlad said:
Try: 3d+volume down+power button
hold til 3 sec after seeing the logo.
Click to expand...
Click to collapse
Nope doesn't work. >_<
The Dark Lestat said:
You can also use the ROM Manager app to boot into recovery.
Click to expand...
Click to collapse
Yeah that's what I was using when it used to work, however now when I do it, It just "deletes all user data". Obviously because it is not having any response from the Clockwork recovery boot, and goes straight into:
Android system recovery <3e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
Click to expand...
Click to collapse
I just don't understand why My boot wont change from android to the clockwork boot. >_<
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
pandaball said:
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
Click to expand...
Click to collapse
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Loopy Frog said:
Thanks Panda, I'll give it ago later when I have time, and let ya know how I go.
Click to expand...
Click to collapse
Also, I'll update the scripts with a newer version, so that it's simplified.
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
It's not using ROM Manager to BOOT into recovery.
It's using ROM Manager to install ClockworkMod that was the issue.
Very weird indeed. I also have flashed yhe 21E rom from LG. Next I rooted the phone and installed CWM touch. I have no problems with it.
JastaPein said:
Holy Sh*t .. .
dont use Rom Manager to boot into recovery.. there where so many bad reports about that app.. if you want to boot into recovery.. do this.. .
install Terminal Emulator..
type in ..
su (enter)
reboot recovery (enter)
your phone will boot into what recovery you have .. .
hope that helps!
Click to expand...
Click to collapse
Thanks, either/or this doesn't matter at this stage, I need to able to boot into recover for this or even clockwork to do it anyway. I'll keep this in mind nonetheless.
pandaball said:
Is it being flashed properly?
Try doing the flashing manually. Download the recovery image from www.clockworkmod.com/rommanager (choose touch for P920, nothing else), then open adb in cmd and type the following commands with phone plugged in:
adb push <image name>.img /data/local/tmp
adb shell su -c "dd if=/data/local/tmp/<image name>.img of=/dev/block/mmcblk0p6 bs=4096"
adb shell "rm /data/local/tmp/<image name>.img"
Replace <image name> with the filename of the img. If everything checks out, you should be able to boot into CWM. If you get errors, post them here
(I took the commands from The Dark Lestat's batch file, props go to him. I was too lazy to search for it Don't judge me, it's 12.30am here)
Click to expand...
Click to collapse
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
C:\Users\Astro\ADB>adb push x.img /data/local/tmp
3204 KB/s (5995063 bytes in 1.827s)
C:\Users\Astro\ADB>adb shell su -c "dd if=/data/local/tmp/x.img of=/dev/block/mmcblk0p6 bs=4096"
1463+1 records in
1463+1 records out
5995063 bytes transferred in 0.992 secs (6043410 bytes/sec)
C:\Users\Astro\ADB>adb shell "rm/data/local/tmp/x.img"
rm failed for /data/local/tmp/x.img, No such file or directory
Click to expand...
Click to collapse
Loopy Frog said:
All went well, expect for the last string, see below;
I renamed "recovery-clockwork-touch-5.8.1.5-p920" - "x"
Click to expand...
Click to collapse
I'm about to upload a newer version of it. Let me know if it works.
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
The Dark Lestat said:
Alright.
Here's the new Recovery Manager with updated scripts. It should be a lot cleaner now.
Recovery Manager
Click to expand...
Click to collapse
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Loopy Frog said:
You my friend, are truly amazing!! what ever your alterations were; it worked!
Thank you.
Click to expand...
Click to collapse
I think it's because my scripts were thrown together in the previous one.
Anyways, it's cleaned up.
Glad it worked!

[CWM] 6.0.3.3 for HP Slate 7

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

[ROM] H910: FULL return to stock v10q

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.

Categories

Resources