Phone always booting into twrp recovery mode, any solution? - Moto E3 Questions & Answers

2-3 days ago I successfully rooted my Moto E3 power by unlocking bootloader and installing twrp recovery. Yesterday I installed Lineage 14.1 custom Rom (7.1.2) for Moto E3 power from here
https://forum.xda-developers.com/moto-e3/development/rom-lineage-14-1-moto-e3-power-t3610435
The Rom installation was successful. Phone was working fine. But there was some minor lag and screen was appearing to be yellowish. Hence I decided to Factory reset the phone. I tried to reset it from phone settings. The phone switched off and turned on into twrp recovery mode. Then I tried to factory reset through twrp mode. But it is always booting into twrp recovery. I wiped all cache and data including system data and flashed the above Rom again. But whenever I try to system reboot, it is not booting normally, but always going into twrp mode.
Please provide solution for the issue with appropriate information and links.
Thanks.

Beauause u delete the all ROM
For Reset phone -: not need to wipe system and boot.. Only do a factory reset

Rupi Singh said:
Beauause u delete the all ROM
For Reset phone -: not need to wipe system and boot.. Only do a factory reset
Click to expand...
Click to collapse
Yes, I know that
I had done just factory reset earlier, but after that it kept on booting into recovery mode everytime I reboot the phone. Then I cleared system data to flash the ROM again. I should have done factory reset through recovery mode rather than from phone settings.

Flash a sp flash ROM without format... And again try twrp and custom ROM

Rupi Singh said:
Flash a sp flash ROM without format... And again try twrp and custom ROM
Click to expand...
Click to collapse
yes, already did same thing today. it worked fine and i successfully installed stock rom again.

sid100 said:
yes, already did same thing today. it worked fine and i successfully installed stock rom again.
Click to expand...
Click to collapse
Hi,
Would be great if you can share step by step process on how you recovered. Am also facing the same issue. Have factory reseted my phone and now its booting only to TWRP recovery mode. Am on Mac. Can try to get a Windows Laptop if required.
Awaiting you response.
Thanks in advance!

question?
Rupi Singh said:
Flash a sp flash ROM without format... And again try twrp and custom ROM
Click to expand...
Click to collapse
can you elaborate this ?
What do you mean by Sp flash ROM.?
Do it mean stock rom?
or i have to install sp flash tool in my computer then install stock rom?
if i have twrp install if than i can use it to install stock rom?
Please reply fast.
my phone is as good as dead now.

Ansh Vijay said:
can you elaborate this ?
What do you mean by Sp flash ROM.?
Do it mean stock rom?
or i have to install sp flash tool in my computer then install stock rom?
if i have twrp install if than i can use it to install stock rom?
Please reply fast.
my phone is as good as dead now.
Click to expand...
Click to collapse
I have got the same problem bro. If I can recover from the situation somehow, I'll update it here.

Have an update!
Ben_android enthusiast said:
I have got the same problem bro. If I can recover from the situation somehow, I'll update it here.
Click to expand...
Click to collapse
Update: Don't know if you still need the solution, but I am gonna share my info. Although as the phone you were talking about must be Moto E3, my phone is Lenovo K3 Note, but the processor should basically be the same, as both runs on Mediatek processors. And for the same reason, they both would use the SP Flash Tool to flash a ROM. You'll need to download the Stock ROM file for your moto E3, and flash it through SP flash tool installed on your computer. You'll get the tutorials on youtube. When the stock ROM is flashed, the phone will start with your stock ROM. I have had my phone do the same and it is fine now.

Ben_android enthusiast said:
I have got the same problem bro. If I can recover from the situation somehow, I'll update it here.
Click to expand...
Click to collapse
Yes i recovered from the situation.
You just had to download the sp flash tool and the stock ROM for your respective phone, and flash it . Remember for the above problem you just have to use the "download only" option in your sp flash tool and it will work. if you use "format all+download"
you will left by losing imei number of your phone and then you have to follow other procedure to fix that. but according to me your phone will start by choosing download only.

Related

[Q] Rooted, custom rom installed but not booting anymore

