Database Develop

[Q] OneClick Root Works, But Superuser App Missing?

Hi, I posted a similar question about this under the OneRoot thread, but I don't see a lot of activity there anymore, so I was hoping to get more responses in a separate thread. I've scoured this forum and everywhere else on the Net and I haven't seen anyone experience this same issue. Hopefully someone will understand the problem and have some idea how to rectify it.
So, I have an AT&T Samgsung Captivate with the stock 2.1 Android "Eclair" build on it. I do believe there was an AT&T issued OTA update for it not long ago that put the build number up to UCJH7. I followed the instructions for TGA_Gunnman's One Click Root/UnRoot method documented here. Everything seems to work fine, in terms of booting into the recovery mode and selecting the update file. After the phone reboots, however, I do not see the Superuser Permissions app with ninja icon in my Applications area. If I browse the directory tree in my internal SD card in /system/apps, I do see a SuperUser.apk file. However, clicking on that shows me the message "Install blocked: For security, your phone is set to block installation of applications not sourced in Android Market." So it appears that rooting procedure worked, all the necessary parts were installed, but I don't have permission to execute su. I see that the xbin folder has been created, and it does contain busybox, su and something called ipctool. Also, a link does exist in /system/bin between su and /syste/xbin/su. If I use the Terminal Emulator and type "su", the prompt sits there for 10 seconds and says "permission denied".
Any ideas on what could be preventing me from gaining superuser access here?
Thanks for your help,
Mike

Download and install "SuperUser" from the Android market

OK, so here is another strange thing about this. This doesn't seem like it'd be related to my original su permission problem, but you never know. I decided to try to un-root using the one click method. Now, during the un-root script, I see the adb daemon start, but it fails on the push command writing unroot.zip to update.zip in the /sdcard folder; it says that permission is denied!. Of course, after booting into recovery, applying the update file fails, as it wasn't found in /sdcard. I'm not sure how this could have happened, as the root script was able to push the root.zip to sdcard just fine initially. Now, after I open a shell against my phone using adb, I check the permissions for the sdcard folder, and this yields rwxrwxr-x. I'm not sure, but I believe there should be another w flag set for other on sdcard. How the heck could that have been cleared?
It does look like I can copy the update.zip to sdcard manually through Windows Explorer and just manually boot into recovery using volume up + down + power, so I'm not completely dead in the water. Yet, I'd like to fix the permissions for sdcard, or else I can no longer use the one-click method.

id10terror said:
Download and install "SuperUser" from the Android market
Click to expand...
Click to collapse
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.

Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App

mskelton said:
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Click to expand...
Click to collapse
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
End points are HIGHLY important, and if you read your post carefully, you have not yet demonstrated that superuser access is broken, only the icon from which you inferred it is broken. Let me know then we can go from there
Sent from my SAMSUNG-SGH-I897 using XDA App

fatttire said:
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks, that was one of the first things I tried last night, but that did not work.

fatttire said:
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, you're right, now that I see that error message, I guess it is trying to install it. That's odd, because I thought that the oneclick method would have already installed this app during the recovery boot load?
Regarding ROM manager, funny you should ask, that was the entire genesis of why I'm trying to root, so I can backup my phone and install the custom ROMs. After I installed ROM manager and tried to run it was where I initially noticed I must not have root access. When I try to flash clockwork recovery, the app hangs for (oddly enough) around 10 seconds. I never see any prompt for granting root access to clockwork recovery, nor does it boot into the recovery mode.

Okay I have another idea.
If your goal is to simply make a backup to flash a ROM, try this:
1. Download Cog 2.3b6. Other ROMs may have the file I'm looking for but I know it is here. Also you may be able to search and find this file directly but I'm too lazy to find the link for you lol
2. Open the zip file on your computer and extract /sdcard/update.zip
3. Adb push update.zip /sdcard/update.zip
4. Reboot recovery, reinstall packages, you are in clockwork recovery and can back up your ROM.
Sent from my SAMSUNG-SGH-I897 using XDA App

