Database Develop

[stock rom][3.0.1] P7100BUKDF + bootloader unlock

Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !

Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?

bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !

Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.

Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now

No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?

My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.

Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.

Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method

gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery

Added the SD-CARD wipe notice for ya

How do root this firmware ?
Thanks

http://forum.xda-developers.com/showthread.php?t=1079781 ?

any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.

Has anyone tried flashing with Heimdall in Linux?

As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.

Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).

I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.

The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!

Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?

[GUIDE] Return to Stock and Upgrade

Hey guys, I am new to this gear live dev and I want to help out. I just got my gear a few days ago and I'm still playing with it I figured that my device is at 5.0.1 and has Dev-Key in the build number. I went ahead and did some research (more than 35 hours) and came to a conclusion. I figured I can help a lot of people by posting my method here. I am currently on 5.0.2 and I am trying to figure out why I still did not get the 5.1.1 update. Looks like Samsung is slow and I will ask around if anyone got the OTA or I'll sideload the OTA scripts. Making the long story short.
Entering the bootloader (hard way)
Press and hold down the power button until your device reboots. Don't let go yet. As soon as you see the Samsung logo you have to swipe from the top left corner to bottom right corner really fast 2 times. Now let go of the power button and you should be in bootloader. If not keep trying again. I would recommend this as the last resort.
Entering bootloader (easy way):
Enable USB debugging by going to settings -> about device -> tapping build number 7 times. A new option should now show up under settings called developer options. At this point make sure that you have proper adb fastboot drivers. If not you can use the minimal ADB FASTBOOT 15 second Installer I will provide a link to the thread. Make sure that the watch is paired with your phone and keep the phone near you. Connect the watch to your machine via USB and let it recognize the device. Open a terminal or cmd window and enter adb devices. You will most likely be returned with some number and unauthorized. At this step if you get an error such like ADB is not an executable program then you have not installed ADB correctly. Switching over to your phone you will now see a debugging request from your watch. Go ahead and it always allow. Now you have granted debug permissions on you watch. Run the command again and this time, the device should return authorized. Run " adb reboot bootloader ". You will be taken to the bootloader.
Unlocking Bootloader and Flashing and relocking the bootloader:
The first step is to unlock the bootloader (don't know if this voids the warranty but I think it will). After you unlock the bootloader (fastboot oem unlock) WARNING: THIS WILL WIPE YOUR DEVICE and then boot back to the OS set it up and redo the steps under Entering bootloader. Once you have entered the bootloader you will need the stock os which is KMV78Y_stock. It is 4.4w and we will upgrade it soon. Open a cmd and run fastboot devices and you should see your device in the list. If not something is wrong , check if you have the right fastboot drivers and your watch is connected properly. Try a different usb port and don't use a usb HUB. ON WINDOWS extract the zip and navigate to the folder till you see the image files. Here shift+right click and you should see an option for open command windows here. For rest of the other people without windows cd to where the image files exist. Run the command “fastboot flash system system.img ” and “ fastboot flash boot boot.img ” . Once you have done that you will have to relock the bootloader. Relocking the bootloader is an important step to receiving further updates so I recommend relocking it. IF YOU DON'T RELOCK THE BOOTLOADER THEN YOU ARE STUCK ON 4.4W WHICH SUCKS SOOOO MUCH!!!!. Relock the bootloader by running “ fastboot oem lock “. Just keep in mind that you can re-unlock your bootloader after you have upgraded but unlocking bootloader will wipe your device again. *SIGH* I ALSO HATE READING LONG INSTRUCTIONS BUT YOU ARE ALMOST AT THE END!!!. After you relock your bootloader go ahead and swipe down on the screen until you highlight the recovery option and swipe right to select. Once you have booted into recovery you will see a warning sign. Don't Panic. Just tap on the screen and you will be brought to the recovery screen once again select reset and select yes.After the reset go ahead and reboot the device. You will be brought into the android wear stock os. Go ahead and set up your device again and go to the setting ->about device -> software updates. You will see that the update is available. There you go install the updates until you get to android 5.0.2. GREAT YOU HAVE UPGRADED YOUR WATCH. There a few ways to get to 5.1.1 but I have not tried them out. I will post the instructions as soon as I have tried it. If your watch says that there is an update the go ahead and install it. Samsung does not push the update to all users at once as it may kill their servers but roll the update out in batches. If you want to sit tight and wait till it comes through or I will be posting a how to soon.
UPDATING TO 5.1.1 AND TO 6.0
Hey, figured out how we can upgrade without waiting. It is actually really simple and easy. You will need to have a locked bootloader to do this or apply any stock update. It does not work with an unlocked bootloader. Your computer will not recognize your watch when sideloading if you have an unlocked bootloader. So let's get started. Download the ota update zip from the links below leave it in the downloads or move it wherever you want it. Open a terminal window or cmd window to the location of the zip either by shift+rightclick (only windows) or by cd’ing you way. At the location of the zip prepare your watch for sideloading. Reboot to recovery by commanding “ adb reboot recovery” or “ adb reboot bootloader” then going to recovery, or going to fastboot the hard way then to recovery. The choice is yours. Once you are in recovery select adb sideload. Now go back to your computer and hit " adb devices ". You should see your device and sideload. If not then something is wrong. Since you are already in the folder where the zip exists simply enter “adb sideload LIVE.zip” and it should send the file to devise. Don't panic if you interrupt the transfer. It will not apply the changes until the entire file has been transferred. Just redo the steps above to resend it. After the update is complete you can restart your device. Upon restart, you will see that your device has upgraded to 5.1.1. Congratulations. Now to go to 6.0 just go to software update and search for another update. I am starting to love this watch at what it can do in 6.0 so I suggest you upgrade.
Thank you, all and I hope this helped a lot of people out there.
Links:
Stock OS:
Android 5.1.1 OTA:
ADB AND FASTBOOT:
I will post inks as soon as I upload them.
-Soma

No Command/Device is corrupt/update

My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?

You might want to try flashing the update manually, using ADB and Fastboot. Doing so will wipe your device, so if you have anything in the internal storage, back it up if you can.

I try flashing manually via adb/nexus toolkit and it just says error code 7 on the phone. The device is bootlocked.

this may help
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660

Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.

I have no backup, the phone is under warranty and as this has happened before. Stock update killed phone, i'm taking it to vodafone today.
I can't be bothered to mess about when my contract comes with warranty

Good thinking...

Didgeridoohan said:
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
Click to expand...
Click to collapse
Exactly same problem, struggling for a day now.
unable to unlock bootloader for flashing the device
"fastboot flashing unlock" returns OKAY but the screen still shows "Device is LOCKED. Status Code: 2"
any suggestions??

Try "fastboot oem unlock".

Strephon Alkhalikoi said:
Try "fastboot oem unlock".
Click to expand...
Click to collapse
"fastboot oem unlock" gives:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
But of course I can't do that as I cannot get it to start. I tried "adb sideload image-shamu-mmb29x.zip" too, but it fails for signature verification probably because it shows I have "MMB29V" on the phone. Downloading "MMB29V" image now, will try that too.

With your bootloader locked, you cannot flash factory images using fastboot, and ADB is not for flashing factory images. You have to flash the Android N preview as an OTA in recovery to restore your device to an operable state. Once Android N finishes optimizing apps and is booted, you need to go into the hidden Development Options menu in Settings and tick "Enable OEM Unlock". Then you can unlock the bootloader in fastboot with the command " fastboot oem unlock" so you can flash factory images.

Aston Martin said:
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
Click to expand...
Click to collapse
Got into the same situation yesterday. Seems like it was not just a security update (it didn't say so though), but it was update for the Android-N preview.
Wasted a whole day trying to figure out what did I do to brick my phone. In the end it was just the stupid update by google.
The solution to the problem now is to update your phone to Android-N preview OTA update - you can get it from here: http://developer.android.com/preview/download-ota.html
aHR0cDovL2RldmVsb3Blci5hbmRyb2lkLmNvbS9wcmV2aWV3L2Rvd25sb2FkLW90YS5odG1s --> base64decode this to get the link [new users not allowed to put direct links ]
Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttobns (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb
Here OTA_UPDATE_FILE_NAME.zip is the name of the ota-update file you download from the developer.android.com link [given above as base64]. For Nexus 6 it is - shamu-ota-npc91k-201dd8d1.zip
Hope it will save someone a lot of their important time.

Well, I am having the same issue as OP. Stock Android on Nexus 6 (t-mobile), received OTA security patch last night. Checked that I have a little over 1GB storage left (24.90GB out of 25.98GB available) and proceeded with installation. Now it says "device is corrupt" and after the four rotating colorful circle animation it gives me the "Unfortunately, Settings has stopped" message box over and over again which I cannot get past. I tried safe mode and it hits the same error.
I am trying the manual OTA update now as ravikumr posted, but I suspect it may run out of storage space since the zip file is 855MBs. Any way I can go in and clean up some space before the installation?
If the reason the original OTA update failed was due to insufficient storage, that would be a really stupid way to annoy the user. I have been reasonably happy with my phone so far but this experience today sucks. I depend on the phone for a lot of things so I never tried to root it or modify in any way, but I guess that's still not enough to make the phone reliable.
I will post my results with the manual update.

Finding update package...
Opening update package...
Verifying update package...
Installing update...
Target: google/shamu/shamu:N/NPC91K/2751853:user/release-keys
Patching system image unconditionally...
Verifying the updated system image...
E:unknown command [retry_update]
system partition has unexpected contents after OTA update
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Anyone has suggestion I can try?

I couldn't wait since I needed the phone to work so I did factory reset. I had to do it twice since the first time it looked hung formatting /data (I waited over an hour) but second time it went through fairly quickly. Afterwards it was stuck on the google logo at boot, probably due to the bad system. I reinstalled the Android N preview OTA patch and it successfully completed this time, and I was off setting up the phone again.
I am still not convinced that what I have experienced was not a simple mistake that whoever put this package together forgot to put in code to check for available storage space before allowing the installation to proceed, or it could be a bug that when space ran out the installation code didn't handle it gracefully and started to do bad things. Either way it was a bad experience for me. Luckily I saved all my pictures and videos a week ago so only lost a few pictures plus other data.

I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks

Kam_El said:
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Click to expand...
Click to collapse
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.

mikeprius said:
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
Click to expand...
Click to collapse
This worked for me, specifically with the update issue on a fully stock and OEM locked Nexus 6 that became buggy after the update was attempted but there was not enough memory. After the update failed and it booted back up (there was an error your device is corrupt message on bootup) there were a ton of error messages and the settings app was broken. Package installer was also broken and Google play and media services were broken, therefore couldn't use the Wugfresh Nexus toolkit, couldn't use fastboot as OEM was locked and couldn't access settings to change it. Factory reset from stock recovery did not fix the errors and following bootup the startup wizard couldn't start either.
The only option was to sideload the OTA - however, for the Nexus 6, after the OTA installed the OEM unlock option was transparent and set at off (because my bootloader was always locked). I then enrolled the device on the Beta programme, and then unenrolled it. Almost immediately a downgrade able OTA notification arrived which dropped it back down to Marshmallow. After bootup all seemed fine, then play services stopped working. I was worried until I recieved a notification for a Marshmallow update - after that was installed everything worked fine as normal. The OEM unlock option was again available (although I decided to keep it locked).
For other devices it won't work, as I believe the Android N OTA is for a select few Nexus devices and possibly GPE devices (full list available on the website above).
Whether this work if you've completely deleted the OS - again I'm not sure. But I cannot see the harm in trying in that scenario. More experienced users could assist here. It should work as long as you can get into stock recovery.
Hope this helps.

Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.

lyuanrich said:
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
Click to expand...
Click to collapse
Glad to have helped. I had already attempted a factory reset before momentarily losing hope lol. Incidentally I'm now running N on my Nexus 9 - loving the new notifications.
Anyway ✌?

How to Re-Lock Bootloader?

I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?

TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore

I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.

Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.

Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.

raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly

raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??

WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?

TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !

WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.

raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.

joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.

Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times

When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.

the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.

metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.

Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly

Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!

I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?

It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).

First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.

I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.

Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0

xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.

YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.

Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.

Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice

Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen

xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.

Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You

Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.

Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.

Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks

Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.

Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.

Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.

Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.