Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
What we need:
1. Nexus One with FRF72
2. The files I provide
3. Android SDK
4. Transcend Class 6 4gig(High recommend but not a must)
5. A brain!!!
Click to expand...
Click to collapse
YOU MUST FOLLOW ALL STEPS, OTHERWISE YOU LOSE!
Step 0:
- Install the SDK
- Make sure there is no "update.zip" in SD card
- Connect your phone with the USB
- Extract all files I provided to your <SDK>/tools
Step 1:
Enable Debugging in Setting->Development
Then, shut down your phone
Step 2:
Booting into bootloader by holding vol- and press Power
Use vol- button to highlight "Recovery"
Step 3:
Open CMD, and cd to the <SDK>/tools
Run "loop"
Step 4:
Press Power to enter Recovery now, you will see the triangle and <!>
Hold Power and vol+ to show the menu
Step 4a:
If your CMD shows you the devices is in recovery, press control + c to stop the "loop"
Step 4b:
If there is nothing, reboot your phone and repeat step 2-4 until it shows up.
(This is 99% caused by the sd card, faster card make it easier to show up)
Step 5:
Select "Apply update.zip", and it will show failed(IMPORTANT!!!!)
Step 6:
Run "adb push ota.zip /sdcard/update.zip"
Run "adb push busybox /sdcard/busybox"
Step 7:
Type but not run "adb push root.zip /sdcard/update.zip"
Step 8:
Select "Apply update.zip" again and run the step-7-code half a second later.
IF IT SHOWS ERROR STATUS 6, DOWNLOAD THE NEW ZIP I UPLOADED
Step 8a:
If it works, it will print ""Nexus One Rooting modified by Booker from Hong Kong"
Step 8b:
If it failed, repeat step 6-8
Step 9:
Finished the process, you can now immediately flash_image.
Step 10:
If you do flash a new recovery image, you may need to remove "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p"
This prevent the system automatically re-flash your recovery image to the stock one.
Click to expand...
Click to collapse
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
requirements. for this method
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
actuallly you can get the official version, put it on your sd card and install it without being rooted. That is what they want you to do.
You see those of us who were rooted had to wait for a repacked version of the FRF72 update or we had to revert to stock with a stock recovery to get it to install. So sir, this is a valid method and you will keep your warranty intact!
O_O this is a really big deal NO?
anangphatak said:
Hey..your post says you require frf72 for this to work
But that requires me to root my n1...(epe54b)...which means bootloader unlocking.
Will your method then remove the padlock?
There is not much reason to root the t-mo n1 since they can flash frf50 anyway (tethering included )
Click to expand...
Click to collapse
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
madj42 said:
So based on the last statement, I'm assuming after doing this I'm not able to flash the stock updates without loosing my root? Just wanted to make sure I understood you correctly. Also the flash_image file. After it's uploaded to the phone I have to run this using a terminal or from a adb shell, correct?
Click to expand...
Click to collapse
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
artcarney said:
Looks interesting to say the least!
Just curious, why no frf83? Is it too new or just not possible?
Click to expand...
Click to collapse
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
jroid said:
you can flash the stock frf72 and don't need to root. just grab an official non-root build, place on sdcard and flash via any recovery u have installed
Click to expand...
Click to collapse
Really? I have been looking for this file for EPE54B for days!
all i have found was FRF50 from EPE27, FRF72 from FRF50, FRF83 from FRF50...
can you please advise us where we could find the one for EPE54B please?
Zapo said:
I was asking myself the same thing. The other thing is, wouldn't we have to flash a new radio too? Coming from 2.1 update1 this is a must afair.
Click to expand...
Click to collapse
i still haven't got a confirmation from anyone that updating radio requires unlocked bootloader....
but i understand everyone's concern as flashing radio is pretty much the only way to brick you phone therefore no one has the guts to be the 1st one flashing Froyo and the new radio with a rooted phone w/o an unlocked bootloader, right?
Rayman0625 said:
No it will not remove the padlock. There is no way to relock the phone as of now.
I really wish this was a week ago..I had gotten a new phone, and decided not to wait to root it.
Click to expand...
Click to collapse
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
kaiser_tytnii said:
can you please advise us where we could find the one for EPE54B please?
Click to expand...
Click to collapse
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
christiankk said:
Have a look here brother: http://forum.xda-developers.com/showthread.php?t=654869
Second thread in this forum.
Click to expand...
Click to collapse
my apologizes, i did not see any Froyo ROM there.
madj42 said:
Let me rephrase my statement above. I have not rooted my phone using the fastboot method. No padlock is shown on the boot screen. I'm asking if after doing this, am I stuck to using the modified builds (one's with root) or can I still use the official builds directly from Google? I'm assuming based on what has been said that if I use the official builds after using this process, that I'll loose the root access. Correct me if I'm wrong.
Thanks in advance. I apologize for being such a newb with all these questions.
Click to expand...
Click to collapse
if you stay with stock recovery and ROM, you will receive OTA from Google.
You can still flash Stock ROM with Custom Recovery but will not be able to install OTA from Google.
hope this help.
Booker-T said:
Sorry about pulling the old post because of some problems.
Here is the latest update, I have modified the root.zip which may solve the flash_image problem.
Let's start!
Have fun to flash great roms from devs.
Hope you can buy me some candies if you do like my work.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3CDK8GTKMZGWJ
Click to expand...
Click to collapse
proud of you Konger!
Is there any way this can work on FRF83?
or
Is there a way to revert back to FRF72?
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
M9x3mos said:
You can revert. Just need to grab the passimg.zip for the phone and flash from bootloader. Good job with tut a little clearer then mine. Didn't check files to see if the same but worked for me. Not reading the memory card was the obstacle which putting card in after detected in recovery was the only way I was able to get it to work.
Click to expand...
Click to collapse
Do you think you could give me a link to the passimg.zip that I can use without having to unlock the bootloader? I've been searching for hours.
PS: there is no busybox in the "Nexus_One_Full_Root.zip" from the original post.
Just a quick advice for everybody.... If someone (like me) is still stuck with the 2.1 Update 1, before update to 2.2 FRF52 test on your phone the point between 2 and 4.b. Once you will have your phone recognized by ADB then you can update to 2.2 FRF52.
For now my 4 microSD (1 * Class 6 Sandisk / 1 * Class 4 Kingston / 1 * Class 6 Transcend and 1 * Class 2 Samsung) doesn't work at all....
Hope this help
Related
This is my first tutorial for installing Cyanogen Mod 7.2.0 on Live With Walkman WT19i. All credit goes to the developers who made all the following and related tools. I simply put together info from various sources. Admins/moderators are welcome to make any changes.
WARNING: Proceed at your own risk! I am not responsible for bricked phones! You might want to do some more research if you're unsure or don't fully understand anything from below
Requirements: ADB drivers:
http://www.mediafire.com/?6u1zl54w3jnvvax
Fastboot drivers:
win_usb.inf file from http://unlockbootloader.sonymobile.com/instructions
Android SDK(unlocking bootloader):
http://developer.android.com/sdk/
Flashtool(flashing kernel):
http://forum.xda-developers.com/showthread.php?t=1351309
Zergrush(for rooting):
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Clockworkmod Recovery(flashing ROM):
http://www.mediafire.com/?73xv18tht0e8zt4
WT19i_4.0.2.A.0.58 firmware:
NOTE:Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
>Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
1) If you're already on official ICS, downgrade to Gingerbread, root Gingerbread and then install other custom ROMs as follows:
2) Flash any Android 2.3.4 firmware (I've tried this method only with the WT19i_4.0.2.A.0.58 firmware though) using Flashtool
->Select Flashmode, Wipe data, Wipe cache
3) Use Zergrush v3 by DoomLord. Works well with 0.58 version
If Superuser app has been installed, rooting is successful.
4) Install ClockWorkMod Recovery 5.0.2.7-nAa-r2(Ported by [email protected])
5) Make a backup in recovery mode. (see below for howto)
6) Install Android SDK Manager
If Google USB Driver is not visible, install Android SDK Tools Rev 20 first, reopen SDK Manager.
Replace android_winusb.inf-file in extras\google\usb_driver folder with the new one on http://unlockbootloader.sonymobile.com/instructions
7) Unlock bootloader officially from: http://unlockbootloader.sonymobile.com/instructions
Instructions on that page are pretty clear.
NOTE: Unlocking the bootloader the official way will void your phone's warranty and DRM keys will be lost. You may want to use the testpoint method as mentioned here:
http://forum.xda-developers.com/showthread.php?t=1285285
8) Download Cyanogenmod 7.2 for WT19i (=coconut version) and place it on your SD card.
9) Ensure that the fastboot drivers are installed.
10) Replace stock kernel : Extract boot.img from the Cyanogenmmod 7.2 ZIP file that you downloaded. Now, in Flashtool, select Flash button > Fastboot mode > Select kernel to Flash > Point it to the boot.img file you extracted. Check log in background window for success.
11) Restart the phone into Recovery. Select Wipe data/factory reset followed by Wipe cache partition followed by Advanced>Wipe Dalvik cache.
Then, install zip from sdcard. Select the coconut 7.2.0. ZIP file you placed here earlier.
Wait for about 5-10 minutes. If you're worried, open Command Prompt, navigate to the fastboot folder and run adb logcat to see what's happening!.
And that's it, you're done!
(If the logging process looks like it's repeating itself for more than 10 minutes, remove battery restart phone, and see if Cyanogenmod now boots up(again, will take ~5 minutes). If it does not still boot(rare case), repeat step 10. Make sure you download the CM ZIP package from your computer)
If you get an 'assert' error (Status 7 error) then, edit the file updater-script in your cm7.2.0 ZIP file\META-INF\com\google\android\. Remove only the first line (ending with a . Now repeat step 10 again.
Extra: To use Google services, you need to flash the gapps.zip similar to the way you did CM 7.2. However, do NOT wipe cache do NOT wipe data or anything! To install, simply boot into recovery, install zip from sd card and choose the gapps ZIP file. Later, Restart phone
How to enter recovery mode on the WT19i:
Turn off phone. Turn it on again. As soon as you see Sony Ericsson logo, keep tapping Volume Down button repeatedly. (Once you are familiar, you'll realize that even 1-2 presses can do the trick)
You do not need to root and install Recovery in the first place, I mean skip steps 3, 4 and 5.
Backup can also be made in the same recovery, which is included with kernel, right before wiping and installing the ROM.
I would just install any Android 2.3.4 firmware, then unlock bootloader, install custom kernel, backup, then wipe, then install.
And if you unlock bootloader officially, then do not forget your phone's warranty will be void and DRM keys lost.
If you succeed with official bootloader unlock, then fastboot drivers are already installed, no need to worry about that
And before ppl go crazy - First boot does take a while, as all the caches need to be recreated.
This tutorial can also work for other custom ROMs aswell, because the process is the same, the only different thing is the kernel and the .zip file.
You do not need to root and install Recovery in the first place, I mean skip steps 3, 4 and 5.
Click to expand...
Click to collapse
Right I meant that to install CWM!
I would just install any Android 2.3.4 firmware, then unlock bootloader, install custom kernel, backup, then wipe, then install.
Click to expand...
Click to collapse
Right except that I had problems with using Zergrush v2 and v4. That's why I thought I'd mention.
If you succeed with official bootloader unlock, then fastboot drivers are already installed, no need to worry about that
Click to expand...
Click to collapse
Yes, but that would entail downloading the android_winusb.inf-file from the mentioned official site, wouldn't it?
And before ppl go crazy - First boot does take a while, as all the caches need to be recreated.
Click to expand...
Click to collapse
Oh, but how common is it for a WT19i to take more than 10 minutes at boot? I did this on two other friends' WT19is; both of them took around 3 minutes. (Obviously i did something wrong the first time on my phone)
Anyhow,thanks for the constructive comments!Editing it accordingly!
blackstallion1234 said:
Right I meant that to install CWM!
Click to expand...
Click to collapse
You do not need CWM in the first place. You can make the full Nandroid backup AFTER flashing custom kernel and BEFORE wiping and installing the ROM.
blackstallion1234 said:
Right except that I had problems with using Zergrush v2 and v4. That's why I thought I'd mention.
Click to expand...
Click to collapse
You don't need root to be honest.
blackstallion1234 said:
Yes, but that would entail downloading the android_winusb.inf-file from the mentioned official site, wouldn't it?
Click to expand...
Click to collapse
What's your point? If you unlock the bootloader official way and it succeeds, you do not have to deal with the drivers anymore, as they have been installed properly and they're working
blackstallion1234 said:
Oh, but how common is it for a WT19i to take more than 10 minutes at boot? I did this on two other friends' WT19is; both of them took around 3 minutes. (Obviously i did something wrong the first time on my phone)
Click to expand...
Click to collapse
I didn't mention about minutes. Some ppl are not aware of that, so it was just a small note for them.
You do not need CWM in the first place. You can make the full Nandroid backup AFTER flashing custom kernel and BEFORE wiping and installing the ROM.
Click to expand...
Click to collapse
Right! The custom kernel would provide a recovery (which isn't present on a stock kernel for our phone), right?
You don't need root to be honest.
Click to expand...
Click to collapse
I shall edit the title to something like 'Root and install CM...' where I express the opinion that rooting does have advantages too!
blackstallion1234 said:
Right! The custom kernel would provide a recovery (which isn't present on a stock kernel for our phone), right?
Click to expand...
Click to collapse
Custom kernels already include recovery and stuff needed for root.
blackstallion1234 said:
I shall edit the title to something like 'Root and install CM...' where I express the opinion that rooting does have advantages too!
Click to expand...
Click to collapse
Rooting is already included in custom ROMs, if not then custom kernel does the job and roots it automatically. You don't need to root it by yourself
didn anyone tried latest nightly
There is a stable rom for LWW listed on the cyanogen mod downloads page. Is it really stable? I'm asking this because when you select 'all' and 'stable' on left panel on that site, there is no stable rom listed for lww! This is very confusing.
hsrbnr said:
There is a stable rom for LWW listed on the cyanogen mod downloads page. Is it really stable? I'm asking this because when you select 'all' and 'stable' on left panel on that site, there is no stable rom listed for lww! This is very confusing.
Click to expand...
Click to collapse
Yes the version of CyanogenMod 7.2.0 listed on their site is stable and indeed the one used in this thread for reference. Click coconut in the left hand pane(that's the codename for LWW) and then selecting stable. (Alternately just go to http://get.cm/?device=coconut&type=stable)
I just installed Cyanogenmod today and it's fantastic!
Do i need to unlock my bootloader?
Hi,
I've rooted my phone (Sony Ericssion Live With Walkman-WT19i) and right now running stock ICS ROM from sony (build: 4.1.B.0.431). Even Clockworld Mod is installed. I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Could You please mail me the steps even to my persoanl mail id [email protected]
sauravsagar said:
Hi,
I've rooted my phone (Sony Ericssion Live With Walkman-WT19i) and right now running stock ICS ROM from sony (build: 4.1.B.0.431). Even Clockworld Mod is installed. I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Could You please mail me the steps even to my persoanl mail id [email protected]
Click to expand...
Click to collapse
You can't install CM with locked bootloader it requires different kernel.
Yes you need to, for CM!
sauravsagar said:
I want to install custom rom from cyanogenmod(or any other custom rom).
My question is : Do i really need to unlock my bootloader,coz as I know rooting may void the warranty but unlocking the bootloader will surely void it.
Click to expand...
Click to collapse
Yes, most custom ROMs need the bootloader to be unlocked(including CyanogenMod). There are two methods to unlock your bootloader - the test point method and the official method. If you're concerned with your warranty(which may already have been voided), use the Test point method described in the FAQ by Someguyfromhell.
And what ^ said.
Please tell me the detailed process of installing custom rom step by step (right after the successful rooting and installing CWM process). I woould be thankful if u include both the process(with and without unlocking bootloader,if any).
Thank You Very Much In Advance.
Click to expand...
Click to collapse
If only people read FAQs on forums...
thanx a million
thanks a million for the tutorial
this thing rocks
i do love this rom
and most nice thing it dose support ad-hoc
wathbiknight said:
thanks a million for the tutorial
this thing rocks
i do love this rom
and most nice thing it dose support ad-hoc
Click to expand...
Click to collapse
Glad it worked for you! Not to be a thanks-whore, but it's just a click away if I really helped ya!
Cheers!
Might be a foolish question but I flashed some custom firmware on my Samsung Star (not Android) back in the days and only had the English language available instead of the Dutch I wanted.
If I root and install the ROM will everything also be available in English only or will I still be able to use Dutch. Will I lose something?
Another question: If I upgrade to ICS official by Sony trough Sony Bridge on my Mac and ICS is installed on my phone, will I lose data and the root and ROM?
Thanks in advance
zeromusx said:
If I root and install the ROM will everything also be available in English only or will I still be able to use Dutch. Will I lose something?
Click to expand...
Click to collapse
That depends on whether the new ROM you're flashing contains a Dutch language pack. Rooting per se will not modify your data or your language. Also note that flashing can erase your internal memory data.(I have no experience with the Star, however I had a Nokia 3500c. Using the official Nokia app, I upgraded my firmware without any data loss. If you will be using the official Samsung app, you should be safe). That said, make it a point to backup your SMSes, contacts, calendars, notes etc.
Another question: If I upgrade to ICS official by Sony trough Sony Bridge on my Mac and ICS is installed on my phone, will I lose data and the root and ROM?
Click to expand...
Click to collapse
Will I lose root? Yes, you will most likely lose existing root permissions if you already are rooted.
Will I lose data? Unlikely, using Sony Bridge.
Will I lose ROM? Of course, that's the reason you're upgrading to ICS in the first place, isn't it?
Have a look at the following resources and any other places you'll stumble across.
http://forum.xda-developers.com/showthread.php?t=1253127,
http://www.techcredo.com/android/android-rom-and-rooting-dictionary-all-the-funny-words-explained
Good luck!
Installed Cyanogen Mod 9 in my Live with walkman. So far So good!
rolo143 said:
I just installed Cyanogenmod today and it's fantastic!
Click to expand...
Click to collapse
Sir can you show us some screenshots?
thanks again
blackstallion1234 said:
Glad it worked for you! Not to be a thanks-whore, but it's just a click away if I really helped ya!
Cheers!
Click to expand...
Click to collapse
my bad
i thought i did click it earlier , but did today
i'll come back for ROM review later
UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
mistral_blue said:
Evening all,
Hoping someone can help me with the following please? Please be as technical as you like, I'm fairly tech-savvy (I have CFW on my PSP, I build my own computers and have flashed/cfw various devices in the past) if I don't understand I can google it, but I need to know WHAT to google first and I'm a bit lost...! :good:
I have stock TF201 which is getting pretty painful despite a recent re-install. I've noticed that there is still no real idea as to if/when KitKat will be rolled out for it and was rather p!ssed off to see my missus's Nexus 7 (2012 version!) get 4.4.3 today!
I've done a lot of googling and forum reading but I'm a little confused as to the best route to go...
Having come across the "one-click method to root" using motochopper (and/or other methods) would it then be possible to install 4.4.2 for example using CM11 and a guide such as this (google "Install Android 4.4.2 KitKat on Asus Transformer Prime TF201" as I can't post URLs) - or will this only work for OFW release like 4.2?
In summary, am I missing the point (I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Long and short is I'm not after doing anything crazy other than getting my TF201 to the latest STABLE(ish) version of Android. I understand the risks of bricking, CFW/OFW & OTA etc. I guess I'm basically after a simple list of steps (or pointing at the relevant thread) to achieve this - from the guides I've seen I have to unlock, root and then go down the CM11 route but I want to know if I can get there more easily/safely using one-click root or another method for example?
All advice gratefully received!
Mark
Click to expand...
Click to collapse
Man your asking for alot
Shoot me a PM lets see if we can point you in the right direction.....
Thx Josh
mistral_blue said:
(I get the feeling I may need to be unlocked as well to have a custom recovery?), THEN root etc...
Click to expand...
Click to collapse
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Thanks for the quick replies gents... Restorer, I'll read up on the methods you suggest (thanks for the detailed list with links, exactly what I was after) and then Josh I'll be in touch to check I've not missed anything before I start following the Yellow BRICK road:laugh:
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
tim2min said:
Restorer thanks for the instructions...like the title I am about to take the "plunge" and flash this Prime and I want to got to KK. Just one thing.. below you state: "4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/show....php?t=2773812. " but when I go to the link it says that I must be on Hairybean and the bootloader 4.2.1. I am currently on the stock 10.4.2.18 and downloaded the unlock v6 .apk file from Asus to do the bootloader "unlocking" Just for the sake of clarity...I am new to this...should I still unlock using the Asus util and once done then do the Hairybean update? which will in turn upgrade the bootloader (10.6.1.27.1)?
Tim
Click to expand...
Click to collapse
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Taking The Plunge!
Restorer said:
Yep, that's the only route to custom ROM and vital you make NVFlash backups:
1. Unlock device using the official tool from Asus website - its says "for ICS" but works fine on JB.
2. Assuming you are on the latest official stock JellyBean (Asus v 10.4.2.18) then go get the latest TWRP 2.6 for TF201 JB from the bottom of this page: http://techerrata.com/browse/twrp2/tf201 Flash that blob using fastboot following the instructions in the section titled "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)" on this page: http://teamw.in/project/twrp2/93.
3. Follow the instructions in the tutorial here for making NVFlash backups: http://matthill.eu/android/transform...ybean-nvflash/
4. You are now ready flash a custom ROM of your choice. If you really want to go straight to KK then my advice would be to look no further than CROMBi-kk: http://forum.xda-developers.com/showthread.php?t=2773812. You will get plenty of help here from people who know about the tf201. Read the whole thread but pay particular attention to post #4 where Josh has written a step by step guide for people starting from scratch.
Finally, though you are pretty safe now with your NVFlash backups and even though you are well experiences at flashing, follow all the instructions to the letter and avoid the sadly well tested routes to brick. I don't believe there is another android device in current use that is so easy to brick as the prime.
1. Use only TWRP recoveries. Steer completely clear of CWM and ROM Manager. They never did produce an official recovery for JB on the prime and installing the last one from their site onto the JB bootloader will most certainly land you with a brick. The flatline process leaves behind its own version of CWM but has been made compatible. However, you probably won't be able to see your external SD card with it and it is based on a clunky non-touch version so best advice would be to ditch it straight away for TWRP 2.6 even though you will be upgrading that shortly anyway,
2. Always check you are flashing the correct version of TWRP for your current bootloader and ROM
3. Never, ever press that Wipe Data button on the fastboot screen - that too will kill your tablet.
Oh, and have fun!
EDIT: just seen Josh has offered to hold your hand - don't let go and you'll be fine
Click to expand...
Click to collapse
Restorer said:
Yes, you can't flash anything until the device is unlocked and you have installed a TWRP recovery.
But make sure to then make your NVFlash backups and once you have those files safely stored go straight on to follow Josh's step-by-step guide for in post #4 of the ROM thread. His guide was written specifically for TF201 people coming from stock. Follow it to the letter but be sure to ask if there is something you don't understand.
Good Luck!
Click to expand...
Click to collapse
Sorry just one more question, since I have a TF201 and and want to use this ROM, it seems I am essentially turning my Prime into aTF300, which is ok, now right after unlocking the boot loader and then running TWRP (2.7 TF300) it is at this point I flash the hairybean update or do the creation & backing up for NVFlash first then the hairybean?...sorry for the elemental question...just want to be sure!
Tim
tim2min said:
now right after unlocking the boot loader and then running TWRP (2.7 TF300)
Click to expand...
Click to collapse
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Taking The Plunge!
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Taking The Plunge!
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Why rename the the .img file to a .blob file ?
Not really the best thing you could do .....
Just boot to fastboot and run the command
Code:
fastboot flash recovery flatline_tf201.img
The blue bar will show up and fill on the write part of the command ...
Once that is done do this command .....
Code:
fastboot reboot-bootloader
Let the tablet reboot into bootloader and VOL up on RCK
Now your golden ......
Make sure you understand what need to be done in flatline ...
Thx Josh
tim2min said:
Hey restorer this can all be done on a non-root device correct? Should root first if so what is the best way you suggest ...read a little something about motochopper.?
Click to expand...
Click to collapse
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
tim2min said:
Have a possible issue when trying to after renaming the original file flat_tf201 (image file) to twrp.blob it looks like on the windows 7 side it sent it fine but on the tablet I did not see the "blue bar". So worried it did not send I tried it again and got the "error cannot open twrp.blob" when I did a dir of the fastboot directory it is there but noticed is the command prompt after renaming (per instructions from TWRP) the full file name was twrp.blob.img should not matter but renamed it (from command prompt) w/o the .img extension still would not send.
I am thinking eventhough it initially looked like it did send (based on output in command prompt initially) is it possible I missed the blue bar on the tablet?... Should I have seen it? Does it take awhile?
The tablet shows "starting Fastboot USB download protocol"
any help what be appreciated
Click to expand...
Click to collapse
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Restorer said:
No need to root first - the custom ROM you will be installing will be rooted.
---------- Post added at 08:09 AM ---------- Previous post was at 07:59 AM ----------
Sounds like you have downloaded (and renamed) the .img file and not the .blob file! "openrecovery-twrp-2.6.3.0-tf201-JB.blob" is the one you want if you are follwoing the instructions on the TWRP page I linked you too. The blob file Josh refers to is the one in this zip file and has a shorter name. You can either use Josh's instructions or TWRP's but not a mixture of the two
@lj50036 I think he referring to the instructions from TWRP on the downloads page which say to rename the file to a shorter form.
@tim2min don't let this renaming stuff confuse you - TWRP are only suggesting it because their full names are so long and prone to error when you are typing them out!
EDIT: Sorry, I hadn't realised Josh had already prepared and renamed the files for you. Just use all 3 of his files contained in his zip and not from my links or you may get further confused.
Click to expand...
Click to collapse
Does no one use auto-complete any more ......
Thx Josh
lj50036 said:
Does no one use auto-complete any more ......
Thx Josh
Click to expand...
Click to collapse
Haha, yes. Why do command windows have to be so primitive .
Restorer said:
No you're not a TF300 yet! Unlock then flash the latest TWRP version for TF201 from the page I linked to (still 2.6). Then do your NVFlash backups. Then you can pick up Josh's guide again where you flash "Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip". It's just the guide assumes you already have your backups .
Click to expand...
Click to collapse
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
lj50036 said:
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Click to expand...
Click to collapse
Thx Josh
Taking The Plunge!
lj50036 said:
How is this saying anything about wiping from bootloader ?
I am sure it say NOW ENTER RECOVERY ....
But maybe I missed something or maybe you did ....
Thx Josh
Click to expand...
Click to collapse
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
tim2min said:
Man it was going so well until my computer could no longer see my tablet via USB! so I can now longer use FASTBOOT because the device is not found. This happen right after flashing Hariybean and I was about to run"
Interesting my Win7 computer says that it sees the Asus device:but fastboot does not see it. Also initially the it saw it as an APX device but no longer so I can not do the next step which is to adb reboot-bootloader and then do flash @ne0zone75 TWRP recovery per the instuctions. I have tried re-pointing to the Universal Naked drivers trying to select a diffrent drvier but to no avail. looks like the tablet can no longer communicate to the computer. I will copy the contents of the fastboot directory to another computer and see if that will work
any ideas?
Tim
Click to expand...
Click to collapse
Sounds like another windows driver issue .....
I really cant help much here as I dont use windows ...
But there is a short term solution at least to get you booted up ....
@ne0zone75's flashable zip twrp
Download this and move it into your folder that contains the fastboot.exe ... Then rename it to twrp.zip
Then boot into the recovery and run this command from CMD window
Code:
adb push twrp.zip /sdcard
Let that happen should not take long, find the zip file under install and flash it .....
YOU MUST DO A REBOOT AFTER THIS NOT JUST A REBOOT INTO BOOTLOADER ...
So lets run this command ....
Code:
adb reboot
Let it fully boot into a bootloop then with the buttons get back to the bootloader screen and enter RCK ...
then once you have done that continue on your way ....
Let me know this works for you ....
Thx Josh
tim2min said:
Just an observation Restorer I note that you said never to select "Wipe Data" in the boot menu but in Josh step by step he suggested to do that which can take a while. In this case it ok to do it since we are putting on a new ROM. I have my backups (blob files) as well as the NVFlash file
Tim
Click to expand...
Click to collapse
Josh has answered you. But this is another fine example of why people here keep banging on about reading things carefully and then following instructions to the letter .
Taking the Plunge
Well, after some "trying" moments I got this ROM on the Prime!...must say extremely excited seems like my TF201 has more than just a "heartbeat" left in her, shoot she may be able to run hard a little longer!. I must admit some EXTREME anxiety occured and I really got scared when after flashing hairybean/bootloader my computer could not find/see my tablet AT ALL!!. This lost of connection was madddding especially when Windows would add the tablet in device manager and you would hear the computer chime every time I connected/disconnect the USB cable from the computer while the other end was in the tablet. I had to fuss around with Android APD Interface/Android APX drivers until my computer settled on one that actually worked after running c:\fastboot>fastboot devices 50x's and if finally saw my tablet I literally shedded a tear, this is definetely not for the faint of heart...lol Needless to say I hurried up and finished going down the instructions just for fear my computer might "inexplicably " loose connection again!....lol
Many thanks to Restorer for chiming in with my question also Josh (especially for the step by step instructions) also to the whole team that made this ROM!
Just a question though: If you wanted to change the color theme on boot up (which now shows in blue "CROMBi-KK") how would I go about that?
Tim
Ladies and gentlemen, I would like to present to you all a formal guide to venture into one of the best smartphones in the market, the underdog to the other mass marketers, the Sony Xperia Z3v for Verizon!
*Please note I am not responsible for any bricking, destruction of your device, alien invasions, or any other problems. It is up to the user's choice to seek out what is done on your device on your own terms.*
This is the method I would recommend that's much quicker and efficient is Kingroot. I know there were some previous controversy about what could be behind Kingroot, but from what I will show here is using Kingroot as leverage to gain access quickly into my prerooted Lollipop firmware that can stand alone after removing Kingroot afterwards.
1. Have the Z3v in your possession.
2. Google "Kingroot" and download for Android and run the rooting process there.
3. Download "Superuser" from the Play Store to have the binary to run root fully. (Optional just in case the next step doesn't work)
4. Install XZDualRecovery (grab the flashinstaller for the Xperia Z3) to install TWRP from here: http://nut.xperia-files.com/path/XZ...40vagg0tpcrnm1vlnt63je5&randomizer=_ehkq575vz
(The link is subject to change, so if that happens, navigate through here: http://nut.xperia-files.com/)
5. Download my new 5.1.1 prerooted Lollipop zip from my thread here: http://forum.xda-developers.com/z3/...08-prerooted-lollipop-5-1-1-23-4-b-0-t3338967
6. Access TWRP by opening an app called NDR Utils in your App Drawer
7. Flash my zip through the install button and now you'll be on the latest prerooted stock build of Lollipop with a few mods.
Optional Step 8. Uninstall any traces of Kingroot from your phone and you're good to go. This step may already be done for you after you flash the prerooted because reportedly there were already no traces left behind. Enjoy!
Thanks to the following people:
@zxz0O0, for achieving root for our Z3v
@jal3223, for helping me as much as you can to guide me through myself
@[NUT], for the custom recovery to install onto our Xperia devices
Please hit thanks for the all in one guide to freedom!
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Mountainfisher said:
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Click to expand...
Click to collapse
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
GigaSPX said:
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
Click to expand...
Click to collapse
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Oh No, I vowed to stop messing with my phones....
jal3223 said:
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Click to expand...
Click to collapse
Personally, I'm fine without doing custom ROMs. I like how Sony's UI works as it is and I prefer it that way than going full AOSP like any other Nexus phone. I just like to buy what came with the package as is intended.
Bobby Buggs said:
Oh No, I vowed to stop messing with my phones....
Click to expand...
Click to collapse
This is well worth to do. I installed Xposed, and unlocked some awesome stuff. Such as using Superior Auto mode with 15 mp right off the start or 20.7 MP. Greater the details, amazing functions made.
Oh and also, I will now proceed to upload the flashable zip of the latest FW being prerooted. Just so there's some better things to deal with.
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Mountainfisher said:
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Click to expand...
Click to collapse
This guy said it took him 10 times so I am going to keep trying till it works!
sthrnsprtsmn said:
I was getting the same errors. I had to factory reset the phone multiple times and redo the steps. On about the 10th time, it took. I skipped the phone set up steps, and kept a root checker apk on my sd card to speed it up. Also, I unchecked the verify apps over USB. I didn't see that mentioned anywhere.
Time to send my donation. Thank you very much @zxz0O0
Click to expand...
Click to collapse
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
JediDru said:
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
Click to expand...
Click to collapse
Your C:/flashtool/firmware folder should be empty. Place the firmware you want to use in /USERNAME/.flashtool/firmware
make sure you uninstall all java and re install fresh!! that was what was holding me up
Someone should do a youtube of this process live
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Bobby Buggs said:
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Click to expand...
Click to collapse
You completely skipped steps 1 and 2 because you're on the latest build. Step 6 is following the instructions that are listed within the exploit.bat.
You won't be reflashing the latest until you've followed through to the new list of steps that occurs after 9.
Giga, sent you a Pm
---------- Post added at 09:31 AM ---------- Previous post was at 09:20 AM ----------
Call me a idiot but I dont see any instructions, I ran the exploit file and my screen shows daemon started successfully but nothing else
ROOT Z3V
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Great write up!
Thanks for the time and effort you put on rooting our abandoned Z3v.
Really look forward to flashing the Pre-rooted firmware that you're about to made
xratablancax said:
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
Click to expand...
Click to collapse
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
What line of code
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
If you look at the link I provided, that gives your a different set of root files, one that the Exploit runs and right after root runs automatically.
VERY IMPORTANT... YOU NEED TO FLASH YOUR DEVICE TO STOCK ROM, YOUR DEVICE NEEDS TO BE IN ROM, 23.0.E.0.376, BACKUP DEVICE, FLASH THEN ROOT THEN OTA UPDATE
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Use TWRP
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
You can flash twrp to root, then install superusersu. There's a zip file that's been posted in the forums recently by ArkAngel 06 that has everything you should need and a step by step guide to do it. Hope this helps
This question has been asked and answered. Do you guys read the other threads at all?
To get root and TWRP.
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks
Thank you both for your help! I saw this posted in the other threads but there's been a lot of activity since the release of 5.1 and it was all getting confusing
to get su 2.49 .zip do a Google search u will find it after twrp just flash su 2.49.zip and ur all set .
I tried n its working fine
Would be best at this time to not flash twrp. Instead fastboot boot twrp.img then install the beta.SuperSU v2.49.
Sent from my MT2L03 using XDA Free mobile app
Re-rooting your LOLLIPOP HAM2
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
If your Bootloader is still unlocked, skip to step 5
UNLOCKING YOUR BOOTLOADER
1) Request your 16 digit Bootloader Unlock Code from [email protected] (you'll need to give them your phone's IMEI and SERIAL numbers)
2) Download the HW-QmOneKeyTool to your PC from here: http://www.mediafire.com/download/um5sqbwp094r2x4/HW-QmOneKeyTool.rar
3) Connect your phone to your PC, open the HW-QmOneKeyTool and enter your 16 digit unlock code into the text box in the first tab of that tool, then click 'ROOT' {This button should actually read 'UNLOCK'}
4) Now that your phone's Bootloader is unlocked, flash TWRP as follows:
INSTALLING TWRP
4a) Download TWRP Recovery from the following site: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
4b) Rename TWRP_MT2-L03_RECOVERY.img to TWRP.img
4c) Move TWRP.img to hard drive C, folder: adb
4d) Connect you phone to your PC, open Command Prompt and type: cd C:\adb
4e) After the adb prompt, type: adb devices
4f) With your device serial showing in the Command Prompt, type: fastboot flash recovery c:\adb\TWRP.img
4g) The Command Prompt should now say "waiting for device"
4h) Unplug your phone and reboot into bootloader (power + volume down)
4i) Once in the bootloader make sure it says unlocked then plug your phone in.
4j) The command prompt should say done after 2 seconds and your phone will stay the same.
4k) Unplug your phone and reboot.
INSTALLING SUPERUSER
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Is there a backup of the mt02 emui 3.1 boot loader before I go to the twrp?
omnithesis said:
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Click to expand...
Click to collapse
Step 7 is required if you don't have an SD card issue?
For anyone that knows, if you root your device, will this cause issues getting OTA updates from Huawei? I registered my IMEI after converting to OEM and loading Lollipop so I would like to ensure I get these updates and can install without issue.
No one?
No
Moody66 said:
No
Click to expand...
Click to collapse
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
What phone because only a few phones are rooted on lollipop and they have to have unlocked bootloaders.
Sent from my SM-N910V using XDA Free mobile app
TheIgster said:
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
Click to expand...
Click to collapse
The question was did root affect OTA. The answer is NO. What more do you want.
Moody66 said:
The question was did root affect OTA. The answer is NO. What more do you want.
Click to expand...
Click to collapse
Well, your simple one worded response was misinterpreted. How about that...
And yes, it does effect OTA. I just received B20 and it clearly said to make sure your phone was NOT rooted before upgrading, so obviously it causes an issue with the OTA updates.
Root does not affect OTA. Only if you change system files. Stock recovery and stock system files will not. At worst you will loose root and have to reroot.
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
does root affect OTA....type that into Google. Thousands of posts will tell you the same thing.
Was simply reporting what the update to B20 said. It stated ensure your device is NOT rooted before updating. Perhaps it is just them being careful and ensuring that bugs that may appear on a rooted device would be tougher to diagnose.
Personally I don't see a big need for root with no ROM's available for the HAM.
Because you can't make some changes without root. LCD etc.
Moody66 said:
Because you can't make some changes without root. LCD etc.
Click to expand...
Click to collapse
Yeah, that's true, but to date, I have been pretty happy with the HAM stock. The LP update made this phone a whole new phone. The UI is very nice for an older phone with older specs. Coming from and LG G3 (yes, some would think the HAM is a downgrade), I love the HAM over the G3. The colors are amazing, the screen size is awesome and the new UI for LP is way better than stock LG.
Have a look at a G4. Shame they are expensive
Worth it. But expensive.