Greetings,
(before I brick my device)
I would greatly appreciate if someone could point me in the right direction for flashing a kernel on the N5110. I'm a Linux/UNIX/Mac person, and I have my environment setup for cross compiling / building kernels. I have one ready to go, but I essentially need some expert advice on getting it on my tablet.
My last experience was with the S3.. whereby I was able to use mkbootimg and fastboot (fastboot boot for example, which was pretty safe). Are there any (safe) methods for booting a kernel on the N5110 like that? or am i correct in that I'd have to dd the image to the block device?
In a nutshell -- I have a uImage built, and I need someone to quickly outline the steps I need to take moving forward to get it running.
Any feedback is much appreciated!
Cheers
seattleweb said:
Greetings,
(before I brick my device)
I would greatly appreciate if someone could point me in the right direction for flashing a kernel on the N5110. I'm a Linux/UNIX/Mac person, and I have my environment setup for cross compiling / building kernels. I have one ready to go, but I essentially need some expert advice on getting it on my tablet.
My last experience was with the S3.. whereby I was able to use mkbootimg and fastboot (fastboot boot for example, which was pretty safe). Are there any (safe) methods for booting a kernel on the N5110 like that? or am i correct in that I'd have to dd the image to the block device?
In a nutshell -- I have a uImage built, and I need someone to quickly outline the steps I need to take moving forward to get it running.
Any feedback is much appreciated!
Cheers
Click to expand...
Click to collapse
I've found the information on how to flash, yet I still need help figuring out how to create the boot.img from the uImage kernel.
Can anyone link me to any resources for doing this, and possibly note any details specific to the Note 8.0?
Solved http://forum.xda-developers.com/showpost.php?p=41304876&postcount=25
many thx to emwno
Related
so i need to know what file type the image needs to be, the size it needs to be, and how to install. basically a step by step of the process.
i'm running osx 10.6 so if anyone can give me some advice for doing it on mac that would be much appreciated.
thanks in advance.
trevor4g said:
so i need to know what file type the image needs to be, the size it needs to be, and how to install. basically a step by step of the process.
i'm running osx 10.6 so if anyone can give me some advice for doing it on mac that would be much appreciated.
thanks in advance.
Click to expand...
Click to collapse
I would also love to learn. Also running osx, and also know nothing about splash screens. Thanks
There is a thread that answers all you questions in the themes forum.
Sent from your mom's phone.
I've been trying to decipher from this thread how to make my Galaxy Nexus (Sprint) be able to boot from either Cyanogenmod, AOKP, or PA (and possibly Ubuntu Touch).
I tried flashing the kernel using boot.img from here but I couldn't figure out what to do with any of the Dual Boot/Triple Boot/ Quad Boot .zips
Currently I'm waiting on a download to fix my foolish soft brick, but in the mean time can anyone give me some directions that are a little more comprehensible for one that doesn't usually deal with kernels?
shadow1413 said:
but in the mean time can anyone give me some directions that are a little more comprehensible for one that doesn't usually deal with kernels?
Click to expand...
Click to collapse
you need to look at u-boot first.
i can't seem to find much info on root/recovery for g3. i found a little bit about bump and stump.... saying that twrp is possible but not much hard reliable facts on the topic.
Can someone who knows what they are talking about or knows a link to someone who knows what they're talking about help me get informed?
Basically i just want to know the procedure, how reliable it is (what are the chances of bricking the device), and any other relevant info that may be available. Any help is greatly appreciated and i'll be looking forward to developing some themes for this phone .
Thanks,
KS
*edit* also wondering if anyone has tried backing up a rooted version of the stock rom and restoring it. Does this work? Or do you have to flash kdz to return to stock after trying out some custom roms?
follow this video... https://www.youtube.com/watch?v=j5T7By2Zqvk (you can skip the parts on installing the rom)
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.
Does anybody have any information about how to modify the HBOOT image, or installing an entirely different boot image (e.g. Das U-Boot) onto this device? Or on any device? I've searched various forums for posts regarding HBOOT but not finding any regarding this.
I recently found my G2 (and G1!) buried in storage. I'd forgotten how much I enjoyed using them, especially the G2. I did the root thing, installing TWRP and a KitKat-based ROM, but it is terribly slow, not least of which for its reported 384M usable RAM.
I like to think I've got a pretty good idea as to how Android devices (generally) boot up, and was thinking I've got a fair amount of practice under my belt building my own Linux kernels, and how I'd really like a Raspberry Pi (or variant), but this device already has everything I'd need for a "SBC"-style device.
If I could slap Das U-Boot on there, I think it'd be pretty easy to (try to) boot a Linux kernel and shell and then figure out laboriously what to do for hardware drivers. (For that matter, what's the G2's capability re: USB OTG?) If it's a matter of making actual changes to HBOOT to tell it to load something other than Android (or kernel followed by Android), I'd be fine with researching that and then doing the laborious building an optimized kernel and drivers.
I could also be talking out my ass and have not, in fact, really understood the Android booting process. But I need a project and it would be really cool if I could work on this, I just don't really know where to look beyond what I've read. I did read one sequence where somebody reported on how they actually did a dual-boot Debian/Android setup (literal dual-boot, not a Debian chroot, which involved him modding the boot image for his LG Optimus). I haven't had time to follow through with it to be sure I can apply any of his findings to HBOOT, but I suppose that might be the best place to start.
One other thing -- if I modify HBOOT and break something, is that a brick, or can I arbitrarily swap out boot images even if they don't work? Or, more directly, will I have a means to re-burn the original image even if I were to completely wipe it? Will fastboot or adb recognize the device and be able to communicate with its filesystem? Not that I'm worried too much about bricking it, but it'd be nice to minimize that chance before I just bite the bullet and try another boot image and cross my fingers.
Hi @dwkindig,
You don't need to install a bootloader other than HBOOT to install non-Android software. For instance, I have recently ported postmarketOS to the HTC Desire Z. So if you need a project to work on, check it out. There are a lot of things you could help out with .