Develop Bugs

How to unlock bootloader on Note 2

Hi there,
This may seem like a daft question but i have just rooted my Note 2 using Odin and i went ahead and installed CWM from the play store.
However, i don't seem to have the option of making a backup of my current ROM.
All it gives me is (in blue)
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache.
This worked on my HTC One X, am i doing something wrong? My Note 2 was purchased as SIM free from phones4u.
I'm on android version 4.1.2, baseband version N7100XXDLK7, BUILD NO. JZO54K.N7100XXDMB2., MODEL NO. GT-N7100.
Could my bootloader still be locked? Is this causing the issue?
Any help would be much appreciated!

Just flash CWM/TWRP recovery.
Here is one of it
http://forum.xda-developers.com/showthread.php?t=2028103

Loading default android recovery even though TWRP successfully installed
Hi,
I am not sure if I should've started a separate thread for this, please move this if this has to be a separate thread but I've mentioned below why I am posting here.
My phone Galaxy note 2 International version GSM is rooted and I installed TWRP through Goomanager and I got a message stating that "Recovery was successfully installed". After this I shut down the phone and pressed Volume up + Home + Power to go into recovery mode and it still goes into the Android default recovery mode. I tried installing it again and still faced the same issue.
Since I was having a problem, I thought I will install TWRP through Odim 3.7. So, I connect PC to my phone and downloaded the openrecovery-twrp-2.3.1.1-n7100.img.tar.md5 and opened Odim in administrator mode and clicked on PDA >> Start. Within a second I got an error stating "odin downloader has stopped working". I went to task manager and shut down Samsung KIES and tried again but still got the same error.
Next, I tried using the Samsung Note 2 Toolkit. Before I installed TWRP through option 5 in the toolkit, I wanted to Rename Recovery Restore files (if present) as suggested by the toolkit. When I chose this option, I get an error stating adbd cannot run as root in production builds. When I googled this error, it went to a post which said that the bootloader needs to be unlocked.
But then the previous post says that I need TWRP for unlocking the bootloader and I'm doing all this to first of all install TWRP.
Apart from this, as additional Info, when I open ROM Manager - Under Recovery Setup - Current Recovery is Team Win Recovery Project. When I choose to reboot in Recovery mode from the application, it goes to the Android System Recovery. No matter what I do, TWRP recovery just does not seem to open up.
I'm pretty clueless now as to what other options I have or if I have messed up somewhere
Any suggestions would be appreciated.
Thank you

its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733

yahyoh said:
its already unlocked :good:
all u need costume recovery ( TWRP or CWM )
TWRP is far better IMO
http://forum.xda-developers.com/showthread.php?t=1938733
Click to expand...
Click to collapse
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.

gr8one said:
Hi yahyoh -
The problem as I've described in my post is that I am unable to go into TWRP Recovery mode, I've installed the scripts using goomanager several times but when I shut down the phone and press volume up + Home + Power, it goes to Android Recovery mode and not the TWRP Recovery mode.
Click to expand...
Click to collapse
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
{
"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"
}
( and make sure kies is fully closed )

Tried that
yahyoh said:
ok forgot goomanager it never worked for me
just download the tar version open odin put it in PDA put ur note 2 in download mode and connect it to ur pc wait for the blue color to show on ID:COM and press start
( and make sure kies is fully closed )
Click to expand...
Click to collapse
Yahyoh,
Thank you for your response but if you see my original post, I have mentioned that I had already tried Odin 3.7 and put my phone in download mode and got the blue color showing ID: COM but when I pressed start, Odin gave an error stating odin downloader has stopped working and the only dialog box was to close. So, once I press START, I get a error message in a second and have to shut down. I did make sure that I have the correct tar version as I downloaded from TWRP's website directly for N7100. I did make sure that Kies was also closed.
After this I tried using Toolkit and that didn't help as well. Kinda going crazy why such a simple thing is getting to become a irritating problem, been sitting on this for the past 4 hours.

try to run odin as administrator

ran odin as administrator
yahyoh said:
try to run odin as administrator
Click to expand...
Click to collapse
Yes. I did run odin as administrator all the time.

try on another PC ? try to download odin again ? try another cable ?

