Hard bricked yureka!! Windows not detecting the phone... - YU Yureka Q&A, Help & Troubleshooting

to all the developers and well wishers out there. i'm actually excited to let you all know that i've just hard bricked my phone. custom roms like cm12, euphoria, resurrection remix were working fine when i actually wanted to flash MIUI v6 to my yureka.
the flash went good but the MIUI wouldn't stop restarting in every 30 seconds after being flash.. tried reverting to euphoria rom. and my phone wouldn't allow any other roms to be flashed unless its a MIUI v6 again.. -_-
i was actually tired of it so went through a procedure to factory restore the stock cm rom and went through the processes of this ****ty link...
http://www.thetechnotriad.com/393/ho...ick-yu-yureka/
and now my phone wont even fastboot. windows wouldn't detect it by any means. and i'm totally screwed.
i've been recently looking around this http://forum.xda-developers.com/yure...ode-k-t3068040 thread from xda itself by tirta.agung for a long time. no luck because he mentioned that the procedure would only work provided that windows could minimum detect my yureka as QHUSB_BULK in device manager.
HELP ME OUT PEEPS... is there any way of giving my YU life back?
ADVICES AND THOUGHTS ARE HIGHLY APPRECIATED...
P.S the YU support told me to download their official rom zip from a link and copy it to internal storage and flash and bla bla bla -_- do they even care to understand my problem properly whilst i've clearly mentioned that MY PHONE WOULDN'T FASTBOOT!!! -_-

same problem here bro
Pragun.Joshi said:
to all the developers and well wishers out there. i'm actually excited to let you all know that i've just hard bricked my phone. custom roms like cm12, euphoria, resurrection remix were working fine when i actually wanted to flash MIUI v6 to my yureka.
the flash went good but the MIUI wouldn't stop restarting in every 30 seconds after being flash.. tried reverting to euphoria rom. and my phone wouldn't allow any other roms to be flashed unless its a MIUI v6 again.. -_-
i was actually tired of it so went through a procedure to factory restore the stock cm rom and went through the processes of this ****ty link...
http://www.thetechnotriad.com/393/ho...ick-yu-yureka/
and now my phone wont even fastboot. windows wouldn't detect it by any means. and i'm totally screwed.
i've been recently looking around this http://forum.xda-developers.com/yure...ode-k-t3068040 thread from xda itself by tirta.agung for a long time. no luck because he mentioned that the procedure would only work provided that windows could minimum detect my yureka as QHUSB_BULK in device manager.
HELP ME OUT PEEPS... is there any way of giving my YU life back?
ADVICES AND THOUGHTS ARE HIGHLY APPRECIATED...
P.S the YU support told me to download their official rom zip from a link and copy it to internal storage and flash and bla bla bla -_- do they even care to understand my problem properly whilst i've clearly mentioned that MY PHONE WOULDN'T FASTBOOT!!! -_-
Click to expand...
Click to collapse
same my phone also bricked what did you do next

Pragun.Joshi said:
to all the developers and well wishers out there. i'm actually excited to let you all know that i've just hard bricked my phone. custom roms like cm12, euphoria, resurrection remix were working fine when i actually wanted to flash MIUI v6 to my yureka.
the flash went good but the MIUI wouldn't stop restarting in every 30 seconds after being flash.. tried reverting to euphoria rom. and my phone wouldn't allow any other roms to be flashed unless its a MIUI v6 again.. -_-
i was actually tired of it so went through a procedure to factory restore the stock cm rom and went through the processes of this ****ty link...
http://www.thetechnotriad.com/393/ho...ick-yu-yureka/
and now my phone wont even fastboot. windows wouldn't detect it by any means. and i'm totally screwed.
i've been recently looking around this http://forum.xda-developers.com/yure...ode-k-t3068040 thread from xda itself by tirta.agung for a long time. no luck because he mentioned that the procedure would only work provided that windows could minimum detect my yureka as QHUSB_BULK in device manager.
HELP ME OUT PEEPS... is there any way of giving my YU life back?
ADVICES AND THOUGHTS ARE HIGHLY APPRECIATED...
P.S the YU support told me to download their official rom zip from a link and copy it to internal storage and flash and bla bla bla -_- do they even care to understand my problem properly whilst i've clearly mentioned that MY PHONE WOULDN'T FASTBOOT!!! -_-
Click to expand...
Click to collapse
did u finded a solution ?

Related

[Q] Probs installing Cyanogenmod 7.1 on x8(E15i)