Hello,
Ii have rooted my S4 device with the procedure from XDA (root original rom with keeping update availability). This was done succesfully. After that TWRP was flashed without problems. Than i decided to installl Omega 9 custom rom. The installation went fine and i could use it for three days. A great rom but after a restart my device will not boot anymore and shows only the Samsung logo. Wiping is possible but trying to restore a backup failed....... Do i have to apply root again? Any help is appreciated to solve my problem! Thanks a lot.
Best regards,
Mark
Dataking said:
Hello,
Ii have rooted my S4 device with the procedure from XDA (root original rom with keeping update availability). This was done succesfully. After that TWRP was flashed without problems. Than i decided to installl Omega 9 custom rom. The installation went fine and i could use it for three days. A great rom but after a restart my device will not boot anymore and shows only the Samsung logo. Wiping is possible but trying to restore a backup failed....... Do i have to apply root again? Any help is appreciated to solve my problem! Thanks a lot.
Best regards,
Mark
Click to expand...
Click to collapse
Go to recovery and try wipe cache dalvik and fix permissions and reboot should work fine
.
Wipe Dalvik cache shows error: FAILED
Dataking said:
Hello,
Ii have rooted my S4 device with the procedure from XDA (root original rom with keeping update availability). This was done succesfully. After that TWRP was flashed without problems. Than i decided to installl Omega 9 custom rom. The installation went fine and i could use it for three days. A great rom but after a restart my device will not boot anymore and shows only the Samsung logo. Wiping is possible but trying to restore a backup failed....... Do i have to apply root again? Any help is appreciated to solve my problem! Thanks a lot.
Best regards,
Mark
Click to expand...
Click to collapse
Install Philz Touch recovery in downloadmode, this will help you http://d-h.st/wSF.
I reflashed Philz Touch with ODIN successfully but the recovery mode did not came up. How is this possible? Back to TWRP now with same problems......
If you already have the omega 9 rom in your phone...try to reflash it via recovery .....don't have to wipe data....but do it to be safe....I think it should work...I really hope it works...sorry about your phone
sadeshmagic said:
If you already have the omega 9 rom in your phone...try to reflash it via recovery .....don't have to wipe data....but do it to be safe....I think it should work...I really hope it works...sorry about your phone
Click to expand...
Click to collapse
Already flashed it several times but still hanging in the boot and no way to use the phone.
Dataking said:
Already flashed it several times but still hanging in the boot and no way to use the phone.
Click to expand...
Click to collapse
Well the only other option is to download a ROM that can be flashed via Odin.....hopefully your download mode works.....i think you can find several compatible ROMs in the forums.....try that out....as a last resort
sadeshmagic said:
Well the only other option is to download a ROM that can be flashed via Odin.....hopefully your download mode works.....i think you can find several compatible ROMs in the forums.....try that out....as a last resort
Click to expand...
Click to collapse
Well, download mode works fine, TWRP works fine, flashing ROM works fine, ROM itselfs works great, until i have to reboot. After booting it hangs in the boatloader and i have to flash rom again.........................to get access.
Dataking said:
Well, download mode works fine, TWRP works fine, flashing ROM works fine, ROM itselfs works great, until i have to reboot. After booting it hangs in the boatloader and i have to flash rom again.........................to get access.
Click to expand...
Click to collapse
Well do you merely flash the ROM? try wiping cache afterwards and setting permission....if that doesn't work try to reflash stock firmware....thats your best bet
:good::good::good::good:
I found the solution using method 3:
http://www.ibtimes.co.uk/articles/4...i9500-gti9505-unbrick-softbrick-hardbrick.htm
This will help some other people too.

Phone only boots into TWRP

I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated
I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.
Is there a workaround to this other than flashing factory images...?
hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos

[NEED HELP]Phone stuck on "Warning:Bootloader Unlocked"...Urgent plz