yahyoh said:
try on another PC ? try to download odin again ? try another cable ?
Click to expand...
Click to collapse
I have tried downloading odin 4 or 5 times. The cable I have is brand new samsung cable. Right now, I dont have another pc but might have to go to a friends and try if that helps. I do have a mac but not sure if there is mac version of odin. I'm attaching a picture of what I see when I press volume up + home+power.

abhijitdroid said:
Hi,
1. Check that USB drivers are properly installed.
2. Your USB cable is proper and allows you to charge your phone as well as copy data from your PC.
3. Change USB port and try again. (This has worked in my case)
Click to expand...
Click to collapse
Usb drivers are installed properly. PC reads the phone as soon as itd connected. Tried three different usb ports that is available in my laptop. The phone does get charged when it's connected and I'm able to transfer data. Only thing left to try is a different pc.

Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;

Nazar78 said:
Since ur already rooted, y not flash via mobile odin app? Untar to internal storage and rename the twrp image to recovery.img (btw theres a newer v2.5.0.2) and let mobile odin look for it.
Or u can dump the image directly to ur recovery partition using terminal apps:
Code:
su;
dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p9 bs=4096;
sleep 5;
reboot;
Click to expand...
Click to collapse
Hi Nazar78,
Mobile odin app is not free, it needs to be purchased. I already have the twrp image in the internal storage and was looking around if there was a free version of mobile odin app somewhere but couldn't find it.
I do not know how to use terminal apps and not familiar with the commands etc. So didn't wanna try that and mess it up. As a temporary solution I have installed CWM latest version using Rom manager but TWRP would be much better as it seems to be more user friendly.
If you could tell me how to enter this terminal apps page, I will probably follow the codes you have given and see if that helps.
Thanks

just install Android Terminal : https://play.google.com/store/apps/...251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
then type via keyboard what @Nazar78 wrote in the terminal

Just download any free terminal emulator app from play store and enter those commands per line each.
Btw u mentioned previously about adbd can't run on prod builds, its because the adbd binary in ur rom is stock, u need a patched one. Look for app called adbd insecure by CF. Or any custom builds should do the trick...

To flash recovery, tou need not to have paid version of mobile odin
Wait updating this post with link
Edit : here is mobile odin lite
http://forum.xda-developers.com/showthread.php?t=1347899
Download attached mobile odin lite from post 1
Then download flasher kernel from post 7
(download 5.0 versiin) and install
Then open mobile odin Select recovery tab, point to recovery file (tar/img) and flash
Sent from my GT-N7100 using xda premium

Thank you
Thanks Nazar78, Yahoyoh and Ketan, It's about 1:30am now, so I'm gonna shut down now and try these tomorrow. WIll get back with updates. Appreciate.

Also if you have installed EMET, a Microsoft software to stop security exploits, disable it.
It's cause me issues in the past.

I've also seen reports of people not having odin running properly when the kies process runs in the background. This was always the case when flashing with the Galaxy s, and might be a rare occurance with the note 2 too.
Sent from my GT-N7100 using Tapatalk 2

[Find7] [X9077] [X9076] Gummy TWRP 2.7.1.0 Based + Easy ROOT Method

Install Gummy TWRP 2.7.1.0 Based Recovery on Oppo Find 7 (X9077/X9076)
Warning: Note: No one but yourself is responsible for what you do to your device.
X9077 = Chinese TD-LTE support // X9076 = EU FDD-LTE or US FDD-LTE support
Requirements:
Download / unzip the file --> AndroidSDKSlim.zip
Download this file --> Gummy-TWRP-2.7.1.0-find7.img
Make sure you have a charged battery (50 % minimum)
How to install:
Connect your phone to your PC. You should see a window with the drivers in an application called 'setup.exe '.
Start the installation process and wait until it ends. then disconnect the phone from the PC.
Extract the contents of the file ' AndroidSDKSlim.zip ' on your desktop. You should have a folder named ' android-sdk-windows ' where there is another folder: 'platform-tools.'
In this folder, move the .img files you downloaded ( Gummy-TWRP-2.7.1.0-find7.img)
Turn off your mobile.
Restart your mobile in fastboot mode by pressing the High Volume + Power buttons until the appearance of the word ' Fastboot ' .
Connect your phone to your PC via the USB cable.
In platform-tools folder 'with your mouse, do' right click 'while holding down the 'Shift ' button, then select ' Open a command window here . '
In this window, type the following code to verify that your device is recognized.
Code:
fastboot devices
Then type the following command to install the TWRP :
Code:
fastboot flash recovery Gummy-TWRP-2.7.1.0-find7.img
Do not reboot your phone, but just flash the "UPDATE-SuperSU-v2.01.zip " to gain root !
How to root :
Just download the attached file --> UPDATE-SuperSU-v2.01.zip
Copy/paste it on your memory phone
Reboot into recovery mode
Flash the file & next reboot your phone
Enjoy ! You're root !
Note: If don't work, try the " [11-07-2014 UPDATE Thread] How to get ROOT with ColorOS v1.2.3i on X9076/X9077/X9007/X9006 " section from this THREAD
Credits & Thanks
papi92
Team Gummy
Chainfire
dhacker29
EthanChen
Your feedback is welcome​ ​

