First of all, I think this tutorial is needed since I see this question pop up everywhere and most flashing/rooting tutorials are for Windows. I found myself struggling a lot with flashing on mac since it so much easier on Windows and there are plenty of tutorials on the net for windows but not so much or very poorly for Mac . So I hope this clears out much of your questions on how to flash for a mac.
Download the mac version of the Android SDK from the website.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Unzip it and place it on your harddrive where you will never delete it. For example:
Code:
Users/your_username/Documents/Android/android-sdk-macosx
Go to the unzipped folder and then navigate to tools. Double click android and let it run. It will open terminal windows and the android sdk itself. Let it load
It will look like this:
Now install the tools, platform tools and I also installed the sdk since 4.0.
Click to expand...
Click to collapse
Download the fastboot files (boot.img and fastboot-mac) here.
Unzip them and place them in the platform-tools in your android-sdk directory for example:
Code:
Users/your_username/Documents/Android/android-sdk-macosx/platform-tools/
Now you download the ROM you want. Here are the most of them located for the HTC One S and you copy it to your phone.
Boot into recovery. If you don't know how to do it, here is a short guide:
Power Off while holding the down volume button
You are into bootloader now if it restarted
Navigate to recovery with your volume buttons
Press the power button to select recovery
Click to expand...
Click to collapse
Then you do the following steps:
Wipe data/factory reset
Wipe cache partition
Install zip from sdcard
choose zip from sdcard
Then you choose the zip you downloaded and where you put it on your phone
Let it install
Click to expand...
Click to collapse
If it is installed:
Turn your phone off while holding the down volume button
Let it boot into bootloader
Connect your phone to your Mac
Select fastboot in bootloader
It will change to fastbootusb
Click to expand...
Click to collapse
Open up Terminal on your mac and type following commands:
cd /Users/your_username/Documents/Android/android-sdk-macosx/platform-tools
chmod +x fastboot-mac
/Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/fastboot-mac flash boot boot.img
You could replace "/Users/your_username/" with "~/" (Option + N). (Thanks to m1schi)
Click to expand...
Click to collapse
let it run and it should show you something like this:
Now reboot and enjoy your flashed ROM!
Note: if this helped you in any means: please leave a thanks.
You could replace "/Users/your_username/" with "~/" (Option + N). This always links to your home directory.
m1schi said:
You could replace "/Users/your_username/" with "~/" (Option + N). This always links to your home directory.
Click to expand...
Click to collapse
Oh thank you! will put it in there.
Sent from my HTC One S using XDA
Nice tutorial, but there is a shorter way.
You don't need to install the Android SDK (unless you want to get involved with android development) you just need a working copy of Fastboot for mac and run it from terminal
That's how I have always done it. Not only on my One S, but also on all the others HTC phones I've Owned
https://dl.dropbox.com/u/1012262/fastboot-mac
solracarevir said:
Nice tutorial, but there is a shorter way.
You don't need to install the Android SDK (unless you want to get involved with android development) you just need a working copy of Fastboot for mac and run it from terminal
That's how I have always done it. Not only on my One S, but also on all the others HTC phones I've Owned
https://dl.dropbox.com/u/1012262/fastboot-mac
Click to expand...
Click to collapse
Well, if they want to work with adb and such they need to download the sdk. So yeah, I know it was a shorter way but i thought: give it the full on way for people so they are sure.
ive done this 14 times and every single time it says no such file or directory this does not work
chuuw33 said:
ive done this 14 times and every single time it says no such file or directory this does not work
Click to expand...
Click to collapse
You can use the Boot Flash Script from my TrickDroid thread which has MacOS support
You can also add the path of the folder in which the fastboot binary is located in ~/.bash_profile
In your guide that would be /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ so with a command:
Code:
echo /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ >> ~/.bash_profile
This will make you able to use the fastboot binary from any directory without having to type the path to the binary. In other words if your boot.img is located on your desktop you could just navigate to your desktop in terminal and execute
Code:
fastboot flash boot boot.img
without the path to the binary
torxx said:
You can use the Boot Flash Script from my TrickDroid thread which has MacOS support
Click to expand...
Click to collapse
thanks i'll give it a go
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
C0mpu13rFr34k said:
You can also add the path of the folder in which the fastboot binary is located in ~/.bash_profile
In your guide that would be /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ so with a command:
Code:
echo /Users/your_username/Documents/Android/android-sdk-macosx/platform-tool/ >> ~/.bash_profile
This will make you able to use the fastboot binary from any directory without having to type the path to the binary. In other words if your boot.img is located on your desktop you could just navigate to your desktop in terminal and execute
Code:
fastboot flash boot boot.img
without the path to the binary
Click to expand...
Click to collapse
thanks i'll try this out
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
sanders858 said:
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
Click to expand...
Click to collapse
The op of trickdroid thread. You may need to change boot may need to edit scripts boot.IMG depending on what ROM your running.
Sent from my Nexus 7 using Tapatalk 2
sanders858 said:
I, like the other guy have tried and tried this formula a ton of times. I always get the error "fastboot-mac: command not found"
Also, I cannot find that Flash Boot Script anywhere? Where do I get it?
Click to expand...
Click to collapse
Try this: cd to folder where your fast boot is, then type:
./fastboot-mac flash boot boot.img
Sent from my HTC One S using xda premium
copy file to phone
Hi,
So i unlocked my bootloader yesterday and flashed a custom rom and my phone was working fine. after this though i wanted to use cyanogen mod, so, using rom-manager i downloaded a stable build of cyanogen mod... since then when the phone starts up, it starts up in cyanogen but there are lots of problems...1.it doesnt recognise my sim.2wifi doesnt work.3 my htc one x now isnt being being recognised as a driver on my mac...so this means i can't easily download a new rom and try to flash that, nor can i connect it to a pc and move a new rom file into my phones storage....
i have been told i need to fastboot the phone and flash a new boot.img... so ive downloaded sdk now, and gone through all of the steps up until the instruction *copy rom file to phone*....any ways to work around this, as i cant simply just copy the file to my phone, i think ill need to use terminal or sdk, but im not proficient enough with either of these
thanks for any help u can give
Related
WOW AFTER AGES>>>>>>> FINALLY!!!! YAY!!!
First i would like to thank every one who made this possible , im sorry i dont know ur names..
This is what i did i dont know if itll work for every one but fingers crossed....
1. its like the normal rooting procedure except with the boot.img that i have!!! U need the sdk for this to work!!
2. Download superhero rom v2: http://www.megaupload.com/?d=3Y02RZAT
3. rename as update.zip and place on sdcard.
4. Shutdown phone.
5. Download: http://rapidshare.com/files/248983573/recovery-RAv1.0H.img
6. place this img in the tools folder of the sdk.
7. Start phone in fastboot mode (power+voulme)
8. from the fastboot menu in cmd restart phone with the boot image provided above. (c:\sdk\tools fastboot boot recovery-RAv1.0H.img).
UPDATE:: DO A NANDROID BACKUP THEN USE THE BOOT.IMG THAT WAS BACKED UP BY NANDROID (ON YOUR SD CARD) FOR STEP NUMBER 12/13/14..
9. wipe data and update .
10. reset phone but remove battery when the rogers sign comes on.
11. go to flashboot mode again.
12. .......... use backed up boot.img
13. place this in the tools directory of the sdk
14. in cmd again flash the boot image (c:\sdk\tools fastboot flash boot boot.img)
15. Now reboot and thats it ur done!!!!
NO WIFI!!!! NO BLUETOOTH IN THE SUPER HERO ROM AM TRYING OTHER ROMS... I THINK THIS METHORD SHOULD WORK AN ALL ROMS NOW... maybe not....
after trying for a while only superhero works not the hero by haykuro... dunno why it keeps restarting at the htc splash screen....
waiting nice
Thanks for using my recovery! lol
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
good job man, very interested in this but gotta wait till wifi works.
i think wifi dosent work becase superhero was for dream not magic... but the ui is sweet!
can someone help to enable wifi and bluetooth??
Oh wow, thanks. I will shortly follow your instructions.
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
haykuro said:
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
Click to expand...
Click to collapse
That is exactly why I am waiting for a proper release to come out.......hint
LOL
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part, used adb pull and push to copy over the file, but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld?? alsoo can u pls show me how to sign a package searched everywhere couldnt find out how...
re: TRIED THE wlan.ko file transfer still it says failed to start wlan!!!
Killadude said:
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
Click to expand...
Click to collapse
Yes, it works. Since June 8th ;-)
But daldroid-recovery is really a quick-mod of haykuro's one, so thank him (and others, I only mentioned him and a few others in a readme file in the ramdisk image)
I'm happy to see that someone else started releasing roms for pvt 32A board, because I was really busy and used all of my sparetime to try to rebuild a working kernel (Hero is running on my phone since 3 weeks, untested-bluetooth-fix, wlan fix, but still no working kernel, no iptables, so no release).
Going abroad for a few days, I'm sure I'll come back and be able to download your (or Haykuro's) new rom with a new built-from-sources-working-kernel for pvt32A ;-)
Greetings
Daldroid
Killadude said:
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld??
Click to expand...
Click to collapse
Im pretty sure he has
http://www.getyourdroidon.com/root/hero-sapphire-signed.zip
or did you mean a rogers specific one?
- Wifi and BT cannot start in this rom
yup one specific for rogers cuz our is the only goddam magic that couldnt until today be rooted!!
I just followed your instructions for the superherov2 rom and I ran into some problems.
I cannot upload the boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now my phone is stuck with the Rogers logo. Any ideas on how about I can go on fixing this problem.
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Killadude said:
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Click to expand...
Click to collapse
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
hotweiss said:
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
Click to expand...
Click to collapse
When you are in fastboot mode, "adb devices" won't show it. I THINK he meant "fastboot devices". It should show your devices in fastboot mode
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
hotweiss said:
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
Click to expand...
Click to collapse
Settings -> Wireless Controls -> Mobile networks -> Access Point Names
EDIT: read the NEXT post for the correct settings to put into the fields
Liberty still has something no other device has - ARIA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..........
Downloads:
cwm-5.0.2.3-liberty-agse.zip AGSE (ARIA) Edition - with cap key lights enabled
cwm-5.0.2.3-liberty.zip Stock Clockworkmod 5.0.2.3 - with cap key lights enabled
attn1 said:
Liberty still has something no other device has - ARIA!
Download: cwm-5.0.2.3-liberty-agse.zip
Click to expand...
Click to collapse
and apparently , interesting background images
*****
I am still on v2.5.0.1 - and help on how to install this img?
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
here's 2 ways to do it:
if you have s-off:
boot phone into fastboot mode
hook phone to computer with usb cable
ON COMPUTER:
unzip cwm-5.0.2.3-liberty-agse.zip
command prompt
fastboot flash recovery cwm-5.0.2.3-liberty-agse.img
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
tommyguns818 said:
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
Click to expand...
Click to collapse
yep, if you are s-off with Revolutionary or AlpharevX.
Nutshell69 said:
and apparently , interesting background images
Click to expand...
Click to collapse
that's Aria herself.
Looking forward to the HTC Jenna
Sent from my Liberty using XDA App
i was wondering.....i've got s-off but no computer around me at the moment. is there a way to install this through the terminal app? I see sObe did it via terminal way but im not sure if he's s-off or not.
EDIT: I went for it and did it through terminal just like sObe and I have s-off. Worked like a charm. Thanks guys!!!
When I chose internal card I get
E:Can't mount /emc/
???
s0be said:
here's 2 ways to do it:
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
Click to expand...
Click to collapse
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
If your doing it through terminal, you need to make sure that your doing it exactly as shown in s0bes post. Also make sure that you have your new cwm 5.0.2.3 download in the download folder on your sd card.
Nutshell69 said:
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
Click to expand...
Click to collapse
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Aside from the background thing, what advantages does this recovery have over 2.5.1.7? Is it faster? are the backups compatible?
T
s0be said:
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Click to expand...
Click to collapse
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Nutshell69 said:
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Click to expand...
Click to collapse
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
SoCalHTCFuze said:
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
s0be said:
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
Click to expand...
Click to collapse
In fact, you cannot flash a recovery without S-OFF, unless you use the original unrevoked tool and select custom recovery (the original unrevoked only managed to install a custom recovery which was good enough at the time).
The whole point of S-OFF is that you can flash the system partition. Like Gene said, if you don't have S-OFF, you'd need to unroot and use unrevoked again.
If you do have S-OFF, it's easy:
(OS X)
md5 /path/to/cwm-5.0.2.3-liberty-agse.img (confirm md5 sum)
./adb devices (confirm you're connected)
./adb reboot bootloader
./fastboot-mac devices
./fastboot-mac flash recovery /path/to/cwm-5.0.2.3-liberty-agse.img
./fastboot-mac reboot
./adb reboot recovery (wait to hit enter until the boot animation starts)
I haven't used it yet but I hear the backups are faster in 5.x
^^^ 5.0.2.3 is a little faster. I saw the new option to fix permissions in the recovery and tried it. Man it took like 30 min to run and chewed about 60 percent of battery. From now on I'll just use ROM manager. It never failed me and is way quicker. On further note....I like it. Go miss aria!
s0be said:
If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago.
Click to expand...
Click to collapse
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
drumist said:
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
Click to expand...
Click to collapse
egads - got this error
Error: failed to get root. Is your firmware too new?
As we all know, Android 4.3 brought with it some extra security features which caused some small issues with root. These have been solved by the likes of Chainfire and other developers, meaning we have root once more. This is their work, I've just botched it together to work on the Android x86 4.3 system, which works slightly differently
You will need:
A device with Android x86 4.3 on it
Optionals:
Another Linux based OS - this can be an OS on another partition on the device or a live disk/USB
Root permissions in that second OS and access to the terminal
Knowledge of which partition Android x86 is installed onto and which is its root folder (if you didn't mess with that, it tells you in the script)
Instructions:
On Android x86:
Download the attached zip and extract it using a file manager
Press Alt+F1 and use "cd" to change directory to where you extracted the zip
You should go as far in as the "README" and "install.sh" files
Run:
Code:
sh install.sh
Follow the instructions on-screen. It tells you the rest.
On a linux boot:
Download the attached zip and extract it to somewhere memorable
Open your terminal and use "cd" to change directory to where you extracted the zip. You should go as far in as the "README" and "install.sh" files
Run:
Code:
sh install.sh
Follow the instructions on-screen. It tells you the rest.
Reboot back into Android x86, it should have root now
Changelog:
v2:
Included version for Android x86 boot, through the Alt+F1 terminal
Made it a bit simpler
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits
@Chainfire for SuperSU and all the files included that the script installs
The SuperSU thread, don't forget to thank on there
The Android x86 project for the OS itself and the init.sh file, which is patched as the install-recovery file is
Hello..
I try to run the install.sh but it said
"This script needs root. Enter your password to continue:
sh: 0: Can't open .install.sh"
I ran it with sudo permission. My Ubuntu is on sdb6 and and android is on sdb7.
Please assist.
Just wondering? Can I just copy the the system folder and let it overwrite (merge) the system folder in the android partition. Also what permission do I need to change for what folder if I were to do this manually.
Thanks minhgi
It hasn't extracted properly, the .install.sh file is in the zip with the install.sh
Just in case, for the next release (in testing now, can be run from the Android x86 boot itself), I made it ./.install.sh, which should work
Here comes version 2:
Changelog:
Included version for Android x86 boot, through the Alt+F1 terminal
Made it a bit simpler
Thanks Quinny,
It is working. Somehow when I downloaded the attachment the first time, the script folder was not there. So there was not script to run. Anyway, I did it through the Ubuntu terminal it is working for me.
---------- Post added at 02:49 PM ---------- Previous post was at 02:29 PM ----------
Opps..I said it to soo. I using an android build 4.3 from www.tabletx86.org and it use chainfire SU. It also seem like your rooting method use chainfire su. When I try to use root explorer to enable r/w permission, the app just force close. Also I try to launch chain su, it also force close. I am not sure if there is an incompatibiltiy issue there. I use the rom build from tabletx86 b/c it have broadcom wifi working for my laptop.
The android 4.3 from android-x86.org does not. Can you test the build from www.tabletx86.org? it was compile on 08-02-2013.
Thanks again.
minhgi said:
Thanks Quinny,
It is working. Somehow when I downloaded the attachment the first time, the script folder was not there. So there was not script to run. Anyway, I did it through the Ubuntu terminal it is working for me.
---------- Post added at 02:49 PM ---------- Previous post was at 02:29 PM ----------
Opps..I said it to soo. I using an android build 4.3 from www.tabletx86.org and it use chainfire SU. It also seem like your rooting method use chainfire su. When I try to use root explorer to enable r/w permission, the app just force close. Also I try to launch chain su, it also force close. I am not sure if there is an incompatibiltiy issue there. I use the rom build from tabletx86 b/c it have broadcom wifi working for my laptop.
The android 4.3 from android-x86.org does not. Can you test the build from www.tabletx86.org? it was compile on 08-02-2013.
Thanks again.
Click to expand...
Click to collapse
I'll have a go at some point, I'm on a slow connection currently so it might be a while
Quinny899 said:
I'll have a go at some point, I'm on a slow connection currently so it might be a while
Click to expand...
Click to collapse
not a problem. Please take you time. these builts are are preview version anyway.
minhgi said:
not a problem. Please take you time. these builts are are preview version anyway.
Click to expand...
Click to collapse
I looked this morning and it can't be run from the boot as it's got a broken superuser installed which means I can't mount the system. Don't see why it would force close though
So I tried doing the script via alt+f1 and it says its in root, then when the script runs it shows that it cant mount permission denied and it fails to remove old files and fails to chmod also. Any help would be appreciated. Thanks
wolfballz said:
So I tried doing the script via alt+f1 and it says its in root, then when the script runs it shows that it cant mount permission denied and it fails to remove old files and fails to chmod also. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
If you're using TabletsX86's build, that's why, also, if you didn't allow /system to be mounted during install, then you're out of luck
Quinny899 said:
If you're using TabletsX86's build, that's why, also, if you didn't allow /system to be mounted during install, then you're out of luck
Click to expand...
Click to collapse
using latest build from android-x86.org and I didn't recall seeing anything about being able to mount /system during install.
wolfballz said:
using latest build from android-x86.org and I didn't recall seeing anything about being able to mount /system during install.
Click to expand...
Click to collapse
There is, right before you install.
Like so:
(Not my image)
Must have breezed right by it. Since i have it with windows how can i remove my current android install and start over? I ran the install again and i dont get that /system question at all.
So i tried installing on a virtual machine and i get the /system option now. Thanks for the help
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
After installing on a virtual machine and mounting /system thw script ran without error. Rebooted but didnt see a superuser app so i installed supersu. Installed and opened root explorer and when trying to mount anything RW it hangs and then root explorer says not responding. Anything else i can try?
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
Hello! I installed this, then a custom font. When I rebooted, I get stuck in a terminal. Any help?
Yoyodude1124 said:
Hello! I installed this, then a custom font. When I rebooted, I get stuck in a terminal. Any help?
Click to expand...
Click to collapse
Most likely the font. Did you set its permissions correctly?
Sent from my Galaxy Nexus using Tapatalk 4
Works perfect. I've used it twice now. Thanks.
If you get stuck in terminal you can type "start" to boot android.
Sent from my Lenovo Thinkpad Edge using Tapatalk 4
Unlockable bootloader/custom roms?
Is there any way to get custom recoveries on this, so we could install custom ROMs?
Yoyodude1124 said:
Is there any way to get custom recoveries on this, so we could install custom ROMs?
Click to expand...
Click to collapse
Nope. And there won't be ROMs like CM or the like, x86 is completely different to ARM and they're highly unlikely to make it compatible
I also only get the question whether to install /system as r/w with builds before 4.3. Using the boot image of 4.2 of course results in a mess but it takes me to the screen where I can choose to use system as r/w or read only.
Tried with a freshly fixed mbr and clean install.
Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out
jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
TexasPride, sorry I stepped in your thread.
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...
@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.
I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it
vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"
So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.
jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?
@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?
jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:
jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?
TexasPride
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
vp1117 said:
TexasPride
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.
@TexasPride
FYI: I no longer participate this hijacked thread.
My phone's LCD touchscreen is broken and the phone seems stuck in bootloop. I have access to a custom recovery (OrangeFox is installed, but I should be able to `fastboot boot` into any other).
I have read on this reddit post that it should be possible to flash a new ROM, push my computer's ADB public key to it, boot it and use `scrcpy` to control my phone.
However I'm stuck on the first step: how can I flash a new ROM to my phone via command line from OrangeFox or other recoveries?
You can't flash a Custom ROM via ADB, you've to do this via FASTBOOT or Custom Recovery.
xXx yYy said:
You can't flash a Custom ROM via ADB, you've to do this via FASTBOOT or Custom Recovery.
Click to expand...
Click to collapse
Yes, when I said "ADB", I meant the ADB of a Custom Recovery. I can boot into OrangeFox and then `adb shell` into it. I'm wondering how to install a ROM from there.
Installing the ROM from Fastboot would work too, if it's simpler.
TWRP uses dd to flash raw images and tar + gzip to backup/restore userdata partition. It's all done with shell scripting and adb shell is nearly the same.
@peoro The custom rom zip archive is build as OTA update.zip and either has a payload.bin (A/B slots) or *.dat.br compressed images for A-only devices. Both can be unpacked to get the raw images. Those images can be flashed via ADB or via fastboot.
peoro said:
Yes, when I said "ADB", I meant the ADB of a Custom Recovery. I can boot into OrangeFox and then `adb shell` into it. I'm wondering how to install a ROM from there.
Installing the ROM from Fastboot would work too, if it's simpler.
Click to expand...
Click to collapse
Don't confuse things:
Code:
adb shell
is used to run Android ( Linux ) system commands on Android devices.
WoKoschekk said:
@peoro The custom rom zip archive is build as OTA update.zip and either has a payload.bin (A/B slots) or *.dat.br compressed images for A-only devices. Both can be unpacked to get the raw images. Those images can be flashed via ADB or via fastboot.
Click to expand...
Click to collapse
Thank you for the replies. My phone is A-only (it's a Poco X3 Pro).
I just downloaded a new ROM (the latest crDroid 12 for my device) and I could find a number of `.dat.br` files in its zip:
Code:
$ unzip -Z1 crDroidAndroid-12.1-20230106-vayu-v8.12.zip | grep '.dat.br$'
odm.new.dat.br
product.new.dat.br
system.new.dat.br
system_ext.new.dat.br
vendor.new.dat.br
However I'm not sure where or how to flash these files and what other commands I need to use to e.g. format the various partitions or whatever is needed.
OrangeFox offers a `fox` command line tool (I believe it's a fork of TRWP's command). I believe it should help me with all of this, but I'm too much of a noob to know what to do and how.
Would you know where to find a good guide about installing a ROM via command line?
Otherwise could you tell me what commands I'm supposed to run and/or what operations I'm supposed to do?
I know my way around Linux pretty well, can write and read bash, but am a complete noob for anything related to android. Don't even know what the various partitions are, how they map to the contents of the drive and in general how the boot process works...
xXx yYy said:
Don't confuse things:
Code:
adb shell
is used to run Android ( Linux ) system commands on Android devices.
Click to expand...
Click to collapse
Yeah. ADB gives me access to a shell on the phone. I can have a shell while the phone is in the Custom Recovery (OrangeFox, currently) and I believe I should be able to flash a new ROM from there. That's what I'm trying to do.
Any way to install a new ROM would work for me: `dd`, the `fox` command line tool, or fastboot.
I'm good with bash, but don't know much at all about Android's internals. But I'd love to find a noob-friendly guide on how to flash to a ROM using whatever tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xXx yYy said:
Click to expand...
Click to collapse
Which part?
While my phone is running a custom recovery (OrangeFox, TWRP, whatever), that recovery is able to flash a new ROM. It offers a UI to do so. Right? I can't use the UI, but can run anything on the recovery, via the shell opened by ADB.
Am I saying anything wrong?
I have access both to `fastboot` and to the shell of a running custom recovery. But I don't know how to install the ROM (the content of crDroidAndroid-12.1-20230106-vayu-v8.12.zip ) with either tool, without using the custom recovery's UI.
peoro said:
I have read on this reddit post that it should be possible to flash a new ROM, push my computer's ADB public key to it, boot it and use `scrcpy` to control my phone.
Click to expand...
Click to collapse
The tool scrcpy installs *.odex compiled Java code on your device. This code isn't executable in any recovery.
Options for flashing your ROM:
– TWRP:
1. Put the raw images of your custom ROM into the ADB folder on your desktop and adb push them to the phone or use MTP to copy them.
2. Then you can use the openrecoveryscript.html (TWRP's commandline tool) to flash images.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
– ADB:
1. copy all raw images into ADB folder
2. use adb push to flash the images on your device.
– ABD (adb shell):
1. copy all images via adb push or via MTP to your device
2. enter the device's shell with adb shell
3. You said you are familiar with bash scripting. Do you know the dd command and its syntax?
CAUTION: The command dd overwrites EVERYTHING and without a warning!! Be careful and only use it if you know what you're doing.
Creating RAW images:
You need this tool to convert *.dat.br to raw image.
Flash custom ROM via fastboot:
1. convert the *.dat.br to RAW images.
*.dat.br filesRAW imagespartitionodm.new.dat.brodm.imgodmproduct.new.dat.brproduct.imgproductsystem.new.dat.brsystem.imgsystemsystem_ext.new.dat.brsystem_ext.imgsystem_extvendor.new.dat.brvendor.imgvendor
2. Use command
Code:
fastboot flash PARTITION RAW_IMAGE
to flash them all.
xXx yYy said:
Don't confuse things:
Code:
adb shell
is used to run Android ( Linux ) system commands on Android devices.
Click to expand...
Click to collapse
Using ADB commands or adb shell to run commands in the device's shell (#!/system/bin/sh) doesn't matter. Both passing commands through adb.exe to the adbd on the device. Killing the adbd will kill the connection anywhere.
You must NOT teach me what ADB is and/or how it works.
WoKoschekk said:
The tool scrcpy installs *.odex compiled Java code on your device. This code isn't executable in any recovery.
Options for flashing your ROM:
– TWRP:
1. Put the raw images of your custom ROM into the ADB folder on your desktop and adb push them to the phone or use MTP to copy them.
2. Then you can use the openrecoveryscript.html (TWRP's commandline tool) to flash images.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
– ADB:
1. copy all raw images into ADB folder
2. use adb push to flash the images on your device.
– ABD (adb shell):
1. copy all images via adb push or via MTP to your device
2. enter the device's shell with adb shell
3. You said you are familiar with bash scripting. Do you know the dd command and its syntax?
CAUTION: The command dd overwrites EVERYTHING and without a warning!! Be careful and only use it if you know what you're doing.
Click to expand...
Click to collapse
Thank you a lot for the detailed answer.
I used the TWRP approach as it seems the simpler.
I know `dd` and can read its man, but I'd rather not mess with the phone's partitions and block devices, unless it could result in a different outcome than using the `twrp` tool.
I tried to install two different ROMs (Lineage and crDroid), but neither manages to boot.
I can see that the few visible pixels on the broken LCD are in different colors for the two ROMs (so it did manage to install something), but neither ROM ever reaches a point where the power button turns the monitor on or off: they're both stuck on the bootloader.
What I did is basically this:
Bash:
$ twrp wite cache
$ twrp wipe system
$ twrp install $ROM.zip
$ twrp format data
$ twrp wipe dalvik
$ twrp wipe cache
$ reboot
If that's a correct way to install a ROM, then I guess I have my answer: some of my phone's hardware is broken
peoro said:
What I did is basically this:
Bash:
Click to expand...
Click to collapse
Use the adb sideload option to flash your ROM. That's the usual way to install it.
Code:
adb shell twrp sideload # to activate the process on client
adb sideload <ROM_PACKAGE> # to activate the process on host
Flashing starts automatically.
xXx yYy said:
You must NOT teach me what ADB is and/or how it works.
Click to expand...
Click to collapse
I'm not teaching. I just gave arguments.
peoro said:
If that's a correct way to install a ROM,
Click to expand...
Click to collapse
Yes, it's the correct way to install. All you need to wipe/format is data.
peoro said:
I tried to install two different ROMs (Lineage and crDroid), but neither manages to boot.
Click to expand...
Click to collapse
Seems you already found the solution yourself
How do you know the ROM does not boot? note first boot takes up to 10 minutes.
alecxs said:
Seems you already found the solution yourself
How do you know the ROM does not boot? note first boot takes up to 10 minutes.
Click to expand...
Click to collapse
When the screen broke, I could tell that the ROM didn't work, because:
1. My phone didn't connect to my router. I can tell by looking at the router's log or at internet services that tell me the last time the device was online.
2. If I try to call or send SMS to SIM on the phone, the phone doesn't ring or vibrate.
3. The screen never turns off. Not even when I press the power button.
All those points still hold with the newly flashed ROM too. Of course now it can't connect to anything, but it still doesn't react to incoming calls or to the power button.
I can kinda see from the glitchy colors on the bottom of the broken LCD that the bootloader animation is displayed, but it seems that it's stuck there...
If you have any ideas on how to debug this, I'm very interested.
This is a dump of `dmesg` (from the custom recovery). It shows a bunch of errors, but I can't tell whether any is about real hardware issues.