Earlier today I was alerted to https://www.cnblogs.com/yanhua-tj/p/15525593.html which has the actual firehose and steps to unlock! However it seems to be in Simplified Chinese so I'll translate it here for you.
The firehose is attached below.
DISCLAIMER: I am not responsible for any damages this may cause as I am merely translating the guide, I am not responsible for you bricking your device because of a missed step so read carefully,
Also, Please backup your data beforehand as this does wipe the phone. Also please note that if you are on android 11 LG Backup will not work after unlocking, neither does the LG Bridge tool.
***IF YOU WANT ANDROID 12, UPDATE BEFORE ROOTING, I HAVE CONFIRMED IT WORKS FINE***
Requirements:
Get QPST Here
Get the FIrehose Here
Engineering Bootloader Here
Adb and Fastboot Here
Qualcomm Drivers Here (When installing make sure to select wwan)
Frp with oem unlock bit set for Verizon Here Not for demo units!
Slight knowledge of the command line
A Brain
Steps:
If you already have it unhidden go to Developer Options under Settings -> System and enable OEM Unlock as well as USB Debugging. If you don't see Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom. Verizon Users: You will not see the oem unlock option, we will fix this later in this guide.
2) Get it into 9008 Mode: (This may take several tries)
Make sure you are connected to your computer via USB.
Hold Volume Down and Power until it shuts off
Now here's the tricky part, as soon as the screen turns off, immediately start tapping volume up quickly, but do not let go of volume down and power, if you did it successfully you will see your screen is off but it appears either in Device Manager or Windows plays the Device Connected sound.
Open and Configure QFIL as shown below:
{
"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"
}
After that click Browse and select the Firehose you downloaded earlier
Next go to the Tools menu at the top then select Partition Manager (If this errors please reboot back into edl using the steps mentioned above!)
After that wait for QFIL to connect then a new window will pop up. FInd abl_a and abl_b, right click on each and click Manage Partition. First thing you want to do for each is click Read Data. This will back them up in case of anything going wrong. QFIl will tell you where it stores them. Then for each click Load Image and select the Engineering Bootloader you downloaded from before.
Once you get that done for both abl_a and abl_b click close on both the Raw Data Manager and Partition Manager and wait for QFIL to say Finish Reset to EDL in the logs at the bottom.
Now it's time to get into Fastboot.
Press and Hold Power and Volume Down for 9 seconds
Once you either see it disappear from QFIL or you hear it disconnect from your PC, let go of power, until you see Fastboot Mode on your Phone's screen.
Open the command prompt on your computer.
Once it's in fastboot verify if fastboot can see it by doing fastboot devices, if it can't see it troubleshoot here:
Check your USB Connection
Double check you installed the adb and fastboot stuff from earlier in the post
There may be a chance WIndows doesn't recognize it properly. So follow these steps:
Open Device Manager by doing Windows + X and clicking Device Manager
There may be an already open row that says Unknown Devies
Right click on android and select Update Drivers
Select Browse my computer for drivers
Select Let me pick from a list of available drivers
Select Android Device
Select Android Bootloader Interface
Click Ok on the pop up
Once that finishes double check the phone can be seen in fastboot devices
Now here comes the fun part, unlocking! Please make sure you have your data backed up.
If you are on verizon (and it's not a demo unit)
Make sure you downloaded the file from above for the unlocked frp
Do fastboot flash frp frp.img
Do fastboot reboot and let it boot into android once, no need to set it up
Reboot back to Fastboot using step 9
Do fastboot oem unlock
Select Unlock the Bootloader using volume down and power, your phone will wipe and reboot
On any other variant
Do fastboot oem unlock
Select Unlock the Bootloader, your phone will wipe and reboot
And that's it! Rooting guide will be on post 3.
If you have any questions or feel like this is too complicated, please don't hesitate to contact us {Mod edit}
Rooting with Magisk:
You need to have already done the unlock mentioned above
Go back to the guide and go all the way to the Partition Manager part, but don't flash anything.
Now find and right click boot_a, click Manage Partition Data, and click Read Data do the same for boot_b.
Wait for that to finish, when it does QFIL will tell you where it stored it.
Grab the file and place it somewhere as a backup.
Rename it to something like boot_a.img and boot_b.img
Either use an existing device with Magisk or restart your device and install the magisk app from Here (make sure to download the Magisk-v2x.x.apk)
Transfer the images you got to your phone in whatever method you'd like.
In the Magisk App where it says Magisk, click Install, then choose Select and Patch a File. Make sure to patch both boot images separately!
Wait for that to finish, after that transfer the modified image back to wherever you want to keep it. To make it easier rename it to something like MagiskPatchedBoot_a.img and MagiskPatchedBoot_b.img
Get into fastboot by Either:
Shutting the phone off, and holding volume down while plugging in the usb cable
Do adb reboot bootloader if you have adb debugging setup.
Now in the directory of your patched image do fastboot flash boot_a MagiskPatchedBoot_a.img and fastboot flash boot_b MagiskPatchedImage_b.img
Now do fastboot reboot and you're golden!
Misc Fixes:
Spoiler: Getting back the Fingerprint scanner after unlock NOT REQUIRED ON ANDROID 12 (Credits to Leronex_1)
Open the dialer and dial: ` *#546368#*600# ` | Verizon (V600VM): ##228378 (+ send)
SVC Menu > Handprint > HandID Logging = ON | ON VERIZON SKIP THIS STEP
Device Test > SAAT > Service Menu – Manual test > Optical Fingerprint test Complete the test and when a green circle shows tap it, when you see a button “pass” click it. At the end it should fail so just click the “fail” button when there is no “pass” button anymore. Start the test by clicking "start", then hold the green circle with your finger till the test finishes. On the last test it will fail so just click on "fail".
Repeat 3 times and try adding a fingerprint, if fingerprint still does not work just restart and retry again.
Spoiler: Making /system RW (Credits to Leronex_1 and lebigmac)
Download system systemrw_1.31d_BUNDLE.zip from https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
Place folder systemrw_1.31d in /data/local/tmp on the phone
Place sysrw_repair_v1.31d on your linux machine
Go to adb shell, su and then do "chmod +x /data/local/tmp/systemrw_1.31d/systemrw.sh"
Then in adb shell do cd /data/local/tmp/systemrw_1.31d and do ./systemrw.sh size=15 or 20 and wait till its done
Go to the linux machine and cd to sysrw_repair_v1.31d from step 3
Connect adb with your phone and make sure to not accidentally disconnect it (This will take a while)
In the sysrw_repair_v1.31d directory, do sudo ./sysrw_repair.sh and make sure your Linux machine has at least 25gb Storage space, this process will take more or less 30 mins depending on how fast the machine is
When its done it should start flashing in fastboot automatically.
Spoiler: Enabling VoWifi on V600EA (Credits to Leronex_1)
Make sure to follow the guide to make /system rw or else you will end up in a non bootable system!
1. Add these lines below to your build.prop (First set permissions on the build.prop so you can write it)
Code:
Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Make sure to set the Permissions back to chmod 600
2. Reboot, go to settings > Networks > Calls > Enable WIFI Calling
3. If it won't turn on by itself you might need to enter the Service menu and go to SVC Menu > VoWIFI > WIFI Calling Toggle = 1
Credit: Leronex (Discord), Leronex_1 (XDA)
Spoiler: Disabling rct (Credits to null-dev)
You must make /system RW using the guide above
1. adb shell, pm uninstall -k --user 0 com.lge.rctprovider
2. adb reboot bootloader, fastboot erase rct, Reboot to System
3. adb shell, pm uninstall -k --user 0 com.lge.srtc
4. Download and install the Magisk module: https://github.com/null-dev/lg-v60-rct-disable-magisk/raw/master/lg-v60-rct-disable-magisk.zip, then reboot the phone.
5. Delete /mnt/product/persist-lg/rct folder
Done, how to check if it is disabled? "Adb shell", "su" and "getprop | grep rct". If it shows nothing as output that means the service is not running. After that check the service menu *#546368#*600# > SVC Menu > LG RCT (Has to say Disabled)
Spoiler: Disable OTA Updates (Credits to Leronex_1)
Code:
adb shell pm uninstall -k --user 0 com.lge.lgdmsclient
On TMO After 20j:
Code:
adb shell pm uninstall -k --user 0 com.lge.android.atservice
adb shell pm uninstall -k --user 0 com.lge.gdec.client
adb shell pm uninstall -k --user 0 com.lge.lgfota.permission
adb shell pm disable --user 0 com.lge.pickme
Spoiler: Disable Smart doctor to save battery (Credits to Leronex_1)
Code:
adb shell pm disable --user 0 com.lge.phonemanagement
Spoiler: Crossflashing Guide (Credits to Leronex_1)
1. Download and install QPST, when installed launch it and select the firehose and Nand type e.g. UFS.
2. Download and install this LGUP from here: https://drive.google.com/file/d/1VxecFNYK2Lr7w1HVg-mNIGEoVa8CSHFt/view?usp=sharing . In the installer select "Install LG Drivers"
3. Put phone into edl mode, here is how: Hold Vol- and pwr, when the screen turns black keep holding them and Repeatedly press vol+ You will see "Qualcomm HS-USB QDLoader 9008" under "Ports (COM & LPT)" in device manager when it is in edl. If the screen shows anything after reboot, instantly retry again.
4. When it is in EDL Mode, open partition manager and make a backup of these partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
5. After backing up, erase the same partitions "FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.
6. Now after erasing it is sort of important to not let it boot to android, and instead boot to download mode. Here is how: force reboot with vol- and pwr button. As soon as it disconnects from windows, Release the Vol- and Power buttons and hold Vol+ to get into Download Mode.
7. When it enters Download mode, open LGUP and select partition DL. Select your favourite V60 KDZ too.
8. Click on start, then it will prompt you to select partitions that can be flashed, select every partition EXCEPT "SID_A SID_B AND ABL_A ABL_B" then confirm. (NOTE: DO NOT CLICK "SELECT ALL" IT IS BUGGED AND WILL FLASH ALL PARTITIONS, EVEN IF UNSELECTED AFTER)
9. Let it install, after that you should be done, hidden menu won't work but you can install this apk to be able to enter hidden menu and fix the fingerprint on an unlocked bootloader. https://drive.google.com/file/d/1g-7BQ_Jlmi-5tpbMg383LaiYr5YjTmqQ/view?usp=drivesdk
Reserved Post #3
looks good
v60 demo unlock boot and root
THX!
Raify4 said:
v60 demo unlock boot and root
THX!
Click to expand...
Click to collapse
This doesn't work for the demo I should have clarified
crimsonrommer said:
This doesn't work for the demo I should have clarified
Click to expand...
Click to collapse
I tried on my demo unit and it worked
Is that the 601?
Raify4 said:
I tried on my demo unit and it worked
Click to expand...
Click to collapse
Note that the verizon variant has removed the OEM unlock option from developer options, so you'll need to flash an FRP partition with the OEM unlock bit already set.
Leronex and I kinda puzzled that one out.
manywelps said:
Note that the verizon variant has removed the OEM unlock option from developer options, so you'll need to flash an FRP partition with the OEM unlock bit already set.
Leronex and I kinda puzzled that one out.
Click to expand...
Click to collapse
Yeah issue is qfil doesn't see frp so we're trying to find a workaround
crimsonrommer said:
¿Ese es el 601?
Click to expand...
Click to collapse
back cover shows lm v601u
Leronex flashed a different V60's FRP (with the bit set) on my verizon phone and then the unlock worked smoothly.
He used Medusa which can flash the FRP partition independently though.
manywelps said:
Leronex flashed a different V60's FRP (with the bit set) on my verizon phone and then the unlock worked smoothly.
He used Medusa which can flash the FRP partition independently though.
Click to expand...
Click to collapse
Yeah I know, the issue is qfil doesn't see it
Would it still be possible to update after bootloader unlock, even if it's by LGUP?
Other than that, you guys rock! Thank you for providing the translations for us mere mortals to understand
vitalez06 said:
Would it still be possible to update after bootloader unlock, even if it's by LGUP?
Click to expand...
Click to collapse
Yep! Just make sure to use partition dl and uncheck abl_a and abl_b that way fastboot remains, and you can still extract your boot partition and root again
i get this error , help
kiory01 said:
i get this error , help
Click to expand...
Click to collapse
i dont see an error
crimsonrommer said:
i dont see an error
Click to expand...
Click to collapse
same for me, actually no error but after clicked on portion manager, there is popup window appeared saying make sure correct firehose file selected, clicked ok, then screen stuck there no partition manager window appeared yet nothing in log folder as well.
Related
{
"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"
}
Micromax Bharat 1 is a feature phone with 4G VoLTE capability at extremely low cost.
Below are its basic specs:
Runs on Snapdragon 200.
Has a custom-made Android KitKat 4.4.4 based rom with a minimalist UI.
Has a 240x320 resolution display.
2000mAH battery.
Basic Notes:
To get into recovery mode: '*' + Power on
To get into fastboot mode: '#' + Power on
What will you find in this thread?
To enable adb and installation of apps from unknown sources.
To obtain root privileges.
Discussion and more ideas worth exploring
To enable installing from unknown sources and to enable adb, follow the instructions below.
Make sure you have installed all the necessary drivers.
Download and extract everything from the attachment to a folder.
Turn off your device.
Put it in fastboot mode and connect to your PC.
Once you can confirm that the device is correctly recognized, open up a powershell (Shift + Right click) in the extracted folder. (Or a terminal if you are using linux based distro).
Type in the following:
Code:
fastboot devices
fastboot boot recovery_V407.img
Your device will now reboot to recovery. The recovery I have provided is not complete. So you will not be able to do much with it on the device. However adb works. So let's continue.
Type in the following code to enable adb
Code:
adb shell
mount system
echo '' >> /system/build.prop
echo '# Enable ADB (By Ravikirancg)' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
reboot
This should reboot your device.
Once you are back in the interface of your phone, you should be able to see an icon on the status bar indicating adb. Just press the left soft key and then notifications.
Now click on the notification about adb. This should take you to the hidden Developer Settings which you could not access earlier.
Scroll down and click on "Revoke USB debugging authorisations".
Turn off Debugging and back on. This should prompt a dialogue box that asks you for providing debugging authorisations. Tick always allow and then on OK. (Enter something like 'adb devices' on the powershell if required.)
Type in 'adb devices' in powershell and it should show your devices id and then 'device' instead of 'unauthorised'
Congrats! You have now enabled android debugging on Micromax Bharat 1.
Now using this, let us enable installing apks from unknown sources. To do that follow the steps below:
Type in
Code:
adb shell settings put global install_non_market_apps 1
That's it! Go ahead and install an apk file that you downloaded from the internet or sent from another phone. You will now be able to do it.
Do note that even though you can install any app you want, it is really difficult to navigate in the app as most are not designed for non-touch screen phones. Apps like share it does work well though.
Going further, if you wish to root your phone, you will need to download the latest installation zip file, extract everything and push the su binary to its place manually. And the install the apk using adb.
Well that's it for now! Go ahead and let me know what you wish to do further! Happy Hacking!
Reserved Post
It shows adb devices attached then blank.
Ravikirancg said:
Reserved Post
Click to expand...
Click to collapse
where can I get the drivers.
Sumati59697 said:
where can I get the drivers.
Click to expand...
Click to collapse
Downlaoded the drivers via Google.
Still stuck at the same place.
Network problem
No internet working on phone after fastboot boot recovery img.v407
Sumati59697 said:
No internet working on phone after flashing recovery.
Click to expand...
Click to collapse
Who asked you to flash recovery? Just boot from it.
Data not working
fastboot boot recovery_V407.img after doing this no internet.I have usb debbugging on but after that no adb devices found on adb shell it
Shows adb device attached
Like this.I have stuck at this place.
Sumati59697 said:
fastboot boot recovery_V407.img after doing this no internet.I have usb debbugging on but after that no adb devices found on adb shell it
Shows adb device attached
Like this.I have stuck at this place.
Click to expand...
Click to collapse
Post a video. Forget about internet, Its not supposed to boot into system when you use the recovery.
ashwinprakas said:
Downlaoded the drivers via Google.
Still stuck at the same place.
Click to expand...
Click to collapse
https://androidfilebox.com/tool/minimal-fastboot-adb-driver-installer/
This version worked for me on Windows 10, all good. Thank you O.P.
android go
can android go version could come in this mobile .because android go programm is for lite hardware phone.i think there would be a custom rom for this phone as the current software is very buggy.{v407}
Gapps
What about gapps
Works like a charm, hell lot of thanks ser
Can we get system updates after doing this.
Awesome! Waiting for Android GO
Unable to enable unknown apps installation
Plz tell me full procedures to enable unknown apps installation however I have enable USB debugging
Plz help any body also who have enable it.
Thanks
bharat 1 recovery mode video tutorial
i have successfully entered into recovery mode.
video tutorial- youtu.be/7WJrvzSiWZo
how plz tell full procedure line by line i hv enable usb debugging but unable to inst
Rishabh728 said:
I don't get root but i can install Apps
Click to expand...
Click to collapse
how
plz tell full procedure line by line i hv enable usb debugging but unable to install any app
Ravikirancg said:
Congrats! You have now enabled android debugging on Micromax Bharat 1.
Now using this, let us enable installing apks from unknown sources. To do that follow the steps below:
Type in
Code:
adb shell settings put global install_non_market_apps 1
Click to expand...
Click to collapse
i have Successfully able to bring on Developer Mode ON but after that adb devices when we enter it shows list of devices attached......not the device id......
for not showing Device id this last code [adb shell settings put global install_non_market_apps 1] go going on
so please help me
---------- Post added at 11:23 PM ---------- Previous post was at 11:19 PM ----------
Rajat chandra said:
Works like a charm, hell lot of thanks ser
Click to expand...
Click to collapse
but how did u able to install app from unknown sources.........i mean developer option is on but unknown source installer still not opened.......
---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------
Sumati59697 said:
Can we get system updates after doing this.
Click to expand...
Click to collapse
nope u can get ota updates & updates will download but after that clicking on install the updates phone will reboot but new update file will not show the system update thus it will automatically reboot the phone but again ota update will pop up that means update will not happen........
unable to install Unknown app
After connecting phone in fastboot
Entering following code in command opne by shift+right click in adb folder.
'fastboot devices (inter)
fastboot boot recovery_V407.img (inter)
adb shell settings put global install_non_market_apps 1 (inter)
error come following:-
/sbin/sh/: settings: not found
How can it enable?????????????????
shahidalam31012018 said:
After connecting phone in fastboot
Entering following code in command opne by shift+right click in adb folder.
'fastboot devices (inter)
fastboot boot recovery_V407.img (inter)
adb shell settings put global install_non_market_apps 1 (inter)
error come following:-
/sbin/sh/: settings: not found
How can it enable?????????????????
Click to expand...
Click to collapse
Read the OP correctly. You are not supposed to do that. You are in fastboot only to modify the build prop and thus enable adb. To enable unknown sources, you need to be booted up into the rom and then have adb enabled.
Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button
RESERVED
Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.
I guess you can type the path to the installation file instead of dragging.
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502
TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:
Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck
very good
Need Custom rom please
nougat / pie
Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.
After downloaded, extract the ZIP anywhere you want.
You should now have a folder 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"
}
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.
-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40
Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)
-Find a device called "fastboot Gadget" or similar name with a exclamation mark.
-Right click it and click on "Update drivers..."
-Click on second option on the setup (search manually)
-Click on the second option again.
-On the list, look for Universal Serial Bus Devices and double click it
-Inside the Manufacturer list select WinUsb Device
-On the right list select ADB Device and double click it
-Click on yes
-After installed, close and its fixed!
When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
help
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
GnarlyBuzzard50 said:
i always get error remote replacing recovery not allowed something like that
what should i do
edit : its this error
remote: 'download for partition 'recovery' is not allowed
Click to expand...
Click to collapse
hey you'll need to unlock your bootloader first
FIRST BACKUP EVERYTHING USEFUL FROM YOUR PHONE, THI WILL FACTORY RESET YOUR DEVICE
after getting adb working (debug on and all that stuff)
enter in your cmd prompt
Code:
adb reboot bootloader
then wait till your phone is in fastboot mode
now you'll type in cmd
Code:
fastboot flashing unlock
read carefully what appears in your phone screen and accapt it (at your own risk, it will probably void your warranty)
now type in cmd
Code:
fastboot reboot
done
TWRP file is not working
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
I get "Unlock Failed"
When I try to enter recovery mode, it says: no command
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
KitK4t said:
Hi guys,
On this post I will share with you a method to root Wiko Jerry.
You will get a TWRP recovery installed too.
Sorry if my english is a bit bad
Sorry if the print screens if you find are in Portuguese, as it would be boring to change my Windows language.
DISCLAIMER:
I AM NOT responsible for bricked devices and lost warranties.
If you don't feel safe modifying your device DO NOT do anything.
Backup the data you have on your phone. Accidents can happen.
That said, let's go to the fun!
What you need:
Your Wiko Jerry
This TWRP 3.1.1 recovery: https://mega.nz/#!rZM2XIhY!tuneB9pGNQzhbGWz1kRY-mzeCGtRjUAP2QqX791r4Go
ADB / Fastboot on your computer. I will explain how to set it up on your PC later.
Magisk flashable ZIP. Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Connect your phone to your PC with your USB cable.
1- Preparing your PC:
If you already have ADB on your PC, you can skip this part.
After downloaded the files you need, let's get your computer ready.
You will need fastboot and ADB for this method, so download from here:
Installing ADB on Windows:
Open this link and click on SDK Platform-tools for Windows.After downloaded, extract the ZIP anywhere you want.You should now have a folder like this:
Keep the folder open (or just minimize it) and go ahead to the next step.
Installing ADB on Linux:
Run one of this commands on your terminal.-Ubuntu/Debian based Linuxes (APT):
Code:
sudo apt install android-tools-adb android-tools-fastboot
-Fedora (YUM):
Code:
sudo yum install android-tools
Test with:
Code:
sudo adb version
You should get something like this:
Code:
Android Debug Bridge version 1.0.40[/INDENT]
[INDENT]Version 4986621
2- Getting your phone ready:
To get your phone ready you need to enable ADB on Settings.
Open Settings>About phone and tap "Buid number" 7 times.
Go back one time and you sholud get a "Developer options" menu on Settings.
Open the "Developer options" and enable "USB debugging" option.
Now you have ADB enabled on your device.
3- Installing TWRP on your phone
Do you remember the TWRP file you downloaded before? Now you will need it.
-Copy the TWRP_3.1_JERRY.img file to your platform-tools folder.
-Rename the file to recovery.img.
-Open a command prompt.
-On command prompt do this to open your platform-tools folder on it:
Code:
cd INSERT PATH TO YOUR platform-tools FOLDER
Now, unlock your phone and run this command:
Code:
adb devices
It should appear something like this on your PC:
Code:
List of devices attached
<your-device-id> offline
And this on your phone:
On that window, check the box and tap OK. This will allow your phone to communicate with ADB running on your PC.
Check if everything is ok doing the "adb devices" command again. If it is ok, this will show up:
Code:
List of devices attached
<your-device-id> device
Now, on your command line run the command:
Code:
adb reboot-bootloader
Your phone will reboot in fastboot mode. It should look like this:
Run this on your command line:
Code:
fastboot flash recovery recovery.img
If you get <waiting-for-device> on command prompt, check this:
-Open Device Manager (Win key+X, click on Device Manager)-Find a device called "fastboot Gadget" or similar name with a exclamation mark.-Right click it and click on "Update drivers..."-Click on second option on the setup (search manually)-Click on the second option again.-On the list, look for Universal Serial Bus Devices and double click it-Inside the Manufacturer list select WinUsb Device-On the right list select ADB Device and double click it-Click on yes-After installed, close and its fixed!
When the command finishes, you should get this:
Code:
Sending 'recovery' (12866 KB) OKAY [ 0.550s]
Writing 'recovery' OKAY [ 0.762s]
Finished. Total time: 1.317s
Congratulations! Now you have TWRP on your phone!
4- Booting into TWRP and root the phone with Magisk
Now you need to turn off your phone. You can just take the battery out and put it again.
This phone has a weird way to boot into the recovery. You need to press the power button and a second later, the VOL+ button.
The Wiko logo will appear and the phone MUST NOT VIBRATE. If it vibrates, the normal Android will start.
Do this procedure anytime you want to go into TWRP.
Connect your USB cable.
Tap "Keep Read Only"
In your PC, go to This PC and open the JERRY device.
Copy the previously downloaded Magisk ZIP file into the Internal Storage.
In TWRP, tap Install
Search for the Magisk ZIP in the file explorer.
Swipe to confirm the flash
Tap Home button
Tap Reboot
Tap System
Android should boot normally
Warning: It could take a few seconds to Magisk Manager to appear on apps list.
Congratulations! You have done it! You have TWRP and Magisk!
Click to expand...
Click to collapse
<thanks man, worked fine for me.
just like he says...
adb reboot-bootloader
fastboot flash recovery <pathoftherenamedTWRP.img>
Take the battery out, back in
press and hold start button, sec later vol down button too
Now TWRP should start
read only
transfer the magisk.zip file to internal storage(PC)
install button(TWRP, Smartphone)
tap on the magisk.zip file and swipe to accept
wait till its done
press on reboot
done
Zaki4t said:
is this recovery image meant for the SPD or the MTK variant?
Tried this on an SPD Jerry & it didn't work
Any other help?
Click to expand...
Click to collapse
Worked for me. Where can i see which i have. maybe i can help
z0mb13m4ch1n3 said:
Worked for me. Where can i see which i have. maybe i can help
Click to expand...
Click to collapse
and if you messed up(like I do in my first try) here...
Wiko Mobile: Kundenbereich / Verbindung.
customer-de.wikomobile.com
take out the battery, theres the imei number
youll download a .exe file. stressed me in linux and lend a win 7 laptop. 5min or so and i had a factory fresh jerry to try again
The problem is there is no WinUsb there i dont have it.
Hi, I have a big trouble i followed all the instructions and everything was just fine, until the step 4- Booting into TWRP and root the phone with Magisk, after a take out and put the battery again in the cell, it doesn't boot from logo, just reset an reset, I already try o hard reset, try to enter TWRP, I try all kind of button combination, nothing works can someone helpme. Thks...
Hi,
For background.. I have rooted and customized several phones so I am not a total n00b. But, I tend to keep my phones for a while, so I do this every 3 years or so and I don't remember the order to do it.
I have a "new" Pixel 3a sitting here.
I want to end up with a Rooted 3a with LineageOS and xPosed Framework (for xPrivacy LUA) and AFWall.
There are step-by-steps I can search for for each of those but I'm not sure on what order and also what recovery to use. Previously I have used TWRP. Also, previously I used edXposed and now there is another option for that too.
Much help if someone can give me the order to do these!
A) To unlock bootloader
Run through the initial setup if you haven't already, if you haven't don't bother logging into your google account.
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt type into the cmd window
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
fastboot devices
See if it lists a device, if not, you need to install the latest drivers to your PC (google adb). If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Your bootloader is now unlocked. Reboot.
B) To root
Grab the system image from https://developers.google.com/android/images unzip the folder and inside of it you will find another zip. Open that 1,6 Gb zip file up, pull the boot.img out and copy it your phone.
In your case you would grab LineageOS i guess.
Install Magisk app on your phone and use it to patch that and then copy patched boot back to your PC.
Open the "flash-all.bat" and remove the -w from the end (this is important as it stops your device from being wiped) save the bat file,
If updateing, remove all Magisk scripts. Systemless may stay.
Now type into the cmd window:
adb reboot bootloader
flash-all.bat
The update may take 180 seconds and then your phone will reboot. Disconnect the phone from PC. Please be patient while rebooting with G underline going on for 3 minutes.
Flash the patched boot image.fastboot reboot
Now type into the cmd window:
adb reboot bootloader
fastboot getvar current-slot
(in this case partition b is active)
fastboot flash boot_b magisk_patched.img
fastboot reboot
In case boot fails… (no valid slot to boot), please flash again above.
TROUBLESHOOT
If you bootloop on "G"
Hold power to reboot
Press power to pause
volume up + power to bootloader mode
Flash stock boot.img
Or try this:
connect your phone to your computer (while bootlooping or stuck on loading)
run the command: adb wait-for-device shell magisk --remove-modules
hold your power button until the phone restarts,
run the command again while the phone powers up
it will restart itself and if you're lucky it will boot properly this time
markd89 said:
and also what recovery to use. Previously I have used TWRP. Also, previously I used edXposed and now there is another option for that too.
Click to expand...
Click to collapse
TWRP recovery does not work on Android 10+ but it is really not needed for root.
I have not used Xposed for many years, but generally everything is done through Magisk addons now.
Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/
V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.