Hey sombody plz help me to get through this,I installed the OTA then I unlocked bootlocker and installed the custom recovery twrp 2.8.7v2 ....then I tried to install the SuperSU....but after flashed it through twrp,I was stucked at "Warning Bootlocker Unlocked" screen for like 15 min,so then I tried to clear cache and then reboot....But that also not help,Then i tried format all the data and tried to to strt in factory mode.but still stucked at same screen.Now what should I do to get into the phone ?PLz ....its urgent
Well the thing you could do is factory resetting via TWRP or you could download a new ROM like CM 12.1 that you can find in the original android developer section and flash it with TWRP, your phone would boot up now. Keep in mind that you will lose everything.
anks095 said:
Hey sombody plz help me to get through this,I installed the OTA then I unlocked bootlocker and installed the custom recovery twrp 2.8.7v2 ....then I tried to install the SuperSU....but after flashed it through twrp,I was stucked at "Warning Bootlocker Unlocked" screen for like 15 min,so then I tried to clear cache and then reboot....But that also not help,Then i tried format all the data and tried to to strt in factory mode.but still stucked at same screen.Now what should I do to get into the phone ?PLz ....its urgent
Click to expand...
Click to collapse
The same happend to me, you must have installed the wrong SU version, just reflash stock firmware via fastboot and reinstall OTA, then if u wanna root use SuperSU v2.61, hope it helps.
Just flashed the CM12.1 through twrp ,problem is solved in a way.
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
facing the same problem...... is flashing CM12.1 gonna solve it ?
praveen1618 said:
facing the same problem...... is flashing CM12.1 gonna solve it ?
Click to expand...
Click to collapse
It will but you should have unlocked bootloader.
praveen1618 said:
facing the same problem...... is flashing CM12.1 gonna solve it ?
Click to expand...
Click to collapse
unlock ur boot-loader first ,then flash cm through fastboot or if u have twrp then copy the cm zip in the sd card and then flash it through twrp.But remember to wipe the system,cache,dalvik cache and data.problem should be gone.
anks095 said:
unlock ur boot-loader first ,then flash cm through fastboot or if u have twrp then copy the cm zip in the sd card and then flash it through twrp.But remember to wipe the system,cache,dalvik cache and data.problem should be gone.
Click to expand...
Click to collapse
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
bablu048 said:
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
Click to expand...
Click to collapse
It will work fine.Backup your current system using twrp and then flash cm12.1.
bablu048 said:
Sorry Noob question- when should I wipe the system,cache,dalvik cache and data ?? Before flashing cm 12.1??
And I am currently on mm rooted. And cm12.1 is based on lollypop, will there be any problem if I flash cm12.1?
Click to expand...
Click to collapse
hope fully there would not be any problem....but in case of going wrong with something you should make a back up with twrp to go back to previous build,and yes ,before flashing any rom, you should wipe your cache ,dalvik cache and data......and system if u need...depends upon you
about moto x stucked while rooting
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
i was trying to root moto x play i unlocked bootloader but when i tried to root my phone stuked in WARNING BOOTLOADER UNLOCKED.......... I TRIED WIPE ALL DATA FROM RECOVERY.... i tried some research someone said try to flash cm12.1 with twrp but i dont know hot to do this..... my mob is not connecting with pc plz help me guyz plz contect me at my gmail [email protected] its very urgent......plz tell me what to do step by step
sonubisht said:
i was trying to root moto x play i unlocked bootloader but when i tried to root my phone stuked in WARNING BOOTLOADER UNLOCKED.......... I TRIED WIPE ALL DATA FROM RECOVERY.... i tried some research someone said try to flash cm12.1 with twrp but i dont know hot to do this..... my mob is not connecting with pc plz help me guyz plz contect me at my gmail [email protected] its very urgent......plz tell me what to do step by step
Click to expand...
Click to collapse
first of all, which super su zip u r trying to flash ???? only this super su - "SuperSU-v2.62-3-20151211162651.zip" works on MXP...... after unlocking the boot loader u need to flash first twrp custom recovery...then entering into twrp interface,format the whole internal memory (I m sorry,u have to do that,no other way is possible)...... then put cm12 zip which u want to flash in sd card then flash the zip through twrp....... I guess this way your problem would be solved.....
If u flashed the correct mentioned supersu you should be fine.It happened 3 times also to me.I just press power continuously to power off and then it boots normally.
Please in case of SuperSU do not use 2.62-3 anymore, use 2.79SR3. Both are supposed to work, but 2.79SR3 is newer and has some bugfixes.
Note: The release 2.79 will not work, the detection fix to install systemless for all Moto devices is only integrated in 2.79SR3. 2.62-3 does no detection, it always installs systemless.
that was rom problm
mausv said:
Well the thing you could do is factory resetting via TWRP or you could download a new ROM like CM 12.1 that you can find in the original android developer section and flash it with TWRP, your phone would boot up now. Keep in mind that you will lose everything.
Click to expand...
Click to collapse
that was a rom problem
my phone is not turning on pls help after updating one ota of marshmallow security patch 1 jan
anks095 said:
Just flashed the CM12.1 through twrp ,problem is solved in a way.
Click to expand...
Click to collapse
Is cm12.1 support direct volte calling,.? Or any other custom rom which support volte calls???.

