[Q] s-off still no perm root. Clock work problems - G2 and Desire Z Q&A, Help & Troubleshooting

I'm having serious problems trying to root this phone. To start I wanted to use the rage method but I couldn't get HTC sync to work with my phone and windows 7 and adb to work. So I then used black prince method off of you tube using visionary r14. I did everything he said. When I press volume down and power I see it says s-off but when I type SU into the terminal it says permissions denied. I even see the superuser app on my phone. I then did some searching and people who have the same problem and they said to do temp root then go to the terminal and type /data/local/tmp/root then sync it again. Still no luck. Any ideas?
My next concern is I have been trying to boot into clockwork recovery with no luck. I have re flashed and flashed the current version's of recovery to many times to remember and did fix permissions. I can not boot into recovery. Any ideas?

What version of ROM is it that you are trying to root ? The latest 1.72 Desire Z ROM cannot currently be rooted.
You need S-OFF to flash a custom recovery. Are you saying you are trying to boot into stock recovery ? If so, when you see the screen with the red triangle/exclamation mark, hold Volume Up and press Power, and it should go into stock recovery.

Your phone isn't fully s off. You need to delete visonary completely off your phone. (Probably have to wipe). Then download pdanet app. And when you plug usb in your computer that should fix the driver problem. Then run rage. Don't do the lock in root command, then follow gfree tutorial, then try lock in root command. If it gives you an error, let me know which error and we can work around it. Pm me when you run into trouble.
Fired from my 7.62mm bullet hose to your face using plunging fire.

Related

[Q SOLVED] My DHD is SHIP S-OFF, supposedly rooted, but cant get Clockwork mod on

Hi peeps
I got my DHD yesterday in Shanghai. It' nice but im trying to flash LeeDRoid onto the phone. The DHD has come from Germany originally and it seems the phone shop has flashed a Chinese custom rom on it already.
I checked and the phone is SHIP S-OFF and rooted. Weird thing is my superuser app wont flag any root permission requests from rom manager or apps like titanium backup. The only thing it has allowed so far is Visionary - and allows that program to root and unroot. Nothing else works...su in terminal - nada, no joy - permission denied.
So as it stands I cant get clockwork recovery on through the phone. So i try to push it through fastboot and i get this:
writing 'recovery'...FAILED <remote: not allowed>
I really have no idea of how to get CWM on the phone - can anyone give me pointers?
handle it as S-ON
permroot with visionary
S-off
install ROM manager from the market
install cw recovery
not sure how this helps as the phone is already S-OFF?
problems is i permroot - i have no access to SU in the terminal - superuser doesnt flag my request
without SU how to i got through the process of taking the phone to S-OFF?
The same thing happened to me, but solved now, what i did were:
flash a stock rom through RUU,
run the root tool from Paul again, but the recovery couldn't be flashed by the ROMManager still, as it's hboot issue, you have to flash recovery through ADB,
the following thread could be helpful:
http://bbs.gfan.com/android-333390-1-1.html
thanks chinesedavid, your suggestions were really helpful
ive now managed to flash LeeDroid on no probs
one thing i didnt have to do was push recovery via adb...i actually managed to flash CWM from rom manager
one issue i have is titanium backup though - whenever i try to remove a system app, my system will reboot but not start up - i end up with a screen of a little droid with a triangular sign with an exclaimation mark in the middle. then it gets stuck and i have to do a batt pull
is this a bug with titanium backup on the DHD or is it my phone that's not allowing the removal
if working properly the phone should boot twice and remove the system app...

[Q] Error switching to Cyanogen

