Related
Let's get things started over here.
While we wait for the kernel source from Samsung, we can grab some basic information about the phone and use it to get things rolling.
I have the Sprint GSII, but I'm very prominent in that area as well.
Note: USB Debugging has to be enabled to run any adb commands.
Anybody with ADB if you would be so kind as to run:
Code:
adb shell mounts > mounts.txt
and then upload mounts.txt in your adb folder, that would be an amazing thing right about now.
Also somebody with some good internet speeds I would love to have a dump of the system and mounts.
Make a new folder (called SGH-T989-dump) from where you run adb and run the following command:
Code:
adb pull / /SGH-T989-dump
then please compress the SGH-T989-dump folder and upload it for me to use in future endeavors.
Thanks guys.
Information about rooting the Samsung Galaxy S II:
The Galaxy S II is immune to exploits unless it is those of an unsecured kernel. To have an unsecured kernel however, we have to compile from source, against a source that hasn't yet been released (as of this post).
Root can be maintained in the kernel or in the ROM, either or.
ClockworkRecovery Mod can be easily ported over to this device once I have a dump as described above and the output of all the commands above.
dump: http://dl.dropbox.com/u/21231693/T989odex.zip
as far as that 'mounts' command... i don't think that's gonna work without root.
I've uploaded everything to my website:
for anybody that wants to take a look.
bubby323 said:
I've uploaded everything to my website:
for anybody that wants to take a look.
Click to expand...
Click to collapse
awesome. on the i9100 i believe it's mmcblk0p5 that's the kernel.
http://forum.xda-developers.com/showthread.php?t=1114297
EDIT: looks like the man 'chainfire' has already been modding kernels for the i9100 for while. http://forum.xda-developers.com/showthread.php?t=788108
Just in case some of you are not familiar with it... I wanna give you the link to Samsung's opensource website. This way we can all be checking it daily for the release for our T989.
https://opensource.samsung.com/
bubby323 said:
Let's get things started over here.
While we wait for the kernel source from Samsung, we can grab some basic information about the phone and use it to get things rolling.
I have the Sprint GSII, but I'm very prominent in that area as well.
Note: USB Debugging has to be enabled to run any adb commands.
Anybody with ADB if you would be so kind as to run:
Code:
adb shell mounts > mounts.txt
and then upload mounts.txt in your adb folder, that would be an amazing thing right about now.
Also somebody with some good internet speeds I would love to have a dump of the system and mounts.
Make a new folder (called SGH-T989-dump) from where you run adb and run the following command:
Code:
adb pull / /SGH-T989-dump
then please compress the SGH-T989-dump folder and upload it for me to use in future endeavors.
Thanks guys.
Click to expand...
Click to collapse
Hey, if you want we can setup a go to meeting remote session and do anything you need remotely that way you can get exactly what you need from my phone and at the same time I can learn something.
I just got my T-Mobile Galaxy S2 and have not even put the sim card in it.
If you like this idea email me at:
[email protected]
Thanks.
Much Needed
It seems like given how much bloatware there is on the T-Mobile version, it seems like Rooting is an absolute necessity for this particular device. The Sprint version at least lets you uninstall all that crapware.
This is a BIG THANK YOU to all of those working on getting a root done for this device.
If there is anything I can do to help (I'm a bit of a n00b but I can at least try), please don't hesitate to let me know.
luckyduck69 said:
well.. i'll put it this way guys. i've 4 top devs remote into my machine and look at the phone and try various things. all of them have said that root will not happen unless samsung drops source. so... you're in a waiting game just hoping that samsung will be gracious enough to give it to you.
as far as that goes... you should talk to some prior samsung owners how that works. i honestly can't believe (based on sever prior samsung experiences) that source will arrive before 6 months from now. probably closer to a year. so that's the bitter hard truth of the outlook right now. if you're still in buyer's remorse period might wanna use it.
Click to expand...
Click to collapse
I didn't say that.. I said put a damn device in my hand and I've got a method which, based on previous models, has a 99% chance of success. That 1% is if UART debugging is not present.
AdamOutler said:
I didn't say that.. I said put a damn device in my hand and I've got a method which, based on previous models, has a 99% chance of success. That 1% is if UART debugging is not present.
Click to expand...
Click to collapse
How would you do it? I'm really curious to hear.
But you don't have to if you don't want to.
-Hercules grabbed my post, and threw it at your face to be read-
wesmagyar said:
I see what ya did there...
LOL just share the method. I'm sure if it works the community would be willing to hook ya up.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I've been repeating this in both of these threads...
UART!
If that does not work, then I'd go inside the device and locate the pre-FSA9240 chip UART lines, connect to them and exploit the battery charging sequence root prompt.
btw.. that video is old. I found a method and the captivate is now a development platform
AdamOutler said:
I've been repeating this in both of these threads...
UART!
If that does not work, then I'd go inside the device and locate the pre-FSA9240 chip UART lines, connect to them and exploit the battery charging sequence root prompt.
btw.. that video is old. I found a method and the captivate is now a development platform
Click to expand...
Click to collapse
I totally have an Arduino board. I never thought about attempting to use it as an interface. That's slick.
icebrkr said:
I totally have an Arduino board. I never thought about attempting to use it as an interface. That's slick.
Click to expand...
Click to collapse
Are you using it or are you just stating that it's cool? I'm betting that it will take at least a few days to get the parts together.
This would already have been done if someone had USPS'd me a device on day one.
Only DEV work on this topic!
Developers only please
keep all comments and chats on this other thread http://forum.xda-developers.com/showthread.php?t=1299840
To figure out which partition the kernel is, and also as an initial "can heimdall even talk to this thing" test, someone needs to install heimdall, enter download mode, and run the following:
Code:
heimdall print-pit
And put the output here.
Preferably someone who is already familiar with heimdall. Download mode is USUALLY accessed as follows:
Turn off device
Hold VolUp + VolDn
Insert USB
Again i wish i was home if for some reason nobody does this throughout today i will when i get home. I am not a dev bit also a quick learner and willing to help in any way possible
Sent from my SGH-T989 using xda premium
Entropy512 said:
To figure out which partition the kernel is, and also as an initial "can heimdall even talk to this thing" test, someone needs to install heimdall, enter download mode, and run the following:
Code:
heimdall print-pit
And put the output here.
Preferably someone who is already familiar with heimdall. Download mode is USUALLY accessed as follows:
Turn off device
Hold VolUp + VolDn
Insert USB
Click to expand...
Click to collapse
I am not familiar with heimdall at all, but if you can't find anyone else, ill try to help.
Sent from my Tmo Galaxy S II
"Steve Jobs is not your boyfriend.....STFU"
Bad news... I've been told that heimdall won't work with the T989, and also supposedly, Odin won't work without a PIT (this is a new thing I've never seen before.)
Entropy512 said:
Bad news... I've been told that heimdall won't work with the T989, and also supposedly, Odin won't work without a PIT (this is a new thing I've never seen before.)
Click to expand...
Click to collapse
that can't be good for business
Sent from my SGH-T989 using XDA Premium App
bzlik88 said:
I am not familiar with heimdall at all, but if you can't find anyone else, ill try to help.
Sent from my Tmo Galaxy S II
"Steve Jobs is not your boyfriend.....STFU"
Click to expand...
Click to collapse
jeffk-macbookpro:bin jeffkloy$ sudo heimdall print-pit
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
I don't create threads on xda very often and 95% of my posts are me trying to help people out, but this is something I wanted to get off my chest.
It seems like everyday in this forum there are about 5 new threads of people "stuck in a bootloop" or "stuck on Google screen." The majority of these people don't know the difference between adb and fastboot or bootloader and recovery.
I bought the G1 on launch and there weren't tool kits. We had to use telnet and command prompt to do everything manually. I knew nothing about linux or coding, but I followed instructions and learned what was happening when I entered these commands. Through owning the G1 and then moving on to the Nexus One I don't remember seeing so many threads about people "soft bricking" their device. I think the reason for this is the tool kits and other scripts that make it almost too easy to unlock and root your phone. While I respect the people who write these scripts (and I think they do serve a purpose in some situations) I think it's causing more harm than good.
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Weigh in with your thoughts, criticisms or tl;dr comments.
Thanks.
EDIT 8/9/12: Link to efrant's Android Galaxy Nexus 101 guide. All the info you need to know. http://forum.xda-developers.com/showthread.php?t=1812959
EDIT 11/14/12 My Thank you & Goodbye post.
I agree that it's lack of research that causes the problems. But don't knock the toolkits, they're designed for ease and they work perfectly with an understanding of what's going on. I can go thru adb and unlock and root because I researched the absolute **** out of it and know how to use adb but I used a toolkit. Like I said, if they don't want to research then bad on them. Gotta learn somehow be it by mistake or research. But the toolkits aren't the enemy.
Sent from my Galaxy Nexus
There's always a bigger fish. Like little man syndrome , be careful before you develop big man syndrome. " I'm taller than you "
PS even with research, " you can't fix stupid " so just let it go. A poor craftsman blames his tools. Simple as that.
Sent from my Galaxy Nexus using Tapatalk
Leaving good enough alone.
It's getting pretty comical when you see a "help me" post and before you even start reading the post you can correctly predict that the post will start something like this: "so I flashed *****'s custom ROM and now my phone's f****d".
This thread is so full of #winning. The easy way is not always the best way.
I used the manual methods for my Atrix so now after getting a good feel for Fastboot and ADB, the GNex Toolkit was really painless to use.
I understand what you're saying though. I guess some people just want easy routes to get what they want, completely scrolling past the giant red text that tells them exactly what could (and most likely will) happen.
phaze one said:
I agree that it's lack of research that causes the problems. But don't knock the toolkits, they're designed for ease and they work perfectly with an understanding of what's going on. I can go thru adb and unlock and root because I researched the absolute **** out of it and know how to use adb but I used a toolkit. Like I said, if they don't want to research then bad on them. Gotta learn somehow be it by mistake or research. But the toolkits aren't the enemy.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I'm going to second this, as long as the toolkits are well documented (showing what they did where, and why it was done) they can save people time typing the commands and looking them up if they forget them.
It's very similar to creating a GUI front end for a program. If done properly they're nothing but useful and time saving.
Im guilty of using the wugfresh kit. I could have easily done everything myself, but it contained everything I needed.
I agree with pretty much everything you said though. I see people offering money for them to root their phone over team viewer, etc. Those are the same people that warranty their phone that they, themselves messed up.
Thanks for your feedback everyone.
I just wanted to clarify I'm not ripping toolkits. They are a great way to get where you want to go quickly. If you know what you are doing by all means use it. But, to me it seems like they are just the cheat sheet to the test. Yeah, you aced the **** out of the test, but when asked to apply what you should have learned from that test in a real life situation; you are screwed.
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
adrynalyne said:
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
Click to expand...
Click to collapse
Exactly.
Wouldn't it be sweet if there was actually "profit" and the phone started spitting out money?
You're a dev. See what you can cook up.
The hardest part is just those drivers, not that I call it hard, just Windows can be a pita.
Once that part is working then using adb and fastboot comands I think is fairly straightforward and don't need the toolkit.
Im hardly experienced with Android or Linux. Ive used both for the past year or so only, and did take time to learn what abd commands there are etc. but also will use the toolkits to save time and headaches.
Anyways, its always like this. iOS hacking forums are similar.
Also, if you can get into recovery why do a nandroid? On SGS I was told by devs its not really needed as long as you dont mix up kernels. Do that, and what help is the nandroid? Cant flash it if you cant get into download mode. If you can, thats what stock images are for? I sync everything I really care about to cloud/PC.
El Daddy said:
Exactly.
Wouldn't it be sweet if there was actually "profit" and the phone started spitting out money?
You're a dev. See what you can cook up.
Click to expand...
Click to collapse
LOL...I wouldn't be here if I could
Toolkits for the nexus is kinda unnecessary because it is so easy to unlock, but there are devices that one the 1%(?) could unlock without a toolkit.
Sent from my HTC Desire HD using XDA App
I
adrynalyne said:
How to unlock, root, and be done with it.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
adb reboot bootloader
fastboot flash recovery recovery.img (clockwork)
fastboot reboot
adb reboot recovery
flash rom
reboot
profit
Not hard at all.
Click to expand...
Click to collapse
One-click rooting on my Fascinate:
I used z4root to root my phone before I flashed my first ROM (back then I just used ROM Manager for everything and didn't even bother looking at the ROM threads on XDA until the late DJ05/DL09 days when I got used to flashing manually in Clockwork Recovery). With z4root I didn't even need to use my PC to root, but it didn't always work when I had to go back to stock.
One-click Odin pitfalls:
My first experience with Odin was using a one-click version to flash a stock Froyo leak on my Captivate when they had just started making custom ROMs for Froyo. I had a bad experience using one-click Odin so I soon learned how to manually use Odin to do much more than simply flash a Froyo leak with one click. I soon discovered that Odin could be used to do much more than simply going back to stock - I could flash different versions of Clockwork Recovery, different Captivate and Fascinate modems, etc.
Learning adb for myself:
When I got my Gnex I used the exact method adrynalyne posted, and I found it more gratifying than any one-click root (I got my Gnex before there even was a 1-click, and I had long gotten used to adb. There's actually a lot more you can do with adb than simply rooting. If you only use it for rooting it's like going to a four-star restaurant and always ordering the hot dog from the kids menu - you're barely scratching the surface of what adb can do. I highly recommend reading up on adb and learning the different commands you can use. For example, it got me out of a bootloop more than once on my Fascinate when I was running AOSP MTD ROMs (long before jt1134 made 3-button recovery work on them).
The tl;dr:
One-click methods actually hinder you from exploring your phone's full potential, and often do more harm than good. Learning to do things manually for yourself lets you discover other possibilities you never would have found with the one-clicks.
Terminators run on Android
skynet11 said:
One-click methods actually hinder you from exploring your phone's full potential, and often do more harm than good. Learning to do things manually for yourself lets you discover other possibilities you never would have found with the one-clicks.
Click to expand...
Click to collapse
This is exactly my sentiment.
android01 said:
There's always a bigger fish. Like little man syndrome , be careful before you develop big man syndrome. " I'm taller than you "
PS even with research, " you can't fix stupid " so just let it go. A poor craftsman blames his tools. Simple as that.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You just used 5 rhetorical sayings that make very little sense, in the context of this topic. Be helpful or don't post, maybe?
OP, I couldn't agree more. Too many people post here (and other places) about being stuck in a bootloop even though they should already know how to fix it, if they knew anything about the process they had gone through. It's utterly insane that people are making heavy modifications to a device that costs $650+ without knowing *what* they're doing.
It's like someone going outside to change the oil on their car without knowing a thing about it and following the most basic instructions from some random person on the internet, then freaking out when someone tells them they poured the oil into the power steering reservoir.
No-ones forcing you to help people who have screwed up their phone so I don't see the need to be all holier than thou about it. Why should people have to understand everything that goes on when they use a one-click method? People should just make sure they read the instructions so they don't screw things up. That's the problem, not the tools they use.
As has been stated before in this thread.. you can't stop the stupid, or protect people from their own stupidity.
After far too many years helping out "stupid" users (here and on other forums), unfortunately, I find it far better to pick and choose who I want to help these days. Then, if I get frustrated, I only have myself to blame.. for even responding in the first place.
Hey everybody,
I'm planning on getting my GN in the next two weeks and wanted to ask a simple question:
first of all - I will want my GN to be a yakju, I will want to root it and I will want to unlock the bootloader.
Now, I believe I have everything understood just wanted to be sure if you could help me..
these are the steps I will take:
1. Check if GN is yakju
1.1 If GN is yakju simply use the gnex toolkit to unlock bootloader and root.
FINISH.
2. If GN is not yakju -
2.1 Use step-by-step (http://forum.xda-developers.com/showthread.php?t=1391881) to change rom to yakju 4.0.4.
2.3 Then use gnex toolkit to root (already unlocked bootloader in 2.1).
FINISH.
Am I good to go?
TNX!
Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,
deepayanneogi said:
Pretty much thats the way it should be,,, advance congrats for the next awesome purchase u r going to make,,,
Click to expand...
Click to collapse
Thanks mate! can't wait already
More replies are welcome.. I just want to feel certain I'm on the right track here..
Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.
Jubakuba said:
Be a big boy and don't use a tool kit =]
My guide makes it super simple...
Stickied above and linked in my sig.
Click to expand...
Click to collapse
Hey tnx
I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?
omricn said:
Hey tnx
I do consider myself an open minded guy and also I usually like to know the bits and insides stuff of things I do, I will usually prefer going the longer way (I.E - rooting\unlocking bootloader) then to just use the toolkit and pressing "next, next, next" because I prefer to know what every "next" does, BUT in this case, I think I managed to (obsessively) learn what everything does, so I decided to take the shorter trip to rooting+unlocking BL, do you think the toolkit has any disadvantages over the longer way?
Click to expand...
Click to collapse
If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.
He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.
Just...do yourself a favor and make sure ADB/Fastboot work.
run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?
That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.
An incorrectly flashed system or boot is "easily" fixable, though.
Theshawty said:
That seems about right. Just be a little cautious when flashing a radio or bootloader, as any of those two when flashed wrong can **** your device up beyond self-repair.
An incorrectly flashed system or boot is "easily" fixable, though.
Click to expand...
Click to collapse
Tnx Actually I'm not going to flash custom roms\radios\BL's just yet (if ever), just going to flash the official 4.0.4 yakju from Google, including the radio that comes with that bundle
Jubakuba said:
If it works it works.
The thing I hate about 'em is...
If a user has a soft-bricked phone.
Comes on here...asks for help.
And I tell him to do some adb/fastboot procedure: he asks "lul wut?"
And we have to help him set that up...and assume he set it up correctly.
He then might complain "oh, ya. It won't recognize my device."
Which is possible in some soft-brick situations...but it also might be user error.
Thus making trouble-shooting/fixing 10x harder.
Just...do yourself a favor and make sure ADB/Fastboot work.
run "adb devices"
and "fastboot devices"
If both of those recognize your phone...I guess the toolkit is fine.
As you said, you know whats going on...so what's the harm?
Click to expand...
Click to collapse
I catch your drift, and I know exactly what you mean.. I'm an IT guy, and apart from my job, I always learn everything there is to know about anything before I buy\change it in any way, to always be super safe and know what to do in every situation I can encounter.
Before I do something I will triple check what could and can happen so that I'm always 3 steps ahead. Thats the reason I already know almost everything there is to know about this phone, about rooting it, about unlocking it, ADB, fastboot etc. even before I bought it call me crazy..
Not crazy by my standards.
I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.
You'll love 'er.
Best phone I've owned...by far.
While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.
</rambling>
This phone STILL gives me the shivers.
Love it.
The 4.0.4 radio and bootloader will do for many more releases, I think. I don't think it's the radio's fault for the signal drops as a simple overclocking counters it.
Jubakuba said:
Not crazy by my standards.
I actually did the same thing...
Even posted a thread "OMG LULZ SO I DO THIS, RIGHT?" as you have...
Because I was excited as hell and wanted to reassure myself.
You'll love 'er.
Best phone I've owned...by far.
While the OS (and a Nexus on Verizon...which we thought we'd NEVER see) is a HUGE part of it...
I was/am actually impressed with the hardware as well.
I could go on and on and on about my Droid X (Got it on release day...didn't fully understand the implications of a locked bootloader...and how it would hinder the experience over that of my Original Droid) and how much I hated having a locked bootloader.
That was MY main push. I was like...Oh. My. God. A Nexus?! That **** is MINE.
</rambling>
This phone STILL gives me the shivers.
Love it.
Click to expand...
Click to collapse
Best. Reply. Ever.
Hey!
I want to start developing on an old Sony smartphone, the Xperia Miro st23i (Mesona).
Why this device? It isn't expensive to buy a new mainboard in case I break it and for reasons of sentimentality
I have already compiled kernels for Desktop Linux for various reasons.
Now to my question:
There are CM10 sources and some 2.5-ish TWRP available which I intended to upgrade.
Can I break access to fastboot by flashing a kernel that doesn't work at all?
This always happens every now and then when trying something. But on my Thinkpad, I could always swap the hdd when I've messed things totally up... Here, I can't do that.
Same question for TWRP, can I break fastboot?
Can a messed up partition layout break fastboot?
How could I break fastboot?
I think my questions applies to more or less every Sony phone.
I couldn't find any information useful to me by Google or Xda search because the results are so full of questions how to get into fastboot...
I absolutely don't know how the fastboot mode works and what it depends on.
I just want to know what major mistakes I could do before I do them. Maybe I can prevent to be in need of a JTAG Interface by asking in advance
Thanks for any useful answer!
PS: Please don't discuss the fact I'm gonna develop on this device. The amount of thanks given in case I'm successful will be like 4 and the device will be sluggish as hell on Marshmallow or Nougat because it has only a few MBs of RAM and only 1GHz CPU. I know that! But I don't want to start developing on a device that's so expensive that I can't afford to break it.
You wouldn't let a newbie "try to learn something" at your new Prius. You would give him your old 1992 car that you don't need anyway, regardless of its top speed -
Kaffeetrinker said:
Hey!
I want to start developing on an old Sony smartphone, the Xperia Miro st23i (Mesona).
Why this device? It isn't expensive to buy a new mainboard in case I break it and for reasons of sentimentality
I have already compiled kernels for Desktop Linux for various reasons.
Now to my question:
There are CM10 sources and some 2.5-ish TWRP available which I intended to upgrade.
Can I break access to fastboot by flashing a kernel that doesn't work at all?
This always happens every now and then when trying something. But on my Thinkpad, I could always swap the hdd when I've messed things totally up... Here, I can't do that.
Same question for TWRP, can I break fastboot?
Can a messed up partition layout break fastboot?
How could I break fastboot?
I think my questions applies to more or less every Sony phone.
I couldn't find any information useful to me by Google or Xda search because the results are so full of questions how to get into fastboot...
I absolutely don't know how the fastboot mode works and what it depends on.
I just want to know what major mistakes I could do before I do them. Maybe I can prevent to be in need of a JTAG Interface by asking in advance
Thanks for any useful answer!
PS: Please don't discuss the fact I'm gonna develop on this device. The amount of thanks given in case I'm successful will be like 4 and the device will be sluggish as hell on Marshmallow or Nougat because it has only a few MBs of RAM and only 1GHz CPU. I know that! But I don't want to start developing on a device that's so expensive that I can't afford to break it.
You wouldn't let a newbie "try to learn something" at your new Prius. You would give him your old 1992 car that you don't need anyway, regardless of its top speed -
Click to expand...
Click to collapse
Sony devices can use flashtool which is different from fastboot and provides the ability to reflash the full firmware - which helps you get out of most issues you may encounter.
hypertrack said:
Sony devices can use flashtool which is different from fastboot and provides the ability to reflash the full firmware - which helps you get out of most issues you may encounter.
Click to expand...
Click to collapse
Thanks for trying to answer my question, but that's not it.
I've already unbricked like 50 phones by exactly following tutorials and reading everything I could find.
In the end, I just want to know what flashmode or fastboot mode depend on. I want to know which partitions I may mess up and which I may not mess up.
My guess is I may do everything as long as I don't reflash the bootloader partition.
Kaffeetrinker said:
Thanks for trying to answer my question, but that's not it.
I've already unbricked like 50 phones by exactly following tutorials and reading everything I could find.
In the end, I just want to know what flashmode or fastboot mode depend on. I want to know which partitions I may mess up and which I may not mess up.
My guess is I may do everything as long as I don't reflash the bootloader partition.
Click to expand...
Click to collapse
Ahh ok - so I bet @Bin4ry would be able to answer that question - either him or @Androxyde
@Kaffeetrinker
This thread by @munjeni used to contain much more detailed info about the S1 bootloader, but most of it can't be accessed right now.
Titokhan said:
@Kaffeetrinker
This thread by @munjeni used to contain much more detailed info about the S1 bootloader, but most of it can't be accessed right now.
Click to expand...
Click to collapse
Thank you very much! This thread gave me some words to google. Doing so, I found the information I needed
As soon as summer's over, the project can start.
To answer my own question in short: you can't hardbrick a Sony device as long as you don't mess with the bootloader.
Fota recoveries are completely seperated from the actual ROM (although they can be updated together).
Fastboot does neither rely on Fota kernel nor does it on the system kernel.
As long as you do only regular rom developing and don't change the partition layout or mess in any other way with the bootloader partition, nothing should go wrong.
If you create an unbootable system kernel, you still can use your twrp. And if you create an unbootable TWRP, you can still get into the system.
If you mess up both, you still habe got fastboot.
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/
Morgrain said:
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/
Click to expand...
Click to collapse
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.
CacheOnlyPlease said:
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.
Click to expand...
Click to collapse
If you want to read a bit about complication, take a search engine and find out what
Android 11 scoped storage
Android 12 Dm-verity (device-mapper-verity)*
Android 12 Vbmeta verification**
SafetyNet Android
Android Hardware Attestation
means.
*is a method by which an image on block devices (the underlying storage layer of the file system) can be checked to determine if it matches an expected configuration, using a cryptographic hash tree. If the hash doesn't match, dm-verity prevents the stored code from loading.
**is the other half of this - it provides a cryptographically signed reference hash which is used to verify the integrity of /boot, /system, and /vendor partitions. The vbmeta image is only used to verify /boot, while vbmeta-system is used to verify /system.
Click to expand...
Click to collapse
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Every firmware update is a small struggle and you got to pray to the man above that your device will still boot up, even if you have those pesky magisk modules disabled.
Morgrain said:
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Click to expand...
Click to collapse
I think Google's goal was to make our devices more secure, not making modding/rooting harder.
CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
Not sure if this fits the bill of what you're looking for
Android Flash Tool
Perhaps this
Android Dollhouse (Flashtool) | TESTERS REQUIRED
Android Dollhouse The Definitive Android Flashtool. This is the support thread for Pixel 6 Pro. If you have another device, please check the other threads: Pixel 2XL: Support Thread Pixel 6: Support Thread I'm releasing the first user-facing...
forum.xda-developers.com
Az Biker said:
Not sure if this fits the bill of what you're looking for
Android Flash Tool
Click to expand...
Click to collapse
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.
For an all-in-one tool... what's wrong with fastboot?
CacheOnlyPlease said:
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.
Click to expand...
Click to collapse
If you haven't already looked them over, check the 6 PRO link in my sig, Step by step directions, pretty much each and every detail to make it easy for people like me who aren't rooting gurus.
Fastboot is the tool to pull you back from the abyss should you screw the pooch. Plenty of places you can find commands to help you out in a pinch, usually bringing you back to a factory fresh image.
Fastboot, update, and root a few times and it'll become much less concerning and tedious.