Related
[Q] My motorola razr i showing message "android is upgrading" then restarting again
I writting with my problem on your post, just getting hope that mine will work too.
Actually I have also ''NIL'' knowledge about all this software/ quote language etc
My issue is; my Moto Razr i is just stuck on '' Android is upgrading '' than shows ''Starting Apps'' thn nothing happen n same things repeats ... couple of hours back it was saying ''finishing boot'' also but now it is just giving this error '' Android is upgrading '' than shows ''Starting Apps'' thn nothing happen n same things repeats
Please I want to request if you are about to guide anything in tough language please consider that I am completely unknown to all the setups and stuff... just if you can help sharing step by step process and also post specific link/software to download (if needed) and how to download and other details in simple guidance plz plz plz.
One more point I tried to chat with Motorola chat service and they suggested me to power off it first but i m pressing vol- and vol + and power button but phone is quickly restarting on its own... i m even unable to go on boot as they suggested me to do so.
Thanks a lot to ''my upcoming angel'' in advance
Hope one can help me at earliest.
i recommend flashing stock rom again.
RSD Lite: http://forum.xda-developers.com/showthread.php?t=1974568
4.1.2 ROM: http://sbf.droid-developers.org/phone.php?device=13
to power down the phone look at this link: http://forum.xda-developers.com/show....php?t=2220242
P.S one thread is enough lets use this one...
5m00v3 said:
i recommend flashing stock rom again.
RSD Lite: http://forum.xda-developers.com/showthread.php?t=1974568
4.1.2 ROM: http://sbf.droid-developers.org/phone.php?device=13
to power down the phone look at this link: http://forum.xda-developers.com/show....php?t=2220242
P.S one thread is enough lets use this one...
Click to expand...
Click to collapse
Yep that's one way of solving it
But your last link doesn't work.
I suggest the following to reboot the phone to AP Fastboot mode (also called 'bootloader' in the android world):
Hold power, vol - and vol + for about 10sec. At the moment the phone reboots, release all buttons except the vol -. U will now boot in AP Fastboot mode. Release the vol - when in AP Fastboot mode.
But before doing this, make sure RSD-Lite is working and u have the right device drivers and right firmware at hand. See the above links.
So first the first link for the drivers and rsd-lite.
Then the second link for you latest firmware 4.1.2 (region)
Then my piece about rebooting
And last the First link again to flash your firmware.
Links not working
Hazou said:
Yep that's one way of solving it
But your last link doesn't work.
I suggest the following to reboot the phone to AP Fastboot mode (also called 'bootloader' in the android world):
Hold power, vol - and vol + for about 10sec. At the moment the phone reboots, release all buttons except the vol -. U will now boot in AP Fastboot mode. Release the vol - when in AP Fastboot mode.
But before doing this, make sure RSD-Lite is working and u have the right device drivers and right firmware at hand. See the above links.
So first the first link for the drivers and rsd-lite.
Then the second link for you latest firmware 4.1.2 (region)
Then my piece about rebooting
And last the First link again to flash your firmware.
Click to expand...
Click to collapse
Thanks a lot for your advice and also sorry for troubling by two posts for single issue, will take care onwards
You have guided in very simple manner but the problem is that I
1 - RSD-Lite is not opening as it says ''find the app to open msi file''
2 - The 4.1.2 region I found is .... Android 4.1.2 Blur_Version.91.2.29001.XT890.Retail.en.GB is it ok?
3 - This link is giving error ''404 Page Not Found The page you requested was not found. Use the search tool below to find content on our site.'' where you said to power down the phone look at this link: http://forum.xda-developers.com/show....php?t=2220242
4 - And last the First link again to flash your firmware. ... I am not sure which first link is it? if its about RSD Lite thn its not opening in my pc dear
I am using windows 8 on my Laptop .. anything else to download to support or open this RSD lite first?
Also my phone is not going on boot by trying your suggested method as well... it is just reopening on its own and going on its problematic ''app starting'' screen error n thn goes off n restart again unless it consumes all of its battery
Without phone its like someone has cut the wings
Please help brother !!!
Thankks
Sohail Ali said:
Thanks a lot for your advice and also sorry for troubling by two posts for single issue, will take care onwards
You have guided in very simple manner but the problem is that I
1 - RSD-Lite is not opening as it says ''find the app to open msi file''
2 - The 4.1.2 region I found is .... Android 4.1.2 Blur_Version.91.2.29001.XT890.Retail.en.GB is it ok?
3 - This link is giving error ''404 Page Not Found The page you requested was not found. Use the search tool below to find content on our site.'' where you said to power down the phone look at this link: http://forum.xda-developers.com/show....php?t=2220242
4 - And last the First link again to flash your firmware. ... I am not sure which first link is it? if its about RSD Lite thn its not opening in my pc dear
I am using windows 8 on my Laptop .. anything else to download to support or open this RSD lite first?
Also my phone is not going on boot by trying your suggested method as well... it is just reopening on its own and going on its problematic ''app starting'' screen error n thn goes off n restart again unless it consumes all of its battery
Without phone its like someone has cut the wings
Please help brother !!!
Thankks
Click to expand...
Click to collapse
Ok, new one.
First the phone should reboot in my way. There is no possibility it will boot to the screen with android "app starting" if it is executed right . Try few more times and get the hang of it. Hold all 3 buttons and at the moment the phone reboots (vibrate, screen goes black and green led will shine a bit after), only hold the vol -. Just release the power and vol+.
There is another way to get to Ap Fastboot mode. It requires you to have adb up and running. Search on the internet for adb (can be found in the razr i subforum) and again make sure your device drivers are installed correct.
If you think al is set and ready. Boot your phone normally to that screen with the message. Then open a command-prompt and type "adb devices". If it says, can't find adb. Open the command-prompt in the adb folder with holding shift and right mouse button. and click command-prompt. When adb devices gives u a device. Type in "adb reboot bootloader" to get into AP Fastboot mode.
If you have issues with executing msi files there is something wrong with your windows. Try and search on the internet to solve that.
Let us know how it goes
Hazou said:
Ok, new one.
First the phone should reboot in my way. There is no possibility it will boot to the screen with android "app starting" if it is executed right . Try few more times and get the hang of it. Hold all 3 buttons and at the moment the phone reboots (vibrate, screen goes black and green led will shine a bit after), only hold the vol -. Just release the power and vol+.
There is another way to get to Ap Fastboot mode. It requires you to have adb up and running. Search on the internet for adb (can be found in the razr i subforum) and again make sure your device drivers are installed correct.
If you think al is set and ready. Boot your phone normally to that screen with the message. Then open a command-prompt and type "adb devices". If it says, can't find adb. Open the command-prompt in the adb folder with holding shift and right mouse button. and click command-prompt. When adb devices gives u a device. Type in "adb reboot bootloader" to get into AP Fastboot mode.
If you have issues with executing msi files there is something wrong with your windows. Try and search on the internet to solve that.
Let us know how it goes
Click to expand...
Click to collapse
Soooo Happy and Grateful to you Mr Genius and Well on time ANGEL''
I realized two things while following all the guidance, First is; I admit that I was too ''NIL'' to understand and act on simple method of rebooting so after few times practices I was able to execute it right. Second that I am not that dumb as finally I was able to notice the issue of ''not opening MSI'' extension as only ''a dot'' was missing in the name of downloaded file, so I have added that ''dot'' in between of 4 and msi ... (4.msi) and rest your software has worked very quick and automatic & I found my phone's breath back...
So bundle of thanks for your quick and kind support brother.
Be Blessed
Take Care
Sohail Ali said:
Soooo Happy and Grateful to you Mr Genius and Well on time ANGEL''
I realized two things while following all the guidance, First is; I admit that I was too ''NIL'' to understand and act on simple method of rebooting so after few times practices I was able to execute it right. Second that I am not that dumb as finally I was able to notice the issue of ''not opening MSI'' extension as only ''a dot'' was missing in the name of downloaded file, so I have added that ''dot'' in between of 4 and msi ... (4.msi) and rest your software has worked very quick and automatic & I found my phone's breath back...
So bundle of thanks for your quick and kind support brother.
Be Blessed
Take Care
Click to expand...
Click to collapse
Glad it is solved!
I have Moto g 2nd Gen Indian edition phone
I have been experiencing a strange issue with my phone from past week, when I lock down my phone via power button or closing the cover of magnetic flip-shell or whether it locks it down itself after 'screen time out' automatically the display just shut downs.
The phone is actually working in background as I can see LED notification sometimes. And when I connect my phone to PC via USB it even shows the Internal storage folder. I can even feel vibration on Powering off the device.
When I try to reboot the device, it boots up normally with Motorola logo animation and everything works fine until device gets lock down and this scenario continues as I reboot it again.
Sometime I can feel the bottom speaker grill getting hotter until I 'Power Off' the device forcefully.
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
I want to clarify that my phone isn't under warranty and also I have not even tempered my phone's software it is completely stock with android version 5.0.2 (recently updated via OTA).
I'm not allowed to post the image as a new user that's why I have written some software specific detail as below.
System version: 22.56.3.titan_retaildsds.retaildsdsall.en.03 retin
Build No: LXB22.99-16.3
Base band version: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
Kernel version: 3.4.42-g0bea67a
[email protected] #1
Wed Aug 26 00:26:33 CDT 2015
I don't think the 'Power Button' can be faulty as it's working as intended properly and almost all the time I use the official Motorola 'Magnetic flip-shells' so I rarely use the power button.
I suspect that this issue may have been caused by some virus or malware as I had visited some torrent hosting and too much ad hosting sites before the issue started.
I contacted Motorola support via chat session and they asked me to get it to the service center, but I have read very bad reviews about service center near my location and I'm afraid to go there.
Although I'm a software developer but in the area of 'Android development' I'm totally noob so joined the XDA to solve the issue with the help of experts.
Can I have some suggestion, solution on this issue? Any help of yours is appreciated.
Also I want to know that if 'Hard reset' can't solve the issue, does that mean the software of device has corrupted?
Try a hard reset first
If not solved use an easy installer
vaisakmct said:
Try a hard reset first
If not solved use an easy installer
Click to expand...
Click to collapse
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.
smartandcool3 said:
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.
Click to expand...
Click to collapse
ya this one will be best for u
vaisakmct said:
ya this one will be best for u
Click to expand...
Click to collapse
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?
Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader
vaisakmct said:
Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader
Click to expand...
Click to collapse
but as suggested by @reefuge in post #13 and #post16 in link below
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612/page2
that 'Phone must have USB debugging enabled and RSA key Allowed, Usb cable plugged in and in normal use mode'
1. I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated please click to disable"
2. if I go into the Device Manager I can see Android Device
3. I changed my USB-Setting to PTP
but nothing works.
smartandcool3 said:
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?
Click to expand...
Click to collapse
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here
reefuge said:
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated
smartandcool3 said:
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated
Click to expand...
Click to collapse
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run easyinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new
reefuge said:
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run eastinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new
Click to expand...
Click to collapse
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?
smartandcool3 said:
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?
Click to expand...
Click to collapse
anywhere as it includes (in extracted folder) ALL the files required to make it work
reefuge said:
anywhere as it includes (in extracted folder) ALL the files required to make it work
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.
smartandcool3 said:
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.
Click to expand...
Click to collapse
Ok, Guys I was able to run the 'EasyInstaller' and it worked perfectly and magically as it should supposed to be.
Unfortunately I was not able to resolve my problem so It might be something else.
@reefuge sir your 'EasyInstaller' was awesome, and I will highly recommend it to everyone for 1-step solution in need, please keep making these kind of awesome tools.
Thank you @reefuge sir and @vaisakmct once again for all your help. If you have anymore suggestion or solution regarding my problem please let me know.
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
PLEASE SEE "TROUBLESHOOTING" AT THE END OF THE GUIDE FIRST IF YOU HAVE PROBLEMS IN THE PROCESS BEFORE ASKING!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
VIDEO GUIDES
FOR LINUX METHOD CLICK HERE - Credits to @bx2_nero
Windows Method
Requirements:
Bypass Tools Pack - (SPFLASH TOOL, DRIVER AND BYPASS FILES)
Decrypted OFP (OPPO FIRMWARE PACKAGE) Files:
FULL FIRMWARE - INCLUDES THE "USERDATA" PARTITION, HENCE LARGER.
B.53 - Mega - Google Drive - Mirror3
B.37 - Mega - Google Drive 2
B.23 (First RUI Update for the device) - Mega - Google Drive - Mirror3
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
NOU (NO USERDATA) FIRMWARE - FOR PEOPLE WITH LIMITED DATA PLAN.
B.53 - Google Drive - Mirror 2
B.37 - Google Drive - Mirror 2
B.23 - Google Drive - Mirror 2
A.50[EU] - Mega - Google Drive
A.42[EU] - Google Drive - Mirror2
Please read an explanation of what is userdata partition and how different is this from other firmware here.
Note: All files with available links above are tested.
Python (Must add to PATH during installation, see screenshot if you don't understand)
libusb-win32 - Having Issues? Use this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure to choose the last option.
1)Open command prompt by running cmd,
enter
python -m pip install pyusb pyserial json5
After the installation, you can re-run the command. If it looks like the screenshot above you're ready to go to next step.
after the installation leave CMD.
2) Go to driver folder, find the .inf file right click and press install.
3)Download this file and install it, after installing plug your phone to PC by connecting your phone to PC while doing Vol+- . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.)
If you had a problem here, please check the end of the guide for it's fix.
5)Go into Flash Tool folder and open the SPFlash tool, after that choose scatter file and also if not set, set your download -agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
After flashing it should look like this. Download has been complete. Enjoy!
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
Spoiler: TROUBLESHOOTING - FAQ AND FIXES
POSSIBLE ERROR: "Verified boot enabled."
There are 2 fixes to this.
1st Method (DIRECT FIX):
Click choose DA Agent. (I uploaded an updated bypass tools pack, if you're using older download new one) Go into Bypass Tools Pack > Verified Boot Fix > Choose the "DA_6765_6785_6768_6873_6885_6853.bin" file.
If its giving error go into Options menu and disable option shown below. You will be able to choose a DA file.
2nd Method (WORKAROUND):
If you're getting this error, and you are SURE you used "Download Only" mode, there's a way to get rid of this. First, load the scatter then untick/deselect partitions listed below.
opporeserve2,
cdt_engineering,
my_custom,
special_preload,
userdata,
super,
After running brom.bat and flashing all partitions except the ones listed above, your phone will be able to reboot to stock recovery. Now select " Power Off" option then go run brom.bat, bypass authorization and then flash partitions listed below from SPFlash Tool.
super,
dtbo,
userdata
Your device will be able to boot into system after this if you have followed steps correctly.
POSSIBLE ERROR: Issues while disabling protection;
Power off your device Restart the process from 2nd step.
POSSIBLE ERROR: Issues while flashing;
Power off your device, you will need to do the bypass again. Check your USB Cable, there might be a disconnection. If not, start from 3rd step and make sure you did everything right.
Spoiler: FOR PEOPLE WHO WANT TO DOWNGRADE AND FOR PEOPLE WHO WERE ON EU VERSION
So, welcome to hell(!).
For people who want to downgrade:
If you want to downgrade to any version you would like, just use the B23 file as it is the oldest ofp file i could find for extracting process. If you were on EU version before (Any version starting with A) download ozip from here(for EU) , here(for Global) and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
For people on EU who want to unbrick:
So, you can use any version starting with B and it should work. It works in my case, i was on A.48, i flashed B53 and over that flashed B23. No probs at all. If you want to return to EU rom (starting with A) download ozip from here and manually flash from Realme UI recovery and format your data. Your device will be back at A.XY firmware with EU features (No heytap, no ads, no theme store, no bloatware) you had before.
Thanks --
https://github.com/bkerler/oppo_decrypt for decryptor.
https://github.com/MTK-bypass for creating the tool.
Thank you for your efforts. Can you add the decrypted A34 file?
mercan01 said:
Thank you for your efforts. Can you add the decrypted A34 file?
Click to expand...
Click to collapse
Hello! I wasn't able to find factory package (ofp) files for any version that makes sense for versions starting with A. (EU). There are A11 and A08 which according to update trackers, did never exist and the A.11 package is %50 larger than all the other files weirdly. I have contacted owner of some sites that do upload files like these and they asked for money. If it's a resonable price i will get it, decrypt it and upload here! If you were able to find any versions starting with A, feel free to message me on telegram (@ctivity) or email me!
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
mercan01 said:
Hi, I have a website that publishes A24 version only. https://www.getdroidtips.com/realme-6-software-update/. It gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello again. According to the site you have just sent, A.11 is the first update to EU version. I was thinking it was a mistakenly uploaded file, since userdata partitions are for some reason 9gb with this one instead of 3. If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work. Unfortunately, these files you sent in the link are ozip files and update packages while ofp files are firmware packages and they include everything. There are only 2 ofps -decrypted and not decrypted- available for now starting with A(EU), A08 (first ever firmware for EU) and A11(first update to EU version).
Hello again. Yes, I noticed there was an ozip file and deleted it.
daeSundae said:
If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work.
Click to expand...
Click to collapse
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
Hello! I'm sorry for the inconvenience I have tried flashing A11 file and it caused several problems just like in your case, however if you didn't select "Format All+ Download" mode you should be able to recover your phone. So, I had the exact same issue today and due to that I will be removing the A11 file from the links. Also, never forget to select Download Mode only! Several people bricked today and their IMEIs, Serial Numbers are all gone! Never select anything else than Download Mode!
So the solution is to download B53 decrypted files, load the scatter and untick listed partitions
opporeserve
,cdt-engineering,
mycustom,
special-preload,
userdata,
super
and then start the flashing in download mode. Now, you might be wondering "How am I going to go into the download mode again?" It's very simple. All you have to do is to keep pressing on Power and Vol- for some time and then, connecting to the pc with both volume buttons pressed while brom.bat is running. If you get an error, just reinstall device filters and that should fix the problem, then you can start downloading. After downloading these partitions to the phone, you will be able to see a boot animation and as well as a realme logo. Reboot to recovery, power of your device and then go into download mode again and flash userdata, dtbo and super partitions this time around. It should boot into system. However, the version will be B.53 but you can use the latest ozip (A.48), flash it from recovery and then format your data. It will bring you back to EU version.
cmfan said:
First of all, thank you daeSundae for posting this info here!
Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.
Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.
Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".
Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.
So the USB controller seems to be still alive, but nothing more.
To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
Click to expand...
Click to collapse
So, i just read your reply again.
"Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device."
i dont think it's an issue caused by the device. Can you install oppo drivers from this link and let me know what happens afterwards? Or if you're fast enough you might prefer going into device manager by right clicking on Windows button and uninstall it's driver? I will also request you to start from step 2 to ensure installing drivers. I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
mercan01 said:
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
Click to expand...
Click to collapse
Hello! I have uploaded B23 files both on google drive and mega. It should work for you, it is working for me at the moment. I also was on A48 firmware and both B23 and B53 versions worked without a problem.
daeSundae said:
I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
Click to expand...
Click to collapse
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt. Do you know if your phone has any charge or not? Can you try different volume and key combinations? A broken firmware shouldn't make the BROM Download mode inaccessible.
cmfan said:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.
I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).
It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
Click to expand...
Click to collapse
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to
use "fastboot reboot" command. Please keep pressing vol - button if you can while rebooting if it works. That should, if possible reboot you into recovery.
Also as you said, keeping pressing on power and vol+ buttons don't work in this state. In fact, in this state nothing visually works, there is no screen output and I'm actually pretty sure it's the same for begonia (RN8 PRO). You will need to ~ if it's detecting it as a fastboot device need to use minimal ADB and fastboot tools to get rid of that state. I didn't have the same issue as you though. While I was in same state, I kept on pressing on Vol - and Power buttons for around 30-40 seconds (obviously without a response from the device) and after that pressed both volume buttons and connected device to PC. Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
MTK Bypass Universal
My screenshots were used in this post. I don't mind
MEGAFON929 said:
MTK Bypass Universal
My screenshots were used in this post. I don't mind
Click to expand...
Click to collapse
I'm sorry for not letting you know Dinolek. I tried to create a guide but my Windows is Single Language and since it's not global version or something I cannot change its language. I had to find an English screenshot. If it's a problem, I'll just remove them.
No, I'm not Dinolek. I just talked to him and he accepted my instructions. Let the screenshots lie, I don't mind.
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt.
Click to expand...
Click to collapse
Sounds reasonable and I hope it's true.
daeSundae said:
Do you know if your phone has any charge or not? Can you try different volume and key combinations?
Click to expand...
Click to collapse
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
daeSundae said:
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to use "fastboot reboot" command.
Click to expand...
Click to collapse
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
daeSundae said:
Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
Click to expand...
Click to collapse
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Can you try ADB reboot command on Linux? As it is identifying as a fastboot device?
cmfan said:
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Click to expand...
Click to collapse
If it's detecting a fastboot device, the device isn't dead. What I'm guessing is that your device is working, and on fastboot mode but since there's no display output in this state it will only show a black screen. Can you do ADB devices command? Im guessing adb reboot requires authorization though, but it's worth trying. What I will be requesting from you is to try pressing (and keep pressing on) different key combinations while device is in that state for like a minute or so, for example keep pressing on Vol- and power for a minute then switch to Power and Vol+ for a minute and then keep pressing on both volume buttons and connect device. Can you also see the results after plugging your device into charge and letting it stay for around a minute? I know these might make no sense technically, but in my opinion randomness is your best friend to get rid of situations like this..
cmfan said:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:
Sounds reasonable and I hope it's true.
The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.
Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.
This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.
Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".
Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)
Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery...
Click to expand...
Click to collapse
Hello. again. So, i have asked few people about your situation. Conclusion is, if none of these work you will need to wait until battery wears off and device turns itself off, i'm afraid. I will ask you to not use your phone for like a day and not to keep it connected to a computer for a long time. After making sure it powered off (which, i'm guessing there is actually no way to do that) make sure to prepare the brom.bat file plug in your device with VOL+ - combo and go on. Before doing this make sure to Device Manager > Action > Add Legacy Hardware > Next > Install the hardware that I manually select from a list (Advanced) > Show All Devices > Have Disk > Choose the cdc-acm.inf > Choose Mediatek USB Port and install it to not waste time. I hope your problems will be fixed. I have confirmed that BROM mode shouldn't fall into an inaccessible state because there's no efuse.ini blown. It must be there, but you're probably stuck in a mode that doesn't allow doing anything for some reason.
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
BrickAlcatel said:
I've ran into the following problem:
came home and try to open my phone, code doesn't work to unlock screen. Unless I'm going insane was sure the code was correct twice.
Restart phone, stuck on enjoy.now for a long time, goes to alcatel logo, then goes into an Android Recovery message saying "can't load Android system. Your data may be corrupt."
Then 2 options: try again or Factory data reset.
I've managed to find the following possible solution: https://glebovdev.medium.com/how-to-fix-cant-load-android-system-issue-8a5b0ead5a15
..but I can't even get to recovery screen with more than 2 options. It would be a huge pain if I have to factory reset.. should it be possible to get to recovery mode on my phone as well?
Is there any possible way to get the data off the phone (mainly Google Authenticator to which I'm not sure I have the codes anymore)?
Thanks
Click to expand...
Click to collapse
It could be that your device is trying to boot to the inactive slot, verify in fastboot mode which slot is marked as active and try to boot either in A and/or in B slot.
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
BrickAlcatel said:
Idk if I'm doing something wrong but holding volume up or down as it restarts, the only boot screen I get is:
Android Recovery
TCL/5003d_EEEA/Curie
8.1.0/OPM2.171019.012/5003d_ALWE_EEA_V3
user/release-keys
(aforementioned error)
Try again
Factory data reset
fastboot mode should show other options right?
Click to expand...
Click to collapse
Well, fastboot is to interact through fastboot commands and you can check from there the slot that is active with
Code:
fastboot getvar all
and you see something like slot_active xx
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
BrickAlcatel said:
When I run adb devices in powershell it does not show any devices connected (although the device does show as connected in Windows device management).
In device management it does show as "MTP USB device".
Is this likely to be a driver issue?
Click to expand...
Click to collapse
Device has to be power on to respond to adb commands and from what you were telling your device is bricked..
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
BrickAlcatel said:
It's technically powered on but yes still does nothing but bootloop and try again/factory reset screen. There's no possible other way to get to Android recovery mode when the volume down+power option doesn't seem to be working?
Click to expand...
Click to collapse
Device has to be strongly and consistently on so adb commands can work, they can't work while in bootloop so forget it this way.
What you can try is tipically pwr + vol. up and pwr + vol. dwn, one of them will take you to fastboot mode where you can give it a try to what I pointed out in previous outputs.
OK some progress.. apparently you have to let go of power button and volume up right as the alcatel logo appears, the timing seems to matter. I'm now able to see Android recovery with more options at least so will try from there.
Thanks again for taking time to reply.
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
BrickAlcatel said:
I've tried
Code:
fastboot getvar all
this results in <waiting for any device>
adb devices still shows no list of devices even though in Device Manager it shows as "Fastboot gadget" under other devices
I've downloaded drivers from Alcatel website in case it's a driver issue but on the list of model numbers during setup mine (5003D_EEA according to recovery screen) doesn't show.
I do see a bunch of websites allegedly offering these specific drivers but assume it's risky to download from anywhere other than Alcatel official site.
Click to expand...
Click to collapse
It seems to be a reliable site https://www.androidusbdrivers.com/alcatel-1-usb-drivers/ it offers the 4 different drivers needed covering all the modes that your device can enter to.
I would recommend mainly two things:
- Uninstall/remove firstly all the drivers that you don't use, it could be something for an old android/tablet that you don't use anymore.
- Don't swap the cable data from/for other device, any of them have its own type of connection, use the same proper cable data for only one device.
From there the typical first step in fastboot is just typing
Code:
fastboot devices
], if the message is "waiting for device" then it's not working.
hi im having the exact same problem, but cant get out of this. Could somebody maybe help me? How did you eventually fixed it? kindregards