Related
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!
Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.
RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks
I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.
To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!
To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)
The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.
To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)
Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed
cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!
To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!
What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.
To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?
To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?
What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App
A few months ago I decided to try and root my Nexus 7 (2013) tablet. At this time I simply cannot remember what process I used but all I know is that everytime I try to power it on the system start screen comes on where it asks what country you're in and so forth. But I also get the following Pop Up Error message "Unfortunately, Google Keyboard Has Stopped" and an "OK" button. When I click on OK the error message simply pops back up in a never ending loop. It stops at the SELECT WI-FI screen and won't let me input the access code because of the Pop Up Error message.
Does anyone have any idea how to completely wipe the system and bring it back to stock or just to the point I can do "anything"?
Thank you in advance for your assistance!
Boot into fastboot by holding volume down and power while the tablet is off. Scroll through the options with volume keys. When you see the option recovery mode at the top of the screen, press power. This will boot you into recovery. From there, there will be several option. One of which should be a hard reset. navigate using the volume keys. You should be OK from here.
sent from my nex7
Thank you for your reply but unfortunately this doesn't work. It puts me right back to where I always end up and still get the Error Message stated above.
I've been working on this for a few hours now and nothing! It basically says I don't have a Keyboard installed after I do anything. If I Factory reset it I get the same Error Message about no keyboard.
Any ideas? PLEASE HELP!
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
mugzylol said:
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
Click to expand...
Click to collapse
Thank you for your reply. I greatly appreciate you taking the time. I am at wits end at this point and simply need it to run again. Can you talk me through loading whatever to get it back to new? I'll take anything at this point. Everything is backed up so I have nothing to lose. How can I load the original image? (non rooted)
Thank you!
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Stuck
mugzylol said:
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Click to expand...
Click to collapse
OK, a couple of things;
1. I'm using a MacBook Pro. Does this make any difference? (It says I don't have to download any drivers using a Mac but other than that is there any differences?)
2. I'm stuck at ..... Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on "open new command window here". Now put your tablet into fastboot mode. Type "fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Everything I do doesn't work. When I hold down Shift and Right-Click on the Platform Tools Folder I do not see "open new command window here". Is this the "platform-tools folder under the SDK folder?
Do you have any windows computers because this will not work without one
sent from my nex7
---------- Post added at 08:27 AM ---------- Previous post was at 08:25 AM ----------
This is because Mac computers do not execute batch scripts and the fastboot commands are made to execute through a command prompt rather than a Linux terminal
sent from my nex7
I honestly made this way too complicated. Just run through setup without using the keyboard. Find an unprotected network (like McDonald's) that works and find a way to get your hands on an apk of any keyboard and install it. I'm not quite sure how you can get a download link to a keyboard with no account (yet) and no keyboard but there must be a way. Its a simple issue that causes so many problems. So in a nutshell, if you can find a way to install an apk of any keyboard, your good
sent from my nex7
i was trying to flash the 2.0 update to my watch. i was in command prompt and was typing in the codes then my watch rebooted into recovery i was able to get my watch back into fastboot mode but now adb isnt recognizing my device and the watch doesnt have any software on it what do i do ?!
Same for me what do I do ? Now when I turn on recovery appears for 2 sec then black screen and over and over again looks like I don't have software installed what do I do ?
I also got the same issue I clicked on recover in the bootloader as everytime I tried to run the following step: Execute the flash-all script by typing flash-all.sh or, in the case of Windows, flash-all.bat.
Set up the watch and begin testing it would just say adb does not recognise this command.
I am now stuck in a cycle of not being access the device in ADB to flash say TWRP or get it to even boot, the only thing I can do is get it back to the boot loader.
OK, so the good news is we didn't brick out watches
First thing is first you will need to get back into the watches boot-loader to do this follow the steps below:
1. Hold the power button down until the Huawei logo show's up
2.As soon as the watch vibrates let go of the power button and do one quick short press of the power button again
3. If you did this right the boot-loader should appear if not you will feel another vibration and will have to start over
Now that you are back in the Boot-loader put the watch back on the dock and plug it into your pc. Fire up ADB and fastboot minimal (Get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Install this and drag the contents of the Sturgeon-nvd file you downloaded from the android site (this is the Android Wear 2.0 preview image) into the same folder that the minimal ADB is installed in like so:
http://i.imgur.com/Vw8sUo1.png
Now double click the Flash-all.bat file in the folder and you should see it processing on the ADB window.
Did you unzip the folder and placed it in the ad folder location?
Just an FYI: ADB is not what is used to flash .img files. Its fastboot. When you are in bootloader mode are you in fastboot mode and would use fastboot commands. Its normal for ADB not to see a device in fastboot mode.
I see a lot of people have this same problem for different reasons and the solutions are seemingly all over the place if any
My phone recently lagged out and i had to restart it, which is when my issue happened.
I know my space was running low so im assuming that may have something to do with why it happened.
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else. I am new to this and have absolutely no idea what im doing. So ive googled as much as i could but some things arent making sense, id appreciate some help or a step by step
some info
my phone is 100% stock aside from my nova home launcher.
I dont not have custom bootloaders
my phone has a password, idk if that matters but just in case
my phone is not jailbroken (i think is the term?)
I did have USB debugging set already, and I BELIEVE i had developer mode enabled
thats about it for the phone info
In the bootloader main scree, it stats im in fastboot mode, secure boot yes, device state, locked
What ive tried
-I have tried the manual OTA install via the adb stuff
i got success 0 but upon restart, nothing changed and i was still stuck
-i tried the flash steps
but i get "flashing is not allowed in lock state pixel 2"
ive tried to use a pull command via adb, but it said some strings were incorrect? I just copy pasted a command from a similar post, it may not have been catered to my situation fully so i dont know about that
Is there any steps i can take to simply either recover my photos before i factory reset, or reset without wiping, or even maybe delete some files to make space via something somehow?? I just need my data, the phone itself i can replace
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Edmontonchef said:
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Click to expand...
Click to collapse
i turned that off initially but checked the site just in case, theyre not backed up ):
Sui77 said:
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Click to expand...
Click to collapse
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
buninthesun said:
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
Click to expand...
Click to collapse
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Edmontonchef said:
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Click to expand...
Click to collapse
the OTA sideload has a success of 0 but nothing happens beyond that, the phone still gets stuck at loading
does 0 mean it should have worked? Any idea why nothing changed?
Sorry for the problems.
My bootloader is unlocked, so that might be the reason.
buninthesun said:
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else.
Click to expand...
Click to collapse
Try the following.
1. Download the latest ADB and Fastboot binaries from the links at this page.
2. Extract the zip file you just downloaded to a directory on the root of a drive. For example, I have my copies of ADB and Fastboot stored at a directory I created, D:\ADB.
3. Open a command prompt, not a powershell window, and navigate to that directory using DOS commands.
4. Enter the bootloader on your device and connect your device to your PC.
5. Type "fastboot devices" to make sure the P2XL appears.
6. If it does, type the following commands:
fastboot getvar all
fastboot --set-active=a/b
fastboot reboot
The idea here is to get you into the device by using the second partition. To do this, you need to find out which slot you are currently using, A or B, and set the active slot to the OTHER partition. "fastboot getvar all" will tell you which slot is currently active. "fastboot --set-active=a/b" will change the active partition to the currently unused one. For example, if the active slot is currently a, you would issue the command "fastboot --set-active=b" to switch to the other partition, and then reboot.
Moral of the story here is unlock your bootloader and leave it that way.
So much easier getting out of trouble
I need help unlocking bootloader on my new Revvl 6 Pro 5g, this is my first mtk device, and I'm a Windows guy and I'm lost on the whole mtk client tool and python.
Any and all help would be a phenomenal help!
I think this phone would have a lot more potential with a gsi running on it!
The T-Mobile Revvl 6 pro 5g is made by Wingtech, code name: Augusta and model # is TMAF035G. I dunno if that's of any help but after all my research that's all I know that's 100% fact!
Help your fellow human geek out to enjoy this phones potential!
sent you pm
_hollywood_ said:
sent you pm
Click to expand...
Click to collapse
Id also like that PM
KenzieAon said:
Id also like that PM
Click to expand...
Click to collapse
sent...
_hollywood_ said:
sent you pm
Click to expand...
Click to collapse
Can you also send to me? I'm trying to root my Revvl 6 with Mtkclient on mac. I have the GUI showing but can't get it to detect my phone
androidn00b11 said:
Can you also send to me? I'm trying to root my Revvl 6 with Mtkclient on mac. I have the GUI showing but can't get it to detect my phone
Click to expand...
Click to collapse
It's starting to look like I need to put together a guide...
I don't know how to do this on a mac. And I didn't like using the GUI on mtkclient, it would recognize the device but sometimes wouldn't connect.
I suggest you download the liveDVD from the mtkclient readme (https://github.com/bkerler/mtkclient), put it on a bootable usb stick and run it from there. This is the setup that worked best for me, better than on windows anyway.
Also, read this (https://github.com/bkerler/mtkclient/issues/79). The REVVL 6 Pro 5G has an A/B setup, and unlocking it is not really explained in the current readme. Basically, you need to find out what slot you are booting from (boot_a or boot_b) and flash accordingly. Don't flash both slots, if something goes wrong you might want a slot to fall back to.
From adb do:
adb reboot fastboot
wait for your phone to boot into fastboot mode, and then:
fastboot getvar current-slot
That should tell you what your current slot is.
In order to get mtkclient to connect I booted into the liveDVD opened up the terminal and entered
python mtk r boot boot.img
It will keep looping, looking for your device and give you time to get your REVVL 6 Pro connected with the right button combo (start with power off, then volume down & plug in usb). When it connects a bunch of information will scroll down the screen. It will look for a "boot" partition but won't find one and will show an error, this is ok though. It's connected and you can begin flashing to your hearts content.
IMPORTANT!
Before you go any further make a backup with:
python mtk rl out
This will dump all partitions to a folder "out" on the computer. Save this somewhere, it is your backup.
You may not want to back up the entire userdata partition (it's huge and may take 4 hours to copy, thanks to @threeeye see post 14 below) so when it gets to that you can hit control+c to stop and then backup any remaining partitions manually with this format:
If you don't want to backup userdata folder then try this:
python mtk rl out --skip userdata
Back up individual partitions with this:
python mtk r partitionToBackup partitionName.bin
example: python mtk r vbmeta_a vbmeta_a.bin
The information for unlocking and rooting is in the links above.
Make a backup BEFORE you unlock and root!
Thanks _hollywood_. I got the slot (b), but am not able to get mtk to find the device, it continues to loop. Any tips of figuring out the "right button combo"?
androidn00b11 said:
Thanks _hollywood_. I got the slot (b), but am not able to get mtk to find the device, it continues to loop. Any tips of figuring out the "right button combo"?
Click to expand...
Click to collapse
Start with the device off and unplugged from the computer, then hold the volume down button while you plug in the usb. I'm not 100% sure now if that's the correct combo, it's been a while since I did it. If that doesn't work maybe try holding the vol up and plugging in the usb?... but I think that takes you into recovery.
I've been trying different GSIs and found CRdroid runs best, with fewest errors, but I'm not able to make calls, and only sometimes send / recieve mms. Maybe I got something wrong with the phh treble settings? I'm having those issues regardless what GSI I flash.
Phones vary GSI friendly, booted and ran every GSI I flashed!
Does anyone have a backup of the boot_a.img? Long story short i've bricked my phone and i dont have a backup anymore
Really a whole stock rom would be best if you can, thanks in advance
_hollywood_ said:
sent you pm
Click to expand...
Click to collapse
_hollywood_ said:
sent you pm
Click to expand...
Click to collapse
May I also get that pm as well plz?
Rickybud99 said:
May I also get that pm as well plz?
Click to expand...
Click to collapse
Everything you need is in post #7 above
_hollywood_ said:
Before you go any further make a backup with
Click to expand...
Click to collapse
Fist, thank you for publishing this guide!
I bricked my Xperia 1 III today, and I rushed to T-Mobile to get a cheap replacement phone and I got this phone (but I still need root to function),
2nd, you failed to mention that backing up the phone with:
Code:
python mtk rl out
(yes, I wanted to backup the userdata as well) would take more than 4 hours... LOL
threeeye said:
...you failed to mention that backing up the phone would take more than 4 hours... LOL
Click to expand...
Click to collapse
Lol, sorry about that!
edited post #7
FOR THOSE IN NEED OF GUIDANCE HERE IS A GUIDE:
*TMOBILE REVVL 6 PRO 5G(TMAF035G) NORTH AMERICAN(NA)*
Step 1(DRIVERS & STOCK FIRMWARE):
Python
BE SURE TO TICK THE BOX THAT SAYS ADD PYTHON TO PATH and install.
Download and install mediatek drivers from here:
Mediatek USB drivers
Download and install UsbDk from here:
UsbDk
Download MTK client from here:
MTK client
and extract to the desktop. Open the folder and move everything to
C:>Users>[username]>AppData>Local>Programs>Python>Python310
In the 310 directory press Alt + D to highlight your directory path and type CMD and hit enter. This opens a command prompt in the Python310 directory.
In cmd type this command without "":
"python setup.py install"
Go make a sandwich. Preferably turkey with mustard.
When you finish your sandwich, come back and type this command without "":
"python -m pip install -r requirements.txt"
Do not exit the command window.
Step 2(REBOOT INTO EDL MODE TO BACKUP):
Make sure the Phone is OFF and Disconnected
On PC paste the following command to the command window:
"python mtk rl backup --skip userdata"
hold Volume + and Volume - buttons together while connecting usb cable to Phone
Let go of buttons after the backup process begins
Wait for Process to Complete
This processes will take about 30 mins to finish backing up the phone
*****If any error stop the process (Handshake Error, LIB Error,Usb Error,Enumeration Error etc)UNINSTALL AND REINSTALLUSBDk***
Step 3(EXTRACT BOOT.IMG):
Unplug the Phone
Make sure the Phone is OFF
paste the following command to the command window to extract boot image :
"python mtk r boot boot.img"
Hold Volume + and Volume - buttons again to Enter EDL Mode while connecting USB
Let go of buttons and Wait for Proces to Complete
The boot.img will be located in the mtkclient-main folder
Step 4(*MANDATORY*WIPE DATA FROM PHONE):
**This will Erase All userdata and wipe the phone clean***
Unplug the Phone
Make sure the Phone is OFF
Enter the following command into the command window:
"python mtk e metadata,userdata"
Hold Volume + and Volume - buttons again to Enter EDL Mode while connecting USB
Let go of buttons and Wait for Process to Complete
This command will result in a clean wipe of the phone
reboot to android os to make sure phone is still functional
Step 5(UNLOCK BOOTLOADER FOR TMOBILE REVVL 6 PRO 5G):
BOOT into android
Go to Settings then About Phone then Tap Build Number 5 times until Phone say "you are now a developer"
Go to Settings again then System
Go to Developer Options
Select OEM UNLOCKING
Now Make sure Phone is OFF
Enter the following command into the command window on PC:
"python mtk python mtk da seccfg unlock"
Hold Volume + and Volume - buttons again to Enter EDL Mode while connecting USB
This will unlock the bootloader
Let go of buttonsand Wait for process to complete
Reboot phone and the phone should state the following:
On the splash screen you will see system type:
"Orange State
Your device is corrupted. Device has been unlocked and cannot be trusted. Press Power key to boot.
Will Reboot in 5 seconds"
****DO NOT SKIP OTHERWISE YOU WILL BRICK THE PHONE****
Make sure to Power OFF the phone, Unplug from PC and Wipe it again with the following command from earlier pasted into the command window:
"python mtk e metadata,userdata"
Reboot the phone
Press power button once while TMOBILE LOGO on the screen to boot up to android
Step 6(ENABLE ADB DEBUGGING):
Go to Settings again then System
Go to Developer Options
Enable USB Debugging
Connect Phone to PC
Step 7(INSTALL MAGISK AND PATCH BOOT.IMG TO PHONE)
Download Magisk from here:
Magisk
Move it to your phone and install. You'll need to allow the installation from unknown sources.
Got to mtkclient-main folder to locate boot.img that you extracted from the phone earlier
Transfer boot.img to your phone's storage
Open Magisk and Tap Install then Tap Select and Patch a File
select the boot.img
The tap let's begin
Check the Downloads folder in your Phone
Then transfer patched image file to your pc
it should be named "magisk_patched-[######]_#####.img"
Step 9(SETUP ADB ON PC THEN REBOOT TO FASTBOOT):
Download sdk platform tools here:
sdk platform tools
Extract.
***ADD THE PATCHED FILE FROM EARLIER INTO THE EXTRACTED FOLDER***
Navigate to the platform tools folder and type Alt+D to highlight directory and type CMD to open a cmd window in platform tools.
Connect device to pc and choose file transfer.
Enter the following command without ":
"adb devices"
A prompt will appear on your phone, click allow.
Enter the following command (again) without ":
"adb devices"
Enter the following command to reboot into Fastbootd:
"adb reboot fastboot"
Keep the Phone connected to PC
Phone will reboot to Fastbootd
Step 9(FLASH THE PATCHED BOOT IMG):
While Phone is Still Connected
Enter the following commands to command window from previous step:
fastboot flash boot magisk_patched-[######]_#####.img
Step 10(REBOOT THE DEVICE):
Unplug and the device and select reboot system now in fastboot
YOU ARE NOW ROOTED AND BACKED UP
ADDITIONAL STEPS BELOW ON HOW TO RETURN TO STOCK:
Step 1(OPEN THE BACKUP FOLDER OR DOWNLOAD STOCK FIRMWARE):
Download and Extract The Stock Firmware below
Here is the Stock Firmware of the TMOBILE REVVL 6 PRO 5G:
Tmobile Revvl 6 Pro 5G stock firmware:
MT6833_TMOBILE_REVVL_6_PRO_5G_STOCK_FIRMWARE.zip
Shared with Dropbox
www.dropbox.com
Place the Extracted folder into the mtkclient-main folder
Type CMD into the navigation bar in File Explorer
Paste the following command into the command window:
python mtk wl "Paste the directory of the extracted folder"
This process will take up to 30 mins so wait awhile for it to finish
If you made a backup from earlier do the following:
Type CMD into the navigation bar in File Explorer for the mtkclient-main folder
Paste the following command into the command window:
"python mtk wl "Paste the directory of the backup folder"
UNPLUG phone then turn it on should be back to stock
Does anyone have the boot.img? No such image on my computer and yes, I waited almost an hour for this file to be created and got confirmation and its nowhere to be found.
@unsmashed91 run this command from mtkclient-main folder "python mtk r boot boot.img" then hold down vol + & vol - then plug in the phone and let go of the buttons once the command initiates the process. The boot.img file will be in the C:\Desktop\mtkclient-main folder after the command is completed.
or you could download the stock firmware I uploaded and extract my boot.img
_hollywood_ said:
It's starting to look like I need to put together a guide...
I don't know how to do this on a mac. And I didn't like using the GUI on mtkclient, it would recognize the device but sometimes wouldn't connect.
I suggest you download the liveDVD from the mtkclient readme (https://github.com/bkerler/mtkclient), put it on a bootable usb stick and run it from there. This is the setup that worked best for me, better than on windows anyway.
Also, read this (https://github.com/bkerler/mtkclient/issues/79). The REVVL 6 Pro 5G has an A/B setup, and unlocking it is not really explained in the current readme. Basically, you need to find out what slot you are booting from (boot_a or boot_b) and flash accordingly. Don't flash both slots, if something goes wrong you might want a slot to fall back to.
From adb do:
adb reboot fastboot
wait for your phone to boot into fastboot mode, and then:
fastboot getvar current-slot
That should tell you what your current slot is.
In order to get mtkclient to connect I booted into the liveDVD opened up the terminal and entered
python mtk r boot boot.img
It will keep looping, looking for your device and give you time to get your REVVL 6 Pro connected with the right button combo (start with power off, then volume down & plug in usb). When it connects a bunch of information will scroll down the screen. It will look for a "boot" partition but won't find one and will show an error, this is ok though. It's connected and you can begin flashing to your hearts content.
IMPORTANT!
Before you go any further make a backup with:
python mtk rl out
This will dump all partitions to a folder "out" on the computer. Save this somewhere, it is your backup.
You may not want to back up the entire userdata partition (it's huge and may take 4 hours to copy, thanks to @threeeye see post 14 below) so when it gets to that you can hit control+c to stop and then backup any remaining partitions manually with this format:
If you don't want to backup userdata folder then try this:
python mtk rl out --skip userdata
Back up individual partitions with this:
python mtk r partitionToBackup partitionName.bin
example: python mtk r vbmeta_a vbmeta_a.bin
The information for unlocking and rooting is in the links above.
Make a backup BEFORE you unlock and root!
Click to expand...
Click to collapse
How do I perform a Network Unlock on My Revvl 6 Pro 5G
KutiFela said:
@unsmashed91 run this command from mtkclient-main folder "python mtk r boot boot.img" then hold down vol + & vol - then plug in the phone and let go of the buttons once the command initiates the process. The boot.img file will be in the C:\Desktop\mtkclient-main folder after the command is completed.
or you could download the stock firmware I uploaded and extract my boot.img
Click to expand...
Click to collapse
Thanks, I actually got it later that day probably using what you mentioned in a different tutorial. The device is now rooted. Anyone know of any possible opensource ROM of any kind that would work on this phone? Or TWRP? Other than that Root seems to be pretty useless on this thing. I can debloat Google via ADB, but thats about it, no R/W access since its stock with Root.