The other day i was installing CrombiKK from Hairybean.
I followed the directions for the bootloader and recovery and installed it fine after many tries choosing different kernels and install methods in aroma.
I noticed after installing with some different kernels that the wifi bug had a separate fix and wasn't because of a faulty kernel so i went to reinstall with the wifi fix and the OC kernel i wanted and the rom installed just fine but i immediately installed the wifi fix and twrp gave me an error. the rom bootlooped.
i thought all was fine and wiped again to install again but i noticed that while installing the rom in aroma it took about 4 seconds versus a minute or so, and thats when i noticed that twrp wasn't writing any rom at all to the tablet.
so im stuck with no rom and twrp doesnt want to install the rom anymore when it worked previously. i have no backups on the tablet either.
i checked the brick guide -http://forum.xda-developers.com/showthread.php?t=1514088- and it seems to line up with brick #3 but they dont have any information on that.
please allmighty devs, help me.
-Forever-stallone
Seriously people should stop trying that rom ... it does more bad than good ... Last week the same happened to me ...
I am no DEV ! I was thinking I permanently bricked my tf201 so I was desperate and tried everything ... maybe think twice before attempting this ...
What version of twrp are you on ?? I believe that the first two steps you take to install CROMBi-kk (.recovery and .blob) basically turns your tf201 to tf300t . The evidence is when I installed cwm for tf201 it didn't work but cwm for tf300t worked pretty well . but generally cwm is useless in this case ...
I suggest make sure you are on latest twrp for tf300t device and go download latest official cyanogenMOD 11 for tf300t device and flash it with twrp.
Again, My case was way more messed up so I messed with many other stuff so maybe wait so someone confirm or deny this !? but I started going for CROMBi-kk now I got a fully working cm11 that thinks my device is tf300t .
S3P3HR said:
Seriously people should stop trying that rom ... it does more bad than good ... Last week the same happened to me ...
I am no DEV ! I was thinking I permanently bricked my tf201 so I was desperate and tried everything ... maybe think twice before attempting this ...
What version of twrp are you on ?? I believe that the first two steps you take to install CROMBi-kk (.recovery and .blob) basically turns your tf201 to tf300t . The evidence is when I installed cwm for tf201 it didn't work but cwm for tf300t worked pretty well . but generally cwm is useless in this case ...
I suggest make sure you are on latest twrp for tf300t device and go download latest official cyanogenMOD 11 for tf300t device and flash it with twrp.
Again, My case was way more messed up so I messed with many other stuff so maybe wait so someone confirm or deny this !? but I started going for CROMBi-kk now I got a fully working cm11 that thinks my device is tf300t .
Click to expand...
Click to collapse
You are completely correct to point out the dangers but the fact is if you follow the the instructions given in the respective threads to the letter then everything will be fine.
Unfortunately, years ago, Asus in their wisdom landed us with firmware that is totally unforgiving when mistakes are made. People do not understand this because they have spent many years flashing happily away on devices with zero penalties for making errors and have come to this forum expecting to just plough on as before. New people just don't seem to understand that a really small mistake can totally brick this device.
To be fair, the forum itself has for a long time now been hard to follow because outdated threads still keep rising to the top,
As one who has been knocking around here for a few years (and who will probably be stuck on the TF201 for a while yet now the new Nexus tablet keeps getting pushed back: 4:3 screen - wtf use is that for my portable TV/media device??) I will take some advice to put together an up-to-date warning post about what should and should not be tried. Experienced users please send PMs with suggestions on what should be included :good: .
S3P3HR-
I followed the instructions for crombikk exactly, hairybean 2.31 with JB 4.2.1, bootloader version 10.6.1.27.1 and twrp 2.6.3.1 and like i said i had it working at first minus the wifi patch that was a separate file.
the real problem was that i wanted to reinstall with a different kernel so i just booted into twrp and installed with aroma and it installed fine but twrp had an error when i immediately after installed the wifi patch. i didnt think much of it at first but now i cant install any roms.
Restorer-
You are deinitely right on this tablet being unforgiving. Ive been running custom roms since 2011 and have never had a problem like this before. It totally caught me off gaurd. i honestly didnt think this would be so bad, even my dad's evo 4g lte wasnt this easy to brick. Im mad about it though because that kitkat rom was the only thing to make it fast enough that i could use it how i like to use my devices.
Could you think about any possible way of fixing my rom installation problem? Its not like i can use it in its current state anyways so if theres a chance i would try it.
Forever-stallone said:
S3P3HR-
I followed the instructions for crombikk exactly, hairybean 2.31 with JB 4.2.1, bootloader version 10.6.1.27.1 and twrp 2.6.3.1 and like i said i had it working at first minus the wifi patch that was a separate file.
the real problem was that i wanted to reinstall with a different kernel so i just booted into twrp and installed with aroma and it installed fine but twrp had an error when i immediately after installed the wifi patch. i didnt think much of it at first but now i cant install any roms.
Restorer-
You are deinitely right on this tablet being unforgiving. Ive been running custom roms since 2011 and have never had a problem like this before. It totally caught me off gaurd. i honestly didnt think this would be so bad, even my dad's evo 4g lte wasnt this easy to brick. Im mad about it though because that kitkat rom was the only thing to make it fast enough that i could use it how i like to use my devices.
Could you think about any possible way of fixing my rom installation problem? Its not like i can use it in its current state anyways so if theres a chance i would try it.
Click to expand...
Click to collapse
Can you still access the bootloader when you hold down volume down and power button before going into recovery ?
flumpster said:
Can you still access the bootloader when you hold down volume down and power button before going into recovery ?
Click to expand...
Click to collapse
Yes, can access the boot loader just fine. I haven't checked if fastboot still works but it should since the boot loader does. I just am wary of trying anything with the risk of making it much much worse.
it has been 10+ days and since nothing helpful has been posted I post this .
I never installed the actuall rom but I installed recovey and .blob and it somehow formatted my /data with all my backups in it . then I panicked and tried to format partition Data and it took a little long so I panicked some more and forced a restart ... I found microSD card and tried to install cm10 and virtuous_prime roms but It was a fail . I investigated and saw my /data was corrupt and showed internal : 0mb . I was still able to flash any recovery I wanted . Usually cwm for tf300 and twrp ...
compare your case to mine and the case I post Down below ... it does Exactly what that on unbrick guide said not to do ... Your choice ... if every thing fails then a mainboard replacement is last option ...
Look at post #5 for his version of fix . I couldn't access asus tf201 official support site so I yahoo'ed stock firmware and for what its worth , I chose a rom that had deoxed in the name ... whatever that means ...
http://forum.xda-developers.com/showthread.php?t=2800506
S3P3HR said:
it has been 10+ days and since nothing helpful has been posted I post this .
I never installed the actuall rom but I installed recovey and .blob and it somehow formatted my /data with all my backups in it . then I panicked and tried to format partition Data and it took a little long so I panicked some more and forced a restart ... I found microSD card and tried to install cm10 and virtuous_prime roms but It was a fail . I investigated and saw my /data was corrupt and showed internal : 0mb . I was still able to flash any recovery I wanted . Usually cwm for tf300 and twrp ...
compare your case to mine and the case I post Down below ... it does Exactly what that on unbrick guide said not to do ... Your choice ... if every thing fails then a mainboard replacement is last option ...
Look at post #5 for his version of fix . I couldn't access asus tf201 official support site so I yahoo'ed stock firmware and for what its worth , I chose a rom that had deoxed in the name ... whatever that means ...
http://forum.xda-developers.com/showthread.php?t=2800506
Click to expand...
Click to collapse
Sorry for the late reply everybody, im up and running again after lj50036 (dev behind crombi) helped me so much. What we did was since the bootloader was working just fine we set the tablet back up with a stock blob and from there we set up NVFLASH (which was needed 10 mins later, haha) and after that i used it to take my tab back to stock and from there i followed his instructions for crombi.
BTW, crombi is literally the fastest rom i have ever used on the tf201, the battery life is lowered a bit because of OC but its worth it.
@ s3ph3r, you might have gotten yourself into a big mess, does your bootloader still work? if so, there may be hope but i couldnt figure out where to start with it.
Related
Hi there.
It seems that I can't help myself anymore.
Got a prime with JB bootlader 10.4.2.18 and TWRP 2.4.3.0 on it.
Flashed SuperSU using TWRP and, after that, tried to flash
ParanoidAndroid for my device. (pa_tf201-3.10-07MAR2013-190411.zip)
Right after starting the flashing procedure TWRP seems to crash.
(It immediately shows it's splash screen again and gets laggy.)
I also tried other TF201-JB-ROMs but it happens with any of them!
I can access TWRP and Fastboot! But I got no ROM on the device
and aint able to flash one.
After hours of searching and reading it still looks like a Option 3 brick
to me and I don't know what to do next.
Some ppl tell to write the original blob from Asus' 10.4.2.18 stock rom,
others advise against that because it will get hard-bricked. I'm stuck.
Any ideas?
Seems to be solved.
Instead of using my MicroSD-card to install the new ROM I now just
used ADB to transfer the file directly onto the device.
It worked fine for cm-10.1-20130308-UNOFFICIAL-tf201.
I'll try AndroWook_Hairy_Bean_v1.51_FINAL tomorrow, or shouldn't I?
trust me andro wook HB 1.51 is the best at all !
i tried each and every one of Roms and no one can beat HB !
if u can live without changing themes or multi user features Andro Wook is best choice for u ...
must annoying issue in other none stock based Roms is that no one of them can play movies in HW acceleration mode . ( image quality will be very lower in other modes )
u should wipe system before flashing new Roms (specially after CM Roms ) ...
its a little risky but best results will come from it !
sorry for my terrible english
marleng said:
Seems to be solved.
Instead of using my MicroSD-card to install the new ROM I now just
used ADB to transfer the file directly onto the device.
It worked fine for cm-10.1-20130308-UNOFFICIAL-tf201.
I'll try AndroWook_Hairy_Bean_v1.51_FINAL tomorrow, or shouldn't I?
Click to expand...
Click to collapse
Hello. The problem is with twrp 4.2.3.0 version. Push 4.2.2.0,your problem will end.
Hi all
ok so i'm a bit nervous writing this expecting all manner of attack in that i may be posting something that's been posted before lol, i've been working on this phone from start to finish about 9 hours, over two days..... i've googled just about every combination of words to do with the title and everything in between but nothing seems to come close to what i actually need to do as nothing works
i have an LG Optimus 2x / p990, it had ICS on it but was far too slow to handle this, it needs something a bit less hardware intensive to run smoothly, so i went ahead an found cyanogenmod stable ...... 7.2 i installed sdk after an hour of finding out how it works i finally got adb and fastboot working, i then needed this, that, this, that, etc etc etc.....
to cut a 9 hour story short, i've managed to get myself to the point where i wiped the phone of everything but CWM partioned for ics via the AIO software but CWM will not let me install any ROM onto the phone. to be more precise it says i have installed CM 7.2 successfully! (i've tried this via the CWM via external SD card and sideload) i reboot the phone it's as if i've never done a thing, no trace or suggestion i've even attempted it on the internal card... nothing
i'm at the point now where i'm quite happy to just have my phone back now and install ICS 404 but can't use the LG kdz install software as the pc doesn't see the phone as an LG p990 because it's recovery and i can only get it to come up as internal and external memory cards
i'm not really a noob when it comes to tech stuff but this little phone has me stumped.... please, i'm begging you, help me any operating system that can get my phone working will do, preferably the CM 7.2 if not back to ICS 404?
and i know, i know i should have backed up but i had no idea it could be so complicated just to put an OS on a tiny computer
ETA i've tried that exitrecovery.zip thing and it did nothing :/
It's quite simple
Try to reset and unroot/re-lock the phone then unlock and root, then what you need to do is get ROM Manager and get the Clockwork Recovery and the version that supports your device, although you might need to hook up your phone to your computer for the process to work.
Also put back in ICS 4.0.4 when unrooted and re-locked again like stock and make sure it's the stock file for your phone.
And after you got ROM Manger and the Clockwork Recovery
Then just in Clockwork wipe out all data on the device and don't do a factory reset in Android just with clockwork and delete everything that was made on that phone then install CyanogenMod.
After that it will seem to take a long time or just a while to boot up and then it boots faster then the original ROM.
If you have Clockwork Recovery just wipe out all the data while it's still in there and you should be set.
When it was my first time putting in CyanogenMod it was 10.1 RC1 on my Nexus 7 and it didn't work and forever bootlooped, and that was because i forgot to wipe the device. Then after going into Recovery with Clockwork I deleted all the data of my tablet and it worked but took 5 mins. to boot up which is nomal.
And if Clockwork doesn't work, do the same with TWRP (Team Win Recovery Project) and download that which can be found here teamw.in/project/twrp
If you don't want to get ROM Manager or that one isn't working then try this website to get Clockwork because it has the whole list of devices and I recommend downloading from the website instead of their app. clockworkmod.com/rommanager
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
twelfty said:
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
Click to expand...
Click to collapse
TWRP has a completely touch driven interface that is 100% themeable, while CWM has a touch version and non-touch version. Also TWRP has a built in file manger and terminal emulator where as CWM does not. A lot of people like TWRP because it provides a lot of good features with a simple and straightforward yet powerful user interface. I would recommend taking a look at this guide if you want more information on the differences between the two http://www.droidiser.com/2013/04/twrp-vs-clockworkmod-recovery.html?m=1.
Sent from my SCH-I535 using xda premium
ok i managed to do it i can't remember exactly how but some good links and info for anyone who stumbles across this in need of help
i went for cyanogenmod 10.1 to make this work i used this AIO tool - http://forum.xda-developers.com/showthread.php?t=2020737
repartioned with OLD partion layout and BL
installed TWRP (included in the aio)
if you need to reinstall the google play store make sure you have right version if you flash it and get "unfortunately setup wizard has stopped" repeatedly you have the wrong version see this link for which one you need http://wiki.cyanogenmod.org/w/Gapps
obviously make sure you have adb and fastboot setup and drivers too.... it's a long process installing the entire sdk, personally for flashing this once and most definately not inclined to do it again i'd go with just the adb and fastboot rather than the whole sdk
also i found a keyboard error with 10.1 where i'd type 1,2 or 3 characters and the keyboard would minmise not sure if there's a proper fix (i found one thing where you disable the autocorrect but didn't want to do that) so i decided to download and install hackers keyboad which is based on the gingerbread keyboad and is much better and comes with full features and integrates nicely
coupled with the info above from YoyoscratchMC and you should be in the field
good luck to all i was ready to jump out my window with my phone first so i could land as hard as possible on it last night but i got there in the end lol
Hi everyone,
It seems I messed up my Prime and I think I know why it happened. I'll first ask my question and then detail what I think happened at the end. I've been reading around the forums for the past few days and I think I'm experiencing brick number 3 as detailed in this thread: http://forum.xda-developers.com/showthread.php?t=1514088 I followed the link provided under option 3 which links to a thread about an Transformer Prime IRC channel: http://forum.xda-developers.com/showthread.php?t=1367016 I logged in into the IRC channel and someone greeted me by asking for the binaries...frankly, I've no idea what to do in that channel.
I was on the stock Asus Jellybean Rom. I used the Asus Unlock tool and installed TWRP via fastboot as explained in their website (installed the JB.blob). Everything worked fine. I then committed a mistake. I was going to perform a data wipe before installing the new ROM (latest CM nightly) but in retrospect I think that I only performed a factory reset. It was my first time using TWRP and when I got into the wipe menu I selected wipe but I recall that the button for wiping read "slide to perform factory reset". I thought that I was wiping the data on my device but I think that I got confused and only performed a factory reset. I didn't realize that at the time and proceeded to flash the new ROM. When I restarted the device it got stuck in the Asus/Nvida splash screen.
I'm able to go into the recovery menu. I've wiped data properly many times after this and flashed CM many times but the device won't get past that splash screen. I tried flashing the ROM via ADB but whenever I enter the command the terminal shows me a list of the actions that can be performed via ADB and nothing else happens.
I've tried looking around for a solution but I've been unable to find one. Should I install/flash a stock blob rom? The links above say it may do more harm than good and no longer advice users to do that but I haven't found any other alternative. There are many threads pertaining this issue but each case is slightly different and I haven't found one that applies to my situation.
I'm mad at myself because I've had flashed so many custom roms on other devices before and had never had any problems whatsoever that I got careless when flashing the Prime. I know this is completely my fault and I don't want to waste anyone's time on this. I just would like for someone to tell me exactly what to read or where to look so that I can try and fix this situation.
just in case...I just remembered that I didn't root before flashing...could that have been the problem?
I was checking out, once again, the options in TWRP and I did wipe the device correctly. I didn't mess up as I once thought. I can't understand why this happened.
Nearly the same problem for me, case n°3 and don't know what to do. I know have a very expensive black mirror...
FIXED
YES! I was able to fix it BUT I'd be careful before trying what I did. Basically, I did what forum members had advised not to do; I flashed the Asus stock rom via fastboot. As I said before I had read plenty about the various issues with the Transformer Prime. I noticed that some people were flashing the stock rom when confronted with my situation and exhorted others to do the same since they had luck with the procedure. After that, it seems plenty of people bricked their devices by following the same procedure. This caused various senior members in XDA to no longer advise others to try to fix their tablet with that method since it was causing more harm than good (see: http://forum.xda-developers.com/showthread.php?t=1514088)
Sadly, I had no other choice but to try that method. We were advised to go to the #Asus-Transformer IRC channel but, understandingly, there aren't many people participating in that channel (it's very old!. I was able to get assistance from a very helpful (as always) android geek but we couldn't get anything to work since I was having problems with ADB recognizing my device.
So, knowing full well the possible consequences of flashing a stock asus rom I decided to go for it. After all, the worst thing that could happen was to end with a hard bricked device and the soft brick I was experiencing wasn't as different as that (i.e. I couldn't use the device anyway). So I decided to play russian roulette and see what happened. Luckily the rom installed fine and I was able to boot past the, dreadful Asus/nvidia splashscreen! I was super lucky! Even though I'm back to the stock rom I'm happy because I can use my device once again! I really wanted to try out Cyanogen on my tablet but I will have to pass on that...I will never install a custom ROM again on my Prime
So, if anyone is feeling adventurous and has lost all hope then why not play russian roulette and check out what happens when you install the asus stock rom? I downloaded the asus image from here http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&os=32 and followed the instructions here http://forum.xda-developers.com/showthread.php?t=1680570 (just step three and four at the end since I already had a custom recovery installed). I had to unzip the download twice (it has a zip inside a zip) and copied the blob file into my fastboot directory (in the PC). I then renamed it to "update.blob" and flashed it.
Don't try it unless you are fully aware of the consequences!
So a complicated story:
I bought a transformer prime some time ago then rooted it and installed WOOKIE rom (http://forum.xda-developers.com/showthread.php?t=1674827) then it's sat unloved for a few months.
However I've tried to resurrect it for the festive period and am in trouble. (I've been a keen user of the roms on here for many years, with a smart phone for over 10 years, so I'm not completely thick!)
I'm trying to get paranoid android on it;
However, as soon as I go to CWM and try to install the ROM I get a terrible error message, (Will update once I can get it on my screen but it's on 0% charge currently) but can roll back to install a backup, so that's not the end of the world.
So my issue is how do I get from what I have to where I want to go to?
I think the solution is as follows:
a) I need to get Clockwork ROM working well first. Any ideas?
b) I need to downgrade the ROM to something, But I'm unsure what
c) If a and b are in place, I think I can do the rest.
Please help me! All this talk of downgrading roms has confused me.
1. Let go of CWM. No one uses it anymore. Download TWRP here: http://teamw.in/project/twrp2 It will probably fix your errors and it has a lot more features than CWM, is more polished etc.
2. Without NVFlash you can't downgrade. Here is guide how to do it: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ If you don't want to downgrade I recommend you to install CMB rom http://forum.xda-developers.com/showthread.php?t=2501812 It's Android 4.3.1, everything works and is probably fastest ROM that we can get on our primes.
Thank a bunch zdenko1.
I'm on the case, however I left my laptop entirely flat overnight, so it's upto 0% and 3% charged. And it's Christmas eve!
It's really good to have someone help me out with a bit of detail - so thanks for this.
If I don't post, assume it works, and here's to a peaceful Christmas break to you all
Now I think I have cooked my goose!
I was unable to get anywhere with this,
So with an air of confidence I ran a program (again the name escapes me) which lets you return your computer back to stock, from which one is able to get it working and you're back to square 1.
Great I thought and as ususal I throw my self both feet in.
It formats fine etc until it asks me to get the original update ROM/blob I think -
which I didn't have, so hen tried to download it and couldn't find it.
So now I think it really is screwed
Nothing formatted, I can't enter recovery mode and things are looking bad.
Does ODIN work/provide an answer? If so please help!
Of course I realise that ODIN is Samsung own!
So I think I need a ROM/BLOB that restores me to a working copy via bootloader?
Is that on the right line?
Just seeing if I have to give this up as lost and sell as broken or can it be resurrected?
Sent from my SM-N9005 using XDA Premium 4 mobile app
DO NOT INSTALL ANY OTHER RECOVERY WHILE USING THE NEW 4.2.1 BOOTLOADER, THEY ARE NOT COMPATIBLE AT THE MOMENT, THE ONE BUILT IN IS MODDED. USE THE DOWNGRADE ZIP TO TAKE YOU BACK TO 4.1.1 BOOTLOADER AND RECOVERY IF YOU NEED IT.
Click to expand...
Click to collapse
Using the link you provided in the OP, scroll down until you see the downgrade hairybean 4.1.1 bootloader and recovery. That should get you to a point of being able to flash a new rom.
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.