Fantastic!
Great news!
Thanks for the instructions. Can anyone confirm if this works on the Find 7 X9076?

Just tested and it works great [Find 7 X9076].
Recovery and root access. Done!
Thank You. :good:

I can load the recovery, but as soon as I press Volume + or - within the recovery I have the following error message:
E:touch_calibrate: EVIOCGABS failed
From there on, if I initiate the touch screen UI by touching any part of the screen, I can no longer use Volume +/- and Power button combination properly. as soon as I use any of those button, it just automatically launch the first option that is on whatever the recovery menu is.
Am I the only one having this issue?

Thank you. This worked. (Find 7 X9076)
kingcedz said:
I can load the recovery, but as soon as I press Volume + or - within the recovery I have the following error message:
E:touch_calibrate: EVIOCGABS failed
From there on, if I initiate the touch screen UI by touching any part of the screen, I can no longer use Volume +/- and Power button combination properly. as soon as I use any of those button, it just automatically launch the first option that is on whatever the recovery menu is.
Am I the only one having this issue?
Click to expand...
Click to collapse
Same here. Got the error, unsure if I had exactly the same problem as you.

binaryfalcon said:
Thank you. This worked. (Find 7 X9076)
Same here. Got the error, unsure if I had exactly the same problem as you.
Click to expand...
Click to collapse
can you try use go into the recovery, use the touch screen on any of the option, then try volume+ or volume - or power button? when I do that, it just automatically press the 1st available option on the menu.

kingcedz said:
can you try use go into the recovery, use the touch screen on any of the option, then try volume+ or volume - or power button? when I do that, it just automatically press the 1st available option on the menu.
Click to expand...
Click to collapse
Confirmed. Seems like I went through the same problem, since it selected reboot twice earlier.

binaryfalcon said:
Confirmed. Seems like I went through the same problem, since it selected reboot twice earlier.
Click to expand...
Click to collapse
ok thanks, at least that is consistent between phones. Unfortunately i m not smart enough to do any fixings, hope this get highlighted and resolve in the future version of the recovery.

Yeah, it's still early though. Just glad it's working this well.

Hi,
Worked fine for me, thanks for the clear easy to follow guide. I noticed the error E:touch_calibrate: EVIOCGABS failed on the screen but all movements in the recovery seemed fine, I used physical keys first then tried the touch screen and that worked too.
At the end of the process it asks if you want to prevent the ROM from flashing the default recovery, I choose yes. Might be worth adding that for completeness as some people might be unsure.
{
"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"
}
---------- Post added at 09:54 PM ---------- Previous post was at 09:37 PM ----------
Just been back into the recovery to do a backup. Which ever button you press you get the error but all the buttons work fine. This sounds like a daft question but you are not getting the buttons back to front are you. On the Find 7 the volume buttons and power buttons are reversed to a lot of phones and it's easy to press power instead of volume.
Sorry if this is not the case. It's just it seems to respond to everything for me and that might explain why you were entering on the first option. Could you double check?

worked for me too

Works great on X9076, thanks OP!:good:

after that we must return to stock recovery if we want to update via ota?

No. I received an update yesterday when I reverted to.colorOS but kept the gummy recovery
Sent from my X9076 using XDA Premium 4 mobile app

Worked on the X9077 too but it didn't recognise my exFAT formatted external card...
Also, like TWRP, it's half size.... Which proves it's not the size but how you use it that matters...:laugh:

ultramag69 said:
Worked on the X9077 too but it didn't recognise my exFAT formatted external card...
Also, like TWRP, it's half size.... Which proves it's not the size but how you use it that matters...:laugh:
Click to expand...
Click to collapse
lol it's the true
Tks for your feedback . Try with another external sd card...

