Great news see here :
http://androidroot.mobi/t3_nvflash/
Preferable to go on dedicated thread here:
http://forum.xda-developers.com/showthread.php?t=1774352
Great news!
Now let's discuss advantages and opportunities that this will open up besides access to repair bricks. I gotta do some research I don't know nearly enough about nvflash.
Sent from my ADR6425LVW using xda premium
I can vouch that it *shouldn't* brick your device.
(Well at least it didn't for mine)
So which of you brave souls will try this first?
Striatum_bdr said:
Great news see here :
http://androidroot.mobi/t3_nvflash/
Click to expand...
Click to collapse
Our "official" xda post is here: http://forum.xda-developers.com/showthread.php?t=1774352
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
williemeiser said:
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
Click to expand...
Click to collapse
From my understanding, if you can flash the bootloader to their custom build one and get hold of someone else's files then it should work...
The thing is,i already flash the custom bootloader n its fine but i cant proceed after that since i dnt hv the files.
Yea I can confirm too it works fine.
If you are unlocked you don't have any disadvantages with this, you only get a very tight security net which recovers you from almost anything you can do to your prime
Apart from that you get some more (dev orientated) new features. Read more on the AndroidRoot site
This is great news.
williemeiser said:
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
Click to expand...
Click to collapse
You need files off your own device. You can't use someone else's files.
However, if you can fast boot flash our bootloader successfully, it's definitely recoverable!
If not, then sorry, it won't work.
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
demandarin said:
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
Click to expand...
Click to collapse
+ 1. I don't normally sound all this nooby dooby, I do a lot of mess on my Dinc2, but this is a pretty costly piece of equipment and is renowned to get bricked with the slightest provocation, SOoooooo.... An automated fool-proof and newb proof procedure is much required, for me and definitely for the many here...
litetaker said:
+ 1. I don't normally sound all this nooby dooby, I do a lot of mess on my Dinc2, but this is a pretty costly piece of equipment and is renowned to get bricked with the slightest provocation, SOoooooo.... An automated fool-proof and newb proof procedure is much required, for me and definitely for the many here...
Click to expand...
Click to collapse
You're right. It is a costly piece of equipment so it NEEDS people thoroughly reading OUR guides, our warnings, our information to fully grasp what they are about to do.
It does NOT need someone just loading a utility and pressing a button labelled: "GIMME NVFLASH ZOMG!".
Also, when it comes to hacking any device - there is no such thing as foolproof.
kmdm said:
You're right. It is a costly piece of equipment so it NEEDS people thoroughly reading OUR guides, our warnings, our information to fully grasp what they are about to do.
It does NOT need someone just loading a utility and pressing a button labelled: "GIMME NVFLASH ZOMG!".
Also, when it comes to hacking any device - there is no such thing as foolproof.
Click to expand...
Click to collapse
Yeah, I just read a similar post on the other thread and it makes sense.. Well, I need to find a day I am willing to spend unlocking my prime and doing stuff on it.. So far, couldn't convince myself to even unlock. Now, that time is probably coming close...
There are at least 2 threads about NVFlash already, people should follow the rules
thread 1 here
thread 2 here
bk201doesntexist said:
There are at least 2 threads about NVFlash already, people should follow the rules
thread 1 here
thread 2 here
Click to expand...
Click to collapse
Those threads are *****ing about there not being nvflash, this one is unrelated to your two examples, if you read the thread you may have seen that, however there is a thread in the dev section for the same thing.
It's Tapatalk's app fault, stickies are not displayed on the same page than regular posts... So didn't see the thread.
Reason to unlock
At last a real reason to unlock. I held off when the first roms appears due to the risk of full brick. Now there is no real risk, unless you brick while backing up your NVFlash files.
Now is the real time to experiment with roms and different device settings. Let the good times roll
Related
Hey guys I recently got the Amaze (2 days ago). When I got it, it was on GB but I went to T-mobile to get a new sim and the guy updated my phone to ICS. Now ive tried rooting it but it does not work, i tried with the all tool kit program and the one click root. IS their anything I am doing wrong? Also do I have to be in recovery mode or can I be at the home screen? Debugging is on.
The only thing I can tell your doing wrong is your not reading enough. There is an Amaze Bible. There are How To Root Tutorials. It's been asked multiple times.
I haven't used All In One (AIO) Tool Kit but I think there's a Tutorial.
Sorry..its just frustrating coming to a forum and everyone ask the same thing over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over......you catch my drift?
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
pakakid said:
Hey guys I recently got the Amaze (2 days ago). When I got it, it was on GB but I went to T-mobile to get a new sim and the guy updated my phone to ICS. Now ive tried rooting it but it does not work, i tried with the all tool kit program and the one click root. IS their anything I am doing wrong? Also do I have to be in recovery mode or can I be at the home screen? Debugging is on.
Click to expand...
Click to collapse
If you searched the word "root" in my thread, there are many posts mentioning that it does not work and I said I was gonna eventually fix it.
On other terms, flash this in recovery
Try the tool kit again, note that you have to install a custom recovery before trying to root via the tool kit, once you have a custom recovery, boot into recovery then hit the root option, it should ask you to press enter once you're in recovery, do this and you shall be rooted.
Dark Nightmare said:
Try the tool kit again, note that you have to install a custom recovery before trying to root via the tool kit, once you have a custom recovery, boot into recovery then hit the root option, it should ask you to press enter once you're in recovery, do this and you shall be rooted.
Click to expand...
Click to collapse
As mentioned below, this might not be working for everyone. It pushed all the files for me but did not result in root. Flashing the superuser zip linked below is what finally worked for me.
hasoon2000 said:
If you searched the word "root" in my thread, there are many posts mentioning that it does not work and I said I was gonna eventually fix it.
On other terms, flash this in recovery
Click to expand...
Click to collapse
Double0EK said:
The only thing I can tell your doing wrong is your not reading enough. There is an Amaze Bible. There are How To Root Tutorials. It's been asked multiple times.
I haven't used All In One (AIO) Tool Kit but I think there's a Tutorial.
Sorry..its just frustrating coming to a forum and everyone ask the same thing over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over and over......you catch my drift?
Click to expand...
Click to collapse
On a separate note,
I very much appreciate the help that can be received here and there quite a few tutorial threads. The problem I think some people have, including me, is that what is written doesn't always make sense to those who don't live and breathe android. I'm fairly tech savvy (have built computers, know basic bash scripting, and have spent excessive amounts of time troubleshooting and hacking in Linux) but instructions like "flash stock RUU in hboot" don't make much sense until you've spent a lot of time reading.
Hasoon's tool is very close to what is needed. Hopefully whatever issue there is with the root option can be fixed. Or maybe it's just a matter of better understanding of how to use it.
droidux said:
As mentioned below, this might not be working for everyone. It pushed all the files for me but did not result in root. Flashing the superuser zip linked below is what finally worked for me.
On a separate note,
I very much appreciate the help that can be received here and there quite a few tutorial threads. The problem I think some people have, including me, is that what is written doesn't always make sense to those who don't live and breathe android. I'm fairly tech savvy (have built computers, know basic bash scripting, and have spent excessive amounts of time troubleshooting and hacking in Linux) but instructions like "flash stock RUU in hboot" don't make much sense until you've spent a lot of time reading.
Hasoon's tool is very close to what is needed. Hopefully whatever issue there is with the root option can be fixed. Or maybe it's just a matter of better understanding of how to use it.
Click to expand...
Click to collapse
That's why we have an amaze bible thread bro, we have every and anything about the amaze from the simplest term broken down and explained, that includes but not limited to hboot, s-off, fastboot, bootloader, etc. Check it, you'll be glad you did.
droidux said:
As mentioned below, this might not be working for everyone. It pushed all the files for me but did not result in root. Flashing the superuser zip linked below is what finally worked for me.
On a separate note,
I very much appreciate the help that can be received here and there quite a few tutorial threads. The problem I think some people have, including me, is that what is written doesn't always make sense to those who don't live and breathe android. I'm fairly tech savvy (have built computers, know basic bash scripting, and have spent excessive amounts of time troubleshooting and hacking in Linux) but instructions like "flash stock RUU in hboot" don't make much sense until you've spent a lot of time reading.
Hasoon's tool is very close to what is needed. Hopefully whatever issue there is with the root option can be fixed. Or maybe it's just a matter of better understanding of how to use it.
Click to expand...
Click to collapse
Google is your friend. I taught myself many things from Google before I asked a question. If I am TRULY stuck, I'll ask a question.
Look at the threads I made, I rarely ask a question because I found it from Google.
You can learn a lot by yourself and just searching stuff online. Not that hard lol
hasoon2000 said:
Google is your friend. I taught myself many things from Google before I asked a question. If I am TRULY stuck, I'll ask a question.
Look at the threads I made, I rarely ask a question because I found it from Google.
You can learn a lot by yourself and just searching stuff online. Not that hard lol
Click to expand...
Click to collapse
I completely agree. I've taught myself tons about programming and such using Google, but you also have to have enough background knowledge to know what to look for and recognize when you find it. I've mostly asked questions here but it wasn't until I did a lot searching and trying things. Eventually, when something doesn't work you can stop and ask a question or keep messing around. In the later case, you either brick the phone or become one of the experts (after bricking the phone ).
Problem with google is that it often points to a thread here which invariably results in someone new asking a question that's been asked before. Happens in all forums.
Dark Nightmare said:
That's why we have an amaze bible thread bro, we have every and anything about the amaze from the simplest term broken down and explained, that includes but not limited to hboot, s-off, fastboot, bootloader, etc. Check it, you'll be glad you did.
Click to expand...
Click to collapse
I did.
I have the following:
Samsung-SGH-I777
2.3.6
I777UCKK6
2.6.35.7
GingerBread.UCKK6
I have spent a lot of time reading XDA and other Android Boards hoping I could find a pretty straightforward way to get control of my phone (su access?). I want to get rid of apps that T put on and I also want to be able to hotspot my phone. But I really want to understand what I am doing. Every thread seems to assume a level of knowledge I just don't think I have. I'm tempted to jump in but feel like I'll then just be a poster saying HELP BRICKED MY PHONE.
When I come across a youtube or pdf that looks promising - it invariably has comments associated with it like: Oh, if you upgraded to 2.3.6 watch out.....or, I did this and now my wifi doesn't work.
Here is my question - can anyone point me to a thread or website that really walks a novice through the basics like the difference between a Rom and a kernel, how the SD card works etc.
And certainly if someone can point me to a solid root procedure for my phone (see above) please feel free.
Thanks for listening
Peter
Stackman1 said:
I have the following:
Samsung-SGH-I777
2.3.6
I777UCKK6
2.6.35.7
GingerBread.UCKK6
I have spent a lot of time reading XDA and other Android Boards hoping I could find a pretty straightforward way to get control of my phone (su access?). I want to get rid of apps that T put on and I also want to be able to hotspot my phone. But I really want to understand what I am doing. Every thread seems to assume a level of knowledge I just don't think I have. I'm tempted to jump in but feel like I'll then just be a poster saying HELP BRICKED MY PHONE.
When I come across a youtube or pdf that looks promising - it invariably has comments associated with it like: Oh, if you upgraded to 2.3.6 watch out.....or, I did this and now my wifi doesn't work.
Here is my question - can anyone point me to a thread or website that really walks a novice through the basics like the difference between a Rom and a kernel, how the SD card works etc.
And certainly if someone can point me to a solid root procedure for my phone (see above) please feel free.
Thanks for listening
Peter
Click to expand...
Click to collapse
Sorry man, That level of knowledge you speak of, is what you need. If you cant find the info, dont root your phone.
We dont hold hands here, there is plenty of info around. Find it and put it to use.
If you searched for everything your looking for, you'd find your answers.
Its obvious that you HAVE NOT spent anytime looking for the answers you seek.
Good luck peter.
Like what was said above, getting the information for all these things is really simple.
Read the stickies.
All of the warnings and disclaimers are tacked onto the instructions because people don't want you to blame them if you don't follow directions or if something that works for someone else doesn't work for you.
Stackman1 said:
I have the following:
Samsung-SGH-I777
2.3.6
I777UCKK6
2.6.35.7
GingerBread.UCKK6
I have spent a lot of time reading XDA and other Android Boards hoping I could find a pretty straightforward way to get control of my phone (su access?). I want to get rid of apps that T put on and I also want to be able to hotspot my phone. But I really want to understand what I am doing. Every thread seems to assume a level of knowledge I just don't think I have. I'm tempted to jump in but feel like I'll then just be a poster saying HELP BRICKED MY PHONE.
Click to expand...
Click to collapse
Are you using the AT&T phone on T-mobile? Just curious.
When I come across a youtube or pdf that looks promising - it invariably has comments associated with it like: Oh, if you upgraded to 2.3.6 watch out.....or, I did this and now my wifi doesn't work.
Click to expand...
Click to collapse
Just my personal opinion, but I would forget all the other sites, and youtube videos, and stick with what you learn here.
Here is my question - can anyone point me to a thread or website that really walks a novice through the basics like the difference between a Rom and a kernel, how the SD card works etc.
Click to expand...
Click to collapse
I'm not aware of such a guide. Some of the information is so basic that no one would think to make a guide for it. But I can give you one tip: in my guide there is a link to extra information for newbies. That can be fairly helpful.
And certainly if someone can point me to a solid root procedure for my phone (see above) please feel free.
Click to expand...
Click to collapse
In my opinion, my guide is the best, but if you must, you can also use Jivy26's how to root guide.
Thanks for listening
Peter
Click to expand...
Click to collapse
Creepy -
Thanks for taking the time to reply. I am using the AT&T network.
Hey man, you gotta be willing to take that big plunge. Over in the Dev section there is some good info. But you gotta be willing to take that challenge on. Just be prepared to have a brick if you do it wrong.
BigRob1712 said:
Hey man, you gotta be willing to take that big plunge. Over in the Dev section there is some good info. But you gotta be willing to take that challenge on. Just be prepared to have a brick if you do it wrong.
Click to expand...
Click to collapse
It is really hard to brick your phone following the instructions here.
As long as you don't flash anything outside the AT&T Galaxy S2 Forums.
Id recommend Creepy's guide, Ive used this myself and can vouch for it. Avoid (no offense meant) using Zedomax's method to avoid the headache of breaking wifi and trying to get it back. and READ and RE READ before starting the process.
enjoy your soon to be freed phone
I very strongly agree with the advice to follow creepyncrawly's guide. Taking the time to read, understand and follow it will make the process easy and save you a lot of headaches. Don't be afraid to ask for clarification, but read, read and then read some more can't be stressed enough. Take it from a fellow novice.
I will continue to read and take the plunge soon. Definitely look into Creepy's guide.
Thanks to all that chimed in without lecturing.....
Try this link:
forum.xda-developers.com/wiki/ROM-VS-Kernel
mmarquis said:
Try this link:
forum.xda-developers.com/wiki/ROM-VS-Kernel
Click to expand...
Click to collapse
What link? Here ya go. http://forum.xda-developers.com/wiki/ROM-VS-Kernel
Sent from my SGH-I777 using Tapatalk 2
That's an OK summary of firmware, but the use of the word ROM as a generic term for firmware needs a little explanation.
A ROM, or read-only memory, is a computer memory chip that has machine executable code built into it when it is manufactured. The code can not be changed. Later models of the chip were programable, and were called PROM, or programable read-only memory which can be programed once, and ePROM, or erasable programable read-only memory, which can be reprogrammed. These type of chips were used in the earliest micro computers, up until current computers, to accomplish the first step in the boot-up process.
Smart phones do not have a ROM or similar memory chip. They use NOR, P-SRAM and/or One-NAND, forms of non-volatile flash memory. The Galaxy series uses NAND memory to store the firmware. The iPhone uses PSRAM.
The use of the term ROM to refer to the firmware which contains the operating system for the phone is merely a convention, but one which has a huge amount of traction, so much so that we all use the term. There are some who would like to see the term ROM disappear in favor of the term firmware, but that is unlikely.
xhepera said:
I very strongly agree with the advice to follow creepyncrawly's guide. Taking the time to read, understand and follow it will make the process easy and save you a lot of headaches. Don't be afraid to ask for clarification, but read, read and then read some more can't be stressed enough. Take it from a fellow novice.
Click to expand...
Click to collapse
+1 to this. Also, if you ever need help, you can check out the IRC channel. There's usually someone there that can help.
creepyncrawly said:
Are you using the AT&T phone on T-mobile? Just curious.
Just my personal opinion, but I would forget all the other sites, and youtube videos, and stick with what you learn here.
I'm not aware of such a guide. Some of the information is so basic that no one would think to make a guide for it. But I can give you one tip: in my guide there is a link to extra information for newbies. That can be fairly helpful.
In my opinion, my guide is the best, but if you must, you can also use Jivy26's how to root guide.
Click to expand...
Click to collapse
I believe I used creepy's guide, entropy's posts. Gotta focus on one thing: getting clockwork recovery mode on (CWM). Get that and you can load a from from here. Don't use rootwiz or anything else. Make XDA your some source.
Sent from my SGH-I777 using xda premium
Irc channell.... so many people in there can answer and if ur going to for some reason use zedomax tutorial.. as i did with my Mac do it with entropy daily driver kernel
im on my phone. expect terrible typos.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
All i did to root my sgs2 was get the proper drivers on pc (kies installs them i believe?). Downloaded odin 1.85 and any kernel that has cwm (i used siyah). put the phone in download mode (lots of places tell you how to do this). Put the kernel in the pda spot in odin. And flash.
Now you have a rooted phone with cwm (if all went right).
then you just download your favorite rom (i used serendipity 9.4) and place on sd card. Boot to recovery. Wipe cache/dalvik cache and factory wipe. Then flash your rom.
That's how i did it any way
Must be something in the water...
murauder said:
All i did to root my sgs2 was get the proper drivers on pc (kies installs them i believe?). Downloaded odin 1.85 and any kernel that has cwm (i used siyah). put the phone in download mode (lots of places tell you how to do this). Put the kernel in the pda spot in odin. And flash.
Now you have a rooted phone with cwm (if all went right).
then you just download your favorite rom (i used serendipity 9.4) and place on sd card. Boot to recovery. Wipe cache/dalvik cache and factory wipe. Then flash your rom.
That's how i did it any way
Must be something in the water...
Click to expand...
Click to collapse
The bolded statement is inaccurate. If you followed this sequence exactly as stated, you were not rooted until you installed serendipity.
Noob to noob
The information creepy posted is the way to go. I used his superoneclick with root to get out of a failed clockwork mod loop back to stock with root.
The post was I777UCKH7OCD Root no BL.7z. This will give you clockwork mod recovery from which you can do further modifications.
The program is a 7zip file. READ about 7Zip. Follow the instructions.
Practice getting your phone into download mode (dry runs).
Don't panic.
After reading if you still have questions, read some more. All the information is here.
When you sucessfully root, look in the dev section and read about the custom roms/firmware and see how they operate, problems, successes before choosing.
Personally I like the AOKP by Task, but it is all preferences.
Good luck, you can do it.
After much hard work and scary semi-bricks, we are proud to finally provide nvflash to the masses!
This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.
Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!
NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
More details at http://androidroot.mobi/?p=452
Important note: We kind of forgot to clarify what the license for wheelie was so here goes. Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.
Update log:
18. July: Added windows version!
21. July: Clarify License
Enjoy
- AndroidRoot.Mobi Team
NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.
Dude... exactly what I need. You are awesome.
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
williemeiser said:
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
Click to expand...
Click to collapse
Nobody else can provide their blobs to other users, Each device has a different SBK making them incompatible with other devices.
however, you are not "bricked" if you can access fastboot, you have enough access to perform what is required
lilstevie said:
Nobody else can provide their blobs to other users, Each device has a different SBK making them incompatible with other devices.
however, you are not "bricked" if you can access fastboot, you have enough access to perform what is required
Click to expand...
Click to collapse
Is it? Maybe Im just too nervous. but I cant access recovery. Even when i flashed it in fastboot,still i cannot access it. N im running out of ideas,
williemeiser said:
Is it? Maybe Im just too nervous. but I cant access recovery. Even when i flashed it in fastboot,still i cannot access it. N im running out of ideas,
Click to expand...
Click to collapse
you could try fastboot boot recovery.img (where you have a cwm image named recovery.img) and see if that boots, if that doesn't work it is probably a hardware issue.
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
demandarin said:
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
Click to expand...
Click to collapse
Tbh... If you don't have the ability to follow the simple instructions then you have no business attempting this process at all...
kmdm said:
Tbh... If you don't have the ability to follow the simple instructions then you have no business attempting this process at all...
Click to expand...
Click to collapse
good one.
I knew someone was going to say that..lol. just like rooting methods and other tweaks, a more simpler automated way usually arrives. I have no problem with this but I'm sure alot of others might.
time will tell. I'm sure this will be cooked up into an app/exe.
its all good though
demandarin said:
good one.
I knew someone was going to say that..lol. just like rooting methods and other tweaks, a more simpler automated way usually arrives. I have no problem with this but I'm sure alot of others might.
time will tell. I'm sure this will be cooked up into an app/exe.
its all good though
Click to expand...
Click to collapse
I cannot speak for the others but I personally would not be impressed with this outcome. It is not like other rooting methods and other tweaks, this carries a high brick risk. One-clicks and all those types of installers trivialize the risk that we are trying to make users aware of. Making someone read the instructions gives us the opportunity to really reinforce the risk that you are undertaking.
Is this for real???? iiiiiaaaaaahhhh!!!
Edit: can anyone mirror nvflash t3/ics binary?
lilstevie said:
I cannot speak for the others but I personally would not be impressed with this outcome. It is not like other rooting methods and other tweaks, this carries a high brick risk. One-clicks and all those types of installers trivialize the risk that we are trying to make users aware of. Making someone read the instructions gives us the opportunity to really reinforce the risk that you are undertaking.
Click to expand...
Click to collapse
very well put. you right.
So if we have twrp and a custom rom installed this will still work correct?
Sent from my Transformer Prime TF201 using Tapatalk 2
Great stuff!
I went to download nvflash from Nvidia and was greeted with the message:
"Posted July 12, 2012
NVIDIA suspended operations today of the NVIDIA Developer Zone (developer.nvidia.com). We did this in response to attacks on the site by unauthorized third parties who may have gained access to hashed passwords."
Can anyone send me the nvflash util?
joeyddr said:
So if we have twrp and a custom rom installed this will still work correct?
Sent from my Transformer Prime TF201 using Tapatalk 2
Click to expand...
Click to collapse
yeah, it should still work fine, as long as /data has not been messed up.
lilstevie said:
yeah, it should still work fine, as long as /data has not been messed up.
Click to expand...
Click to collapse
Could you kindly post a mirror link for NVflash? The Nvidia development forums are down due to an investigation of a hacking attack... Or, may be I am searching the wrong place so could you link an active download link from Nvidia site?
litetaker said:
Could you kindly post a mirror link for NVflash? The Nvidia development forums are down due to an investigation of a hacking attack... Or, may be I am searching the wrong place so could you link an active download link from Nvidia site?
Click to expand...
Click to collapse
Anyone with the tegra 3 ICS nvflash? I can't find it anywhere either.
I tried following the instructions on Androidroot.mobi but when I run the following command in windows
fastboot -i 0x0b05 flash bootloader ebtblob.bin
I get bootloader error 0x30003 and I am told that flash was unsuccessful in Command prompt, I am a little confused as to what this means. Additionally is there special setup required for Fastboot? (ive done a quick look around and havent found anything). If anyone can point me to a detailed explanation I would appreciate it, I clearly don't know enough yet to press forward this set up and I'd rather not risk bricking my prime cuz of my ignorance
Thank you in advance
shreddintyres said:
fastboot -i 0x0b05 flash bootloader ebtblob.bin
I get bootloader error 0x30003 and I am told that flash was unsuccessful in Command prompt,
Click to expand...
Click to collapse
What bootloader version do you have at the moment?
kmdm said:
What bootloader version do you have at the moment?
Click to expand...
Click to collapse
I'm not sure, i should have the stock asus bootloader, I am unlocked and have TWRP as recovery.
Presently i am running AOKP milestone 6.1
I experienced issue when using Rom Manager Premium 1.0.7. In fact, when I want to go to recovery mode from the application to backup my current rom, the app automatically asks me to make a title for the backup. After that I continue, it shuts my device and restarts it and it says Failed to Boot 2 and Starting RSD Mode... and it stays there for few minutes and I assume that it is frozen then I pulled the battery out and restart the phone. It boots normally, so I try it again but every time when I give a try it does the same thing. What can I do?
I am using a rooted Atrix 4G with stock Gingerbread ROM 2.3.4 and the CWM recovery is already flashed before attempting to do the above procedures.
There's also a thing that bothers me, my Atrix is an unlocked phone (it is not those that is on contracted, "locked', with the carrier) and rooted, but I've hear some people saying that even your device is unlocked and rooted, that does not guarantee that the bootloader is also unlocked, especially with the Motorola devices. Am I corrected or is this the case?
Some other information about my device:
System version:
45.0.23.ME860.Retail.en.05
Model number:
ME860
Android version:
2.3.4
Baseband version:
N_01.100.00R
Webtop version:
WT-1.2.0-133_21
Kernel version:
2.6.32.9
[email protected] #2
APflex version:
GAS_ASIA_OLPSGBAPHKTWN_P011
GAS_ASIA_OLPSGBAPHKTWN_A001
GAS_ASIA_OLPSGBAPHKTWN_M001
Build number:
4.5.2A-74_OLH-25
PLEASE HELP!!!
Don't bother with rom manager. Its a crappy app that most times doesn't work. Besides which, it sounds like you are bootloader locked, which means you can't use a custom recovery until you unlock it. Best place to start is searching for the unlock thread, then you can begin to utilize fastboot to get a proper recovery and ultimately a custom rom if you choose.
I saw online that many people unlock their bootloader by using Command Prompt on their computer which I do not like since I am not good in computer language and entering codes. Any suggestion for a easy way to unlock the bootloader such as an application similar to Superoneclick for rooting [slightly complicated one is also accepted as long as no command prompt or computer language are involved]? Thanks.
The unlock method by using what you call "computer codes" is as simple as it gets. It's just a few commands. I don't think anybody is going to bother making a clickable GUI frontend for such a trivial task. I think your best bet is to just follow the procedure and quit being scared of "computer codes".
ravilov said:
The unlock method by using what you call "computer codes" is as simple as it gets. It's just a few commands. I don't think anybody is going to bother making a clickable GUI frontend for such a trivial task. I think your best bet is to just follow the procedure and quit being scared of "computer codes".
Click to expand...
Click to collapse
What he says is true. Until my atrix (had backflip and flipside previously) I only used one click root. Once I got the atrix, one clicks didn't work, so I just CAREFULLY followed instructions to root and eventually unlock 2 atrixes and I dislike codes as much as you. Its all in how much you read read read. Its well worth it to do so.
pre4speed said:
What he says is true. Until my atrix (had backflip and flipside previously) I only used one click root. Once I got the atrix, one clicks didn't work, so I just CAREFULLY followed instructions to root and eventually unlock 2 atrixes and I dislike codes as much as you. Its all in how much you read read read. Its well worth it to do so.
Click to expand...
Click to collapse
I also hear people say that Motorola put a code on Droid X that when you want to unlock your bootloader it will "permanently" brick your phone and you can not turn it on again. But I am not sure that if they do the same on Atrix or maybe some guys already crack it since this is not a news. Do anyone here has the same experience like this?
Hm. Seems to me you developed an irrational fear of all this due to an information overload, even though much of that information doesn't even apply here.
Do you think there would be a clear and detailed tutorial (which countless people followed successfully already) if this was really so risky?
Put some trust into our devs here, will ya? Nothing can go wrong so long as you follow the instructions PRECISELY and take necessary precautions (if a tutorial says to do a backup, you do it).
ravilov said:
Hm. Seems to me you developed an irrational fear of all this due to an information overload, even though much of that information doesn't even apply here.
Do you think there would be a clear and detailed tutorial (which countless people followed successfully already) if this was really so risky?
Put some trust into our devs here, will ya? Nothing can go wrong so long as you follow the instructions PRECISELY and take necessary precautions (if a tutorial says to do a backup, you do it).
Click to expand...
Click to collapse
Sorry about that, but unlike those of you who are in the game for years, right now I just got ONE (1) Android phone (and I just got XDA last night) so I can not get any error when doing these tweaks. Maybe I should slow myself down a bit and wait until Christmas after I got my Huawei Ascend D1 Quad to hack my Atrix. You know, it's like playing poker.
Oh yes. You should definitely not jump the gun and do something before you're ready. Do read and learn and educate yourself before you take any actions. Just keep in mind that this is not as complicated as it may seem.
ravilov said:
Oh yes. You should definitely not jump the gun and do something before you're ready. Do read and learn and educate yourself before you take any actions. Just keep in mind that this is not as complicated as it may seem.
Click to expand...
Click to collapse
So so true. So many people automatically panic at one minor thing (anyone who has unlocked their bootloader knows what I mean ) but if the tutorial is followed TO THE LETTER that minor thing is not an issue. Good luck and yes educate yourself.
Alright so there are a few users who are locked on Jelly Bean and are wanting to take the dive of unlocking and installing a custom rom. So I figured I'd put together this little guide to hopefully help y'all out.
I am not responsible for any damage you do to your device. Following this is your choice.This will void your Asus warranty and you assume all responsibility from here on out.
As long as you follow all directions in this guide your device will not be bricked. It will be unleashed to this beast of a tablets max power
Before you continue make sure you:
1. Have the drivers for your device installed on your computer
2. Have made the upgrade to Jelly Bean
3. Have the USB cable for your Prime
4. Have nerves of steel and the ability to read all and follow instructions in this guide.
Useful Information for total beginners: Some people using this guide may not even entirely understand what they are undertaking. This is not acceptable so it's time for some education. Android is a Linux based operating system (in it's self, not direly important information but it's nice background knowledge) which means that there are certain permissions to users. Having "root" permission is like being an "Administrator" on Windows systems. All devices come without "root" permissions as the total new users can do irreparable damage to their device. This is different than unlocking your boot loader. Unlocking your boot loader (in the Transformer Prime's case) is the act of saying to Asus "I willingly give up my devices warranty in exchange for the ability to totally control my device so I can flash custom software". Unlocking does not automatically give a device root permissions. This can only be obtained through an exploit or by flashing the proper thing after unlocking. Since I'm not perfect at wording (and it's best to educate yourself as much as possible on the subject) there is more info here:
http://www.androidpolice.com/2010/0...top-5-benefits-of-rooting-your-android-phone/
http://www.droidforums.net/forum/ga...53-explain-unlocking-boot-loader-rooting.html
Step 1 Download the Unlock tool here: http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download (navigate to Downloads, then select the OS as Android, then scroll to utilities and expand the menu. Find the unlock tool and download that. Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean). Install this app on your Prime and run it. Connect to a network before doing so and follow all on-screen directions.
Step 2. By this point the unlock tool has done it's job and when you boot your Prime now has a nice "Your device is unlocked" message in the upper left corner of the screen. The next step is to flash a custom recovery image (TeamWin Recovery Project(TWRP) in this guides case). This may sound complicated but there are multiple easy ways to do this.
Option 1: Go to the TeamWin website and download the needed files as directed on the page and follow the instructions on the website to flash TWRP. (http://teamw.in/project/twrp2/93)
Option 2 (easy option): This option flashes TWRP running a file from your Windows computer. The file attached at the bottom of this guide needs to be downloaded and unzipped to your desktop. Once this is done you power of your Prime and turn it back on while holding the volume down button. Once the tab vibrates release the power button but continue to hold the volume down button.
Once this has been done you will see 4 icons pop up. One is the USB symbol. Navigate to that by pressing the Volume Down button until the icon is highlighted and press volume up to select it (the menu will say use Volume Up to navigate but this is incorrect). This will put your device into fastboot mode. Connect your Prime to your computer via the USB cable and open the folder you extracted earlier. Run the Windows Batch File. This will automatically flash the TeamWin Recovery image for the Jelly Bean bootloader.
Now that you have unlocked and have a custom recovery installed you can begin the flashing. To get into your recovery all you do is power up while holding volume down and select the RCK icon. This boots the recovery image and you'll be able to flash, back up, and restore roms. All threads will have a guide on how to flash the rom in the thread so I won't go into detail. I do suggest however, using a microSDcard to store downloaded roms for flashing as it is safer than internal storage. If you are looking to back up your apps then there's this amazing app called Titanium Backup on the Android Market. It's very powerful and can backup your apps as well as user data.
HELP! Something went wrong and I need help: As with all processes there can be issues that arise. Some are common and others are individual. Let's address some common problems for all you who are still nervous about this:
1. Everything seemed to go fine but my Prime won't boot into TWRP
SOLUTION: This problem comes up for a few reasons and is pretty common. A lot of time it's simply a bad download or you have the wrong files. Check the files you have and make sure they are the right ones. If so then download them again. Sometimes a download just gets corrupted. If neither of these solutions worked either try another method of installing TWRP outlined on their website or post here and either I or another helpful person will do everything possible to help
2. When I tried to flash a custom ROM it won't boot:
SOLUTION: Usually this is an issue specific to the ROM you are flashing. The basic list of problems to eliminate are:
1.Ensure you have a good download
2.Ensure you have the proper boot loader for the ROM (i.e. JB boot loader for Jelly Bean ROMs
3. Try reflashing the rom. Sometimes something just doesn't work and the only way to fix it is to reflash
Vocab guide for totally new users:
Rom(s): Basically the operating system of your device.
TWRP: Team Win Recovery Project. Started by developers here at XDA and is a powerful recovery tool.
Brick/bricked device: Developer term for saying your device will no longer work due to software/roms and is basically a very, very expensive brick/paper weight.
FAQ: Q: My device is on Jelly Bean but the unlock tool will not work for me no matter what I do. What's wrong?
A: Asus has some issues as a company and certain people are completely unable to unlock their device no matter what. I suggest contacting Asus with your devices S/N and politely ask for an explanation and see if the issue can be resolved. Many users who have used the Asus RMA have still been unable to unlock afterwards.
Other useful links: http://www.youtube.com/watch?v=-pW05Jf87dg&list=UU7YzoWkkb6woYwCnbWLn3ZA&index=22&feature=plcp
Very comprehensive video guide with a full walkthrough to help all with this process. And of course all users can PM me with questions or ask them here.
SuperSU.zip attached is for those who want to root the stock rom. Any custom rom should already be rooted for you.
Good tutorial ..On your way to becoming a recognized contributer
Sent from my LG-P509 using Tapatalk 2
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
DaLongTjeu said:
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
Click to expand...
Click to collapse
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
applesuckz said:
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
Click to expand...
Click to collapse
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
DaLongTjeu said:
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
Click to expand...
Click to collapse
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
McJesus15 said:
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
Click to expand...
Click to collapse
I don't doubt your answer, I had never heard about any server-related issues though. Lots of people reported that their Prime's somehow had forgotten their serial numbers, but mine still has it's serial number. Also I registered my S/N online and it's still there, but I don't think that's related in any way. I RMA'd twice, I'm able to get OTA fm updates (possibly a clue that there are no server-side issues with my S/N), but now I'm unable to unlock.
Your guide is great and I really hope it helps many users unlock their Primes so they can get rid of the stock rom and flash a proper one onto their devices. You might want to insert a note though, that even though the unlock tool has been confirmed to work on some JB-primes there's still a chance it won't work (whatever the reason is).
OK let's stop squabbling about semantics here. Fact of the matter is that whoever's able to unlock at this point is quite lucky. The rest of us will just have to wait until ASUS fixes the issues or some whizzkid with too much time on his hands does.
You are a Gem, this finally made the process so much clearer
Shizbazki said:
You are a Gem, this finally made the process so much clearer
Click to expand...
Click to collapse
Thank you feel free to hit the thanks button
Sent from my Zio using xda app-developers app
Hi. I did all the steps you mentioned. In flashing TWRP I chose the 2nd option and everything went great.
The problem appears when I want to go to my recovery (power up holding volume down and then RCK) I get the droid with exclamation mark and nothing happens. Flashing recovery was succesful and I dont have an idea what could went wrong. I'm bit a new user of TF201 so would be grateful if You can help me
EDIT: Ah, I saw now that recovery is not flashing properly, saying sth like InvalidState.
EDIT 2: Ok I handled it myself, thanks again for the guide it was very useful!
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
Nvflash is only available to users who did it while on ICS.
Sent from my Zio using xda app-developers app
McJesus15 said:
http://forum.xda-developers.com/showthread.php?t=1998359
Link to my guide thread in the general forum. If anybody has any questions you can PM me or comment there and it'll likely be answered quickly. I'll gladly guide anyone through this process if they need other information.
Click to expand...
Click to collapse
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
kingdazy said:
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
Click to expand...
Click to collapse
Once unlocked you can root with a flashable zip. Can't link to one but they're easy to find here on the TFP forum
Sent from my Zio using xda app-developers app
So this would be su.zip (or whatever it's called), and have the following structure?
su.zip
META-INF/
CERT.RSA
CERT.SF
MANIFEST.MF
COM/
GOOGLE/
ANDROID/
update-binary
updater-script
system/
app/
Superuser.apk
bin/
su
I just want to confirm if the file I found is correct or not. Does it need to be for a specific tablet/system? If it was just the app folder and the su binary I wouldn't ask, but the inclusion of metadata has me concerned as I can't seem to find one for the prime specifically.
EDIT: Yup, that's it. I stuck it on the internal storage, went into TWRP, choose "install", navigated to the zip, and it went without a hitch (installed the su binary and superuser app, effectively rooting the system).
Overall, this a good process for people that just want to root without all the hassle of replacing the whole OS.
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
What do you think of androwook? Is much better than stock JB?
BashYaBro said:
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
Click to expand...
Click to collapse
Try contacting Asus.
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Androwook 1.4 turns the prime into the tab it should be. Out scores stock by a lot on benchmarks
Sent from my Zio using xda app-developers app
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
mrwookie6379 said:
Just to give you guys a heads up I will be releasing v1.5 fairly soon to take advantage of the new update that is out but before anyone groans about only having just flashed v1.4 I will release it as an update to those already on v1.4 but also as a full ROM for those who want to skip v1.4 and go straight to v1.5.
Beta 1 for v1.5 was created this PM and is being uploaded for testing now so watch this space.
Click to expand...
Click to collapse
Awesome.
kingdazy said:
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
Awesome.
Click to expand...
Click to collapse
I really ansious about flashing androwook... Just have to found some time!! Thinking about doing it this weekend!
Well.... So do you think really worths the upgrade to Androwwok? I saw that the search bug has a fix, but are there too many other bugs?
And, the performance, is really much better?
Thansk for the answer, friend.
regards