Bricked, always loops back to splash screen

Title says it all. Fastboot works, flashing works. Even if I try to charge the phone on power off condition, it loops infinitely to splash screen. Tried flashing both custom and official ROMs via fastboot. I don't think this is an emmc problem since I can still format and erase all partitions.
Before all of this, I used the official RR Nougat ROM. Everything works fine until it suddenly bootloops out of thin air.
bakanui said:
Title says it all. Fastboot works, flashing works. Even if I try to charge the phone on power off condition, it loops infinitely to splash screen. Tried flashing both custom and official ROMs via fastboot. I don't think this is an emmc problem since I can still format and erase all partitions.
Before all of this, I used the official RR Nougat ROM. Everything works fine until it suddenly bootloops out of thin air.
Click to expand...
Click to collapse
Flash stock firmware with QFIL
mshoaib7 said:
Flash stock firmware with QFIL
Click to expand...
Click to collapse
I have tried to flash via QFIL, but it stopped midway flashing the system and device won't turn on now
I guess it's just me messing up somehow with the cables or something
Thank you anyway mshoaib7!
https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
Try this one. May help u. Extract from official ROM. And flash those things. System IMG is not needed if u have any old backup means. Flash use this. Go to recovery and restore old one.
Bcz system image is large, so sumtyms it fails to flash. That's y I said lrave the system data image flashing and restore the backup.
mshoaib7 said:
Flash stock firmware with QFIL
Click to expand...
Click to collapse
@mshoaib7 bro you like idli or dosa??
Give it to service centre
bakanui said:
I have tried to flash via QFIL, but it stopped midway flashing the system and device won't turn on now
I guess it's just me messing up somehow with the cables or something
Thank you anyway mshoaib7!
Click to expand...
Click to collapse
bro use downloader the flash tool which is already given in the stock firmware if still it get stuck in the middle then it is driver problem then format u r pc or use friend pc
how to properly revert back from mm or nougat roms to stock kitkat rom?
I was on cm13 by ed300, then I tried to restore nandroid backup of stock kk via twrp
then my phone stuck on boot logo, only fastboot mode works, then flashed twrp and stock kk rom after some attempts.
So what are the steps to successfully revert back to kk? (in case this problem happens again in future)

Stuck in BOOTLOOP

