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.
Related
i know there are many tpics similar but i cant find a straight answer or working link..
basically i flashed a rom and this rom ws working fine until it started to reboot everytime i chargd the phone then it would boot loop for like 30min and finaly go in to the rom.. ive tried to access the recovery to switch roms but it just bootloops.. onlything i can go is to bootloader.. i was looking for a stock rooted
P0g5?? file to flash in bootloader but all i can find is mr2 and its in multiupload which is not working for me.. can anyone please give me a working link or answer... and the last option i would hate to do is completely restore to stock and root allover again.. i want to restore to stock rooted/s-off.. not stock rooted/s-on.. please help anyone....
Can u download a new recovery, rename, then flash in hboot possibly?
Sent from my ADR6400L using XDA
I had an issue kinda similar like this and ended up having to flash the RUU through the bootloader. It is the stock firmware 605.19, and I had to reroot. It's a pain I know but it works
Sent from my ADR6400L using xda premium
dizzyman1180 said:
I had an issue kinda similar like this and ended up having to flash the RUU through the bootloader. It is the stock firmware 605.19, and I had to reroot. It's a pain I know but it works
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I to had to this at one point and it does work. I would first try to flash cwm in fastboot though. Sometimes that works.
Sent from my ADR6400L using Tapatalk 2
My friend's phone tried to pull an OTA while he had CWM recovery installed, and it started boot looping. Had to download the stock recovery, name is PG05IMG.zip in the root of the SDCard, and force the phone to boot to the bootloader and install it. Once it did, the phone started up, rebooted itself, and installed the OTA fine. Sounds like yours may be trying to do something similar?
If so rooted phones need caches cleared for the ota to work.
Sent from my ADR6400L using Tapatalk 2
From my understanding, Rooted can still take OTA, but you have to have stock recovery to do it (as I witnessed earlier). You will lose root, and will have to re-flash recovery to TWRP, CWMR, or whatever your normal choice is, and then re-apply the su.zip, but otherwise easy as pie.
Tiezane said:
My friend's phone tried to pull an OTA while he had CWM recovery installed, and it started boot looping. Had to download the stock recovery, name is PG05IMG.zip in the root of the SDCard, and force the phone to boot to the bootloader and install it. Once it did, the phone started up, rebooted itself, and installed the OTA fine. Sounds like yours may be trying to do something similar?
Click to expand...
Click to collapse
Do you by chance have a working link to the stock recovery? I have been trying to find one without success.
Sent from my ADR6400L using xda premium
I won't be home to later, I'll get it to you then, but I'm piety sure I found it through thunderboltforums.com
Sent from my ADR6400L using XDA
Tiezane said:
I won't be home to later, I'll get it to you then, but I'm piety sure I found it through thunderboltforums.com
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
I would appreciate that. Thank you
Sent from my ADR6400L using xda premium
dizzyman1180 said:
I would appreciate that. Thank you
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Stock recovery PG05IMG.zip http://dl.dropbox.com/u/61129367/PG05IMG-Stock-Recovery.zip
Hello, first of all I would like to thank everyone who has posted in this thread to try and help out. I just started having a very similar problem- I'm rooted and running stock, but apparently my phone accepted an OTA and I'm stuck in a bootloop as well.
I got into CWM recovery and downloaded the stock recovery PG05IMG.zip, but it won't install. It just aborts every time I try to install it. I'm a noob at this stuff and not very good at dealing with these sorts of things and I've been having a panic attack for the past hour, so if anyone could help me as soon as possible I would really appreciate it.
I'm really scared of making things worse than they already are. I just want a working phone.
trter10 said:
Stock recovery PG05IMG.zip http://dl.dropbox.com/u/61129367/PG05IMG-Stock-Recovery.zip
Click to expand...
Click to collapse
Much appreciated my friend.
Sent from my ADR6400L using xda premium
pull battery, wait a minute, turn on phone
when in bootloader screen,
volume down, select reboot
back to white screen, select recovery ( i had to do this twice)
hold volume up and power when black screen appears
choose the bottom option (wipe cache i believe)
choose reboot
phone should be good aftter this
( idont own a thunderbolt, but i had to fix this for a nother phone, called tech support and this worked)
hope this helps - hopefully saves someone from ruu'ing and wiping their phone
Thank you for posting the file, life got in the way yesterday. Hope that fixes your situation!
Sent from my ADR6400L using XDA
webermn15 said:
Hello, first of all I would like to thank everyone who has posted in this thread to try and help out. I just started having a very similar problem- I'm rooted and running stock, but apparently my phone accepted an OTA and I'm stuck in a bootloop as well.
I got into CWM recovery and downloaded the stock recovery PG05IMG.zip, but it won't install. It just aborts every time I try to install it. I'm a noob at this stuff and not very good at dealing with these sorts of things and I've been having a panic attack for the past hour, so if anyone could help me as soon as possible I would really appreciate it.
I'm really scared of making things worse than they already are. I just want a working phone.
Click to expand...
Click to collapse
The zip won't work in CWM because it's not designed for use with CWM. It's designed for use in Fastboot. Should be on the root of your sd card. From off, if I'm correct (like this with other HTC devices), hold volume down and power to boot into fastboot. This will allow it to flash the stock recovery.
dlamber7 said:
The zip won't work in CWM because it's not designed for use with CWM. It's designed for use in Fastboot. Should be on the root of your sd card. From off, if I'm correct (like this with other HTC devices), hold volume down and power to boot into fastboot. This will allow it to flash the stock recovery.
Click to expand...
Click to collapse
Right. I also have a recovery zip that installs the stock recovery if anyone wants it?
It can be found here: http://dl.dropbox.com/u/61129367/OTARestoreAndRecovery.zip
(warning: I have tested it and it works but it did cause me a bootloop, and im assuming this is becuase im on a different rom - - - so not responsible for any damages)
HELP
My battery went tits up the other day so I had to purchase a new battery.....Ended up with HTC extended battery.(all verizon had in stock). When I put the battery in and powered on it just pops up with the HTC screen....couple secs go by the phone vibrates....HTC again......I can get the phone into bootloader.....but for the life of me can only get fastboot to work.....I have tried pushing cwm through that as well as the img above with no luck.....The Hboot only shows my device as android 1.0 and is unrecognized.I have reloaded drivers and everything I know how....Someone please help
Windows 7 64 bit ultimate
Rooted Thunderbolt running Thunderstick
BaD TacTics said:
My battery went tits up the other day so I had to purchase a new battery.....Ended up with HTC extended battery.(all verizon had in stock). When I put the battery in and powered on it just pops up with the HTC screen....couple secs go by the phone vibrates....HTC again......I can get the phone into bootloader.....but for the life of me can only get fastboot to work.....I have tried pushing cwm through that as well as the img above with no luck.....The Hboot only shows my device as android 1.0 and is unrecognized.I have reloaded drivers and everything I know how....Someone please help
Windows 7 64 bit ultimate
Rooted Thunderbolt running Thunderstick
Click to expand...
Click to collapse
Have you tried an ruu?
Sent from my ADR6400L using Tapatalk 2
Hello, Out of desperation for a quick answer as I find many on 2.3.5 or situations that aren't the same as mine, I tried flashing MIUI and it failed. I made a backup prior but then it failed .. I tried it a few times and so I decided to reboot device.. I am now stuck.. I rooted my wifes phone right after she got it about a year or so ago and so It's using the recovery that you boot into while running the phone. I"ve never been able to get to recovery unless I open the app "System Recovery". I click install recovery.. then boot recovery.. I don't even know what it's called it's been so long.
Anyway, Now I can't even do anything. As soon as I plug the phone in it sits at the dual core logo and does nothing. I can get to fastboot but have no idea what to try. My battery is probably not charging and I"m screwed on how to charge it to as it doesn't seem to power off and charge once plugged in. I know she was on 2.3.4 last time I looked and it failed everytime she tried to update. She uses her phone for her business hence my desperation to fix quickly. I've been clicking links frantically but can't seem to find a clear cut solution as I'm just not able to get into recovery. Thanks for any help!!!
xsisbest said:
Hello, Out of desperation for a quick answer as I find many on 2.3.5 or situations that aren't the same as mine, I tried flashing MIUI and it failed. I made a backup prior but then it failed .. I tried it a few times and so I decided to reboot device.. I am now stuck.. I rooted my wifes phone right after she got it about a year or so ago and so It's using the recovery that you boot into while running the phone. I"ve never been able to get to recovery unless I open the app "System Recovery". I click install recovery.. then boot recovery.. I don't even know what it's called it's been so long.
Anyway, Now I can't even do anything. As soon as I plug the phone in it sits at the dual core logo and does nothing. I can get to fastboot but have no idea what to try. My battery is probably not charging and I"m screwed on how to charge it to as it doesn't seem to power off and charge once plugged in. I know she was on 2.3.4 last time I looked and it failed everytime she tried to update. She uses her phone for her business hence my desperation to fix quickly. I've been clicking links frantically but can't seem to find a clear cut solution as I'm just not able to get into recovery. Thanks for any help!!!
Click to expand...
Click to collapse
I've never heard of a "system recovery" app. To get into the custom recovery just press and hold volume + power until fastboot appears. Press down until you see android recovery. Press up to enter it. Then restore your backup. You can do all of this with a dead battery or no battery as long as it's plugged it. What recovery are you using?
Reading it again looks like bootstrap?? That's not a real recovery, it's almost useless. You can't install ROMs like MIUI with it. You have to unlock your bootloader and use a custom recovery to do that! If you want to restore without losing data you'll want to SBF back to stock.
Sent from my MB853 using XDA
Thanks for the reply. When I get to android recovery I get the error in the title. It just sits there. I guess bootloader is what it is. I can't even get into recovery and that is my issue. It just says failed to boot 2. This photon is garbage imo. I've had the EVO now the EVO LTE and both were so simple but this one just confuses the hell out of me. I'm a flashaholic on my evos but I rarely attempt anything on the wife's as it seems way more complicated. I'm sure its not and if it was my phone I'd have more patience but the wife hates me at the moment so I'm desperate lol. Any other solutions besides boot into recovery cause that just isn't working...I was able to get into recovery when it was working but now it goes to the error and sits on the logo.
sent from my EVO 4g LTE minus the LTE
xsisbest said:
Thanks for the reply. When I get to android recovery I get the error in the title. It just sits there. I guess bootloader is what it is. I can't even get into recovery and that is my issue. It just says failed to boot 2. This photon is garbage imo. I've had the EVO now the EVO LTE and both were so simple but this one just confuses the hell out of me. I'm a flashaholic on my evos but I rarely attempt anything on the wife's as it seems way more complicated. I'm sure its not and if it was my phone I'd have more patience but the wife hates me at the moment so I'm desperate lol. Any other solutions besides boot into recovery cause that just isn't working...I was able to get into recovery when it was working but now it goes to the error and sits on the logo.
sent from my EVO 4g LTE minus the LTE
Click to expand...
Click to collapse
nah man! the photon is a great device. it's nearly impossible to brick it. which i love. you don't have a custom recovery. that's why you get an error. you're just seeing the stock recovery. which isn't a recovery, it's just made to factory reset. pressing volume up + down will allow you to see the recovery without the error. you need to SBF if you want to get the system back. that is the BEST solution if you are on 2.3.4. once you do that. you can unlock the bootloader if you want. but that wipes all your data. so backing up would be necessary. this is the same all devices. INCLUDING THE EVO. if you are locked forever and on 2.3.5 you need to do some work arounds as there's no sbf available.
http://www.motosunfire.com/sbf-restore-photon/
BOOTSTRAP IS NOT A REAL RECOVERY. YOU CANNOT FLASH UNLOCKED ROMS THROUGH IT. KEEP THAT IN MIND!
U need to flash sbf file throught the pc open youtube search for a video called .how to unbrick photon .by qbking77 that will fix ur phone if u face any problem just ask ur problem is completly fixable just be patient
Sent from my MB855 using xda app-developers app
Thanks for the words of encouragement and advice. I'll let you know of it worked!
sent from my EVO 4g LTE minus the LTE
xsisbest said:
Thanks for the words of encouragement and advice. I'll let you know of it worked!
sent from my EVO 4g LTE minus the LTE
Click to expand...
Click to collapse
good luck!
MIONS said:
U need to flash sbf file throught the pc open youtube search for a video called .how to unbrick photon .by qbking77 that will fix ur phone if u face any problem just ask ur problem is completly fixable just be patient
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
You guys are saviours! This fixed me right up. Now to root properly. I always thought she was rooted as she had root access and what looked to me like an Amonra recovery. The full root process sounds a little more in depth than the EVO but I'm sure ill figure it out. Thanks again for all your help!
So can you guys recommend a Rom? I hate the motoblur and was leaning towards miui since I've ran it before but am open to suggestions.
sent from my EVO 4g LTE minus the LTE
U r wellcome first if u want a new rom u should unlock ur bootloader and install a reall recovery not the bootstrap
U can also see a qbking channel for unlocking photon bootloader then the recovery
If u find any difficulty just ask
ALL THIS IF UR 2.3.4
IF I HELPED U JUST PRESS THANK BUTTON
Sent from my MB855 using xda app-developers app
xsisbest said:
You guys are saviours! This fixed me right up. Now to root properly. I always thought she was rooted as she had root access and what looked to me like an Amonra recovery. The full root process sounds a little more in depth than the EVO but I'm sure ill figure it out. Thanks again for all your help!
So can you guys recommend a Rom? I hate the motoblur and was leaning towards miui since I've ran it before but am open to suggestions.
sent from my EVO 4g LTE minus the LTE
Click to expand...
Click to collapse
as mentioned above if you're on 2.3.5. you cannot unlock your bootloader. it's permanently locked! that phone will most likely never see a true ROM. like CM, MIUI, AOKP, etc. no way around this whatsoever. sorry my friend.
again, don't attempt to flash any ROMs through bootstrap except stock locked ROMs.
if you're on 2.3.4 you should try out CM or AOKP or PA!!! unlocking is easy.
I'm unlocked and ready to roll! I was always on 2.3.4 so thank god that ota always failed I think I'm gonna give a look at that PA rom you mentioned if I can find what PA stands for lol. I've tried CM on my evo's and AOKP was still a bit buggy and my wife needs her phone to work on almost every function (camcorder not so much..) Bluetooth is huge! I think MIUI is goin up first she likes the look of that but what does PA stand for? . Thanks again for all your help! Thanks button hit for all!!
xsisbest said:
I'm unlocked and ready to roll! I was always on 2.3.4 so thank god that ota always failed I think I'm gonna give a look at that PA rom you mentioned if I can find what PA stands for lol. I've tried CM on my evo's and AOKP was still a bit buggy and my wife needs her phone to work on almost every function (camcorder not so much..) Bluetooth is huge! I think MIUI is goin up first she likes the look of that but what does PA stand for? . Thanks again for all your help! Thanks button hit for all!!
Click to expand...
Click to collapse
Paranoid Android!
Gonna give Paranoid a go.. I flashed MIUI 5 times and it just hangs on the bootanimation. Never did get to the rom. Hopefully I have better results with aokp and paranoid. I realized that's what it was right after posting but thanks again!
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
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
Ok im new to this whole rooting thing, i own a galaxy note i717 and i tried rooting it but when i used odin clicked pda then slected file and hit start it went through the process and even passed but now when i turn my phone on it shows the samsung logo then a blank screen i think i might have screwed up my phone really good, and can it be fixed? IF YOU would help me unbrick my phone please do. My phone is my whole life i have alot of important information on it. email @ [email protected]
mwebb34 said:
Ok im new to this whole rooting thing, i own a galaxy note i717 and i tried rooting it but when i used odin clicked pda then slected file and hit start it went through the process and even passed but now when i turn my phone on it shows the samsung logo then a blank screen i think i might have screwed up my phone really good, and can it be fixed? IF YOU would help me unbrick my phone please do. My phone is my whole life i have alot of important information on it. email @ [email protected]
Click to expand...
Click to collapse
Do you have clockworkmod recovery installed? If so try going into recovery and wipe the cache and dalvik cache
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
it's showing the Samsung logo, you aren't bricked it is still turning on.
just reflash a stock Odin file
mwebb34 said:
Ok im new to this whole rooting thing, i own a galaxy note i717 and i tried rooting it but when i used odin clicked pda then slected file and hit start it went through the process and even passed but now when i turn my phone on it shows the samsung logo then a blank screen i think i might have screwed up my phone really good, and can it be fixed? IF YOU would help me unbrick my phone please do. My phone is my whole life i have alot of important information on it. email @ [email protected]
Click to expand...
Click to collapse
You might give some more info on what all you did or what file you were trying to flash....
Sounds like the problem of Gingerbread root on ICS system, or vice-versa. Just redo your work, ensuring you use the appropriate file for your system.
By the way, NEVER tweak your system until you learn to move important stuff to your external sd card or pc.
Boot into clockwork mod. Do factory wipe, wipe dalvik/cache. Should fix it.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Adonisd said:
Boot into clockwork mod. Do factory wipe, wipe dalvik/cache. Should fix it.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Yea what i said.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Its the best advice that's why it deserves an echo!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Really? I think the best advice was rangercaptain's advice followed by crixley. OP was using odin which means he was trying to install a rooted kernel most likely from a different android version or he was installing CWM. So I highly doubt he has CWM installed and functioning. So how is he going to boot into CWM??
Well I guess I thought he followed the proper instructions and installed cwm first. I admittedly skimmed most of the posts.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
What if we can't get into clockwork mod any more?
Adonisd said:
Boot into clockwork mod. Do factory wipe, wipe dalvik/cache. Should fix it.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I screwed mine up by not wiping after installing the new Cyanogenmod. The thing is, I can't get it to boot into clockwork mod recovery mode any more. Volume up + home + power is not doing it. Have I bricked it?
stinkyp00t said:
I screwed mine up by not wiping after installing the new Cyanogenmod. The thing is, I can't get it to boot into clockwork mod recovery mode any more. Volume up + home + power is not doing it. Have I bricked it?
Click to expand...
Click to collapse
Its volume up + volume down + power hold those.
ROM: Jamie's 4.2.2. Previews\Jellybam v6.6.0\Sons Of Android.
Kernel: Chris's Aces Kernel.
Recovery: TWRP.
:thumb up: Give Thanks! :thumb up:
I have to chime in here...I have bricked mine, too, started with 4.0.1...I installed cwm-LATEST touch-i717, followed by openrecovery-twrp-2.2-sgh-i717-signed, ran fine. Then I was going to use Liquid-JB-v2.0-RC8-d2att.zip, but used the wrong gapps (Google Apps) file, gapps-jb-20120726-signed, instead of Liquid-JB-v2.0-RC8-gapps. Now, I have a black screen, and on my Mac, the thing just connects and reconnects all by itself! Can I get out of this, if I can't get to a restore screen?
lildaddym said:
I have to chime in here...I have bricked mine, too, started with 4.0.1...I installed cwm-LATEST touch-i717, followed by openrecovery-twrp-2.2-sgh-i717-signed, ran fine. Then I was going to use Liquid-JB-v2.0-RC8-d2att.zip, but used the wrong gapps (Google Apps) file, gapps-jb-20120726-signed, instead of Liquid-JB-v2.0-RC8-gapps. Now, I have a black screen, and on my Mac, the thing just connects and reconnects all by itself! Can I get out of this, if I can't get to a restore screen?
Click to expand...
Click to collapse
You were going to flash the wrong Rom anyways d2att is s3. Would have bricked you right there if you flashed it. If you can't get to download mode or recovery you will most likely need jtag
Sent from my SAMSUNG-SGH-I717 using xda premium
Is that something one can do themselves? What is JTAG?
rquiett said:
You were going to flash the wrong Rom anyways d2att is s3. Would have bricked you right there if you flashed it. If you can't get to download mode or recovery you will most likely need jtag
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
A JTAG is a recovery service offered for bricked phones. You can find one for your device at mobiletechvideos.com for 50$. Just Google android JTAG service. It will come up. Hit thanks
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
There has to be another answer...
When you find it, come back here and share it with us.
JTAG service costs $50, takes a week, and restores a phone that cannot enter recovery, or download mode, or isn't recognised by a computer.
WWW.mobiletechvideos.com
MobileTechVideo Works
rangercaptain said:
When you find it, come back here and share it with us.
JTAG service costs $50, takes a week, and restores a phone that cannot enter recovery, or download mode, or isn't recognised by a computer.
WWW.mobiletechvideos.com
Click to expand...
Click to collapse
Just to chime in here... I just got my AT&T Note back from MobileTechVideo. I had them do a JTAG repair ($50) and ordered a new jig. They replied with fast, reliable service. I highly recommend them if you decide to send your phone out for repair.
zancro said:
Just to chime in here... I just got my AT&T Note back from MobileTechVideo. I had them do a JTAG repair ($50) and ordered a new jig. They replied with fast, reliable service. I highly recommend them if you decide to send your phone out for repair.
Click to expand...
Click to collapse
Thanks, but I found someone a little more personal...when I approached them, they simply recommended that I send it to them, rather than try some basic troubleshooting... Maybe just the way they do things...lots of volume with MobileTechVideo...