Related
BEFORE YOU BEGIN
As always, mucking with your device at this level is risky. If you follow this process, you do so entirely at your own risk. I accept no responsibility for any detrimental effects resulting from following this process, or for any problems associated with the updated files. Only if you accept these risks should you use these instructions.
PREREQUISITES
Unlocked bootloader (see my guide to do this)
Working fastboot (also see my guide )
Patience
NOTES
I developed and followed this process on Ubuntu Natty, 64bit. I see no reason why it should not work on any other platform, since the only tool used is fastboot and the syntax for fastboot is the same on any platform. if you need to know how to get fastboot working, there are already many guides for that (see my how to unlock your bootloader thread, for example)
BUTTON CONFUSION
When in landscape mode, with the camera at the top, the power button is on the left 'vertical' side of the tab. On the top is the volume rocker. In this orientation:
- The LEFT side of the volume rocker is VOLUME DOWN
- The RIGHT side of the volume rocker is VOLUME UP
This might seem obvious, but to anyone who is used to phones, this is the opposite, since they were designed to be used in Portrait mode.
PREPARE
1) With your Tab in fastboot mode (step 1 of "GETTING ROOT" below), make sure you have a working fastboot implementation:
Code:
fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won't get any response.
2) Downlad View attachment skitzandroid-10-1v-root_0.2.zip and View attachment skitzandroid-stock-recovery.zip
3) Create a folder on your desktop called "root"
Code:
mkdir ~/Desktop/root
for Ubuntu or
Code:
md %userprofile%\desktop\root
for Windows
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!)
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder should now have 1 IMG file and one ZIP file.
6) This was an afterthought - Make sure fastboot is somewhere in your path (ie can be executed from anywhere). To test, 'cd' to any random folder and type 'fastboot' and make sure it runs.
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
Code:
adb push skitzandroid-10-1v-root.zip /sdcard/
from your working directory
...now the easy part
GETTING ROOT
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
Code:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
Code:
cd ~/Desktop/root
for Ubuntu or
Code:
cd %userprofile%\desktop\root
for Windows
5) Run the following command:
Temp Root:
Code:
fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
Permanent Root:
Code:
fastboot flash recovery skitzandroid-recovery.img
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options) to select "Install zip from SDCARD" (or something like that - if someone can post the exact menu item wording, I will update the guide). Press (tap!) the POWER button to confirm the menu selection
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
8) Once complete, use the Volume rocker to select "REBOOT" from the menu and press (tap!!!) the POWER button to confirm selection.
9) You're done! Press the thanks button on this thread to continue
TESTING
1) Once your Tab boots up, check your apps menu to confirm the existence of SuperUser app.
2) With the Tab attached to your PC via USB cable, do the following:
Code:
adb shell
su
..and watch the screen on your Tab for a SuperUser prompt. If you see this, congratulations!
If you have never rooted a phone/tablet before, go get Titanium Backup Pro and ROM Manager from the market. As soon as the custom ROMs start flowing in, you'll be all set to go.
Edit: How about thanking smaskell who was very patient and persistent in dumping the image from his Google IO 10.1 - for the good of his fellow XDA members. Without his help, this would not be possible.
Note that the above process doesn't flash the recovery, just loads it.
If you want to flash the recovery permanently, all you need to do is follow the guide above and then, in step 5, use this command instead:
Code:
fastboot flash recovery skitzandroid-recovery.img
You will then have a permanent recovery which you can get to by doing:
Code:
adb shell
su
reboot recovery
at any time.
Note that doing just
adb reboot recovery
Click to expand...
Click to collapse
...for some bizarre reason does not boot to recovery. Open up a shell first, as shown above.
I will also give you credit in the guide for having "Balls of Steel" to steal a phrase from PaulObrien
EDIT:
...and the Balls of Steel award goes to *drumroll*
Egan
...for having the balls to flash the recovery. Thanks egan. If I was in a battle, I'd definitely want you in our squad
FAQ
Does it need unlocked bootloader? Yes, see my other guide for this.
Do I need to wipe, or will it wipe my device? No and No.
Can I return my device to factory default config? Yes. This process does not flash the partition unless you follow the process in post 2 which is optional.
Changelog
0.2 - Added busybox (can be flashed over the top of 0.1 without wipe)
0.1 - Initial Relase
Factory Voda Tab Images
Recovery
Boot
System
Awesome news! Thanks to everyone who worked on this - I can't wait!
Great, great job you guys! This thing needs root so it can grow
Thanks a lot bcmobile and smaskell! Ill give it a go around launch.
Sent from my LG-P990 using XDA Premium App
Thank you guys, it's working great on my 10.1v
I'm pretty sure I know the answer to this already - but is there anyway of getting temp root on these devices so I can backup all my apps and data (properly) before unlocking / flashing recovery / rooting??
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
gjroeleveld said:
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
Click to expand...
Click to collapse
That's all the backup I have done so I hope so
Just uploading a new version of the update zip (v0.2) which includes busybox
bcmobile said:
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Click to expand...
Click to collapse
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
gjroeleveld said:
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Click to expand...
Click to collapse
Sorry for the ignorance, but are these fastboot or a adb commands?
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Regards
EDIT:
black beard said:
Sorry for the ignorance, but are these fastboot or a adb commands?
Click to expand...
Click to collapse
These are adb commands you need to do with su!
black beard said:
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
Click to expand...
Click to collapse
That is part of the recovery image, not the unlocked bootloader.
You can always put back a stock image using fastboot which is one of the really nice things about fastboot unlocking vs bootloader exploits. "fastboot oem unlock" can then be undone by "fastboot oem lock" and nobody would know the diff.
seraphimserapis said:
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Click to expand...
Click to collapse
Thanks!
Yeah, oem unlock doesn't actually do anything until the next boot
Egan said:
Thanks a lot bcmobile and smaskell! Ill give it a go around lunch.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Egan said:
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Click to expand...
Click to collapse
Are you going to flash it?
You will earn the official "Balls of steel" badge
Thanks,
Also remember to enable USB debugging after you have done the unlocked bootloader, took me 5 min to to realize why adb did not want to work, 5 scary min after the reboot.
I've tried to make a proper nandroid backup but haven't been able too.
Tried with romdump 0.72 but that crashes :-(
Most tutorials use Rom Manager, but that needs some work from @koush before we can use it.
I'll google on
Sent from my GT-I9000 using XDA Premium App
hi to all!! i have a doubt....
can i do a nandroid backup of my current rom using adb or fastboot parameters??
anyone can write or leave it here?
thank´s in advance!!
No. Custom recover does it. You can issue the adb reboot recover command to get into it etc....
Sent from my Nexus One using XDA App
Yea...maybe its the reason that i dont know this parameter lol
sent from my amstrad CPC powered by LOL..(premium xda)
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
bassmadrigal said:
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
Click to expand...
Click to collapse
all rigth buddy... thank´s!!! i´ve a adb fastboot command list and this does not stay in the list...
bassmadrigal said:
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
Click to expand...
Click to collapse
ok i did it with the commands that you gave to me... and i obtain it when i try...
E:UNKNOWN VOLUME FOR PATH [/SDCARD]
CAN´T MOUNT SD CARD
#.
any advise????? please.......
some one can help-me please?? thanks in advance for your advises!!
SERGI.3210 said:
ok i did it with the commands that you gave to me... and i obtain it when i try...
E:UNKNOWN VOLUME FOR PATH [/SDCARD]
CAN´T MOUNT SD CARD
#.
any advise????? please.......
Click to expand...
Click to collapse
Sorry, I was out of town all day...
At what point is this failing? I assume you actually have an sdcard loaded in the phone?
bassmadrigal said:
Sorry, I was out of town all day...
At what point is this failing? I assume you actually have an sdcard loaded in the phone?
Click to expand...
Click to collapse
thanks for your continuity in this thread!!
shell shows me this when i put my device into recovery and enter the code that was provided to my above...sd card is in my device... but i think that the problem is that i don´t know what´s exactly the status that the phone need to stay.. into recovery with sd card usb mounted?(i think that not)
with the phone booted and in usb debugging mode & only chargue?
If you are booted into the phone (ie. fully loaded and able to use your phone), you need to issue the adb reboot recovery command. If the phone is off, hold down the volume down button as you are booting up. This will load the bootloader. From there, it will do a little check, and then you can use the volume keys to go to Recovery. Hit the Power button to select it. The phone will load the 'X' screen and eventually be in recovery (the text should be green or orange).
Once you are in recovery, you don't need to do anything else on the phone. Just issue
Code:
adb shell
nandroid backup
(You might have to issue the 'su' command if it shows a $ instead of a # before you run the backup.)
bassmadrigal said:
If you are booted into the phone (ie. fully loaded and able to use your phone), you need to issue the adb reboot recovery command. If the phone is off, hold down the volume down button as you are booting up. This will load the bootloader. From there, it will do a little check, and then you can use the volume keys to go to Recovery. Hit the Power button to select it. The phone will load the 'X' screen and eventually be in recovery (the text should be green or orange).
Once you are in recovery, you don't need to do anything else on the phone. Just issue
Code:
adb shell
nandroid backup
(You might have to issue the 'su' command if it shows a $ instead of a # before you run the backup.)
Click to expand...
Click to collapse
when i did it i obtained:
Code:
~#nandroid backup
E:unknown volume for path [/sdcard]
can´t mount sdcard
and if i write su i obtain it:
Code:
~#su
/sbin/sh: su: not found
~#
sorry for my ignorance mate i´m open for your help
also i know that the device is in the correct mode thank´s to you... and confirmated with command:
Code:
adb status-window
-[2j-[2hANDROID debug bridge (adb mode)
status:unknown
Which recovery do you use?
What happens when you type
Code:
adb devices
?
bassmadrigal said:
What happens when you type
Code:
adb devices
?
Click to expand...
Click to collapse
shows me that the device its connected and a big number... this part its correct
danger-rat said:
Which recovery do you use?
Click to expand...
Click to collapse
CWM recovery
SERGI.3210 said:
CWM recovery
Click to expand...
Click to collapse
CWM 3.x, or 2.x?
same problem
danger-rat said:
CWM 3.x, or 2.x?
Click to expand...
Click to collapse
I'm having the same problem with my HeroC. If you have any idea what to do I would really appreciate it! I'm running AOSP 2.3.4, Firerats MTD, and CWmod 3xxx
Don't use CWM 3.x, stick to the latest 2.x
danger-rat said:
Don't use CWM 3.x, stick to the latest 2.x
Click to expand...
Click to collapse
Should I just flash the CW2xxx over the CW3xxx and then proceed with the nandroid backup? I can't use my screen at all, so will that be a problem?
Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.
Edit: nvm
Here is the dump. Thanks for your work.
KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?
I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.
Glad I could help. Now folks have less things to worry about when they decide to root
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.
efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).
For science
KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.
Hi guys,
Accidentally wiped the internal storage and system files, was distracted and on phone with someone else and messed it up. Didn't do a backup because I'm selling the phone and backed up all my stuff to PC before going with the wipe.
Current status:
-Tampered
-Unlocked
-S-On
-Hboot 1.44
-Bootloader with fastboot working
-Recovery TWRP 2.8.0.0. working
-Fastboot recognizes device
-Adb doesn't recognize device
-Have managed to push a stock TWRP nandroid backup for Developer Ediion by mounting. It sits along with the TWRP folder in /sdcard
-Tried RESTORE button through TWRP recovery, can't see the ROM.zip file
-Tried INSTALL button through TWRP Recovery, gets stuck at "updating partition details"
Please help me, thanks in advance.
shabx said:
Hi guys,
Accidentally wiped the internal storage and system files, was distracted and on phone with someone else and messed it up. Didn't do a backup because I'm selling the phone and backed up all my stuff to PC before going with the wipe.
Current status:
-Tampered
-Unlocked
-S-On
-Hboot 1.44
-Bootloader with fastboot working
-Recovery TWRP 2.8.0.0. working
-Fastboot recognizes device
-Adb doesn't recognize device
-Have managed to push a stock TWRP nandroid backup for Developer Ediion by mounting. It sits along with the TWRP folder in /sdcard
-Tried RESTORE button through TWRP recovery, can't see the ROM.zip file
-Tried INSTALL button through TWRP Recovery, gets stuck at "updating partition details"
Please help me, thanks in advance.
Click to expand...
Click to collapse
You will need to unzip the nandroid backup and place it in the <serial #> directory for TWRP to see it. The nandroid backup folder needs to be in //sdcard/TWRP/BACKUP/<Serial #>/<Nandroid_folder_name>. You might also change to TWRP 2.6.3.3 it works best with stock roms.
Thanks, i can try this today. If its possible, can you put up a screenshot showing the exact filepath.. Or confirm if what I understood below is accurate.
/sdcard/twrp/backup/serial #/nandroid/<contents of zip file>
shabx said:
Thanks, i can try this today. If its possible, can you put up a screenshot showing the exact filepath.. Or confirm if what I understood below is accurate.
/sdcard/twrp/backup/serial #/5.11.1540.9 TWRP NANDROID
Click to expand...
Click to collapse
See attached pictures, this is the view from the zip. You see there is only one folder in the zip. This folder is extracted out of the zip and it becomes the folder that is placed in the serial # folder. The contents of the folder are shown in the second picture. The serial # is the serial # of your phone. If you don't know it then you can find it in fastboot getvar all.
One more thing. The mount function is very inconsistent. Out of 60-70 attempts.. It mounted only once properly and I could push the stock ROM to the phone. Is there a way to unpack the zip in twrp?
shabx said:
One more thing. The mount function is very inconsistent. Out of 60-70 attempts.. It mounted only once properly and I could push the stock ROM to the phone. Is there a way to unpack the zip in twrp?
Click to expand...
Click to collapse
No, I don't think you can unpack the zip in TWRP. Just what is the file you are trying to move? Could you give the name and location where you got the file?
I got it from htc1guru database. Its the M7 TWRP Nandroid Backup CID BS US001 1.29.1540.3 .. Its for the developer edition which is the same as my phone..
Currently the phone only has twrp folder on sdcard.. And inside twrp, there's .twrps
. that's it.. I will have to create a new folder called backup, a new folder with their serial number as its name etc.
shabx said:
I got it from htc1guru database. Its the M7 TWRP Nandroid Backup CID BS US001 1.29.1540.3 .. Its for the developer edition which is the same as my phone..
Currently the phone only has twrp folder on sdcard.. And inside twrp, there's .twrps
. that's it.. I will have to create a new folder called backup, a new folder with their serial number as its name etc.
Click to expand...
Click to collapse
That file may not work with your phone it is pretty outdated. Can you post a fastboot getvar all (except for imei and serialno)? So, we can see if there is a better version or way to do the same thing.
Ok I will post the details when I get back home tonight.. Any other ideas? Anyway to get the adb working? I could then use revone for s-off and then RUU from desktop
shabx said:
Ok I will post the details when I get back home tonight.. Any other ideas? Anyway to get the adb working? I could then use revone for s-off and then RUU from desktop
Click to expand...
Click to collapse
ADB works in OS if USB Debugging is enabled and in custom recovery. In other words, the phone is in Recovery and attached to your computer you can run the command adb devices and you should see your serial number and next to it "recovery". If you are in FASTBOOT USB, only fastboot will work not ADB. Depending on your hboot you can use revone (hboot 1.4X), rumrunner (hboot 1.54) or firewater (hboot 1.5X) to achieve S-OFF.
Adb doesn't work. I tried adb devices and it would not return any values. Fastboot devices always gave the serial number but not adb. I have hboot1.44 and because of adb device not found I can't push revone too
shabx said:
Adb doesn't work. I tried adb devices and it would not return any values. Fastboot devices always gave the serial number but not adb. I have hboot1.44 and because of adb device not found I can't push revone too
Click to expand...
Click to collapse
Here try this method:
How to get ADB to recognize the device
After you re-install adb & fastboot
Disconnect your phone from the computer
Then reboot the computer and open the command window
Type: adb kill-server
Then when it is finished
Type: adb start-server
Now connect your phone to the PC
Type: adb devices
Click to expand...
Click to collapse
majmoz said:
Here try this method:
Click to expand...
Click to collapse
@majmoz
shabx said:
@majmoz
Click to expand...
Click to collapse
This is an old method that I used to get S-OFF with revone:
Revone S-OFF on the phone methodRevone Download:
http://revolutionary.io/revone
Big thanks to the Revolutionary dev team. The original thread can be found here.
Written instructions:
Download the Revone file above and transfer it to your phone (or download on your phone)
Use a root file explorer and paste the file inside the /data/local/tmp folder
Open a terminal emulator and type the following:
Code:
[B][I]su[/I][/B] (enter)
[B][I]cd /data/local/tmp[/I][/B] (enter)
[B][I]chmod 755 revone[/I][/B] (enter) (IF revone doesn’t work, type revone.bin)
[B][I]./revone -P[/I][/B] (enter)
Reboot
Open terminal again and type:
Code:
[B][I]su[/I][/B] (enter)
[B][I]cd /data/local/tmp[/I][/B] (enter)
[B][I]./revone -s 0 -u[/I][/B] (That would be a ZERO) (enter)
Reboot
That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
Code:
[B][I]cd /data/local/tmp[/I][/B]
[B][I]su[/I][/B]
[B][I]./revone.bin -t[/I][/B]
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.
Click to expand...
Click to collapse
You will need a terminal emulator you can download one from the Google Play Store.
majmoz said:
This is an old method that I used to get S-OFF with revone:
You will need a terminal emulator you can download one from the Google Play Store.
Click to expand...
Click to collapse
@majmoz
This wont work. My phone has no OS so I can't get in and download stuff from Play Store. Also the ADB steps listed by you didn't work. ADB devices does not return anything.
shabx said:
@majmoz
This wont work. My phone has no OS so I can't get in and download stuff from Play Store. Also the ADB steps listed by you didn't work. ADB devices does not return anything.
Click to expand...
Click to collapse
@majmoz
OK ADB devices found works. How do I get S-Off now? I tried Revone, but its failing with error code = 1
shabx said:
@majmoz
OK ADB devices found works. How do I get S-Off now? I tried Revone, but its failing with error code = 1
Click to expand...
Click to collapse
Let's get a rom on your phone first. Did you have a rom that you wanted to put on your phone? It should be a Sense ROM.
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@majmoz I'm currently downloading the 1.29.1540.17 from htcdev.com .. This is the same as shown in he getvar all posted earlier. Will push the ROM via adb and post results or errors. Thanks.
shabx said:
@majmoz I'm currently downloading the 1.29.1540.17 from htcdev.com .. This is the same as shown in he getvar all posted earlier. Will push the ROM via adb and post results or errors. Thanks.
Click to expand...
Click to collapse
That file is a RUU rom zip for your phone. I believe you will have to flash it in bootloader like firmware. Your bootloader will need to be relocked.
Rename file to rom.zip and put in your fastboot/adb folder.
Put the phone in bootloader/FASTBOOT USB:
After that, type:
Code:
fastboot oem lock
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
The phone came with an unlocked bootloader. Then why do I need to relock it. You have given me 2 sets of instructions above.. One is using adb and other is flashing the ruu in bootloader.
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
How did you install that Hong Kong lollipop?
mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
i installed hk lollipop zip from my custom twrp recovery. and when rom istall has finished ; recovery gone.
mrp1375 said:
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
Click to expand...
Click to collapse
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
mca1 said:
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
Click to expand...
Click to collapse
Below are 2 solutions to get a properly working recovery
Preperation:
1. Download Dual recovery installer: XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip
2. Install NDRUtils
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this: http://nut.xperia-files.com/path/XZDualRecovery/Kernel_Builder
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: X-plore File Manager The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
thank you
mca1 said:
thank you
Click to expand...
Click to collapse
Does that mean it worked?
tetsuo55 said:
Does that mean it worked?
Click to expand...
Click to collapse
Yes it worked, thank you much. :good:
tetsuo55 said:
Below are 2 solutions to get a properly working recovery
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this:
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
Click to expand...
Click to collapse
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
comcastic08 said:
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
Click to expand...
Click to collapse
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
tetsuo55 said:
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
Click to expand...
Click to collapse
snag. gy/gi8Ji. jpg
sorry i cant post links yet
comcastic08 said:
snag. gy/gi8Ji. jpg
sorry i cant post links yet
Click to expand...
Click to collapse
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
tetsuo55 said:
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
Click to expand...
Click to collapse
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
comcastic08 said:
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
Click to expand...
Click to collapse
Can I have another screenshot of that?
tetsuo55 said:
Can I have another screenshot of that?
Click to expand...
Click to collapse
snag .gy/AekHa. jpg
comcastic08 said:
snag .gy/AekHa. jpg
Click to expand...
Click to collapse
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
tetsuo55 said:
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
Click to expand...
Click to collapse
snag. gy/aWyCY .jpg
comcastic08 said:
snag. gy/aWyCY .jpg
Click to expand...
Click to collapse
All i can think of is that you have the wrong boot.img
tetsuo55 said:
All i can think of is that you have the wrong boot.img
Click to expand...
Click to collapse
i downloaded the one you said XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and renamed it to boot.img
even the twrp.img doesnt work ugh