Hello, excuse my English but I'm Spanish and I used the translator, I hope someone can help me, it is that I have a fova orange and tinkering delete accidentally the launcher or something, the issue is that the battery alone carrying 50% and I made a reset from recovery and the result was catastrophic lol, to turn all black was seen and only the time and the battery appears, unfold the notification menu and just have no access to anything, I say I was root with kingroot but not There is no backup.
I tried everything:
1- from the factory recovery can not install an update that I found in the forum because I E: error in /tmp/sideload/package.zip (status 7), as original rom also gives me another error and this in CPB format.
2- from adb I can not because I have usb debugging enabled in fastboot mode and I did not recognize the PC and can not find anywhere drivers (ignition normal if recognized) plus I guess you also need the usb debugging.
3- I tried from the same phone but heard nothing but notifications can not be accessed.
Well that's all lol friends if anyone has any formulation would appreciate.
Cheers
sebas1979 said:
Hello, excuse my English but I'm Spanish and I used the translator, I hope someone can help me, it is that I have a fova orange and tinkering delete accidentally the launcher or something, the issue is that the battery alone carrying 50% and I made a reset from recovery and the result was catastrophic lol, to turn all black was seen and only the time and the battery appears, unfold the notification menu and just have no access to anything, I say I was root with kingroot but not There is no backup.
I tried everything:
1- from the factory recovery can not install an update that I found in the forum because I E: error in /tmp/sideload/package.zip (status 7), as original rom also gives me another error and this in CPB format.
2- from adb I can not because I have usb debugging enabled in fastboot mode and I did not recognize the PC and can not find anywhere drivers (ignition normal if recognized) plus I guess you also need the usb debugging.
3- I tried from the same phone but heard nothing but notifications can not be accessed.
Well that's all lol friends if anyone has any formulation would appreciate.
Cheers
Click to expand...
Click to collapse
Do you have a custom recovery ? If yes then making a flashable zip of a launcher and flashing it will solve your problem
sdeepb said:
Do you have a custom recovery ? If yes then making a flashable zip of a launcher and flashing it will solve your problem
Click to expand...
Click to collapse
The recovery is the original.
Thanks for your answer.
sebas1979 said:
The recovery is the original.
Thanks for your answer.
Click to expand...
Click to collapse
Is your stock recovery capable of flashing non OEM zips ?
I tried to install zip original and non-original and always gives me errors and similar errors signature except an update that gives the following error :
"/system/app/logkit.apk" has unexpected contents.
E:Error in /tmp/sideload/package.zip (status 7)
sdeepb said:
Is your stock recovery capable of flashing non OEM zips ?
Click to expand...
Click to collapse
I tried to install zip original and non-original and always gives me errors and similar errors signature except an update that gives the following error :
"/system/app/logkit.apk" has unexpected contents.
E:Error in /tmp/sideload/package.zip (status 7)
Related
First Sorry for my Bad Englisch. I am German.
I have brick my Tablet wth LCD Screen Resolution App
I Chance the Value, now on Boot the Homesceen crash.
I have make a Facory Reset, now the Tablet Say
OLS Terminated
Press ok
The Recovery will not work signed-nbx03_007-ota-120803058.zip
Erohibit update as a result of checking version or base sku
The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell do nothing.
4.0.3r1a
the _hack_recovery.zip tell me
assert failed: file_ getprop /system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2/THMAS11001/11001.003:user/release-keys"
file.getprop/system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys-keys
E:Error in /tmp/desklunvr/desklunvr.zip
status 7
I can not put the Device in USB MODE.
False recovery.zip?
adb devices say nothing in Recovery mode
Same problem
Koto99 said:
First Sorry for my Bad Englisch. I am German.
I have brick my Tablet wth LCD Screen Resolution App
Chance the Value now om Boot the Homesceen crash.
I have make a Facory Reset not the Tablet Say
OLS Terminated
Press ok
The Recovery will not work signed-nbx03_007-ota-120803058.zip
Erohibit update as a result of checking version or base sku
The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell do nothing.
4.0.3r1a
the _hack_recovery.zip tell me
assert failed: file_ getprop /system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2/THMAS11001/11001.003:user/release-keys"
file.getprop/system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys-keys
E:Error in /tmp/desklunvr/desklunvr.zip
status 7
I can not put the Device in USB MODE.
Click to expand...
Click to collapse
I'm having the exact same problem after using FLASHER 2.1. Tablets gets stuck on the S.O.N.Y logo and I can enter the recovery screen, however no access through the USB to my files, already try the factory reset and still nothing. I would even consider installing the official firmware even if a lose root. I don't have the_hack_recovery.zip or any key. What can I do? I've been looking for solutions for over two days now.
I will appreciate any suggestions. :crying:
Now a have testes this
As long as your 'region.zip' file is not damaged, then for 99% your tab can be fixed.
Firstable try to flash this: 3.2.1r2 firmware
if not works, then try this:
signed-nbx03_016-ota-120803071.zip,
in fot works, then try this:
signed-nbx03_001-ota-120803002.zip
In most cases it works. If it will fail then:
1. Boot into RECOVERY;
2. Try to flash the update again - it will fail - thats ok;
3. Wait for 2-3min to get adb available;
4. Use 'adb pull /tmp';
5. Post your recovery.log and region.prop files.
http://forum.xda-developers.com/showthread.php?t=1515720
Hooray, Horray is a Glory Day (for me and i Hope your can this Help again)
The Flashing signed-nbx03_016-ota-120803071.zip will work vor me. Now i have 4.0.3 r1
The Link for http://info.update.sony.net/ST002/nbx03_001/contents/0016/signed-nbx03_001-ota-120803002.zip
are Down.
Dammed
Is it possibel to improve the Backup for future Times again?
Possibel to make a Backup that aways Restore the System if it fail`?
The LCD Screen Things can simpel Brick a Unit is dammed
I have Rootet an set up Boot Loop Protection. What do this Option without USB Debugging?
Please help me to improve the Recovery for the Future
$40 to the person that helps me fix my tablet S
Koto99 said:
Now a have testes this
As long as your 'region.zip' file is not damaged, then for 99% your tab can be fixed.
Firstable try to flash this: 3.2.1r2 firmware
if not works, then try this:
signed-nbx03_016-ota-120803071.zip,
in fot works, then try this:
signed-nbx03_001-ota-120803002.zip
In most cases it works. If it will fail then:
1. Boot into RECOVERY;
2. Try to flash the update again - it will fail - thats ok;
3. Wait for 2-3min to get adb available;
4. Use 'adb pull /tmp';
5. Post your recovery.log and region.prop files.
http://forum.xda-developers.com/showthread.php?t=1515720
Hooray, Horray is a Glory Day (for me and i Hope your can this Help again)
The Flashing signed-nbx03_016-ota-120803071.zip will work vor me. Now i have 4.0.3 r1
The Link for http://info.update.sony.net/ST002/nbx03_001/contents/0016/signed-nbx03_001-ota-120803002.zip
are Down.
Dammed
Is it possibel to improve the Backup for future Times again?
Possibel to make a Backup that aways Restore the System if it fail`?
The LCD Screen Things can simpel Brick a Unit is dammed
I have Rootet an set up Boot Loop Protection. What do this Option without USB Debugging?
Please help me to improve the Recovery for the Future
Click to expand...
Click to collapse
Hello Koto99
Thanks for your reply, I tried running the signed-nbx03_016-ota-120803071.zip and it didn't work, I'm looking everywhere for the signed-nbx03_001-ota-120803002.zip which should work for me, since my tablet was bought in the U.S. but it isn't available anywhere. I can't access the tablet through the ADB Shell, I press option 6 on the main menu and it does nothing. When I'm in the recovery mode I can see windows asking for drivers for a device named Sony, but none of the adb drivers work. If I go to the Sony logo I have it recognizes the MTP USB device and it looks ok for about 40 sec. and then it puts the yellow exclamation mark. I really need to get this tablet fix, I'm willing to donate $40.00 to the person that helps me restore it.
signed-nbx03_001-ota-120803002.zip.
Have you See the Cordi Mirror?
http://forum.xda-developers.com/showthread.php?t=1515720
First Cordi Posting down the Posting
Files mirror - My Google Drive
Good Luck
Koto99 said:
signed-nbx03_001-ota-120803002.zip.
Have you See the Cordi Mirror?
http://forum.xda-developers.com/showthread.php?t=1515720
First Cordi Posting down the Posting
Files mirror - My Google Drive
Good Luck
Click to expand...
Click to collapse
I also uploaded (not realizing condi had an upload).
he tried the file and it did not help him (so off to Sony it goes )
Stifilz
Help
Find attached my build prop and recovery. What files do I need to recover my bricked tablet.
Can you give me your build.prop (I mean the one in /system/) and can you enter the system at all?
Sent from my Sony Tablet S using xda premium
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
I have downloaded many rom from your site only
but
some are saying E: invalid OTA
and some are saying
E: signature verification failed
Signature verification failed
installation aborted.
Also i have complain that i have seen many threads here on which you all reply very fast but no one is replying on my thread
This is my 4th or 5th thread .
My mobile is not working , when i am powering it on and open its lock it says " Unfortunately, Launcher has stopped. :crying:
TanzeelKhan said:
I have downloaded many rom from your site only
but
some are saying E: invalid OTA
and some are saying
E: signature verification failed
Signature verification failed
installation aborted.
Also i have complain that i have seen many threads here on which you all reply very fast but no one is replying on my thread
This is my 4th or 5th thread .
My mobile is not working , when i am powering it on and open its lock it says " Unfortunately, Launcher has stopped. :crying:
Click to expand...
Click to collapse
Sorry you are having trouble, but you included absolutely no information that could be helpful for pointing you in the right direction. We don't know:
Your phone
What update it's on
What recovery you are using
What roms you have tried
Without that info, no one would have a clue on how to help you.
Information
My mobile is " Peace mobile "
it is having android 4.0.4 ICS
I Want to install a new ROM because some files in " FILE SYSTEM ROOT " are deleted by mistake
i cannot power it on . I only have access in recovery mode and factory mode , from there only i can update , i do not have access in the mobile i have also posted earlier about this " FILE SYSTEM ROOT" problem 50+ reviews but no reply.
you can see to it here : " http://forum.xda-developers.com/android/help/deleted-file-root-ect-vendor-t2928314 "
plzz help if you could .
or if there is no solution please let me know .
But please don't ignore .
this phone use mt6739.so i want to flash it the twrp to my phone.i dunno to unlock the bootloader but the twrp file not have for this device.
I just saw this post as I too have a Honor 7S
There is NO TWRP for our device.
The TWRP for the Honor 7A/7C/7X and Honor 7 doesn't work on our device and you got to pay 4 euros to unlock the bootloader before you can even flash TWRP (and there isn't one)
This Device is treble compatible but now I've found out there is zero development and no Devs Interested in it it's a complete and utter waste of time and has gone back into its box, never to be seen again.
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Samuel Ladziansky said:
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Click to expand...
Click to collapse
Hi I have a problem. I'm having brom issues in trying to flash it
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
usab1oy said:
Hi I have a problem. I'm having brom issues in trying to flash it
Click to expand...
Click to collapse
and little hint
dont flash whole rom if the phone can boot becasue after clean flash "format+download"
you lost log and cust partition because the image files are not secureboot signed and your phone get in to bootloop
and also you lost imei codes so no cellular after that
If you do so
you can fix it in that recovery were I enabled option to format log partition
after you format log to ext4, your phone will boot but without huawei/honor bootanimation
you dont need to worry about cust partition, if you didnt format it it still boot but without bootanimation and you lost some of garbage apps that are in that partition (amazon etc...)
(twrp boots in russian language, idk for now how to change it to boot in english or slovak lanuage (because Im from slovakia) and also it have Lenovo Logo becasuse I use sources from Lenovo A5 that have same cpu)
I will make in future separated thread for this....
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Samuel Ladziansky said:
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
Click to expand...
Click to collapse
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
usab1oy said:
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
Click to expand...
Click to collapse
you can patch it or flash it without disconecting the battery
Here is how:
turn it off
Push and hold volume down
While holding volume down connect usb cable
But is recomended to disconect battery because the phone can boot up instead to go in flash mode.
usab1oy said:
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Click to expand...
Click to collapse
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Samuel Ladziansky said:
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Click to expand...
Click to collapse
Yeah. For the flash mode, I wonder why his own he said I need to hold the volume up and down button at the same time. But thanks I'll do it and let you know.
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Samuel Ladziansky said:
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Click to expand...
Click to collapse
At this point. Might just abandon it. Thanks for everything. Ran into laptop issue on my third trial lol.
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Samuel Ladziansky said:
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Click to expand...
Click to collapse
Honestly. I spend a whole night researching videos for the phone. Only to get that link I send. And after all that. It still didn't work. Lol. I have a Poco x3 pro. I wonder if snapdragon android 12 can be rooted. Probably going to try it next month or so.
Snapdragon is eazy for root.
I have Redmi note 11 and it was easy, now I running on Android 13 from stock android 11, if you will need some help with something, I'm here, and I think there is device forum so there is community for that device
Hello guys! I have a problem with one phone that i am trying to fix for someone and I feel sooo, sooo completely lost in all of this as I know almost nothing about this. The cell phone model that is in question is Alcatel One Touch Pop C3-4033x.
It seems to be using a Mediatek chipset and I was reading some of your advices here & there and tried using the program called SP FlashTools but it always resulted in error, in the end. It seems that something is wrong with this phones emmc flash memory. So, I tried transfering some files as a zip files to the SD-card and tried to apply update from it, but it said always: Installation aborted. And then, I have tried looking for a way to flash stock firmware of that specific Alcatel model on SD-card, but I just don't have any clue how to do it, if it is possible, even. Maybe I should just give up trying?
Oh, I almost forgot to write that the phone doesn't have the access to Android OS and USB debugging isn't turned on, because computer doesn't seem to list it and I don't know if there any button combinations that Alcatel uses for this model to get into that fastboot or adb mode, even though have installed mediatek drivers. It can only get into Android System Recovery 3e. That seems to be everything, I think, at least.
Oh guys, I am so, so, so sorry if I am bothering you with this. I just didn't know what or where else to ask this. Thank you sooo much!
Hi download those files:
Firmware:
https://www.mediafire.com/file/bpm4ibsbmr4q6nc/OT-4033X-Without_Mobilis_logo__BY_GSMSERVE.rar/file
SP Flash tool:
https://androidfilehost.com/?fid=11410963190603870440
Driver:
https://mega.nz/#!8VYkQCxD!fkhTrZwFFILDAglO1cR_8pIM4Cel52brZ7RB6QZoc6o
Once you downloaded all right driver open SP flash tool and add Scatter file
MT6572_Android_scatter.txt
Click on Download , connect your phone without battery and see if the process is going on if not try again with battery inside.
If you end up with error do the same thing but now first do Format then after is Finish do Download. Good luck ...
It still displays error :/
Teddy Lo said:
I have tried to do everything like you have said, but it still displays error when i press the Download button, and it displays that error after some seconds pass and also the same happens hen i try to use the Format function. This is the error it displays when i tried with the download button: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3149)
And this is the same error it displayed when i tried using the Format function: S_DA_SDMMC_WRITE_FAILED (3149)
i am so, so sorry for bothering with this.
Click to expand...
Click to collapse
Try with another version of SP Flash tool little bit newest .