Hi !!
First, i tried to flash Resurrection Remix ROM but i stucked in BOOTLOOP
And then i flashed latest stock rom Version: V9.5.9.0.ODHMIFA using mi flash but i had a problem that when i wan to connect to WiFi it will say save then disable but never connect so i flashed the stock rom again and i still getting the WiFi problem and i flashed the rom for the third time and i got stuck in weird BOOTLOOP, the device will start normally but after few minutes it will restart over and over and over, so what should i do ? can anyone help me ?
that's all and i'm sorry if my english is bad
SooMi22 said:
Hi !!
First, i tried to flash Resurrection Remix ROM but i stucked in BOOTLOOP
And then i flashed latest stock rom Version: V9.5.9.0.ODHMIFA using mi flash but i had a problem that when i wan to connect to WiFi it will say save then disable but never connect so i flashed the stock rom again and i still getting the WiFi problem and i flashed the rom for the third time and i got stuck in weird BOOTLOOP, the device will start normally but after few minutes it will restart over and over and over, so what should i do ? can anyone help me ?
that's all and i'm sorry if my english is bad
Click to expand...
Click to collapse
if u want to use custom rom just follow proper steps and it will install.
-unlock bootloader (which i assume u already have)
-fastboot boot latest twrp
-do a full wipe and reboot to bootloader.
-again fastboot boot the latest twrp
-now copy rom,gapps,magisk(mandatory) and twrp installer(optional)
-install rom and twrp installer only
-reboot to booatloader and fastboot boot twrp again or if u installed twrp installer just reboot to recovery.
-now flash magisk and gapps
-reboot system
By mistake if u flashed factory.bat then read this : https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
if your phone is rebooting after every 60 sec then u most probably corrupted /persist. Don't worry custom roms will work without any problem as they don't touch persist.
did you by chance used flash_factory.bat in mi flash tool ?
anshu945 said:
if u want to use custom rom just follow proper steps and it will install.
-unlock bootloader (which i assume u already have)
-fastboot boot latest twrp
-do a full wipe and reboot to bootloader.
-again fastboot boot the latest twrp
-now copy rom,gapps,magisk(mandatory) and twrp installer(optional)
-install rom and twrp installer only
-reboot to booatloader and fastboot boot twrp again or if u installed twrp installer just reboot to recovery.
-now flash magisk and gapps
-reboot system
also if u want to use stock rom read this : https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
if your phone is rebooting after every 60 sec then u most probably corrupted /persist. Don't worry custom roms will work without any problem as they don't touch persist.
also did you by chance used flash_factory.bat in mi flash tool ?
Click to expand...
Click to collapse
thank you for help
i will try to use custom rom and i hope it will work
and i did use flash_all_lock_crc.bat in mi flash tool then i'm start getting the restart problem with unread sim card
use flash_all_lock.bat only or flash all except storage.bat or flash_all.bat .except these nothing else.
flash custom rom or flash_all_lock.bat in mi flash tool (it will work work most probably).
anshu945 said:
if u want to use custom rom just follow proper steps and it will install.
-unlock bootloader (which i assume u already have)
-fastboot boot latest twrp
-do a full wipe and reboot to bootloader.
-again fastboot boot the latest twrp
-now copy rom,gapps,magisk(mandatory) and twrp installer(optional)
-install rom and twrp installer only
-reboot to booatloader and fastboot boot twrp again or if u installed twrp installer just reboot to recovery.
-now flash magisk and gapps
-reboot system
also if u want to use stock rom read this : https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
if your phone is rebooting after every 60 sec then u most probably corrupted /persist. Don't worry custom roms will work without any problem as they don't touch persist.
also did you by chance used flash_factory.bat in mi flash tool ?
Click to expand...
Click to collapse
problem solved !!
first, i tried to flash custom rom with your steps but it didn't work for me, getting stock in boot logo
then i tried the solution in thread u give me, i flashed tissot_images_7.8.23_7.1 via mi flash tool then i restored restore persist partition and everything work great !!
wifi and sim card works fine, thanks man for your help :good:
great, just keep in mind not to flash factory.bat or any other bat files except the three i mentioned above.
anshu945 said:
great, just keep in mind not to flash factory.bat or any other bat files except the three i mentioned above.
Click to expand...
Click to collapse
ok i will, thanks again
anshu945 said:
great, just keep in mind not to flash factory.bat or any other bat files except the three i mentioned above.
Click to expand...
Click to collapse
sorry for bothering, but now i have 'no service' issue, the phone read the sim but it shows that i have no service
do u have any idea to fix this ?
SooMi22 said:
sorry for bothering, but now i have 'no service' issue, the phone read the sim but it shows that i have no service
do u have any idea to fix this ?
Click to expand...
Click to collapse
now to recover imei follow the same guide above, if u have trouble editing qcn let me know.
hi, i need some help with reflashing the stock rom
its always stuck on pushing the system neither manual nor using mi flash.
here i attached the log file, wish it help in some way.
littlecrap said:
hi, i need some help with reflashing the stock rom
its always stuck on pushing the system neither manual nor using mi flash.
here i attached the log file, wish it help in some way.
Click to expand...
Click to collapse
you followed this guide?
YayJohn said:
you followed this guide?
Click to expand...
Click to collapse
no i dont follow the guide you mentioned, i dont know whats wrong but its always stuck in writing system b
the log says its ok but no further action.
littlecrap said:
no i dont follow the guide you mentioned, i dont know whats wrong but its always stuck in writing system b
the log says its ok but no further action.
Click to expand...
Click to collapse
You can try following the guide I sent u but if it doesn't work I can't help you

Categories

Resources