Related
Well, there we go. Dun wanna wait anymore, and I unfortunately are not too clever myself. So! I propose a root bounty. Whoever manages to root the device first and post a guide here will get it. If you don't have an Xperia play, I can do and upload dumps/test out new root methods for you if you contact me.
Some rules tho:
- It has to be possible for the average user without the use of additional hardware or commercial software (as in, software we have to buy)
- It doesn't have to work on devices that still have a locked bootloader, altho that would be very awesome.
- It has to work on the stock Sony Ericsson Software. Unless you can create a fully functional Cyanogenmod. Then I'll donate $100 to you instantly.
For starters, I throw $35 into the pot.
$20 by gnasher666
I'll go $20 for root
Meister_Li said:
- It has to work on the stock Sony Ericsson Software. Unless you can create a fully functional Cyanogenmod. Then I'll donate $100 to you instantly. .
Click to expand...
Click to collapse
this will be a problem, there is most definately a sig check on the file it pushes to your phone through bundled software. A modified boot.img can be pushed and flashed to the phone with fastboot. Also the update software detects the fact you unlocked the bootloader and it basically doesn't work on those phones anymore.
not to **** in your cereal, but making a modified kernel and push through fastboot is just a matter of doing it, not a whole lot of skill will be required.
like I said in the fastboot thread, if someone who has not unlocked their bootloader can upload the recovery image package that the bundled software downloads and mirrors it, it will make things a lot quicker.
johnsongrantr said:
this will be a problem, there is most definately a sig check on the file it pushes to your phone through bundled software. A modified boot.img can be pushed and flashed to the phone with fastboot. Also the update software detects the fact you unlocked the bootloader and it basically doesn't work on those phones anymore.
not to **** in your cereal, but making a modified kernel and push through fastboot is just a matter of doing it, not a whole lot of skill will be required.
like I said in the fastboot thread, if someone who has not unlocked their bootloader can upload the recovery image package that the bundled software downloads and mirrors it, it will make things a lot quicker.
Click to expand...
Click to collapse
I'm aware of that. I just mean that we should still be able to use the normal Sony Ericsson Android software, so root on the current software of the phone, even if the boot image or kernel have been replaced with other ones.
I just want to avoid loopholes, like someone saying: "I got root! But only if you replace everything and don't actually plan on using your phone because nothing else works!"
I will have my device coming this week.
please keep an eye on this thread for the arc.
http://forum.xda-developers.com/showthread.php?t=1035306&page=11
i will be updating my device before unlocking to get all the files needed. (hopefully)
I sure hope the phone can be rooted soon to much bloatware I want to get rid off
You cant get the boot.img with an unlocked one either I have got 2 one locked one open.
Sent from my R800i using XDA Premium App
waz000000 said:
You cant get the boot.img with an unlocked one either I have got 2 one locked one open.
Sent from my R800i using XDA Premium App
Click to expand...
Click to collapse
why do you need the boot.img for root?
rooting the system should be sufficient
johnsongrantr said:
this will be a problem, there is most definately a sig check on the file it pushes to your phone through bundled software. A modified boot.img can be pushed and flashed to the phone with fastboot. Also the update software detects the fact you unlocked the bootloader and it basically doesn't work on those phones anymore.
not to **** in your cereal, but making a modified kernel and push through fastboot is just a matter of doing it, not a whole lot of skill will be required.
like I said in the fastboot thread, if someone who has not unlocked their bootloader can upload the recovery image package that the bundled software downloads and mirrors it, it will make things a lot quicker.
Click to expand...
Click to collapse
There is no bundled software in the box. Which one are you talking about?
also,
What is wrong with this dump
http://forum.xda-developers.com/showthread.php?t=1022224
?
Thank you for sharing with us your ideas
FrAsErTaG said:
why do you need the boot.img for root?
rooting the system should be sufficient
Click to expand...
Click to collapse
Agreed, but id like to try and install CW and get a proper recovery screen sorted.
waz000000 said:
Agreed, but id like to try and install CW and get a proper recovery screen sorted.
Click to expand...
Click to collapse
A custom recovery would be awesome. However, the Play doesnt seem to have a recovery partition.
Sent from my Nexus S using XDA App
NielDK said:
A custom recovery would be awesome. However, the Play doesnt seem to have a recovery partition.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
not stock, but you can always make one, other SE devices don't have a *proper* recovery because they didn't have full access to the bootloader.
I'm curious what mode holding the back button on while plugging in the device, it appears to be different than holding search
johnsongrantr said:
not stock, but you can always make one, other SE devices don't have a *proper* recovery because they didn't have full access to the bootloader.
I'm curious what mode holding the back button on while plugging in the device, it appears to be different than holding search
Click to expand...
Click to collapse
Yep, it seems to be another kind of flash mode, altho I wasn't able to get any response out of the device with the usual fastboot and/or adb commands.
Hopefully this might be recovery mode. And that would open for custom recovery. Allthough I didnt find recovery partition, this might be because that MTD block is hidden. Root may show
Meister_Li said:
Yep, it seems to be another kind of flash mode, altho I wasn't able to get any response out of the device with the usual fastboot and/or adb commands.
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
I thought I should jump in here and clarify a few things. Bounty threads are allowed here at XDA as long as no donations are given up front. Meaning what you are doing here is just fine, as long as no one is "collecting" the donations up front.
A bounty thread can motivate development.
So...people who want to participate should NOT DONATE now they should PLEDGE and when you feel that the goal has been met THEN donate to the developer directly.
XDA will not mediate disagreements about these matters...so you do this at your own risk.
Have fun!
Thanks for clearing that up - that's how I planned it, actually. As soon as someone accomplishes root, I'll send my donation his way and I hope that others will too!
that works as I hoped it would. I'm good for the money once root access is available.
Personally, I think root will be a lot harder than cfw as it will potentially allow access to parts of the software Sony don't want you playing with.
fingers crossed some clever person finds an exploit sooner rather than later.
I would chuck in $20 if the Neo could be included....
Just spent an hour on the phone with sony ericsson trying to get a direct link to the recovery image to no avail.
I got 20 usd for the person who gets me a copy of that recovery image.
Once you get me that, I can make a kernel with root out of it ill give it away for free with instructions on how to flash it (given unlocked bootloader)
I wish I woulda did this myself before I unlocked my bootloader. Kinda frusterrated after dealing with their tech support.
I have a locked one still cant get img files,
Right im trying a system restore on the new one (locked bootloader) im hoping the recovery image will be downloaded onto the computer and i can extract from there, lets see huh/
well it restored but cant find the image, it's pissing me off now spent to long doing sh!t.
connected to the phone to ADB pushed SU no permission chmod busybox no permission, gahhh we need that boot.img or system.img but how the hell do we get it?!?
So, yes - I need to know how to brick my phone beyond repair please....
"Why !?" I hear you ask....
Imagine the situation: Some b*st*rd has stolen your phone . You are never going to see it again... ever... absolutely zero chance of getting it back...
If you had the option to brick it so no one could sell or use it, would you?
Yes, of course you would!!
It's possible to remotely execute any BusyBox/Terminal Command using the application Tasker and I want to know which one would do the most damage!?
Please let me know! "How do I totally brick my phone?"
load a corrupted radio file
ohhh, sorry to hear that. I had the perfect solution if you still had the phone. But um yea I don't take out my phone near any friends. My brother got his vibrant stolen only after 2 weeks.
Didn't mean to mislead! My phone hasn't actually been stolen! But I'm working on security profiles and need to know what the final command should be to end its life....
Can you flash a radio from the Terminal Emulator?
Sent from my HTC Desire using XDA Premium App
This is what I did and I actually got Verizon to give me a re-furb. What it does is bring you to the htc inc white screen then nothing else. Use root explorer go into systems/fonts and change the name on one of the droidsans.ttf files. I think I totally erased the files but changing them should cause the phone to be totally [email protected]#$. I hope this messes up your phone. Lol
skinny jeans piss me off
BIGshot87 said:
This is what I did and I actually got Verizon to give me a re-furb. What it does is bring you to the htc inc white screen then nothing else. Use root explorer go into systems/fonts and change the name on one of the droidsans.ttf files. I think I totally erased the files but changing them should cause the phone to be totally [email protected]#$. I hope this messes up your phone. Lol
skinny jeans piss me off
Click to expand...
Click to collapse
Great, thank you! Shall test and hopefully be able to revert in fastboot?!
skinny jeans piss me off too...
Further to the above, does anyone know if it's possible to disable entering recovery by deleting certain system files?
brandall said:
Further to the above, does anyone know if it's possible to disable entering recovery by deleting certain system files?
Click to expand...
Click to collapse
Flash a stock recovery image to disable flashable recovery. Also renaming a file doesn't make the phone broken, it just doesn't allow it to boot.
Sent from my Hero that never dies! ;D
dastin1015 said:
Flash a stock recovery image to disable flashable recovery. Also renaming a file doesn't make the phone broken, it just doesn't allow it to boot.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks - I need it to boot - just don't want someone else to be able to wipe and/or flash a custom ROM
I need to read up if there's a way to flash a recovery image from the Terminal...
hmmm...
brandall said:
Thanks - I need it to boot - just don't want someone else to be able to wipe and/or flash a custom ROM
I need to read up if there's a way to flash a recovery image from the Terminal...
hmmm...
Click to expand...
Click to collapse
To flash a recovery image from TE use this if your ROM supports it: flash_image recovery /sdcard/(name of recovery)
An example for me is: flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
Sent from my Hero that never dies! ;D
dastin1015 said:
To flash a recovery image from TE use this if your ROM supports it: flash_image recovery /sdcard/(name of recovery)
An example for me is: flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
That's brilliant thank you. Do you know if that can be reverted by flashing the custom recovery image again? Or will I lose the ability to do that once I flash back to stock?
Sorry for the questions, this stuff confuses me...
brandall said:
That's brilliant thank you. Do you know if that can be reverted by flashing the custom recovery image again? Or will I lose the ability to do that once I flash back to stock?
Sorry for the questions, this stuff confuses me...
Click to expand...
Click to collapse
As long as you're on a custom ROM that supports flash_image you can flash a recovery image through TE.
Sent from my Hero that never dies! ;D
dastin1015 said:
As long as you're on a custom ROM that supports flash_image you can flash a recovery image through TE.
Click to expand...
Click to collapse
Thanks again - mine does, so sorted
Never thought of using lookout?
Sent from my MB860 using XDA App
makr8100 said:
Never thought of using lookout?
Click to expand...
Click to collapse
Hopefully going way beyond that... see >>here<<
Do you have the information to know whether it's truly been stolen yet? I'd make sure that it's really been stolen and you, for sure, wouldn't get it back before attempting something like this. I definitely wouldn't want to brick my own phone on purpose just to find out I forgot it somewhere...
ChrisDang said:
Do you have the information to know whether it's truly been stolen yet? I'd make sure that it's really been stolen and you, for sure, wouldn't get it back before attempting something like this. I definitely wouldn't want to brick my own phone on purpose just to find out I forgot it somewhere...
Click to expand...
Click to collapse
See the link above Chris. My phone hasn't actually been stolen, but these commands will be a last resort feature of Sherlock Droid.
Agreed, it would be a nightmare to brick it and then find it under the sofa!
Sent from my HTC Desire using XDA Premium App
You shouldn't brick it quite the opposite, the thief should be able to keep using the phone as much as possible but in the mean time the gps should be secretly turned on and photos should be make so you can track the thief or if that fails publish his info and name and shame him
godutch said:
You shouldn't brick it quite the opposite, the thief should be able to keep using the phone as much as possible but in the mean time the gps should be secretly turned on and photos should be make so you can track the thief or if that fails publish his info and name and shame him
Click to expand...
Click to collapse
You are absolutely right godutch, that is the main aim of the profiles to keep booting into the OS at every opportunity, even using fake recovering images (as in a photo of the custom recovery screen) for the splash and boot animation that appear to be the device gathering system information - all the time it will actually be booting with the launcher, notification bar and lock screen etc disabled so not to give it away - once there the priority is to get a GPS fix
However, there will come a point when you've not heard a peep from the device in days and perhaps your insurance (if you have it) have already paid out... In which case, some users will want to execute the remote 'self destruct' command, to make sure the phone will never be usable to anyone else....
Edit: Trying to make the thief provide a valid gmail address and forwarding the new number if the SIM is changed are all in there too!
What if thief changes to SIM that has no data plan or does not enter any wifi area?
Hey guys I just joined the site a few days ago after being sent here by some guys from some Audio forums, which is my main hobby. I guess you could say Im kind of a techy but am just now getting in to laptop building and things like that so I am still a newb. Anyways I just got the HTC DNA which I like quite a bit but Id like a little more out of it such as little better battery life, more customization, and to get rid of the bloat ware installed. On that note however I have never done anything much with phones since this is my first Droid after using Iphones which is why Im starting this thread...
I have been reading around and am still quite lost as to what I need to do to get what I wanted (battery life, customization, and to get rid of bloatware). I really like the ViperDNA ROM after watching the video but not sure if....
1. It will do what I want?
2. How to install it/make it run properly?
3. If there is something better?
So if you guys could walk me through what it takes to run something like that I would greatly appreciate you helping out some one new to this whole "Rooting" thing since this is my first Droid... If I can return the favor by helping out with your Car audio or talking guns with anyone Id be glad to!
Better n' Reverse said:
Hey guys I just joined the site a few days ago after being sent here by some guys from some Audio forums, which is my main hobby. I guess you could say Im kind of a techy but am just now getting in to laptop building and things like that so I am still a newb. Anyways I just got the HTC DNA which I like quite a bit but Id like a little more out of it such as little better battery life, more customization, and to get rid of the bloat ware installed. On that note however I have never done anything much with phones since this is my first Droid after using Iphones which is why Im starting this thread...
I have been reading around and am still quite lost as to what I need to do to get what I wanted (battery life, customization, and to get rid of bloatware). I really like the ViperDNA ROM after watching the video but not sure if....
1. It will do what I want?
2. How to install it/make it run properly?
3. If there is something better?
So if you guys could walk me through what it takes to run something like that I would greatly appreciate you helping out some one new to this whole "Rooting" thing since this is my first Droid... If I can return the favor by helping out with your Car audio or talking guns with anyone Id be glad to!
Click to expand...
Click to collapse
I love the ViperRom! It has every customization imaginable and is very professional looking. It helps with battery life but you can use pretty much any kernel you want with a rom and that probably has as much or more affect on battery life. You need to be rooted and have adb installed on your pc - are you to this point yet?
Here is a good link by droidmodd3rx that walks through most things on video. http://forum.xda-developers.com/showthread.php?t=2012346
Also did you accept Verizon ota update in the last week? If so I am not sure you can root yet, they will have to work out a new method for that.
TJMac44 said:
I love the ViperRom! It has every customization imaginable and is very professional looking. It helps with battery life but you can use pretty much any kernel you want with a rom and that probably has as much or more affect on battery life. You need to be rooted and have adb installed on your pc - are you to this point yet?
Here is a good link by droidmodd3rx that walks through most things on video. http://forum.xda-developers.com/showthread.php?t=2012346
Also did you accept Verizon ota update in the last week? If so I am not sure you can root yet, they will have to work out a new method for that.
Click to expand...
Click to collapse
It asked me today if I wanted to update and I held off since I read something about it not working with the new update... So Im still on the 1.15.605.4 Software number...
Also what is this ADB I need to have installed on my PC?
Newer "B" than Better-n-Reverse!
Better n' Reverse said:
Also what is this ADB I need to have installed on my PC?
Click to expand...
Click to collapse
This is my second Droid phone, but I am interested in rooting this beast (HTC DNA). But I think I might temporarily be out of luck as my Software Number is 2.04.605.2 71 ORD.
I'll sit tight if this is true, but once there is a rooting option for this update can someone PLEASE, please, please post a V-E-R-Y detailed and simplified method for rooting?
I have to do whatever it take to get rid of "DROOOIIIDDD" on start up. Seroiously, that is my primary reason for looking into this rooting business. I'm such a sad case
Cheers!
It looks like its quite the long process if you don't have SDK and ADP already installed which you will need to unlock the bootloader...
Better n' Reverse said:
It looks like its quite the long process if you don't have SDK and ADP already installed which you will need to unlock the bootloader...
Click to expand...
Click to collapse
Here is a guide for installing adb
http://www.jailbreakeye.com/android/install-adb-fastboot
Here is a video that I went by to install my adb
http://www.youtube.com/watch?v=oaNM-lt_aHw
Here is page for new easy way to unlock bootloader
http://forum.xda-developers.com/showthread.php?t=2109862
And here is page with video guides to Root, install custom recovery and install kernels and Roms.
http://forum.xda-developers.com/showthread.php?t=2012346
You also need to install usb drivers on your pc. If you have't already done so you can get them here
http://forum.xda-developers.com/showthread.php?t=2000896
It seems overwhelming but it really isn't if you read/watch things carefully and follow instructions it is pretty easy and fun.
TJMac44 said:
Here is a guide for installing adb
http://www.jailbreakeye.com/android/install-adb-fastboot
Here is a video that I went by to install my adb
http://www.youtube.com/watch?v=oaNM-lt_aHw
Here is page for new easy way to unlock bootloader
http://forum.xda-developers.com/showthread.php?t=2109862
And here is page with video guides to Root, install custom recovery and install kernels and Roms.
http://forum.xda-developers.com/showthread.php?t=2012346
You also need to install usb drivers on your pc. If you have't already done so you can get them here
http://forum.xda-developers.com/showthread.php?t=2000896
It seems overwhelming but it really isn't if you read/watch things carefully and follow instructions it is pretty easy and fun.
Click to expand...
Click to collapse
Thanks for putting all that together for me! What is the purpose of the USB drivers?
Better n' Reverse said:
Thanks for putting all that together for me! What is the purpose of the USB drivers?
Click to expand...
Click to collapse
So your computer can see your phone.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
So your computer can see your phone.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Awwww ok... I got SDK loaded just trying to get it open...
Well I followed the video exactly and I cant get ADP to run when I type in ADP the command still and have double checked everything...
Better n' Reverse said:
Well I followed the video exactly and I cant get ADP to run when I type in ADP the command still and have double checked everything...
Click to expand...
Click to collapse
depending on what you named your directories are you going to the platform-tools directory? you need to type adb not adp, lower case not caps, and then there needs to be a command after adb. Try adb devices.
Better n' Reverse said:
Well I followed the video exactly and I cant get ADP to run when I type in ADP the command still and have double checked everything...
Click to expand...
Click to collapse
You set up your system variables crooectly?
Sent from my HTC6435LVW using xda app-developers app
Better n' Reverse said:
Well I followed the video exactly and I cant get ADP to run when I type in ADP the command still and have double checked everything...
Click to expand...
Click to collapse
It's adb not adp
Sent from my HTC6435LVW using XDA Premium HD app
TJMac44 said:
depending on what you named your directories are you going to the platform-tools directory? you need to type adb not adp, lower case not caps, and then there needs to be a command after adb. Try adb devices.
Click to expand...
Click to collapse
I believe so...
Bigandrewgold said:
You set up your system variables crooectly?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Like I said I followed that vid exactly so...
.torrented said:
It's adb not adp
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
Ya thats what I meant just wasnt paying attention last night
Well I got it unlocked finally but now when I go to flash the Recovery I just get an error... Sometimes the "emulator" one, "waiting on the device" , Or just cant the find file... Just doing it straight from the comand I open in the file or using Hansoon2000's tool...
Quick question
Hey, going to do a little thread jacking here. It seems like this would be the best place to ask my question. I'm a long-time iOS user that just switched and silly me accepted the OTA 2.04.605 update. Now, if I performed a hard reset wouldn't that put my software back to its factory settings and would allow me to unlock my bootloader? Sorry if this annoying just trying to make sure it'll work before I go through the hassle of restoring. Thanks for any help!
Better n' Reverse said:
Well I got it unlocked finally but now when I go to flash the Recovery I just get an error... Sometimes the "emulator" one, "waiting on the device" , Or just cant the find file... Just doing it straight from the comand I open in the file or using Hansoon2000's tool...
Click to expand...
Click to collapse
Your phone needs to be in fastboot for you to find it. Connect the phone, boot into the bootloader, enter fastboot, open a new command prompt, and try "fastboot devices". you should see the phone.
If you can't find the file then you're not in the right directory. Make sure you navigate to the folder that contains the file then run the command. (or you can just give it the full path to the file)
ASAPscotty said:
Hey, going to do a little thread jacking here. It seems like this would be the best place to ask my question. I'm a long-time iOS user that just switched and silly me accepted the OTA 2.04.605 update. Now, if I performed a hard reset wouldn't that put my software back to its factory settings and would allow me to unlock my bootloader? Sorry if this annoying just trying to make sure it'll work before I go through the hassle of restoring. Thanks for any help!
Click to expand...
Click to collapse
No, I don't think that'll help. The factory reset basically wipes memory and restores the original ROM. The OTA updates the radios / kernel. But don't quote me on that. I'll let a dev who knows better comment.
drumz0rz said:
No, I don't think that'll help. The factory reset basically wipes memory and restores the original ROM. The OTA updates the radios / kernel. But don't quote me on that. I'll let a dev who knows better comment.
Click to expand...
Click to collapse
I think you are right because I have not heard of anyone suggesting this, and it was just my noob idea! Thanks for the help.
ASAPscotty said:
Hey, going to do a little thread jacking here. It seems like this would be the best place to ask my question. I'm a long-time iOS user that just switched and silly me accepted the OTA 2.04.605 update. Now, if I performed a hard reset wouldn't that put my software back to its factory settings and would allow me to unlock my bootloader? Sorry if this annoying just trying to make sure it'll work before I go through the hassle of restoring. Thanks for any help!
Click to expand...
Click to collapse
This question has been answered, but I thought I'd provide a little more detail to their answers:
On android, the memory is divided into several partitions (you might think of it like different disk drives), including a /boot, /system, and /data partition. The /boot partition is where the kernel (the heart of the android o/s) resides; the /system (where the bulk of the android o/s resides); the /data is where your apps and personal data reside. The /boot and /system partitions require system administrator level rights in order to change the information stored there (the system administrator account on android/linux is known as "root" or "superuser").
The update that came from VZW changed elements in the /system and /boot directories, using a superuser key to grant the update permission to change the files on those partitions.
Unfortunately, a factory reset only essentially re-formats the /data partition, wiping out all the user information stored there, but doesn't change the /system or /boot partitions.
The root process essentially hacks the device to gain system administrator rights to the android phone, using exploits in the android o/s. This is essentially a cat and mouse game. The update sent by VZW/HTC patches the exploits that were used to gain root access (that is why it is always dangerous to accept updates from VZW/HTC).
Hopefully the developers on this website will be able to find another exploit/weakness, and provide a way for those who have phones that have the update to obtain root, unlock the bootloader (another partition), and gain s-off (another level of turning a security flag to "off" so that even more partitions can be accessed/changed (ie.the /radio partition).
I have a vzw max and i recently reverted everything back to stock and unrooted; or so i believed. The kernel still says 3.4.10 etc. and the phone has no signal nor can it find my location. It keeps rebooting every 30 secs or so and no matter what mode I put the device into, it isn't recognized by my PC. the bootloader is locked and I am S-Off. This all happened after I tried to flash CWM's HTC M7 recovery because the Max isn't listed and I couldn't figure out how to flash TWRP. Help please because this is getting crazy and I can't figure out what to do...
bump
nobody at all eh...
LocBox said:
nobody at all eh...
Click to expand...
Click to collapse
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
dude i feel for you.
why did you put m7 cwm on there. clearly not for this device.
can you still get to bootloader? if you can flash the correct recovery! then find a backup someone has done and restore. or flash the correct boot.img
dude here's the correct recovery
http://forum.xda-developers.com/showthread.php?t=2498749
Well the only problem is my any pc won't even detect that it's connected when I plug it into it. So I can't use any fastboot or adb methods and even when I put the phone into fastboot mode it doesn't connect either. I'm able to put it into bootloader mode and it doesn't reset but still no connection; just charges. I've tried flashing through stock recovery manually and it aborts every attempt I'm assuming because my BL is locked..
No it doesn't
dottat said:
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
no it doesnt'
LocBox said:
no it doesnt'
Click to expand...
Click to collapse
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Thanks
Dottat has helped me and not a moment too soon, I was seconds from printing out the return label for HTC and sending it in for a refurb exchange. smbh. thanks man.:good:
dottat said:
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
pradeepvizz said:
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
Click to expand...
Click to collapse
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
pradeepvizz said:
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
Click to expand...
Click to collapse
That is correct, full flash from bootloader. 0P3PIMG.zip on root of sd. and boom with some pow.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
dottat said:
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
Click to expand...
Click to collapse
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
JBS976 said:
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
Click to expand...
Click to collapse
Check your pm shortly. S-off later today ?
Sent from my HTC6600LVW using Tapatalk
Hello,
is there a way to modify or get rid of the warning screen that pops up if you boot your unlocked XX?
You know, that one with the yellow triangle and the five seconds delay.
As I understand you can modify it with fastboot, but I only found that threads for some Motorola devices, so is it possible with the Xperia X?
Maybe by relocking the bootloader?
bauboni said:
Maybe by relocking the bootloader?
Click to expand...
Click to collapse
Well, I installed a custom kernel with root. If I relock the bootloader, I would lose root wouldn't I? So I think that's not an option for me ?
Anyone please? :/
ceejay105 said:
Anyone please? :/
Click to expand...
Click to collapse
Cant do it. That warning is in the bootloader, not the kernel so it can't be modified.
shoey63 said:
Cant do it. That warning is in the bootloader, not the kernel so it can't be modified.
Click to expand...
Click to collapse
Thanks for your answer. In the Motorola forums someone described to remove it by flashing a custom logo.bin file. Isn't there any way to adopt this for the XX?
ceejay105 said:
Thanks for your answer. In the Motorola forums someone described to remove it by flashing a custom logo.bin file. Isn't there any way to adopt this for the XX?
Click to expand...
Click to collapse
If there was a logo.bin in the kernel ramdisk it would be possible, but there isn't. The warning is embedded somewhere else in the bootloader partitions and attempting to modify those would most likely cause a hardbrick. I wouldn't recommend going there...
shoey63 said:
If there was a logo.bin in the kernel ramdisk it would be possible, but there isn't. The warning is embedded somewhere else in the bootloader partitions and attempting to modify those would most likely cause a hardbrick. I wouldn't recommend going there...
Click to expand...
Click to collapse
Okay, seems I have to stick with that warning though. Thank you anyway.
Well someone did find that the PNG format image itself is in \ramdisk\res\images\warning
I can confirm that it is not in the kernel. The kernel does contain two folders at this location with some battery images (likely when you charge while phoine is off) but none of them are named warning. I own X Compact myself. Just wanted to mention this if someone with the nessesary skills decides to take up this task.
RaXelliX said:
Well someone did find that the PNG format image itself is in \ramdisk\res\images\warning
I can confirm that it is not in the kernel. The kernel does contain two folders at this location with some battery images (likely when you charge while phoine is off) but none of them are named warning. I own X Compact myself. Just wanted to mention this if someone with the nessesary skills decides to take up this task.
Click to expand...
Click to collapse
I really don't know why someone would be so happy to remove that warning, but anyaway if someone has the time it would be nice
FoxTheLegend said:
I really don't know why someone would be so happy to remove that warning
Click to expand...
Click to collapse
Because it's unnecessarily annoying and jarring/alarming every single time your phone boots up?
Every single Motorola phone I've owned I've been able to overwrite the warning with a custom image with a simple and safe fastboot command. It ends up looking a lot cooler too than the stock (locked) screen since you can put whatever you want in there as long as it's the entire size.
The Motorola forums have entire threads dedicated to shared bootlogo images, with the only difference being the size/resolution, but otherwise they work cross-device.
Sorry....Had a Motorola Moto g2 once that i could Just sas: Okay flash this and this, BAM!" and it was removed.....but in Sony devices IT SEEMS it ist imbedded into bootloader
FoxTheLegend said:
I really don't know why someone would be so happy to remove that warning, but anyaway if someone has the time it would be nice
Click to expand...
Click to collapse
we would like to do that because
1. it is annoying
2. 5 seconds less boot time because of bootimage not even loading when it appears
Some random said:
we would like to do that because
1. it is annoying
2. 5 seconds less boot time because of bootimage not even loading when it appears
Click to expand...
Click to collapse
Yeah dude I got it but I wrote this thing like 2 years ago
FoxTheLegend said:
Yeah dude I got it but I wrote this thing like 2 years ago
Click to expand...
Click to collapse
I realised that too now.....