Database Users

[Q] Did I brick it or not?

I tried to root my 3G XOOM (MZ606) last night and eventually I did brick it but I am not sure. I did definitely dl the wrong img file (as I didnt read here before Anyway everything of the procedure went fine till I had to type the commands (like adb remount) after reboot. Actually the XOOM does not seem to connect to my wireless hotspot anymore (is that due to a missing key?) and it remains in the boot up screen (just the MOTO logo)
Is there any solution to get the XOOM reconnected may be? Can anyone push me into the right direction? Do I really need those certain cable (someon mentione in any thread here)?
--
thanx a lot for your help
Michael

if you have ANY type of screen coming up, its not bricked. Depending on your situation, you just need someone whos good with ADB/Fastboot to get things back to where they need to be.
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
go into recovery and wipe Everything/ factory reset, wipe cache, and go into advanced and wipe dalvik cache. then flash any rom available here in the DEV section.

hmmm I found out how to do that
>go into recovery and wipe Everything/ factory reset, wipe cache
but what means
>and go into advanced
? There is no advanced option at the recovery menu. So may be thats an otion once I choose 'reboot system now'?
And just for my understanding, that
>then flash any rom available here in the DEV section
is not necessary just may be in my interest, right?
--
Thanx anyway, great help
Michael

It might help us if you tell us what model your Xoom is...3g/wifi - us/uk - all the specifics.
Hopefully you knew this before you installed the wrong image.
Then we can help you get back to where you need to be.
And 'flashing any ROM here in the development section' is what got you here in the first place so I wouldnt do that.

Hola,
well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?
So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1
Hope those background information allows some more conclusions but
right now I am still trying to figure what kenfly ment by mentioning
>go into advanced and wipe dalvik cache
If I understand for example those guys http://forum.xda-developers.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?
--
Cheers Michael

[email protected] said:
Hola,
well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?
So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1
Hope those background information allows some more conclusions but
right now I am still trying to figure what kenfly ment by mentioning
>go into advanced and wipe dalvik cache
If I understand for example those guys http://forum.xda-developers.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?
--
Cheers Michael
Click to expand...
Click to collapse
Did you flash the ClockworkMod recovery before rooting [after unlocking], and if so, which version?
If you don't have that installed, you wouldn't see the advanced option in the recovery menu.
You have a wifi model and I think the wifi hardware is all the same so you could flash the US Xoom system image and that should solve your access and updates problem, But since it's a HongKong Xoom, there may be some differences, so try it out but use caution.

hey guys looks as I dont get the message. I am still stuck at the recovery screen. I did
>go into recovery and wipe Everything/ factory reset, wipe cache
but whats next? Rebooting does not change anything, still the same logo screen only. So am I supposed to apply a proper image by 'apply update...'?
--
Cheers

You say you have a 3G Xoom - but the MZ606 is WiFi only.
Do you remember what image you applied to mess things up in the first place?

sure, the name is rootboot.img
It should be the one from 3*w.addictivetips.com, '/?attachment_id=45936'. I separated the link as I dont wanna mislead anyone here but I hope its still possible to follow up
--
Thanx for your help
-sorry for the 3G thing, no idea why I did type that. It definitely is a WiFi only
-and i idd not do any clockworld thing before or what ever. It has been just an ordinary MZ606 automatically updated to the 3.1 android version, but unlocked. For unlocking I used the android.sdk and typed the command to do so, thats everything I did before getting stucked with those rooting procedure

Hey guys dont leave me alone. I may tend to do another stupid thing ... well I am capable to find former posts about how to recover so on but as U asked some more details it seems to be depending on which exact device I have and what exactly I did before. So I hope U could still guide me to the harbor

hey.ur on 3.1 right?
I assume you have knowoedge on fasboot.
Find the appropriate boot.img for ur device then flash it via fasboot.
Maybe u flash the wrong boot.img
---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------
Or go back to stock. http://developer.motorola.com/products/software/

well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.
So how could I flash another ROM to the device without having the OS working on it properly?

[email protected] said:
well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.
So how could I flash another ROM to the device without having the OS working on it properly?
Click to expand...
Click to collapse
Do you have the proper drivers installed? Make sure you get them from Motorola.
Your device should be seen if ADB and Fastboot are set up correctly.
Once you can see the device I would use fastboot to reinstall the proper image (again from Motorola - they will have the correct Image for your Chinese Xoom)

yes I do have the proper drivers from M and they worked perfectly before once I flashed the wrong image. May be my problem is too simple for U guys or as I am not capable to deliver appropriate information to get some help.
For my understanding it is obvious why my pc can't get the device as the device obciously cant get an wireless IP without knowing the WPA2 key and I cant type in the wireless key as the OS (on that device) does not fully start up. Which wireless device works without any basic configuration? So does mine I guess even though I am not expert... but even I deactivated any security measures on my router it still the device didn't connect (check only at the routers active device list)
Once again my question: How could I flash another ROM to the device without having the OS working on it properly? I think the OS is (part of) those wrong IMG i did flash before, so I assume I will never get it working
--
Regards

Can u go to fastboot?
When the xoom bootup press vol down immediately.it says starting fastboot etc.
If your pc can detect it then flash the correct images to ur xoom.
Btw lets talk on yahoo msgr. Pm me ur email.im free this time.

princenoob said:
Can u go to fastboot?...[/UOTE]
I keep he decvice at the recovery menu for 2 days now but yes I can "go to fastboot" too but again that doesnt change anything regarding connecting my device to the wireless router. Why none of U guys replies on those obvious fact? The XOOM like all other devices I know will not connect to any wireless hotspot without any confirmation (may be a password) on its UI and as I cant get into the UI...
May be its the wrong directory for thes question. Is it possible to shove to Q&A?
Click to expand...
Click to collapse

No no.why would you connect it on wireless router in the first place.connect it on ur pc! So if the pc detected it.then flash thru adb.

oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.
So if it really is the MZ606 (I can take the battery off the HTC just to make sure should I go back to the original image first, then install clockworld, then root?
--
thanx in advance

Sdk only detects devices connected to pc.so your phone has nothing to do with it.did u already download the firmware for ur xoom?the link i post awhile ago download the rom there.do you know how to flash it thru fastboot?.if yes then i think u can revive ur xoom.
---------- Post added at 10:30 AM ---------- Previous post was at 10:25 AM ----------
if you have ur original copy of ur boot.img then flash it.if not better flash from stock.the use this tutorial to root. http://forum.xda-developers.com/showthread.php?t=1242241
Please hit thanks if i help you in anyway.

[email protected] said:
oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.
So if it really is the MZ606 (I can take the battery off the HTC just to make sure should I go back to the original image first, then install clockworld, then root?
--
thanx in advance
Click to expand...
Click to collapse
[email protected], you seem to be lacking some very basic understanding of how all of this works on the Xoom. No wonder you felt frustrated.never in a million years would I guess you would try to flash an update or recover your Xoom via a wireless connection.
That said, hopefully you are now on the right track. I wish you good luck.

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?

Phone will only boot into TWRP

So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.

hegro said:
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
Click to expand...
Click to collapse
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.

GtrCraft said:
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
Click to expand...
Click to collapse
Pretty sure I was just stock rooted. How would I go about doing that? Like I said, I have a stock rom downloaded on my PC. Tried to flash it but all I get is 'waiting for device' in the cmd window after directing it towards the zip file.
Also as I said, trying to learn and absorb as much info as I can here, never done this before so I am a little slow. =/

just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?

hegro said:
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
Click to expand...
Click to collapse
Boot to twrp and flash a custom rom zip like lineage os. Or a modified stock rom like stoneware

Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.

hegro said:
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
Click to expand...
Click to collapse
I had this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig

Go into fastboot and just type fastboot continue
fixed

alevity said:
I has this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Click to expand...
Click to collapse
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.

hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash

power off your phone then volume down and power together until bootloader screen appearing than select factory mode and then press power button to select factory mode

hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bornlivedie said:
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
Click to expand...
Click to collapse
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.

pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.

hegro said:
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
Click to expand...
Click to collapse
That's stock recovery

alevity said:
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
Click to expand...
Click to collapse
I wouldn't know about "perfectly ok" but I had that bad key thing before, and read the rebooting into TWRP fixes the "issue". It's true, it works. I have N/A now and not "bad key".

I discovered super brick

Yes folks,
As I said, I discovered SUPER BRICK, TOTAL BRICK, COMPLETE FAILURE or whatever yoy want to name this new brick. It has been like this: I was following the instructions to update oreo in HONOR 8 LITE, at the end I had to write some codes in twrp (advance / terminal ...) so it was starting to do the last update (sd card update.zip) and by accident I touched the screen where it appears: REBOOT, so the phone restarted but the screen is not working when it tries to enter erecovery mode, so here is the list of my problems:
- it does not work: erecovery (so I can not recover the phone)
- fastboot works: when I install something (twrp or firmware, I have tried everyone of them) the phone does not start
- if I try to go to TWRP (after installing an oreo one): the screen seems to break and you can not see anything
Please, my phone is 2 months old, man I need to make it work again, I need it.
Help help help

You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work

Nikola6511 said:
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Click to expand...
Click to collapse
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance

alopez_666 said:
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
Click to expand...
Click to collapse
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?

Nikola6511 said:
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Click to expand...
Click to collapse
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.

alopez_666 said:
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
Click to expand...
Click to collapse
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?

Nikola6511 said:
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Click to expand...
Click to collapse
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead

alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead

alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
I think your EMMC memory might be fried

Nikola6511 said:
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
Click to expand...
Click to collapse
What about using DC PHOENIX???? What do you think????

alopez_666 said:
What about using DC PHOENIX???? What do you think????
Click to expand...
Click to collapse
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work

Nikola6511 said:
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Click to expand...
Click to collapse
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.

Same for me, how to fix please. Bricked following this "guide"
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official Emui Nougat, wanted Oreo, forced update with nocheck, everything is broke except fastboot.
When I want to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk /path/to/img" it work but can't reboot to recovery.
I press Power + Vol+ but it reboot "phone untrusted" with Vol+ for going to eRecovery (usualy it's here you can shutdown the phone) but error mode.
Maybe the OreoTWRP work after my command but can't boot into it. Please help.

alopez_666 said:
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Click to expand...
Click to collapse
Bro my P8lite is also bricked, I accidentally wiped the EMMC then I showed it to a repairer and he somehow took me to fastboot mode, now I can't flash anything because that repairer has partitioned the EMMC and now it is showing 486mb total storage so no ROM is flashing because of size. Can you please give me your USERNAME and PASSWORD of DC Pheonix as you've already bought it. It will solve my issue and it will also save me some money.... I will be very thankful to you....
WAITING FOR A POSITIVE REPLY.

I bought it some time ago and it was a 72 hours license and it expired so I do not have anything from that situation. I will check my computer but I will not probably find anything.

alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps

legionfx said:
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
Click to expand...
Click to collapse
Problem was solved, I used DC Phoenix and installed a rom, but I did it some time ago. Thanks anyway

Attempting to root and install Android 10 on Nexus 6P. Noob needs help!!!

Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you

xa3phod said:
Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you
Click to expand...
Click to collapse
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?

Ata Ur Rehman said:
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?
Click to expand...
Click to collapse
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?

xa3phod said:
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?
Click to expand...
Click to collapse
Probably It is losing connection to PC try another cable and reinstall and drivers on your PC.
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
You can follow this video for detailed installation ( keep in mind if you aren't a BLOD user so you just skip flashing 4 core files )

Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!

xa3phod said:
Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!
Click to expand...
Click to collapse
Did you Turn OEM unlocking on?
Did you have flashing and downlaod mode unlocked?