I'm hoping somebody here can help, because I'd hate to have to get rid of a device that I really love...
Used Helmi's WM6 (http://wiki.xda-developers.com/index...angel_WM6_Home) to upgrade from WM2003SE and everything was working beautifully!
I was absolutely LOVING the new software until my device just stopped accepting the passcode that I had been using for 2 years. What I don't understand is I had to use the passcode a few times after the upgrade and all was fine. What could have happened for it to suddenly change by itself (because I know it wasn't me)?
Someone at the PocketPCAddicts forum suggested that I locate an original factory ROM to wipe out everything on the device and try again from scratch. I've searched the web looking for such a beast and can't find one (since the manufacturer/carrier no longer support it).
Can someone here help?
Debbie
Had the same problem...
Hi Debbie,
Same thing happened when I upgraded from WM2003 to the WM6 ROM. Unfortunately there was no solution and I just ended up disabling the password to ensure I never got stuck.
If you ever stumble upon a solution that works for you, I'd be happy to hear about it!
I'm about to try out the latest WM6.11 and hope it will have that particular issue solved - I'll let you know.
Ken
if you press and hold power+record+camera the same time and then reset you get to the boot loader.
you will see the 3 options, which i have fogotten, but if you put in the same options as instructions tell you after flashing a new rom, then push the mail button i believe, it will format you memory and you will be able to get back in again.
i had the same problem where i was locked out and i did that and just sync'd again to get back to my positon prior getting locked out.
hope that helps
Thanks, I will try it again.
Should I be able to simply repeat those steps, or should I start from the beginning? I don't have the device with me right now.
Thanks again,
Debbie
follow the instructions after the flashing the rom stage all the way to the end.
you choose to format memory on the gray screen with 3 options.
i flashed the wm6.1(5.2.19716) several days ago, and tested in several situations, my BA can remember the pw now, thanks for the hardwork of rom maker.
Thanks! (Now Internet Problem)
I got it to finally work, after getting a 3rd hand to help in the key combination/timing.
Only problem now is that my SX66 no longer connects to the Internet. Tried every setting/CAB I could find and no dice. AT&T tech and advanced tech support didn't help and I was told that the OS may have corrupted the connectivity.
Should I try loading another WM6 version?
Thanks again,
Debbie
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
http://forum.xda-developers.com/showthread.php?t=1280097
Please read my problem I have encountered and how I have solved, hope this helps.
After step 6 while trying to install Mango I recieve error code 801812c1.
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
theonlyremedy said:
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
Click to expand...
Click to collapse
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
alodar1 said:
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Click to expand...
Click to collapse
Called Dell Mobility. Even though I could restore back to previous version, they offered to replace the device, which I took.
Kind of sad though, I've never had problems with wifi or anything else on this phone. In fact the only problem ever with a VP was me dropping the thing. I'm hoping the refurb I get will also not be a problem.
alodar1 said:
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
Click to expand...
Click to collapse
Thanks alodar1..
I asked Dell to do a service and added that I don't need an replacement. The service guy said the phone is new and they are not trained to service this, so they would only do a replacement. I'm not ready to do a replacement, they ask me to go for international warranty, moreover they replace with factory refurbished phones.
BTW, I would like to know if there is anyway to format the memory card without removing or replacing. Right now I have another problem whenever I press the power button to boot my phone it directly goes to Software Download mode, the camera button was never pressed.
While trying to repair using Windows Phone Tool, I received this error "The tool cannot recover this phone, please contact technical support", so being a little curious I fired up .NET Reflector and loaded the tool to find out what was happening, I found that the this error is thrown if the phone is not Samsung made (see attached file). Is there any similar tool for Dell Phones?
*UPDATE 1* Is there anyway to force flash without using Zune, any third party tool, Zune seems to go to restore mode and can't find my phone. I have a feeling that erasing the contents of SD card will solve the problem.
*UPDATE 2* I did the registry trick and was able to see my DVP in Computer window. But instead of one DVP, I see 2 and both have storage of 3.75 GB each. But my DVP is 16GB, both DVP are empty. Previously I was never able to see my DVP even after registry patch. Now I have feeling that corrupt drivers caused the problem, yesterday I completely removed and reinstalled Zune Software, now the registry patch worked.
Please let me know with problem my DVP could be hardware fault or just the software. If its hardware then I'll go for replacement right away.
Just recieved my replacement VP. Ordered yesterday around noonish. Went downstairs to get the Motorola Xoom box that was delivered...and the VP was there too. Bonus....
Did not come with Mango....but....there's not a scratch on this thing....not a rub, not a bump...nothing. Still has plastic in places I doubt they would put plastic after refurb. I'm wondering if I got one of hte left over new ones....
Doesn't matter....Mango won't install no matter what...so...maybe I'll try ICS.
My Mango is now Ripe..
alodar1 said:
My Mango is now Ripe..
Click to expand...
Click to collapse
Nice to hear that!
alodar1 said:
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
Click to expand...
Click to collapse
How do you flash it back to 7392? I need to flash mine.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
not a flash, but a restore. I've always made copies of my backups ...
You an't reflash as the user above me already said, that said, the backups are stored in
=> %userprofile%\AppData\Local\Microsoft\Windows Phone Update
so for backing up your restore poiints you can copy that folder and then keep it.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
I was just curious. I wanted to fix my phone. The backup restore didn't work. I was just looking for some way to flash it or at least format the SD Card, so that I reinstall OS and can get my phone working. After four days of trying to fix my phone, I finally gave up and sent it for service to Dell. I even copied a little bit of code from phone support tools and tried them, I was just able to get the phone details without any problem, Mango was installed in the phone, but still it didn't boot. It would be good if we find a way to touch the SD card and format it from PC, probably we'll be able to revive many bricked phones. I would be happy to join the project if some one starts it. I can write C# code.
Mine is an error during backup
Error Code 801812DC during backup
I also add new thread.
If anyone knows, please tell me what I need to do.
Hello
I have a Yotaphone 2 running android 5.0. I have a huge problem with the device which is, that the phone reboots automatically all by itself after the screen turns off. The screen timeout is set at 1 minute and once the screen goes off, the phone reboots! I don't know what the problem is but its making me crazy!
Note: The phone does not reboot if the screen doesn't turn off. So I changed the screen timeout to 30minutes. Also note that Wi-Fi doesn't start immediately. It doesn't even start most of the time and is stuck at "turning on"! And also, the phone isn't detecting my SIM Card!
Hope someone can solve my problem.
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
I got the phone as a gift
TheArt. said:
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
Click to expand...
Click to collapse
-The phone was a gift from "Aramex Company".
-Yes, I have factory reset it! Note: It wasn't possible to reset it from settings because it would always get stuck in "Shutting Down" phase and nothing would happen. So I hard reset it.
-I found something strange going on though. Whenever I reset it, It would restart (after the reset is over) and say that "ANDROID IS UPGRADED TO 5.0".
I think it is upgrading by itself to 5.0.
-No, I haven't tried any flashing.
-Yes, the phone was working fine for a while and then started behaving like this!
Cheers!
(Thank You for your support and attention by the way)
Video
Hello!
I have made a video showing what the problems are! Please give me your e-mail so that I can send you the "Dropbox" link to the video.
Thank You!
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Flashed it!
TheArt. said:
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Click to expand...
Click to collapse
Hey!
As you had prescribed, I flashed it! First I flashed it with Android 5.0.0-ME1.1.60 and after opening the phone I used it for a while and the phone was same as before flashing! There was no difference at all! The phone was restarting on turning screen off as usual, the WiFi wasn't turning on, and the SIM wasn't being recognized!
But then I flashed it with Android 4.4.3-S01-003-ME1.0.3.61a and the phone is still rebooting by itself upon switching the screen off and the WiFi problem still persists! The WiFi just simply won't turn on. It's stuck at "turning on"! The SIM isn't recognized either! Also, the phone is restarting from the inside now (It wasn't restarting before. I had to keep the power button pressed every time I wanted to restart)! But NOTE that the phone still cannot be just shut down, it can only be restarted!
I don't know what to do!
Cheers
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Why are you unable to make yotaflasher work
lgk350tr said:
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Click to expand...
Click to collapse
Hi lgk350tr,
Why are you unable to make yotaflasher work, it is a pretty simple application. Have you tried to see instruction videos on YouTube on how to use it? Instructions are also available on XDA Developers' website. ( https://forum.xda-developers.com/yotaphone-one/general/yota-flasher-download-t3480922 )
Don't hesitate to contact, for any problem!
Cheerio
Please help..................I spent 800 USD on this phone and I can't use it
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
akahomeacc said:
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
Click to expand...
Click to collapse
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Is this what you mean?
tomgaga said:
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Click to expand...
Click to collapse
I have attached a screenshot of the Yotaphone 2 General guide page, I want to know if you are referring to the text that I highlighted in the screenshot!
Thank You
I do experience similar issue, but only recently. I haven't done anything like flashing or upgrading my phone, it started by itself .
I am experiencing reboots whenever battery drops below about two thirds of its capacity. Also, charging and handling some load prevents this.
Note that my Yotaphone has both displays damaged. Still working though.
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.
s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.