I have a G2. I decided to root it using the guides on Lifehacker and Cyanogens wiki. I got a temproot using Visionary, and permaroot using terminal. Everything went swimmingly. I only used download links that I found on Lifehacker and on Cyanogen's site (the same places I got the guides to root my phone) I attempted to root my phone and put CM7 on it. I backed up everything with Titanium Backup. I downloaded Rom Manager, flashed ClockworkMod Recovery to get the latest version, downloaded CM7 through Rom Manager, and attempted to install it as well as backup existing ROM and wiping data and cache. My G2 returns to the HTC startup screen and just stops.
I tried to do a factory reset, it just stops at the same area. I tried doing a factory reset from the startup options (power and down volume), nada. I tried reflashing ClockworkMod Recovery, zilch. I restored my backup from Titanium, nothing.
The phone works, I'm able to do everything I would normally do on it, but I just can't get this to work and I don't know where I went wrong or how to fix it. I have experience with UNIX based systems so I know how to work a command line to an extent and I know that part went off without a problem. I just can't figure out what's going on with it.
can you connect to your phone using adb? if you can access the shell you might be able to figure out why it's hanging.
ADB
I'm not sure I've tried ADB, any tips?
Are you talking about hooking it up to my computer as an alternative method to flash it? I had a bit of trouble with that because my computer is currently down (I just moved and don't have the room to set it up yet). I think I need a copy of the original ROM for my phone as well, if I get that I believe I can restart the whole process and do it right this time. Any ideas where to get it?
yes hook it up to the PC, even if it's in a bootloop you might be able to access the phone's system to do repairs using adb to enter the shell.
check this thread: http://forum.xda-developers.com/showthread.php?t=865685
it also explains how to use it
http://developer.android.com/guide/developing/tools/adb.html
this one got all the adb commands.
I'm not sure about the log command, but there's a way to call on the system log to see where it fails.
it's not recommended to flash an original image again, you can try to restore the backup of the original ROM (nandroid backup) if you made one...
hope this can help you.
Sounds like there is a problem with your recovery, try to manually flash recovery using flash_image instead of ROM Manager.
Use this thread for a guide: http://forum.xda-developers.com/showthread.php?t=902493
You can get the latest version of CWM (currently 3.0.2.4) here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html just scroll down to the link that says "HTC G2"
After you flash try to manually go into recovery by shutting down the phone and powering it up while holding the volume button down, this should bring you into the bootloader menu and allow you to launch recovery.
Thanks!
I'll give that a try as soon as I can, thanks for the assistance!

I'm in a bit of a pickle (GB, S-ON, ADB is broken)

First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
My HBoot is version 1.07.0000 (I was 0.92.0000, but now I flashed cmlusco's newer HTC rom, so it changed)
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot, and I got my bootloader unlocked!
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Thanks for the help you guys are amazing!
UPDATE: It's FIXED!!!! Here's the short version of how (in case it happens to anyone else)
To start, my phone A: Would not boot B: Would not read the SD card, or EMMC, EVEN in recovery C: all USB was broken including ADB (but fastboot worked) and D: I managed to lose root by flashing like mad in hopes of fixing AB and C
Step 1: I flashed cmlusco's ROM that he suggested which got my hboot up to date etc...
Step 2: I went to http://htcdev.com/bootloader/ and unlocked my bootloader (BUT I skipped straight to step 8 (the fastboot part, since everything before that was a waste of my time since my USB/ADB was hosed))
Step 3: I flashed this recovery image and ran "fastboot flash recovery recovery.img"
Step 4: I downloaded superuser and loaded it through recovery, now that my SD card worked
Step 5: I then was able to do the following in order to fix the USB/ADB problem:
using this file and this file and running them in an android emulator app I downloaded from google play (since my USB was broken)
Terminal emulator & ADB commands:
Code:
su
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd-eng.img > /data/mtd-eng.img
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd-eng.img
reboot
(credits for this to this thread)
Step 6: I was now fixed, so I just wiped my phone and flashed Albinoman's Jellybean ROM because it rocks!
Thanks to tiny4579 and cmlusco for both of your help!
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
meadowsjared said:
First of all, I gotta give props to Albinoman for getting the Incredible to where he has (Jellybean, on the Incredible!... wow!)
http://forum.xda-developers.com/showthread.php?t=1778190
I've been following Albinoman's progress and while I was trying to troubleshoot the "low space notification" we're all too familiar with, I made a HUGE mistake.... I was using Albinoman's Beta 2, which worked great, but I tried restoring a nandroid backup and it failed, due to a corrupt SD card. Then, I tried restoring to another backup, which also failed. I then set out to run a scandisk on the SD card, so I shut off my phone thinking I could just boot back into recovery no problem right?!? WRONG!
After fixing the SD card, I was unable to even boot into recovery, I was getting the scary 5 vibrates of death, and I found this thread, which was half-helpful:
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/showthread.php?t=1110865
It was able to get my SD card working (previously it didn't at all), but I still cannot boot without having a USB cable plugged in (otherwise I get the 5 vibrates and a blank screen).
The thread suggested using z4root to gain temporary root but when I try that, it just sits there for a very long time and times out.
Here's where my biggest problems come in...
I'm currently running Gingerbread 2.3.4, S-ON, and ADB is BROKEN on my phone
What I currently have to work with (what works):
Wifi, SD Card (new one of course), 3G, and I'm able to boot
I cannot find any way to root my phone based on my current situation.
I have found plenty of ways to root (I'm used unrevoked plenty of times but it wont help me now because ADB wont work with my phone because it's broken, but I can't fix ADB, because I can't get root, it's really a sad situation)
I've tried HTC's RUU official root method, other RUU's, and Unrevoked, but they all don't work because my ADB is messed up
Also, I don't know if this helps, I can use fastboot, and I was able to flash an image using fastboot commands, but it's been awhile since I've tried that, and I don't know of anything I can flash via fastboot to help my situation.
My main goal is, I just need to get rooted again so that I can re-flash Albinoman's sweet Beta 3 ROM which I've been unable to even try
Any help anybody could offer me would be GREAT! Thanks XDA, you guys are amazing!
Click to expand...
Click to collapse
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
1st of all, thanks for getting back to me so quickly Tiny, you're amazing, and I appreciate all the work you've done with the Dinc, thanks for being so active!
1. No, mass storage doesn't work (I assume you mean plugging in the phone and having it mount the SD card as a drive on the computer)
However, I am able to now use both my SD card from within Gingerbread, and the recovery, but only after doing the "fastboot oem enableqxdm 0" trick
2. I haven't tried uninstalling and reinstalling the ADB drivers, but only because.... I'm a developer, and sometimes I develop on my home computer, and sometimes I develop at work, and they both exhibit the same behavior, so I don't think it can be that both computers, just happened to get messed up at the exact same time, right when my phone got hosed?
Also, I've used ADB plenty in the past, on both computers, so I'm certain they're set up right, just between having two computers to work with, AND the extensive use I've made of ADB in the past (I'm the office Root-er, I've rooted most of my co-worker's phone for them, so I've had quite a bit of experience (and should have known better than to turn off my phone when I did which got me in this pickle ))
Just to be clear though, basic USB communication works, but only in HBOOT, NOT from Gingerbread, actually, having the phone plugged into USB (whether or not USB debugging is turned on on the phone), WILL lock up my computer until I unplug it, and as soon as I unplug, my computer snaps back to normal So I think somehow something in the phone got hosed so the ADB is broken, however, I can't fix it because I can't get my root back because I'm stuck in the horrible stock gingerbread (no offense to anyone that likes it )
Also, yes, I've tried a ton of times to flash a superuser zip to root and it says it's not allowed/bad signature or whatever, because it's still S-ON
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
@cmlusco
I didn't even know you could use RUU's through hboot, I'll try that, as well as using the HTC unlocker RUU with hboot.
I'd already tried those things normally, but with by USB being hosed, it didn't help much. :-\
I'll post back when I've given them a try
cmlusco said:
What hboot version are you on? Have you tried an ruu thru hboot?
I would try an ruu thru hboot first. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
If that dosent let you boot, use the htcdev site to unlock your bootloader. And then fastboot flash cwm recovery, and then superuser thru cwm. Then you will be rooted and can try to wipe everything and flash a rom.
Click to expand...
Click to collapse
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
meadowsjared said:
I'm on HBoot 0.92.0000
and it seems to only allow me to flash newer, or the same version as what I've got (because I've tried downgrading)
I just tried the RUU from HTC to root my phone.
I ran the RUU, put the phone in hboot, and it sat and said "verifying phone information" or something like that and said "error 170, usb connection error"
I also put the phone in "fastboot" and tried again, it didn't seem to make a difference.
Now regarding flashing an RUU through hboot, how would I go about doing that? I'm assuming you're talking about throwing the PB31IMG.zip on my SD and booting into Hboot. Now that DOES work however, I'm still S-ON, so unless it's a factory image, it ain't gonna like it
That is, unless there's some kind of fastboot voodoo that can be done to get something on there to exploit it and get my back my root I once had and loved!
Click to expand...
Click to collapse
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
cmlusco said:
That PB31IMG.zip i posted is 4.08.605.15, the latest android version for our phone. It is official and signed by htc, so it should flash even if your s-on. Just place it on your sd in no folders and hboot should find it.
Click to expand...
Click to collapse
Yes, you're right, I was able to flash that image using hboot, but sadly... the adb is STILL broken and doing all the same things it was before (it doesn't work, and when I plug it into my computer, it freaks out my computer and the computer freezes until I unplug the phone, then everything is fine again)
It seems that all these images write everything to the phone... BUT what I need. I've found some things that "should" fix my problem, but they are all unsigned, and therefore they require root. Is there a chance that now with this newest RUU you gave me "z4root" will work cmlusco? (the reason I ask is, I'm hoping that an app that roots the phone without the computer will work, since every time I plug into a computer, it doesn't work, and just freaks out the computer)
Also, regarding the official HTC way to root, I tried running their "PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe" file, however, that didn't work in the slightest (because it uses adb commands to talk to the phone). Is it possible that there's a way to extract the PB31IMG.zip file from that exe file and therefore I would be able to flash that using hboot, and the phone would like it because it's signed by HTC (I'm assuming)?
By the way, ever since I flashed that newer PB31IMG.zip ROM, now when I go into hboot, at the top it says "*** LOCKED ***", and it never said that before, I don't know if that matters at all? :-\
Also, if it helps any, here's what the update looked like....
*** LOCKED ***
INCREDIBLE XC SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.12.20
Apr 24 2012,22:58:40
HBOOT
Parsing... [SD ZIP]
[1] RADIO_V2 - OK
[2] BOOT - OK
[3] RECOVERY - OK
[4] SYSTEM - OK
[5] SPLASH1 - OK
Update Complete...
Then, after running the update, it asked me if I wanted to reboot, it showed the picture of the phone with the arrows in a circle around it, then when it wen to reboot, it did the usual (for me lately), and gave me the 5-vibrates of death and a black screen, the only way to get out of it is to do a battery pull. Then, after doing that, if I just plug in the cable, I can boot into the new rom just fine, but if the cable isn't plugged in, I just get the 5 vibrates of death, like this guy....
[HOW-TO] Fix 5 vibrate and black screen
http://forum.xda-developers.com/show....php?t=1110865
But sadly, in order to completely fix myself, I need root, and I can't seem to even get temporary root? :-\
I'm hoping maybe something there might help y'all to help me? :-\
tiny4579 said:
Two quick questions:
1. Does USB mass storage work? (do your sdcard and emmc get recognized as drive letters when it boots) - if it doesn't there MAY be a problem but question 2's suggestion may fix it.
2. Did you try uninstalling and reinstalling the adb drivers?
This is just off the top of my head. Oh, now I see that fastboot works so basic USB communication works so it may be a driver issue.
Oh, since fastboot works you should be able to flash CWM recovery and a superuser zip to root unless it says not allowed. But if you can flash and boot recovery at that point no point on rooting, just flash a rooted ROM like jellybean beta3.
Click to expand...
Click to collapse
@tiny4579
To be more clear, the basic USB communication doesn't work, the only way I can get anything that uses USB to work, is by booting into fastboot, and I have been able to do fastboot commands (like "fastboot oem enableqxdm 0"). So it seems that fastboot's USB works just fine (I've tested this on multiple computers), but anything after that, like trying to use the USB from the operating system, is totally broken. So I'm guessing that internally, the phone's drivers for USB are separate for hboot, and therefore still work, however, the phone's USB drivers for Gingerbread, are completely broken, even though I've been able to flash 2 different versions of signed gingerbread from HTC, they still don't seem to fix my USB problem even though it's writing the entire system all over again. Is it possible that there's a signed HTC zip that will fix my USB, that would fix me... the only question is.... does a signed HTC zip exist that will fix my USB??? :-\
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
meadowsjared said:
Ok, I've got great news, I was able to finally unlock my bootloader! so now when I go into HBOOT, it says at the top "UNLOCKED", however, it still says S-ON, and I still don't have root, but I think we're getting there!
So now that my bootloader is unlocked, I'm assuming I should be able to either load a custom recovery (like clockworkmod), however, I still can't use ADB to do anything so things like unrevoked wont work for me sadly
Do you guys have any advice on what I can now do that my bootloader is unlocked? (I'm a little unclear about what the whole bootloader thing does for me). I think I understand rooting, at least enough, and I thought I understood the bootloader, and the unlocking. But now that my bootloader is unlocked, it still wont let me load anything like CM7.1, or clockworkmod (I tried both of those by going into recovery and trying to flash the update.zip).
Either way, I'm very encouraged by the fact that my bootloader is unlocked, I'm assuming it should help me to acheive my goal of rooting and eventually gettting Albioman's Jellybean on there?
Click to expand...
Click to collapse
Now you need to fastboot flash cwm. Download this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it on your pc in the same folder as the fastboot.exe file.
Open a cmd prompt on your pc to where fastboot.exe and recovery.img are. Type the folowing:
Code:
fastboot flash recovery recovery.img
If you get no errors, go to the maim hboot menu and select recovery. You should now be in cwm recovery.
Download superuser http://dinc.does-it.net/Superuser/SuperUser_3.0.7.zip, and place it on your sdcard by going to mounts and storrage and selecting mount usb storrage. If it freezes up the phone or the pc, you will need to take the sd out and use a card reader to put it on the sd with a pc.
Then flash it thru recovery like you would a rom. Now you will be rooted. Then flash a rom of your choosing and hope it boots.
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
Yeah i guess it is pointless to flash su, then wipe it, then flash a rooted rom.
Thank you both of you, you were a HUGE HELP!!!!! I'm FIIIIIIXED!!!!!!!!!!!!!!
I'm going to update the original post to detail how I got fixed (the short version is, I just did what cmlusco said, and as soon as I had root, I followed this and it worked!!!!)
tiny4579 said:
Might as well load the ROM when you load superuser. But flashing superuser is silly if you're going to flash a ROM with root right after it but it's probably still a good zip to keep on your sdcard.
Click to expand...
Click to collapse
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
meadowsjared said:
I wound up loading superuser like cmlusco suggested, only because I wanted to have everything fixed and perfect before loading Albinoman's new ROM, just in case there were issues, that way I'd know that it was the ROM or my phone, especially since my SD Card freaked out on me and that's how I got into this mess
....But, you are right, the only problem is, I'm super paranoid, and I like to be super-thorough
Click to expand...
Click to collapse
Glad its working for you.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Root r800at on .285 and locked bootloader?

I've been trying this for awhile and I don't know if it's just impossible or i'm really dumb.
My cousin had been complaining of his phone always saying his internal storage is full from the games that , so I said I'll just root it, install Titanium Backup and remove them from there, well apparently it's a lot easier said than done.
He's running 2.3.3 and has the .285 build. I've tried using SuperOneClick but everytime I run it, it either does nothing or the program freezes at step 7. I then tried Doomlord's easy rooting toolkit and it just goes through all the steps normally and reboots but nothing actually happens. I noticed that on some of the steps it will say something like "rm failed for /data/local/tmp permission denied" I thought it was my drivers at first but I made sure all the appropriate drivers were installed. I tried to use Flashtool as well but with no success. I then saw somewhere that you have to be on .270 build for those programs to work, but to flash that build you have to put it into "flash mode" which I tried holding both the search key and the back key while plugging in the usb cable but either times it did not work. I'm guessing it won't boot into flash mode because it's an at&t model and has a locked bootloader. Sorry for the wall of text it seems but is there anyway to get this freaking phone rooted?

Rooting 910V - Non Dev Model

Instead of flooding the bootloader thread, I humbly ask for anyone's help in getting my N4 rooted so that I can unlock the bootloader.
1. I am able to use Kingroot to obtain temp root
2A. I open Root Checker and N4 reboots
OR
2B. Root checker OK then I get to ADB and enter a push command, the N4 reboots
This is where I am stuck.
Bootloader
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66371097&postcount=237
I had the same bootloop problem and following those directions fixed it for me. I had to use Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip as my kernel. Later versions didn't work (wrong phone version?).
coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
Why don't you guys flash a ROM that is rooted instead of flashing SU?
Edit:
But if whatever you guys are doing works eventually, keep doing that.
thanks for everyone's help - I finally got DEV mode to stick!

Categories

Resources