Hey.
I'm having difficulties with new cyanogenmod 7.1
I Followed different tutorials and none of them helped me.
I started with stock 2.1 rom and did all the unlocking bootlader stuff , then installed custom kernel and managed to install cyanogenmod 7.1 but then occurred a funny thing . There was only FreeXperia logo showing up, nothing else, and it rebooted all the time. Then I flashed stock rom again and tried to understand what's wrong and tried to use different kernels and nothing.
So my question is. Is there anything I'm missing here?
Henri.
Full wipe after you install rom.
Dot forget to make backups first.
about that...
i always do full wipe after installing roms, so it has to be something else.
Thnks anyway..
But after browsing several topics in XDA forum I saw that I'm not only one with the problem.
If anybody has had the problems like I do and got the solutions, every kind of tips are welcome.
Thread closed
I got it all working, but I don't know what was the reason, because, I just did the whole thing again about three or four times, and then it just booted and worked.
I never could install Cyanogenmod in my phone... could you?
Hey!!!
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Does wifi and/or 3G work for you longer then 15 minutes?
No, but at the moment I'm using RC1 flawlessly.
Sent from my E15i using XDA App
coffee-break said:
I could write a total working tutorial how I managed to get to work everything, but it takes time, so if you want tutorial send me private message , so I create it for you.
Henri
Click to expand...
Click to collapse
umm..why not post it publicly man ? It will be useful for everyone including myself.
Would also like that tutorial
ok,
i'm gonna post it here after finishing it.
So, the wanted tutorial is here!
Firstly it's for xperia x8(E15i) to be superclear.
I'm gonna put that tutorial into steps.
STEP 1
You need to have stock 2.1 rom with baseband XXX015 , if you don't have it, then go to Sony Ericsson's webpage and download the upload service and flash it back into your phone.
STEP 2
You phone has to be rooted. Easieset way is using Superoneclick(sorry, i'm not gonna provide the link, because it's just google-ing thing to you who need rooting program)
STEP 3
Now, everything comes to the unlocking process for bootloader. there is also tutorial how to succeed when using s1tool and msm7227 (if you have problem, then I don't know). Try to undestand the tutorial of doing it.
S1tool is for identifying if your phone is unlocked or not.
and msm7227 is for unlocking
tut is here - LINK
I wish luck, don't brick your phone, but it's not so hard to understand tutorials if you have right phone and right tutorial.
STEP 4
I totally suggest to install stable rom. The reason is that released 7.1 has bugs and incompatibility with some phones and i haven't got wifi and 3g working , but tried different roms and kernels.
I provide links i got from deani77, big thanks to him.
You can try this link for FXP028 ROM - http://www.multiupload.com/IIWIPG1ALH
For FXP030 kernel try this link - http://hotfile.com/dl/132650338/7b17...USTOM.ftf.html
(that release is RC1 of Cyanogenmod 7.1 but I think it's the best at the moment!)
and you download all the files as usual. Rom zip package should be in the SD card's root folder, so you can easily install it after flashing kernel
STEP 5
installing is quite simple actually. You need to use flashtool that is provided with rom(link in step 3)
firstly you flash kernel. Kernel file is the one you downloaded .ftf file. You have to put that file(X8_custom.ftf) into firmware folder which is inside of flashtool folder.
Then you open flash tool and you click FLASH, then appears little window and you click ok and then you need to plug in your phone into usb while holding down back button. Your phone has to be off when you are doing that. Then flashtool identifies your phone and will flash the kernel into your phone. when everything comes smooth then you now have fxp custom kernel. it has clockworkmod recovery and you need to click several times back button when FreeXperia logo appears.
STEP 6
You have to do factory reset and format, also i suggest from advanced menu using format system.
Then you select from the recovery menu install custom zip... and you browse your rom .zip file and if everything is OK then it should display "installing update or smth" if it's done then good for you, you reboot and it should work.
IF YOU WANT GOOGLE APPS , then google the link and install it same way you did with the rom. You can do it any time.
..
So if anything is not understandable then ask. I'm not an expert or anything, I just did things like I described.
Best,
Henri.
i have still had problems with bootloop and passing md5 checksum any idea on how to fix this?
mm.. at the moment I don't know but what that md5 checksum means?
I fixed my bootloop issue when I flashed back to stock rom, then I just did all the steps I describe again (not unlocking bootloader because it was unlocked already) .. but I don't know what's really does the bootlooping thing. I just got lucky. It took me like billion hours until I got it working...

JUST SOFT BRICKED & RECOVERED ...huff...

I just soft bricked my device today. I know it sounds silly because i just take extra measure to flash my roms.
Ok this what happened i was on Jelly Bean for 2 days testing it. I was cycling through roms for couple of days and decided i will go flash stock TW from Mobile Odin. I forget that CM10 does not allow any other kernel except CM9. Also thought the Odin will flash on anything and flashed LRG stock :victory: after MD5 check success and my screen went black and nothing happened. Then i realized that something went wrong. Waited for 5 mins but nothing, i thought that i bricked my phone So pulled out battery & inserted back & tried to put in Recovery & success :highfive: But problem was here, it some how was in CWM 5.8 (JB is 6.0) but i could not do anything (flashing rom or kernel). So i realized that it was soft brick. Big relief put the phone in download mode flashed GB stock. To make it worst everything went well but stuck in boot loop. Nothing worked pulled out battery. Just made myself comedown & thought the hole process then went back to recovery wiped data & cache you know what it worked . Now fully rooted and ready to flash another rom
I think its all those curses i got telling bricked people how stupid they are and realized that there are many ways to get bricked. I am glad it was not a hard brick. So think twice before what you are doing. I learned it, may be other too..
I have also had a soft brick a couple of times flashing roms on my note but since I started using cyanogenmod roms I decided that in comparison touchwiz SUCKS and I will NEVER go back to a touchwiz based rom. Cyanogenmod kernels have pretty much been proven to be safe from the brick bug and I only encountered soft bricks using samsung kernels.I am by no means an expert, just an informed reader(although I do get lazy at times and post redundant questions ).
so wait ,you're saying that Mobile ODIN can't work properly while on CM10?!! that's very weird since Mobile ODIN launches it's own recovery and temp kernel to flash from.
maybe it's just a coincidence that Mobile ODIN failed to flash? maybe the flash kernel wasn't loaded properly while on CM10 ,and maybe you were using an older version??
anyway ,yes I've had my share of soft bricks and boot loops (some even on purpose for testing ) ,hell I even almost superbricked it once when the official ICS first came out.
samsung phones are very hard to brick ,just look out not to mess with the bootloaders ,and on our phones (note ,S2 ...etc) careful not to trigger the EMMC bug .
other than that ,any brick is manageable .
MR.change said:
so wait ,you're saying that Mobile ODIN can't work properly while on CM10?!! that's very weird since Mobile ODIN launches it's own recovery and temp kernel to flash from.
maybe it's just a coincidence that Mobile ODIN failed to flash? maybe the flash kernel wasn't loaded properly while on CM10 ,and maybe you were using an older version??
anyway ,yes I've had my share of soft bricks and boot loops (some even on purpose for testing ) ,hell I even almost superbricked it once when the official ICS first came out.
samsung phones are very hard to brick ,just look out not to mess with the bootloaders ,and on our phones (note ,S2 ...etc) careful not to trigger the EMMC bug .
other than that ,any brick is manageable .
Click to expand...
Click to collapse
Even i don't know how it happened usually Mobile Odin is safe. It was backing up kernel. I think it was CM10, still in preview stage needs lot of experiment. Flashing from CM10 to another rom does not work. I have tested it, only you can flash CM9.
Galaxtus said:
I just soft bricked my device today. I know it sounds silly because i just take extra measure to flash my roms.
Ok this what happened i was on Jelly Bean for 2 days testing it. I was cycling through roms for couple of days and decided i will go flash stock TW from Mobile Odin. I forget that CM10 does not allow any other kernel except CM9. Also thought the Odin will flash on anything and flashed LRG stock :victory: after MD5 check success and my screen went black and nothing happened. Then i realized that something went wrong. Waited for 5 mins but nothing, i thought that i bricked my phone So pulled out battery & inserted back & tried to put in Recovery & success :highfive: But problem was here, it some how was in CWM 5.8 (JB is 6.0) but i could not do anything (flashing rom or kernel). So i realized that it was soft brick. Big relief put the phone in download mode flashed GB stock. To make it worst everything went well but stuck in boot loop. Nothing worked pulled out battery. Just made myself comedown & thought the hole process then went back to recovery wiped data & cache you know what it worked . Now fully rooted and ready to flash another rom
I think its all those curses i got telling bricked people how stupid they are and realized that there are many ways to get bricked. I am glad it was not a hard brick. So think twice before what you are doing. I learned it, may be other too..
Click to expand...
Click to collapse
Nothing in this post would have hard bricked your device. You didn't issue the "format(/system)" command on an unsafe kernel, You used mobile odin to flash back to a different kernel, why I do not know, mobile odin is horrid. ALWAYS USE PC ODIN.
Not sure how this is scary, or even remotely dangerous. Simple fix. No need to come on here and tell everyone about it.
I don't post every time I have a boot loop, or soft brick my nexus or gNote. You read how to recover it. Recover it and move on.
antiochasylum said:
Nothing in this post would have hard bricked your device. You didn't issue the "format(/system)" command on an unsafe kernel, You used mobile odin to flash back to a different kernel, why I do not know, mobile odin is horrid. ALWAYS USE PC ODIN.
Not sure how this is scary, or even remotely dangerous. Simple fix. No need to come on here and tell everyone about it.
I don't post every time I have a boot loop, or soft brick my nexus or gNote. You read how to recover it. Recover it and move on.
Click to expand...
Click to collapse
LOL .....hahahahaha.....

[HELP] ZTE Blade Q Maxi stock rom

Hi guys, after a year and a half of running custom roms, I am sick of it. My main problem is that I do not receive SMS messages when they should arrive. I receive them hours after they have been sent. Another problem is that sometimes, I can't be called. My phone doesn't display a call, or being called at all. But somebody is calling me and my phone doesn't say anything. So this is very frustrating because you can miss important calls without you even knowing. And this has been happening to me almost on every rom tried. They all work well for some time, but after they start to screw around and not be consistent.
My question is, how can I install the stock rom from Orange Reyo Romanian (ZTE BLADE Q MAXI) so that my issues will go away? I have cwm, but it seems that the firmware at the zte site is only installable with the stock recovery, not with a custom recovery like CWM or TWRP.
So yeah, any help would be much appreciated.
just copy the update .zip from zte syte on your sdcard and then install with twrprecovery!
i test it and it work
or you can download a stok backup for spflashtool posted by me on xda for restoring the phone stok rom
search it 2-3 pages back
it has a recovery stok too included
http:// http://forum.xda-developers.com/zte-blade/general/orange-reyo-stok-rom-backup-t3154351
Thank you! But what drivers do I need to install? SP flash tool does nothing when I connect the phone to te pc
Can I install it with CWM? As i have not installed TWRP on my phone
deepside_dj said:
Thank you! But what drivers do I need to install? SP flash tool does nothing when I connect the phone to te pc
Click to expand...
Click to collapse
did you conect the phone OFF?
and the spflash tool doesnt start ?
Sent from my ZTE Blade Q Maxi using Tapatalk
The phone is off. The sp flash tool starts. But after I click download, and connect the phone to the pc, nothing happens. The SP flash tool says nothing.
deepside_dj said:
The phone is off. The sp flash tool starts. But after I click download, and connect the phone to the pc, nothing happens. The SP flash tool says nothing.
Click to expand...
Click to collapse
yea! loks like a drivers problem.
make a serch on google after "Zte handset usb driver" and install it.
the pc see your phone if turned it ON?
what windows do you have?
Sent from my ZTE Blade Q Maxi using Tapatalk
I have installed the drivers. But still doesn't work. Even when the phone is on, SP flash tool doesnt see it. I have windows 8.1. I run your zingerone rom. Maybe it is the problem that even when my phone is on, when I connect the phone, the pc doesnt see it? The pc doesnt see it at all, when i have the zingerone rom installed. SHould I install other rom and then try SP flash tool?
The backup cannot be installed with CWM?
Now, after installing drivers, i get another error. After i click download and connect my phone to pc, SP flash tool sees my phone, but de download bar is red, and after 3 seconds my phone disconects and i receive the error: PMT has changed; it must be downloaded. I have no idea what this means.
EDIT: IT WORKS! I managed to make SP flash tool see my device by flashing it. But, by flashing it, it bricked my phone. So I thought I'm screwed. But I installed the stock recovery from @vaserbanix and at least got the phone to boot, but it was stuck in bootloop. So i downloaded the update.zip from ZTE site and put it on my sd card, got into the stock recovery and managed to install the update.zip. And now my phone has the stock rom and is working flawlessly.
Thank you @vaserbanix my friend for your help. Also, how is your health? Are you feeling well, my friend?
Hi @deepside_dj,
Glad to know that you solved out your problem. I want to ask you, if you don't mind, do you have that problems regarding SMS messages and phone calls before you start installing customs ROM's? I have to ask you this because I received a Orange Reyo(Blade Q Maxi) branded by Orange, with exactly the same issue. In the company were I work, the phone was used internally, for GSM testing especially. And I understand from the test user that was using the phone, that, even if the phone was having the stock ROM on it, was having exactly the same issues sometimes.
For examples, some text messages were received just only when the phone receive a call, even if the message have been send with a few hours before, or something like this.
So, in this case, I'm wondering if actually the custom ROM's are the root cause.
Right now, I'm using the phone for test software development and also as a spare phone. And because of this, even if @vaserbanix have done a great job porting other ROM's for this phone, I already start working on a custom ROM for me to use that is going to be based on the stock one, but much more smaller and without that bloatware preinstalled on it. So I have to know at what to look after. Maybe is not the custom ROM's fault, but just an update or a wrong placed internal command that is interfering with the RIL normal execution with the radio hardware.
Best Regards,
DarKay
DarKay said:
Hi @deepside_dj,
Glad to know that you solved out your problem. I want to ask you, if you don't mind, do you have that problems regarding SMS messages and phone calls before you start installing customs ROM's? I have to ask you this because I received a Orange Reyo(Blade Q Maxi) branded by Orange, with exactly the same issue. In the company were I work, the phone was used internally, for GSM testing especially. And I understand from the test user that was using the phone, that, even if the phone was having the stock ROM on it, was having exactly the same issues sometimes.
For examples, some text messages were received just only when the phone receive a call, even if the message have been send with a few hours before, or something like this.
So, in this case, I'm wondering if actually the custom ROM's are the root cause.
Right now, I'm using the phone for test software development and also as a spare phone. And because of this, even if @vaserbanix have done a great job porting other ROM's for this phone, I already start working on a custom ROM for me to use that is going to be based on the stock one, but much more smaller and without that bloatware preinstalled on it. So I have to know at what to look after. Maybe is not the custom ROM's fault, but just an update or a wrong placed internal command that is interfering with the RIL normal execution with the radio hardware.
Best Regards,
DarKay
Click to expand...
Click to collapse
When I first got the phone, obviously, it had the stock rom. I used the stock rom for months on end, up until @vaserbanix ported the first rom for this device. While using a fresh stock rom, fresh as in directly from the factory, I didn't have any issues with calls/SMS. All came when they were supposed to. Even after using custom roms, for some time, i haven't encountered deal-breaking issues. Clearly not something as big as missing calls, that don't appear when they should etc. Well, all went good until all of a sudden I didn't receive calls. I was using the MIUI v5 rom, which is my favorite rom. I thought it might be a bug, so I flashed the rom again, but nope, the problem still persisted. Which was odd, since I was using that specific rom for months. After that, I tried many other roms ported by the one and only @vaserbanix until i settled on the Zingerone rom. This was the fastest and most clean looking rom for me, and I was happy that it ran good. Until, the issue with calls/sms not being received reappered. Which really frustrated me, because I lost an important call, without me even knowing it. That is when I had enough, so I installed the stock rom again, with a bit of work, but in the end the install was good.
So now I am using the stock rom, it has been only a day since I installed it, but it seems solid. Only time will tell. If I encounter the same issues, be sure I will report it here!
OK, thanks for the information. I wanted today to take the SIM card from the test operator to make some tests on the phone, to see if I can find something wrong with the card or the phone or at least, reproduce the issues, and found out that the SIM card was replaced. It looks like on another phone was still having the same issues. So in this case, it seems that the problem was with the SIM. I will make some logs on the phone to see if the problems resides also on it, especially now, because I modified and installed one of the custom ROM's build by @vaserbanix. Only the time will tell.
In the mean time, I have a new "toy" (Blade Q Maxi ) so I have to play with it a little bit, but I will let you know if the problems returns, or at list found the root cause of this, because I think you are going to get bored real soon of the stock ROM. See you soon.
I find Stock rom for ZTE Blade Q Maxi on this Site
kinotube.info/channel/watch/lOg52L-wBsQ
----
mega.nz/#!w8x3iADC!OsNuOELkG5SE9z5cu-gvyaIQxqFCssMmc4_GxR1W-BI
pass __ gem-flash
----
There is stock rom for ZTE Blade Q Maxi with which can move apps from phone to SD card.
But it's a full of Viruses, adware, malware and hijacking trojans.
If someone know how to remove viruses and others stufs. Or find what was change in android to be able move to SD Card, and put that change in regular clear stock rom?

Micromax Canvas Knight A350 Phone totally dead...

Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Frank Morris said:
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Click to expand...
Click to collapse
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
harvir46 said:
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
Click to expand...
Click to collapse
I tried it but did not worked. when i open device and printer, i can see DA USB VCOM PORT when battery is in and MTK USB PORT when battery is removed, i guess i should see preloader but that is not happening. when i connect karbonn without battery then i see preloader there and flashing get completed successfully.
Please help my phone is not charging, power buttons also not working, Tried to hard reset by pressing power button, volume up and down simultaneously but still phone does not respond.
I request members to help. i am trying from last 15 days.
raghubar said:
I tried it but did not worked. when i open device and printer, i can see DA USB VCOM PORT when battery is in and MTK USB PORT when battery is removed, i guess i should see preloader but that is not happening. when i connect karbonn without battery then i see preloader there and flashing get completed successfully.
Please help my phone is not charging, power buttons also not working, Tried to hard reset by pressing power button, volume up and down simultaneously but still phone does not respond.
I request members to help. i am trying from last 15 days.
Click to expand...
Click to collapse
Sorry but this thread limits to A350 only.
---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------
Frank Morris said:
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Click to expand...
Click to collapse
Using SP Flash Tool, flash the preloader.bin first.Use meta mode if not detected,all three buttons together while connecting and keep pressed until flashing starts.
If flashing was successful then your phone should at least be able to vibrate when you press the power button or boot if the correct files are present on your phone; else, flash other necessary files to make the phone boot up and start working normally again.
P.s. writing again and again is painful as I'm lazy-ass.
I'm thinking of making a thread about this but again,I'm lazy-ass.
it worked...wow...thanks ...but now it gets into a boot loop
harvir46 said:
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
Click to expand...
Click to collapse
Thanks buddy, the phone started but now it ends into a bootloop. Tried getting into custom recovery and doing a factory reset. It starts and goes all the way through and finally restarts and the same thing again...bootloop....Please suggest what should I do...Thanks and God bless.
In the meanwhile i tried flashing a new custom ROM from xdafirmware.com. But the SP flash tools downloads upto 9.86MB and then the download stops...What could be the reason? Also please let me know if Miracle Box is any kind of solution for these kind of problems! Thanks and God bless.
Mr.Ak said:
Sorry but this thread limits to A350 only.
---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------
Using SP Flash Tool, flash the preloader.bin first.Use meta mode if not detected,all three buttons together while connecting and keep pressed until flashing starts.
If flashing was successful then your phone should at least be able to vibrate when you press the power button or boot if the correct files are present on your phone; else, flash other necessary files to make the phone boot up and start working normally again.
P.s. writing again and again is painful as I'm lazy-ass.
I'm thinking of making a thread about this but again,I'm lazy-ass.
Click to expand...
Click to collapse
I am also talking about Micromax A350 and i am facing same problem
as written by thread creator.Please help me, all things mentioned in this thread i tried but none worked.
Please tell whether i should do all these step with battery or without battery.
Frank Morris said:
Thanks buddy, the phone started but now it ends into a bootloop. Tried getting into custom recovery and doing a factory reset. It starts and goes all the way through and finally restarts and the same thing again...bootloop....Please suggest what should I do...Thanks and God bless.
In the meanwhile i tried flashing a new custom ROM from xdafirmware.com. But the SP flash tools downloads upto 9.86MB and then the download stops...What could be the reason? Also please let me know if Miracle Box is any kind of solution for these kind of problems! Thanks and God bless.
Click to expand...
Click to collapse
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
www.canvasknightroms.blogspot.in
Good luck!
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
raghubar said:
I am also talking about Micromax A350 and i am facing same problem
as written by thread creator.Please help me, all things mentioned in this thread i tried but none worked.
Please tell whether i should do all these step with battery or without battery.
Click to expand...
Click to collapse
Do you even know A350's battery is non-removable?
The only way you can remove it is by disassembling the device but doing that will compromise with your battery life.It should only be used in worst case scenario and everything else fails to work!
Mr.Ak said:
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
Good luck!
First of all, I apologize for my mistake. It was not a custom ROM but a Canvas Knight Stock ROM... The file name is this...Micromax_A350_V2_040614_KitKat_(by_xdafirmware.com). It's a version 2 (unmerged storage). However, earlier I had flashed a version 3 (merged storage) ROM and since it was constantly giving me trouble I tried to reflash version 2 ROM...But unable to do so...it gets stuck at 9.6MB or 0% in the SP Flash tool.
I tried the format+download option too. But in vain. Guess I am doing something wrong! What could it be? Thanks and God bless.
Btw, I have been through your blog in the past and benefited from the same. Thanks
Click to expand...
Click to collapse
Frank Morris said:
Mr.Ak said:
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
Good luck!
First of all, I apologize for my mistake. It was not a custom ROM but a Canvas Knight Stock ROM... The file name is this...Micromax_A350_V2_040614_KitKat_(by_xdafirmware.com). It's a version 2 (unmerged storage). However, earlier I had flashed a version 3 (merged storage) ROM and since it was constantly giving me trouble I tried to reflash version 2 ROM...But unable to do so...it gets stuck at 9.6MB or 0% in the SP Flash tool.
I tried the format+download option too. But in vain. Guess I am doing something wrong! What could it be? Thanks and God bless.
Btw, I have been through your blog in the past and benefited from the same. Thanks
Click to expand...
Click to collapse
What was the problem with v3?
Click to expand...
Click to collapse
Version 3 problem...
Mr.Ak said:
What was the problem with v3?
Click to expand...
Click to collapse
Version 3 booted well the first time...it went all the way...i was setting it up nicely...and it hung and just stopped. Ever since then I tried to reboot it would not load...the Canvas Knight logo with the sound would come on and then restart or get hung at that point. In short, it would not fully boot anymore except for that once!
So I decided to do away with version 3 and thought version 2 would be fine because that's what was originally on my phone...but now this is the problem...i mean the SPFT gets hung at 0%.
Thanks and God bless you.
On a different note, I would still love to have version 3 if possible since I plan to install a custom ROM...most likely Cyanogenmod....
Latest update...
Latest Update…
I finally managed to successfully flash a Kitakat 4.4.2 vs. 2 (unmerged storage) stock rom…I downloaded the file again from xdafirmware.com and flashed it. There was no problem. The phone has started and its up since the last one hour or so.
Before booting I entered into stock recovery and did a wipe data/factory reset and also wipe cache partition. So far no problem. I have not yet switched on my wifi coz I am worried it might go off again and enter a bootloop.
Battery was 95% when booted...its now 94% since one hour...I have not used the phone at all though...
Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock rom. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the bootloader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the bootloader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3
Sorry for the trouble. But I have messed up many times in the last one month with innumerable flashing of the ROM’s and zip files. Now, once bitten twice shy I want to play safe.
So please let me know your thoughts if they are fail proof and time tested. Thanks for all your help. God bless.
Frank Morris said:
Latest Update…
I finally managed to successfully flash a Kitakat 4.4.2 vs. 2 (unmerged storage) stock rom…I downloaded the file again from xdafirmware.com and flashed it. There was no problem. The phone has started and its up since the last one hour or so.
Before booting I entered into stock recovery and did a wipe data/factory reset and also wipe cache partition. So far no problem. I have not yet switched on my wifi coz I am worried it might go off again and enter a bootloop.
Battery was 95% when booted...its now 94% since one hour...I have not used the phone at all though...
Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock rom. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the bootloader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the bootloader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3
Sorry for the trouble. But I have messed up many times in the last one month with innumerable flashing of the ROM’s and zip files. Now, once bitten twice shy I want to play safe.
So please let me know your thoughts if they are fail proof and time tested. Thanks for all your help. God bless.
Click to expand...
Click to collapse
Well I hate giving bad news to people but I might know what causing all this.
As you say,the phone booted fine now but you'll likely see random hangs and sudden reboots in using it,to be sure,use it for atleast 2 hrs constantly and then we can proceed further with your questions.
In mean time,check this post:
https://forum.xda-developers.com/showpost.php?p=69482562&postcount=697
Mr.Ak said:
Well I hate giving bad news to people but I might know what causing all this.
As you say,the phone booted fine now but you'll likely see random hangs and sudden reboots in using it,to be sure,use it for atleast 2 hrs constantly and then we can proceed further with your questions.
In mean time,check this post:
https://forum.xda-developers.com/showpost.php?p=69482562&postcount=697
Click to expand...
Click to collapse
Well I tried using it for a while...no internet...just going through settings and checking...then I enabled Developers options and connected USB. Tried to check if the phone was listed on ADB etc....but then it went into a bootloop and kept shutting down after periodic bootloops...now its totally down...not responding at all.
Anyway, I think I know how to get it back when everything else fail. Until then stay blessed and don't give up.
God bless.
Frank Morris said:
Well I tried using it for a while...no internet...just going through settings and checking...then I enabled Developers options and connected USB. Tried to check if the phone was listed on ADB etc....but then it went into a bootloop and kept shutting down after periodic bootloops...now its totally down...not responding at all.
Anyway, I think I know how to get it back when everything else fail. Until then stay blessed and don't give up.
God bless.
Click to expand...
Click to collapse
How?
The Phone has been up and about for the last 6 hours now...
Mr.Ak said:
How?
Click to expand...
Click to collapse
Hi, Sorry for the sudden disappearance. I really didn't know how to reply to your "HOW"? But I knew there was a CERTAIN possibility of getting the phone back...I call it faith in God. And I have plenty of faith and I believe in the impossible coz I have seen some of the most impossible things happen in my life and around me over the years. So plain hope and faith in God was what I banked on. But I have no logical explanation to give on the phone starting again smoothly. I have been struggling with this phone for the last 45 days. And this is the first time the phone has really stayed put and it got booted in just one go!
Also your signature line was a source of continued inspiration to hit out against all the odds and doubts.
I would now kindly appreciate any help in restoring the phone to full functionality...I mean would love to hear answers for my questions from the previous post.
In the meanwhile, I did a bit of study on the Miracle Box and a tool called ALL-IN-ONE-TOOL_V2.1...
But, I don't want to jump the gun and get going...Will wait for expert advice. Until then God bless us all. Stay blessed. And yes, thanks for all the help. Shalom.
Frank Morris said:
Hi, Sorry for the sudden disappearance. I really didn't know how to reply to your "HOW"? But I knew there was a CERTAIN possibility of getting the phone back...I call it faith in God. And I have plenty of faith and I believe in the impossible coz I have seen some of the most impossible things happen in my life and around me over the years. So plain hope and faith in God was what I banked on. But I have no logical explanation to give on the phone starting again smoothly. I have been struggling with this phone for the last 45 days. And this is the first time the phone has really stayed put and it got booted in just one go!
Also your signature line was a source of continued inspiration to hit out against all the odds and doubts.
I would now kindly appreciate any help in restoring the phone to full functionality...I mean would love to hear answers for my questions from the previous post.
In the meanwhile, I did a bit of study on the Miracle Box and a tool called ALL-IN-ONE-TOOL_V2.1...
But, I don't want to jump the gun and get going...Will wait for expert advice. Until then God bless us all. Stay blessed. And yes, thanks for all the help. Shalom.
Click to expand...
Click to collapse
You don't need all those tool box.
Sp flash tools is enough to give life to your device.
Help required to set up the device fully...now that it is working!
Mr.Ak said:
You don't need all those tool box.
Sp flash tools is enough to give life to your device.
Click to expand...
Click to collapse
Hi Ak,
Thanks for your reply. My device is up and about since the last hmmm...to be exact...26 hours. I didn't have any reboots or bootloops or anything for that matter.
However, I need to set it up complete...customization I mean...and these are some of the problems I am facing... Quoting a part of the previous post to save typing...
Quote "Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock ROM. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the boot-loader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the boot-loader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3" Unquote.
In the meanwhile, I have done a little bit of study and RnD of the miracle box/MTK Droid Tools/S&N Writer tool etc. on my old Canvas HD 116. And I realized that the Miracle Box is one good tool. The IMEI No. can be changed in a jiffy. Rooting is extremely easy using this box. I did via adb.
In short, a bit too confused with too much knowledge on hand. Looking for wisdom to apply this knowledge correctly. There could be many simpler ways too!!! Any help in this regard is much appreciated.
Thanks and God bless us all. Shalom.
Frank Morris said:
Hi Ak,
Thanks for your reply. My device is up and about since the last hmmm...to be exact...26 hours. I didn't have any reboots or bootloops or anything for that matter.
However, I need to set it up complete...customization I mean...and these are some of the problems I am facing... Quoting a part of the previous post to save typing...
Quote "Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock ROM. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the boot-loader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the boot-loader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3" Unquote.
In the meanwhile, I have done a little bit of study and RnD of the miracle box/MTK Droid Tools/S&N Writer tool etc. on my old Canvas HD 116. And I realized that the Miracle Box is one good tool. The IMEI No. can be changed in a jiffy. Rooting is extremely easy using this box. I did via adb.
In short, a bit too confused with too much knowledge on hand. Looking for wisdom to apply this knowledge correctly. There could be many simpler ways too!!! Any help in this regard is much appreciated.
Thanks and God bless us all. Shalom.
Click to expand...
Click to collapse
Okay don't panic!
Clearly your device is fine by hardware stuff so let's fix some myths and problem of yours.
Firstly,this is mt6592 so you don't have to unlock any boot loader stuff.You can just root your device using kingroot or kingoroot(google it).
For more please read out this whole section,
https://canvasknightroms.blogspot.com/2015/10/rooting-canvas-knight.html?m=1
Now I believe you have root by now. Now all you need to do is get a recovery and as you're on v2 you can find it here,
https://drive.google.com/file/d/0B5W6R0DsDjWTU1o3TEpfWGFsMEE/view
This is philz recovery with OTG support.As you've root just download the IMG file and flash it though flashify,you can find it on Play store.So you've recovery!
Again,these are just suggested methods,you can do all that with other methods too.Also please stop wasting time on stuffs like miracle boxes and etc etc.
Secondly to get your imei back it would be very easy as you've recovery.
https://drive.google.com/file/d/0B6-QF5uchBNhbFlfVk1wOEthbms/view
Just flash this file in recovery and everything shld be fine.
Now to fix Nvram error,just extract the folder from this backup zip,
https://drive.google.com/file/d/0ByuIKfMkBBxBaXBZRHJnNHVRMVk/view
And using any root explorer(I prefer es file manager) go to /data root and replace nvram folder with the folder in this zip
Now the best recovery would be philz recovery for v2 but I greatly suggest you to flash v3 for a variety of reasons and custom ROMs.Yes,you need to shift to v3 to get LP or MM and new updated ROMs though you can still flash available ROMs for v2 which you can find here,
https://canvasknightroms.blogspot.in/2015/10/all-roms-link-for-v2.html?m=1
Very less isn't it? That's because storage barrier in v2.
You can find various mods here,
https://canvasknightroms.blogspot.in/2015/10/mods.html?m=1
You can find correct stock ROMs here,
https://canvasknightroms.blogspot.in/2015/10/stock-rom.html?m=1
Flashing the sim fix above will eventually fix SN too.
And yes many custom ROMs are bundled with SuperSU so you should use that.
To convert from kingroot user to super su use this guide,
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
And lastly mtkdroidtools is a good tool and you should definitely have it just in case for backing up stuff and tinkering with ADB.
With all that said,you should join our Whatsapp group for more faster help and updates by messaging me on my Whatsapp No. +919468519959
Enjoy!
Edit: writing all this is a pain in ass,at least one thanks is deserved
Thank you so much...
Mr.Ak said:
Okay don't panic!
Clearly your device is fine by hardware stuff so let's fix some myths and problem of yours.
Firstly,this is mt6592 so you don't have to unlock any boot loader stuff.You can just root your device using kingroot or kingoroot(google it).
For more please read out this whole section,
https://canvasknightroms.blogspot.com/2015/10/rooting-canvas-knight.html?m=1
Now I believe you have root by now. Now all you need to do is get a recovery and as you're on v2 you can find it here,
https://drive.google.com/file/d/0B5W6R0DsDjWTU1o3TEpfWGFsMEE/view
This is philz recovery with OTG support.As you've root just download the IMG file and flash it though flashify,you can find it on Play store.So you've recovery!
Again,these are just suggested methods,you can do all that with other methods too.Also please stop wasting time on stuffs like miracle boxes and etc etc.
Secondly to get your imei back it would be very easy as you've recovery.
https://drive.google.com/file/d/0B6-QF5uchBNhbFlfVk1wOEthbms/view
Just flash this file in recovery and everything shld be fine.
Now to fix Nvram error,just extract the folder from this backup zip,
https://drive.google.com/file/d/0ByuIKfMkBBxBaXBZRHJnNHVRMVk/view
And using any root explorer(I prefer es file manager) go to /data root and replace nvram folder with the folder in this zip
Now the best recovery would be philz recovery for v2 but I greatly suggest you to flash v3 for a variety of reasons and custom ROMs.Yes,you need to shift to v3 to get LP or MM and new updated ROMs though you can still flash available ROMs for v2 which you can find here,
https://canvasknightroms.blogspot.in/2015/10/all-roms-link-for-v2.html?m=1
Very less isn't it? That's because storage barrier in v2.
You can find various mods here,
https://canvasknightroms.blogspot.in/2015/10/mods.html?m=1
You can find correct stock ROMs here,
https://canvasknightroms.blogspot.in/2015/10/stock-rom.html?m=1
Flashing the sim fix above will eventually fix SN too.
And yes many custom ROMs are bundled with SuperSU so you should use that.
To convert from kingroot user to super su use this guide,
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
And lastly mtkdroidtools is a good tool and you should definitely have it just in case for backing up stuff and tinkering with ADB.
With all that said,you should join our Whatsapp group for more faster help and updates by messaging me on my Whatsapp No. +919468519959
Enjoy!
Edit: writing all this is a pain in ass,at least one thanks is deserved
Click to expand...
Click to collapse
Hi Ak,
I went through your entire post and more or less got most of the useful and helpful information. I have not gone through all the links and will do so in due course.
I have been on your website and have read quite a bit and was happy to see the dedication and commitment to help people like us.
I am sure the phone like you said is stable and away from hardware issues. I will consider flashing vs. 3 soon. Yes, i agree with you there are more choices for vs. 3. I did peep into the website last week to see the big list of custom ROM's for vs. 3.
Last but not the least, God bless you. Shalom.
Frank Morris said:
Hi Ak,
I went through your entire post and more or less got most of the useful and helpful information. I have not gone through all the links and will do so in due course.
I have been on your website and have read quite a bit and was happy to see the dedication and commitment to help people like us.
I am sure the phone like you said is stable and away from hardware issues. I will consider flashing vs. 3 soon. Yes, i agree with you there are more choices for vs. 3. I did peep into the website last week to see the big list of custom ROM's for vs. 3.
Last but not the least, God bless you. Shalom.
Click to expand...
Click to collapse
What about joining our whatsapp group?

[Solved] Stuck in Bootloader

so i was trying to flash CherishOS so i followed the instruction and found some problem but i was managed to solve the problem. FYI, the rom gave the link to the custom recovery which is the PixelExperience one, since i'm coming from the stock latest rom so i flashed that. until i done everything and boot to system, and it just keeps returned to the bootloader no matter which option i choose (boot to system & recovery), but luckily the device is still detected in my computer
What i've tried :
- flash recovery (PixelExperience & TWRP)
- Followed this instruction
but none of that is working, one thing i found out while doing the 2nd method is that it shows some errors like "flashing is not allowed for critical partition" and "partition not found".
I have no clue what to do, i've tried whatever solution i could find and none are working. please help, thanks
edit:
I also tried the "fastboot flashing unlock_critical" and tried to reboot into fastbootd but failed and the fastboot shows all command list
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
xtcislove said:
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
Click to expand...
Click to collapse
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
B1nz said:
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
Click to expand...
Click to collapse
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
flo musti said:
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
Click to expand...
Click to collapse
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
B1nz said:
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
Click to expand...
Click to collapse
already tried but the phone is not going in Qualcomm EDL mode...
flo musti said:
already tried but the phone is not going in Qualcomm EDL mode...
Click to expand...
Click to collapse
in my experience, my phone is just showing nothing it's like the screen is off. i realized that my phone is in EDL mode is it's detected in my computer as qualcomm something.., when it shows like that that means you haven't installed the qualcomm driver. after that the name will change to "more normal" name. and then you can proceed into the tools

Categories

Resources