Hey everyone.
After recently hard-bricking my Google Nexus 7 2012 (nakasi/grouper) I managed to unbrick it using NvFlash. As the official guide only taught us how to back up the blob files, I had to experiment a bit.
So, after only a few hours of messing with NvFlash commands, I found a solution to unbrick the Nexus 7 by reflashing the bootloader.
IMPORTANT! This guide requires that you have already made a back up of your device's blob files by using AndroidRoot.Mobi's tutorial, located here: http://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Step 1: Download and Install the APX Drivers
From a powered off state, connect your hard-bricked Nexus 7 to your computer, then hold down the power and volume-up buttons until your computer recognizes your device.
Download and extract the Universal APX Drivers package from the download section below. Open the Windows Device Manager, right-click on anything that resembles your Nexus 7 or an APX device and click Update Driver.
Instruct Device Manager to search for drivers in the recently extracted driver folder.
If Windows displays an error while installing the drivers, you may need to disable Driver Signature Enforcement via Windows Startup Settings.
Step 2: Set Up NvFlash
Download and extract the NvFlash package from the download section below. Open a terminal window in the recently extracted NvFlash folder. Ensure your Nexus 7 is in APX mode (power and volume-up).
Type "wheelie --blob blob.bin" without the quotes. If necessary, replace "blob.bin" with the location of your Nexus 7's blob.bin file.
NvFlash should now load, and the Google boot logo should appear on your Nexus 7.
Step 2.1 OPTIONAL: Boot the system
To test NvFlash's connection with your Nexus 7, type "nvflash -r --download 5 eks.img" without the quotes. If necessary, replace "eks.img" with the location of your Nexus 7's blob.bin file. Your Nexus 7 should reboot into the ROM you previously had installed. Just keep in mind this is a temporary way of bypassing the bootloader to boot the system; the device is technically still bricked.
Step 3: Flash the bootloader
Type "nvflash -r --download 4 bootloader.img" without the quotes. Replace "bootloader.img" with the location of the bootloader found in any Nexus 7 stock factory image. NvFlash will flash the bootloader and boot to Android.
Step 4: Access the bootloader
By now, your Nexus 7 should be unbricked. However, to be on the safe side, I recommend that you reboot into the bootloader and flash whichever factory image you find to be the most stable.
Congratulations! If you completed the above steps and are able to access the bootloader, you have successfully unbricked your Nexus 7. I recommend that in order to prevent hard-bricks in the future, make as many backups of your "blob.bin" and "eks.img" files as you can. Keep them on multiple disks, upload them to the cloud, share them with your Facebook friends or even burn them to a CD. You cannot complete the above steps without them.
See you next time.
too bad I dont have a backup of the blob files. Is there a workaround for this? my nexus 7 is stuck on Erasing and I cant access bootloader no matter how I tried. Erasing is stuck no matter how many hours. It's stuck in erasing until its drain and when I full charge it and turn it on, it goes back to that.
too bad I dont have a backup of the blob files. Is there a workaround for this? my nexus 7 is stuck on Erasing and I cant access bootloader no matter how I tried. Erasing is stuck no matter how many hours. It's stuck in erasing until its drain and when I full charge it and turn it on, it goes back to that.
Click to expand...
Click to collapse
As long as the device displays something on the screen, it's most likely not bricked.
Could you please post a screenshot of what's showing on the Nexus 7's screen, and tell me which version of Android you were using?
I am using the latest 5.1 image from google. I just factory resetted. The screen stayed with android mascot on the center and label "ERASING" but man hours has passed to the point of loosing battery but can't get pass through it. Upon loosing battery, it goes back to "ERASING". I cant still charge offline but if I turn it on it goes back to "ERASING" also. If in that screen I press UP+Power, it shows "Formatting /data" but it is stuck there.
Here are the Pictures:
{
"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"
}
Are you able to access the bootloader? Try turning off your Nexus 7 and holding down the power and volume down buttons.
You should see a screen like this:
Before I can access that but now I can't. Everytime I try to hold power button to turn off it will reboot instead. If I try to hold vol down +power button before google logo appears, theres no effect
From recovery mode, hold the power button until the screen goes blank, then immediately release the power button. After that, immediately hold the power and volume down buttons BEFORE the Google logo appears.
This is because the bootloader is a low-level part of the device, and appears before anything else.
If you wait until the Google logo appears before holding the volume down button, it will have been too late, and you'll need to try again.
Calvin Hogg said:
From recovery mode, hold the power button until the screen goes blank, then immediately release the power button. After that, immediately hold the power and volume down buttons BEFORE the Google logo appears.
This is because the bootloader is a low-level part of the device, and appears before anything else.
If you wait until the Google logo appears before holding the volume down button, it will have been too late, and you'll need to try again.
Click to expand...
Click to collapse
yes that is what I am exactly doing. as soon as the screen goes blank i immediately press and hold power+vol down before google logo appears. After that all it does is either turns off again or go to that stuck ERASING part. I can do this on this nexus 7 before but now I can't. On my Nexus 5 I can do this trick to access bootloader
amnher said:
yes that is what I am exactly doing. as soon as the screen goes blank i immediately press and hold power+vol down before google logo appears. After that all it does is either turns off again or go to that stuck ERASING part. I can do this on this nexus 7 before but now I can't. On my Nexus 5 I can do this trick to access bootloader
Click to expand...
Click to collapse
You could try the following:
- Open the Nexus 7 by sliding a credit card around the edge, and pulling it open with a fingernail
- Remove the battery's connector from its slot and leave it out for at least an hour
- Reconnect the battery and immediately hold the power and volume down buttons (with the cover off they look like little grey circles)
Refer to the images below for the location of the battery and power/volume buttons.
I have the same problem with my nexus stuck on APX mode . Bad news is i dont have a backup of the blob files... Is there another way to use your backup or something similar ?
adybaesu said:
I have the same problem with my nexus stuck on APX mode . Bad news is i dont have a backup of the blob files... Is there another way to use your backup or something similar ?
Click to expand...
Click to collapse
Bad news for you: No, there is no chance. Either you've created 'your' blobs before or ...
Calvin Hogg said:
You could try the following:
- Open the Nexus 7 by sliding a credit card around the edge, and pulling it open with a fingernail
- Remove the battery's connector from its slot and leave it out for at least an hour
- Reconnect the battery and immediately hold the power and volume down buttons (with the cover off they look like little grey circles)
Refer to the images below for the location of the battery and power/volume buttons.
Click to expand...
Click to collapse
Ill try that but you think that the volume down button can also be busted resulting not able to enter fastboot?
I did not get this problem mine was that I was getting the Supported API:3 loop and could not get into the bootloader to do anything. It may be that the answer I found may help you and other as I was at my wits end finding dead end fixes that did not work.
I had my problem with two Nexus 7 2012 tablets and have recovered them both this way.
While in the 'Supported API:3 ' loop ADB is loaded so you need to have the ADB/Fastboot drivers installed and working.
With your device attached to your PC go into the command prompt and type 'ADB Devices' without the quotes of course and hopefully it will show the ID of your tablet.
If it does then just Type' reboot bootloader' and it should boot into the bootloader.
Now you need to see if fastboot is working so type 'fastboot devices'. Again it should show you the ID of your device.
Download the latest stock update and extract the files. For the latest Nexus 7 2012 you will find the bootloader image file called 'bootloader bootloader-grouper-4.23.img'.
Type 'fastboot flash bootloader bootloader-grouper-4.23.img'
This will make sure you have the correct bootloader installed. Now type 'fastboot reboot-bootloader'
Your tablet should now boot into the bootloader again with no problem. To flash the stock image then type 'flash-all.bat' or if you wish type 'fastboot -w update image-nakasi-lmy47v.zip' then when that has finished type
'fastboot reboot' and set up your tablet again.
If you have problems make sure you have a good USB cable, the proper ADB/fastboot drivers installed and it has been suggested not to use a USB 3 port.
The only other trouble I had with one of my tablets was that when it rebooted it said that my data was encrypted or currupted and I had to enter my google password and once I found that fastboot did not work. I ran ADB devices and it found my tablet so I ran fastboot devices and it was ok then.
I could not get ADB to work at all in Windows 10 so I used Linux instead which does not need the drivers but does need the ADB/fastboot repository installed.
I installed VirtualBox on my Windows 10 laptop and installed Peppermint Linux in VirtualBox. This enabled me to get booted into bootloader on both occasions.
I realise that my problem was not the same but I hope at least it points you to a solution and you finally you have as good a result as I have and that this helps you.
I think I'm missing something. Does this also restore data, because i assumed the easiest way was to use Wugfresh's root toolkit, and that does the lot.
My Nexus 7 was stuck in APX, I got the driver on it. As I have a second (working) Nexus 7 could i use the blob files from the second tablet and how should I progress in your tutorial?
Hi. My Nexus 7 was in bootloop so tried installing the stock firmware through the Nexus Root tool. The version was correct and so was the USB connection but it somehow got stuck in Installing Bootloader part for quite some time. I rebooted it and there was no display after that. I have the bootloader image from the stock firmware but can't install it as the Nexus Root Tool is not recognizing it as fast boot device. Is there a way to get it working? Thanks
@sam214 nvflash is working for the Nexus 7 only if you have extracted your device specific binaries before. In that case you can restore the device with that binaries and get it running again. You cannot flash the extracted bootloader from the factory image with nvflash.
AndDiSa said:
@sam214 nvflash is working for the Nexus 7 only if you have extracted your device specific binaries before. In that case you can restore the device with that binaries and get it running again. You cannot flash the extracted bootloader from the factory image with nvflash.
Click to expand...
Click to collapse
Is there any way to unbrick without blobs?
TheDarkKnight said:
Is there any way to unbrick without blobs?
Click to expand...
Click to collapse
As far as I know: no, there is no way if your device is really bricked i.e. starts into APX mode only.
If the device does not start at all there is also the chance that "only" your battery power is too low ... so low that it does not even charge within the device. In that case there is the chance to revive the battery (there are several videos and instructions about that) if you are lucky.
AndDiSa said:
As far as I know: no, there is no way if your device is really bricked i.e. starts into APX mode only.
If the device does not start at all there is also the chance that "only" your battery power is too low ... so low that it does not even charge within the device. In that case there is the chance to revive the battery (there are several videos and instructions about that) if you are lucky.
Click to expand...
Click to collapse
My device only boots in APX mode So theres no way? What if I use blobs from someone with the same device?
Related
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
Please excuse my lack of knowledge I am a complete beginner.
My wife left her working Asus k013 (do not know which model as I no longer have box) on charge over night, next day it would no longer get beyond the boot screen. We are stuck with the Asus Logo and the revolving boot start symbol.
I have tried the start/volume up and start/volume down options to do factory reset but just returns to the boot start. If I hold the buttons down for a long time it just shuts down. I them tried downloading 'clear data' to sd card but this presumably requires the tablet to boot before it works.
I have purchased a new tablet for her so I do not want to send the tablet for repair but would really like to get it working as spare and to experiment with rooting etc. to try an improve my knowledge.
If you boot with Power + Volume Down (stop pressing power once the backlight turns on, but keep pressing Volume Down) does it boot into the Droidboot screen (with NORMAL BOOT, RECOVERY MODE buttons)?
Asus k013 stuck on boot
lambdadroid said:
If you boot with Power + Volume Down (stop pressing power once the backlight turns on, but keep pressing Volume Down) does it boot into the Droidboot screen (with NORMAL BOOT, RECOVERY MODE buttons)?
Click to expand...
Click to collapse
Thanks for trying but this still ends up trying to do a normal boot without completeing
593jim said:
Thanks for trying but this still ends up trying to do a normal boot without completeing
Click to expand...
Click to collapse
Did you install the Lollipop (Android 5.0) update on it when it was still working or were you still on KitKat (Android 4.4)?
Asus k013 stuck in boot
lambdadroid said:
Did you install the Lollipop (Android 5.0) update on it when it was still working or were you still on KitKat (Android 4.4)?
Click to expand...
Click to collapse
Not sure which release it is on. Received an OTA a while ago from the original when bought.
Upgrade was not recent so do not think that's it unless the OTA was done last weekend.
593jim said:
Not sure which release it is on. Received an OTA a while ago from the original when bought.
Upgrade was not recent so do not think that's it unless the OTA was done last weekend.
Click to expand...
Click to collapse
Huh, well. Do you get a "Fastboot starting..." screen if you press Volume Down + Volume Up + Power while turning the tablet on?
lambdadroid said:
Huh, well. Do you get a "Fastboot starting..." screen if you press Volume Down + Volume Up + Power while turning the tablet on?
Click to expand...
Click to collapse
Great we have a start, doing as you said has brought up 'Fast boot starting' then 3 lines #1, #2, #3 but does not move from there.
Thanks for your help so far, how do I proceed please.
Regards,
Jim
593jim said:
Great we have a start, doing as you said has brought up 'Fast boot starting' then 3 lines #1, #2, #3 but does not move from there.
Thanks for your help so far, how do I proceed please.
Regards,
Jim
Click to expand...
Click to collapse
Download http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip.
Install ADB+Fastboot on your PC. There are various guides available online for this, so you should google or take a look at https://wiki.lineageos.org/adb_fastboot_guide.html
Boot into that mode again and connect the tablet to your PC (via USB). On a command prompt, verify that...
Code:
fastboot devices
... displays a device. Extract "droidboot.img" from the ZIP you've downloaded in the first step, then run:
Code:
fastboot boot droidboot.img
Does it now show the "NORMAL BOOT" etc screen?
Asus k013 stuck on boot
lambdadroid said:
Download http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip.
Install ADB+Fastboot on your PC. There are various guides available online for this, so you should google or take a look at https://wiki.lineageos.org/adb_fastboot_guide.html
Boot into that mode again and connect the tablet to your PC (via USB). On a command prompt, verify that...
Code:
fastboot devices
... displays a device. Extract "droidboot.img" from the ZIP you've downloaded in the first step, then run:
Code:
fastboot boot droidboot.img
Does it now show the "NORMAL BOOT" etc screen?
Click to expand...
Click to collapse
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Asus k013 stuck on boot
593jim said:
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Click to expand...
Click to collapse
Sorry, should have added 'Fastboot device' no longer works.
May need to go back to my friend for help.
Can't see how to attach the photo.
Regards,
Jim
593jim said:
Sorry so long to get back, I got help from a friend over the weekend but we did not succeed.
Had another go today and got to normal boot. Tried to go to recovery and got failed. Volume down offers 'power off' 'recovery' and restart bootloader.
I have attached a screen shot, the last line shows
E: No valid installer medium found.
I seem have a problem with the files I downloaded to my computer have the 'user/adb-fastboot/' file but cannot find the bring up the tools extention.
Regards,
Jim
Click to expand...
Click to collapse
Sorry, this might have been confusing but I didn't post all needed steps yet. I just wanted to make sure you actually get to the droidboot screen.
Since you managed to get there, this is what I recommend: Use https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 on the "NORMAL START, RECOVERY MODE" etc screen to get into a temporary recovery session. For this tablet you should use trigger T4 and TWRP portrait. Copy the UL-K013-WW-12.10.1.36-user.zip you already downloaded to a external SD card first.
Once you are in recovery, you can try flashing the ZIP. This might restore your system to a usable state.
As for fastboot devices not showing any device: On Windows you may need to install the right USB drivers to make it work properly. You can try the Universal ADB drivers available from https://adb.clockworkmod.com/ or the USB driver provided by ASUS http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip. I cannot help you with this because I'm not using Windows much myself.
Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia
---------- Post added at 06:46 AM ---------- Previous post was at 06:40 AM ----------
Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
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.
Hello fellas,
The other night I got frustrated over some bugs on MIUI 13 on my RN10 5G and decided to install MIUI 12.5. I did everything right and the FW downloaded from miuirom.com. It's EU, It's the correct, but it wouldn't boot.
Decided to flash PE, because I've used it and it was cool and all, but when it finished, I did the usual - Recovery-Wipe Data-Reboot.
Here's the problem - it took more than 15s on the Redmi boot screen (before it took less than 10s) and after that it restarted. OK, maybe something went wrong. After restarting it boots to a black screen, stays on it for about 3-5s and restarts again. Cool, it's in boot loop. But it doesn't display the boot screen, can't access recovery and holding for recovery immediately halts the phone and it turns off.
My question - other than getting a new phone, is there a way to... like, un-brick the phone?
Something a bit useful might be, that I've used a VNDKLite version of PE, and if I understood right, it partitions the phone in some weird way, to keep the vendor's data and the OS separately. Maybe this is causing it? I don't know.
P.S. If there is something with solidering, like changing the Flash Memory chip, I'm out...
Here are some steps you can take to try to fix your phone:
Try to enter recovery mode: Depending on your phone model, you can try to enter recovery mode by holding down a combination of buttons. Once in recovery mode, you may be able to reset your phone to factory settings, which can help fix the issue.
Contact the manufacturer: If your phone is still under warranty, contact the manufacturer for support. They may be able to provide a solution or offer a repair or replacement
Seek help from the developer community: If you installed PixelExperience through a custom ROM, try seeking help from the developer community on forums or social media. They may have experience with similar issues and be able to provide assistance.
Consider professional repair: If none of the above options work, you may need to take your phone to a professional repair service. They may be able to diagnose and fix the issue, but be aware that this can be expensive.
In any case, it's important to be cautious when installing custom ROMs on your phone, as they can potentially cause issues if not installed correctly. Make sure to research thoroughly and follow instructions carefully to minimize the risk of bricking your phone.
@timjohnson2584 Thanks for the help! That's also a quick update.
So, the first one, I literally cant enter recovery nor fastboot. Acidentally I've entered a secret menu, that gave me the option between Recovery, Fastboot and normal. VolUp to change choice and VolDown for confirm. I wasn't able to access it again, but it doesn't matter, because when I was in it, i chose fastboot and it restarted into the same boot loop. Second - the phone is unlocked, re-flashed with, i dont even know what anymore, and I've disassemble it to change the screen, so the warranty is no no. The 3rd - nothing personal, but "...that's why I'm here". Fourth - I don't really have the finances for a technician and just want to repair it @ home, sooo...
Thanks anyways
Again, a quick update!
I found out that the menu i have accessed may have been the weirdass BROM menu, because after some search I've found out how to enter it. When the screen lights up, hold PWR and VolUp, till the screen turns off, and then immediately hold VolUp and VolDown. When screen lights up, no matter what it enters the mode. Sadly, just hanging there doesn't give me access trough adb nor fastboot and if i choose fastboot it restarts. But if it's normal or recovery, it vibrates, freezes, disappear and halts.
Hey guys, another quick update that might frustrate some people. I've left it for the night to boot-loop reboot and stuff and today when I tried powering it up, it wouldn't show signs of life. When connected to this PC, from which I'm sending this, and hold any combination of buttons, it shows in the Comp Mgmt for a brief second as COM3 Serial Port. That's cool, at least its recognizing it, but if before there was at least backlight on the screen, this time it's fully blank - no picture, no backlight, no sh*t. If someone asks, the weirdass way Xiaomi did it is the phone's daughterboard for charging is connected to the screen, AND THEN it all connects to the mainboard. If it chargin', then it ain't disconnected - that's how I look at the situation. :/
P.S. Also, I don't think it's a problem, but I've disconnected the speaker and vibrator motor, so I can sleep peacefully.
someone here has had a similiar issue with you but differently recovered without using brom
anyways, i took a glance at your issue, seems like you are still in brom right?
install MiFlashPro, you will need it to fill the Download-Agent in sp tool (see what the spaces means below)
then, download any miui rom from any website (my favorite is mifirm.net, it downloads faster)
extract the rom folder. now open sp tool.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
{
"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"
}
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
After it is finished and was successful, now go back to sp tool, and click "Download" asap.
Now wait for it to flash, maybe 5-15 minutes, and some time to boot, and done, your phone is alive again.
if anything didnt work post about it asap so i can help
(ps: if you get this, its a easy procedure to repair your bricked mtk, and you will get used to it quickly)
OK, thanks, I'll try that. But just to ask, do I have to stay in this BROM mode with options on blank screen while doing this, or select fastboot, recovery, normal first?
bg0169 said:
OK, thanks, I'll try that. But just to ask, do I have to stay in this BROM mode with options on blank screen while doing this, or select fastboot, recovery, normal first?
Click to expand...
Click to collapse
well, not necessarily. only when you get to the bypassing, because brom will automatically restart if theres no command taken in a few seconds
OK, now I have a problem. All my programs are ready, the phone is in BROM mode, but the PC is not recognizing it. It's not from the cable and it doesn't appear in Device Manager.
bg0169 said:
OK, now I have a problem. All my programs are ready, the phone is in BROM mode, but the PC is not recognizing it. It's not from the cable and it doesn't appear in Device Manager.
Click to expand...
Click to collapse
Wait a few moments, i think i have the mtk brom drivers for it, sorry for the wait
No problem, have your time
bg0169 said:
No problem, have your time
Click to expand...
Click to collapse
There you go its attached, try them. Should work
OK, update again, again, again... Now I even have a picture on my phone in BROM mode and what's happening even with the drivers from above:
Down there is the phone and on the screen is SP flash ready in the background and the MTK bypass tool. Also, PLEASE don't question the webcam, I know
Also here is what the Dev Mgmt sees. It's not showing even as serial port (the COM3 port from which it showed during the bootloop)
bg0169 said:
OK, update again, again, again... Now I even have a picture on my phone in BROM mode and what's happening even with the drivers from above:
View attachment 5860261
Down there is the phone and on the screen is SP flash ready in the background and the MTK bypass tool. Also, PLEASE don't question the webcam, I know
Click to expand...
Click to collapse
BROM mode is not that!
BROM is accessed by pressing down VOL+, VOL- & POWER all at the same time when device is turned off or rebooting, while connecting it to the pc, and BROM does not display anything, not even the LCD lights up, you just got to know whenever it is in BROM by your computer
Let the device reboot (select any mode from the list), and right as it reboots, press down all of the buttons, and connect the phone simultaneously.
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
bg0169 said:
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
View attachment 5860273, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
Click to expand...
Click to collapse
press the "disable auth" button, and then connect it into BROM again, then it will bypass normally
it restarts because its not receiving any command, its normal
OK, I'll try it out in a moment... Thanks!
OK, even if u want, I have a screen capture. I open the tool, click bypass, connect the phone, and hold all the buttons. BUUUT it just keeps connecting and disconnecting. Always! Even with the drivers! Restarted my PC, same s**t! Now I'm pissed off a lot! Are you sure this is the only way, am I doing something wrong? I saw your "How to Guide" thread and followed everything and it's the same.
bg0169 said:
OK, even if u want, I have a screen capture. I open the tool, click bypass, connect the phone, and hold all the buttons. BUUUT it just keeps connecting and disconnecting. Always! Even with the drivers! Restarted my PC, same s**t! Now I'm pissed off a lot! Are you sure this is the only way, am I doing something wrong? I saw your "How to Guide" thread and followed everything and it's the same.
Click to expand...
Click to collapse
i see the problem
its the driver. well, not exactly the driver
it seems like its a issue from the phone's side. but its normal! it also happens to me every time i try to bypass it
bg0169 said:
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
View attachment 5860273, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
Click to expand...
Click to collapse
just like you show here, the port is not working (error symbol), so clearly it cant detect the phone to be able to do any commands
i tried bypassing to see just now, and yes, it also shows the same problem as you, the error symbol, however if you have the patience to retry lots of times, trying to bypass it, then its the solution for it.
what you can try is just keep bypassing lots of times till you get it.. thats it, i hope