I'd like to try that, except that it appears there is some type of permission snafu on /sdcard. I believe the permissions on that folder *should* be 777, but it is 775 (other has no write access) for some odd reason, and I have no clue how that happened. Hence, when adb tries to push the update.zip to the internal SD folder, it gets permission denied. As I mentioned, not sure if this is related to not being able to execute su, but it is strange nonetheless.

Guys, please disregard what I mentioned earlier about adb and not being able to push the root/unroot.zip to /sdcard. I'm a moron, and I had left the internal SD card mounted to Windows after connecting the phone via USB. Clearly for adb to push/pull off of /sdcard, the internal SD card must *not* be mounted by Windows. My mistake, sorry for the confusion.
The original theme of the thread is still unanswered though, which is how the one-click root could have worked and not installed the SuperUser app onto my phone.
I will try the recommendation earlier in the thread, to download and install the SuperUser app from Android Market to see if that fixes things.

OK, so I downloaded and installed the SuperUser app from the Market, and for whatever reason, this seems to have addressed the issue. I am now prompted to allow applications root privileges. I'm not sure why this was necessary or how it fixed things, perhaps because it overwrote the version of su that was on my phone with a newer one. In any case, it's working.

[GUIDE][DISCONTINUED] Wildfire/Buzz 2.2 - 2.1 + Links for s-off Guides & Root

