I've been trying to change my device from CN to WW but when I get to the last part of sideloading my device is not reconized.
error: device not found
It shows my device in device manager with a yellow symbol, I tried adding the drivers manualy but it just returns an error also.
I'm new too android after 6 years of having an iphone and I'm pretty frustrated I can't update to kitkat
did you fix it?
Related
Hi,
-A few months ago i installed kingroot and rooted my Wiko Bloom(MediaTek MT6589). A couple of days ago i tried to update the firmware and i forgot to unroot first. the result is a softbricked phone.
- When the phone tries to boot it gets to a point where i get android with exclamation "no command".
- Besides this, not always is the phone detected on windows, when its detected it shows up as usb descriptor failed.
I can enter recover, but if i try to update from sdcard it shows /mnt/sdcard/, when the real path should be /mnt/sdcard0/, and i cant change it.
- I installed android sdk and google usb drivers but windows wont let me use them because the phone is not properly detected.
- I dont know what else can i do, i even searched for a usb jig but it seems they only support samsung phones.
Can someone help me recover my phone? I believe i have to unroot it first and then install official firmware, but i have no info or idea on how to do it since adb tools cannot detect my phone.
Thank you so much
:good:
My Zenfone 5 received today an OTA update (3.24.40.78) and I authorized it, but it went into a bootloop, maybe because it was rooted (I had the 3.23.40.52 version until now).
I couldn't risk not backing up some of the data I had in the internal memory, so I decided to try TWRP and it really helped on that issue (doing a backup).
But now I am stuck with a (soft) bricked device, and I really (!!!) need help with it.
I also have tried factory resetting, of course, but all it does is enter the bootloop again.
For some reason, TWRP sideloading is not working on my computer: the device is properly recognized in all modes but sideloading, it just vanishes, then comes back as a USB-connected device again when I mount it or go into bootload/droidboot. I tried updating drivers, uninstalling and reinstalling drivers and devices, etc., but no good. So instead of sideloading I went for the "install" option in TWRP (after copying the files to the internal memory, of course). But here is the bad part, I have tried four different versions and none work:
2.22.40.54: it shows "Device image SKU:" and nothing comes after that, then states "OTA image SKU: WW" (my device is WW!), then gives the following error:
Code:
assert failed: getprop("ro.build.asus.sku") == "WW"
return code 8
5.3.3.3 [i.e., trying to downgrade from Lollipop to Kitkat]: approximately the same error. It also leaves blank after "Device image SKU:" and, after stating "OTA image SKU: WW", it says "Please use the right SKU for updating".
3.23.40.52 [i.e., trying to go back to the version that was installed until today]: it says "Only higher than Android 4.4.2 20150409 image version can upgrade to Android 5.0" (but I was already on 5.0!).
3.24.40.78 [i.e., trying to properly install the latest version, that bricked my phone]: the error is "Only Android 4.4.2/Android 5.0 20150522-20151001 image version could upgrade with this package".
On all four cases it ends saying there as an error executing the updater binary in the chosen zip file.
My device was always WW, but I even tried tried to "change from TW" to WW by flashing fastboot and recovery img files from one of the zips, but all I got was a dead android robot logo, so I installed TWRP back again.
Please help...
I have a problem with my Paris X device. I had an unofficial rom and I wanted to flash the official one. When I started the flashing process with SP flash tool I got this message: "BROM ERROR: S_INVALID_BBCHIP_TYPE (0x3EB)"
Since that my phone is like dead. I cant switch on, I cant either flash again because my driver disappears in 2 seconds and I got the same error everytime.
Please help me, I would really appreciate it. :fingers-crossed:
hi i also bought paris x last year tried to flash it today using sp flash tool with official android 6 rom everything fine until i clicked download...
pmt changed rom - error #1
so then i looked up im supposed to switch to firmware upgrade but that resulted in error
s_invalid_bbchip_type - error #2
now my phone is bricked and whenever i connect it to my pc it appears for about 2 seconds and then disappears...
well im hoping that someone here could actually help cause this is really frustrating and i need to be able to use my phone next week... :/
thanks for replys
same probleme here
invalid bbchip type (0x3eb)
If anyone have this solution, Then please reply
I have also this type of problem In my Intex ace mini mobile
I also experienced problems like that, and couldn't solve it.... ERROR: S_INVALID_BBCHIP_TYPE (1003)
slekdor50 said:
I also experienced problems like that, and couldn't solve it.... ERROR: S_INVALID_BBCHIP_TYPE (1003)
Click to expand...
Click to collapse
Check the scatter, make sure that the line, i.e. matches the device chip type:
platform: MT6735M < -- is this correct?
peti2ty said:
I have a problem with my Paris X device. I had an unofficial rom and I wanted to flash the official one. When I started the flashing process with SP flash tool I got this message: "BROM ERROR: S_INVALID_BBCHIP_TYPE (0x3EB)"
Since that my phone is like dead. I cant switch on, I cant either flash again because my driver disappears in 2 seconds and I got the same error everytime.
Please help me, I would really appreciate it. :fingers-crossed:
Click to expand...
Click to collapse
I think this is scatter file mismatch, because I have done a proper read back of Inew L4 mt6735 to flash it to another phone with exact same model and build. But that flash file is not even working to flash that phone from which I made it giving this same error.
ERROR: S_INVALID_BBCHIP_TYPE (1003)
Still working on it.
[Update]
Only a single "m" in MT6735M in scatter file was missing, now its working all fine. :fingers-crossed:
I searched the whole internet for years to solve this error...
So if your getting this error better check your scatter platform names etc.....bcz even if you get it from readback or official flash files, like in my case it can give you error.
If you're getting this same error every time so try the above advice and here is a tip for early disconnection, connect while holding volume button or open yiu device and find kcolo[\B] and short it with GND.(better find details from google bcz i am too funding it)
Hello , Guys
Since you all probably know, Lenovo A7020a48 has Android 6.0 Marshmallow which cannot be rooted because of the following :
1 - We got a locked bootloader, we can't flash or boot into custom recoveries and sadly at the moment I couldn't find a way to unlock it.
2 - We don't even have a custom recovery made for that model yet, I tried different version of TWRP for A7020a40 ~ A7020a46 models and they all crashed upon booting to them.
3 - Kingroot and similiar apps can't root Android 6.0.
So the only way to root your phone would be to downgrade it to Android 5.1 Lolipop which is easy.
Here is download links for the stock roms :
A7020a48_LL_S125_160419_ROW.rar.7z
A7020a48_S259_160721_ROW.7z
When you finish downloading please don't forget that we are going to use the SP Flash Tool provided in the rom as only that version "SP_Flash_Tool_5.1552.00" worked for me with no errors however with latest versions i got problems.
Obviously you are going to install the USB drivers and CDC drivers located at the "DRV_Tools" folder in the rom you downloaded.
after installing the drivers correctly turn off your phone, open SP flash tool, and choose the scatter file located at : "\SW\target_bin\MT6755_Android_scatter.txt" and then choose "Download Mode" then wait for it to finish checking the files, then click on the download button on the top left corner.
Then connect your device and wait for it to detect the device .
Wait until the flashing is complete Then After the green circle appears, simply disconnect your phone and boot into system normally.
Note: You might see a black box in the bottom left corner saying "efuse flash done or similar stuff" don't worry about it" it won't appear again however if you got an error saying "DL image failed" then you did something wrong repeat the previous steps again and make sure you choose everything correct especially your rom.
Now to the last part, finish the first time setup screens by skipping most of them and DO NOT UPDATE YOUR SYSTEM AT ALL
if you got a notification to update, simply ignore it or press cancel, and open google chrome, download king root and wait for it to simply root you phone.
Congratulations that's the first part for rooting your phone.
Now to Fixing Your IMEI
Simply Enable USB debugging in options and enable OEM unlocking.
Then power off your phone.
Download this tool : MauiMETA_v9.1635.23.rar
Yes Again it has to be that specific versions, with other versions i couldn't connect to my device however with this version i could.
Extract it to a random location on your pc and MauiMeta.exe and click on options and enable "enable composite kernel usb (adb)" then click on reconnect.
Now you have to connect your device with usb and turn it on, don't worry MauiMeta will change the boot to META mode automatically after it starts booting leave it as it's and wait for the tool to connect to your phone.
***After it connects simply choose IMEI download and a new window should appear, first click on upload from flash button then click yes to retrieve the modem file from your phone, then simply type your IMEI ( Please note that changing your IMEI is illegal however you should only use this method to fix your IMEI not change it ! , you have been warned)
Note : IMEI numbers should be 15 numbers however with MauiMeta you should only type the first 14 number as the 15th number is only a checksum number and will be added automatically.
After typing the IMEIs and checking them simply click on download to flash.
After it says "flashing is successful" then close the window and click Disconnect, and your phone should turn off automatically and you should start it up again.
*** Note : If you have a corrupted NVRAM file on your phone then you are lucky since that rom comes with the modem db file as well to fix NVRAM issues, simply click "Change NVRAM database file" then click No to choose the file, The file exists in the ROM package you downloaded earlier in the following location : "SW\modemdb\MDDB_InfoCustomApp....etc.EDB" and continue the rest of the steps normally.
Please Note that I won't provide support for this, I have only created this tutorial to save time for other people and I'm not expert yet to fix all the problem you may face however after following these steps i managed to root my device and even fix the invalid imei errors i got.
Also if you found errors in my thread or mistakes Please let me know so i can fix them.
Good luck and Don't hard brick your phone XD
I get this error in SP FLASH TOOL 5.1552.00- STATUS_SEC_PL_VFY_FAIL (-10*****)
Any idea ?
Error coming?
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
nishkarshxda said:
i got the same error in SP FLASH TOOL 5.1552.00- (BROM ERROR : STATUS_SEC_PL_VFY_FAIL (-1073610746))
Click to expand...
Click to collapse
Use This Version Of Flash tool enable usb and storage checksum hit download ( Use different usb port better use backside of CPU )
Sp-flash-tool-V5-1548
10000% Working
mobile not getting switched on after downgrading
Hi, I tried to flash my Lenovo vibe K5 note (a7020a48 4 GB RAM). It was done without any error but I couldn't switch on my mobile nor it was detected in my computer. Please help me
Bro i download and flashed successfully but phone cant turn on but i flashed again marshmallow phone will turn on...Why lollipop cant boot... Second link for rom is lollipop or not
Any proof?
Bro where did you get these two rooms from? Tell us the source. Otherwise, how will we know?
after flash mobile no on anybody can u help me to how to flash 5.0 in lenovo k5 note
It worked great thanks .......though minor glitches may occur such as not playing any sound and not supporting JIO sim card. These can be fixed by System Updating your phone to the latest version preferably through a sound wifi connection.
Guys,
Been struggling with my Vertu for a long time and thought of bringing it here.
Basically, im trying to reinstate the Firmware on my Vertu and looked at this link.
Rooted the phone successfully via KingoRoot
I am able to get to the point where I have the drivers and the flashtool ready.
1. Consistently I found an error while I tried to mount the "scatter file" but then I saw a video where someone opened it and added ## in the first line and mine loaded correctly.
2. Now when I try to run the update, it gives me a BROM error S_INVALID_BBCHIP_TYPE(0x3EB)
OR Failed to get PMT Info
Any idea how I can get the Firmware loaded ?
Can someone please try and help this guy get his very expensive phone working.
https://www.google.com/search?q=BRO...nt=ms-unknown&sourceid=chrome-mobile&ie=UTF-8