Hey guys, I've only rooted a droid razr before and am trying to root my incredible 4g right now but whenever it get to the step below I get the following response: 'adb' is not a valid internal or external command, operable program or batch file. Any ideas? Any help would be appreciated as I am not very experienced at this kind of stuff but love the benefits of being rooted. Also, i did try and search the thread but couldn't find a solution. Thanks in advance. This is the step I'm stuck on:
Close cmd and start a new one then type
Code:
adb pull /sdcard/mmcblk0p4
rrupp said:
Hey guys, I've only rooted a droid razr before and am trying to root my incredible 4g right now but whenever it get to the step below I get the following response: 'adb' is not a valid internal or external command, operable program or batch file. Any ideas? Any help would be appreciated as I am not very experienced at this kind of stuff but love the benefits of being rooted. Thanks in advance. This is the step I'm stuck on:
Close cmd and start a new one then type
Code:
adb pull /sdcard/mmcblk0p4
Click to expand...
Click to collapse
Make sure adb is in your path, or make sure you are in the adb directory when you execute the command.
Jafmf95 said:
Make sure adb is in your path, or make sure you are in the adb directory when you execute the command.
Click to expand...
Click to collapse
How would I do that?
this webpage will help you get setup:
http://wiki.cyanogenmod.org/wiki/Howto:_Install_the_Android_SDK#Windows
it's the instructions I used to install the android SDK and get adb and fastboot working
down towards the bottom there are instructions for installing on Windows (im assuming that's what you have anyway, other directions are on there as well)
Much thanks to both of you! I followed the wikipedia page and am now successfully rooted.
rrupp,
What root method are you using? Just curious...
Fireballas root method
Sent from my ADR6410LVW using xda app-developers app
rrupp said:
Fireballas root method
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Download current zip attached since the problem is you dont have android sdk installed or your not running it from there
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
binaryhat said:
rrupp,
What root method are you using? Just curious...
Click to expand...
Click to collapse
There's only one root method isn't there?
andybones said:
There's only one root method isn't there?
Click to expand...
Click to collapse
Well theres the script and the guide which are very different since the manual is for advanced
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Big Problems
jose51197 said:
Well theres the script and the guide which are very different since the manual is for advanced
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Hello, I finally unlocked and rooted last night, using the automated script. That part went relatively smoothly. I am greatly appreciative of all the efforts to make this available, because i know it wasn't easy. I feel like I'm standing on the shoulders of giants whenever I even attempt something like this, and I'm very grateful. A little background: Over the years I've managed to root every device in my house: a Droid Eris, a Droid Incredible, a Droid 2, a Droid Incredible 2, and a Le Pan tablet. So far, so good, but many of those were pretty simple, one-click, etc. I knew there were complications with the Incredible 4G and I bided my time until it seemed foolproof enough that even I could do it. However, I'm rather worried that I really screwed something up this time:
1) After unlocking and flashing Viper 2.0, I noticed right away that some of the functionalities were missing. Basically everything crashed: the browser, the dialer, messaging app, etc. I was somewhat prepared for this in reading the threads and tried going back into the automated script and choosing option 3 to revert the CID. However, it keeps starting me off at step #1, even though I've chosen #3. Is that correct? How would I go through the whole process again and still get to step #3? Maybe it's because...
2) During the initial installation, being unfamiliar with the TWRP recovery, I think I screwed up by doing a System Wipe (along with the more familiar wipes I would normally do). Looking back at it, is that why basically nothing works? Ex: When I open up the messaging app, it says the app is not even installed. Did I accidentally delete crucial elements? Can I get them back?
3) To really compound things, I forgot to make a backup before I did all this. I realize this was completely stupid, especially now I fear that I have nothing to go back to in terms of a stock image (oops!!)
So, now I'm really stuck. I can follow basic directions, but definitely don't have the knowledge or skill to get creative at this point. Can anyone help?
Thanks
dodgerinNH said:
Hello, I finally unlocked and rooted last night, using the automated script. That part went relatively smoothly. I am greatly appreciative of all the efforts to make this available, because i know it wasn't easy. I feel like I'm standing on the shoulders of giants whenever I even attempt something like this, and I'm very grateful. A little background: Over the years I've managed to root every device in my house: a Droid Eris, a Droid Incredible, a Droid 2, a Droid Incredible 2, and a Le Pan tablet. So far, so good, but many of those were pretty simple, one-click, etc. I knew there were complications with the Incredible 4G and I bided my time until it seemed foolproof enough that even I could do it. However, I'm rather worried that I really screwed something up this time:
1) After unlocking and flashing Viper 2.0, I noticed right away that some of the functionalities were missing. Basically everything crashed: the browser, the dialer, messaging app, etc. I was somewhat prepared for this in reading the threads and tried going back into the automated script and choosing option 3 to revert the CID. However, it keeps starting me off at step #1, even though I've chosen #3. Is that correct? How would I go through the whole process again and still get to step #3? Maybe it's because...
2) During the initial installation, being unfamiliar with the TWRP recovery, I think I screwed up by doing a System Wipe (along with the more familiar wipes I would normally do). Looking back at it, is that why basically nothing works? Ex: When I open up the messaging app, it says the app is not even installed. Did I accidentally delete crucial elements? Can I get them back?
3) To really compound things, I forgot to make a backup before I did all this. I realize this was completely stupid, especially now I fear that I have nothing to go back to in terms of a stock image (oops!!)
Uide
So, now I'm really stuck. I can follow basic directions, but definitely don't have the knowledge or skill to get creative at this point. Can anyone help?
Thanks
Click to expand...
Click to collapse
Try downloading viper again and reflashing and if you want to reverse cid follow the manual guide on bugs section
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
thanks for the response, re-downloaded and am re-flashing now. If that doesn't work, I'm still not clear on how to revert CID using the automated tool (option 3). Do I start from scratch and go through the whole process again? (The first time I tried it I selected option 3, but it started me back at #1, and I doubt I would want to go that route again?
Also, how would I reacquire a stock image, given that I shouldn't have done a system wipe without backing up in recovery first? Is that possible?
dodgerinNH said:
thanks for the response, re-downloaded and am re-flashing now. If that doesn't work, I'm still not clear on how to revert CID using the automated tool (option 3). Do I start from scratch and go through the whole process again? (The first time I tried it I selected option 3, but it started me back at #1, and I doubt I would want to go that route again?
Also, how would I reacquire a stock image, given that I shouldn't have done a system wipe without backing up in recovery first? Is that possible?
Click to expand...
Click to collapse
If you want to return to stock flash a ruu and ill take a look at newer script sijce on this one i didnt collaborate just on the first three but now will modify it to include new options
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
jose51197 said:
If you want to return to stock flash a ruu and ill take a look at newer script sijce on this one i didnt collaborate just on the first three but now will modify it to include new options
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
thanks I'll give it a shot to try to get back to stock in the meantime. I located the files. There are 4 of them. I assume I need them all?
dodgerinNH said:
thanks I'll give it a shot to try to get back to stock in the meantime. I located the files. There are 4 of them. I assume I need them all?
Click to expand...
Click to collapse
Which files are you talking about? Btw i think more files more error less
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
jose51197 said:
Which files are you talking about? Btw i think more files more error less
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
andybones posted 4 files:
stock boot; stock hboot; stock recovery; stock radio
Then I looked a little further and found the full RUU (575 MB), so not sure which route I should go?
I did notice other people getting error messages and were told they needed to re-lock in order to flash the RUU. Is that correct? Keep in mind, I'm just trying to get a working phone again until I can regroup and figure out how to revert CID from the automated script. I am unlocked and rooted.
thanks,
dodgerinNH said:
andybones posted 4 files:
stock boot; stock hboot; stock recovery; stock radio
Then I looked a little further and found the full RUU (575 MB), so not sure which route I should go?
I did notice other people getting error messages and were told they needed to re-lock in order to flash the RUU. Is that correct? Keep in mind, I'm just trying to get a working phone again until I can regroup and figure out how to revert CID from the automated script. I am unlocked and rooted.
thanks,
Click to expand...
Click to collapse
in order to flash the RUU in bootloader you need to first lock it, this goes even for my s-off phone, but once you are unlocked you are good to go, so even if you deleted your Unlock_code.bin you can always re-run the process to get it back.
the codes to lock and unlock are
lock
fastboot oem lock
unlock
fastboot flash unlocktoken Unlock_code.bin
andybones said:
in order to flash the RUU in bootloader you need to first lock it, this goes even for my s-off phone, but once you are unlocked you are good to go, so even if you deleted your Unlock_code.bin you can always re-run the process to get it back.
the codes to lock and unlock are
lock
fastboot oem lock
unlock
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Thanks, you guys have been great. I'll try everything you've suggested. Sorry to continue taking up so much of your time. I knew when I woke up today it would be a pretty unproductive Sunday, but I have to get my phone working again, particularly since I need it for work. After that, I really do want to have a successful install of Viper 2.0 because it looks pretty sweet. At least this time I'll be smart enough to make a backup before I plunge ahead!! But one more question for the time being:
Can I flash the RUU from the TWRP recovery, or does re-locking eliminate my ability to go that route?
Also, do I need to rename the RUU before flashing, regardless of whether I use the bootloader or TWRP recovery (if possible)?
dodgerinNH said:
Thanks, you guys have been great. I'll try everything you've suggested. Sorry to continue taking up so much of your time. I knew when I woke up today it would be a pretty unproductive Sunday, but I have to get my phone working again, particularly since I need it for work. After that, I really do want to have a successful install of Viper 2.0 because it looks pretty sweet. At least this time I'll be smart enough to make a backup before I plunge ahead!! But one more question for the time being:
Can I flash the RUU from the TWRP recovery, or does re-locking eliminate my ability to go that route?
Click to expand...
Click to collapse
Twrp doesntaffect anything but just flash it from exe or bootloader
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Related
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Daaaavinnn said:
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Click to expand...
Click to collapse
Were you able to reflash a kernel or the stock ROM?
I couldn't flash ANYTHING. -_-
Sent from my GT-I9100 using XDA App
I made the mistake of flashing one of the stock roms derived from RUU which was a big mistake since it flashed the hboot I no longer have revolutionary which lead me to not being able to fastboit anything. I can get the adb to.connect to the device while in recovery with system mounted. but that's pretty much it. If i install a custom ROM when I reboot revolutionary will see device but not ling enough to.root and install the drivers. Just setup your pc to use fastboot otherwise you might do the same thing I did. After two days of searching trying different things my fix was going and buying a new phone last night.
Sent from my PG86100 using XDA App
mteezey said:
I made the mistake of flashing one of the stock roms derived from RUU which was a big mistake since it flashed the hboot I no longer have revolutionary which lead me to not being able to fastboit anything. I can get the adb to.connect to the device while in recovery with system mounted. but that's pretty much it. If i install a custom ROM when I reboot revolutionary will see device but not ling enough to.root and install the drivers. Just setup your pc to use fastboot otherwise you might do the same thing I did. After two days of searching trying different things my fix was going and buying a new phone last night.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If you relocked your phone "fastboot oem lock" and installed a stock RUU, this should have brought your phone back to stock. This wasn't the case?
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
Daaaavinnn said:
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Click to expand...
Click to collapse
When you root your phone, never accept updates unless you unroot your phone and go back to stock. Are you on hboot 1.5? I would suggest finding a rom that you want to flash (I recommend Myn's warmtwopoint3 RLS1 Deodex). To do this go into fastboot USB and load the custom recovery in the folder you downloaded to root your phone "fastboot boot recovery.img" (recovery.img should be replaced with the name of the CWM***.img file in that folder. This will give you full access to write the kernal and install the rom). Your issue is only likely kernal related so unless you do what I just mentioned, you wont have access to write a new kernal.
JayDaKissEP said:
Your issue is only likely kernal related so unless you do what I just mentioned, you wont have access to write a new kernal.
Click to expand...
Click to collapse
Agreed. Sounds like a kernel issue to me.
JayDaKissEP said:
If you relocked your phone "fastboot oem lock" and installed a stock RUU, this should have brought your phone back to stock. This wasn't the case?
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
When you root your phone, never accept updates unless you unroot your phone and go back to stock. Are you on hboot 1.5? I would suggest finding a rom that you want to flash (I recommend Myn's warmtwopoint3 RLS1 Deodex). To do this go into fastboot USB and load the custom recovery in the folder you downloaded to root your phone "fastboot boot recovery.img" (recovery.img should be replaced with the name of the CWM***.img file in that folder. This will give you full access to write the kernal and install the rom). Your issue is only likely kernal related so unless you do what I just mentioned, you wont have access to write a new kernal.
Click to expand...
Click to collapse
I have hboot 1.4 it wasnt locked. I just falshed the pg86img for my hboot but since it flashed the hboot too it doesn't have fastnoot anymore
Sent from my PG86100 using XDA App
mteezey said:
I have hboot 1.4 it wasnt locked. I just falshed the pg86img for my hboot but since it flashed the hboot too it doesn't have fastnoot anymore
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Does it still show hboot 1.4? According to the instructions, after the PG86IMG.zip installs, you need to go into fastboot and type "fastboot oem writesecureflag 3"
I think your probably just doing something wrong. Pull your battery out, put it back in, hold down volume button and power to boot into bootloader. Explain to me what you see. You should see fastboot on the top and you should be able to press the power button to enter fastboot and when you plug in your phone it will show fastboot usb. If this isnt happening I'm very curious as to what is.
Daaaavinnn said:
Okay guys, I have an HTC Evo 3D CDMA that is somewhat unusable. All I did was root the phone and in a few days the phone just wouldn't start up. It gets stuck on the HTC logo. I've tried getting it into download mode to flash a new stock firmware (but it didn't want to), I've tried to put the .zip stock firmware file onto the sd card to "install zip from sd card", I've tried to put the update file on the sd card to install it through "hboot", and even factory resetting it, but it still would get stuck on the logo and fail to boot up. I've tried just about everything I can think of, or find on the internet. Any other suggestions or solutions?
Click to expand...
Click to collapse
did you nandroid?
Thanks for the help everyone!
Hi everyone. The only reason why I wrote this status was because I rooted the phone for someone, and gave it back to them in working order. Then about a week later, they came back to me with that problem and I tried to fix it. But with no success as I stated above. They threatened to sue me or take me to small claims for this problem which i didn't even start. Talk about assholes. Anyways, they gave me the option of paying them 350 which is half of what they bought the phone for, or having me try to fix it. If I do fix it, no need to pay, but if I don't then I'd have to pay the full price which is 700. So I've decided to just pay them the 350 to shut their mouth, get my ass out of trouble, and get on with my life.
So yea, I guess I won't be needing this thread anymore. I really want to try fixing it to save me money, but I don't want to risk it. And yea, I know how much of an asshole they're being. But oh well, shows what kind of people they are.
Were you paid initially for services rendered, when first "working" on the phone? Did you make mention any guarantee/warranty for "work" performed? At any time was this person/persons aware of such forum/s which clearly express "do this at your own risk"?
Sent with L*W*H
Anytime your altering anything on anyone's phone always run them through the normal disclaimer. Make certain that they understand that you take ABSOLUTELY NO RESPONSIBILITY for any damage that might be caused by what THEY want you to do. **** happens sometimes and and you gotta cover your ass. This is why every Rom, Radio/firmware updates, themes and guides have the same disclaimer.
Sent from my PG86100 using xda premium
Just read the OP again. You only rooted the phone, didn't install a custom ROM? Also, after rooting it, the person whom you rooted the phone came to you after a week, not a day or two? In that time frame who knows what they tried to do. Also, someone mentioned a kernel issue as the most likely culprit. Are you able to get into recovery, volume down + power/recovery? Can you get to the bootloader/HBOOT screen? If you get anything other than just the bootloader screen, you may still salvage it. Any progress?
Sent with L*W*H
Daaaavinnn said:
Hi everyone. The only reason why I wrote this status was because I rooted the phone for someone, and gave it back to them in working order. Then about a week later, they came back to me with that problem and I tried to fix it. But with no success as I stated above. They threatened to sue me or take me to small claims for this problem which i didn't even start. Talk about assholes. Anyways, they gave me the option of paying them 350 which is half of what they bought the phone for, or having me try to fix it. If I do fix it, no need to pay, but if I don't then I'd have to pay the full price which is 700. So I've decided to just pay them the 350 to shut their mouth, get my ass out of trouble, and get on with my life.
So yea, I guess I won't be needing this thread anymore. I really want to try fixing it to save me money, but I don't want to risk it. And yea, I know how much of an asshole they're being. But oh well, shows what kind of people they are.
Click to expand...
Click to collapse
Did you check the SD card for anything that you didn't put on there? Sounds like you were scammed to me. Give me half now or try to fix it and if you can't you have to pay me full. Something doesn't sound right with that. Sounds like they didn't want to give you enough time to dig to deep into the phone. Did you check to see if it was even the same phone? Did you charge them for this service originally? What was the reason why they wanted root access?
Sent from my PG86100 using xda premium
Replies to all
Robert542 said:
Anytime your altering anything on anyone's phone always run them through the normal disclaimer. Make certain that they understand that you take ABSOLUTELY NO RESPONSIBILITY for any damage that might be caused by what THEY want you to do. **** happens sometimes and and you gotta cover your ass. This is why every Rom, Radio/firmware updates, themes and guides have the same disclaimer.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
That was the mistake I made, by NOT telling them that. Which is why I have absolutely NOTHING to cover my ass. Which is the reason why I'm going to pay for it to get out of this mess.
intrlude said:
Just read the OP again. You only rooted the phone, didn't install a custom ROM? Also, after rooting it, the person whom you rooted the phone came to you after a week, not a day or two? In that time frame who knows what they tried to do. Also, someone mentioned a kernel issue as the most likely culprit. Are you able to get into recovery, volume down + power/recovery? Can you get to the bootloader/HBOOT screen? If you get anything other than just the bootloader screen, you may still salvage it. Any progress?
Sent with L*W*H
Click to expand...
Click to collapse
I don't have the phone with me right now. Which is why I can't try anymore repairs. And I'm not going to in case it fails, then I'll have to pay full price.
Robert542 said:
Did you check the SD card for anything that you didn't put on there? Sounds like you were scammed to me. Give me half now or try to fix it and if you can't you have to pay me full. Something doesn't sound right with that. Sounds like they didn't want to give you enough time to dig to deep into the phone. Did you check to see if it was even the same phone? Did you charge them for this service originally? What was the reason why they wanted root access?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I don't remember what I did and didn't put on there. So I can't use that as a way to back myself up. And I honestly started thinking that it is a scam, but again, it is kind of is my fault for not taking extra precautionary measures to protect myself in the event that this thing happens. Yes, I did charge for the service. And they didn't say why they wanted it rooted. And even if they are scamming me, I'm just glad it happened sooner so that I could learn from it and prepare myself for the future. As for the money, I am bummed that I have to pay them, but God knows who's the better person and what kind of people they are so I'll let God deal with them.
I have the same issue, sort of. A friend brought me his Evo 3D for me to work on.
My friend 'rooted' his Evo3D through some steps up on youtube that claims root for the 1.5 hboot with S-ON. He then later DL Rom Manager and flashed the freEVO ROM. Now its only useful for WIFI, connected media/google talk/phone dialer/contacts do not work, they all say 'Could not launch the requested activity.'. I have tried factory resetting but it resets to the same issue, cant flash any other rom since there is no actual recovery.
Any ideas on how I can make this thing work
the258 said:
I have the same issue, sort of. A friend brought me his Evo 3D for me to work on.
My friend 'rooted' his Evo3D through some steps up on youtube that claims root for the 1.5 hboot with S-ON. He then later DL Rom Manager and flashed the freEVO ROM. Now its only useful for WIFI, connected media/google talk/phone dialer/contacts do not work, they all say 'Could not launch the requested activity.'. I have tried factory resetting but it resets to the same issue, cant flash any other rom since there is no actual recovery.
Any ideas on how I can make this thing work
Click to expand...
Click to collapse
You will find the answer for your problem here. Sticky's are our friend.
http://forum.xda-developers.com/showthread.php?t=1444285
Sent from my PG86100 using xda premium
thanks, i have already checked it out and tried some but this phone wont 'work'.
the258 said:
thanks, i have already checked it out and tried some but this phone wont 'work'.
Click to expand...
Click to collapse
I'm in the same boat. If I figure my phone out we will have a new guide "how to unbrick the EVO 3d"
Sent from my PG86100 using XDA App
mteezey said:
I'm in the same boat. If I figure my phone out we will have a new guide "how to unbrick the EVO 3d"
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
How is it bricked? Are you able to get into hboot or recovery. Never mind I read back.
Sent from my PG86100 using xda premium
Hi.
Why the mother flipping heck won't my Prime root?
I've tried the Zedomax 1 click script and ViperMODs method for devices running 9.4.2.11 and later (which mine is as its 9.4.2.28).
The first time I ran ViperMODs script I did all the tasks including number 3 to install the unlocker which seems to have run successfully as my Prime says 'this device is unlocked' in small white letters in the top left hand corner of the splash screen when booting.
But nothing has root privileges (I use Titanium backup to check).
What is going on, other people have rooted their .28s so why won't mine?
I have installed the USB drivers for the ADB interface and I've even done a full system restore on the Prime so that I'm working with a stock ROM but nothing helps
If anyone can help me to root my Prime I will let them marry my daughter* or take my son* as a slave (*as soon as I have one)
Thanks:crying:
thintin said:
Hi.
Why the mother flipping heck won't my Prime root?
I've tried the Zedomax 1 click script and ViperMODs method for devices running 9.4.2.11 and later (which mine is as its 9.4.2.28).
The first time I ran ViperMODs script I did all the tasks including number 3 to install the unlocker which seems to have run successfully as my Prime says 'this device is unlocked' in small white letters in the top left hand corner of the splash screen when booting.
But nothing has root privileges (I use Titanium backup to check).
What is going on, other people have rooted their .28s so why won't mine?
I have installed the USB drivers for the ADB interface and I've even done a full system restore on the Prime so that I'm working with a stock ROM but nothing helps
If anyone can help me to root my Prime I will let them marry my daughter* or take my son* as a slave (*as soon as I have one)
Thanks:crying:
Click to expand...
Click to collapse
I guess the first question would be, are you planning on putting a custom rom on the prime? If you are, they are all pre-rooted If you want to stick with a stock .28 rom look at virtuous....
If you are going to put a custom recovery on, which I am guessing your going to do since you have unlocked it, either go for an earlier version of twrp (2.1) or go the nvflash route, get the modified bootloader and then put on the latest twrp (2.2)...
I was going to root, use titanium to backup my user data and then try some custom ROMs. But I'm using another app backup program that doesn't require root now so I guess I can just go strait for a custom ROM lol. I got so hung up on why this thing wouldn't root that I forgot why I was doing it; D'oh!
So, on to flashing recovery then... why did you say to flash an older version first?
Thanks.
Sent from my Transformer Prime TF201 using XDA Premium HD app
thintin said:
I was going to root, use titanium to backup my user data and then try some custom ROMs. But I'm using another app backup program that doesn't require root now so I guess I can just go strait for a custom ROM lol. I got so hung up on why this thing wouldn't root that I forgot why I was doing it; D'oh!
So, on to flashing recovery then... why did you say to flash an older version first?
Thanks.
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
because the latest version requires you have the mobi modified bootloader which is only available if you follow through with the whole nvflash process. Not being familiar with your level of comfort/expertize if you use the older version you don't "need" to go the nv flash route right away... just gives a guy some breathing room.....
I have attached the older version or if you feel brave enough take the nvflash road..... it aint that hard if you follow the instructions... I can give some pointers to make it easier if you decide to go that way....
thintin said:
Hi.
Why the mother flipping heck won't my Prime root?
I've tried the Zedomax 1 click script and ViperMODs method for devices running 9.4.2.11 and later (which mine is as its 9.4.2.28).
The first time I ran ViperMODs script I did all the tasks including number 3 to install the unlocker which seems to have run successfully as my Prime says 'this device is unlocked' in small white letters in the top left hand corner of the splash screen when booting.
But nothing has root privileges (I use Titanium backup to check).
What is going on, other people have rooted their .28s so why won't mine?
I have installed the USB drivers for the ADB interface and I've even done a full system restore on the Prime so that I'm working with a stock ROM but nothing helps
If anyone can help me to root my Prime I will let them marry my daughter* or take my son* as a slave (*as soon as I have one)
Thanks:crying:
Click to expand...
Click to collapse
The method below works on 9.4.2.28
http://forum.xda-developers.com/showthread.php?t=1706588
success????
Gage_Hero said:
I guess the first question would be, are you planning on putting a custom rom on the prime? If you are, they are all pre-rooted If you want to stick with a stock .28 rom look at virtuous....
If you are going to put a custom recovery on, which I am guessing your going to do since you have unlocked it, either go for an earlier version of twrp (2.1) or go the nvflash route, get the modified bootloader and then put on the latest twrp (2.2)...
Click to expand...
Click to collapse
i have this problem re rooting, i have tried the vipermod primetime and DebugfsRoot_Generic_v2.3 both say once tablet reboots it will be rooted. then i try and ope cwmr and busybox and no root error message comes up, the device is unlocked as far as the top left tells me on boot, it is running 4.0.3 build no 9.4.2.28 the issue is this inverted x-axis problem but i cant even get the dam thing rooted to do anything with it. i have galaxy note 2 s3 and nexus 7 all rooted so i really am baffleld why this is so hard, if anyone has found a foolproof idiots guide please feel free to mail it to me. ..
i thank you all in advance and thanks for reading this request.
kindest regards
phil
philsmusic2000 said:
i have this problem re rooting, i have tried the vipermod primetime and DebugfsRoot_Generic_v2.3 both say once tablet reboots it will be rooted. then i try and ope cwmr and busybox and no root error message comes up, the device is unlocked as far as the top left tells me on boot, it is running 4.0.3 build no 9.4.2.28 the issue is this inverted x-axis problem but i cant even get the dam thing rooted to do anything with it. i have galaxy note 2 s3 and nexus 7 all rooted so i really am baffleld why this is so hard, if anyone has found a foolproof idiots guide please feel free to mail it to me. ..
i thank you all in advance and thanks for reading this request.
kindest regards
phil
Click to expand...
Click to collapse
You should go here and install this rom, the support here is very good. The rom is already rooted so there is nothing but install and play... since it looks like you are on an old rom play close attention to updating the bootloader first.....
http://forum.xda-developers.com/showthread.php?t=1674827
I just want to say a massive thanks for the help. I have now managed to get hairy bean 4.1 on it andnit is now fully unlocked and rooted. I still unfortunately habe thw inverted x-axis problem and from what I understand from what I've read the official jb4.2 will rectify this problem.
I can boot into the hairy recovery but not twrp I do the same reset/clear data as in the hairybean install instructions but then try to install jb4.2. The blue line goes to the top thwn it reboots but back into hairybean.
What am I doing wrong for this to keep happening?
Your help so far has been great and very much appreciated.
I thank you in advance for any further help that coukd direct me.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
Anyone?
Sent from my GT-N7105 1.8ghz using xda app-developers app
philsmusic2000 said:
Anyone?
Sent from my GT-N7105 1.8ghz using xda app-developers app
Click to expand...
Click to collapse
1. Unlock device
2. Install TWRP
3. Install Hairy Recovery & Upgrade Bootloader
4. Install Hairybean 2.2
But be sure your bootloader is 4.1.1 first before flashing TWRP(JB)、Hairy Recovery & Upgrade Bootloader
Did you upgrade to stock Jellybean before doing these procedures?
I just did these procedures 2 days ago from stock JB to Hairybean 2.2
Ok. I have managed to get stock 4.2.15 installed. But I am still lost ad to where I go to get this inverted x axis fixed. Its not at least not bricked so im relatively happy. But would really enjoy being able to press on what I want rather than opposite.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
philsmusic2000 said:
Ok. I have managed to get stock 4.2.15 installed. But I am still lost ad to where I go to get this inverted x axis fixed. Its not at least not bricked so im relatively happy. But would really enjoy being able to press on what I want rather than opposite.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
For HB2.2, there are kernels in the install options for the Reverse Axis
http://forum.xda-developers.com/showthread.php?t=1674827&page=931
Maybe it can fix your inverted x axis
Hmmm I downloaded the 2.2 but I believe that I have managed to brick it in the worst possible way. It wont boot into recovery. When I get it into apx mode. My pc wont see it as driver installed. So I cannot push any files to it or do anything. Dohhhhh.
Sent from my GT-N7105 using xda app-developers app
Any possibility of getting some advice on how to get this working again? Sorry to be a pain in the a$$ guys.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
philsmusic2000 said:
Any possibility of getting some advice on how to get this working again? Sorry to be a pain in the a$$ guys.
Kindest regards
Phil
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
You need to at least get into the bootloader. What happens when you keep holding volume down and power button the same timer for about 20 seconds. Do not stop holding them when the prime restarts after 10 seconds.
If you get to some icons on the screen then we might be able to help you.
Sadly if I hold vol dwn and pwr it just goes to the asus logo screen. Not boot loader options what so ever I have bought a new mobo off ebay thinking that would have helped. But this one seems to just jam on the rck loader. Try the rck mode it reboots to the same option screen. Trying usb mode does the same. Factory wipe wnds up the same and the android option just boots back into the asus logo. I cannot get my head around the way these are built. With any windows os unless you somehow screw the bios you can pretty much reinstall from any situation. Why is Android so different? I enjoy a challenge as much as the next guy but this is ludicrous. I have just done 6 16 hr days at work so I am not the most patient person with this right now so I think on tues on my day off work I will start again and see if I can get this working and redeem myself. I do just want to say thanks for the help off this forum though as people do seem very helpful and friendly.
Cheers guys.
Sent from my GT-N7105 using xda app-developers app
Sadly if I hold vol dwn and pwr it just goes to the asus logo screen. Not boot loader options what so ever I have bought a new mobo off ebay thinking that would have helped. But this one seems to just jam on the rck loader. Try the rck mode it reboots to the same option screen. Trying usb mode does the same. Factory wipe wnds up the same and the android option just boots back into the asus logo. I cannot get my head around the way these are built. With any windows os unless you somehow screw the bios you can pretty much reinstall from any situation. Why is Android so different? I enjoy a challenge as much as the next guy but this is ludicrous. I have just done 6 16 hr days at work so I am not the most patient person with this right now so I think on tues on my day off work I will start again and see if I can get this working and redeem myself. I do just want to say thanks for the help off this forum though as people do seem very helpful and friendly.
Cheers guys.
Sent from my GT-N7105 1.8 Ghz using xda app-developers app
Bump....
Does anyone have a spare tf201 mobo for sale?
Kindest regards
Phil
philsmusic2000 said:
Sadly if I hold vol dwn and pwr it just goes to the asus logo screen. Not boot loader options what so ever I have bought a new mobo off ebay thinking that would have helped. But this one seems to just jam on the rck loader. Try the rck mode it reboots to the same option screen. Trying usb mode does the same. Factory wipe wnds up the same and the android option just boots back into the asus logo. I cannot get my head around the way these are built. With any windows os unless you somehow screw the bios you can pretty much reinstall from any situation. Why is Android so different? I enjoy a challenge as much as the next guy but this is ludicrous. I have just done 6 16 hr days at work so I am not the most patient person with this right now so I think on tues on my day off work I will start again and see if I can get this working and redeem myself. I do just want to say thanks for the help off this forum though as people do seem very helpful and friendly.
Cheers guys.
Sent from my GT-N7105 1.8 Ghz using xda app-developers app
Bump....
Does anyone have a spare tf201 mobo for sale?
Kindest regards
Phil
Click to expand...
Click to collapse
When you say that the new mobo can get to where the icons are, when you press volume up on the usb icon does it say starting fastboot and then freeze?
If it does we have a chance.
Yes. Thats exactly what happens. Is there light at the end of the tunnel?
philsmusic2000 said:
Yes. Thats exactly what happens. Is there light at the end of the tunnel?
Click to expand...
Click to collapse
If it freezes there then you are in fastboot mode. Look in your device manager in windows and see if you have an unknown device or a fastboot device (names could have been changed to protect the innocent =] .)
If you have an unknown device then install the "naked drivers" from the dev thread to get fastboot working on your pc.
Let me know if you get this far and you see a fastboot device in your device manager.
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
squeezyb said:
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
Click to expand...
Click to collapse
Did you relock the boot loader?
Sent from my DROID RAZR using Tapatalk 2
yes i did
squeezyb said:
yes i did
Click to expand...
Click to collapse
More info would help like what errors you are getting
Sent from my DROID RAZR using Tapatalk 2
adb wont even find my device, so i am not getting any errors. is there a working RUU i can rename to PJ53IMG, and flash that through the bootloader?
http://forum.xda-developers.com/showthread.php?p=28723878
Sent from my DROID RAZR using Tapatalk 2
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
i know this is something simple that i can flash, but it is not working
squeezyb said:
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
Click to expand...
Click to collapse
Either should work but try the other
Sent from my DROID RAZR using Tapatalk 2
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupted on my end
squeezyb said:
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupt
Click to expand...
Click to collapse
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Have you tried the recovery? Check to see if that works. If not try to fastboot a recovery. The command is "Fastboot flash recovery". Try with TWRP. If that takes then try to flash a ROM with that.
blazingwolf said:
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Click to expand...
Click to collapse
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
On my side ill say do what the ther said, if you still have supercid you can unlock device and flash recovery and flash a working rom if you want it booteable
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
squeezyb said:
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
Click to expand...
Click to collapse
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
blazingwolf said:
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
Click to expand...
Click to collapse
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Great to hear.
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
No truer words are spoken
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Yep. And somehow time stands still for an eternity until something happens to let you know its alive.
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
prairiedogn said:
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
look here: http://forum.xda-developers.com/showthread.php?t=1435228
After flashing nocturnal Rom and installing apps i experienced a slight overheating and i turned off my phone. I turned it back on and I was unable to access the Rom, recovery, or boot loader. I flashed stock with LGPNST and i re-rooted and unlocked the bootloader. I had the same problem upon rebooting. SO...I can flash through LGPNST stock and root but every time i try the boot loader unlock and reboot my phone has the original problems . I've tried the process a few times with the same results.please help.
Dr0!dFreek said:
After flashing nocturnal Rom and installing apps i experienced a slight overheating and i turned off my phone. I turned it back on and I was unable to access the Rom, recovery, or boot loader. I flashed stock with LGPNST and i re-rooted and unlocked the bootloader. I had the same problem upon rebooting. SO...I can flash through LGPNST stock and root but every time i try the boot loader unlock and reboot my phone has the original problems . I've tried the process a few times with the same results.please help.
Click to expand...
Click to collapse
Nevermind that i got it working
Dr0!dFreek said:
Nevermind that i got it working
Click to expand...
Click to collapse
It may be helpful to someone else, if you were to explain how you fixed it.
Yes, it would indeed be quite helpful if you could elaborate... because this just happened to me and I'm stumped...
I followed the same exact procedure I've used other times without error...
Except that now, after LGNPST, then root, then freegee... go to restart the phone and it hangs... won't boot up. What gives?
I repeated the process and did a factory reset after LGNPST back to stock, since I noticed (oddly enough) that all my apps were still there after LGNPST (full, to 100%)...
Still no luck...
EDIT-- Can't for the life of me figure this effing thing out. LGNPSTed I don't know how many times... with factory reset, without... I've tried fully relocking and unrooting the device... both through the FreeGee app *and* manually through adb... no error mssgs, double-checked... everything followed to the letter. There's only one constant each time: Once I've re-unlocked the bootloader (either with the app or through adb)... the phone is basically softbricked... once I turn the power off, it is A) not possible to boot into the stock rom, B) not possible to access fastboot menu, and C) not possible to boot into recovery. The only thing it *is* possible to do is get into download mode... and from there I'd just have to LGNPST again, but what's the point, because once I've done that and tried to unlock again, I already know what's coming. Never been this frustrated with a phone before, any help would be greatly appreciated.
EDIT 2-- No luck. LGNPSTed to stock once more, and factory reset, because yet again, all my apps were still intact... idk. Anyways, decided to do some hunting around with adb, and "adb reboot recovery" produced an error screen... the android lying on his back with case open... am I to assume this means there is a problem with my recovery partition that could be causing my difficulties... or would one expect to see this screen when trying to access recovery on the stock phone?
adfurgerson said:
It may be helpful to someone else, if you were to explain how you fixed it.
Click to expand...
Click to collapse
Honestly I don't know how it was resolved. I lgpnsted and rooted and unlocked the bootloader like 5 times.I got into recovery a few times but then got the same problem two more times. The last time I got into recovery I managed to flash a custom kernel and everything was fine from then on. I just don't understand how this problem is caused or even how it is truly fixed.
Sent from my LG-E970 using xda premium
dht2005 said:
Yes, it would indeed be quite helpful if you could elaborate... because this just happened to me and I'm stumped...
I followed the same exact procedure I've used other times without error...
Except that now, after LGNPST, then root, then freegee... go to restart the phone and it hangs... won't boot up. What gives?
I repeated the process and did a factory reset after LGNPST back to stock, since I noticed (oddly enough) that all my apps were still there after LGNPST (full, to 100%)...
Still no luck...
EDIT-- Can't for the life of me figure this effing thing out. LGNPSTed I don't know how many times... with factory reset, without... I've tried fully relocking and unrooting the device... both through the FreeGee app *and* manually through adb... no error mssgs, double-checked... everything followed to the letter. There's only one constant each time: Once I've re-unlocked the bootloader (either with the app or through adb)... the phone is basically softbricked... once I turn the power off, it is A) not possible to boot into the stock rom, B) not possible to access fastboot menu, and C) not possible to boot into recovery. The only thing it *is* possible to do is get into download mode... and from there I'd just have to LGNPST again, but what's the point, because once I've done that and tried to unlock again, I already know what's coming. Never been this frustrated with a phone before, any help would be greatly appreciated.
EDIT 2-- No luck. LGNPSTed to stock once more, and factory reset, because yet again, all my apps were still intact... idk. Anyways, decided to do some hunting around with adb, and "adb reboot recovery" produced an error screen... the android lying on his back with case open... am I to assume this means there is a problem with my recovery partition that could be causing my difficulties... or would one expect to see this screen when trying to access recovery on the stock phone?
Click to expand...
Click to collapse
I had access to stock and I could root it. One thing that bothers me is that when I flash with lgpnst my data isn't erased and I feel like there may be a problem there of whether lgpnst is even taking our phones back to stock completely
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
I had access to stock and I could root it. One thing that bothers me is that when I flash with lgpnst my data isn't erased and I feel like there may be a problem there of whether lgpnst is even taking our phones back to stock completely
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
dht2005 said:
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
Click to expand...
Click to collapse
Sorry I wish I could help but I don't know that much.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
Sorry I wish I could help but I don't know that much.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
It's okay, I posted in XsMagical's thread, I'm hoping he can shed some light.
But actually, I'm just glad that I'm not the only one this has happened to...because if this error is reproducible, it can probably be fixed... so that's good. Thanks for your replies!
dht2005 said:
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
Click to expand...
Click to collapse
There have been a small number of phones that will not unlock with standard freegee. They can be unlocked but it is riskier, you would need to talk to Shelnutt in irc.
http://webchat.freenode.net/?channels=lg-optimus-g
adfurgerson said:
There have been a small number of phones that will not unlock with standard freegee. They can be unlocked but it is riskier, you would need to talk to Shelnutt in irc.
http://webchat.freenode.net/?channels=lg-optimus-g
Click to expand...
Click to collapse
Our phones successfully unlocked with freegee originally but some error caused us to lose access to the bootloader and corrupt whatever ROM we were on and then cause errors where we could use free gee but run into problems. In my situation the problem was resolved somehow and free gee worked fine afterwards
Sent from my LG-E970 using xda premium
I'll try and post how I fixed it, but it is recovery related. I'm also working on another way to reset our phones without using LGNPST, but I've been really busy. I'm close though and I believe it will be easier and faster.
Sent from my LG-E970 using Tapatalk 2
I'm still at work but I read most of the post and will try to see if there is a work around
Stroked from my Dirty Nocturnal'd Optimus G
droidiac13 said:
I'll try and post how I fixed it, but it is recovery related. I'm also working on another way to reset our phones without using LGNPST, but I've been really busy. I'm close though and I believe it will be easier and faster.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
XsMagical said:
I'm still at work but I read most of the post and will try to see if there is a work around
Stroked from my Dirty Nocturnal'd Optimus G
Click to expand...
Click to collapse
Thank you guys! I'm willing to try anything at this point. I appreciate it. And droidiac... this phone could really use a quick, easy, and reliable way to completely reset back to 100% stock, so that sounds exciting!
dht2005 said:
Thank you guys! I'm willing to try anything at this point. I appreciate it. And droidiac... this phone could really use a quick, easy, and reliable way to completely reset back to 100% stock, so that sounds exciting!
Click to expand...
Click to collapse
I just picked up a new laptop today so it's going to be a while unless it goes well.
Sent from my LG-E970 using Tapatalk 2
Just for the sake of documentation, I made a little log of my most recent attempt at getting back into the fastboot menu... obviously it's convoluted, but hey... sometimes experimentation gets results. This time, however, it did not... still no luck.
LGNPST back to stock
factory reset from settings->backups
run root exploit
restore original backups from first time freegeeing via adb using carrett's method
reboot
full unroot from SU app
factory reset
LGNPST to stock
re-run root exploit
reboot
re-unlock with freegee script (adb)
disconnect cable
reboot
(right here is the failure. after running "power off and reboot" from the power button menu, phone shuts off. it tries to start up, then i get a quick flash of the LG logo, straight to a backlit black screen that hangs indefinitely. only thing possible from here is to enter download mode.)
Back to the drawing board...
Same here
dht2005 said:
Just for the sake of documentation, I made a little log of my most recent attempt at getting back into the fastboot menu... obviously it's convoluted, but hey... sometimes experimentation gets results. This time, however, it did not... still no luck.
LGNPST back to stock
factory reset from settings->backups
run root exploit
restore original backups from first time freegeeing via adb using carrett's method
reboot
full unroot from SU app
factory reset
LGNPST to stock
re-run root exploit
reboot
re-unlock with freegee script (adb)
disconnect cable
reboot
(right here is the failure. after running "power off and reboot" from the power button menu, phone shuts off. it tries to start up, then i get a quick flash of the LG logo, straight to a backlit black screen that hangs indefinitely. only thing possible from here is to enter download mode.)
Back to the drawing board...
Click to expand...
Click to collapse
Just for documentation and in case I can help solving this, I am having the same problem, I explain my case with more detail on the FreeGree Thread, but pretty much I am on the same ship as you, I have tried after LGNPST, with and without factory reset, with the Google Play application and with the desktop application, but same result, black screen after restart.
I have a brand new phone, picked it less than a week ago, could LG have changed something? bootloader/recovery partition sizes? something?
I am still within the 14 days period and as much as I like the phone, if I can't bootloader unlock, means I will be stuck on stock ROM, and that is something I don't want... might as well go and change it for a different phone, or sell it and get a nexus 4...
I get same.thing. black screen after freegee. Its two days old. So now what!?
Sent from my LG-E970 using xda premium
Its a known issue. IRC guys can help. Something about the misc.IMG file getting corrupted
Sent from my Nexus 7 using xda app-developers app
nygfan760 said:
Its a known issue. IRC guys can help. Something about the misc.IMG file getting corrupted
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
How does this happen from a random stock ROM. I think I was using nocturnals ROM and how was the problem resolved through multiple flashes?
Sent from my LG-E970 using xda premium
Can somebody please provide me with a forum on how to unlock the bootloader, root the phone, and install a custom recovery on my droid dna. My software version is 2.07.605.1 710RD. Thank you.
http://forum.xda-developers.com/showthread.php?t=2437614
Sent from my dlx using Tapatalk
Or here.. http://forum.xda-developers.com/showthread.php?t=2314771
Sent from my HTC6435LVW using xda app-developers app
Looking for the same info...
gocool767 said:
Can somebody please provide me with a forum on how to unlock the bootloader, root the phone, and install a custom recovery on my droid dna. My software version is 2.07.605.1 710RD. Thank you.
Click to expand...
Click to collapse
I'm a complete n00b to rooting and have been trying to find an answer to the same question before diving in. I have looked through tons of info, including the 2 threads posted in responses, but can't seem to get a clear answer as to whether these methods work for 2.07... There seems to be a lot of conflicting reports. Would love to know if you confirm that either of these work.
May have answered my own question
It looks like there are further reports of moonshine working on 2.07.
http://forum.xda-developers.com/showthread.php?t=2510910
I'm going to give it a try tonight and will report back here.
I haven't seen anything about unlocking or rooting on 2.07, only s-off. I have a new DNA being shipped out thanks to my warranty, but I really don't want to go back to 4.1 after being on 4.3 for a few great months!
Moonshine works on recent dnas
schott12521 said:
I haven't seen anything about unlocking or rooting on 2.07, only s-off. I have a new DNA being shipped out thanks to my warranty, but I really don't want to go back to 4.1 after being on 4.3 for a few great months!
Click to expand...
Click to collapse
Yep, sorry for mixing up unlocking and rooting with s-off. I just thought getting s-off would better for a n00b like me as it seems to make the custom ROM / kernel process a bit more straight forward.
thayl0 said:
Moonshine works on recent dnas
Click to expand...
Click to collapse
I tried last night and ran into a few problems and then ran out of time. Got an error along the lines of [can't obtain temproot] during one of the moonshine steps... This may be due to the fact that I did not factory reset before moonshining. I will try again this evening (after factory reset).
Do you know I should go through the normal phone set-up after the factory reset? Or just reset then dive into moonshine?
Thanks!
GrzlyAdms said:
Yep, sorry for mixing up unlocking and rooting with s-off. I just thought getting s-off would better for a n00b like me as it seems to make the custom ROM / kernel process a bit more straight forward.
I tried last night and ran into a few problems and then ran out of time. Got an error along the lines of [can't obtain temproot] during one of the moonshine steps... This may be due to the fact that I did not factory reset before moonshining. I will try again this evening (after factory reset).
Do you know I should go through the normal phone set-up after the factory reset? Or just reset then dive into moonshine?
Thanks!
Click to expand...
Click to collapse
I'd think factory reset everything. I believe that is what I done. There is a support page for the moonshine program but I forget where it was.
---------- Post added at 06:12 PM ---------- Previous post was at 05:55 PM ----------
GrzlyAdms said:
Yep, sorry for mixing up unlocking and rooting with s-off. I just thought getting s-off would better for a n00b like me as it seems to make the custom ROM / kernel process a bit more straight forward.
I tried last night and ran into a few problems and then ran out of time. Got an error along the lines of [can't obtain temproot] during one of the moonshine steps... This may be due to the fact that I did not factory reset before moonshining. I will try again this evening (after factory reset).
Do you know I should go through the normal phone set-up after the factory reset? Or just reset then dive into moonshine?
Thanks!
Click to expand...
Click to collapse
I found the site..
I must had been on 2.06 when i done mine. I didn't even know there was another update.
I read on the moonshine site its only for 2.06
JUst type moonshine droid dna and you'll see it. I don't think I'm allowed to post links.
Well, I can 100% confirm that moonshine works for 2.07. It took several tries (4 to be exact, with factory reset between each), but I am now s-off! Woohoo! Now on to flashing twrp, and my first try at a custom ROM.
GrzlyAdms said:
Well, I can 100% confirm that moonshine works for 2.07. It took several tries (4 to be exact, with factory reset between each), but I am now s-off! Woohoo! Now on to flashing twrp, and my first try at a custom ROM.
Click to expand...
Click to collapse
Let me know if you need help flashing and ill tell you how.
thayl0 said:
Let me know if you need help flashing and ill tell you how.
Click to expand...
Click to collapse
Thanks for the offer! I was actually able to flash twrp and a custom ROM. It was much easier than I originally anticipated. My eyes are now open to a whole new world... Not sure I'll ever be able to go back to a stock Stock/manufacturer ROM.
Now running ViperDNA 2.0.1. I picked Viper as it sounds like this is one of the most stable/least buggy ROMs out there right now (plus it runs fine on the stock kernel). Do you have any other suggested ROMs for the DNA?
GrzlyAdms said:
Thanks for the offer! I was actually able to flash twrp and a custom ROM. It was much easier than I originally anticipated. My eyes are now open to a whole new world... Not sure I'll ever be able to go back to a stock Stock/manufacturer ROM.
Now running ViperDNA 2.0.1. I picked Viper as it sounds like this is one of the most stable/least buggy ROMs out there right now (plus it runs fine on the stock kernel). Do you have any other suggested ROMs for the DNA?
Click to expand...
Click to collapse
Looks good.
I too just had success with Moonshine. Just literally got my DNA, previous owner took the OTA. First time failed at "temproot", second time ran flawless.
Congratulations if u need help installing. SDK. Adb. Fastboot. Recovery and or a ROM. Message me
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Well, still troubleshooting some things. Successfully had root access and using the correct settings I could run wireless tether fine. I then proceeded to backup then install viper Rom. Set everything up fine however nothing I tried would get tether going. So I restored my backup (tether is a must) and still same issue. It starts but I cnt connect which is strange as I was using it fine earier.
So now I did a factory reset and flashed superuser, now tether won't start. Says "started with errors" using the exact same settings. So I'm going to try flashing the stock ota deodedex Rom see if that solves it.
Sent from my HTC6435LVW using xda app-developers app
GrzlyAdms said:
Well, I can 100% confirm that moonshine works for 2.07. It took several tries (4 to be exact, with factory reset between each), but I am now s-off! Woohoo! Now on to flashing twrp, and my first try at a custom ROM.
Click to expand...
Click to collapse
Did you use the Windows or Linux version?
Little Green Robot said:
Did you use the Windows or Linux version?
Click to expand...
Click to collapse
Windows (Vista believe it or not...). Make sure you have the correct device drivers installed first, and uninstall HTC Sync.
Sent from my dlx using Tapatalk