Related
Hey guys
1) Restarted my phone today using CM10.1 from a very recent nightly (within the past week).
2) On restart, phone froze and got kernel panic.
3) Restarted into CWM and tried to do a restore to an earlier backup I had made.
4) Half-way through the restore, I got ANOTHER kernel panic (never had that before)...
5) Only things I could do with the phone after that was enter download mode...nothing else...couldn't enter recovery mode anymore.
6) Went into download mode and flashed this CWM-Recovery (http://forum.xda-developers.com/showthread.php?t=1118693) and followed the instructions to the letter.
7) Odin 3.07 hung on NAND Write Start
8) Tried using Odin 1.3, and it seemed to flash correctly. It says completed no errors.
Phone will now not even start and is completely unresponsive...pressing any combination of buttons will not start the phone, and the phone is not recognized in Odin anymore...did I just hard brick it? Any other ideas?
Thanks,
Elliott
Service centre. Although if you can have someone who does JTAG's have a look at it to determine whether it can be JTAG'd without you giving them any money up front (I.E you only pay them if it can be JTAG'd), try that first.
Thanks that's what I thought.
Also, try a jig if you can get one. In all likelihood won't work, but stranger things have happened & you have nothing to lose.
Yeah thanks that's what I plan on doing. Any idea what I did wrong, though? I don't want it to happen again if I get it working with a jig.
Impossible to say. Not sure why you flashed that nondescript kernel/recovery in that situation tho given it probably wouldn't have worked even if the flash had been successful (You would probably have ended up with bootloop given recovery was obviously 'broken'). I would have flashed stock with Odin (And that's certainly what I tell people in your situation on here to do because it normally works).
But flashing recovery rather than a stock rom probably didn't break your phone, put it that way, so you didn't do anything 'wrong' per se. Just remember if you get into a similar situation again, go back to stock via Odin & start again (re-root your phone/restore a backup, flash your custom rom/kernel again, etc).
If the jig works (and don't get your hopes up or anything, we're talking a 1 in 10,000 chance, and that's probably being generous), flash stock with Odin (you wont have much choice).
Well...brought it to a JTAG specialist today and he couldn't fix it either...says it's very rare and he's had 5 out of 80 S2's like this happen without being able to fix them...
Bummer. Motherboard replacement in that case. If the phone's under warranty, take it to a service centre & say as little as possible. You might blag it for a warranty fix. No warranty ? You can still have a new motherboard put in by a service centre (more expensive option usually), or you can source a 2nd hand MB from a 'donor' phone (one with a broken screen that's otherwise OK, etc) & either swap it in yourself or pay a local mobile repair shop to do it (usually cheaper option).
@ OP By following what you flashed I noticed the date, we're talking about a 2 years old thread, a lot have changed since.
Not sure that was what bricked your device but I get that panic mode.
The other thing that it comes to mind is nand corruption, which has been quite common these days with people running custom.
I'm with bungle there, the best recovery package is going back to stock and start fresh.
I, on the other hand, wouldn't accept the situation you are on, I would spend a whole week trying to get that phone to boot again, whether a second opinion on a jtag, a new jig, another battery or any other thread on here at xda.
If the device gets hot near the rear camera and it won't even charge nor get warm around that area dismiss what I just said and proceed with the mobo replacement bungle suggested.
And of course, if you did something else to your device and didn't share it please, come clean so others don't freak out by reading this.
Sent from...this is not even my S2
Hey
Nothing else was done to the device...just what I stated exactly.
I caved today and bought a BNIB S3 because I couldn't go without a phone anymore...
Thanks for the help, guys
Elliott
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
So I posted the following on a few other places
(please expand)
I am in desperate need of help . Yesterday, I woke up and went on my phone and it was acting strange. It was saying that apps that I wasn't using had stopped working or something like that, which was pretty weird, so I decided to restart it. However, when I tried to turn it on again, it got to the carrier screen (I have AT&T) it didn't do anything after. It just stayed on that screen and vibrated in a pattern. I was able to hold home + power + volume down to restart it, and I was able to get to the recovery options screen. I tried clearing the cache and all the data, but no luck. I tried flashing the stock firmware but I couldn't find anything new enough. I had rooted my phone about 5 days earlier, but it had worked perfectly fine up until yesterday. I tried everything I could think of and find online. I recently called AT&T up and they're sending me a new phone, but I have to send my phone to them, and I feel almost certain that they'll find that I've been messing with it. Whether it's the giant lock with the word "Custom" above it, or something in the files. I have 10 days to send it in to them and I need a way to either fix my phone, or wipe ALL of my phone's data before then, but I feel like completely wiping everything might void the warranty as well. I'm not even sure that the root caused the problem.
I do have friends who have the same phone as me, would it be possible to somehow get the most recent firmware off of one of their phones and get it on to mine? I have the G930A and I couldn't find firmware recent enough for my device. I have read A LOT about this issue in the past day and I vaguely remember something about being able to get someone at Best Buy or some other store to flash the most recent firmware onto the phone? Is something like that possible?
Please help, I can't afford the $600+ if it doesn't pass. Any and all ideas are welcomed. Thanks .
After reading some stuff here, I have found out that I can somehow make a backup of the stock firmware. I wouldn't actually be using my phone to make the backup since I don't actually have the stock firmware. I wouldn't be using my phone to make the backup, I have friends with the same phone and carrier. All I need is direction on how to do it. I have a Galaxy S7 (not the bomb edition) and my carrier is AT&T, although I'm not sure that's needed.
first do a factory reset then flash latest stock firmware from sammobile
messi2050 said:
first do a factory reset then flash latest stock firmware from sammobile
Click to expand...
Click to collapse
sammobile.com doesn't have G930A which I need. I've been finding it from other places but none of them have worked so far.
My Lg G5 (Tmobile) keeps on rebooting to recovery mode (TWRP) no matter what rom I flash. I tried using LG Up software but no matter how many times I install the driver phone is not recognized. Firstly I flashed Fulmics ROM then I installed LineageOS (Cyanogenmod) after that phone was working fine for a while till I saw an update and tried updating it to new nightly version. Please help me out if anyone knows how can I fix this issue.
You probably need to put the phone in download mode and then try LG up otherwise try pushing a rom that works through adb
Veliion said:
You probably need to put the phone in download mode and then try LG up otherwise try pushing a rom that works through adb
Click to expand...
Click to collapse
Also make sure you use autoprime version of LGup
Sent from my LGE LG-H830 using XDA Labs
Veliion said:
You probably need to put the phone in download mode and then try LG up otherwise try pushing a rom that works through adb
Click to expand...
Click to collapse
HAHA I wish it was that easy. No matter what on earth I do, phone doesn't get recognized
Try this
https://forum.xda-developers.com/lg-g5/how-to/bring-lg-g5-to-life-download-mode-lgup-t3565508
dksoni411 said:
Try this
https://forum.xda-developers.com/lg-g5/how-to/bring-lg-g5-to-life-download-mode-lgup-t3565508
Click to expand...
Click to collapse
I am sure this method would fix it but I already returned my phone and got new one as I had 1 year warranty. I bought it from T-mobile and I locked the bootloader before turning in the phone so it doesn't look like I was trying anything fishy. Now instead of phone going to twrp each time it goes to boolop saying "device is currupted and won't boot". It won't go to recovery mode no matter what I do and hope I don't get charged from T-mobile saying this and that.
However, I am really grateful to all of you great people who tried their best to help and you sir actually threw me a solution but I was too impatient to wait for it. I know this method will work no matter what as I had been using this tool for my G2 in old days and fixed the worse bricks where I had to openup the whole phone take battery out and stuffs like this. I was looking for this method found everything but LG tool asked me for .dll file which I couldn't find anywhere and decided to give up on it...
Thank you for your help and now I know I am not going to be bricked anymore as I have this method to work with in future issues and am her waiting badly for Xposed to be available for Nougat.
Prabin Dhital said:
I am sure this method would fix it but I already returned my phone and got new one as I had 1 year warranty. I bought it from T-mobile and I locked the bootloader before turning in the phone so it doesn't look like I was trying anything fishy. Now instead of phone going to twrp each time it goes to boolop saying "device is currupted and won't boot". It won't go to recovery mode no matter what I do and hope I don't get charged from T-mobile saying this and that.
However, I am really grateful to all of you great people who tried their best to help and you sir actually threw me a solution but I was too impatient to wait for it. I know this method will work no matter what as I had been using this tool for my G2 in old days and fixed the worse bricks where I had to openup the whole phone take battery out and stuffs like this. I was looking for this method found everything but LG tool asked me for .dll file which I couldn't find anywhere and decided to give up on it...
Thank you for your help and now I know I am not going to be bricked anymore as I have this method to work with in future issues and am her waiting badly for Xposed to be available for Nougat.
Click to expand...
Click to collapse
Good to hear that, You are welcome,
And as you mentioned about "device is corrupted and won't boot", that's because you locked bootloader. And as you were using twrp which means modified system partition so phone said that. But you can still go to download mode and use the method to make it live or can try unlocking bootloader to start twrp.
I experienced similar situation. I thought I had to send my phone for repair. As I was able to put the phone to download mode, I used uppercut with downloaded kdz file from LG G5 development thread and restored my phone. I didn't use my phone for four days thinking that I had to take to a phone shop or send to service center. But after careful reading of unbrick tutorials, I brought my phone back to life. Now I can play flashing anything as I am confident that I can easily unbrick my phone.
Sent from my LG-H850 using Tapatalk
A few days ago I got my G5 H830 and came with version 6.0.1 h83010i, looking for information on how to install custom rom, I read the post to install the .TOT file to be able to install TWRP and through this the Custom Rom, until there is Everything okay, I did everything right, but then I decided to go back to the Rom stock, on the night of that same day I saw that when I reboot my cell phone it stuck on the LG logo and it had some color pixels damaged (but no screen Damaged, if not because of small brick) then force a restart and continued the same, I did factory reset by stock recovery and then normal start, I went to sleep leaving it in 100% battery, and when I wake up in the morning the cell phone It is off, when I turn it on 5% and I get scared, then I wanted to go back to custom rom to leave those problems behind, but then when I install the TOT again and install the custom ROM it will restart half installed and any rom that installed it would stay Stuck and the LG logo and a bootloop until when it was flash the kdz several times until the cell did not want to ignite more, the pc does not recognize it or anything, I need help with this.
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
edit: correction, not clickbait, but need to signup
vincom said:
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
Click to expand...
Click to collapse
Yeah i saw your post a couple of days ago and it is legit , about the file hosting it's not clickbait it's just 4shared and this little guy is older than the xda :laugh::laugh: , i agree that the androidfilehost is faster and more convenient but i'm not the uploader , i just copied it from another source, it would be great if you re-upload it for others and i will update the link.
Now we come to testing: i tested this myself and it is 6.0.1 for sure but i don't remember which release it was cause i updated to 7.1.1 20.32.67.25 release for various reasons, mainly for battery life (spoiler: not much difference and it's still poor) and i will keep flashing / debloating apparently in (in search of incredible) but i'm quite sure this phone is hopeless without a custom ROM from scratch as the amount of services and wakelocks are enormous.
Why don't you participate and use your knowledge in the "allegedly upcoming" Lineage 15.1 hopefully we get a working build before the end of the year :cyclops: i'm sure you are aware of the situation.
And if you're into kernels then kernelwise this phone's kernel was made by noobs ,ASUS put an AMOLED display and they are not using it's features as the blacks are lit and power consumption by the screen is well above an LCD one of the same size.
Long story short buying this phone was/is a mistake.
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
vincom said:
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
Click to expand...
Click to collapse
All you need is one fw to start with and after that you can update to whichever release you want without any problem , strait forward from asus site and update via sd card even if it's rooted or bootloader unlocked, you can do anything and even get updates as FOTA app works as soon as you boot cause asus update procedure is very primitive HOWEVER it should be on stock recovery and honestly twrp is pretty much useless here and i didn't seem to need it in anything with this device!! (i use magisk to root), it's not like there's half a dozen of custom ROMs to flashed , the only possible modification is within the stock fw and that's our limit.
If you find a screen replacement under 50$ it is worth it , i knew that 2.5D glass is poor engineering and very fragile, so screen protector and case was crucial since day 1.
Notes:
Don't trust asus download center's description cause i downloaded the latest nougat release before the Oreo (as described in their section) and it turned out to be the first release of their lousy O fw.
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
the only one i can't get adb enabled so i can mirror the screen is the mm 11.40.86.71, the same one you have linked here
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
vincom said:
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
Click to expand...
Click to collapse
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
sam.fisher190 said:
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
Click to expand...
Click to collapse
not impossible, very doable to use a phone even with a dead screen.
after alot of trials and error ...from a new flashed stock thats was completely wiped, i can get to a remotely controlled/viewed phone in about 10mins .
i will write up a tut on that.
i can get that done with all the availabe working raw fw except with the mm 2017/04 release
yes, i have a completely dead screen, no display, no touch. all other phone functions work.
the reason for stock recovery procedure was to update to oreo, but i really dont care if i get it. just seeing if its doable.
playing with it for giggles, going to be a security camera as the cam is vg, useless as a phone that has no working screen.
i can be the sacrificial tester if need be, pretty hard to hardbrick this phone as i also have the back cover off so to disconnect the battery connector for those hard soft brick occasions and/or to make sure phone was completely off b4 doing something
I think I killed my phone please help Asus ze553kl
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Nikido2930 said:
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Click to expand...
Click to collapse
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
vincom said:
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
Click to expand...
Click to collapse
sam.fisher190 said:
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
Click to expand...
Click to collapse
THREAD CLOSED and download link removed. 4shared.com requires to have an account for downloading i.e. not accepted as file host on XDA.
Please advise the moderators' team when ready to provide a download link from an accepted file host.