When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
borgqueenx said:
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
Click to expand...
Click to collapse
I read your post in my guide thread. What recovery do you have CWM or TWRP?
borgqueenx said:
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
Click to expand...
Click to collapse
I know my device(From the Netherlands Sim Unlock) is on WWE firmware. Is yours carrier branded?
My advice would be to try Reinstalling CWM through HTC One AIO toolkit and then place the backup back in the CWM folder.
Maybe that will work.
clockworkmod is the installed recovery.
it just doesnt want to start the restore function. i can however select install from sd card fine, proofing that it has no problems seeing the data....
mine is not carrier branded.
So when you attempt to do the restore from CWM it lists the date/name of your backup but fails? Or can you not even get CWM to start the restore because it doesn't see the backups?
crushalot said:
So when you attempt to do the restore from CWM it lists the date/name of your backup but fails? Or can you not even get CWM to start the restore because it doesn't see the backups?
Click to expand...
Click to collapse
no it does not list anything.
tried moving the backup folder but i have no idea where to place it. already tried putting it in root, triying to put it in /backup and in /clockwordmod or something.
the error i get is: couldnt open directory, no files found.
borgqueenx said:
no it does not list anything.
tried moving the backup folder but i have no idea where to place it. already tried putting it in root, triying to put it in /backup and in /clockwordmod or something.
the error i get is: couldnt open directory, no files found.
Click to expand...
Click to collapse
Sorry this part can be tricky because folder path is slightly different on 4.1.2 than 4.2.2. Also I haven't used CWM in a long time since I switched to TWRP.
Did you try putting the entire clockwordmod folder in:
/data/media
Then try the restore.
crushalot said:
Sorry this part can be tricky because folder path is slightly different on 4.1.2 than 4.2.2. Also I haven't used CWM in a long time since I switched to TWRP.
Did you try putting the entire clockwordmod folder in:
/data/media
Then try the restore.
Click to expand...
Click to collapse
had to make both folders, they didnt exist. there is a .data folder though.
edit: didnt work putting the backup folder in there.
borgqueenx said:
had to make both folders, they didnt exist. there is a .data folder though.
edit: didnt work putting the backup folder in there.
Click to expand...
Click to collapse
You didn't use the correct folders. I am not talking about folders on the root of your sdcard, I am talking about root of file system.
You should have a file explorer tool that will allow you to navigate to root and have R/W permissions so we can move files if needed. If not go to the play store and install https://play.google.com/store/apps/...wxLDEwOSwiY29tLmVzdHJvbmdzLmFuZHJvaWQucG9wIl0
Open the application and on the top left there is a small icon, click it and should open the fast access menu. Choose Root Explorer and then Mount R/W when prompted, click ok (keep defaults).
Now you should be at the device root and it will say Device in the top middle of ES.
Now browse to /data/ then /media
If you do not see a clockwork mod folder in media that is where we need to move the CMW backups in order to be able to restore them from recovery.
So move the clockwordmod folder from media/0/clockworkmod to the root of /media folder so it looks like
/data/media/clockworkmod(folders within here have your backups)
Then boot into recovery and try the restore.
crushalot said:
You didn't use the correct folders. I am not talking about folders on the root of your sdcard, I am talking about root of file system.
You should have a file explorer tool that will allow you to navigate to root and have R/W permissions so we can move files if needed. If not go to the play store and install https://play.google.com/store/apps/...wxLDEwOSwiY29tLmVzdHJvbmdzLmFuZHJvaWQucG9wIl0
Open the application and on the top left there is a small icon, click it and should open the fast access menu. Choose Root Explorer and then Mount R/W when prompted, click ok (keep defaults).
Now you should be at the device root and it will say Device in the top middle of ES.
Now browse to /data/ then /media
If you do not see a clockwork mod folder in media that is where we need to move the CMW backups in order to be able to restore them from recovery.
So move the clockwordmod folder from media/0/clockworkmod to the root of /media folder so it looks like
/data/media/clockworkmod(folders within here have your backups)
Then boot into recovery and try the restore.
Click to expand...
Click to collapse
tried to do exactly what you told me.
there is a data folder in root, but there is no media folder inside of that.
and if i try to create it it fails and says i should try giving the folder another name.
edit: never mind a restart of the app fixed it.
EDIT: didnt work.
my backup folder is inside /data/media/clockworkmod/
and clockwork recovery still gives desame error.
First confirm where CWM is actually putting your backups. Do this by booting into recovery and choose to do a backup. Then uncheck all partitions but the smallest and allow it to backup.
When you reboot navigate through the folders we have been talking about and see the exact path of where it put it. Then compare the contents of the backup folders to make sure it is not your original backup that is messed up.
As long as you place your backup(inside its folder) in the folder where CWM put the test backup, then you should be able to see it from recovery and restore it. If not your original backup may not be any good.
Going offline for about hour for lunch. Be back around 1:30pm EST.
grrrrrr...
made a backup for testing where clockword puts them.
they are in /data/media/clockwordmod/backup
my backup is placed in /data/media/clockwordmod.
when i try to move my backup folder to /data/media/clockwordmod/backup it says successfull, but nothing happens. i cant seem to move the folder.
EDIT: ok copying pasting worked instead of cutting pasting.
i now restored...but for some reason recovery is still clockwordmod, and it still shows tampered and unlocked on first screen before recovery.
Well you probably backed up with the custom recovery installed, right? You'll have to flash the stock recovery manually.
If you want it to be locked, you'll have to lock it. revone will do that for you, after you've flashed stock recovery.
BenPope said:
Well you probably backed up with the custom recovery installed, right? You'll have to flash the stock recovery manually.
If you want it to be locked, you'll have to lock it. revone will do that for you, after you've flashed stock recovery.
Click to expand...
Click to collapse
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
borgqueenx said:
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
Click to expand...
Click to collapse
Odd.
Have you tried looking for the stock recovery? A high proportion of the posts here are about returning to stock.
borgqueenx said:
grrrrrr...
EDIT: ok copying pasting worked instead of cutting pasting.
i now restored...but for some reason recovery is still clockwordmod, and it still shows tampered and unlocked on first screen before recovery.
Click to expand...
Click to collapse
That is all normal. All you have done is reset the ROM back to default. You will still need to restore the stock recovery and then relock the bootloader to get to 100% stock.
I am trying to find all the info needed for you to finish up and I will post it.
---------- Post added at 02:02 PM ---------- Previous post was at 01:44 PM ----------
borgqueenx said:
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
Click to expand...
Click to collapse
Back in post number 4 you state that CWM is your installed recovery.
So it seems correct that you have a custom recovery installed. However since you are S-Off, before I put together something for you to go back I need to know:
Did you upgrade your firmware?
Did you flash a new hboot (to get rid of the red warning lettering)?
Did you flash a new splash screen?
If you answered no to all three of those questions, you should be able to get back to stock by performing the following:
Download the ResetRecovery zip I made for you here:
https://dl.dropboxusercontent.com/u/36946918/ResetRecovery.zip
Unzip all the files into a folder. (examples will use C:\temp)
Install the HTCDriver.exe to make sure the device drivers are installed on your PC.
Make sure that USB device debugging is enabled on your device.
Open a command prompt and navigate to that folder - Start>Run>cmd Enter
Code:
cd c:\temp
Connect USB cable to phone and PC.
With the PC booted type:
Code:
adb reboot bootloader
When the bootloader screen appears:
Code:
fastboot erase cache
Then:
Code:
fastboot flash recovery recovery.img
Reboot phone and go into recovery to make sure that CWM has been replaced by HTC stock recovery. If HTC recovery appears then reboot phone.
Now relock the bootloader:
Use the revone file that you probably used to get S-Off. (If needed it can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2314582)
Push revone to your device:
Put the downloaded revone (rename file to just revone) file in your adb/fastboot folder (c:\temp) and push it using this command:
Code:
adb push revone /data/local/tmp/
open a adb shell by typing:
Code:
adb shell
Now change to that directory:
Code:
cd /data/local/tmp
Now set permissions
Code:
chmod 755 revone
Since you have the tampered flag run this to remove it:
Code:
revone -t
Now do this so it will show locked:
Code:
revone -l
The newer revisions of revone don't do the actual locking any longer but it may output the command you need to run to fully re-lock:
Type exit to exit the adb shell session and issue the command to re-lock the device:
Code:
fastboot oem writesecureflag 3
Now verify that it worked by booting into the bootloader:
Code:
adb reboot bootloader
You should see it say Locked at the top and S-On, just like it was out of the box!
i have no idea if i upgraded firmware. i was from stock to android revolution wich is the newest android version.
but now i am back on stock.
software number 1.29.401.16
i didnt try to get rid of warning texr and i didnt flash a custom splash screen.
can i proceed with those instructions?
borgqueenx said:
i have no idea if i upgraded firmware. i was from stock to android revolution wich is the newest android version.
but now i am back on stock.
software number 1.29.401.16
i didnt try to get rid of warning texr and i didnt flash a custom splash screen.
can i proceed with those instructions?
Click to expand...
Click to collapse
Yes, you would know if you flashed firmware because it has many warnings and a few steps. Your version number is stock, the thing that worries me is that you are S-off and originally you thought you only unlocked bootloader.
Did you use revone or moonshine to achieve S-off?
Do you see the red warning lettering on the splash screen when booting?
AS long as the custom recovery is back to stock and you see the red warning letter on splash then you should be ok to proceed with locking now.
crushalot said:
Yes, you would know if you flashed firmware because it has many warnings and a few steps. Your version number is stock, the thing that worries me is that you are S-off and originally you thought you only unlocked bootloader.
Did you use revone or moonshine to achieve S-off?
Do you see the red warning lettering on the splash screen when booting?
AS long as the custom recovery is back to stock and you see the red warning letter on splash then you should be ok to proceed with locking now.
Click to expand...
Click to collapse
is s-off desame as unlocking bootloader?
i unlocked bootloader yes. no idea about s-off. never did anything where i saw s-on or s-off.
yes i see those red warning letters.
i have never used or heard of revone or moonshine before you mentioned it here.
need to know how to get stock recovery back then^^
Related
The other day my phone's touchscreen developed a dead spot. Verizon was kind enough to send me a "Like-New" replacement and requested that I return the old phone. The only problem with that was I had hacked the hell out of it and didn't want them to see what I did and charge me.
I had rooted the phone, installed Clockwork Recovery, set S-OFF with Unrevoked Forever, updated to the latest radio and installed all kinds of different ROMs before finally settling on CM6. Now I had to find a way to install either stock 2.1 or stock 2.2 with the correct radio for either one, flash back the stock recovery, and finally set the phone back to S-ON. If you find yourself in a similar situation, you'll probably want to read this instead of spending 6 hours pulling your hair out, like I did. Here's what I finally came up with:
STEP 1: Get ADB Running.
Make sure you have ADB up and running. If you're rooted with a custom ROM and you don't have ADB running you have more problems than I can help you with. If you use a Mac, see Step 1A below to make things a little easier when using ADB.
Step 1A: (Mac Users Only) Make Your Life Easier.
Let's add the android SDK tools folder to your .bash_profile. What does this do, you ask? It makes it so that you can run any ADB commands without having to be in your SDK Tools directory. How do we do this?
Open a terminal window. Type
Code:
nano ~/.bash_profile
This will open a text editor in the terminal and create a new text file in your home directory called .bash_profile, which will be invisible in the Finder.
Enter the following:
Code:
PATH=$PATH:/Applications/Utilities/android-sdk-mac_86/tools
export PATH
!!IMPORTANT!! I have my "android-sdk-mac_86/tools" folder inside my "Utilities" folder, which is inside the "Applications" folder. If you have your android sdk folder somewhere else you will have to change the above text to reflect the proper path to your folder.
Hit ctrl-x. Not cmd-x, ctrl-x.
The editor will ask you if you want to save changes. Press "Y".
It will ask you what you want the file name to be. Just press enter, as we've already named it .bash_profile.
Quit and re-open terminal.
You can now use any command in the SDK tools folder from any directory.
STEP 2: Install Fastboot.
Make sure you have the HTC Fastboot tool installed. If you don't, you can get it here: http://developer.htc.com/adp.html
Download it for your particular operating system.
Another tip for Mac users: Once you download and unzip it, rename it from "fastboot-mac" to just "fastboot", then place it in your SDK Tools directory.
STEP 3: Downgrade To 2.1 With Old Radio.
We now need to downgrade our radio and get back to stock 2.1. The best way I found to do this was explained in this thread: http://forum.xda-developers.com/showthread.php?t=757927
Download the zip and follow the instructions.
Hat tip to Berzerker7 for the write-up, and aiccucs for putting together the zip file in that thread.
The next step will be a little bit of backtracking, but it's mostly painless, and it still seems to be the easiest way to do this.
STEP 4: Set NAND To S-ON.
We now need to set the NAND to S-ON. Problem is, in step 3 we flashed the stock recovery back onto the phone. Not a huge issue.
First, go to unrevoked.com and download unrevoked3. Run it. This will re-root the phone and install Clockwork recovery. Once this is done, go here: http://unrevoked.com/rootwiki/doku.php/public/forever and download the unrevoked-forever S-ON Tool.
Copy this file to your SD card and rename it "update.zip"
You can do that with adb like this:
Code:
adb push /path/to/unrevoked-forever-son.zip /sdcard/update.zip
Reboot into recovery and use Clockwork to apply the patch, which will set the NAND back to S-ON.
STEP 5: Get The Phone To Accept Stock Recovery With S-ON
This was the biggest problem that I ran into. The phone would regurgitate every zip I found which contained a stock recovery when the phone was set S-ON. I finally found a way around that.
First, download this PB31IMG.zip file: http://d01.megashares.com/index.php?d01=CHoQD3B
This IMG file was posted by Diego Mejia, on a youtube video he uploaded. Thanks to Diego, his work was very helpful in this process.
Here's the catch: in order to apply this PB31IMG.zip, we need to downgrade HBOOT or we'll get an error, due to the fact that we had set S-ON in the previous step.
Here is a link to a post on androidforums.com with an attached zip file called "revert.zip": http://androidforums.com/incredible-all-things-root/123816-how-revert-back-earlier-version-hboot.html
Credit is due to adrynalyne for coming up with this process and posting the files, I just tweaked his instructions a bit to make them work for me.
Once the "revert.zip" file has been downloaded, follow adrynalyne's instructions on what to do with the files. Reposted below:
Boot the phone into Clockwork Recovery.
Go to partitions, and mount data.
Type the following commands in a terminal window:
Code:
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Watch for your phone to reboot to a silver HTC logo.
Then type:
Code:
fastboot devices
Verify your device shows up/responds/etc.
Click to expand...
Click to collapse
If the "fastboot" command works you should see an "H" followed by a string of random numbers and letters. So far, so good.
STEP 6: Reapply Stock 2.1 With Stock Recovery.
Once you've run the "fastboot" command successfully, go ahead and pull the battery. Leave the phone off. Go back to the PB31IMG.zip you downloaded in step 5, and copy it to the root of your SD card. Put the SD card back in the phone and boot it into recovery. If you've done all this correctly, the phone should recognize the PB31IMG.zip as valid and ask if you want to apply it. Do so. This will reflash the stock 2.1 ROM with the stock recovery while the phone is set S-ON. You can now send your phone back to Verizon.
STEP 7: Profit.
--B
Hey Mods, any chance of a sticky?
--B
There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.
Berzerker7 said:
There's a much easier/faster way to do this:
Just S-ON before you downgrade a first time, and then flash_image misc right away. The PB31IMG will take and you'll be at 2.1 with a single RUU flash.
Click to expand...
Click to collapse
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B
xraystyle said:
Interesting. I couldn't get RUU to jive for some reason and didn't happen upon the bit about the flash_image until I'd already gone around in circles for several hours. Cool if the shortcut works, though! Where was your info at one o'clock this afternoon when I needed it?
--B
Click to expand...
Click to collapse
Not reading your topic. lol
I found it easier, to just since your rooted already, just put it to S-on, then run the stock RUU for 2.2. and your done in two steps. no need for all the codes.... I just did it, got my refurb yesterday,...
Thanks for the informative post! This will help a lot of people in the future.
The Ultimate guide on how to do everything for noobs
Anyone taking these steps please be aware, you do this as your own choice/Risk....If you have anything important on your phone, back it up right now before you proceed....as everything will be wiped by the bootloader unlock!
Bootloader unlock.
Download this >http://www.mediafire.com/download.php?uma19r3pysr93dr
Unzip into a new folder on your c: called Android (C:/Android)
Plug your Phone into Computer/PC and select charge only.
Follow the guide precisely on HTC
1. Go to HTCDEV website: http://www.htcdev.com/bootloader/
2. Click on "Begin Unlock Bootloader" (create a user if you don't have one)
3. follow the instructions step 1 through step 10 on htcdev.com
4. In step 10, when posting your token, make sure you remove the blanks preceding each line
5. After you receive your Unlock_code.bin in email, follow step 11.
6. Now your rezound should reboot and you have your bootloader unlocked.
so you have updated the HBOOT and unlock bootloader....
Good now for the next bit.
If by chance you cannot unlock via HTC Dev please tell me as i maybe able to help you on that.
I require knowing which RUU you have installed, this u will find out by using HTC Dev.
Using HBOOT 1.0.7 and updating should be easy and fast.
Installing CWM 5 (Recovery Menu)
Please also read my orther thread on recoverys...it hold same details with extras >http://forum.xda-developers.com/showthread.php?t=1791707
This is a program installed into the phone itself.
This allows you to do pretty much anything you want.
Main things are Backup and restore of your device.
Flashing of custom Roms
Here is the recovery file >http://forum.xda-developers.com/attachment.php?attachmentid=852074&d=1326296914
Save the recovery.img and flash_image in the root of your adb folder.(this means C:/Android)
Now using DOS CMD window
goto C:/Android
*hint, copy the txt in these windows into your DOS window and press enter....it saves time and spelling errors*
DOS txt
Code:
adb reboot bootloader
it should now reboot and show Fastboot USB mode
DOS txt
Code:
fastboot flash recovery recovery.img
from the hboot menu, go to recovery.
now if above doesn't work and you cannot get into bootloader to flash the cwm. follow this
pull out battery
insert battery
hold volume down key and press power at same time
Hboot will appear
scroll down and select bootloader option, press power.
and your ready now in fastboot usb mode
Rooting
Please note, this method is old, current methods are simply just flash a new rom!
All roms come Pre Rooted with all apps required to run with root (Superuser)
For details in these check out the Android Development forum in our salsa section.
or go here>http://forum.xda-developers.com/forumdisplay.php?f=1043
Download this file >http://www.mediafire.com/download.php?pypn6v69o0vnvl9
(This is outdated somewhat and requires updating via Google Play)
place this file on the base of your sd card.
Now goto your new recovery menu.
use this cmd from DOS Windows
Code:
adb reboot recovery
it will reboot automatically
1-Select Install Zip from SDcard
2-Choose Zip from SDcard
3-Find Root.Zip on the SD card
4-Scroll upto Yes-Install Root.zip
it will now flash the root.zip
5-Go back
6-Reboot System Now
Now from here you will have done the following
Unlocked your bootloader
Flashed recovery system
Rooted your stock device.
if by any chance you make a mistake which is not very likely, but odd chance u do...redo the steps per section till you get it right.
WIKI
Root-2 meanings
System root giving superuser access pr SU
Root of SD - meaning base of sd no folders
ADB Android debug bridge - used with dos commands when phone is plugged into computer via USB cable
extra Utilities are Java SDK
>http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download and install accordingly to instructions given.
this gives access to more functions via ADB
thanks
thank you sir, you are a genius. i was stuck in 'adb'. and dont know what does it mean. got it cleared from geek.com . would like to suggest that please also add things like 'installing utilities from android sdk platform, root means the root directory of system(usually c:\ )for amateurs like me.
nevertheless it's really a useful post.... hats off to you and developers of this site!!!!!!
Save the recovery.img and flash_image in the root of your adb folder
MOD EDIT: No need to quote the whole post when asking a question
"Save the recovery.img and flash_image in the root of your adb folder"What does this mean root of adb folder???and from where will i get this file- flash_image??
raghavaggsss said:
"Save the recovery.img and flash_image in the root of your adb folder"What does this mean root of adb folder???and from where will i get this file- flash_image??
Click to expand...
Click to collapse
read the OP, the files are in the link provided!
>Here is the recovery file >http://forum.xda-developers.com/atta...4&d=1326296914<
can u also trim down the quotes too....being as the first post is big...
Files given by your link
Do we have to download these files from htcdev.com or can we just use your files posted here????
the files are:
adb.exe
AdbWinApi.dll
fastboot.exe
kashttl said:
Do we have to download these files from htcdev.com or can we just use your files posted here????
the files are:
adb.exe
AdbWinApi.dll
fastboot.exe
Click to expand...
Click to collapse
i've hosted the files here in my thread so u don't have to get them from HTCDEV.
Stuck at step 8.. please help!!!!
I am stuck at step 8
It's supposed to show some block of text
Which didn't come up.....
Instead I got a message saying--
<Waiting for the device>
Please help me out....
kashttl said:
I am stuck at step 8
It's supposed to show some block of text
Which didn't come up.....
Instead I got a message saying--
<Waiting for the device>
Please help me out....
Click to expand...
Click to collapse
settings>applications>Development>Debugging mode (Select this option)
Now retry the cmds.
already in debug mode
BigBearEvo said:
settings>applications>Development>Debugging mode (Select this option)
Now retry the cmds.
Click to expand...
Click to collapse
its already in debug mode...... Still not working
kashttl said:
its already in debug mode...... Still not working
Click to expand...
Click to collapse
only thing left is your hboot update!
do u have locked or unlocked in pink?
I dit it all
BigBearEvo said:
only thing left is your hboot update!
do u have locked or unlocked in pink?
Click to expand...
Click to collapse
What is
locked or unlocked in pink
Click to expand...
Click to collapse
kashttl said:
What is
Click to expand...
Click to collapse
in your hboot menu or bootloader menu, at the top of the screen it will show up locked or unlocked in a pink background, u can't miss it!
do u have this locked or unlocked?
Unlocked or locked....
It's locked..... It shows something like
LOCKED(OOW)
Click to expand...
Click to collapse
What could i do now.......!!!
kashttl said:
It's locked..... It shows something like
What could i do now.......!!!
Click to expand...
Click to collapse
unlock it...simple...without going to htcdev and following the steps which you didn't do, i cannot help
Another problem(the CWM recovery part)........ when i use the adb reboot bootloader cmd command.... it show device not found.........What can I do........!!!
kashttl said:
Another problem(the CWM recovery part)........ when i use the adb reboot bootloader cmd command.... it show device not found.........What can I do........!!!
Click to expand...
Click to collapse
select debugging mode in settings>application>Development
if this is unchecked, check it. then try cmds.
if this is already enabled and it still dont work on cmds then reboot into hboot yourself.
to do this, pull out battery, insert battery, hold volume key down while pressing power on button, hboot will appear, now wait...then select bootloader, and then fastboot usb will appear.
now follow cmds to install recovery
again all this is explained in main thread
SuperUser?
Hi BBE,
Followed your tutorial and was successful at every step. But one thing that is bothering me (or maybe I messed up at some step) is that I still do not have the Superuser (Su) rights. I used "Root Check Basic" and it says I have Root access. But when I try to run "Link2sd" or "Titanium Backup" it says I do not have Superuser rights. Is this method supposed to give us Superuser rights? If yes then what should I do now? If no then how can I get Superuser rights for my HTC Salsa?
Thanks.
Zaeem
Look in the apps list and you should see a pirate like app icon. If you do open app up and update it. This should rectify the su problem. If not.gimme a shout
BB is using Xparent Tapatalk ICS Blue
BigBearEvo said:
Look in the apps list and you should see a pirate like app icon. If you do open app up and update it. This should rectify the su problem. If not.gimme a shout
BB is using Xparent Tapatalk ICS Blue
Click to expand...
Click to collapse
Yea I did update it myself and now I have Su on my Salsa . However the binary is out dated and when I try to update it, it gives me 'failure' status. Downloaded the SuperUser binary installer fix from Market but still getting the error. Any help with that? (I think I am good even with the out dated binary though)
ZaeemRaza said:
Yea I did update it myself and now I have Su on my Salsa . However the binary is out dated and when I try to update it, it gives me 'failure' status. Downloaded the SuperUser binary installer fix from Market but still getting the error. Any help with that? (I think I am good even with the out dated binary though)
Click to expand...
Click to collapse
ok goto market, download, SuperSU looks like a large blue hashtag lol.
install that, update it etc, see if that runs, if you get successful updated binary, reboot the phone. u can run with both SU apps, but you would be better removing the old Su in favour of the new one...im gonna look around for a root.zip with new Super Su in there
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
rougegoat said:
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
Click to expand...
Click to collapse
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
wranglerray said:
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
Click to expand...
Click to collapse
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
rougegoat said:
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
Click to expand...
Click to collapse
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
wranglerray said:
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
Click to expand...
Click to collapse
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
rougegoat said:
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
Click to expand...
Click to collapse
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
wranglerray said:
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
Click to expand...
Click to collapse
Giving it a shot now.
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
wranglerray said:
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
(Edit) Success getting it to be usable again. Now to start from scratch. (/edit)
rougegoat said:
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
Click to expand...
Click to collapse
good luck! post your results i'd be interested in knowing how it ends up.
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
---------- Post added at 09:57 PM ---------- Previous post was at 09:51 PM ----------
cburch85 said:
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2250904
I know another person suggested this earlier, but failed to mention that sideloading once you're caught in this loop won't work. Run the RUU, unlock, and flash ViperRom.
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Rooted HTC one, no os, don't know how to push rom
I accidently wiped my os while putting a new rom on. I am INCREDIBLY inexperienced with this and really had no business fooling around with it. Regardless, I have the HTC One rooted with TWRP but cant get the new rom on to the phone. I'm on a mac and android file transfer is not recognizing my phone. Any help anyone could give would be great.
Try putting the rom on a usb stick and using an otg cable then mount it under twrp and flash from there?
Sent from my HTC One using xda app-developers app
Good Info
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
Thanks for the Info
Hello.
I'm having issues TWRP backups. Maybe I was undone system. I need a friend using the honor 7 PLK-L01 system backup of your phone by then compressed .zip TWRP.roi nk.len up for me to use. My machine is now no longer on the operating system.
*Help me.
thank you
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
Thank.
multi tool can use the phone while I was hanging not. and restore them in any way.
memht said:
There are many ways to bring your phone to life. But I can suggest this;
- Extract boot(if necessary) and recovery .imgs from a full rom(which one you want) via http://forum.xda-developers.com/showthread.php?t=2433454
- Flash them by adb commands
- Put the update.app file in your sd card and start the update by 3 button way
Another suggestion is more simple; use Multi-Tool to flash the stock recovery and that's it.
Click to expand...
Click to collapse
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
hotboymen2026 said:
after restore I saw this line
"MD5 failed to match on ... / ... twrp / backups /............./.........../ system.ext4.win001"
do not know why?
Click to expand...
Click to collapse
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
memht said:
I don't know actually but md5 errors are usually harmless. But if your recovery is working, just do fresh installation.
Click to expand...
Click to collapse
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
hotboymen2026 said:
Do not really undersand. I've manually restore your backup files, but only running to 99%. and restore fail.
Errors are displayed MD5 "system.ext4.win001"
Click to expand...
Click to collapse
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
memht said:
Actually I am really confused.. What is your phone's condition right now? And what do you want to do?
Click to expand...
Click to collapse
Status phone rom I'm wrong. logo only lead to hang on is TWRP, connect PC and Fastboot. but when I rom stock (PLK-L01 C432B270) is successful but unable to reboot the operating system. H7 is due to the security, it's hard to be rescued. I also put it into the service center (not the local machine), they also confused with my H7. I need to find ways to revive it, no matter how well!