Related
I tired to restart phone after noticing that WI-FI isn't working (maybe my internet was laggy, don't know). After restarting phone was stuck on LG logo, i tried many times but again LG logo.
Then i started recovery, and wanted to flash some new ROM. But my CWM won't recoginze my SD card (to add, i wasnt using SD card with this phone). I tried other SD but problem stays. I google it and found out that maybe CWM needs update?
Version of CWM Recovery v6.0.3.1
This shows up when recovery starts..
E:Cant mount / cache/recovery/command
E:Cant mount / cache/recovery/log
E:Cant open / cache/recovery /log
E:Cant mount / cache/recovery/last_log
E:Cant open / cache/recovery/last_log
How to unbrick phone now?
Unfortunatly don't know what ROM was flashed before, or is bootloader unlocked or not. (coming from LG 3D, LG l9 was present. LG 3d methods for flashing is diffrent, so im little confused how to start anything now)
To add that phone now cannot turn on without charger pluged in. Powering on was OK in first few time...
First and important question. Did you unlock your booloader? If yes, you can install cutom roms. If not, you can't install custom roms.
Did you also try to enter SV mode?
1. Power off phone
2. Press and hold volume up
3. Connect phone by usb to PC
4. Wait few sec
5. SV mode should appear.
When you are in SV mode, you can restore stock rom by official LG program.
Rammar515 said:
First and important question. Did you unlock your booloader? If yes, you can install cutom roms. If not, you can't install custom roms.
Did you also try to enter SV mode?
1. Power off phone
2. Press and hold volume up
3. Connect phone by usb to PC
4. Wait few sec
5. SV mode should appear.
When you are in SV mode, you can restore stock rom by official LG program.
Click to expand...
Click to collapse
I started S/W upgrade, and in upper corner it says Bootloader Status: unlocked. So bootloader is unlocked for sure then..
If i manage to update CWM will that solve my problem with SD card? After that just to flash ZIP from recovery?
O something else?
ratluci said:
I started S/W upgrade, and in upper corner it says Bootloader Status: unlocked. So bootloader is unlocked for sure then..
If i manage to update CWM will that solve my problem with SD card? After that just to flash ZIP from recovery?
O something else?
Click to expand...
Click to collapse
I dont know but you should update cwm to 6.0.4.5+ After it you will be able to install all roms from 4.2-5.0.
Rammar515 said:
I dont know but you should update cwm to 6.0.4.5+ After it you will be able to install all roms from 4.2-5.0.
Click to expand...
Click to collapse
Thanks, now really noob question..
I googled how to update recovery on L9, and found methods with installing some APK, but as i cannot start system how to flash then?
There is 2 ways to install new recovery.
You can flash .zip in old recovery, reset phone and you will have new recovery.
You can also flash new recovery by fastboot. You need to have .img recovery.
Can you reset to fastboot in recovery options?
Rammar515 said:
There is 2 ways to install new recovery.
You can flash .zip in old recovery, reset phone and you will have new recovery.
You can also flash new recovery by fastboot. You need to have .img recovery.
Can you reset to fastboot in recovery options?
Click to expand...
Click to collapse
Not sure how to enter fastboot. Cannot see restart to fastboot in CWM..
You can try to enable adb in recovery and use command "adb reboot oem-unlock"
Rammar515 said:
You can try to enable adb in recovery and use command "adb reboot oem-unlock"
Click to expand...
Click to collapse
I cannot start fastboot, dont know how, something doing wrong. On CWM i only have, install zip with sideload (something like that)
Can i flash to stock rom from S/W menu? And what i need if can?
You need phone + usb + pc + lg flash tool (just download it) Connect your phone with SV mode and let program find rom, download and install it.
Rammar515 said:
You need phone + usb + pc + lg flash tool (just download it) Connect your phone with SV mode and let program find rom, download and install it.
Click to expand...
Click to collapse
Not sure what to try next.
I tried this http://forum.xda-developers.com/showthread.php?t=2085344 stays on 15%, and PC cannot see phone
this http://forum.xda-developers.com/showthread.php?t=2797190 , someone sad that this worked becaause first method didnt (was same problem as mine, how i understaned ..)
and tried this http://forum.xda-developers.com/showthread.php?t=2748384 , stuck after 6 sec (something like that). I readed that maybe BIN was corrupted (because of conversion from KDZ to BIN), now ill try with thid BIN http://uploaded.net/file/j32p8p7y/from/xh3dqq ...
What next.. S/W mode says Bootloader unlocked, and before all this phone was using JB..
I still didn't succeded to recover my phone.
My computer simply cannot see my phone, i tried all tools that were avalible. On 3% to 7% (on updating), just says that phone is not connected.
Strange thing is that i managed to flash V20H_00.kdz two times. Every single time i do the same but only that 2 times flash was successful. One time was with "offline method" and then with "LG flashtool 2014", after that flashing i got dead android with red triangle both times.
Then i wanted to flash v20c_00.kdz , but cannot pass 3% to 7% on flashing AGAIN. I'm frustrated !
I tried to flash on other computer but again, phone is not recognisable.
What to do now?
Can i flash ROM with fastboot ?
UPDATE.
I started upgrade recovery with LGMobile support tool, and finished flashing. But AGAIN i got dead android with red triangle!
Now what to try!?
Update
I even tried to flash ROM on WIN XP, but nothing. Again proces stops on 3% (then quckly) jump to 7%. And thats it.
Strange thing that when i start UPGRADE RECOVERY on Official LG TOOL (i think thats official), program download 500mb+ KDZ and process is successful, but i get Dead Android with red triangle..
Anyone have any advice? What to try?
I did everything that was stated in the how to's but to no avail. additionally i cant get TWRP installed via fatboot, i have checked and crosschecked usb debugging and unlock OEM , but i cant get it to work , with SP Flash my phone pops up and vanishes in the hardware manager withing fractions of a second so it doesnt work with the sp Flash , in fastboot it wont let me download to recovery even if i use the command line oem unlock , because the volume up button that you have to use to accept[yes] doesnt work , only the vol down[no ] button has an effect, anyone any ideas anyone?
?
Kylekassar said:
I did everything that was stated in the how to's but to no avail. additionally i cant get TWRP installed via fatboot, i have checked and crosschecked usb debugging and unlock OEM , but i cant get it to work , with SP Flash my phone pops up and vanishes in the hardware manager withing fractions of a second so it doesnt work with the sp Flash , in fastboot it wont let me download to recovery even if i use the command line oem unlock , because the volume up button that you have to use to accept[yes] doesnt work , only the vol down[no ] button has an effect, anyone any ideas anyone?
?
Click to expand...
Click to collapse
To use SP Flash tools, turn the phone off, press download on the software then plug the phone in. The preloader is only meant to show for a short time (a fraction of a second to a few seconds) so SPFT needs to be sending the signal to download in that time window.
What I've also found works is to press download on SPFT then press and hold power and volume up until the device starts downloading.
thx for the quick answer i will try a.s.a.p.
Kylekassar said:
thx for the quick answer i will try a.s.a.p.
Click to expand...
Click to collapse
Tried but it doesnt work , i starts the dload but then i end up on brom error : STATUS_PRELOADER_INVALID(0xC0030004) no recovery flashed
Kylekassar said:
Tried but it doesnt work , i starts the dload but then i end up on brom error : STATUS_PRELOADER_INVALID(0xC0030004) no recovery flashed
Click to expand...
Click to collapse
That could be a couple of things:
Which SPFT version are you using? If its an older version try using a newer one.
Or
The scatter file you loaded is not good, download a stock firmware and use the scatter file from that.
Try this:
fastboot flash recovery "filename".img
or
fastboot flash boot "filename".img
Do you have the MTK drivers installed? What does your phone appear as in the Device Manager? Like others have said, once you've chosen your scatter file and recovery to flash, hit download and then plug in the phone.
Managed to fix this? I have the exact same problem and not able to fix it till now....
I'm in a similar situation. I CAN get my phone to flash recovery in SPFT and get a lovely big green tick but when I power off and boot into recovery using power and volume up it boots into the stock android recovery rather than TWRP.
Going another way via ADB, I can get the phone detected but when I send the OEM unlock bootloader command I am unable to use volume up to confirm. Only the volume down key works to cancel.
All I want is to put viper4android on. Never had any issues until this phone.
chandlerp said:
I'm in a similar situation. I CAN get my phone to flash recovery in SPFT and get a lovely big green tick but when I power off and boot into recovery using power and volume up it boots into the stock android recovery rather than TWRP.
Going another way via ADB, I can get the phone detected but when I send the OEM unlock bootloader command I am unable to use volume up to confirm. Only the volume down key works to cancel.
All I want is to put viper4android on. Never had any issues until this phone.
Click to expand...
Click to collapse
Are you 100% sure the recovery.img you flashed was TWRP?
Absolutely. Downloaded from this very site. It was this one: recovery_TWRP_3021_P9000.img
---------- Post added at 02:23 PM ---------- Previous post was at 02:17 PM ----------
Did an OTA update this morning and am showing as on build number Elephone_P9000_20160608 now. Haven't tried flashing since the update as I'm at work with locked down computers. Was going to try again over the weekend. Which recovery and version of flash tools would you recommend trying this time?
thanks for any advice.
Actually I have the same problem.
I tried to reinstall the drivers because it seems to be not the correct one. Here is a pic: i.imgur.com/FoUnVyz.png
After I read somewhere that i can try and hold down Volume+ while connecting my phone to the pc where i started the download in sp tools prior.
I got this error code: STATUS_PRELOADER_INVALID(0xC0030004)
And here I am with a not-up-to-date elephone p9000.
Anybody care to help me?
I'm in the same situation, tried everything - flashtool recovery.img separate in download mode, flashtool in update mode full 7.0 with replaced original recovery.img with TWRP one, played with fastboot with no luck as did not find the way to OEM UNLOCK it - vol + not reacting. Bought the phone on Gearbest, looks like it's locked very hard.
Can't install TWRP
Me too! I've updated my p9000 to latest stock v7 rom with spft. I can't install twrp recovery despite getting a geen tick from spft. Tried four times but it won't overwrite the stock rom recovery. A locked bootloader seems to be the popular diagnosis but spft doesn't use the bootloader. What else could it be? Ideas very welcome.
Did you boot into recovery immediately after flashing? A normal system boot will overwrite TWRP with the stock recovery. Once you start TWRP there is an option to prevent this from happening.
Can't install TWRP
Thanks for the suggestion. I flashed twrp again but it won't boot into recovery afterwards without a restart, just hangs. Stiĺl on stock recovery.
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
EFAYSAL said:
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
Click to expand...
Click to collapse
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
SubwayChamp said:
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
Click to expand...
Click to collapse
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
EFAYSAL said:
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
Click to expand...
Click to collapse
Ok, I guess that your device is actually in bootloop and don´t booting.
Tutorial that you followed has many steps and don´t need to do all this to just root device and it contains some files like lk.bin that you can´t be sure that should be for your device.
Some users use this file (lk.bin) of an unlocked device and think that flashng in other device then get unlock it but no need, your device can be unlock it just follow some commands in fastboot mode.
Now you can do the next;
Try to flash again your rom stock (I guess that you don´t have a backup), if for some reason your official tool doesn´t work then use only some images like boot, system and userdata with the scatter.txt to flash them through SP Flash Tool.
Here a link to TWRP https://youtu.be/6vj_BY6xJdA, you can root it with supersu v2.78 0r v2.82 and here some files that can be usefull too https://drive.google.com/uc?id=0BwJgeCYTpnEHNlg2VUlieHFTYVU&export=download
Update steps that you are following to can assist. What extension has your rom and if it is recogniced for SP Flash Tool. I didn´t ask you if you can enter to fastboot mode and if you can then you can know if your bootloader is unlocked typing fastboot oem info
Most info that you give and some screenie will help to understand better
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
EFAYSAL said:
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
Click to expand...
Click to collapse
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
SubwayChamp said:
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
Click to expand...
Click to collapse
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
EFAYSAL said:
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
Click to expand...
Click to collapse
I´m not sure if you are connecting correctly your device at right time and form to can flash it properly. Every device has more or less a specific way to do it. My last alcatel it was connected just with device power off and after to tap on download, but in other device Blu Dash was connected pressing just vol_up and my last mt6757 Bluboo had to press both vol up and down at time to connect to pc and after to tap on download option. To have sure that is well done increase volume in your pc, you will hear a first sound that is cause pc is recognicing but then you have to hear a second sound that is when SPFlashTool is recognicing device and you will see a red line in down side of the tool window, release button inmediately and let tool to work.
This is a good rom for your device according the author is optimized https://droid1311.blogspot.com/2017/08/alcatel-fl02-aka-flash-plus-2-via.html and this is the link directly if you have troubles with pop-up-adds https://drive.google.com/file/d/0BwAGh1drb91SeDZwV1VXbXpjQWM/view
Also you can try with other versions of SP Flash Tool, most stable maybe should be v5,1628 https://androidmtk.com/smart-phone-flash-tool leth me know how you go
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
SPFlashTool 5.1628:
I try all the way with and without pressing any button but no luck . And when it work finishing with error.
SPFlashTool 5.1628:
I try all the way to get that mode but nothing works. So I try to click download button then conect the phone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
EFAYSAL said:
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
I try all the way to get that mode but nothing works. So I try to click download button then conect the pkone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
Click to expand...
Click to collapse
There is a part that is not variable in the way to use this tool, ever you have to tap on download before to connect device and is recommendable too connect cable usb to pc (not yet to device); from here is when the button that you have to press can vary but like I said you before in my last mt6757 (a very similar to yours) works pressing both vol at same time to connect terminal cable to device and now you will see a red line (could be violet-ish)
Try before just flashing only preloader file to recreate some partitions and then do other flash for the other files.
Of course you have to be sure that all drivers are installed correctly cause this tool needs to put your device in download mode (a special level) and also keep it in this state so find VCOM drivers for Alcatel and adb/fastboot installer and try to uninstalling some older drivers that you don´t use and many times we keep in our pcs and for a short data transmission can helo that all the rom move it in same folder where SPFlashTool is allocated.
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
EFAYSAL said:
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
Click to expand...
Click to collapse
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
- In what android version are you, 6.0?
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
- Did you try to flash just preloader, only this file?
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
SubwayChamp said:
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
Click to expand...
Click to collapse
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
SubwayChamp said:
- In what android version are you, 6.0?
Click to expand...
Click to collapse
Yes, last time it was 6.0 before the root
SubwayChamp said:
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
Click to expand...
Click to collapse
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
SubwayChamp said:
- Did you try to flash just preloader, only this file?
Click to expand...
Click to collapse
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
SubwayChamp said:
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
Click to expand...
Click to collapse
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
EFAYSAL said:
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
Yes, last time it was 6.0 before the root
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
Click to expand...
Click to collapse
You need to try two different ways to flash files and restore your device.
First method: fastboot mode
You need to get device enter to fastboot in order to flash some files like system, boot and userdata, then there are two main methods to do it:
- Pressing pwr + vol down
- And I mentioned that sometimes work pressing both volume button + pwr and a menu have to appear to can select an option to enter to (fastboot mode), in some devices this method is not working but you have to try several times attempting to.
Second method: SPFlashTool
You have to ever press first of all Download box and connect terminal cable to pc and the buttons thhat you need to press at time to connec cable usb to your device may vary, sometimes vol down, sometimes both vol but never pwr button; if pc recognice then you have to release all buttone an let it pc continue the flash process.
If SPFlashTool recognice device first flash only preloader file and select now lk.bin too. Flash only these two files and after do again a new flash with the rest of the files, Why you need to do this? your partitions are corrupted and you need to restore them with these files in order to can flash all another files.
Before all of this charge your battery, if you have a cover removable then extract it some minutes and put it again.
Also I read that for this model it´s used this tool instead of SPFlash Tool https://androidmtk.com/download-sugar-mtk-sp-flash-tool (inside the zip you will find a password to start the tool) but I´m not sure what kind of rom it needs, you have to connect your device to begin the process, you will find in product models section in the tool this variant for your device "FL02"
Try first the other tool and then this and let me know how you go, mtk devices are almost unbrickeable so it´s just to find the appropriate way to return it to the life.
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
EFAYSAL said:
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
Click to expand...
Click to collapse
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
I understand that you tried with Sugar tool with no lucky.
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Is there some custom development, recovery, roms for your device?
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
SubwayChamp said:
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
Click to expand...
Click to collapse
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
SubwayChamp said:
I understand that you tried with Sugar tool with no lucky.
Click to expand...
Click to collapse
Yes. After recognizing it keeps trying to download data but no luck.
SubwayChamp said:
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Click to expand...
Click to collapse
I know it is disappointing!. I try this but no luck.
SubwayChamp said:
Is there some custom development, recovery, roms for your device?
Click to expand...
Click to collapse
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
SubwayChamp said:
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
Click to expand...
Click to collapse
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
EFAYSAL said:
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
Yes. After recognizing it keeps trying to download data but no luck.
I know it is disappointing!. I try this but no luck.
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
Click to expand...
Click to collapse
I´ll tell you some ideas with no any specific order that you can try or see if works.
Really very strange that display stays in black, you told me that flashing files through fastboot is working but doesn´t appear not even bootlogo, connect to pc as it is and see how pc recognices in devices manager and my pc if appears like a determined drive d/e/f so it looks that some bad flashing burn your kernel and this case is similar to when a Samsung device need to use jtag method to revive, if in your country no-one knows about Alcatel devices this could be a similar case to what I´m saying then it could be a clue for a technician. I tell you this cause many time ago when I flashed by error a Samsung s4 and only this method revived my device.
Try this, flash your stock recovery only through SPFlash tool and flash after through Alcatel Download tool your stock rom cause some firmwares need to detect stock recovery first to can flash other partitions.
At this stage don´t you have stock recovery, no? so you can try to format data cause sometimes when bootloader is altered then avoid to boot and formatting data can solve this.
If this recovery twrp is for your device you can try flashing through SPFlash tool, you have to put recovery.img and scatter-txt in a same folder. then if succesfull format data, system, wipe cache and dalvik and maybe later try to port some custom rom would be a way to solve this.
To flash any partition through fastboot this is the syntax, just follow one by one any of the files that are in your rom folder so just follow these, if some of then can´t be flashed don´t worry then it´s not flashable:
fastboot flash boot bot.img
fastboot flash cache cache.img
fastboot flash lk lk.bin
and so on till the end
...But after try this if you didn´t get boot to recovery and obviously you can´t delete data nor system then delete first the next partitions trough fastboot typing:
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase boot
Try all this and let us see how it goes
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
EFAYSAL said:
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
View attachment 4518365
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
Click to expand...
Click to collapse
I see that Sugar tool detects your device like rooted and refuses to flash anything, compare imei number which is in the box, I hope that it couldn´t be changed.
Don´t tell me simply no luck, what it says in SPFlash tool when you tried to flash TWRP and I guess that you put scatter-txt and twrp renamed recovery.img simply in the same folder. Just to be clear, to can flash with this tool your device it has to be off not needed fastboot for this. (provide some screenie)
Other combination of keys to enter to fastboot to flash some partitions when something is missing is, try these three ways:
- Pressing only vol down and at same time connecting to charger (connect first one terminal of cable to your device and then to the charger)
- Pressing the three buttons till a menu appears (you must to release inmediately all)
- Pressing vol up + pwr till a menu appears (you must to release pwr button inmediately) then choose fastboot
In the post 4 I provided a link from Google Drive, in this zip there are 8 items;
- From the item 2 use this version of SP Flash tool, put the four files in a folder and flash them
- In the item 3 you will find some scripts for fastboot, maybe they´re working better and also you have here a subfolder with twrp image.
- And if you get sucessfully install twrp in the item 7 there is a backup with some files to restore from this recovery.
Try one by one and update the info, I hope that your motherboard is not damaged.
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
!!! Whatever you do, it is at your own risk !!!
This procedure will unbrick any Axon 7, returning it to stock. It fixes any kind of brick as long as your hardware is not damaged. You can't damage your hardware using software so if you have a healthy unit, you can recover it from any flashing "accident".
1. GET THE SOFTWARE
You need a Windows PC, Windows 10 is highly recommended. Do this:
01. Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
02. Download the EDL flashable stock firmware package for your model:
A2017 (China): B14_MIFAVOR5 Android: 7.1.1
A2017G (Europe): B10_NOUGAT Android: 7.1.1
A2017U (Americas): B35_NOUGAT Android: 7.1.1
03. Unzip the firmware ZIP file to a folder in your hard drive.
2. ENTER EDL MODE
Option A: USING THE REBOOT COMMAND
If you still have access to your system but not to recovery or fastboot, then you just need to install any terminal app, open it and at the app's command prompt enter:
Code:
reboot edl
. You device will reboot into EDL mode. Now you can safely plug your Device to your computer. In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you'll need to explore the next option.
Option B: USING THE BUTTON COMBO
04. Press the VolUp and VolDn buttons in your device and keep them pressed.
05. Now press the power button until the red LED flashes, it does it really quick. Then release the buttons, starting by the power button.
06. Plug the device to your computer.
In your computer right click in the Windows Start Menu icon and select Device Manager. Under Ports (COM & LPT) your device should appear as Qualcomm HS-USB QDLoader 9008 using a virtual COM port. If you can see it, then you can continue to the flash section, step 14. Otherwise, if you do not see anything or a DFU device, then you need an EDL cable.
OPTION C: USING THE EDL CABLE
So, you need to get a Qualcomm EDL cable. With it you can recover from any situation. I use this one, DrakenFX uses this other model. There are cables out there not working properly so do not try to save 4 or 5 bucks and get yours from a reliable source. Alternatively you can solder your own by following this guide. If you are in an emergency (or your patience threshold is very low) and have a thin wire around you, then you can follow this DIY hack video.
Do you already have the EDL cable? then follow these steps:
07. Connect your bricked Axon 7 to your PC using the EDL cable.
08. Press the EDL cable button and keep it pressed.
09. Press the Power button of your bricked unit and keep it pressed too.
10. Wait 20 seconds.
11. Release the power button.
12. Wait 10 seconds.
13. Release the button of the EDL cable.
Voilà, your device is now in EDL mode. The device manager in your PC, under the ports category, should detect it as Qualcomm HS-USB QDLoader 9008. Now you can proceed to the flash section. If this procedure doesn't work, then your unit could have a hardware problem. Your only hope is to dissemble it by following this last resort guide.
3. FLASH FIRMWARE
14. Open MiFlash in your computer.
15. Click Browse button and select the folder you created in step 03 with the stock firmware files.
16. Click Refresh button and your device will appear listed as virtual COM port.
17. Click Flash button and wait for a few minutes until it finishes. Note that the bottom options are not applicable.
18. Now you have a stock Axon 7. Your data partition will still have garbage data, so you should enter recovery by pressing VolUp while rebooting your device with the power button. Release VolUp only when you reach Recovery. Using Recovery do a Factory Reset of your device.
That was the last step. Hopefully now you have a fully functional stock Axon 7.
By the way, this guide can also be used to return to stock any working device for selling or service!!!!
Cheers!!!!
Nice! I just disassembled mine and did it that way the other day.
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
@Oki
Thnx for this guide :good:
Find the latest A2017G N-B10 here
Harmtan2 said:
Nice! I just disassembled mine and did it that way the other day.
Click to expand...
Click to collapse
Glad to see you solved your issue.
mb0 said:
thank you.
i will save the files and guide for rainy day.
i have A2017 that i converted into A2017U; which file do i need to download?
Click to expand...
Click to collapse
I don't know what you mean about converting an A2017 into an A2017U. They are the same device except for the radio, that that's a hardware difference. You should always use the right modem firmware for your radio hardware so you should use the A2017 modem firmware. After unbricking your unit, you can unlock it again and flash any universal firmware the same way you did before. It is a long but safe process.
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
mb0 said:
yes, i meant to say that i flashed U radio over my A2017
so China version is for me.
Click to expand...
Click to collapse
If you flashed the A2017U radio in a A2017 hardware and worked fine for you, then you can use the A2017U B35 stock firmware.
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
My phone shows up as Handset Diagnostic Interface (DFU) (COM3) but it doesn't get detected on Miflash program......
aLexzkter said:
What will be the bootloader status after following this guide? I need my phone with a locked bootloader.
Click to expand...
Click to collapse
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Oki said:
It should be locked. But in case you end up with an unlocked phone, then locking it is very easy. You only need to connect your phone, enter into fastboot mode, download the adb/fastboot tools and execute the command fastboot oem lock from your computer.
Click to expand...
Click to collapse
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3).
Edit: I managed to get into EDL mode thanks to Axon 7 EDL Tool but I got a "File analysis: error" "not important files found" so I went back to MiFlash and also got an error about the files. Will update the post when I get it to work.
aLexzkter said:
I can't get into EDL mode. I hold down volume buttons, then power. When the red led lights up, I unpress power, then the volume buttons, connect the USB cable and nothing happens on my phone (black display) red led still on. On my computer I see ZTE Handset Diagnostic Interface(DFU) (COM3)
Click to expand...
Click to collapse
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Oki said:
You can enter EDL mode from the system. Just install any terminal app, open it and enter the command reboot edl
Click to expand...
Click to collapse
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
aLexzkter said:
xD My phone was bricked. I thought this tutorial was mainly targeted for bricked devices.
Anyway, my phone is working now. The downloaded EDL zip was corrupt so it only had a few files inside.
@Oki
Edit: I have a working phone on Nougat B10. But I can't lock the bootloader because I don't have access to fastboot. My phone's variant is A2017G
Click to expand...
Click to collapse
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Oki said:
Glad to see you solved your issue. I misunderstood your problem. I thought you had access to the system and not to recovery or fastboot. Anyway, this guide is for unbrick or return to stock. I'll investigate the relock problem. Usually clearing devinfo partition should be enough to relock any bootloader.
Click to expand...
Click to collapse
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
aLexzkter said:
In order to get access to fastboot I had to use the tool Axon7Toolkit, select "unlock bootloader" option, make sure you have an old version of MiFlash installed (20161212) and then you can select "lock bootloader" on Axon7Toolkit.
Thanks for everything.
Click to expand...
Click to collapse
Well, I am considering to link the older Marshmallow ROMs since the Nougat ROMs have some issues with fastboot. Anyway. It is going to take some time to test the alternatives. Thanks for letting us know!
Some of the most recent firmware for Axon 7 (@NFound's B12 bootstack, I think) doesn't support the EDL button combo. But if you have TWRP installed, you can boot to recovery, then reboot to EDL from there.
I kept getting the device registering in device manager in DFU mode. But I noticed that it briefly registers as QUSB_BULK before reverting to DFU. So I installed zadig winUSB driver and now it registers as QUSB_BULK when I turn on the device pressing all 3 buttons.
How can I proceed now?
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Flogisto said:
Hi there
Thanks for this guide. I have a 2017U, so I got A2017U_B35_NOUGAT_FULL_EDL.zip file. After unzipping and connecting the phone to the computer it gets properly recognized and i can start the process from the MiFlash program. After reaching somewhere between 30-40% of the flashing process, it goes suddenly to 100% and it says that is finished. When I reboot the phone, it appears as if I was still under an unlocked bootloader (warning message + TUX penguin image) and the phone starts but during the initial setup process, i chose to start as a new phone but it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device" and obviously this is not what I am interested for.
How can I get rid of this message and get a full clean install, with bootloader relocked and all that??
Thank you for any help you can provide!
Click to expand...
Click to collapse
There ate several ways to remove that. One involves TWRP 3.2.1-7 and the other Axon 7 EDL tool, if you dont have TWRP then use the second . Jusy go to the unlock menu and apply the google unlock.
A third way would be to setup the phone with your old google account and do afactory reset from within Android, not from the bootloader. That would remove also the owner safety.
Thank you so much for your guide and software bundle.
I even had to make a EDL cable to restore my device.
After flashing, I do not see vendor as a partition but looks like it is a folder. Is it OK for future ROMs ?
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Wow that can't be good. I'm new to the oneplus stuff, normally I would say boot into recovery and reflash to stock but since we do not have roms yet I have a feeling your going to have to take it back to tmobile or oneplus and exchange it.
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Restore with hard reset or Recovery mode OnePlus Nord N200 5GRestore with hard reset or Recovery mode your OnePlus Nord N200 5G can solve problems that have not been solved with a normal factory reset.
1- First turn off your OnePlus Nord N200 5G completely. If you can not unlock the screen, press and hold the power button for about 20 seconds and the phone will turn off.
2- Keep holding on volume down and power keys together for a few seconds in your OnePlus Nord N200 5G. In some devices according to the Android version the combination can be the power key and the volume key up.
3- When the OnePlus logo is displayed, release the buttons.
4- Move through the menu with the volume up and volume down keys until you reach the “Recovery Mode” option and press the power button to access.
If the device menu appears in Chinese characters, click here to see how to reset a mobile in Chinese
5- Use the volume up and volume down keys to select the “wipe cache partition” option and press the Power button to activate the option and clear the mobile cache.
6- After a few seconds you will return to the previous screen, with the volume buttons go to the option “wipe data / factory reset” and press the power button to enter. A screen with many NOes and a YES will appear, with the volume keys again go to the YES and press with the power key.
7- After finishing again with the volume keys, click on “reboot system now” and press the power key of your OnePlus Nord N200 5G, the device will reboot and take several minutes to start while restoring the device to its factory state and optimizing the applications pre-installed in the system Android 11, OxygenOS 11.
Click to expand...
Click to collapse
edale1 said:
He should still be able to recover it with a factory restore via the stock recovery. As far as I know (and I'm not an expert) a bad ROM flash doesn't touch the recovery partition.
from https://www.devicesfaq.com/en/reset/oneplus-nord-n200-5g
Click to expand...
Click to collapse
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
fogles2021 said:
I can't even get into recovery. I can get into download mode but theres no way for me to restore it from that...
literally recovery mode is gone also. it's so weird, i did this from my phone's settings, it shouldn't have done this.
Click to expand...
Click to collapse
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
edale1 said:
phone off -> volume down + power (hold both in until phone's booted)
that doesn't work to get into recovery mode?
How about
volume up + volume down + power
to get into fastboot mode?
Can you connect via USB to run ADB commands?
Click to expand...
Click to collapse
I can only boot into fastboot, recovery just boots back to "your device is corrupt'.
I can connect usb but i can't find drivers for the phone, its connect as QUSB.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
edale1 said:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
There's the USB drivers.
Selecting recovery from within fastboot mode brings up the corrupt message as well? Very odd.
I'm seeing 2 options then. Take the phone back to the store you got it at to see if they can fix/replace it; or wait for the ROM to be released.
Click to expand...
Click to collapse
I've installed these and it still comes up as qusb bulk.
Yeah, selecting recovery from fastboot goes to corrupt message, too.
Just going to make a aservice request.
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
daboross said:
There was another report of this on the OnePlus forums a while ago, too, if I'm inferring what happened correctly: https://forums.oneplus.com/threads/...-the-oneplus-nord-n200.1460001/#post-23393026
The only real recourse right now is to submit a ticket as you've done and wait until you can send your device back and they send you a new one.
Once OnePlus releases a full stock ROM image, if they ever do, it will be possible to recover a bootloader-unlocked device from this state. But even then that won't work if you weren't bootloader unlocked beforezs the update.
---
While you've still got the device, though, could you try something for me? Could you install the android platform tools, see if you can get fastboot working on your computer, and try the fastboot command "fastboot set-active a"?
The Nord N200 5G is a A/B partitioned device, which means it has two of each system partition, one labeled "a" and one labeled "b". The update process is *supposed to* install all updates into the partition that you aren't currently using, then instruct the system to switch to it so it can update seamlessly.
I have no idea what went wrong in your update process, but if it did an incomplete update then instructed the system to use the other partition (and now for some reason doesn't switch back) this could help. I kind of doubt it will, since in my attempts at flashing bootloaders, if I put anything fully invalid in boot partition 'b', the phone automatically switches back to 'a' and boots into "safe mode".
But if for some reason it isn't corrupted enough to trigger that, maybe switching back to the "a" partition set could fix it. Or if you're already on "a", you could try switching to "b".
Click to expand...
Click to collapse
Can u give me a link to platform tools, also..my computer is detecting the phone as QUSB BULK:"
From one of my other threads:
------
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
Click to expand...
Click to collapse
------
Basically, you need to manually update the drivers through device manager.
edale1 said:
From one of my other threads:
------
------
Basically, you need to manually update the drivers through device manager.
Click to expand...
Click to collapse
I can't get it to work...
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
From the first update drivers dialog (your phone should be in fastboot mode):
"browse my computer for drivers"
"let me pick from a list of available drivers on my computer"
"have disk"
And the drivers should be at
Code:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
Once you select the .inf, you'll want to select this from the resultant list:
"Android Bootloader Interface"
fogles2021 said:
I can't get it to work...
Click to expand...
Click to collapse
Your phone is in EDL mode, also known as hard brick. It seems like the phone thinks both of your system partitions are empty or corrupt, as well as the bootloader is perhaps corrupt, due to which it is now gone to EDL mode as a last resort.
Typically, the only way to come out of it is to flash in EDL mode using MSMDownload Tool. Unfortunately for you, I don't see that Oneplus has released the MSMDownload Tool for the N200.
There are 4 things you can do at this stage.
1. If the phone is in return period, get it exchanged for another one.
2. Assuming the phone is under warranty, get it repaired under warranty
3. Wait for Oneplus to release the MSMDownload Tool for the N200. From past experience, Oneplus has eventually released it for every one of their phones. Once it is released, it is literally a 5 minute fix to get your phone to factory refreshed stage.
4. As a long shot, we can try to see if the bootloader is not corrupt, and if that is working, try to check if either of the 2 system partition is still intact, as @edale1 is suggesting above. Try the following
a. Press Volume Down+Power when phone is power off stage, and see if you can get the phone in fastboot mode.
b. Go to the folder when you have downloaded the Android SDK Toolkit. Alternately, search for the folder containing "fastboot.exe" on your hard drive. Open a command prompt in that folder containing fastboot.exe.
c. Run "fastboot devices" in the command prompt.
d. If you get a response of "no devices", then that means either phone is not in fastboot mode ( Go to Step a and repeat a,b,c until it is in fastboot mode) or bootloader is corrupt (nothing can be done other than Steps 1, 2 or 3 I have outlined above)
e. If you get a response of "XYZ fastboot" where XYZ is a random string/number, then bootloader is not corrupt. Proceed to Step f.
f. Type "fastboot getvar all" in the command prompt.
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device, either 'a' or 'b'
g. Follow @edale1's instruction above to change active partition to the *opposite* of whatever currently active partition e.g. if it says 'a' as the active partition in Step f above, then type in "fastboot --set-active=b" in command prompt, and vice-versa i.e. if it says 'b' as the active partition in Step f above, then type in "fastboot --set-active=a" in command prompt
h. If you get success in Step g, type "fastboot reboot" in command prompt, and keep your fingers crossed that it boots up normally. If not, that means both system partitions are corrupt. Follow Steps 1, 2 or 3 above.
Good luck!
fogles2021 said:
Well, ok..I have a huge problem.
I was in developer mode and it said i could switch my rom so i installed it and now my phone says "Your device is corrupt. It is not trusted and will not boot".
Any suggestions on how I can fix this?
Click to expand...
Click to collapse
No stock rom on oneplus/tmobile website
Im having a device corrupt error and cannot access phone anymore. Im trying to find the stock rom to flash with MSM tool but cantyfind it anywhere. You'd think oneplus would have it up on their website already. Anyone?
forum.xda-developers.com
Had the same problem, had to do a warranty replacement
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Ethanvio said:
I followed your mini guide but it says "Slotchange is not allowed in lock state"
Anyways to unlock it using fastboot ?
Click to expand...
Click to collapse
If you didn't enable OEM unlocking in developer options before you bricked your phone, you can't unlock those fastboot commands.