For those who only want custom roms - an easier way to convert from T-Mobile USA. You don't need to flash system/product/vendor partitions. No restoring modem to get signal, data will work on first boot after you install a custom rom.
This could be easily done on Linux and Windows too. I don't recommend flashall. Just do it manually. For this discussion, I am converting T-Mobile to Euro:
1. Get T-Mobile MSM package from HERE. Get Euro package (for converting) from HERE
2. Flash T-Mobile MSM (you can't transfer the MSM package via flash drive, as some files will be corrupted and you won't be able to start the package. Just download straight, unzip and execute the exe. file)
3. Boot, enable OEM unlock (you'll have to connect to the internet for a few minutes) and unlock bootloader (get unlock bin from Oneplus)
4. Once unlocked, boot again, connect to PC, enable Developer options, enable ADB. Open terminal and execute adb command:
Code:
adb reboot fastboot
You will get into 'fastbootd' recovery, but that's how it should be. Your fastboot commands will be accepted.
5. Now, unzip the downloaded Euro version, go to that directory, open terminal and execute manually the following commands separately (just copy and paste a single command from the code below) followed by pressing 'enter', i.e. paste the command, press enter, paste the next command, press enter. Watch the terminal to make sure that each command went through:
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash modem modem.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
6. Once done, don't reboot in system. Instead, reboot into bootloader. From that, follow directions to install a custom rom. If Lineage, for example, flash their recovery first (fastboot flash recovery...), then boot into that recovery. Don't flash their 'copy partitions' files. Instead, just install the latest release via 'adb-sideload' (factory reset before or after flashing is required). Then boot into System normally. Your phone will have normal IMEI/Baseband and it will be listed as IN2013.
This is only for those who want custom roms. No stock OOS updates, which vendor is not needed any way, as all custom roms for Oneplus 8 provide their own vendor.
How to Unlock Oneplus 8 tmobile Bootloader without unlock token
farhansaeeddnp3021 said:
How to Unlock Oneplus 8 tmobile Bootloader without unlock token
Click to expand...
Click to collapse
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
optimumpro said:
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
Click to expand...
Click to collapse
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
farhansaeeddnp3021 said:
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
Click to expand...
Click to collapse
That's because there is a modified MSM tool for Oneplus 7 with a removed device name check. That enables you to flash global firmware on any Oneplus 7 variant. This is not possible on Oneplus 8.
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
aikattx said:
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
Click to expand...
Click to collapse
No. You don't. The tool already includes the downgrade software.
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
FoxyDrew said:
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
Click to expand...
Click to collapse
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
optimumpro said:
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
Click to expand...
Click to collapse
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
FoxyDrew said:
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
Click to expand...
Click to collapse
All right. Thanks for a very useful comment. Ha-Ha!
optimumpro said:
All right. Thanks for a very useful comment. Ha-Ha!
Click to expand...
Click to collapse
Ouch you seem salty lol, I could say the same
FoxyDrew said:
Ouch you seem salty lol, I could say the same
Click to expand...
Click to collapse
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
optimumpro said:
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
Click to expand...
Click to collapse
oh no that was genuine lol
FoxyDrew said:
oh no that was genuine lol
Click to expand...
Click to collapse
All right. My apologies. Sometimes it's difficult to figure out intentions on the internet.
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.
Has anyone seen this before?
ManlyP0tato said:
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.View attachment 5426977 Has anyone seen this before?
Click to expand...
Click to collapse
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
optimumpro said:
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
Click to expand...
Click to collapse
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader.
this is the screen I'm getting, is this fastboot with recovery or only fastboot?
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
ManlyP0tato said:
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader. View attachment 5426993 this is the screen I'm getting, is this fastboot with recovery or only fastboot?
View attachment 5426995
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
Click to expand...
Click to collapse
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
optimumpro said:
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
Click to expand...
Click to collapse
Ooh! I see I misunderstood that, it works just fine from the recovery screen!
I tried flashing the entire global rom because I don't want a custom rom but I just got a qualcomm crashdump mode . Currently using MSM to fix that. Is it even possible to use the global rom with the Tmobile model? Otherwise I'll just use Lineage.
Related
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
This guide will help you unlock your bootloader, flash a factory image, and return you to a stock device. It is wriiten assuming you have a windows PC (MAC users, see post 2). This can be helpful if you need to RMA your device or if you are getting erratic behavior or messed something up.
Tools and Files You’ll Need
If you don’t have adb and fastboot installed on your PC go here for a quick install of the necessary files, thanks to @Snoop05, http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users go here. http://forum.xda-developers.com/showthread.php?p=32305619
For Linux users, http://forum.xda-developers.com/showthread.php?p=10746225
For the factory image go here, https://developers.google.com/android/nexus/images You’ll download a .tgz file. Use winrar or 7-zip to extract the file to its own directory and remember where that directory is. Inside is another zip file, extract that too. You’ll need those image files if you use the long method to install the factory image. It’s also good to know where they are as they come in handy as you get more familiar with fastboot and what you can do with it.
How To Unlock the Bootloader
If you don’t have developer options enabled on your device go to settings, about device and tap on the build number 7 times.
In settings, developer options enable oem unlock
Now you get to use fastboot! Boot you device into the bootloader, vol up + power with your device shut off. Once booted into the bootloader connect it to your PC with the usb cable and open a command window on your PC. Once connected type the following command in the cmd window:
fastboot devices (Your device serial number should show up and this will ensure fastboot is working properly)
Then type:
fastboot oem unlock (This will unlock the bootloader and you’re now good to go)
NOTE, UNLOCKING THE BOOTLOADER DOES WIPE YOUR DEVICE SO BACKUP OFF YOUR DEVICE FIRST
How To Flash the Factory Image, SHORT METHOD
Open a command window on your PC in the same directory as you extracted the factory image. In that directory shift, right click in an open area and use “Open a command window here”
Boot your device into the bootloader and connect it to your PC. Then simply double click on the flash-all batch file. Note that there are batch files in there that will work for Windows as well as Linux machines
Let the batch file run and when it’s done you’ll be back to stock.
NOTE THAT FLASHING BY THIS METHOD DOES WIPE YOUR DEVICE SO MAKE SURE YOU BACKUP OFF YOUR DEVICE FIRST.
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
Congratulations, you’ve now flashed a factory image and learned how to use fastboot!
For MAC users, proceed each fastboot command with a ./ e.g. ./fastboot flash boot boot.img
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
GedBlake said:
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks @GedBlake. I would have responded sooner but I had to get home and check my tablet. Actually both work, vol up + power and vol down + power.
Sent from my Nexus 9 using XDA Free mobile app
But.... Toolkit so easy?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639!
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought.
Edit : That ^^^^ was a hint to other members to get your guides, tutorials, info threads, FAQ... Etc... Going..... This is a Nexus section after all. :silly:
Darth said:
But.... Toolkit so easy? ?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639! ?
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought. ?
Click to expand...
Click to collapse
I'll keep an eye it and do a roll up when the need arises
Sent from my Nexus 9 using XDA Free mobile app
cant flash system.img
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
nyasha1935 said:
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
Click to expand...
Click to collapse
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
cam30era said:
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
Click to expand...
Click to collapse
Ok thanks gonna try on windows, im a noob on linux
nyasha1935 said:
Ok thanks gonna try on windows, im a noob on linux
Click to expand...
Click to collapse
You'll be sorry.....
cam30era said:
You'll be sorry.....
Click to expand...
Click to collapse
Ok back to linux, how do I update android SDK
nyasha1935 said:
Ok back to linux, how do I update android SDK
Click to expand...
Click to collapse
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Is it possible to flash a factory image using a custom recovery like TWRP?
Sent from my Nexus 9 using Tapatalk
iamroddo said:
Is it possible to flash a factory image using a custom recovery like TWRP?
Click to expand...
Click to collapse
Is it possible to extract the .img from the volantis-lmy47x-factory-3efdc8d4.tgz from https://developers.google.com/android/nexus/images and flash them individually with TWRP (with the exception of recovery.img, which I guess would over-write TWRP)? Can it this be done directly from 5.0.1 or would I need to first upgrade to 5.02?
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Leoncino said:
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Click to expand...
Click to collapse
No need top apologize. You're English if fine.
There's a lot of discussion and lack of agreement about what affects the warranty on the Nexus 9. HTC says that even unlocking the bootloader "may void the warranty".
My advice would be to do what you want to it, but make sure you understand what you are doing. Ask a lot of questions before you do something you're unsure of.
Unlock your bootloader (if you haven't already). Do not relock bootloader if something goes wrong (this does not solve anything). With an unlocked bootloader, you can recover from almost any problem.
And you can flash the Google factory images anytime you want to return to stock.
I'm sorry there's not a clear answer to your question.
cam30era said:
No need top apologize. You're English if fine.
Click to expand...
Click to collapse
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Leoncino said:
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Click to expand...
Click to collapse
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
cam30era said:
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
Click to expand...
Click to collapse
And what happens if i lock again my bootloader, will i restore the warranty?
Leoncino said:
And what happens if i lock again my bootloader, will i restore the warranty?
Click to expand...
Click to collapse
That's a good question, without a clear answer (unfortunately).
This is the method tried on H815T model. But I think this should work with also other H815 models (other devices cannot say). Thanks to @autoprime, @thecubed and @Unjustified Dev for this.
Disclaimer: I am not responsible if your device gets into any more trouble for this.
Steps:
1. Download & clean install LG Drivers in your pc if u don't have it already.
2. Go into download mode by presing down the UP button and connecting the usb cable to the pc.
3. Go into LG ROOT folder. see this link to download: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
4. Double click on ports.bat to know your COM port. Let's say it's COM4.
5. Open a windows command promt by Shift+Rt Click into the Lg Root folder.
6. Now send these commands:
Code:
Send_Command.exe \\.\COM4
It will reply
Code:
SPECIAL COMMAND : ENTER , LEAVE
#
7. Now command type
Code:
id
It should reply
Code:
uid=(0)root gid=(0)root
#
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
9. Now pull out your battery, put it back in, go into HARD RESET mode by pressing down DOWN BUTTON+POWER BUTTON together and when the LG logo apprears, release the power button for a second and press it back again.
10. Now in HARD RESET, it will ask you whether you want to reset everything or not. Select "No" and it will take you to fastboot mode.
Special note:
1. @autoprime told me to factory reset everything before starting this whole process. I did as my bootloader was locked. Don't know how it affects in unlocked bootloader.
2. How to get out of fastboot normally: I don't know it quitely. My bootloader was locked, so neither I could flash any system file through fastboot, nor "fastboot reboot" or "fastboot reboot bootloader" worked for me. @autoprime told me to get out of fastboot, manually go into download mode, then pull out your battery and put back in. Actually you can't get out of the fastboot that way until you flash a KDZ.
Thank u. Reply in the comments if fastboot could help you any.
delete
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
TheBledard said:
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
Click to expand...
Click to collapse
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
nipun1110 said:
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
Click to expand...
Click to collapse
I couldn't get into Fastboot at all. Any command typed in send_command.exe gives "Fail" as result... Phone is connected in Download Mode and recognized in Windows, DIAG1 port is COM4.
Screenshot attached
lock bootloader , fastboot unnecessary
29y6145 said:
lock bootloader , fastboot unnecessary
Click to expand...
Click to collapse
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
I always get a "FAIL" reply. Any ideas?
nipun1110 said:
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader...
Code:
adb reboot bootloader
nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Hahahah tru!
nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
maybe u r suggesting to say
fastboot reboot bootloader
right?
Sent from my LG-H815 using Tapatalk
This does not work for me, I have an unlocked bootloader, but just get the response "FAIL".
And... Why don't you just zero the laf partition instead through an adb shell? What does this do that's different?
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
petermg said:
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
Click to expand...
Click to collapse
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
autoprime said:
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
Click to expand...
Click to collapse
Ok then if u suggesting me I should delete the post, I will ask Moderator to do so.
Sent from my LG-H815 using Tapatalk
It's good
Holly molly sir! You are a legend. Long story not so short. My lg got the bootloop bug. Took 2 months to fix, but apparently they changed my locked to three uk H815 "eu open" motherboard with actually unlocked one. So I was finally able to unlock boot-loader, root and **** up (LOL). Apparently I didn't install twrp properly (you'd think "fastboot boot twrp.img" would not install it but run it once) And i was following this to get Android M on. But it requires reboot before boot-loader is flashed. Right when i clicked reboot i figured it wont start in twrp but in stock recovery. So I couldn't even get proper bootloop, it would cut half way into the LG logo. I reckon kdz-ing would havedone the trick, but god it takes ages to DL the kdz file. So in the mean time i found this legendary post. The odd thing was i had to click Yes, on the factory reset screen, but it got me to "Fastboot mode started" and from there i booted into twrp and finished what it had started, currently its Optimising app 35 of 55. Nice one OP, Nice One!
hi i have unlocked bootloader. but i keep getting FAIL as response
nipun1110 said:
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
Click to expand...
Click to collapse
Hi,
how can I change it back to default Factory reset??
I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
just fastboot flash the factory images. you should be good to go since you can get into the bootloader.
painfree said:
I had a M build from the original D which I flashed and I saw the LTE was no different from the L so I tried to go back to MDA..D and I made an error or the file was corrupted as all I have is a large white Google. I can get to the bootloader and lock/unlock it but when it is unlocked there is an error message about unable to check corrupted files and press Pause and when I did that it still had message and to press Continue and still it only will go back to the large Google ?
Is my phone beyond repair now as I tried your toolkit and must not have chosen the right options as there is no escaping the White google screen?
I have used and supported your toolkit since the Nexus 5 days but now I am really stumped..
Click to expand...
Click to collapse
Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
painfree said:
So you are saying that the Skipsoft Toolkit is NOT able to resolve this situation by using any of its options?
Click to expand...
Click to collapse
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Why use a toolkit in the first place? As you've found out they're more trouble than they're worth. Plus, with a Nexus you really shouldn't need one anyway, these phones are simple to work with. Check out my guide, it has everything you need to know:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
painfree said:
I am using windows 10 and I cannot for the life of me figure out the file locations .. How do I do a simple thing as find a file called fastboot.exe on my PC using windows 10 ? this is what I have so far :
http://screencast.com/t/qhapdJk8
I have no idea where bootloader.exe is located and I cannot figure out how to do a simple file search on Windows 10. As a result I cannot open up a command prompt there if I cannot find it..
Click to expand...
Click to collapse
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Heisenberg said:
Did you follow the instructions in the beginning of the thread to install the SDK and in turn install adb/fastboot? I make no mention of bootloader.exe so I'm not sure where you're getting that from, there's no such thing, you don't know what the bootloader is? It might be a good idea for you to read the prerequisites section and the quick tips section at the beginning of the first post, and the FAQ section in the second post.
Click to expand...
Click to collapse
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
painfree said:
yes I completed part 1 with all the command prompt tests and someone said to skip to step 9... I read this regarding bootloader and I assumed it was an exe file.. sorry..
"Like the guy above said to fastboot the factory image.
See the link below, follow step 9
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
Also note in these commands that the xx.xx.img, the xx's are numbers. Just make sure you change the xx to whatever the number is. It will vary depending on version you flash.
http://forum.xda-developers.com/nexu...nners-t3206928 "
Click to expand...
Click to collapse
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Heisenberg said:
Are you following my instructions as they're written? They're very thorough so should be easy to follow.
Click to expand...
Click to collapse
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
painfree said:
OK I am back to system but there is a message about internal system problem yet it is factory now. .." Android System There's an internal problem with your device. Contact your manufacturer for details"
Click to expand...
Click to collapse
Which images did you flash? And which build?
Heisenberg said:
Which images did you flash? And which build?
Click to expand...
Click to collapse
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
painfree said:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-
01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-01.29.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
MDA089D I have t mobile and all the other builds K L M crippled my in home reception..
Click to expand...
Click to collapse
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Heisenberg said:
Ok, but you're able to actually boot into Android, right? Or are you not able to? If you're able to it's probably worth trying a factory reset (Settings>Backup & Reset>Factory Data Reset).
Click to expand...
Click to collapse
I am able to set up the phone as I normally would but my replacement via RMA just arrived so I will be sending this one back but now I know to avoid the toolkits.
This is FINAL working method.
First off you must unlock bootloader, and install twrp.
instructions for unlock bootloader are in this thread
http://forum.xda-developers.com/r1-...mazon-root-t3490882/post69387472#post69387472
I made many cycles between 6.6 and 6.1 and found that this set of files was minimum needed to maintain stable device. I started with only the preloader, and that left the phone able to connect to spft but the preloader was o longer in the "trusted zone" so it would not load the second step of power on (lk). replaceing the lk with spft after that allowed to boot to the boot menu, but would not trust the next step(boot.img). But with the preloader and lk I was able to fastboot, so was able to oem unlock.. this was the first method I was going to suggest. After more trials I decided it better to foll back all the bin files that the update replaced and also the secret bin so no more need to oem unlock after the roll back.
I got so comfortable moving between preloaders and version I got careless. My carelessness allowed me to mix up secure preloader and bin files with custom non secure recovery files and without realizing it I rebooted like that. I was left in a secure environment that was panicking because the recovery was not properly signed. (a terminal soft-brick)
My point is once you roll back DO NOT go back to locked and DO NOT blame me if you forget and restore some backup that does that to you down the road.
I do recomend that you roll back though. Because with the roll back, you are almost certain not able to brick because you can always use spft to to fix things.
THIS WILL ROLL BACK BOOT LOADER AND ALLOWS SPFT .
THIS HAS ONLY BEEN RUN WITH TWRP.
But the fastboot mode can also flash preloader if prefered. Just remember you may also need to oem unlock again after. This has not and will not be tested by me.
ONCE YOU HAVE UNLOCKED BOOTLOADER AND INSTALLED TWRP, return here and download "after_bootloader_roll_back_5.tar" unpack the tar and run the .bat file. It will adb push the recovery image to you phone and then install it.
It will rewrite :
1. preloader
2. lk (little kernel)
3. boot img
4. seccfg.bin
5. frp (to make sure bootloader remains unlockable)
6. trustzone (goes into both TEE1 and TEE2
7. secro.bin
All done.
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
jhonjahegu said:
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
Click to expand...
Click to collapse
Sounds like you need to do oem unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot oem unlock"
6. If need to do oem unlock you will also need to "fastboot format userdata"
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
digihaven said:
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
Click to expand...
Click to collapse
If it is looping into twrp then you must do step 6 from above.
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
clownkitty said:
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
Click to expand...
Click to collapse
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
mrmazak said:
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
Click to expand...
Click to collapse
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
clownkitty said:
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
Click to expand...
Click to collapse
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
mrmazak said:
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
Click to expand...
Click to collapse
I didn't realize you had to load straight into recovery mode after flashing it, I got it to work now, thank you so much!
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
tuespazio said:
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
Click to expand...
Click to collapse
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
mrmazak said:
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
Click to expand...
Click to collapse
Hi, dont worry now is fixed i return to 6.1 and then flash full 6.5 firmware.
Data is now working fine .
Thanks for your Support
sorry, wrong thread
ncy1 said:
Hi guys, sorry to bother you with this
I was on 6.0 rooted and without ads, i just tried to update my phone using the v17 and settings on this thread, when i went to cellphone info on settings it said i was still on 6.0. Did i miss something or this a normal thing? Anyway, i went back to recovery mode, did a wipe and tried to flash the 7.4.2 rom but it sent me an error, now the phone won't boot and gets stuck on the blu loadscreen.
Click to expand...
Click to collapse
Don't get me wrong, I feel bad for you that your phone is in this situation, but that has nothing to do with the thread you are posting in.
This thread is for rolling back the preloader.
And all the oem and Amazon Roms are 6.0
To get help you should post in the thread you got the ROM from.
And include the error you got.
mrmazak said:
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Click to expand...
Click to collapse
I think I just want to try this method, since I want to convert it to OEM and still keep OTA updates anyway. I'm blanking though as to how I need to go about this.
I have adb installed, and I have access. I assume this requires a fastboot command, but I don't know which.
Jessooca said:
Mrmazak... does this work on a new out of the box blu r1 that came with the 6.6 August update already installed?
I'm trying to help a friend, I surprisingly can't get the bootloader unlocked, dirtycow continually failed.
He doesn't care about updates etc... just wanted to flash the no ads firmware onto a prime version blu r1 hd
Click to expand...
Click to collapse
To the best of my knowledge it was.
Last time someone told me they were having trouble, they ran the codes manually one by one instead of using the script, and it worked. Apparently they had trouble pushing the files from the batch file. I had similar trouble when I wrote the script, that is why there are 3 second pauses ,that seemed to fix it for me. I will change them to 10 seconds and see if it helps.
I will update here when I change it then you candownload again and try, or you can make the changes yourself and let the me know
OK i updated the one-click.bat . you can download it again to see if that help. Also you said dirty-cow keeps failing, please let me know the fail message and also the comments displayed during the first part of the script. the part that is pushing files.
Also I have not been able to get feedback on the one-click.sh for linux. I don't normally use linux and did not test the shell. If you are using that one maybe the fail is my poorly written .sh
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
danbcooper said:
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
Click to expand...
Click to collapse
"oem" is not supposed to be capitalized
i went back and edited that original post too.
mrmazak said:
"oem" is not supposed to be capitalized
i went back and edited that original post too.
Click to expand...
Click to collapse
Now I ran "fastboot oem unlock" and it says FAILED (remote: unknown command). Do you know why?
Never mind.. Tried again and worked! Thanks for everything!