Related
I've been searching XDA endlessly to answer this question or to point me in the right direction and have had no luck.
Basically, I know JF etc can modify the OTA updates so that they can keep root, but I can't find out how they actually go about doing it.
Since I'm a dev myself, I would like to have a crack at modding the updates. I know that JF created a modded recovery image signed with test keys so that you can update any update.zip signed with the same keys. (<- I'd quite like to know how this was done also). But it's the keeping root on update.zip that I want to know how to do and not just by using JF's build enviroments. Ie which files in update.zip need modifying etc....
Does that even make sense? Any help would be much appreciated or if anyone can point me in the right direction...
Many thanks
first you have to make a copy of sh and name it su and put it under /system/xbin
then you'll have to modify the update script buried in meta-inf and ask it to grant that su (and presumbly adbd) 4755 permission uid=0 gid=0
forgot this: resign...
Also need to unpack boot.img and change adb persist and secure.
bp8575 said:
I've been searching XDA endlessly to answer this question or to point me in the right direction and have had no luck.
Basically, I know JF etc can modify the OTA updates so that they can keep root, but I can't find out how they actually go about doing it.
Since I'm a dev myself, I would like to have a crack at modding the updates. I know that JF created a modded recovery image signed with test keys so that you can update any update.zip signed with the same keys. (<- I'd quite like to know how this was done also). But it's the keeping root on update.zip that I want to know how to do and not just by using JF's build enviroments. Ie which files in update.zip need modifying etc....
Does that even make sense? Any help would be much appreciated or if anyone can point me in the right direction...
Many thanks
Click to expand...
Click to collapse
Look in the init.rc startup script. You could probably setuid sh.
The truth is out there...
http://forum.xda-developers.com/showthread.php?t=518251
This could be considered part of the development forum or the apps and theme forum depending on how you look at it. if you have an issue, just click the report button and request that it be moved. no need to flame and troll and post that you reported it, just do it and move on.
Lots of people have asked me how to put together a theme control file, and its actually VERY easy but this tool makes it even easier.
this is an example of a theme control file created by this tool
Test-Theme.xml
Code:
<themename>Test-theme</themename>
<author>tater-salad</author>
<phone>Android Phone Codename Hulk</phone>
<rom>CM 8</rom>
<item>Phone.apk</item>
<path>/system/app<path>
<item>framework-res.apk</item>
<path>/system/framework</path>
<description>Requires reboot</description>
<item>FM-Reciever.apk</item>
<path>/data/app<path>
<item>My-custom-app.apk</item>
<path>/data/app<path>
run the mm-builder script and follow the on screen directions. you will of course need to put the correct replacement files in their respective directories, but this script will make all the right folders and set up your theme.xml for you. Bash scrip means linux only. This is also a super easy script, so i may get a batch version soon.
You can extract this file to any directory
All thanks to Stericson. W/O him we wouldnt have a metamorph app to begin with
######################################################################################################
v2
includes these additions
Code:
mkdir $app
mkdir $app/res
mkdir $app/res/drawable
mkdir $app/res/drawable-mdpi
mkdir $app/res/drawable-land-mdpi
mkdir $app/res/drawable-port-mdpi
these are the commonly used directories when it comes to theming. now all the sub-folders should be set up right.
I think this tool will be very helpful for newer themers and the like, looking forward to a windows adaptation.
also, what does it matter if ban_dover was andrizoid, seems to me hes not doing any harm here now, just trying to help people out, so give a guy a chance to rectify himself before you all start the flamethrowers
snyluc13 said:
I think this tool will be very helpful for newer themers and the like, looking forward to a windows adaptation.
also, what does it matter if ban_dover was andrizoid, seems to me hes not doing any harm here now, just trying to help people out, so give a guy a chance to rectify himself before you all start the flamethrowers
Click to expand...
Click to collapse
windows version is certainly viable, but batch is SO alien coming from bash. there isnt even an ls command
im going to have to play around and get a feel for batch before i get to work on it.
v3 is up. ive put together working metamorph themes using v3, so its been pretty well tested.
How about some constructive use of this thread?
ban_dover,
I've got a question. I read through Stericson's announcement post on XDA, and also the project page, and he mentions limitations due to signing checks of market apps.
Does it actually re-sign the .apk with the test key that all the devs use, or does it merely re-zip the .apk so that the manifest and keys are broken (won't pass a jarsigner -verify test)?
If it is the 2nd alternative, I guess that would means that Android does not check "non-market app" installs for valid signatures? Or that it doesn't check system apps but does check market apps?
The reason this piques my interest is that I noticed one of the devs recently released a ROM which had all its apps de-odexed and re-signed with the test key. (Can't remember which ROM, perhaps an xtr* ROM?)
Anyone else that knows how this goes is welcome to answer as well.
bftb0
Im going to lock this thread if the flame war doesn't stop
Play nice
Edit: Thread re-opened, ban_dover and I discussed and hopefully we will not have any more issues.
Thanks
Captainkrtek
bftb0 said:
How about some constructive use of this thread?
ban_dover,
I've got a question. I read through Stericson's announcement post on XDA, and also the project page, and he mentions limitations due to signing checks of market apps.
Does it actually re-sign the .apk with the test key that all the devs use, or does it merely re-zip the .apk so that the manifest and keys are broken (won't pass a jarsigner -verify test)?
If it is the 2nd alternative, I guess that would means that Android does not check "non-market app" installs for valid signatures? Or that it doesn't check system apps but does check market apps?
The reason this piques my interest is that I noticed one of the devs recently released a ROM which had all its apps de-odexed and re-signed with the test key. (Can't remember which ROM, perhaps an xtr* ROM?)
Anyone else that knows how this goes is welcome to answer as well.
bftb0
Click to expand...
Click to collapse
to be honest im not sure. but i can say that the rom your talking about isnt going to have any issues with anything because of the re-signing.
so the those who have downloaded it, what do you think?
ive tested it by putting together a few simple MMs, and it worked fne for me. have any of you ran into any issues?
This is my easy-rooter for the Thunderbolt. I do not personally have a thunderbolt but I have tested it and fixed as many problems as I could. As far as I'm aware this will only work with firmware versions lower than version 1.12.605.9.
If adb does not see your device try installing the htc sync drivers. If that doesn't wok install PDA.net. If it still does not register please post here. If you have a 64-bit version of windows replace the files in the rar with these
THIS IS A WINDOWS-ONLY PROGRAM. You must have windows or a windows VM to use this.
As always there is a small chance of bricking your phone.
DISCLAIMER: AndIRC is not affiliated with this program and by using it you agree that neither AndIRc nor myself is responsible for any damages caused by this program.
This provides all necessary files and gives you in-program instructions.
Please read this before using this.
Known bugs:
Sometimes you need to redo step 3. If the phone does not reboot on its own simply press the step 3 button again.
Issues:
The files take a long time to push. It could be anywhere from 3-10 minutes.
Once you have completed step one do not redo it for any reason! If it flashes only continue from step 2!
Credits:
Team AndIRC - for developing the root method found here
XDA - for giving me the chance to make programs like this
me - for making it
Donations:
Please donate to charity first and myself only if you want to. Please make donations in AndIRC's name as well as your own. You can donate here, to the Japan Relief Fund, or any other worthy charity.
since I just saw jcase's thing about my donation link (apparently I'm blind) here it is for those of you who wish to donate to me.
Downloads:
http://www.megaupload.com/?d=28H4U0QS
mirrors:
Instructions:
For those of you who can't follow or understand the directions in the program here is a pdf with instructions.
For anyone having problems getting steps 1 and 2 to work the first time through here's something to try.
lado44 said:
Hey man, I'm new so can't post in dev forum.
Your method worked for me - one thing I found. It was hanging at step 1 like some folks have reported, pushing the files (could see .ZIP on SD card), but would fail to reboot. This happened several times with Fast Boot enable under Settings>Applications. When I unchecked Fast Boot and re-ran Step 1 it worked first try. Couldn't tell you why or if just coincidence, but might help others.
Cheers.
Click to expand...
Click to collapse
For those of you who are interested in how this method works, here's the explanation. I will be focusing on what the program does,not user interaction so much except where necessary.
Push busybox, psneuter,and misc.img to /data/local/
Push PG05IMG_downgrade.zip to /sdcard and rename to PG05IMG.zip
chmod psneuter and busybox
execute psneuter
check the md5 hash of misc.img
flash misc.img to /dev/block/mmcblk0p17 if the hash is c88dd947eb3b36eec90503a3525ae0de
reboot into the bootloader
press power to enter bootloader and flash PG05IMG.zip (done by user)
once back in android:
remove PG05IMG.zip
push busybox, psneuter, and wpthis to /data/local
chmod all 3 files
run psneuter
run wpthis
push the engineering hboot(hbooteng.nb0) to /data/local/
check the md5 of the hboot file (it should be 6991368ee2deaf182048a3ed9d3c0fcb)
if it is flash hbooteng.nb0 to /dev/block/mmcblk0p18
push the PG05IMG.zip file to /sdcard
reboot into the bootloader
again press power and flash PG05IMG.zip (done by user)
push su, busybox, and psneuter to /data/local
chmod psneuter and busybox
run psneuter
mount /system as read/write (rw)
copy su to /system/xbin/su
chown and chmod su
install superuser and RomManager
Click to expand...
Click to collapse
I do recommend learning ADB as it is quite helpful but I realize that for some people that is a daunting task at first glance. I remember being a n00b and this will allow you to fully utilize your phone while still learning at your own pace on the side.
I am attaching just the updated exe.
Great idea showing what happens. Cool that you put something together for TBOLT owners, I just hope people will try and figure out what is going on when they use this.
After seeing a lot of issues people having with setting up adb I guess I should share this link... ADB For Dummies by AndroidSamurai
Even has an app to set everything up in the right spot.
This is a great thread on altering the android_winusb.inf for compatibility with Thunderbolt (adb driver).
<open>Can of Worms</open>
Thanks for the hard work.
One of the conditions for release was that I explain what happend. Hope this helps people out.
Nicely done. thanks for your hard work and knowledge. Now to get adb up and running finally.
You're welcome, and if the program functions properly you shouldn't need to setup adb beforehand as it comes with the necessary files for interaction. If it doesn't work properly try the debugging steps I posted in the OP and if that doesn't work setting up adb as a system command (adding the tools folder to PATH) should fix things.
^Thank you kind sir. I plan on giving this a spin tonight.
Ooking o walk a friend through this.later on tonight. And he camt boot into to the bootloader so im anxious to hear any feedback about this. If u guys dont mind please post anything you feel needs to be known about this, or just post that it rocks ass
Sent from my ADR6400L using XDA App
Hey guys, I didn't think about it when I created the thread but I want to have a bit of a poll here. If it works post here letting us know, and I'm fairly certain if there's a problem I'll hear about it so I don't think I need to say anything about posting them
Don't let dbzfanatic marginalize himself, don't forget some donations for him. (kinda hard to find his link in his post).
I hope it won't brick any phones. You're up on AP now - http://www.androidpolice.com/2011/0...en-tried-and-true-meets-new-and-blazing-fast/
I saw that. In my test group I had no reports of bricks, just random quirks which I have sense fixed (except those listed in the OP).
need to find an excuse to get off work early now...
Is firmware version the same as software number ? . My software number is 1.12.605.6 .
Yes it's the same, you should be fine to use this.
Looks awesome, but I'll still wait until all of the kinks have been worked out.
Since this uses the same method as manual root, it SHOULD continue to work until gingerbread.
awesome, cant wait to get outta work!
Does this wipe the phone like the manual adb does?
Yes, it's exactly the same method, just automated to make things easier.
BTW what do you mean "ADB needs to be setup as a system command"?
My ADB works properly and I can see the device so I assume that's the one I'd need to download and not the one that says "ADB need not be previously setup"?
I have searched, read, and tested my butt off on this so, I'm not posting without doing my own homework. I promise.
I'm looking for CURRENT documentation on how to create a standard update.zip file that simply copies a file into /system/foo/bar and chmods it.
All the links I've looked at seem to have old deprecated syntax on the update-script file, or the examples given simply do not work.
I do NOT want to download someone else's script-pak, windows app, or any other such thing that makes it for me.
As for signing, I'm completely comfortable signing using the SDK, although I'll probably take the easy route with ZipSigner/Signapktic running on the phone/tab now that I've discovered those.
Can someone please post a very simple howto?
Thanks for posting this -- I'm with you, I'm not a script-kiddie using someone else's tools, I want to learn it for myself, but like you, I've searched, and what I've found -- while probably correct and accurate -- isn't working the way they say it should. I've even followed the directions on android.com itself and they fail, so I'm starting to suspect my recovery or my ROM is at fault, not the signing itself.
I have a bunch of files I want to place in /system/foo/bar and chmod, as you say, and the error I'm getting is "No signature (172 files) Verification Failed". I do indeed have signatures in the file, as when I open them I see CERT.RSA and others that weren't there before signing, so IDK what the deal is with the error I'm getting (obviously something's missing -- maybe a public key verification from a trusted authority like Thawte or VeriSign).
I see you, too, are getting as much help as I am seeing others get. They start threads, get all sorts of praise from script kiddies who have no clue and just see a point-click solution, and then someone asks for real help and everyone shuts up for months until the thread eventually dies.
But kudos to you, sir, for being in the same boat as I!
cj chitwood said:
Thanks for posting this -- I'm with you, I'm not a script-kiddie using someone else's tools, I want to learn it for myself, but like you, I've searched, and what I've found -- while probably correct and accurate -- isn't working the way they say it should. I've even followed the directions on android.com itself and they fail, so I'm starting to suspect my recovery or my ROM is at fault, not the signing itself.
I have a bunch of files I want to place in /system/foo/bar and chmod, as you say, and the error I'm getting is "No signature (172 files) Verification Failed". I do indeed have signatures in the file, as when I open them I see CERT.RSA and others that weren't there before signing, so IDK what the deal is with the error I'm getting (obviously something's missing -- maybe a public key verification from a trusted authority like Thawte or VeriSign).
I see you, too, are getting as much help as I am seeing others get. They start threads, get all sorts of praise from script kiddies who have no clue and just see a point-click solution, and then someone asks for real help and everyone shuts up for months until the thread eventually dies.
But kudos to you, sir, for being in the same boat as I!
Click to expand...
Click to collapse
See my other reply to you in a similar topic.
I may be wrong but dont you have to sign system apps with the same key that the rom was signed with.
You can compile and sign from source and then add system apps or data
From something awesome
killersnowman said:
I may be wrong but dont you have to sign system apps with the same key that the rom was signed with.
You can compile and sign from source and then add system apps or data
From something awesome
Click to expand...
Click to collapse
System apps must be signed using the same key that is used to sign the platform. This has nothing to do with the ZIP signature that may or may not be present on a recovery update. The actual platform public key is stored within the ROM and gets extracted just like any other file in the system image.
If you compile from source, you use the platform key provided in the source; typically: build/target/product/security/platform.x509.pem. If you are an OEM like say HTC, you'll use your own key to compile the platform and sign the system apps.
Gene Poole said:
System apps must be signed using the same key that is used to sign the platform. This has nothing to do with the ZIP signature that may or may not be present on a recovery update. The actual platform public key is stored within the ROM and gets extracted just like any other file in the system image.
If you compile from source, you use the platform key provided in the source; typically: build/target/product/security/platform.x509.pem. If you are an OEM like say HTC, you'll use your own key to compile the platform and sign the system apps.
Click to expand...
Click to collapse
So in order to put ringtones in the appropriate system folder, I have to sign the update.zip with the same key that e.g. Roalex uses to sign the ROM? Of course that won't work, as I don't have his key, and then there are kernels and themes that other people make that work, and surely they don't have Roalex's key.
So I think I'm misunderstanding this still.
But if I compile from source, I sign with the key that's in the source, so if I know Roalex compiles from source, if he signs with the source key, I can sign an update.zip with that key and it will work?
Also, Recovery says there is NO signature in the file, but does that not necessarily mean really what it says?
I don't know who Roalex is. I don't know anything about your device per se. I don't know anything about Amon-Ra recovery. I was hoping some others would jump into this thread to help out with these unknowns. I've always used clockworkmod recovery so that's all I can speak for, but I did D/L an Amon-Ra recovery to analyze it.
As far as custom ROMs go, most are based on some OEM ROM and still contain system files signed by the OEM and the OEM certs are still included with the ROM so no modifications are necessary.
If you have a simple update.zip with just some files to be written to the system partition, then signing the update.zip file is unnecessary. A signed update.zip is only useful when it is distributed by an OEM with an official OEM update since the stock recovery will refuse anything not signed by the OEM. One of the reasons for using a custom recovery on rooted devices is that it gets around this security check to allow you to install custom stuff written by someone other than the OEM.
If you are having trouble installing an update.zip that contains an otherwise valid working "amend" or "edify" script, then I don't know what the issue might be. Clockworkmod recovery (at least all the versions I've run) has an option to toggle signature checks in the "apply update from SD card" sub-menu, but I don't know of any good reason that it is there since it only has one key and it is the same "test" key distributed in official source distributions, and the toggle is off by default.
I've been poking around github and grabbed the current source for amon-ra recovery (https://github.com/packetlss/amonra_bootable_recovery) and interestingly, amon-ra has a signature verifyer that is missing from clockworkmod recovery. It actually parses the zip file for the META information and ensures that the included signing key for the zip is consistent with the manifest and each file's signature.
So, it would seem that your update.zip should be signed the same way an APK is signed, using jarsigner.
Do you have a valid signing certificate and are you signing your update.zip correctly?
After learning to compile cm from source I found it easiest just to edit the .zip and then resigning the zip. I have added a few programs into /system and never had an issue. Perhaps this is because it's cm?
Gene Poole said:
I've been poking around github and grabbed the current source for amon-ra recovery (https://github.com/packetlss/amonra_bootable_recovery) and interestingly, amon-ra has a signature verifyer that is missing from clockworkmod recovery. It actually parses the zip file for the META information and ensures that the included signing key for the zip is consistent with the manifest and each file's signature.
So, it would seem that your update.zip should be signed the same way an APK is signed, using jarsigner.
Do you have a valid signing certificate and are you signing your update.zip correctly?
Click to expand...
Click to collapse
i was just going to conjecture that perhaps the amon-ra recovery is verifying sigs. you however have found proof. thank you
the only way someone would have the valid sig is for it to either be public, or for them to have signed the platform themselves and have there own private key. i ran into this same problem when investigating the android.intent.action.REBOOT intent which can only be broadcast by system apps signed with the same sig as the platform.
Gene Poole said:
I don't know who Roalex is [...]
Click to expand...
Click to collapse
Sorry, he's the guy who put together the COS-DS ROM for G1/HTC Dream based on CyanogenMod and AOSP sources.
Gene Poole said:
As far as custom ROMs go, most are based on some OEM ROM and still contain system files signed by the OEM and the OEM certs are still included with the ROM so no modifications are necessary.
Click to expand...
Click to collapse
Wait... can signing the zip be as easy as including the CERT.MSA and related other two files as found in the other update.zip files I have that work? Seems that would be too easy... I assumed there would be something in the zip file headers that would be modified to reflect a key as well so that they would also have to match. Maybe this is getting too in-depth...
Gene Poole said:
If you have a simple update.zip with just some files to be written to the system partition, then signing the update.zip file is unnecessary.
Click to expand...
Click to collapse
So just put together a common zip file with the update-script and the right folder structure in it, and I'm good? I tried that too and it also failed. Does the NAME of the file have to be update.zip in that case, though? I didn't actually try that. My unsigned one was named "CJ-Audio-Update_unsigned.zip" or something like that.
Gene Poole said:
A signed update.zip is only useful when it is distributed by an OEM with an official OEM update since the stock recovery will refuse anything not signed by the OEM. One of the reasons for using a custom recovery on rooted devices is that it gets around this security check to allow you to install custom stuff written by someone other than the OEM.
If you are having trouble installing an update.zip that contains an otherwise valid working "amend" or "edify" script, then I don't know what the issue might be. Clockworkmod recovery (at least all the versions I've run) has an option to toggle signature checks in the "apply update from SD card" sub-menu, but I don't know of any good reason that it is there since it only has one key and it is the same "test" key distributed in official source distributions, and the toggle is off by default.
Click to expand...
Click to collapse
Okay then. From here it's a lot clearer than a week ago. Thanks for taking the time to explain it so thoroughly... I think so many people understand so little and they're so quick to say "here, just use this other guy's tool LOL!!!111!1 he r0x0r$!!!1!1". I mean, that's great, that there are tools, but I want to understand it, not just be a script kiddie with someone else's tools, blindly trusting that they're doing it right and all that. Not saying the tools are bad or wrong, but by knowing myself, I know whether it's done right, you know? Same reason I learned automotive mechanicals, computers, and electrical wiring. Oh, and plumbing is slowly being added and in a few years roofing
Then it's on to framing as I build a 20-by-20-foot "workshop" in the back yard but I digress...
Thanks again!
Well this is interesting...
I took the MSA and other two files from the COS-DS update, and put them in a new zip containing my other files (not signed) and it didn't complain about no signature... instead, it failed saying some lib file is missing. Stagefright or some such. Progress is still progress though...
EDIT:
Okay, so it looks like there's something in those signats that says, "hey, look for all these other files too", so I'ma try a different tack...
EDIT2:
I guess I'm just gonna have to use Testkeys. They appear to have worked. :/ But if everyone else is doing it that way, I guess there's no harm.
OK i got a MT4 so i flashed the engineering bootloader, since it wasn't my first mytouch 4, i already had the files in my computer, so somehow my files got corrupted thanks to the new SSD technology, so now i have a phone that won't turn on at ALL.
Any way to recover from this one or the board is tossed? any way to save it with a JTAG?
thx
greenstuffs said:
OK i got a MT4 so i flashed the engineering bootloader, since it wasn't my first mytouch 4, i already had the files in my computer, so somehow my files got corrupted thanks to the new SSD technology, so now i have a phone that won't turn on at ALL.
Any way to recover from this one or the board is tossed? any way to save it with a JTAG?
thx
Click to expand...
Click to collapse
I don't know of any way to save it through software. You'd need the bootloader in order to use fastboot.
Advice for everyone:
Before you flash that bootloader, verify it by comparing it's md5 checksum to the one provided in grankin's thread. If you can't find it, this is it:
Code:
md5sum: df4fd77f44993eb05a4732210d2eddc6
I check mine at least once before and ALWAYS check after flashing. Here's how:
1. On your computer, after downloading. Mac/Linux users can probably do checksums in terminal. I downloaded a checksum utility for Windows that adds a checksums tab when I right-click >> properties on any file.
2. On the phone with terminal emulator. Assuming you pushed the file to /data/local, open terminal emulator and do this:
Code:
cd /data/local
md5sum hboot_dhd.nb0
If what you get does not match the above, re-download the file.
3. After flashing. You can enter the path of the bootloader as the argument for md5sum. This is ALWAYS a good idea to make sure it was written properly, even if you checked it already in /data/local. The command (in terminal emulator) is this:
Code:
md5sum /dev/block/mmcblk0p18
If what you get does not match the above, DO NOT REBOOT THE PHONE. Re-download the file if you have to and flash again. Only reboot if md5sum matches the above.
jdkoren said:
I don't know of any way to save it through software. You'd need the bootloader in order to use fastboot.
Advice for everyone:
Before you flash that bootloader, verify it by comparing it's md5 checksum to the one provided in grankin's thread. If you can't find it, this is it:
Code:
md5sum: df4fd77f44993eb05a4732210d2eddc6
I check mine at least once before and ALWAYS check after flashing. Here's how:
1. On your computer, after downloading. Mac/Linux users can probably do checksums in terminal. I downloaded a checksum utility for Windows that adds a checksums tab when I right-click >> properties on any file.
2. On the phone with terminal emulator. Assuming you pushed the file to /data/local, open terminal emulator and do this:
Code:
cd /data/local
md5sum hboot_dhd.nb0
If what you get does not match the above, re-download the file.
3. After flashing. You can enter the path of the bootloader as the argument for md5sum. This is ALWAYS a good idea to make sure it was written properly, even if you checked it already in /data/local. The command (in terminal emulator) is this:
Code:
md5sum /dev/block/mmcblk0p18
If what you get does not match the above, DO NOT REBOOT THE PHONE. Re-download the file if you have to and flash again. Only reboot if md5sum matches the above.
Click to expand...
Click to collapse
Wow, thank you for this!
Phateless said:
Wow, thank you for this!
Click to expand...
Click to collapse
+2 same here
Phateless said:
Wow, thank you for this!
Click to expand...
Click to collapse
No problem, if it helps people avoid bricking their phones.
greenstuffs said:
OK i got a MT4 so i flashed the engineering bootloader, since it wasn't my first mytouch 4, i already had the files in my computer, so somehow my files got corrupted thanks to the new SSD technology, so now i have a phone that won't turn on at ALL.
Any way to recover from this one or the board is tossed? any way to save it with a JTAG?
thx
Click to expand...
Click to collapse
Same here. Screen lights up but just blank when power button is pressed. Power + volume down doesn't work. Power +volume up makes the phone vibrate though but I dunno what that means. PC can't detect the unit via USB, tried ADB devices but no success.
Bricked forever? what's the cure??? help?