Related
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
carnby24 said:
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
Click to expand...
Click to collapse
flash prims barebone via twrp, or else first flash stock recovery and thn adb sideload firmware
and did you reported this at his thread??
say99 said:
flash prims barebone via twrp, or else first flash stock recovery and thn adb sideload firmware
and did you reported this at his thread??
Click to expand...
Click to collapse
yes i did, but i was kicked out of the thread...
trying it now..let me see if your suggestion works...
carnby24 said:
yes i did, but i was kicked out of the thread...
Click to expand...
Click to collapse
weird I didnt see anyone else complaining such things, and yes it will work so relax
Hi, seems the same..i can only restore if i uncheck system from the list of backup options. But fast charge and mtp and otg function all doesnt seem to work.
Sent from my ASUS_Z00AD using Tapatalk
I miss my fast charge and adb function..please help guys..
Sent from my ASUS_Z00AD using Tapatalk
Reflash the latest rom v1.1 , hopefully everything will work fine then
anyone know whats the reason for this??
unmount system before flashinh prism barebone, you wont get error if you unmount system
serhangelgor said:
unmount system before flashinh prism barebone, you wont get error if you unmount system
Click to expand...
Click to collapse
is this the same if i want to flash stock?
carnby24 said:
is this the same if i want to flash stock?
Click to expand...
Click to collapse
didnt tried on stoct, idk
Guys! Is there any chance my problem (http://forum.xda-developers.com/zenfone2/help/asus-zenfone-2-recognized-pc-t3294980) is related with this issue?
Reflashing stock recovery could help? I´m afraid to do it and not be able to recover any thing else or get stuck on boot without usb connection.
Another question: This might be related to kernel? i´m using BitOkObssesion
I am not sure what went wrong on your side. But i flashed the kernel on a phone of a friend and he has no issues at all.
Did you try to download again ? Maybe a bad download..
Sometimes it happens
carnby24 said:
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
Click to expand...
Click to collapse
Every ROM developer or Kernel developer spent a lot of his time on making better experience for user
i personally have my own ROM and i did try Echoe ROM & AEL Kernel because its from Awesome Developer and everyone loves him and he's kind to everyone
many users used his ROMs and Kernels and never experience hardware or software problems because he checks every single detail of his work
all problems that you mentioned cause by Asus and many users sent their devices to service center, so please dont blame anyone about
something they did do and research next time before post something similar
im still using AEL Kernel without any problems
BTW
TWRP backup is broken for our device, Reboot again to recovery and dont select Data or Cache in Restore options
and check this post
Wow..thanks..will try it...thanks..didnt know..cos before this used to select all data and cache..no problem..
carnby24 said:
Wow..thanks..will try it...thanks..didnt know..cos before this used to select all data and cache..no problem..
Click to expand...
Click to collapse
Good luck with it
and for adb and mtp, did you tried other pc ?
or other cable ?
if its the same then its from Asus :crying:
can you please remove "echoe kernel" from thread title and from the thread also ?
But what about the MTP function and fast charing? Doesnt seem to work now.Tried all other PC and cables as well. Still the same.
AL_IRAQI, so you´re saying thats a hardware related issue? i´m asking because i got the same issue but with another rom...
tried different cables different pcs and nothing
carnby24 said:
But what about the MTP function and fast charing? Doesnt seem to work now.Tried all other PC and cables as well. Still the same.
Click to expand...
Click to collapse
Restore Stock and go to Asus service center, Asus messed up these things in latest update
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
RiskTaker10 said:
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Click to expand...
Click to collapse
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Puddi_Puddin said:
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Click to expand...
Click to collapse
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
RiskTaker10 said:
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
Click to expand...
Click to collapse
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
hrishikeshgramani said:
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
Click to expand...
Click to collapse
Unfortunately that is out of the question, there is no Service Center for Oneplus where I live so I cant get it checked ASAP
Puddi_Puddin said:
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
Click to expand...
Click to collapse
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
RiskTaker10 said:
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
Click to expand...
Click to collapse
You can always try..
Puddi_Puddin said:
You can always try..
Click to expand...
Click to collapse
Okay thanks good citizen of XDA I'll try to flash a custom rom and I'll try to report back here ASAP
After the latest update of Oxygen os my 5t had start crashing so I Installed TWRP recovery and Installed Linage OS but in that rom also there was same problem so i Installed another rom OMNI and there was the same problem Today the phone crashed as always and it Didn't boot up It got stuck in Boot animation and that i tried to flash another rom but no rom will get flashed from twrp also so I used ADB Sideload to flash rom it got flashed but it also got stuck in bootanimation It wasn't a Bootloop It just got Hang on Bootanimation and than I use hardbrick method (MSMdownloadTool V4.0.8) It flashed The Stock OS which Booted Fine for 10sec And the same problem happens again I have Flashed two Stock OS (1 - dumpling_43_O.06_171206.ops) and (2 - dumpling_43_O.36_180613.ops) Now there is no boot-animation Its Stuck on One-plus Logo (POWERED BY ANDROID) Plz Help sorry for my English
Sounds like a faulty flash storage. RMA it.
freyrnygaard said:
Sounds like a faulty flash storage. RMA it.
Click to expand...
Click to collapse
what is RMA I Really Need your Help PLZZZ
Why did you use nougat and oreo unbricking tools if you were on pie? No wonder your phone doesn't boot.
The latest unbricking tools for 9.0.3 can be found here: https://www.androidfilehost.com/?fid=11410963190603910105
RMA means Return Merchandise Authorization (send back to the seller). Since you've already used the phone, you can't just send it back anyway. If unbricking doesn't work, you'll have to contact oneplus support to find out what your options are.
bud7dha said:
Why did you use nougat and oreo unbricking tools if you were on pie? No wonder your phone doesn't boot.
The latest unbricking tools for 9.0.3 can be found here: https://www.androidfilehost.com/?fid=11410963190603910105
RMA means Return Merchandise Authorization (send back to the seller). Since you've already used the phone, you can't just send it back anyway. If unbricking doesn't work, you'll have to contact oneplus support to find out what your options are.
Click to expand...
Click to collapse
Offtopic but you can use Nougat and Oreo unbrick tools even if you're on Pie (I did it myself because I was curious to see if it will erase /vendor partition or not). I however agree that this is not a normal situation and that his storage might be faulty.
Can you at least flash stock recovery?
freyrnygaard said:
Sounds like a faulty flash storage. RMA it.
Click to expand...
Click to collapse
Hmm. I was thinking about rooting mine today. But you got me thinking again lol.
I googled "faulty flash storage Android" and not much came up tho. Can you get into a little bit more detail what is that and is it very common with onePlus devices ?
*Sorry if I asked sth dumb. Im new to Android ?
nevethlexfiend said:
Hmm. I was thinking about rooting mine today. But you got me thinking again lol.
I googled "faulty flash storage Android" and not much came up tho. Can you get into a little bit more detail what is that and is it very common with onePlus devices ?
*Sorry if I asked sth dumb. Im new to Android
Click to expand...
Click to collapse
I meant as in a a damaged internal storage drive. You know, a storage drive can fail but it certainly won't happen from rooting your phone. So go ahead and enjoy.
Tried installing a few GSI 10 and 9 ROMs, didn't work at all, got them to bootanimation at best, since there's no TWRP yet I had to do it all on fastboot, here's my logcat if anyone can help me boot this thing
VyktorJonas said:
Tried installing a few GSI 10 and 9 ROMs, didn't work at all, got them to bootanimation at best, since there's no TWRP yet I had to do it all on fastboot, here's my logcat if anyone can help me boot this thing
Click to expand...
Click to collapse
Well long time since your post. And nobody responding. This advice is not confirmed , as I don't have device yet. But this phone has vbmeta partition, so chances are, you need to flash vbmeta with disable-verity.
I don't remember the exact format right now. But you can simply Google that. ??
VyktorJonas said:
Tried installing a few GSI 10 and 9 ROMs, didn't work at all, got them to bootanimation at best, since there's no TWRP yet I had to do it all on fastboot, here's my logcat if anyone can help me boot this thing
Click to expand...
Click to collapse
install the rom of one macro on it after that boots the blank flash of one macro then it will restart directly on the bootloader and without restarting apply the rom again of one macro and that's it, from there vice you can install gsi arm64 s difficulties
if you apply the wrong commands in the hira to oassar the rom it will bootloop.
sorry english, using google translator from portuguese to english is awful
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.
zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash
I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters
Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.
As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.