AlphaRev X Beta is now available for Wildfire/Buzz users stuck on 2.2.1 with HBOOT 1.01.0001 and above. This will make your Wildfire/Buzz s-off and give you the ability to get root. Follow this excellent guide http://forum.xda-developers.com/showthread.php?t=1130881
If you have downgraded to a 2.1 rom and want to get back to official 2.2 rom to use Alpharev X Beta or have HBOOT 1.01.0002 and want official 2.2 with HBOOT 1.01.0001 to use Alpharev X Beta follow this excellent guide http://forum.xda-developers.com/showthread.php?t=1132028
Thanks to all who made this method possible and to those who developed the tools used etc.... This is not my work just trying to simplify it.
I accept no responsability if you brake your phone
Will NOT downgrade the HBOOT but useful if you need to go back to stock 2.1 rom.
Right Here we go:-
Downloads you will need:
Android SDK:- http://developer.android.com/sdk/index.html Google search for a guide to setting this up and read the guide carefully so you know how to use adb.
HTC Sync:- http://www.htc.com/uk/SupportDownload.aspx?p_id=316&cat=3&dl_id=1073 Basically for the drivers to use adb as these are included with htc sync you no longer have to install drivers from sdk to use adb.
HEX Editor:- http://mh-nexus.de/en/downloads.php?product=HxD I suggest you find a guide on making a GOLD CARD as you will need a GOLD CARD any way, this will get you ready and use to using the hex editor later in this guide.
Super One Click:- http://forum.xda-developers.com/showpost.php?p=10452428&postcount=43 Download un zip it and save to pc.
Flash_Image:- http://www.android-hilfe.de/attachm...-how-rebrand-o2-desire-fertig-flash_image.zip un zip and save somewhere on your pc you will remember.
A 2.1 rom RUU to downgrade to:- http://shipped-roms.com/index.php?category=android&model=Buzz Choose the one that best suits you WWE=Unbranded or chose one for your provider/carrier, download and save to ur pc.
Now your have set up the Android SDK you know what ADB is and how to use it (hopefully), you have created a GOLD CARD, you have installed HTC Sync, you have downloaded the 2.1 RUU.exe you want to downgrade to, you have downloaded Super One Click 1.5.5 and un zipped it and save it to ur pc and you have dowloaded the Flash_Image and un zipped it and place on ur pc.
Ready Here We Go:
Step1 - Open Super One Click and press SHELL ROOT it will run its commands and will give you temp root. You will see rooted at the bottom when its done. Try again if it says FAILED it may take a couple of attempts. ( Make sure you have adb working ) and (make sure usb debugging is ticked on your phone and unknown sources tho im not sure if unknown sources needs to be ticked, mine was and that when you plug your phone it the pc via the usb cable you select charge only on the phone)
step2 - open a cmd (command Prompt) on your pc and type adb shell (if you installed the android sdk and read about how to get to adb shell you will have no problem) (for me i type cd C:/android-sdk-windows/platform-tools and hit enter, the type adb shell. (if you see a $ try shell root in super one click again, if you see # your good to go).
step3 - copy the mtd0 file to sdcard.
(in cmd type) cat /dev/mtd/mtd0 > /sdcard/misc.img
step4 - move the misc.img to your pc and use the hex editor to edit it. (run HxD as administrator click extras, open disk image and select your misc.img you just got from your sd card).
step5 - go to 11th row down, you will find current version number at
the end of that row.
step6 - Change it to 1.25.405.1 if you want to use "Ruu_Buzz_HTC_WWE_1.25.405.1", the press file and save. (change the numbers to match the 2.1 RUU you are going to downgrade to (common sense) ok)
step7 - copy the flash_image (the one you downloaded at the start of this guide) and misc.img back to your sdcard.
step8 - (in cmd type) cat /sdcard/flash_image > /data/flash_image
step9 - (in cmd input) chmod 755 /data/flash_image
step10 - (in cmd input) /data/flash_image misc /sdcard/misc.img
Now you can flash offical android 2.1 RUU rom you downloaded earlier (don't forget to make gold card).
Now your on Android 2.1 but your HBOOT is still version 1.01.0001, so Unrevoked still wont work. So still no full root as yet.
Once again not my work just trying to keep everything simple and in one place, ALL THANKS TO ORIGINAL DEVS AND GUIDE CREATERS. BUY THEM A BEER.

Thanks for making this clear, then i wont have to explain it in details
Notice Adb is included in the SuperOneClick directory

Birthe88 said:
Thanks for making this clear, then i wont have to explain it in details
Notice Adb is included in the SuperOneClick directory
Click to expand...
Click to collapse
Yip lol. Ive been asked so many times on how to do this because i posted on a thread that i done it, so i thought i would try and give a step by step brake down of how to do it lol. i wrote it all out the other night went to submit the thread and it wiped cos i got signed out while typing it up (gutted lol) so here it is, hope its clear enough for every one.

Tried it but keeps saying waiting for device and then loops

elinho said:
Tried it but keeps saying waiting for device and then loops
Click to expand...
Click to collapse
Just updated link to super one click download that i used should work now also have usb debugging and unknown sources tick on your phone as i did whilst using super one click.

elinho said:
Tried it but keeps saying waiting for device and then loops
Click to expand...
Click to collapse
my phone got this loop, too
i even tried in fastbat and recoevry mode...
edit:
just try another usb port, not at an hub

Can someone confirm this and create a video tutorail of this?
thanks in advance.

MarkPower said:
Can someone confirm this and create a video tutorail of this?
thanks in advance.
Click to expand...
Click to collapse
Confirmed - make sure to have proper drivers, adb working, put phone in charge only usb mode + usb debugging

This How To works but its useless hboot cant flashed.
For clockwork-recovery is a flashed hboot needed to get Nandroid.
save your time and wait for unrevoked update
PS: find a way to zip a edited orginal rom with changed hboot or find a way to take of the siganture verification this is the way to get full root

INET.exe said:
This How To works but its useless hboot cant flashed.
For clockwork-recovery is a flashed hboot needed to get Nandroid.
save your time and wait for unrevoked update
PS: find a way to zip a edited orginal rom with changed hboot or find a way to take of the siganture verification this is the way to get full root
Click to expand...
Click to collapse
Its not useless if you need to flash back to a 2.1 rom for any reason, which is why i made the guide because i was asked by a few people who did not like the 2.2 update or were experiencing problems on 2.2 that they were not on 2.1...

Will superoneclick allow you to do temproot so you can use root apps
Sent from my GT-P1000 using XDA App

brilldoctor said:
Will superoneclick allow you to do temproot so you can use root apps
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
It gives you temp root so you can downgrade to a lower rom but I couldnt get it to work with titanium or get su permission in terminal app on the phone! have not really tested past the downgrading stage yet will update if I get any more info.

dj_destruction said:
Its not useless if you need to flash back to a 2.1 rom for any reason, which is why i made the guide because i was asked by a few people who did not like the 2.2 update or were experiencing problems on 2.2 that they were not on 2.1...
Click to expand...
Click to collapse
2.2 is more stable and use less of ram and the radio reception is better for most providers.
superoneklick cant give the access for root apps its shell root not file system root

I read somwhere a technique that involved fooling a RUU installer to apply an older rom by replacing some file(s) with older one(s).
I too am stuck with 2.2 and hope to see an easy way to set my phone free
Sent from my weak Wildfire, can't wait to trade in for HD2.

try this>>>>>
open the ruu setup and do not click on and let it open, look in the temp directory of your windows user, according to the extracted files of the setups and replace try something there maybe it will work, I have not tried it yet because most processed rom . zip files stop at the signature and the md5 check.

As if I wan to downgrade my wildfire in order to root . does it downgrade work ? Because u said tat "Will not downgrade the HBOOT" . Newbie here.. dont flame me~ thx..

wait for an other way to root. Downgrading the rom to 2.1 dont give a possible way to root because it will still have the new hboot. The unrevoked team say weeks a go that they are working on it but i guess still without succes. Just wait a read the forums.

I have extracted the 2.2.1 firmware and the rom.zip file within it!
--------------------------------------------------------------------------------
Hi i am unable to post in Dev area, I have managed to extract the .exe from the 2.2.1 to revel all the files including the rom.zip file to which the hboot file is in there.
Do you think we can change the hboot file and fake it to think its 1.01.001 when infact is a hboot file that can be rooted.
I am kind of new to the android platform but not to linux. My device came with 2.2.1 pre installed. This is just a idea weather it will work i don't know.
Could you post this question in the forum that you posted asking the same question with the words that i have managed to extract everything. Thanks
this was a pm sent to me, i am just posting it incase any one can answer

dj_destruction said:
I have extracted the 2.2.1 firmware and the rom.zip file within it!
--------------------------------------------------------------------------------
Hi i am unable to post in Dev area, I have managed to extract the .exe from the 2.2.1 to revel all the files including the rom.zip file to which the hboot file is in there.
Do you think we can change the hboot file and fake it to think its 1.01.001 when infact is a hboot file that can be rooted.
I am kind of new to the android platform but not to linux. My device came with 2.2.1 pre installed. This is just a idea weather it will work i don't know.
Could you post this question in the forum that you posted asking the same question with the words that i have managed to extract everything. Thanks
this was a pm sent to me, i am just posting it incase any one can answer
Click to expand...
Click to collapse
nice idea. I have tried to replace hboot img.zip with a clockworkmod once,but signature failure came up. I will try also your way although i don't know much.hopefully a solution will be released SOON.

beastaki23 said:
nice idea. I have tried to replace hboot img.zip with a clockworkmod once,but signature failure came up. I will try also your way although i don't know much.hopefully a solution will be released SOON.
Click to expand...
Click to collapse
Nice try. And if you test with the img.zip from the older official RRU?
Sent from my HTC Wildfire using XDA App

[HACK] Superboot Method for 2.3.2 (GRH78C)

The Superboot root method boot.img for 2.3.2 is now live thanks to Paul over at Android @ MoDaCo.
"Superboot is a boot.img that when flashed, will root your device the first time you boot (installing su and the superuser APK). No need to flash the system partition, no need to use ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just flash the boot image using the instructions below and you're done!"
Using Superboot
- Download the zip file and extract
- Connect Nexus S via USB cable (with debugging enabled - Settings->Applications->Development->Check "USB Debuggging")
- Boot into bootloader mode - (Turn on while holding 'volume up')
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
*Again, All credit goes to Paul at Android @ MoDaCo*

Cool I'm rooted already but nice to see easier ways of doing it for the noobs. Appreciate the work.
Sent from my Nexus S using Tapatalk

Updated today to 2.3.2 and lost root. Used this and I'm back up and running ! Thank you!!!
Sent from my Nexus S using XDA App

2.3.2
can u do this being rooted or do you have to revert to stock

For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?

qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
i think you would

fastboot
fastboot satus failinvalid command

finally regain root, thank you!!!

qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk

maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?

dakiz71 said:
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
Click to expand...
Click to collapse
Yes. You may have to re-root after updates but your phone will prompt you when OTA updates are available just like normal.
Sent from my Nexus S using Tapatalk

annndrewww said:
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Figures. The answer was staring me in the face the whole time. I think I even remember unlocking it last time I rooted this way. I guess I should just leave it permanently unlocked then so it doesn't keep wiping every time I go to root after an update.

Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!

Am I the only one that did not lose root after the latest 2.3.2 update?

DarkAgent said:
Am I the only one that did not lose root after the latest 2.3.2 update?
Click to expand...
Click to collapse
I used the superboot method for 2.3.1 and also did not lose root in with the 2.3.2 update.
Sent from my Nexus S using Tapatalk

You shouldn't.
P

Windows 7
For me install-superboot-windows is waiting for device long without success :\
No matter ... i had to force my pc recognize Nexus once more

Thank you. This seems simple. I'm stuck with my XP recognizing my Nexus S USB Driver after installing SDK and Google USB Driver even after trying to "update" driver under Device Manager and redirect the directory to Google USB Driver? I'm very confused.

philbs17 said:
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Click to expand...
Click to collapse
Ok buddy heres what you need to do, on the MAC, this is how i do it.:
DL the .zip in the OP.
Extract it on you're desktop
Rename the Extracted file to Nexus (thats what I name it)
youre device needs to have the bootlader Unlocked.
Open Terminal and type
cd desktop
cd nexus
chmod +x install-superboot-mac.sh (press enter)
./install-superboot-mac.sh (press enter)
then you're done. hope this helps.
Let me know.

Simply amazing! Thanks for the breakdown.

cwm touch

So iam running bo 2.0.1 with cwm 5.5.0.4. Tried to update to cwm 6 touch by replacing cwm image in pretty much all the aio's.. it'll either say it pushed and still reboot into old cwm or I'll get permission denied on /data/local/temp/sh and mmcblk14 even after giving them all read write and execute permission. Can someone help me get this on my revo? Maybe a guide to do it with adb? It would be much appreciated..... sorry if this is posted in wrong section... I wasn't sure where it would be seen by the dev 's who can help

All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!

slimzim said:
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
Click to expand...
Click to collapse
The same exact way I've done it. Numerous times with no success. It said it pushed but reboot back into 5.5.0.4

Anyone else have this problem? How can I achieve this with adb or file explorer... the method posted just isn't pushing the image...

To do it from within the phone... (Insert the usual disclaimers here about messing your phone up here. It's all you from here on out)
You can open up the .bat batch file of one of the rooting tools that have CWM install scripting.
Copy the commands they perform in preparation for the procedure. Remove adb shell and push from the commands as you will be doing this from inside the phone, not via adb. I think you might have to remove some open/close quotation marks too, unnecessary from the terminal prompt.
Rename the new CWM file to match the command prompt change the command to match the new CWM filename.
Move that file to the expected location (/local/tmp if I recall correctly).
Use app Terminal Emulator to create a terminal windows and type su and Press enter. That will get superuser access.
Then, issue the commands you took note of from the batch file.
Reboot to Recovery to test if successful.
I used this basic process to get CWM on after rooting stock ZV9 a few weeks ago. Combing through a couple different batch scripts, I wanted to make sure I wasn't going to bork my phone. The adb remount command doesn't seem to work after rooting for some reason. That seems to be the cause of adb failure to update CWM.
If you get into trouble, I can't help you much there as I'm not that advanced. Good luck.
Anyone else with tips please chime in and help the chap :beer:
Sent from my VS910 4G using Tapatalk 2

Ill try it out. Thanks for the advice

Didnt work.. iam hoping that resetting back to stock and using that image from the start will work

Weird. I was expecting to hear good news since that's how I got CWM onto my phone. Good job trying!
Sent from my Transformer Prime TF201 using Tapatalk 2

Recovery cannot mount any storage/data!!!

Hi, I am having problem, rooting my HTC One. I have done boostloader unlocking everal times with different devices, but HTC One is giving me some weird problems...
To start off with, the recovery could not be flashed at one go. I had to command flash recovery ' ' three times to get it installed. Anyhow, I did manage to flash it, but now recovery cannot mount any storage /data, /sdcard as well as /cache.(Ii.e. I cannot see any file even if I click install from SD card.) Also, tried rooting via clicking reboot, it says to root device and I am saying to it for more than five times, but it cannot be rooted. And now i am stuck .... -_-
Any suggestion/help please?

uggies said:
Hi, I am having problem, rooting my HTC One. I have done boostloader unlocking everal times with different devices, but HTC One is giving me some weird problems...
To start off with, the recovery could not be flashed at one go. I had to command flash recovery ' ' three times to get it installed. Anyhow, I did manage to flash it, but now recovery cannot mount any storage /data, /sdcard as well as /cache.(Ii.e. I cannot see any file even if I click install from SD card.) Also, tried rooting via clicking reboot, it says to root device and I am saying to it for more than five times, but it cannot be rooted. And now i am stuck .... -_-
Any suggestion/help please?
Click to expand...
Click to collapse
Use TWRP and sideload a ROM

Rex2369 said:
Use TWRP and sideload a ROM
Click to expand...
Click to collapse
Tried, but even sideload says failure...

Are you sure you have the proper drivers installed? You need HTC Sync Manager if you're on Windows in order for the proper drivers to be loaded. And um, do you have the mini-SDK or full SDK folders?

TarekElsakka said:
Are you sure you have the proper drivers installed? You need HTC Sync Manager if you're on Windows in order for the proper drivers to be loaded. And um, do you have the mini-SDK or full SDK folders?
Click to expand...
Click to collapse
Yes, I am sure.. If that was the problem than I could not unlock bootloader. I dont think that is the problem here
I have sdk tool downloaded from xda. i think it was called all-in-one rooting/unlocking or something

Are you sure you are navigating to the correct SDK folder which has the ROM you want to download inside it? I just tried sideloading a ROM using my Mac but for some reason it actually did not work. I used Windows, however, with full Android-SDK and Java-JDK installed and it worked brilliantly, so I am assuming it is because I did not have the platform-tools folder on Mac but rather the mini-SDK which doesn't seem to work well for sideloading ROMs using ADB.

You need to let the device boot properly at least once for the partitions to be set up properly before you go about rooting and stuff.
Sent from my SGH-M919 using xda app-developers app

TarekElsakka said:
Are you sure you are navigating to the correct SDK folder which has the ROM you want to download inside it? I just tried sideloading a ROM using my Mac but for some reason it actually did not work. I used Windows, however, with full Android-SDK and Java-JDK installed and it worked brilliantly, so I am assuming it is because I did not have the platform-tools folder on Mac but rather the mini-SDK which doesn't seem to work well for sideloading ROMs using ADB.
Click to expand...
Click to collapse
Thanks for your advice, I try it with new sdk tool.
Dark Nightmare said:
You need to let the device boot properly at least once for the partitions to be set up properly before you go about rooting and stuff.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
It did boot up normally, and everything seems just fine including storage its just recovery that is causing problem