Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
WARNING - If it works on your device, be careful, as with an unlocked bootloader you can brick you tab faster than you can imagine.
How to:
0. It has been tested on the A100 ICS firmware. This bootloader doesn't work with HC firmware.
1. The tablet should be already rooted and charged more than on 30 %. Сonnect the tablet to the computer and power on.
2. Download this archive. Unpack it to any place.
3. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator
Code:
install-eng.bat
for Linux with the rights of root
Code:
bash ./btl-a200.sh
4. Wait. The tab will show a screen with two icons. One for lock and on for unlock. I used the volume down to highlight the one I wanted and the volume up select it.
Then you have to reboot, using, for example, this command:
Code:
sudo fastboot reboot-bootloader
And you'll get the message on the screen when it comes up in fastboot mode.
Code:
"Bootloader v0.03.06-ICS(UnlockMode): Starting Fastboot USB download protocol"
It's unlocked and available for fastboot flashing, etc.
---
For return original bootloader:
for Linux with the rights of root
Code:
bash ./btl-a100.sh
PS: After unlocking bootloader there is a noncritical distortions of the picture at a stage of initial loading.
THX THX THX !!! to them and to you
yehhhhhhh !!
God exist !!
Enormous THX.
now waiting for Recovery & Custo_ROM !! ynak ynak ynak
Hi there,
First off, great work. Just tested this on a100, once I re-read your post and I ran the a200 named script first it worked fine, I assume this is method shoehorns the a200 bootloaded into our a100s?
Excellent work, this means a lot!!
oh nice! I assume, if you could use the a500 patched bootloader as well, yes? That one is actually the same version as the A100 ics bootloader.
Thanks for the script.
ZeroNull said:
Original article is published on this site and created by ZeroNull and vdsirotkin (4pda.ru).
WARNING - If it works on your device, be careful, as with an unlocked bootloader you can brick you tab faster than you can imagine.
How to:
0. It has been tested on the A100 ICS firmware.
1. The tablet should be already rooted and charged more than on 30 %. Сonnect the tablet to the computer and power on.
2. Download this archive. Unpack it to any place.
3. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator
Code:
install-eng.bat
for Linux with the rights of root
Code:
bash ./btl-a200.sh
4. Wait. The tab will show a screen with two icons. One for lock and on for unlock. I used the volume down to highlight the one I wanted and the volume up select it.
Then you have to reboot, using, for example, this command:
Code:
sudo fastboot reboot-bootloader
And you'll get the message on the screen when it comes up in fastboot mode.
Code:
"Bootloader v0.03.06-ICS(UnlockMode): Starting Fastboot USB download protocol"
It's unlocked and available for fastboot flashing, etc.
---
For return original bootloader:
for Linux with the rights of root
Code:
bash ./btl-a100.sh
PS: After unlocking bootloader there is a noncritical distortions of the picture at a stage of initial loading.
Click to expand...
Click to collapse
many thanks zero, its certainly been a long quest....superb work! also thanks @vdsirotkin, you guys rock!
Euclid's Brother said:
oh nice! I assume, if you could use the a500 patched bootloader as well, yes? That one is actually the same version as the A100 ics bootloader.
Thanks for the script.
Click to expand...
Click to collapse
No A500. A200 Bootloader.
ZeroNull said:
No A500. A200 Bootloader.
Click to expand...
Click to collapse
I thought as much, hearing that the A200 bootloader is unlockable. Any word on a custom recovery? Perhaps we could roll our own Clockwork?
ZeroNull said:
No A500. A200 Bootloader.
Click to expand...
Click to collapse
hey zeronull, have you already tried the cwm for the a200? if not it will possibly work...i will look into it if i get time tonight. thanks again friend!
oneovakindoldys2 said:
hey zeronull, have you already tried the cwm for the a200? if not it will possibly work...i will look into it if i get time tonight. thanks again friend!
Click to expand...
Click to collapse
Would you be looking into CWM 5.5 or 5.8 (touch version)? I ask because after using it on my Atrix, I think the latest version is far better than the old volume rocker navigation.
Awesome
Sent from my SPH-D710 using Tapatalk
littleemp said:
Would you be looking into CWM 5.5 or 5.8 (touch version)? I ask because after using it on my Atrix, I think the latest version is far better than the old volume rocker navigation.
Click to expand...
Click to collapse
CWM Touch on my Nexus rocks, wish it would display scripts a bit better though, but other than that it's niiiice
Awesome news.. official ICS soon and an unlocked bootloader. I've been so on the fence with my Iconia tab.. ICS leak made it better but now....
BRING ON THE ROMS!
BrockVegas said:
Awesome news.. official ICS soon and an unlocked bootloader. I've been so on the fence with my Iconia tab.. ICS leak made it better but now....
BRING ON THE ROMS!
Click to expand...
Click to collapse
First Clockwork & Nandroid, then bring on the ROMS.
tomlogan1 said:
First Clockwork & Nandroid, then bring on the ROMS.
Click to expand...
Click to collapse
Nandroid will come with CWM .
So stoked!!! Looking forward to some real progress on this little gem of a tablet!
Not working
got this mid script
-
Execute scripts
/system/bin/sh: su: not found
-
-
Rebooting
_
_
I never saw the two icons? I am rooted and SU works, strange?
---------- Post added at 11:17 PM ---------- Previous post was at 11:17 PM ----------
Love CM9 on the Atrix, now to have it on my A100, awesome.
You need to let the script finish and reboot the machine....you didn't let it run long enough it seems. good luck!
I let it run
for half an hour, no dice.
saw the cwm recovery installer thread too. just need to get past this unlock. the bat says completed, just reboots my a100 into a download mode, then nothing
open a command prompt after the script is finished if you are on linux type sudo fastboot oem unlock and windows just type fastboot oem-unlock see what it says.
found issue
I dont have SU
I have superuser installed, not sure why su is not there.
suggestions?
C:\fbr>adb shell
[email protected]:/ $ su -c 'sh /mnt/sdcard/wrtbtla200.sh'
su -c 'sh /mnt/sdcard/wrtbtla200.sh'
/system/bin/sh: su: not found
127|[email protected]:/ $
Related
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.
I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App
renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.
you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.
Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.
fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.
Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?
it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file
fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?
There is now a MUCH easier way to root ALL Sony Ericsson 2011 phones including the Xperia Pro, making these instructions obsolete. Please see DooMLorD's thread here: http://forum.xda-developers.com/showthread.php?t=1319653
Remember to say thanks to DooMLorD for his awesome work!
However, I'll sill keep the 2 sets of instructions here in case anyone needs them or wants to refer back to them. My ZIPs do have all the drivers needed with good instructions on how to install them after all
My original instructions based on alvaroag's work can be found below, and the instructions via my instructions the Xperia Pro CWM Recovery method can be found on post 50 of this thread.
It's important to note that DooMLorD's tool only works for Windows. You can still use our original method in this post if you're running Linux.
We finally have a method to root the Xperia Pro MK16a (and PROBABLY MK16i) thanks to XDA Member alvaroag!!
This is his method, with the instructions modified by myself for ease of use.
What you need before you begin:
1. A rock hard stomach, because should the very unlikely happen and this brick/damage your phone in some way, I’m not responsible
2. An Unlocked Bootloader
NOTE: Sony offers a totally free, official, and simple method to unlock your bootloader here: http://unlockbootloader.sonyericsson.com/
Should that not work for you, your phone is probably SIM locked from your carrier (FIDO for example does that). You'll need to get the bootloader unlocked remotely from someone who has SETool and the appropriate security USB dongle. THIS COSTS MONEY, as SETool requires that user to pay per use.
Please see this thread for further instructions as it's the method I used personally: http://forum.xda-developers.com/showthread.php?t=1232050
Alejandrissimo was awesome at helping me through it.
3. On the phone itself navigate to the following locations:
a. Settings - applications – Make sure Unknown Sources (first option) is checked
b. Settings – applications – development – Make sure USB Debugging is checked
4. Download this archive. It contains all the files and drivers you will need:
http://www.mediafire.com/?7cz7672da9cxkrd
Instructions:
1. Extract the archive you downloaded to a folder on your computer. Where doesn’t matter as long as you remember where it is.
2. Navigate to the folder ADB For Dummies (thanks to VanillaTbone for his guide) and install ADB for Dummies.exe
a. This will create a new folder on your C: drive called “android-sdk-windows”
3. Take the file “xperia_pro_root.zip” from the archive you downloaded and extract the contents to C:\android-sdk-windows\platform-tools\
4. Power off the phone and make sure it’s not plugged into anything.
5. Hold down the MENU button and connect the USB cable. A blue light will appear. If a blue light does NOT appear, then your phone can't get into FastBoot, and probably still has the bootloader locked.
a. If Windows asks you to install the drivers, install the driver from the folder “Fastboot Driver” in the archive you downloaded. Should those drivers not work, try the drivers found in "C:\android-sdk-windows\google-usb_driver"
6. Open the “Fastboot” folder in windows explorer (its part of the archive you extracted in step 1. Hold down the shift key and right click on an empty space in the folder window, select Open Command Prompt Here.
7. Type:
fastboot boot recoveryNEO.img
8. The blue light on the phone will turn off, the screen on the phone will be blank, and the phone will be disconnected from windows, but after a few seconds you will get a Mass Storage & ADB Interface Detected. Note that the phone’s screen will continue to be black for the rest of this process. THIS IS NORMAL, your phone has not been bricked. If you need to stop anywhere along the way, simply unplug the phone from the computer and take your battery out. The phone will return to normal operations, though UNROOTED.
a. Windows will PROBABLY say hardware failed to install. This is fine.
i. Open the start menu, right click on “Computer” and select “Manage”
ii. Select Device Manager on the left side of the Computer Management window that opens.
iii. Look for the unknown piece of hardware. Right click on it and select update/install driver.
iv. Browse your computer, and select the main folder you extracted the archive to way back in step 1 – the drivers are somewhere in there, don’t worry about where, as windows will find them just fine.
9. On your computer navigate to “C:\android-sdk-windows\platform-tools”. Hold down the shift button on your keyboard and Right click on an empty part of the windows, and select “Open Command Window Here”
10. Type "adb shell". If it says "device not found", disconnect the USB cable, remove the battery, and try again from step 6. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
Now you’ll have to run a bunch of commands inside the ADB Shell window (the one with the black background and looks like a DOS window). You can just copy and paste each one from here. Be sure that once you start this step, you continue until the end of these instructions.
mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system
If it says “/system is not empty” then type:
"rmdir /system/bin" and then run the first mount command again
type "exit"
11. From the DOS window, Run these commands (again copy and paste each one is fine)
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell
12. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot
13. The adb shell will terminate. Disconnect the phone from the USB cable, wait for about 15 sec, remove the battery, and then turn it on.
14. From the phone, Open the Market, search for "Busybox" by "Stephen (Stericson)". Install that
15. From the Market, go to My Apps, search for "Superuser" by "ChainsDD" and make sure you're running the latest edition
16. Run the App "Superuser" from your app tray.
- under the settings tab, scroll to the bottom and click SU Binary "tap to check for updates"
17. Run the "Busybox Installer" app. Follow the onscreen instructions - just leave everything at default.
Congratulations! Your device should now be rooted! I personally suggest downloading and installing Titanium Backup to make sure - it will run a root check on startup and notify you if anything is wrong.
Notes:
This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution. - alvaroagThanks to VanillaTbone of XDA Developers for his awesome ADB For Dummies guide and app.
http://forum.xda-developers.com/showthread.php?t=502010
And of course thanks to Bin4ry for his NEO recovery image.
And thanks to all the other contributors to this thread for their help, advice, and overall contribution.
And if this thread helped you in some way, Please click THANK YOU to show your appreciation
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rcummings100 said:
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk
Edit; ............
Sent from my LT15i using XDA App
taaviu said:
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess
XperienceD said:
There is a Mini Pro forum. ;-)
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Totally different phone
This is just the "Xperia Pro" - it was released in August. It's the same phone as the Neo, but with a slide out QWERTY keyboard. Model is MK16a (or MK16i for the international one)
Gingerbreak??
Sent from my MT15i using Tapatalk
Alejandrissimo said:
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess
Click to expand...
Click to collapse
How to do it? Generate prerooted system.img
Thanks!
Sent from my MT15i using Tapatalk
I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards
Bin4ry said:
I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards
Click to expand...
Click to collapse
That was the first thing I tried, since the Pro should just be a Neo with a keyboard. Unfortunately it doesn't work.
Here's the output:
C:\root-play>fastboot boot recoveryNEO.img
downloading 'boot.img'...
(bootloader) USB download speed was 9336kB/s
OKAY [ 0.517s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.002s]
finished. total time: 0.519s
The phone is clearly still turned on, but no longer in fastboot mode, and the screen is totally blank, though the backlight is active.
I've tried the same thing with the Arc and Play recovery images and had the same results.
What do you mean by the keys are mapped wrong?
Is this what you're talking about?
http://www.knowyourcell.com/sony-er..._hard_reset_the_sony_ericsson_xperia_pro.html
The instructions on how to get into Recovery on that site are very similar to how to do it on the stock build of my previous phone, the Motorola Milestone. Unfortunately THEY DON'T WORK
I've tried substituting the volume down button with other keys, but with no success. Pretty difficult to guess the right key combination when there's a full qwerty keyboard on here
Is there a way to boot into the standard recovery from ADB or fastboot or something? Possibly from an on-board terminal emulator? A command like "Reboot Recovery" perhaps? Or is that too easy to be possible...
It's ironic that my old Motorola milestone with a totally locked down bootloader proved easier to hack than this phone with it's wide open bootloader
Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards
Bin4ry said:
Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards
Click to expand...
Click to collapse
Nope, adb shell doesn't work. Shows "error: device not found"
But because I'm new to this (I came from a motorola milestone), I want to make sure I did what you actually asked of me:
- I turned on the phone into fastboot mode (hold down menu, plug in usb cable, get blue light)
- from a command prompt window: fastboot boot recoveryARC.img
(replacing ARC with NEO and PLAY depending on the image I'm trying)
- phone now boots into black screen, no blue light, screen backlight is on
- unplug from computer, plug back in
- from command prompt: adb shell
Are those the instructions you wanted me to follow?
Fastboot works fine. Can I do anything from there? Getvar for example, or something? can I run the command Update and flash the RootXperia.zip file? Or will that not work because it's not signed properly or something similar?
Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards
Bin4ry said:
Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
Click to expand...
Click to collapse
I figured as much. Just hoped I might be wrong.
Bin4ry said:
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards
Click to expand...
Click to collapse
Can anyone give me instructions or pointers on how I extract the kernel.sin from my firmware?
Thanks for your continued patience with me. I really do appreciate it.
Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium
datagubben said:
Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
It's because they're all so similar, and are based on the same hardware as the Arc.
Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards
Bin4ry said:
Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards
Click to expand...
Click to collapse
Unfortunately the very first thing I did with the phone was unlock the bootloader. 'Fido' is the only phone company selling the phone, but I'm with 'Rogers'...so I needed to unlock the bootloader in order to actually use the phone as a phone, which was and remains the most important thing to me.
That being said, I'll see if Alejandrissimo can give me a hand with re-locking the bootloader, then I can get the firmware as you instructed, then have him re-unlock the bootloader. I'll just stick my SIM Card back in my old motorola milestone while we work on this so I can still have a working phone.
You're awesome Bin4ry for helping like this
Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.
ratius said:
Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.
Click to expand...
Click to collapse
If you could, that'd be great. I don't especially want to lock my bootloader over again since you have to use SETool to unlock it, which costs money each time you use it (essentially). Not to mention it involves some acrobatics with a paperclip to connect a testpoint inside the phone to a ground!
Unless there's an easier way to lock/unlock now that I've done it once that is...if so, I'm happy to do it.
As for accessing the files Bin4ry is talking about, boot to windows if you can and do it that way. Just follow his instructions to repair your firmware, then go to that folder in windows (it's located in C:\Program Files (x86)\Sony Ericsson\Sony Ericsson PC Companion). At least, that's my understanding.
Hi. Yesterday, I bought a Xperia Pro. Ive spent most of the afternoon and the nigh trying to root it, and I've finally got how to do it. It's a manual method, as there is not an automated one.
There's no need to say I'm not responsible for any damaged or bricked devices(but mine is working ok )
What you need:
1. The Xperia Neo Recovery, by Bin4ry, get it here
2. xperia_pro_root.zip I'm attaching. It contains the files from RootXperia.zip, but without the update.zip-related files, as they are not needed.
3. The Android SDK, with the Google USB Drivers Package.
4. If you've never used your device in fastboot mode, you may also need to follow steps 7 & 8 from SE bootloader unlocking tutorial.
5. [NOT REALLY SURE] Application Debugging & Unknown Sources enabled.
6. [NOT REALLY SURE] Unlocked Bootloader. This is because mine is unlocked, but I don't really know if that is required to boot the recovery image via fastboot.
I'm assuming that you are working on a Windows/Unix terminal, with a working directory where you have recoveryNeo.img, Superuser.apk and su /these two from the zip file I attach), and that fastboot & adb are on the PATH. If some file is not on the working directory, or fastboot/adb are not on the path, use full paths.
Instructions:
1. Disconnect & Power off the phone.
2. Hold down the menu button and connect the USB cable.
(If Windows asks you to install the drivers, install the driver from ANDROIDSDK\extras\google\usb_driver folder).
3. Run "fastboot boot recoveryNeo.img". The fastboot device will be disconnected, but after a few seconds you will get a Mass Storage & ADB Interface Detected.
4. Run "adb shell". If it says "device not found", disconnect, remove the battery, and try again from step 1. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
5. Run "mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system" from the adb terminal. If it says /system is not empty. run "rmdir /system/bin" and then run mount again.
6. type "exit"
7. Run :
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell
8. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot
9. The adb shell will terminate. Disconnect the phone, wait for ~15 sec, remove the battery, and then turn it on.
10. Your device should now be rooted.
Notes:
1. When booting with recoveryNeo.img, the screen will keep blank. That's normal(I think).
2. This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution.
Hope this is usefull for you.
This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error
Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.
Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)
Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.
Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.
Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?
w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!
Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD
looks pretty simple ... hopefully it will be the same process for us in the States
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus
Oh ok! I'll look at that now. Thanks fellas
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse
Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App
Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks
Want closed till me and 8trix figure what the hboot update IMG is called
PLEASE HIT THANKS.... READ ALL BEFORE PROCEEDING
FIXED COMMANDS HAD A COMMON MISTAKES
Hi, I am a developer from the " HTC Droid Incredible 4G LTE " My Rom http://forum.xda-developers.com/showthread.php?t=2065615 and I am still a newbie at this developing thing.. So with this being said I am not resposable for anything that could or may happen.*
Now I'm this TUTORIAL I will be providing the links and the instructions on how to proceed on the rooting process
*Requirments*:
-Android SDK - http://developer.android.com/sdk/index.html
-HTC drivers -*http://www.htc.com/us/support/
-The Su .zip - attachment
-And.... The HTC One Xv of course.
STEPS:
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4. To makes matter safer your gonna need to Temp Root, download this : http://uploaded.net/file/h44f6vni
5.Once downloaded, unzip it to C:\Root. Navigate to the folder in the command Prompt by typing *please follow directions CLEARLY
- *cd c:\Root\stuff
- *adb devices
- *adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet! Now type:
- *adb shell "while ! ln -s
/data/local.prop /data/data/com.android.settings/a/file99; do
:; done"
(errors will appear, ignore) Accept the restore on the device, then type:
-adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.) After reboot type:
- adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over. At this point, you can optionally do this ONLY if you want to revert changes:
- rm /data/local.prop
- exit
- adb reboot
Close cmd and start a new one then type
- adb devices
- adb install /system/apps/superuser.apk
- adb push su /system/bin or try adb push su /system/bin/su
6. - adb reboot
7. reboot twice, and if this don't work then please leave a comment and I will explain a new way.
ATTENTION
2nd way to try to root
1. On your computer make sure you have adb access ( usually just install android sdk )
2. Make sure you have HTC drivers installed ( remove HTC sync after the installment )
3. With that being said download the attachment file ( I downloaded the SU from*http://androidsu.com/superuser/ )
4.read carefully
5. create a folder were the superuser.apk and Su file is and name it system and inside that make a bin folder and place the Su file in the bin folder
6.Go to the folder were you extracted root folder in the last root alternative
7.Open cmd in that folder and make sure to extract the files ( superuser.apk and Su file to the root of the root folder )
8.Type : adb devices
9. Type: adb shell
10. Type: adb install ( locate were apk is on your pc.... Here is an Example of what ide put: adb install c:/root/nameOf app.apk , then press enter )
11. Type: adb push su /system/xbin or try adb push su /system/xbin/su or try adb push system/xbin/su /system/xbin/su
12. Use the following command to add the correct permissions to the su binary on the device adb shell chmod 6755 /system/bin/su
13. Adb reboot
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
I'll try when I get ack home tonight,
thanks for this
avid.aria said:
I'll try when I get ack home tonight,
thanks for this
Click to expand...
Click to collapse
Download a ruu to be on the safe side too... There's 2 ways on how you could root
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Reserved
Another reserved
Hope this helps everyone
Not working
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
8trix said:
So after we spent all that time I thought we should update people that at least for me this doesn't seem to work, even when we get the UI to break and not show anything there's still no root access. For anyone that does this and breaks the UI, mine seems to come back after locking and unlocking the bootloader. The following commands will get you back to a good state:
Reboot into fastboot mode
Make sure you have the fastboot and Unlock_code.bin (you get that from HTC dev website, you probably already have it) files in the same directory and:
fastboot oem lock
Device reboots, go back to fastboot
fastboot flash unlocktoken Unlock_code.bin
To unlock it again, then it should restart and be factory reset, which works for me to get it functional again. Hope that helps.
Click to expand...
Click to collapse
Me and you will work on finding a way
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
hasoon2000 said:
Both methods will not work.
1st method is designed for the Droid Incredible 4G LTE, not this phone.
2nd method requires to be rooted before you can even push files to the system folder.
Click to expand...
Click to collapse
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
To unlock the bootloader is easy, its like any other htc. Go to htc dev site and choose "all other supported devices" and follow the guide. It'll give you the file to fastboot flash to unlock. We're just working on getting root now. HTC definitely did something different with this phone because none of the other methods seem to work. Seems like there are some smart dedicated people working with us so please be patient and keep a watch on this thread!
lateral18 said:
but there is no support for unlocking the bootloader in htc dev , how did you do it ??
Click to expand...
Click to collapse
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
24ky said:
Yeah me and 8trix found this out.... We need a temp root or We need a costom recovery. And I have no experience on that
Bringing Life To The " Vivid, Incredible 4g, One XV "... Oh yeah.!!
Click to expand...
Click to collapse
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
flipinfin said:
Yes there is. Re check
---------- Post added at 06:07 AM ---------- Previous post was at 05:59 AM ----------
I tried to help my friend before he brought it back his htc to [email protected] cuz he bricked his phone. I unlocked bootloader and tried to flash recovery with HTC ONE V recovery thinking it would be similar. It did brick my phone with a warning on boot though i flashed the recovery again with the recovery in sdk platform tools and no longer brick. I know this might not be useful though i think u can flash the recovery with different recovery's till u find one that works with htc one v x just use htc models. Also the ruu is out where is the link ?
Click to expand...
Click to collapse
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
jose51197 said:
With ruu all will be fixed
Sent from my Incredible 4G LTE using xda app-developers app
Click to expand...
Click to collapse
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
8trix said:
I wish that were true lol. I cant seem to get the ruu to run all the way even on an xp machine. I think once it finished sending but then errored out right after.
I have flashed a bunch of random recoveries and nothing seems to work, but none have bricked my phone, my recovery just doesn't work. If someone could decrypt the rom.zip from the ruu that would be awesome and we could make custom recovery from that right?
Ruu:
http://forum.xda-developers.com/showthread.php?t=2097438
If that doesnt work (looks like its not there), i have already extracted the encrypted rom.zip and put it on my web server here:
Http://pnxcloud.com/rom.zip
Click to expand...
Click to collapse
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
jmztaylor said:
Did you relock before flashing ruu?
Sent from my HTC EVARE_UL using xda premium
Click to expand...
Click to collapse
I know this is old and not needed anymore since you're putting up root tomorrow, but I wanted to close this with yes, I did re-lock, and it kind of almost worked, like it finished sending the file, but then errored out with some other bs. No woory now though, I am back to fully stock unlocked and will test your root tomorrow if it's up then. Thanks again jmz, great work!
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
zeratos said:
So... how do I get the UI working again? I'm stuck with an unusable UI ._. !
Click to expand...
Click to collapse
Whats wrong?
None of the methods described on the main post work and I got stuck on the unusable UI, I google how to do a factory reset and now it's working again.
Thanks.
Also, is there a way to root this thing?
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable TWRP recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
I've created an easy installer for all you Windows folks!
Download this: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/easy-twrp-e98010g.zip
Extract it to somewhere on your computer.
Enable USB debugging on your phone, if you need the drivers I've included them in the "files/drivers" folder in the zip
Run the 'install.bat' script.
Check for any errors, if it was successful, you can 'adb reboot recovery' or use an app on your phone to get you into TWRP now!
Profit! (and realize that this was pretty easy!)
(thanks to hkfriends for pointing out the errors in my script!)
OR..
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-twrp-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-twrp-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have not tested external SD cards, since I don't have one with me at work.
I have also not tested backups or restores in TWRP yet.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
hkfriends
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
This is killer, I love twrp. So this will just over flash the cwm currently added earlier of course correct? Awesome work m8:thumbup:
EDIT: Not sure why but the Loki flash file downloads as a. Txt file for me
Sent from my LG-E980 using Tapatalk 2
maybe i am doing something wrong, but when i get into twrp the touch does not work
Very nice work there
testing back up and restore now
rbf351 said:
maybe i am doing something wrong, but when i get into twrp the touch does not work
Click to expand...
Click to collapse
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
sorry for the "newbie" question...but the file to download are getting to the phone right?
thecubed said:
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
Click to expand...
Click to collapse
yup, AT&T version, but it happens when i type in adb reboot recovery
Everything works so far tried backing up restore flashing and external sd... very nice work I will keep playing to see if i find any bugs
rbf351 said:
yup, AT&T version, but it happens when i type in adb reboot recovery
Click to expand...
Click to collapse
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
thecubed said:
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
Click to expand...
Click to collapse
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
rbf351 said:
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
Click to expand...
Click to collapse
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
thecubed said:
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
Click to expand...
Click to collapse
i have the following
ADB Interface
Android Sooner Single ADB Interface
edit, that wasn't while i was in recovery mode
in recovery mode i have
other devices
LG-E980 with an exclamation
I was able to flash and get into recovery without any issues. Excellent work! Thecubed and djrbliss, you guys are awesome!
here is the pastebin
http://pastebin.com/XPYi0v44
rbf351 said:
here is the pastebin
http://pastebin.com/XPYi0v44
Click to expand...
Click to collapse
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
thecubed said:
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
Click to expand...
Click to collapse
CWM works perfectly, i can navigate through all the menus using the softkeys
TWRP working perfectly here for me also! thank you for this! :good:
verry nice work........would be nice to have a kind od "how to" when thing get all set.....:good:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Gotroot said:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
yeah ...but i have all the file....does i have to put the phone in download mode??