scumpicule said:
lol it's the true
Tks for your feedback . Try with another external sd card...
Click to expand...
Click to collapse
I think it doesn't like exFAT, FAT32 seems to work ok but that seems silly to me to have a kickass hd screen and not use it with hd movies...

Stock Recovery
How can I backup my Stock recovery image before flashing this. Or is the Stock X9076 Recovery already available for download?
Can official Oppo Stock Roms (ColorOS 1.2.1i for example) be installed with this recovery?

Fasboot not working
which system did you use it?
- I tried to Windows 8.1 x64 with USB 3, and I could not find the find 7 (x9076). No detect the phone.
Do you have any idea, how I can use it?

gazsyka said:
which system did you use it?
- I tried to Windows 8.1 x64 with USB 3, and I could not find the find 7 (x9076). No detect the phone.
Do you have any idea, how I can use it?
Click to expand...
Click to collapse
Use Win 8.1 64bit too.
Make sure you are going to fastboot on the phone by pressing up volume +power until Oppo logo appears, release power but keep holding up volume, you should see fastboot on the screen...
Using the ADB files, make sure you open the files until you can see the .exefiles, it helps to have the file you wish to flash in there too, and hold "shift" key down while right clicking on white space in the window. Choose "open command window here".
Connect the Find 7 to the PC & type "Fastboot Devices" in command propmt. You should get a serial number and device found or something, if you don't try a new cable or usb port...
Once the phone has been detected type "fastboot flash recovery "the file name of the recovery.img", to make it easy, the file needs to be in the ADB file and after you type the 1st letter of the file you want to flash, press "tab" it will autofill the filename (just make sure you have different names for the files).
Then you can follow the other instructions with Supersu to get root....

My phone system deleted

Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21

ayadmanhal said:
Hi guys
Well I guess I ruined my phone , I rooted my honor 7x BND-L21 a couple weeks ago and it worked after I rooted it everything was fine and normal till I was stupid enough and went into the super su app and I saw the full uninstall super su so I was even more stupid to press it and thinking that I’m gonna be free from the root and I won’t have to be afraid that it getting wrecked which I did it with my own hands after I pressed the uninstall super su the phone went black and won’t reboot anymore so I linked the phone to my laptop and went into my internal storage I didn’t find anything but the TWRP file which means there are no more system or systems files what so ever that’s my sad story I hope that any one of you can help me and make a backup to there phone like mine and take the time to help me install it because I don’t know anything about these stuff and I’ll be great full for you guys for the rest of my life
Again My phone is a : honor 7x BND-L21
Click to expand...
Click to collapse
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.

mrmazak said:
There is , at this time, no suggestion for you to fix.
Because, you do not tell enough of what you were doing, or did.
I mean. First superSU does not work on updated device(Oreo) . So must be nougat, but you did not say.
Next , removeing superSU , from inside of it's settings, will not erase system.
Your description of connecting to PC with USB and not able to see any system files. Well you cannot see Android system files in this way anyhow. Add to that USB (mtp) does not wokif there is no system I place to run the adb/mtp service.
Well if you mean you uninstalled root/superSU , then tried to restart, and that made the black screen, well this is different completely to what you asked. And this makes sense.
If this is what you need. You just need boot.img, if you were in fact on nougat. Or ramdisk.img, and/or kernel.kmg if it was Oreo.
For l21, I do not have these.
Click to expand...
Click to collapse
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
{
"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"
}

ayadmanhal said:
bro .
i was playing a game in my phone and the game shot me out and i see the system apps deleted in the menu of apps
i trie restart phone when idid my phone stuck wont open the system but its redirect me to twrp recovery
when the twrp opened i connect my phone with usb to pc
and i see nothing in internal storage only the twrp files !
im find all backup files (IMGs) system.img and cus.img etc..
but idk how to install it
My android version is 7..0 nougat 5.1 emui
and sry for my bad english ..
Click to expand...
Click to collapse
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!

I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img

dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???

crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE

crayonicle said:
If you have all the needed files, just do this:
1. Boot into TWRP
2. Flash vendor.img, recovery_ramdis.img (Or something similar to that), and system.img
3. Flash them ^^^^ to the required partitions (Partition names to flash to should be self explanatory)
4. Do a factory reset
5. Reboot
Report back please if this works!
Click to expand...
Click to collapse
i did everything but nothing changed
ihave installed all IMGs
nothing happened and my phone still empty !
i trying to flash [OpenKirin's RROS ] room
it says succes but when im reboot still rebooting into recovery mode {twrp} 3.1.1.0
and my storage still empty
idk what i have to do
im think we have nothing to do !?

dutyyaknow said:
I have the exact same problem as OP. When I go into TWRP and mount an img or zip, there is always an error message saying
"Unable to find partition for path '/system' ". /system also doesn't show up anywhere else. . .
I tried your suggestion too but to no avail.
I don't know what to do anymore.
Edit: Now I can’t even get into TWRP after trying these 5 steps. All it shows me is the bootloader screen but with error messages.
“Please update the system again”
And at the bottom of the screen something about the boot.img
Click to expand...
Click to collapse
i think we loose our devices <\3

crayonicle said:
If you're talking about my suggestion, then please quote me next time.
Also, are you sure you have the right twrp installed?
When in bootloader mode, connect your device to adb. Does you device get recognized when you type "fastboot devices" ???
Click to expand...
Click to collapse
ayadmanhal said:
i think we loose our devices <\3
Click to expand...
Click to collapse
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.

dutyyaknow said:
There has to be a way to fix it from fastboot mode.
If everything fails, we can still try to send it to a Huawei Center to get fixed. Just don't tell them that you rooted or unlocked your device. I heard that they will then switch out the motherboard for a new one.
Click to expand...
Click to collapse
we cant go to huawei center bcz the phone unlocked and rooted
so the phone has no Guarantee and they will see the boot when says the device is not trusted <\3

After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP

dutyyaknow said:
After reflashing my old TWRP from fastboot, I can now access TWRP again and /system partition is showing up too. The ERROR MODE screen still shows up when I boot the phone with VOL + and POWER but when I press VOL + - and POWER I load into TWRP
Click to expand...
Click to collapse
my device only auto booting for twrp nothing more

up

no help :\

ayadmanhal said:
no help :\
Click to expand...
Click to collapse
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk

RSGI said:
Do you have ADB support on TWRP mode?
If so just use dd command to flash stock boot.img.
Try it by fastboot if you can.
You need to flash stock boot.img because rooting patches boot image and you tried to unroot but were unable to reboot that would replace the patched boot with the stock one.
If i undetstood the issue correctly...
If not, please enlight me...
Enviado do meu Le 2 através do Tapatalk
Click to expand...
Click to collapse
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files

dutyyaknow said:
Thank you for helping out.
Yes, I tried your suggestion and I used version 3.1.1.0 of TWRP.
Unfortunately it looks like my device is not getting recognized in adb anymore. All I get is either the screen where it says "booting your device now" forever or the white ERROR MODE screen with "Attention! Please update system again.
There are two error messages at the bottom of the screen :
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Now, how do I save myself out of this? It looks like I can't do anything. . .
Edit: correction, it does get recognized in adb in fastboot mode. Can I just flash your suggested TWRP from there?
Edit2: tried to flash the complete_twrp_ramdisk.img in fastboot mode with fastboot flash recovery command. Then I rebooted but instead of TWRP it still shows ERROR MODE
Click to expand...
Click to collapse
Have you re-flash with Huawei Multi Tool, but first you must have file update.zip and extract update.app from http://pro-teammt.ru/firmware-database/?firmware_model=BND&firmware_page=0
---------- Post added at 06:48 AM ---------- Previous post was at 06:41 AM ----------
ayadmanhal said:
i trie much of boot.img files but no change
i tried everything but the phone still wont read the system files
Click to expand...
Click to collapse
you on Nougat? have try to upgrade to Oreo from this thread,
https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
there's maybe can fix your system file

Question Xiaomi K40 Became A Brick

Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!

Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!​
Thanks to VD171 for his post.

I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.

Learn more about it in this video

reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?

mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.

no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked

reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know

khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}

last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine

ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"

reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)

Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual

Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.

Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.

reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.

if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp

Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.

He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick

Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.

Question Red Warning and UnWorking Lockscreen. HELP

{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)

Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...

redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?

Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely

i have this error also what should i do?
the phone not boot up
the red warning are stuck

yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.

[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!

yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.

[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much

yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!

turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"

izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!

[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.