i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
abdulmajed1 said:
i got pixel 6 and I've been planning to sell it, i tried to lock the bootloader but the commend didn't work i don't know why. After that i was trying to re flash the stock ROM via fastboot mode but for some reason flashing process aborted at particular point and phone wasn't booting, kept in bootloop .. google logo then restart and it went on.
after that i made a mistake which was i attempted to re lock the bootloader while phone was in bootloop and the process completed successfully.
now I'm not able to flash anything via fastboot as bootloader is locked and it's cannot get unloaded ..
is there anything i could do to reflash the stock image in this state? phone now doesn't boot .. only google logo the it restarts it self
Click to expand...
Click to collapse
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Device not boot
Click to expand...
Click to collapse
Lughnasadh said:
Try sideloading the OTA. Also, if you still have OEM unlocking enabled in Developer Options you can try using Android Flash Tool.
Click to expand...
Click to collapse
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
No kidding? I wasn't aware of that!
Doesn't help in this situation, sadly.
V0latyle said:
Android Flash Tool can't be used on a locked bootloader. That being said, it's the best way to return the phone to stock state.
Sideloading the OTA is the only possibility of restoring the device in this situation. I don't think the Pixel Repair Tool works with the Pixel 6 yet.
Try booting to recovery mode and perform a factory reset.
Lastly...A "bricked" device is completely unresponsive. If the device boots, the screen works, and can be forced into bootloader/fastboot/recovery, it's not bricked.
Click to expand...
Click to collapse
I've tried sideloading the latests ota file but then the process got aborted.
it showed: failed to verify whole file signature.
I've tried both latest stable ota " Androd 12 " and beta as well
Lughnasadh said:
All you need is OEM Unlocking enabled to use Android Flash Tool. You don't actually have to have your bootloader unlocked. The Flash Tool will do it for you.
Click to expand...
Click to collapse
I'm not able to reach oem unlocking option since it cannot boot
abdulmajed1 said:
I'm not able to reach oem unlocking option since it cannot boot
Click to expand...
Click to collapse
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Lughnasadh said:
Sideload the OTA. Make sure your Platform Tools are up-to-date. Make sure you are sideloading the OTA and not the factory image and it's the correct OTA for your device. Try different cables and ports. Re-download in case your original download got corrupted.
Click to expand...
Click to collapse
already tried sideloading different ota versions, different ports and cables as well. There's no point
Have you tried the Android Flash Tool?
I don't know if it would work since I believe locking the bootloader also disables OEM Unlocking, but it's worth a try.
hello guys
I fixed the pixel
ٖ:
The problem was mostly from the laptop
I used an Bugjaeger Mobile ADB - USB OTG app and install beta update from adb update recovery
thanks
Related
So I rooted my Huawei G520
Download this flashing tool
Followed the prompts as best as i could
Nadda!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just sits there grinning at me
I know I've missed something really simple
Tried it with/without the phone connected - Nadda
Click Download and nothing happens
JethroUK said:
So I rooted my Huawei G520
Download this flashing tool
Followed the prompts as best as i could
Nadda!
Just sits there grinning at me
I know I've missed something really simple
Tried it with/without the phone connected - Nadda
Click Download and nothing happens
Click to expand...
Click to collapse
Do you have the USB drivers installed for your device and is your device being recognized by Windows Device Manager? If you don't have the drivers installed for your device I would recommend installing them and if you can't find the specific USB drivers for your device I would recommend trying Koush's Universal ADB device drivers which can be downloaded from here.
I'm ignorant , there i said it. The flash tool is good and dandy, but why not just use something like ROMtoolboxpro, for the recovery install. The previous answer is good though, you need drivers, but I must ask, if you didnt have the drivers installed correctly, then how did you root????
i would suggest CWM app for recovery install, but it crashes on me. Like I said Iam ignorant because I don't know your device,
Warped420 said:
.... why not just use something like ROMtoolboxpro, for the recovery install....,
Click to expand...
Click to collapse
installed it - current Chinese software closes it everytime i open it - hence i desperately need to flash a new rom
You do understand you have to buy ROMtoolboxpro right?, if you purchase it, it shouldn't close automatically. Dude it is quick and it gets the job done.. Credit = whoever made this little "work of art"
EDIT: If your trying to flash a rom, why don't you just transfer it to your sd card and flash from recovery if you have recovery already?
OK , so my google skills suck today, but if you know Arabic ,this is perfect.
http://www.winkabarkyaw.net/2013/04/how-to-root-huawei-g520-5000.html
They have links to drivers for the flash tool and your device on here ..
shimp208 said:
Do you have the USB drivers installed for your device and is your device being recognized by Windows Device Manager? If you don't have the drivers installed for your device I would recommend installing them and if you can't find the specific USB drivers for your device I would recommend trying Koush's Universal ADB device drivers which can be downloaded from here.
Click to expand...
Click to collapse
Installed those drivers - still no go
I am missing something really fundamental:
My Huawei is rooted (I think)
USB drivers are installed
Mobile is in USB debug mode (is that right?)
Mobile is connected
I have been working on this for days and seem to get further away not nearer
Someone mention Bootloader code - what the devil is that?? Anyone know?? Do i need one?
To install CWM on your phone ,First you need to unlock the bootloader ,you have to ask for this code in huawei website
http://www.huaweidevice.com/cn/servicePolicy.do?method=preUnlock china version
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock English version
take a look here
Again, i found this by using "Google"
Thanks for the links!
Warped420 said:
To install CWM on your phone ,First you need to unlock the bootloader ,you have to ask for this code in huawei website
http://www.huaweidevice.com/cn/servicePolicy.do?method=preUnlock china version
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock English version
take a look here
Again, i found this by using "Google"
Click to expand...
Click to collapse
I did try that earlier but the y dont list the G520 - cheers anyhow
Warped420 said:
To install CWM on your phone ,First you need to unlock the bootloader ,you have to ask for this code in huawei website
http://www.huaweidevice.com/cn/servicePolicy.do?method=preUnlock china version
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock English version
take a look here
Again, i found this by using "Google"
Click to expand...
Click to collapse
I tried a different rooting tool and it flashed CWM onto my phone
Actually managed to boot in recovery mode
Tried to flash a rom
Deleted cache and reset the phone
It tries to install the rom - verifies, etc then aborts - dang!
Same when i tried another rom
Same when i tried to install gapps package
Could it still have a locked bootloader if it's rooted with CWM installed?
That's what it looks like to me. Friends of mine say they always have issues with bootloaders. Since other models of that brand have them, then you should look for the correct code or a way to hack it.
How did you flashed CWM
Hi.
Could you tell me how did you flashed CMW, and for which specific version of the phone? There are two versions of Huawei G520:
- 5000 (chinese version with Mediatek processor)
- 0000 (occidental version with Snapdrago). I have this one.
Thanks
JethroUK said:
I tried a different rooting tool and it flashed CWM onto my phone
Actually managed to boot in recovery mode
Tried to flash a rom
Deleted cache and reset the phone
It tries to install the rom - verifies, etc then aborts - dang!
Same when i tried another rom
Same when i tried to install gapps package
Could it still have a locked bootloader if it's rooted with CWM installed?
Click to expand...
Click to collapse
JethroUK said:
So I rooted my Huawei G520
Download this flashing tool
Followed the prompts as best as i could
Nadda!
Just sits there grinning at me
I know I've missed something really simple
Tried it with/without the phone connected - Nadda
Click Download and nothing happens
Click to expand...
Click to collapse
do you use sd card to ROM, or use usb cable to Rom?
I'm not sure if this is the right section, but has anyone else received the 5.0.2 update? I got mine about half an hour ago, but I can't find a changelog. These are the changes I've noticed so far:
It's somewhat faster
Apps no longer fail to launch (I'd try to open them before, but they would close immediately, and I'd have to dim the screen before trying to open the app again)
By the way, does "sunlight mode" do anything at all?
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just got this, I haven't loaded it yet, I have Gohma loaded. It will not let me swipe the notification away, Is installing my only option because that kind of messes up getting any other notification.
Just got this but cant find anything new. Sunlight mode was already available via lollipop update. Never used it but i assume if you use low brightness levels a quick swipe will make it brighter and vice versa rather than manually altering the brightness. Not an issue for me as i used mini launcher but they can't assume everyone does
http://www.talkandroid.com/237608-a...o-the-samsung-gear-live-and-the-lg-g-watch-r/
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
I don't suppose any of you guys have the system image for this do you? I'm itching to get my hands on this, but my watch is saying that 5.0.1 is up to date.
Apoplectic1 said:
I don't suppose any of you guys have the system image for this do you? I'm itching to get my hands on this, but my watch is saying that 5.0.1 is up to date.
Click to expand...
Click to collapse
Don't feel bad mine too I'll probably still be on 5.01 when everyone else is on 5.1 update in mar.
dligon said:
Don't feel bad mine too I'll probably still be on 5.01 when everyone else is on 5.1 update in mar.
Click to expand...
Click to collapse
I'm just hoping someone can catch the OTA files and upload them onto here, sort of like this:
http://forum.xda-developers.com/showthread.php?t=2796326
Apoplectic1 said:
I'm just hoping someone can catch the OTA files and upload them onto here, sort of like this:
http://forum.xda-developers.com/showthread.php?t=2796326
Click to expand...
Click to collapse
Here it is my update.zip from the 5.0.2 OTA inside the /cache partition:
prototovsky said:
Here it is my update.zip from the 5.0.2 OTA inside the /cache partition:
Click to expand...
Click to collapse
Thanks man! Does one just flash it in a custom recovery, or do you have to sideload it?
Apoplectic1 said:
Thanks man! Does one just flash it in a custom recovery, or do you have to sideload it?
Click to expand...
Click to collapse
It does not work by installing OTA with TWRP or flashing directly. I´ve tried to upload it with adb sideload and the original recovery, but it says "Error: protocol fault (no status), because I need adb 1.0.32 version.
I´ve installed also the new version, but now it says "unexpected contents on the update.zip"...
prototovsky said:
It does not work by installing OTA with TWRP or flashing directly. I´ve tried to upload it with adb sideload and the original recovery, but it says "Error: protocol fault (no status), because I need adb 1.0.32 version.
I´ve installed also the new version, but now it says "unexpected contents on the update.zip"...
Click to expand...
Click to collapse
Do you have the Gohma ROM or Arter Kernel installed? Have you tried flashing a stock boot image from the LG G Watch Toolkit before flashing the update?
I'd fiddle around with it myself, but I keep my dock at work during the week.
Apoplectic1 said:
Do you have the Gohma ROM or Arter Kernel installed? Have you tried flashing a stock boot image from the LG G Watch Toolkit before flashing the update?
I'd fiddle around with it myself, but I keep my dock at work during the week.
Click to expand...
Click to collapse
No, I've stock rom with root and TWRP recovery. A user says me that the OTA doesn't work because root overwrites this two files: install-recovery.sh and recovery-from-boot
prototovsky said:
No, I've stock rom with root and TWRP recovery. A user says me that the OTA doesn't work because root overwrites this two files: install-recovery.sh and recovery-from-boot
Click to expand...
Click to collapse
Do you know the path for those two files? We may luck out and the root process may have renamed them install-recovery.bak and recovery-from-boot.bak before writing the new files.
Apoplectic1 said:
Do you know the path for those two files? We may luck out and the root process may have renamed them install-recovery.bak and recovery-from-boot.bak before writing the new files.
Click to expand...
Click to collapse
No, but I'll try some things ...
I just tried to flash it using TWRP after completely wiping everything but internal storage, thinking it might need a clean flash, but it gave me an error saying that it was unable to flash due to an error in executing the updater binary.
I'm going to flash the stock recovery on it, wipe the data and caches and see if adb sideloading it is any more effective.
EDIT: It isn't.
Im trying to manually push this update to my watch as well, has anyone figured out any solutions?
I tried flashing update-LWX48P5.0.1-to-LWX49K5.0.2.zip from http://rootjunkysdl.com/?device=LG G Watch&folder=OTA but it errors when I try through TWRP. I went back to stock but I do have an unlocked bootloader, I will try relocking and trying then.
Okay so thats weird, im on 5.0.1 but when i try and flash 5.0.2 from TWRP is errors saying that the device "lge/cm_dory/dory:4.4.2/KVT49L/567135e166:eng/test-keys"
how get it to read as 5.0.1 which I am on?
edit:
Soo, I wound up on 5.0.2 while trying to fix some of the random flashes I was trying to update. I wound up erasing my system.img and it was only booting to recovery, so I did the "back to stock" option from rootjunkys toolkit and it reflashed boot/system etc, and when I booted up to turn dev options back on it looks like it put 5.0.2 back on. So that fixed that
Bugs after LWX49K update
Since my watch was updated I cannot open any app on phone using my watch. Moreover - several watchfaces like those of Smartwatch Bureaux do not sync anymore. I own LG G3 and use Chupachups ROM v.4.2 V20h.
Can anyone solve that problem?
Hey guys!
Since it seems some of you are a bit confused about all this: Just use THIS tool here (LG G Watch Restore Tool, make sure you use version 9.5), go into fastboot mode (rebooting, when LG logo appears swipe from left upper to lower right corner) over USB and choose the option "6 Restore your G watch to stock".
Voila! Now you're on 5.0.2 with less effort than OTA updating
I discovered this by accident actually. I tried to restore stock so I can OTA update to 5.0.2, then I saw it's a pre-rooted system.img (because root overwrites OTA critical things so it fails) and already suspected it'd be the newest one
danr said:
Since my watch was updated I cannot open any app on phone using my watch. Moreover - several watchfaces like those of Smartwatch Bureaux do not sync anymore. I own LG G3 and use Chupachups ROM v.4.2 V20h.
Can anyone solve that problem?
Click to expand...
Click to collapse
I was getting a lot of bugs also, but I'm not sure if it is watchmaker or update. Super slow now and notifications are random. I'm uninstalling watchmaker first to check.
going back to stock cause fricking anoying notification...
and some one made a kernel for 5.0.2. a new guy
Hey guys I've seen that a lot of people have been having trouble getting the bootloader unlock to work I made a tutorial for you to follow so make sure you follow the tutorial before asking questions. I've answered every question I could think of in this video so please watch it first. You must follow the directions! Please
https://youtu.be/ilteTn7EISk
Link to download the latest firmware for your Verizon Galaxy Note 3 to flash in Odin if you need to reinstall it before unlocking (if you have no luck with my instructions you should try flashing the firmware again with Odin so that you have a completely stock phone):
http://www.sammobile.com/firmwares/
How to root the Verizon Galaxy Note 3 on the latest firmware (0F1):
http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569
Official Verizon Galaxy Note 3 bootloader unlock thread:
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
All files you will need for unlocking your Verizon Galaxy Note 3:
https://drive.google.com/file/d/0B83noRHOimrRdkhoWWxhR19QWGc/view?usp=drivesdk
Sent from my SM-N900V using Tapatalk
**TWRP AND FLASHING ROMS**
Now that your Verizon Galaxy Note 3 bootloader is unlocked is time to flash some roms. For this you will need TWRP. A simple way to obtain the latest and stay up to date with a couple clicks is TWRP with Flashify. You will not need Odin or a PC at all to do this.
STEP 1:
Download flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STEP 2:
Open the app and give it root access permissions when your Super User app prompts you with the regular pop-up.
STEP 3:
STEP 4:
STEP 5:
STEP 6:
Flash roms till you pass out lol. Don't forget to backup your files.
----------------------------------------------------------
**************************************
----------------------------------------------------------
USING TWRP:
*****Yes- Jasmine Rom 6.1 can be flashed with twrp*****
When you flash your first rom after unlocking your bootloader and flashing twrp it's best to start with a clean slate. Make sure you put the rom of your choice on your Micro SD card. Wiping everything ensures that you have as few errors as possible. When flashing completely new roms this is also advised to avoid any errors.
Sent from my SM-N900V using Tapatalk
**Jasmine Rom 6.1**
Official thread:
http://forum.xda-developers.com/showthread.php?t=2760380
Download link for Jasmine Rom 6.1 ZIP:
https://www.androidfilehost.com/?fid=24052804347812398
Sent from my SM-N900V using Tapatalk
i had my vzw note 3 sm-n900v of1 rooted and bl unlock
i reverted back to official stock OF1 with odin.
i noticed that emmc brick debug tool shows my CID as the dev version and not my original cid
i was wondering after i root it again do i need to change my cid back to original before i run "samsung_unlock_n3" or is it ok to run it with the new cid already like it is.
thanks and nice guide here
en11gma said:
i had my vzw note 3 sm-n900v of1 rooted and bl unlock
i reverted back to official stock OF1 with odin.
i noticed that emmc brick debug tool shows my CID as the dev version and not my original cid
i was wondering after i root it again do i need to change my cid back to original before i run "samsung_unlock_n3" or is it ok to run it with the new cid already like it is.
thanks and nice guide here
Click to expand...
Click to collapse
No just run the unlock tool again and you're good to go.
Sent from my SM-N900V using Tapatalk
alexp1289 said:
No just run the unlock tool again and you're good to go.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
i ran the tool with no busybox installed
odin says im developer edition
I tried to do this, but the phone wouldnt boot and it kept booting to a message that said ""system software not authorized by Verizon wireless has been found on your phone"
it also says "recovery is not seandroid enforcing"
nevermind, going back to stock, re-rooting, and re-unlocking the bootloader again seems to have fixed it
well
for some reasons above mentioned method isnt working at all in my case..
after giving all the commands in the terminal this is what it says.
it doesnt go further to the step where cid is displayed and device doesnt go for reboot .
(.)am on 4.4.2
(.)device is rooted
(.)on stock rom..
(.)never ever flashed anything to my device.
(.)i havent set up samsung account yet as a result there is no option in settings to disable reactivation screen but i did disable the lock screen before attempting anything on terminal..
urgent help needed
Sent from my SM-N900V using XDA-Developers mobile app
pakiyoungster said:
well
for some reasons above mentioned method isnt working at all in my case..
after giving all the commands in the terminal this is what it says.
it doesnt go further to the step where cid is displayed and device doesnt go for reboot .
(.)am on 4.4.2
(.)device is rooted
(.)on stock rom..
(.)never ever flashed anything to my device.
(.)i havent set up samsung account yet as a result there is no option in settings to disable reactivation screen but i did disable the lock screen before attempting anything on terminal..
urgent help needed
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Flash 0F1 firmware the unlock method doesn't work on the firmware version that you're on. Follow my links in the first post to update firmware.
Sent from my SM-N900V using Tapatalk
secure fail: recovery
Followed the instructions, ended up with a soft bricked phone. Back to odin to re-flash OF1 I guess...
Using Flashify to flash TWRP after everything else looked great, rooted, bootloader unlock seemed to take.
Now looks like knox has me locked up and no path but to re-flash.
What did I miss?
tw3ak.
Thanks for the links and turorials. Will the Darklord N5 rom run on the Verizon note 3 after taking these steps?
Thanks.
tw3ak said:
Followed the instructions, ended up with a soft bricked phone. Back to odin to re-flash OF1 I guess...
Using Flashify to flash TWRP after everything else looked great, rooted, bootloader unlock seemed to take.
Now looks like knox has me locked up and no path but to re-flash.
What did I miss?
tw3ak.
Click to expand...
Click to collapse
If you saw a "secure fail: recovery" message you were not unlocked. (You were rooted, which allowed you to flash a recovery, but not unlocked)
If you are unlocked the Odin/Download screen will say "MODE: DEVELOPER" at the bottom of the text block at the top left side of the screen.
It is doubtful you were soft-bricked either. You might have been stuck in a "reboot to recovery every time loop" (which would then give you a secure boot: fail message)
but you can get out of that with the following:
- pull battery; wait a few seconds; reinsert battery
- hold down VolDown+Home+Power to start phone
- choose "Cancel" when the phone gives you the warning pop-up message about using Odin mode.
Sm-n900v (Rooted)
Android 5.0,
Baseband N900VVRUE0B6.
Will the unlock n3.zip work for me?
baabafadil said:
Sm-n900v (Rooted)
Android 5.0,
Baseband N900VVRUE0B6.
Will the unlock n3.zip work for me?
Click to expand...
Click to collapse
Based on my reading, it requires baseband OF1. You also need to do the CID check, to be sure your phone can be unlocked.
I did that already like post suggested n my Cid starts with 15
Hi everyone, I have a Blackview bv6000 device with android 6.0, firmware BV6000_blackview_V01_20160608
I have already unlocked the bootloader and i would like to unlock the root but i don't know how do it. Can someone help me?
Another thing, i have unlock the System UI Tuner but it doesn't appere in my settings menu, any idea to solve it?
Regards, Marco
traneXD said:
Hi everyone, I have a Blackview bv6000 device with android 6.0, firmware BV6000_blackview_V01_20160608
I have already unlocked the bootloader and i would like to unlock the root but i don't know how do it. Can someone help me?
Another thing, i have unlock the System UI Tuner but it doesn't appere in my settings menu, any idea to solve it?
Regards, Marco
Click to expand...
Click to collapse
Hi Marco,
could you please describe how to unlock the bootloader?
Thanks,
Chris
HI, for the bootloader just go in settings, unlock developer options and u can find there unlock OEM
I Have BV6000 now too, an no way found to root it.
Pappmann said:
I Have BV6000 now too, an no way found to root it.
Click to expand...
Click to collapse
Hi mate the System UI Tuner appere on your device?
Ring R00T?
Does King R00T work? This would be my 1st choice.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Avast! detects it as a PUP (POTENTIALLY UNWANTED PROGRAM) due to the exploit. And yes, avast!'s detection is correct, it is "Potentially" unwanted, you have the choice to have it ignored.
Also, I have the desktop version of King R00T installed into a netbook, so I don't have all the detection's going nutz, I do my R00T and jail brakes from the netbook.
Also, does the phone have an LED notification for calls/text/mail/charging on the front?
UnableToResetOldProfile said:
Does King R00T work? This would be my 1st choice.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Avast! detects it as a PUP (POTENTIALLY UNWANTED PROGRAM) due to the exploit. And yes, avast!'s detection is correct, it is "Potentially" unwanted, you have the choice to have it ignored.
Also, I have the desktop version of King R00T installed into a netbook, so I don't have all the detection's going nutz, I do my R00T and jail brakes from the netbook.
Also, does the phone have an LED notification for calls/text/mail/charging on the front?
Click to expand...
Click to collapse
The Phone have not led notification, i haven't tra King root yet because nobody have used it on this device
R00T, The '00' is the base directery in R'00'T
traneXD said:
The Phone have not led notification, i haven't tra King root yet because nobody have used it on this device
Click to expand...
Click to collapse
King R00T is for Chinese phones, by Chinese people, who live in China .... :silly:
Use the desktop version as it has better exploit ability's. It works on most Chinese phones that I R00T, the last Chinese phone I did (THL T7) it was flawless.
KR has a page here at XDA: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
PLEASE REPORT BACK WITH YOUR SUCCESS
.
.
.
.
.
.
.
UnableToResetOldProfile said:
King R00T is for Chinese phones, by Chinese people, who live in China .... :silly:
Use the desktop version as it has better exploit ability's. It works on most Chinese phones that I R00T, the last Chinese phone I did (THL T7) it was flawless.
KR has a page here at XDA: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
PLEASE REPORT BACK WITH YOUR SUCCESS .
Click to expand...
Click to collapse
I tried to root my BV6000 with KR, but it failed!
dr.dog1987 said:
I tried to root my BV6000 with KR, but it failed!
Click to expand...
Click to collapse
I guess it's early, this device was released in may :/
i tried kingroot too, does not work yet.
its quite simple, just flash TWRP from Needrom and then su.
worked for me
yankeeboy said:
its quite simple, just flash TWRP from Needrom and then su.
worked for me
Click to expand...
Click to collapse
yankeeboy,
could you please provide more details?
thanks in advance!
SuperSU 6.0 R00T
"Chainfire has released SuperSU root for Android 6.0 Marshmallow without modifying system partitions"
Give this a try: http://www.supersuroot.com/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:fingers-crossed:
chris-ba said:
yankeeboy,
could you please provide more details?
thanks in advance!
Click to expand...
Click to collapse
1. copy UPDATE-SuperSU-v2.65-20151226141550.zip (attached) to BV6000, remember where you place it
2. flash TWRP recovery.img(decompress from zip attached) with sp flash tool v5.1604 or newer, use scatter file attached, check only recovery for flashing
3. boot into TWRP recovery
3. flash UPDATE-SuperSU-v2.65-20151226141550.zip within TWRP recovery
4. wipe dalvik/cache
5. reboot
done
i'm not responsible for any bricked phone, use this all at your own risk!!!
yankeeboy said:
1. copy UPDATE-SuperSU-v2.65-20151226141550.zip (attached) to BV6000, remember where you place it
2. flash TWRP recovery.img(decompress from zip attached) with sp flash tool v5.1604 or newer, use scatter file attached, check only recovery for flashing
3. boot into TWRP recovery
3. flash UPDATE-SuperSU-v2.65-20151226141550.zip within TWRP recovery
4. wipe dalvik/cache
5. reboot
done
i'm not responsible for any bricked phone, use this all at your own risk!!!
Click to expand...
Click to collapse
many thanks for your remarks. I'm going to test it as soon as my phone arrives.
on needrom I read that some people have some problems. the touchscreen is not responding or they lost their IMEI.
were you faced with any problems quite like this?
chris-ba said:
many thanks for your remarks. I'm going to test it as soon as my phone arrives.
on needrom I read that some people have some problems. the touchscreen is not responding or they lost their IMEI.
were you faced with any problems quite like this?
Click to expand...
Click to collapse
no problems for me so far
Which v of TWRP?
yankeeboy said:
1. copy UPDATE-SuperSU-v2.65-20151226141550.zip (attached) to BV6000, remember where you place it
2. flash TWRP recovery.img(decompress from zip attached) with sp flash tool v5.1604 or newer, use scatter file attached, check only recovery for flashing
3. boot into TWRP recovery
3?. flash UPDATE-SuperSU-v2.65-20151226141550.zip within TWRP recovery
4. wipe dalvik/cache
5. reboot
done
I'm not responsible for any bricked phone, use this all at your own risk!!!
Click to expand...
Click to collapse
Sorry, for the post, I figured out my own question ... :silly:
Hi, does the bootloader need to be unlocked before flashing the TWRP and if so why is there no mention of this? Thanks!
Gyro installed incorrectly.
There is a possibility that a large production run is defective.
This defect may be in all the phones produced.
The gyro was installed incorrectly and the pitch and roll are swapped.
Check your phone and report this problem to Blackview.
https://youtu.be/LARkSzgvPjU
http://bbs.blackview.hk/viewtopic.php?f=142&t=42024
Moto G Power 2021
XT2117
borneo
Firmware
Rescue and Smart Assistant (LMSA)
https://mirrors.lolinet.com/firmware/moto/borneo/official/
https://t.me/s/MotoUpdatesTracker
[Index] Motorola Stock Firmware
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Moto G Play
XT2093
Moto G Stylus
XT2115
I have the moto g power borneo, just got it yesterday. the option for "enable oem unlocking" is greyed out. I did a full factory reset, and still grey. It's not tied to any carrier, and I've already connected to the internet via wifi. the phone is network unlocked. Would I be able to flash the stock rom via LMSA, and that might get it to work?
edit: just to clarify. yes, the bootloader is locked.
gutter_chris said:
I have the moto g power borneo, just got it yesterday. the option for "enable oem unlocking" is greyed out. I did a full factory reset, and still grey. It's not tied to any carrier, and I've already connected to the internet via wifi. the phone is network unlocked. Would I be able to flash the stock rom via LMSA, and that might get it to work?
edit: just to clarify. yes, the bootloader is locked.
Click to expand...
Click to collapse
Sometimes there's a time delay for the allow oem unlocking, it may take a few days, be sure to connect to wifi or lte after factory reset.
You certainly can try LMSA, but reflashing the firmware is unlikely to speed up the process.
sd_shadow said:
Sometimes there's a time delay for the allow oem unlocking, it may take a few days.
Click to expand...
Click to collapse
Yeah, I had read that somewhere yesterday. Thanks for confirming that. I will wait patiently first.
If anyone has suggestions on how to flash the cricket firmware to a boost mobile device let me know. I'm open to try anything on this $90 device.
TheTrueJayTwenty said:
If anyone has suggestions on how to flash the cricket firmware to a boost mobile device let me know. I'm open to try anything on this $90 device.
Click to expand...
Click to collapse
You may only need the radio flash
Flashing the Radio Firmware
https://mirrors.lolinet.com/firmware/moto/borneo/official/Cricket/
I would try to unlock the bootloader first, but just flashing the radio firmware is pretty safe.
sd_shadow said:
You may only need the radio flash
Flashing the Radio Firmware
https://mirrors.lolinet.com/firmware/moto/borneo/official/Cricket/
I would try to unlock the bootloader first, but just flashing the radio firmware is pretty safe.
Click to expand...
Click to collapse
Unfortunately OEM unlock is grayed out, but I was able to get an unlock key from Motorola. I've been trying to figure out a way to flash the cricket firmware because I don't think OEM unlock is grayed out.
TheTrueJayTwenty said:
Unfortunately OEM unlock is grayed out, but I was able to get an unlock key from Motorola. I've been trying to figure out a way to flash the cricket firmware because I don't think OEM unlock is grayed out.
Click to expand...
Click to collapse
Flashing a different software channel with a locked bootloader, will not end well.
Better off trying a factor reset, and connect to wifi or lte.
There can be a timed delay of a few days, on the allow OEM unlock
sd_shadow said:
Flashing a different software channel with a locked bootloader, will not end well.
Better off trying a factor reset, and connect to wifi or lte.
There can be a timed delay of a few days, on the allow OEM unlock
Click to expand...
Click to collapse
I have it on Wi-Fi right now, hopefully its just delayed. I only got this device to use on Wi-Fi, but if I don't keep airplane mode on Boost mobile locks the Wi-Fi unless you activate service with them. Very strange way to do business if you ask me.
TheTrueJayTwenty said:
I only got this device to use on Wi-Fi, but if I don't keep airplane mode on Boost mobile locks the Wi-Fi unless you activate service with them.
Click to expand...
Click to collapse
I have the same issue. Anyone know of a way to disable this? I've tried to remove anything associated with carrier and boost from the device (borneo) through adb. Some I was able to disable but most failed as non-disable. I got this device for my 5 yr old to mess around on, but the TOS popup is intrusive and she has repeatedly accidentally pressed the accept button which locks out wifi. Would rooting and flashing a new rom even resolve the TOS requests from boost. Forgive my ignorance as I haven't messed with root or custom roms since my lg g3. Any help is greatly appreciated.
MuffinGod said:
I have the same issue. Anyone know of a way to disable this? I've tried to remove anything associated with carrier and boost from the device (borneo) through adb. Some I was able to disable but most failed as non-disable. I got this device for my 5 yr old to mess around on, but the TOS popup is intrusive and she has repeatedly accidentally pressed the accept button which locks out wifi. Would rooting and flashing a new rom even resolve the TOS requests from boost. Forgive my ignorance as I haven't messed with root or custom roms since my lg g3. Any help is greatly appreciated.
Click to expand...
Click to collapse
So I may have figured it out, I did a factory reset, on setup I declined everything. I removed everything I could via adb that had anything to do with sprint, boost, and carrier. I then went into the apps list on the device clicked show system apps, went through the apps I couldn't disable under advanced I denied the app permission to modify system settings. As for the TOS the keeps popping up you can try turning on airplane mode you can still use Wi-Fi, I've had hit or miss luck with this one. But Wi-Fi is still working as of now... Hopefully someone can get the bootloader unlocked on the boost model.
I think we're in the same boat. I have airplane mode on with wifi but it doesn't seem to stop the popup. I did get the bootloader unlocked with a code from Motorola, but I'm unsure what step I should take next. Root the device and blast everything I don't think I'll need off of it. Or install a stock moto rom?
MuffinGod said:
I think we're in the same boat. I have airplane mode on with wifi but it doesn't seem to stop the popup. I did get the bootloader unlocked with a code from Motorola, but I'm unsure what step I should take next. Root the device and blast everything I don't think I'll need off of it. Or install a stock moto rom?
Click to expand...
Click to collapse
Do you have the boost version? My oem unlock is still grayed out so my bootloader code us useless, but yeah I would root, and remove carrier device manager.
TheTrueJayTwenty said:
Do you have the boost version? My oem unlock is still grayed out so my bootloader code us useless, but yeah I would root, and remove carrier device manager.
Click to expand...
Click to collapse
Yeah boost varient. Mine was grayed out for a couple of days and then it wasn't.
If I understand correctly I download the firmware from lolinet. Patch it with magisk and then flash in fastboot, reboot, done. Has anyone made a detailed post on this process? I really prefer to understand each step as I do it.
MuffinGod said:
If I understand correctly I download the firmware from lolinet. Patch it with magisk and then flash in fastboot, reboot, done. Has anyone made a detailed post on this process? I really prefer to understand each step as I do it.
Click to expand...
Click to collapse
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Great guide. Thank you
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
sd_shadow said:
I have a general moto root thread.
Pretty much all the same as long as ramdisk is in the boot.img
Spoiler: Like this
Just make sure the firmware matches what is installed (device, channel, software version)
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Great guide. Thank you
Hmm... I followed steps correctly (I think) flashed img and rebooted. Downloaded root checker and confirmed had root. I downloaded a system app Uninstaller, granted root permissions and tried to uninstall carrier device manager. The app requested a reboot. Reboot completed anf now I don't have root access and the carrier app is still installed. Any ideas what I did wrong?
Re-flashed and have root again. Trying to delete system apps through root explorer results in a failure. Is there a system write protection on this phone I need to disable?
Is it safe to try:
adb shell reboot disemmcwp