Related
[Edit] 2/05/2011: Use this new guide instead: http://forum.xda-developers.com/showthread.php?p=11087674#post11087674
[Edit] 1/13/2011: If you are on stock 2.2.1 FRG83D, click here to for SuperOneClick Root !
{
"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"
}
*
So I recently decided to take my 100% stock Nexus One to Sense UI and I've documented every single step of the way. I've written this guide for two reasons. First, this entire process is scattered around in dozens of threads, written by equally as many people. Not only that, but most people in these threads assume that you know by heart exactly what adb, fastboot, recovery, and others are all about. Second, to put it bluntly, most people are pretty terrible at writing documentation. Writing down what you did so other people can follow seems extremely difficult for many people. Luckily, this is a skill I am good at. So here is a full consolidation of all the information, re-writtern for clarity as I went along step-by-step, from my many hours of attempting to bring my Nexus One from 100% stock to Desire's Sense UI. (Edit: Some people have said they'd run through this guide in 20 minutes!! It might look like a lot, but a lot of steps take a few seconds.)
Disclaimer:
You agree that by doing this process, I'm not responsible for any bricked devices.
Unlocking the bootloader will void your warranty.
This process will erase all of your phone's data.
Please don't copy/paste this elsewhere (to prevent having outdated info); just link back.
If you need immediate help, these guys might be able to help -> http://webchat.freenode.net -> Channel "modaco".
And this guide is written as if you are using Windows XP.
*(Yes, the above image of Google's campus is totally unrelated, but totally cool!)
Note: the notifications tray is personally modified
-------------------------
Backup [Optional]
On PC: www.gmail.com -> Contacts -> Export, choose Google CSV
On N1: Market -> AppMonster (or any other Backup application you prefer) -> Backup all apps
(If you want/need to backup sms etc, I don't know what non-root app does this)
Remove any authenticators etc
Downloads
Download nexus-addon-0.1-signed.zip, (From thread: CyanogenMod-5)
Download Desire Sense UI OR CyanogenMod:
Sense UI:
Download the latest version here: MoDaCo Custom ROM Desire Port (Choose with MoDaCo Additions, without A2SD)
Alternate download location (mirror) for r21: alpha-r21-update-modacocustomrom-nexusone-desire-withadditions-sig.zip
Cyanogen Mod:
CyanogenMod
Download the "Google Addon" as well
Don't download any "radio" updates unless you know what you're doing! (I would highly advise against it!)
Place both zip files (3 for Cyanogen) on N1's sdcard (don't unzip)
Setup SDK
Download android-sdk_r06-windows.zip
Unzip to C:\ drive so it looks like C:\android-sdk-windows\
Run SDK Setup.exe
Double click everything so it has a red X except for green check mark next to "USB Driver Package"
(Click for larger image)
Install
On N1: Settings -> Application -> Development -> enable USB debugging
Connect phone to PC, do not mount
New Hardware Found -> Point the install location to C:\android-sdk-windows\usb_driver\
(Click for larger image)
PC: Start -> Run -> cmd -> press Enter. A black window should appear.
Type: cd C:\android-sdk-windows\tools
Press Enter
Type: adb devices
Press Enter
(Click for larger image)
- It should say something similar to "HT123P123456 device" (this is your phone's serial number).
- If it says "cannot find" or "invalid path" etc, make sure you're typing *exactly* what the green text above says.
- If it says something else, try to reinstall the USB Driver package and restart your PC.
- If it still doesn't work, reply to this thread and say "adb devices does not work. When I type 'adb devices', it says _______________. My PC is running _______________." [Choose one: Windows XP | Windows Vista | Windows 7 | Mac | Linux]
If it works, your PC is correctly recognzing the phone. Continue on to the next step!
Unlock Bootloader
Turn phone off -> Hold Trackball, then hold Power until white bootloader screen shows up:
(Click for larger image)
FASTBOOT should be highlighted. Press the Power Button to go into Fastboot.
PC: Start -> Run -> cmd -> press Enter. A black window should appear.
Type: cd C:\android-sdk-windows\tools
Type: fastboot devices
- Note: Mac users need "fastboot-mac", available here: http://developer.htc.com/adp.html
(Click for larger image)
- It should say something similar to "HT123P123456 fastboot" (this is your phone's serial number). If it doesn't say this, something is wrong. Make sure you pressed the Power Button to go into FASTBOOT.
- If you are typing fastboot devices and it just returns a blank line or ???????? (ie Windows 7 64-bit users), try using USB drivers in the PdaNet install: http://www.junefabrics.com/android/download.php
- If that doesn't work, try not pressing the Power button to enter Fastboot. A few people have had it work that way. (Or may have been holding the Power button for too long.)
- If you can't get this step to work, reply to this thread and say "When my phone is in the bootloader and I type 'fastboot devices', it says __________ instead."
Type: fastboot oem unlock
Read what the screen says. (Decision time!) (All data will be wiped here)
(Click for larger image)
Your phone should reboot with a picture of an open padlock under the Google logo. If so, everything is good so far!
(Click for larger image)
Flash Recovery - (Update 09/01/2010: this may not work on SLCD Nexus Ones. Need an SLCD-supported recovery and then a ROM with SLCD support)
Turn phone off -> Hold Trackball, then hold Power until white bootloader screen shows up
FASTBOOT should be highlighted. Press the Power Button to go into Fastboot.
PC: Download latest .img file - Amon_RA's Recovery Image
Place img file into C:\android-sdk-windows\tools\
PC: Start -> Run -> cmd -> press Enter. A black window should appear.
Type: cd C:\android-sdk-windows\tools
Type: fastboot devices
It should say something similar to "HT123P123456 fastboot" (this is your phone's serial number). If it doesn't say this, something is wrong. Make sure you pressed the Power Button to go into FASTBOOT. If you can't get this step to work, reply to this thread and say "I'm trying to flash the recovery image. I unlocked my bootloader but fastboot devices doesn't work anymore. When I type 'fastboot devices', it says __________ instead."
Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img (Note: the underlined part may be different depending on what you downloaded.) (Tip: On Windows XP, you can press tab to auto-complete the filename.)
It should say: sending 'recovery' (3962 KB)... OKAY . . . . . writing 'recovery'... OKAY This should take a few seconds.
(Click for larger image)
If it doesn't work, try using Superboot (ignore this unless you're having issues flashing the Recovery):
Modaco's Superboot -> "Before download, check your device 'about' screen to determine whether you need a superboot for 'ERD79' (the original shipping ROM, 'ERE27' (the official update) or ERE36B (the new leaked update)."
Turn phone off -> Hold Trackball, then hold Power until white bootloader screen shows up
Don't touch anything
Open superboot file on PC
Try to Flash Amon_RA's Recovery again
If it still doesn't work, reply to this thread and say "When I tried to flash the recovery file, it said ________________ instead."
If flashing the recovery was successful, use the menu options to boot directly into recovery, or turn the phone off and continue on with next step!
Root
Turn phone off -> Hold Volume Down, hold Power button
Press Volume Down to highlight Recovery -> press Power to select Recovery. Your screen should look like this:
(Click for larger image)
Do this step only if you didn't use Superboot: Use trackball -> "Flash zip from from sdcard" -> nexus-addon-0.1-signed.zip
- If you get a Triangle with a ! in the middle alongside an Android for 5+ minutes, you MAY have to remove battery and re-flash recovery (I had to do this once.) (Make absolutely sure that nothing is happening on your phone, as removing the battery when it's doing something can cause a brick.)
- Alternatively, try the optional Superboot method, and then re-flash Amon_RA's recovery image.
Select Reboot.
Install ROM (Sense UI, Cyanogen, etc)
Turn phone off -> Hold Volume Down, hold Power button
Press Volume Down to highlight Recovery -> press Power to select Recovery
Backup/Restore -> Nand backup
Wipe -> Wipe data/factory reset
Wipe -> Dalvik Cache
Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
- If you get an error such as "E:\Can't open /sdcard/[blah].zip (bad)", the file is probably corrupt. (Modaco has had some issues with this recently; I don't know why.)
- If you want to make sure, use http://portableapps.com/node/19346 and drag the zip file onto it to verify the MD5 sum. For r21 with MoDaCo Additions, the MD5 should be: e5eb15ea971b220ffdfcac8f56037013
If you're using Cyanogen, flash the Google Addon.
Reboot
- If a picture of an Android falling out of a box shows up, something went wrong. Just wait for it to reboot into recovery. (Good you made a backup! Just in case.)
- Go back into recovery, Wipe all data again, Wipe Dalvik/cache again, and reflash the Sense ROM.
- If it still doesn't work, reply to this thread and say "I keep getting the Android falling out of the box when flashing the Sense ROM, even after repeated wiping."
If successful, a white HTC splash screen appears. It should take about 2-3 minutes to load into Sense.
If it gets past that, congratulations! You made it!
Post in this thread that it worked! And if you're feeling generous, feel free to send me a beer!
And finally, enjoy and have fun!
-->
--------------------------------------------------
Install a Different ROM
If you want to install a new version of a ROM, switch to a different ROM like Cyanogen, etc, only repeat the "Install ROM" section. The only difference is you'll be downloading / flashing a different zip file of course.
Make sure you backup (and wipe!) first before flashing any new roms!
To go back to the original Android ROM, either Restore your backup, or download the zip file from the following thread and repeat the Install ROM section: http://forum.xda-developers.com/showthread.php?t=614850
Known Issues:
Bluetooth is known to be buggy / will most likely not work. (Can't be fixed until HTC releases the Desire source code.)
USB mount notification does not appear - use 'USB Mount' application from menu.
To set live wallpapers, go into Settings -> Personalize.
--------------------------------------------------
What's the status on Bluetooth?
http://android.modaco.com/content/g...8-mar-desire-port-to-nexus-one-status-update/
A status update!
I now have the release candidate of the Desire ROM!
The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.
That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.
Basically, it all comes down to the kernel.
I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!
All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.
Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.
If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.
There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!
P
Click to expand...
Click to collapse
Update:
http://twitter.com/buxit/status/13119161481
http://twitter.com/PaulOBrien/statuses/13119278256
Reserved...
Quick question..will CyanogenMod ever support the new Sense UI built in? I realize its in Alpha stages but when its actually stable enough/all features working.
Because from what I understand only the Modaco rom comes with it?
What do you mean by "rooting"
As I understand, after you unlock bootloader and have Amon_Ra recovery you should be able to install any custom rom including both Modaco and CM
btw, if you are newbie, u should try out CM, Modaco or Enom stable first. Modaco Sense is in alpha state and still has many problems
Good guide btw
Great guide! Just explain to me the recovery image though, I don't understand what that one does, since I haven't actually done anything yet. >.>
Amon_Ra recovery is extremely helpful. It replaces the existing recovery and adds many features, including nandroid backup to back up and restore your phone in case you got screwed. It also applied zip custom roms from SD card(1 click) so you don't have to use command prompt -> more newbie friendly I guess.
btw, I don't think you need to flash Google apps in step E, correct me if I'm wrong though.
and take extra caution when flashing Radio, don't pull out the battery or do anything stupid because your phone might brick
Cheerio, very helpful guide. I'll bookmark it to link to people in the future.
"Quick question..will CyanogenMod ever support the new Sense UI built in?"
I doubt it. I don't think he did any Sense roms for the G1. But that's ok: Cyanogen if you prefer stock Android, Modaco if you prefer Sense UI. It's good to have options. And isn't that the greatness of Android?
---------------
"What do you mean by "rooting"?"
Rooting gives you superuser access. This is similar to using the Administrator account on Windows, but more so.
From http://www.linfo.org/root.html - "root is the user name or account that by default has access to all commands and files on a Linux or other Unix-like operating system. It is also referred to as the root account, root user and the superuser."
From http://wiki.cyanogenmod.com/index.php/Main_Page - "In addition to locking the phone, carriers may impose software limitations to prevent using the handset in a manner that might undercut their voice plans - Skype, Google Voice, etc - or putting strain on the data network - tethering, streaming video, etc - The way round this is to acquire 'root' (administrator) access on your phone so you can install/modify/fix/break anything you want."
Click to expand...
Click to collapse
Many applications require root like Wifi Tethering, N1 Torch, and of course, installing some custom roms
---------------
"Great guide! Just explain to me the recovery image though, I don't understand what that one does, since I haven't actually done anything yet. >.>"
duylong186 had a good explanation. So I'll just post a picture
Having a Nand Backup/Restore is downright AMAZING by the way. It's the ULTIMATE undo button!
This is also good info, just to stress this point again:
and take extra caution when flashing Radio, don't pull out the battery or do anything stupid because your phone might brick
Click to expand...
Click to collapse
Be careful everyone!
nice guide. i did everything except flash the radio. i would get the android out of the box error. everything is working fine here so far. anyways, i have all the google apps as well.
sticky please! great work
Thx for the great guide! Got Sense working on my N1 now!
about flashing the radio...
flashed the radio twice..once from stock to the OTA version, then to leaked (current) version.
both times, i applied the update, rebooted, android out of box appears, phone does its thing, get to a point where it says its updating index or something and hangs...reboot at that point...new radio with no issues both times.
point of my post - don't panic if you see the android out of the box...
nmeofdst8 said:
about flashing the radio...
flashed the radio twice..once from stock to the OTA version, then to leaked (current) version.
both times, i applied the update, rebooted, android out of box appears, phone does its thing, get to a point where it says its updating index or something and hangs...reboot at that point...new radio with no issues both times.
point of my post - don't panic if you see the android out of the box...
Click to expand...
Click to collapse
To be honest, I'm not exactly sure what the android-out-of-the-box means.
Are you saying that it will always show that after flashing any radio, and it is normal?
I cant even install the SDK
"Failed to fetch URL //dl-ssl.google.com/android/repository/repository.xmll reason: HTTPS SSL error. You might want to force download through HTTP in the settings."
The program loads but i dont get a usb driver folder....
marmankites said:
I cant even install the SDK
"Failed to fetch URL //dl-ssl.google.com/android/repository/repository.xmll reason: HTTPS SSL error. You might want to force download through HTTP in the settings."
The program loads but i dont get a usb driver folder....
Click to expand...
Click to collapse
Try changing the settings to force http?
Awesome, got a bit further... next issue is down to stupid windows os...
When trying to do the recovery carebear img... as i hit enter windows launches "windows disc image burner" and It doesnt do anything to my phone, I hit cancel and go round in a loop.
marmankites said:
Awesome, got a bit further... next issue is down to stupid windows os...
When trying to do the recovery carebear img... as i hit enter windows launches "windows disc image burner" and It doesnt do anything to my phone, I hit cancel and go round in a loop.
Click to expand...
Click to collapse
Which letter / step #, and what are you typing?
Got past this stage. was windows being stupid, on a different pc now
Finally got to E6.
If you get a Triangle with a ! in the middle alongside an Android, remove battery and re-flash recovery (I had to do this once)
Had this 3 times now! This is not enough of an idiots guide for me
Should I try the non carebear one?
marmankites said:
D6...Type: fastboot flash recovery recovery-RA-nexus-v1.6.0-carebear.img (Tip: you can press tab to auto-complete the filename -- on WinXP)
Thanks for any help! anyone have Gmail chat or anything who has any ideas?
I cant type links but... i306.photobucket.com/albums/nn248/marmankites/helpnexus.jpg
Click to expand...
Click to collapse
Ah I see.
In the picture, you are typing "recovery-RA-nexus-v1.6.0-carebear.img", which is the file name only.
You should be typing:
fastboot flash recovery recovery-RA-nexus-v1.6.0-carebear.img
Read carefully
Should I try the non carebear one?
Click to expand...
Click to collapse
The carebear one doesn't do anything except just change the background picture to a carebear
This tutorial is for us P769/MS769 owners with phones manufactured after mid 2013, who have trouble unlocking our bootloaders using this method, because the bootloader seems to be encrypted.
The solution is to flash using a special LG Flash Cable with a 910k resistor. In this tutorial I will show you how I did it and how you can do it too.
You will need:
A reasonably modern PC running Windows 7. XP or Vista most likely will work also, but I've heard Windows 8 has problems.
Your LG P769/MS769
SIM card with a valid cellular connection (you need a cellular data plan for this to work).
A micro SD card, at least 1GB free space recommended.
A standard Micro USB cable
A 910k resistor cable
LG United Mobile Drivers. You can download these from the official LG website, but I also included it in the files.
Toolkit of all the stuff you need
7zip or other to extract the toolkit
ROM you want to install (gapps also, if you want)
Optional: KDZ of V20H. Only needed if you want to flash back to stock before flashing your ROM. I didn't include this in the toolkit to save space.
---Obtaining 910k Cable---
You can buy this from various sites on the internet
GSM Support and Alibaba have them. There are some on Ebay as well. If you want others just Google it.
Or, if you are comfortable with soldering you can make your own.
You will need a 910k resistor, a micro usb male head, and a spare usb cable.
Here are some helpful diagrams:
{
"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"
}
Note: If it doesn't work, then try reversing the order of the wires. For some reason, the heads i bought had the pins in reverse order.
You can also test which wire corresponds to which with a multimeter, wrap a resistor around one lead and touch a pin in the microusb head, the other lead the corresponding pin on the regular usb head.
---Preparation---
First, backup all your data of course.
Download the toolkit, and extract it.
Install the LG United Mobile Drivers.
Navigate to the folder SD Card. Copy the files to your micro SD card. I recommend in the root directory, it could save you a lot of time and frustration later.
Also copy your ROM (and gapps) to the SD card.
Navigate to the folder Flash V10G. Copy RootFlash and shttps to the root directory of your hard drive (C:\). It must be in the root, or else it simply won't work.
Turn on USB debugging.
---Flashing V10G---
Use the normal Micro USB cable to connect your phone to PC.
Put the phone to Software Mode. Autorun should pop up, go ahead and run it. A popup will appear, just close it.
Follow this tutorial (thanks cmahendra) to flash V10G_00.kdz. (Note: No need to download the tools again from that tutorial, you already have them )
After the flash is complete, you can unplug the micro usb cable.
Phone should reboot, and get stuck at the bootscreen.
Just pull the battery for a few seconds, and replace.
Hold Volume Up, Home, and Power buttons simultaneously. This will factory reset your phone.
When the phone powers on, release Power but hold on to Volume Up and Home until the Android appears.
Your phone should reboot into the setup. Just go through it real quick, and let the apps install.
Now go to Settings:
Go to Apps and disable: Lookout Security
Go to Security and check: Install from Unknown Sources
Go to Developer Options and check: USB Debugging, Show Touches
Power off your phone.
---Flashing V20B---
Navigate to folder Flash V20B > LGFlashTool. Run LGFlashTool.exe.
A prompt will appear.
For DLL: selectLGP760_20120911_LGFLASHv1350.dll
For S/W: select LGP760_AP.bin
It should look like this:
But don't click OK yet!
On your phone, hold Volume Up (or down?) and plug in 910k cable. S/W mode should appear.
Find: Device Manager > Ports (COM & LPT) > LGE Mobile USB Serial Port (COM#) > Properties. > Port Settings tab > Advanced.
Change COM Port Number to COM41. You can exit Device Manager now.
Now go back and click OK.
Click this:
And change it to look like this:
Press OK.
Click this:
A ready sign should pop up in the first box. Now just unplug the 910k cable, wait a few seconds, and replug.
Now it should flash, just wait for it to finish.
(thanks to sammyz for the original tutorial)
---Enabling Radio---
Your phone should reboot into a blue LG logo. You can unplug the 910k cable now.
When it loads, the screen and colors is inverted. A mirror may be helpful for reading the inverted font.
The touchscreen is also completely whack. Enabling Show Touches helps immensely here.
The top half is normal but shifted down slightly. The bottom half is completely upside down. This is very frustrating to navigate. Just have patience, and think of the joys of an unlocked bootloader. :laugh:
Note: If for some reason the phone factory reset, then you have to enable USB Debugging, Unknown Sources, and Show Touches again. Otherwise continue on.
Insert the SD card.
Open up File Explorer and navigate to external_SD. install LGPwn, SuperSU, Busybox, LG Recovery Installer APKs you put there earlier.
Open LGPwn, and go through until the LG Backup options appears.
Click Restore > Internal Storage > Lgpwn.
When it finishes, press the button and it will reboot the phone.
Now open SuperSU, and install the binary in Normal mode.
Open Busybox Installer and just press the install button on the bottom.
Open LG Recovery Installer (thanks artas). It should say Status: Not Installed.
Click the install button, and install the stable version. After it completes, it will ask if you want to reboot to recovery. Reboot into recovery.
Note: You can press the button that reboots, or you can restart the phone and hold Volume Down when the key lights flash.
You should now be in a backwards CWM screen.
Go to install from zip > install zip from external sd
Select radio.zip. Wait for it to finish, then navigate to the main menu and restart the phone.
---Unlocking Bootloader---
Now you should have data enabled. Note: If you have T-Mobile 4G, it will probably show as H+ instead of 4G.
Open up the YouTube app, and play something long. This is to keep the connection active.
Wait 35-45 minutes. Most people get the unlock token at around 35 minutes, but I personally waited 45 minutes.
After that, plug in the normal USB cable.
On your PC, open up Command Prompt and navigate to Unlock BL. I have also made corresponding batch scripts for these commands as well, you can just run those.
Note: You can also open the folder in Explorer, hold shift, right click in the window, and there will be an option to open command prompt there.
Type this magic command: adb reboot oem-unlock
Your phone should reboot into a fastboot screen, with very small font.
Basically, just press Volume Up to unlock bootloader. Don't exit fastboot.
Type this to flash a newer ClockWorkMod: fastboot flash recovery CWM.img
Note: If you want to do the optional step below, you can exit without flashing CWM.
Power off your phone and remove the SD card.
---Optional: Reverting Back to Stock---
For whatever reason, you might want to flash back stock before flashing Cynogen, just to make sure you have latest firmware, radio, etc.
I can't prove that there's any difference, so it's up to you.
Just flash V10G, then flash V20H, both with the tool from the first flash.
The touchscreen will still be whack, but you're probably used to it by now.
Then once you get to V20H, install LGPwn, SuperSU, Busybox, and Flashify
Boot into recovery and install cwm_ts_fix_p769.zip.
Reboot and your touchscreen should be back to normal.
Now open Flashify, install recovery, and select recovery-6.0.4.9-p769.img
This will install the latest CWM, now you are ready to flash the ROM.
Note: if you enjoy stock ROM you can stop here.
---Installing Cynogen---
There are many different versions of Cynogenmod and other ROMs for our phone.
A whole list can be found here. I recommend KANG CM11, as it seems to be the most frequently updated.
but there are other CM11 by AntonX and BobZhorne.
Power on your phone, boot into CWM the same way by pressing Vol Down when the lights flash.
Flash the zips of your ROM and gapps if desired.
Have fun! :laugh:
I hoped my tutorial helped you guys.
Please, comment if you need help, have questions, or notice I forgot something!
Thanks to cmahendra, sammyz, kuma82, lelus, CygnusBlack, carloswii, and anyone else for their wonderful tutorials and tools!
Thanks to mven45, DarryDoo, anstoss, and anyone else for the valuable information about 910k cables!
Couldn't have done it without them.
How Much
How Much Does the 910K resiter cable cost?
thegoldenandroid said:
How Much Does the 910K resiter cable cost?
Click to expand...
Click to collapse
Around $10
what do you mean for "valid sim"?
trixi3 said:
what do you mean for "valid sim"?
Click to expand...
Click to collapse
You need cellular data connection. But it doesn't have to be a T-Mobile plan, any will work, including roaming.
leereyzhe said:
You need cellular data connection. But it doesn't have to be a T-Mobile plan, any will work, including roaming.
Click to expand...
Click to collapse
I'm from El Salvador, and I'm using the 769 with a local operator, would this work?
trixi3 said:
I'm from El Salvador, and I'm using the 769 with a local operator, would this work?
Click to expand...
Click to collapse
It should work fine. :good:
Although, you might need to flash a different "radio.zip" for your operator if you can't connect after flashing V20B. (The one I have included is for T-Mobile USA)
In that case I wouldn't know what to do. I don't know much about how radios work. \
I would try it without flashing radio.zip first, and see if it will connect. Can you give me more info about your operator?
leereyzhe said:
It should work fine. :good:
Although, you might need to flash a different "radio.zip" for your operator if you can't connect after flashing V20B. (The one I have included is for T-Mobile USA)
In that case I wouldn't know what to do. I don't know much about how radios work. \
I would try it without flashing radio.zip first, and see if it will connect. Can you give me more info about your operator?
Click to expand...
Click to collapse
Leereyzhe so did you finally get your bootloader unlocked? Your post tells me you did, if so that's great news and especially so since you figured out how to do it with a different cable for encrypted bootloaders.
CygnusBlack said:
Leereyzhe so did you finally get your bootloader unlocked? Your post tells me you did, if so that's great news and especially so since you figured out how to do it with a different cable for encrypted bootloaders.
Click to expand...
Click to collapse
Indeed I did, I've been running KANG for the past 2 days and so far its been great :thumbup:
I don't hate this phone anymore
Sent from my LG-P769 using XDA Free mobile app
leereyzhe said:
Indeed I did, I've been running KANG for the past 2 days and so far its been great :thumbup:
I don't hate this phone anymore
Sent from my LG-P769 using XDA Free mobile app
Click to expand...
Click to collapse
You should Rice and Secure your phone with hardened configs now. I did that to mine and I get 2 days battery on my stock battery. I can also play DSI, 3DS and PSP games on my phone now too. Ricing it makes it even better because you get it to where the system only uses less than 10% of the hardware resources. Install F-Droid then install AFWall+, AdAway and Firefox from F-Droid repos. Doing that for starters and having those configured will remove all ads and unwanted network packets outbound then you get maximum Internet speed too. I have the unlimited no throttle plan from T-Mobile and I usually torrent anywhere from 300 Gigabytes to 1 Terabyte worth of movies, games, music just about anything I want in a pay period. In CM11 there is a wifi hotspot feature so you can tether wirelessly to all you computers and when the browser on your computer is redirected to the T-Mobile site you just change the user-agent in the browser so the network thinks it's an Android lol. Anything with the Linux string will work.
Not too shabby for a $100 device I must say! I'm thinking of getting a new Nexus though here in a few weeks however unless I can get a stable Ubuntu Touch with all the drivers working for this P769. If I can I would probably milk this P769 for a couple more years and keep saving up all my mobile fund haha
how is battery for you with Kang rom...it was draining and I had to use battery saver to enable deep sleep...so far cmx (based on cm 10.2) works for me the best...but love to know there is any other rom that is very performing...I also experienced some lag with Kang...
leereyzhe said:
This tutorial is for us P769/MS769 owners with phones manufactured after mid 2013, who have trouble unlocking our bootloaders using this method, because the bootloader seems to be encrypted.
The solution is to flash using a special LG Flash Cable with a 910k resistor. In this tutorial I will show you how I did it and how you can do it too.
You will need:
A reasonably modern PC running Windows 7. XP or Vista most likely will work also, but I've heard Windows 8 has problems.
Your LG P769/MS769
SIM card with a valid cellular connection (you need a cellular data plan for this to work).
A micro SD card, at least 1GB free space recommended.
A standard Micro USB cable
A 910k resistor cable
LG United Mobile Drivers. You can download these from the official LG website, but I also included it in the files.
Toolkit of all the stuff you need
7zip or other to extract the toolkit
ROM you want to install (gapps also, if you want)
Optional: KDZ of V20H. Only needed if you want to flash back to stock before flashing your ROM. I didn't include this in the toolkit to save space.
---Obtaining 910k Cable---
You can buy this from various sites on the internet
GSM Support and Alibaba have them. There are some on Ebay as well. If you want others just Google it.
Or, if you are comfortable with soldering you can make your own.
You will need a 910k resistor, a micro usb male head, and a spare usb cable.
Here are some helpful diagrams:
Note: If it doesn't work, then try reversing the order of the wires. For some reason, the heads i bought had the pins in reverse order.
You can also test which wire corresponds to which with a multimeter, wrap a resistor around one lead and touch a pin in the microusb head, the other lead the corresponding pin on the regular usb head.
---Preparation---
First, backup all your data of course.
Download the toolkit, and extract it.
Install the LG United Mobile Drivers.
Navigate to the folder SD Card. Copy the files to your micro SD card. I recommend in the root directory, it could save you a lot of time and frustration later.
Also copy your ROM (and gapps) to the SD card.
Navigate to the folder Flash V10G. Copy RootFlash and shttps to the root directory of your hard drive (C:\). It must be in the root, or else it simply won't work.
Turn on USB debugging.
---Flashing V10G---
Use the normal Micro USB cable to connect your phone to PC.
Put the phone to Software Mode. Autorun should pop up, go ahead and run it. A popup will appear, just close it.
Follow this tutorial (thanks cmahendra) to flash V10G_00.kdz. (Note: No need to download the tools again from that tutorial, you already have them )
After the flash is complete, you can unplug the micro usb cable.
Phone should reboot, and get stuck at the bootscreen.
Just pull the battery for a few seconds, and replace.
Hold Volume Up, Home, and Power buttons simultaneously. This will factory reset your phone.
When the phone powers on, release Power but hold on to Volume Up and Home until the Android appears.
Your phone should reboot into the setup. Just go through it real quick, and let the apps install.
Now go to Settings:
Go to Apps and disable: Lookout Security
Go to Security and check: Install from Unknown Sources
Go to Developer Options and check: USB Debugging, Show Touches
Power off your phone.
---Flashing V20B---
Navigate to folder Flash V20B > LGFlashTool. Run LGFlashTool.exe.
A prompt will appear.
For DLL: selectLGP760_20120911_LGFLASHv1350.dll
For S/W: select LGP760_AP.bin
It should look like this:
But don't click OK yet!
On your phone, hold Volume Up (or down?) and plug in 910k cable. S/W mode should appear.
Find: Device Manager > Ports (COM & LPT) > LGE Mobile USB Serial Port (COM#) > Properties. > Port Settings tab > Advanced.
Change COM Port Number to COM41. You can exit Device Manager now.
Now go back and click OK.
Click this:
And change it to look like this:
Press OK.
Click this:
A ready sign should pop up in the first box. Now just unplug the 910k cable, wait a few seconds, and replug.
Now it should flash, just wait for it to finish.
(thanks to sammyz for the original tutorial)
---Enabling Radio---
Your phone should reboot into a blue LG logo. You can unplug the 910k cable now.
When it loads, the screen and colors is inverted. A mirror may be helpful for reading the inverted font.
The touchscreen is also completely whack. Enabling Show Touches helps immensely here.
The top half is normal but shifted down slightly. The bottom half is completely upside down. This is very frustrating to navigate. Just have patience, and think of the joys of an unlocked bootloader. :laugh:
Note: If for some reason the phone factory reset, then you have to enable USB Debugging, Unknown Sources, and Show Touches again. Otherwise continue on.
Insert the SD card.
Open up File Explorer and navigate to external_SD. install LGPwn, SuperSU, Busybox, LG Recovery Installer APKs you put there earlier.
Open LGPwn, and go through until the LG Backup options appears.
Click Restore > Internal Storage > Lgpwn.
When it finishes, press the button and it will reboot the phone.
Now open SuperSU, and install the binary in Normal mode.
Open Busybox Installer and just press the install button on the bottom.
Open LG Recovery Installer (thanks artas). It should say Status: Not Installed.
Click the install button, and install the stable version. After it completes, it will ask if you want to reboot to recovery. Reboot into recovery.
Note: You can press the button that reboots, or you can restart the phone and hold Volume Down when the key lights flash.
You should now be in a backwards CWM screen.
Go to install from zip > install zip from external sd
Select radio.zip. Wait for it to finish, then navigate to the main menu and restart the phone.
---Unlocking Bootloader---
Now you should have data enabled. Note: If you have T-Mobile 4G, it will probably show as H+ instead of 4G.
Open up the YouTube app, and play something long. This is to keep the connection active.
Wait 35-45 minutes. Most people get the unlock token at around 35 minutes, but I personally waited 45 minutes.
After that, plug in the normal USB cable.
On your PC, open up Command Prompt and navigate to Unlock BL. I have also made corresponding batch scripts for these commands as well, you can just run those.
Note: You can also open the folder in Explorer, hold shift, right click in the window, and there will be an option to open command prompt there.
Type this magic command: adb reboot oem-unlock
Your phone should reboot into a fastboot screen, with very small font.
Basically, just press Volume Up to unlock bootloader. Don't exit fastboot.
Type this to flash a newer ClockWorkMod: fastboot flash recovery CWM.img
Note: If you want to do the optional step below, you can exit without flashing CWM.
Power off your phone and remove the SD card.
---Optional: Reverting Back to Stock---
For whatever reason, you might want to flash back stock before flashing Cynogen, just to make sure you have latest firmware, radio, etc.
I can't prove that there's any difference, so it's up to you.
Just flash V10G, then flash V20H, both with the tool from the first flash.
The touchscreen will still be whack, but you're probably used to it by now.
Then once you get to V20H, install LGPwn, SuperSU, Busybox, and Flashify
Boot into recovery and install cwm_ts_fix_p769.zip.
Reboot and your touchscreen should be back to normal.
Now open Flashify, install recovery, and select recovery-6.0.4.9-p769.img
This will install the latest CWM, now you are ready to flash the ROM.
Note: if you enjoy stock ROM you can stop here.
---Installing Cynogen---
There are many different versions of Cynogenmod and other ROMs for our phone.
A whole list can be found here. I recommend KANG CM11, as it seems to be the most frequently updated.
but there are other CM11 by AntonX and BobZhorne.
Power on your phone, boot into CWM the same way by pressing Vol Down when the lights flash.
Flash the zips of your ROM and gapps if desired.
Have fun! :laugh:
I hoped my tutorial helped you guys.
Please, comment if you need help, have questions, or notice I forgot something!
Thanks to cmahendra, sammyz, kuma82, lelus, CygnusBlack, carloswii, and anyone else for their wonderful tutorials and tools!
Thanks to mven45, DarryDoo, anstoss, and anyone else for the valuable information about 910k cables!
Couldn't have done it without them.
Click to expand...
Click to collapse
leereyzhe said:
You need cellular data connection. But it doesn't have to be a T-Mobile plan, any will work, including roaming.
Click to expand...
Click to collapse
Hey Can You Use Wifi And A Deacticated SIM Card?
no, based on my experience, cellular data connection is mandatory to unlock bootloader. wifi is not required.
OMG why did no one tell me about this.
Just bought a 910k cable. Should be here in 1-2 weeks.
Thanks for this, and your welcome for my guides/files
So I helped in unlocking my phone without trying to
My life is complete lol.
This is pretty awesome! May I ask what specific problems arise with Win8 use?
I'd like to downgrade to Win7, but I've got some apps that are really important to me for grad school in Win8 that I can't give up. Also, is it possible to try this on a May 2013 phone? What are your thoughts on this? Thanks!
sammyz said:
OMG why did no one tell me about this.
Just bought a 910k cable. Should be here in 1-2 weeks.
Thanks for this, and your welcome for my guides/files
So I helped in unlocking my phone without trying to
My life is complete lol.
Click to expand...
Click to collapse
knowledge comes full circle.
jbonilla51 said:
This is pretty awesome! May I ask what specific problems arise with Win8 use?
I'd like to downgrade to Win7, but I've got some apps that are really important to me for grad school in Win8 that I can't give up. Also, is it possible to try this on a May 2013 phone? What are your thoughts on this? Thanks!
Click to expand...
Click to collapse
Hmm. Come to think of it, I don't know of any actually
I've heard the first flash tool crashes on Windows 8, for whatever reason, when trying to flash V20B. But come to think of it, it crashes anyway regardless of OS when using the cable. So, that's why we're flashing it with the other tool, which does work with Windows 8...
You should try it and lemme know how it goes.
Oh yes, this will work on your phone. :good:
Here's to hoping
I just ordered a 910K cable today. I've already tried unlocking previously with no luch. Mine IS a May 13 phone too, so the old way should have worked. Hopefully if this works I can stop punching my phone in frustration over slowness. XD An idea I have of course for the 45 minute wait on youtube is to put on "War of the servers" since it's a long as* video. should be fine lol
Holy **** it works. Got the cable today. I have a p760, had 2nd-init CM9 on it so i just flashed v20b with LGFlashTool (not sure why but it doesn't reach 100%, it stops at 80%). First time i waited 30 minutes, tried the command, didn't work (got a little nervous at this point). Flashed v20b again, waited about 45 minutes i think, tried the magical command and it worked! (note: i did this on 8.1 which i don't advise if you don't have fastboot drivers already installed, cause windows wouldn't let me install my own drivers, had to use ubuntu to flash recovery) Now i'm happily running PAC .
I could not believe my eyes when I saw the fastboot screen. This worked for me, and the words thank you don't even express how appreciative I am for this tutorial and those who created the methods. :good: :victory: :highfive:
I couldn't flash Cyanogen because my phone was being read as a p950, error status 7. I flashed the uboot and xloader knowing it would remove the bootloader, and can't get it back... While flashing 20B originally it stopped at 80% and said it failed, this could be what caused all this. The tool now fails to complete at 170 seconds when writing to eMMC memory... The eMMC memory could be broken now, but I can factory reset to stock. I'm pretty sure I essentially ruined the phone . Any ideas?
Fixed by flashing 20F then flashing, but I can't make the phone see itself as p769.
Hello guys, I was one the unfortunate guys who tried to downgrade from an updated XLOADER version FW to an older and failed to do so, resulting a hard brick. I managed to get my phone up and running again with free tools without DC-Phoenix, I include everything detailed in my post, even a preconfigured virtualbox linux system for the initial steps. I also included an UPDATE.app splitter too.
So, this is not an XLOADER downgrade tutorial, with this you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
What you need for this whole thing:
This archive, it contains the firmware, the tools, the preconfigured linux, and the drivers.
VirtualBox downloaded and installed, just google it.
A physically opened phone, unscrewed motherboard, as the testpoint is on the other side, and something to short your testpoint.
First steps:
After you downloaded the archive, just unzip the whole thing to a folder where you have enough space ( the archive is ~7.8GB unzipped)
Now you need to download and install VirtualBox, and import the HIKEY.ova virtual system I included in the zip.
Here's how you can do it
Step one, The HIKEY.ova file is located in the virtual machine folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step two, Leave the settings at default and import it
Setting up your phone and computer:
You need to open up your phone physically, here is a good video of the disassembly https://www.youtube.com/watch?v=Zkj7YVeSzS4
Now, if you got your motherboard unscrewed, you must leave the cable with the big arrow connected to it.
Plug your usb cable into your phone and into your computer, now you must short your testpoint, I included an image about where the testpoint is. https://i.imgur.com/q9ZNGgx.jpg
Just use metal tweezers or a bent metal paperclip, one end on the test point, and the other end to something you can ground it with, the metal shields next to it are good to use.
If you did everything right, your computer should recognize a new device named USB SER, if this is the case, you now must install the huawei android phone drivers. Now the USB SER is now recognized as HUAWEI USB COM 1.0 in the device manager.
Starting the revive process:
After you got the HUAWEI USB COM 1.0 set up, you need to start the virtual linux machine.
The first thing it will ask for is hw login, just type this with lowercase letters.
Code:
hw
hw (again)
Now, you need to add your HUAWEI USB COM 1.0 to the virtual machine.
To do this you need to click the USB icon in the lower right corner and select HUAWEI USB COM 1.0.
.
.
It should have connected as ttyUSB0, you can check it with the command
Code:
dmesg
Now you need to type
Code:
cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0
(if it asks for sudo password its hw again, also if your device is connected as other ttyUSB number, then you should use that number)
You should see this written from the console if it succeded
With this, you now have a special fastboot booted in your phone.
Flashing the system:
You can now exit the virtual machine, and run first batch, named 1. revive flasher.bat.
It will give you two options after it finished flashing the system, check the one you need, VTR-L29 or VTR-L09.
After the batch is done and you felt that the phone rebooted from the fastboot mode, you can now disconnect the phone from the computer.
You now need to connect the LCD cable, the battery cable, and buttons cable back to your motherboard, no need to re screw the mobo yet, just leave everything hanging in case you need to do the process again with the testpoint.
Now manually boot back into fastboot, Hold volume down while connecting your usb to your computer.
Now you need to flash a TWRP with 2. TWRP recovery.bat.
After that, boot into TWRP, wait for it to completely boot up, and flash an oeminfo with one of the oeminfo batches 3a or 3b.
With this, you should now be able to boot into the system, if there are still problems like bootlooping, do a factory reset from recovery.
Big thanks to:
@goodwin_c for the special fastboot/hikey_idt combo.
@Pretoriano80 for the TWRP recovery
@ante0 for the splitupdate.exe
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
NowLearn said:
Im downloading all the files right now. Let you know how it goes. THANK YOU so much
---------- Post added at 06:02 PM ---------- Previous post was at 05:46 PM ----------
This you can get your phone running again with the newer xloader FW-s. In this case I used files from the B386 version, so your phone will be on 8.0.0.386(C432). WARNING your IMEI number will most likely be gone if you do something wrong, as mine did, this method is only a last bastion to reset your phone. And I don't really have acces for my phone in the coming weeks, but I have some stuff left from firmwares if there is any problem with the script, just hit me up in the thread for any errors or missing stuff.
-what can I do wrong?. I don't want to break my IMEI. if i follow your instructions, Also my firmware before it was hard brick is VTR-L09 8.0.0.310(c25) Custom version CUSTC23D001. I wont have any issues flashing the firmware you provide? , thank you for your help
Click to expand...
Click to collapse
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
yoghurt13 said:
What I did wrong was flashing the board fw wrong, erasing modemnvm partition, erasing nvme partition, and some other partitions that got my imei ****ed up. I excluded those from the batch, and because of this, there are possibilities that it might not work. And as of your version, I did not include that one in the stuff. I used the european fw, but with some modification you can use your own FW with my stuff. I can maybe compile it for you, but that'll take some time.
Click to expand...
Click to collapse
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
NowLearn said:
Im installing the virtualbox right now. I would like to know If i flash your VERSION, i wont have any issue? if its european and my phone its from Latin America?. I dont mind having a different firmware as long that my phone dont break.
Click to expand...
Click to collapse
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
yoghurt13 said:
Most likely your phone will work, but there would be baseband differences because of the oeminfo, and update version, wich would mean you can't make phonecalls and mobile data. I'm downloading your firmware currently, so be patient and I'll get stuffed in a new zip with the modifications.
Click to expand...
Click to collapse
bro, u didnt have to do that, but I appreciate it. Let me pm u. Thank you again
Would it be possible to rebrand VTR-L09 to VTR-L29 using this method?
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
volpula said:
2. TWRP Recovery.bat not working. just say waiting any devices. ı cant make phone restart to fastboot mode. I do disconnect battery,lcd and botton cable and connect usb cable in ps.use testpoint to connect,ps see the device anythings okay. cd hikey_idt/
sudo ./hikey_idt -c config -p /dev/ttyUSB0. I enter this codes and says finish downloading and phone get vibration thats all.after that open revive flasher.bat. and choıce vtr-l29 and enter thats all.ım stuck in the.connect again lcd,battery and botton cable trying to open twrp.bat but not open.by the way if when phone get vibration after that ı need see phone start with fastboot mood? because cant access fastboot mode. I dont really understand how this works.
Click to expand...
Click to collapse
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Ekenfo said:
Ok, so I was able to rebrand to VTR-L29 but my IMEI is 0.
Anyone can help me put my IMEI back? I tried to use HCU but it's telling my that my current security patch is not supported.
Thanks!
Click to expand...
Click to collapse
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
I can give you only my instagram.beacause I dont have a backup phone rightnow just waiting to fix my phone.if I can fix that buy a new phone but never huawei again.
yoghurt13 said:
Currently there is no way to reset your IMEI with android 8+, as HCU and the other softwares does not support our phone over android 8, if your IMEI is erased then It's might be gone forever at this rate, but I'm trying to find a method, but no guarantees.
Click to expand...
Click to collapse
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
yoghurt13 said:
Do you have any direct messaging app we can communicate? I can maybe help with teamviewer if that's an option for you.
I can currently suggest that if your phone vibrates after linux command and finish download, that's already a good sign. After that, try to close the linux machine, and just remove and reconnect usb, and see if your device is now visible in device manager.
Click to expand...
Click to collapse
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
volpula said:
by the way I try remove and reconnect usb but device manager can't see the device. only see device when I reach and touch testpoint area again.
Click to expand...
Click to collapse
Then there is the problem, try to install HiSuite, or my android driverpack, and try to see if the phone shows up in device manager.
Ekenfo said:
Do you know if the IMEI is contained in the oeminfo image? Maybe we could just hex edit it and flash it back?
Or maybe using the AT+EGMR=1,7,"IMEI"' command? But root is needed for that.
In the steps you described in your first post you say to flash twrp in fastboot. My device is locked so it's not working.
The only way I can get twrp to flash is after using the testpoint method. But then when I try to go in recovery I'm only getting in the stock recovery, not trwp...
Any idea?
Thanks!
Click to expand...
Click to collapse
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
yoghurt13 said:
That command only works on MTK devices, and for the TWRP if you can flash it in testpoint instead of the normal recovery, with
Code:
fastboot flash recovery_ramdisk twrp image file location
, then you should be able to boot that if you disconnect the usb, and hold vol up while restarting phone.
Click to expand...
Click to collapse
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Ekenfo said:
I'm not sure why but for some reasons I can't get the phone to boot into TWRP, I only get the emui recovery screen.
Another thought : It appears hisuite could rollback the firmware to a nougat version. That option is not available with my phone.
Is there a version that we know for sure that hisuite allows to downgrade from?
Maybe we could flash that version, downgrade using hisuite and then hcu would work?
Click to expand...
Click to collapse
There is currently no way to downgrade from XLOADER2, huawei did some black magic with it, and there is a checker built in the phone that checks if its a loader1 or 2.
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Ekenfo said:
So, I flashed TRWP in both recovery_ramdisk and erecovery_ramdisk and I was able to access it.
I got my nvme image and patched it to unlock the bootloader.
But that doesn't help to get hcu to work...
Any idea what would be the next step to fix my imei?
Click to expand...
Click to collapse
I literally have no ideai yet how to fix our IMEI, since the NVME partition does not contain the information we need, I just tested one from a working phone, and it was the same as before, zeroed out IMEI.
Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
I've got a Goclever Zoom.me - Android 4.2.2 based photo frame. Really crappy device by the way... but, I really need to install some apk to have a possibility of remote connection to this device (FTP or SMB, or at least just create some network-shared directory). It would be also perfect to have any launcher with android menu and so on...
The issue is that it's impossible to connect to this device via adb. I remember that with old firmware it was actually possible, but long time ago (2015) I upgraded it to newer software, and official instruction to click 8 times a serial number in a device's software to enable USB debugging doesn't work anymore... I thought it had enabled debugging permanently but it seems to be not true, as adb nor fastboot don't see the device. PC recognizes it as a camera allowing to transfer files only.
Device doesn't have any hardware buttons except power and hard reset buttons. I was looking for any possibility to solder volume buttons, but didn't find a spot for them (mainboard is marked as: e351308 topwise-014).
I can connect OTG keyboard and mice instead, which may be helpful... but escaping nor ALT+ESC in the best case moves me to black screen with mouse cursor only...
Can you advice anything to connect to device via adb? What else can I try?
Modify the update perhaps? Seems to work.
GoClever Zoom.me and GApps
I need some help. I own a digital photo frame GoClever Zoom.me which is based on Android 4.2.2. It is rooted and USB debugging is on. I managed to install standard launcher but unfortunately there is no GApps installed on this device. I'm able...
forum.xda-developers.com
Still available
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZOOM.ME_WiFi_Zmiana_Oprogramowania.pdf
80 page manual for a photo frame? LOL!
http://zoom.me/files/manual_en.pdf
Well, some say repetitio est mater studiorum, so they have put it there twice...
LOL! 40 page manual for a photo frame...
CXZa said:
Modify the update perhaps? Seems to work.
Click to expand...
Click to collapse
What do you mean by modifying the update? To modify /system/build.prop ?
I saw that thread, but the issue is that I can't update device again... PhoenixSuit nor adb can see it connected - seems like USB debugging is not enabled anymore and I can't enable it anyhow.
CXZa said:
80 page manual for a photo frame? LOL!
(...)
LOL! 40 page manual for a photo frame...
Click to expand...
Click to collapse
That frame was released with a huge marketing action...but it became a failure as it's a terrible design in total - from housing to software...
matisys said:
Hi Team,
Long story short - I have a problem with adb connection to Android device. And details below.
Can you advice anything to connect to device via adb? What else can I try?
Click to expand...
Click to collapse
That's really weird, because ADB since ever is integral part of every Android distribution. May be in the ROM your device is running on either ADB in fact isn't implemented or USB.debugging isn't allowed or ADB isn't bound to Android's USB-service.
matisys said:
What do you mean by modifying the update? To modify /system/build.prop ?
Click to expand...
Click to collapse
Meant flashing. So, do you have the MTK or Allwinner?
With one button it might be difficult to enter the update mode, but if opened you could possibly connect some pins to make boot to fail thus making it to boot such mode... IDK.
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own. (If recovery keys aren't changed when updated.) Or if you can enter the recovery mode then install it from sdcard.
I have multiple tools, but none can see the device without debugging on.
It's actually easy to open, but I didn't find a proper spot to enforce recovery mode...
CXZa said:
Other possibility is to make your wifi to connect to your own server instead of http://ota.zoom.me/ and let it "update" itself.
Their update zips are signed using test keys so you can make your own
Click to expand...
Click to collapse
How do you know that?
Running an own server is actually an easy part for me, but I'm not sure how to prepare a proper package...
There is actually an update package available to download:
http://downloadfiles.goclever.com/Tablet/Zoom_me/ZM7WIFI_20150717.img
But I couldn't modify it using Dragonface...
matisys said:
How do you know that?
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
I checked the recovery in case build.prop lies.
Then again is their update a zip? Might be something exotic.
I also checked their ota apk and tested it.
It didn't download. Sent a lot of info from my tab. Some didn't match (faked what I easily could)... or no updates anymore...
Gave 502...
matisys said:
I didn't find a proper spot
But I couldn't modify it using Dragonface...
Click to expand...
Click to collapse
Another soc and device, but might work.
Entering to Flashing/Adfu mode (and Recovery mode too) - Actions Semi ATM7029 Quad-core ARM CPU devices
Entering to Flashing/Adfu mode (and Recovery mode too) - posted in Actions Semi ATM7029 Quad-core ARM CPU devices: The instructions given in this thread should work, but still as always, you use them at your own risk!If there is a hardware problem then the tablet probably is bricked for good...
www.slatedroid.com
Battery removing might be the safest...
Try imgRePacker...
OK, I managed to unpack the img file and to edit build.prop - Thanks fot that info One small step forward.
I added:
qemu.hw.mainkeys=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=ptp,adb (this one already exists)
Hoping it will allow me to access the system via adb or screen directly after reflash.
I didn't pack it back yet as I still didn't manage to access this device from computer...
I tried to find a spot on mainboard - I've made a connection on two spots:
{
"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"
}
But no luck...
There is more spots however, but none marked as recovery, ADFU, or similar...
And still no USB debugging, nor adb connection...:/
Tried of course some tricks with power button holding, clicking, reseting while hold, etc...
Any further suggestions...?
Maybe some ideas to enforce upgrade via wifi? I can establish a server, but not sure what exactly server should serve...? Just an img file is rather not enough...
Below that E351308 text, or above if other way around, is the target for those pin suggestions. But try battery, you can always solder it back together,.. or just let it go empty - might work...
> what exactly server should serve...?
yeah, there probably is some data exchange before the download..
BTW, this img appears to have adb enabled, so it's not the last one... Or it's disabled by other means...
Data it sent:
{"genderId":-1,"email":"","Locale":{"L":"eng","S":"en_US","C":"USA"},"deviceInfo":{"TIME":1419244414000,"FINGERPRINT":"ZOOM_ME\/ZM7WIFI\/ZM7WIFI:4.2.2\/JDQ39\/20141222:eng\/test-keys","HARDWARE":"gs702a","VERSION.SDK_INT":17,"BOARD":"exdroid","PRODUCT":"ZM7WIFI","DISPLAY":"ZM7WIFI_20141222","VERSION.INCREMENTAL":"20141222","DEVICE":"ZM7WIFI","TAGS":"test-keys","MODEL":"ZM7WIFI","BOOTLOADER":"unknown","CPU_ABI":"armeabi-v7a","CPU_ABI2":"armeabi","VERSION.CODENAME":"REL","MANUFACTURER":"ZOOM_ME","BRAND":"ZOOM_ME"}}
Click to expand...
Click to collapse
That hardware exposed me. It didn't get that from *.prop files.
OK, so currently it's like below.
I already tried some tricks with battery - disconnecting, connecting while booting, and no luck...
I tried with all spots marked below - one by one, and some combinations of few of them...
And the status is like that - spots 2 and 3 - seems to be ignored when connected - device behaves like nothing happened. It's more interesting when I connected 1 or 4. Device didn't start, and in a computer it appeared as unknown winusb device or Billboard device when connected 4 (USB\VID_1F3A&PID_EFE8&REV_02;3).
Universal ADB driver installer doesn't recognize it...
The only driver I managed to install was Allwinner driver and it appeared as USB Device(VID_1f3a_PID_efe8).
But still no luck with adb connection... Phoenix suite also doesn't recognize the device... In this state screen remains black and AXP223 (Power management) quickly becomes hot as hell (battery unplugged)...
Once unsoldered - it went back to life.
I also realized that my device says that it is version ZM7WIFI_20150717... what is confusing a bit because in other place it says it's 2.2 23-5.03.2015 software version...
But still no connection or any option to flash it
Can you tell me how do you run this software/hardware to see what does it send?
I can still use OTG keyboard and mouse - maybe there is some option to enter android settings and simply enable USB debugging?
Those pins that I mentioned at slatedroid are on the sides of that chip.. and don't solder, just place some tool - a needle between them. And if recognized remove it as after error it must function again in order to flash or what ever..
Here is one older post showing pin connecting for Amlogic,
that other was Actions Semi. Both go a mode that enables flashing when device looks dead. I don't know about Allwinner, is it similar...
How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - Ainol Novo 7 Crystal
Page 1 of 47 - How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0 - posted in Ainol Novo 7 Crystal: How To Unbrick Your Amlogic AML8726-MX Series Tablet - v2.0If Ive helped you unbrick your device please consider a donation, even if it is small it will help!My laptop is currently all...
www.slatedroid.com
So it seems that would be all, and the device got bricked...
I started the device with 7 and 8 pin of Flash memory connected - it was connected to PC and PhoenixSuite with original img loaded was running.Phoenix asked me immediately if I want to format the device - I clicked no, and it still started to flash the memory... It finished succesfully, device restarted and...now it freezes on initial logo.
Phoenix and adb recognize the device now, but adb shell doesn't work:
- exec '/system/bin/sh' failed: No such file or directory (2) -
and when I try to repeat flashing, phoenix recognizes device, but once I click upgrade - device resets, and upgrade is not performed...
EDIT: It's not that bad... I managed to make it working again on original software, and after one more reflash - ADB works well
Thanks a lot for all your help!
Did the reset hole fix it?
Maybe you should have formatted it in case the data is the reason to the freeze. But how it recovered?...
This Allwinner seem to be quite good.
Open source and giving info.
FEL - linux-sunxi.org
linux-sunxi.org
Installing to NAND - linux-sunxi.org
linux-sunxi.org
FEL/USBBoot - linux-sunxi.org
linux-sunxi.org
matisys said:
after one more reflash - ADB works well
Thanks a lot for all your help!
Click to expand...
Click to collapse
Great! Now disable that ota updater apk so it doesn't update it again...
It's actually hard to tell how it got fixed... instruction tells to not format the storage to not loose the unique device number - so I didn't, but it seems that it got formatted by itself as I lost all my pictures, but number remained untouched.
Now adb is enabled and I can freely connect to it - seems that something simply went wrong during previous upgrade years ago.
build.prop file gets restored after every reboot, so I can't put and store any changes there...
And OTA is not an issue as this device is not supported for a long time now And I'm not exactly sure how to do it, and feel a bit afraid of touching it when it finally works...
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
matisys said:
But just to finish entire project - can you recommend some reliable android SSH and FTP server? Or maybe something to share a folder via SMB?
Click to expand...
Click to collapse
Not really but that android version limits the choices nicely...
Here is one saying it's open source.
swiftp
A FTP Server for your Android device.
ppareit.github.io
I think I once tested cifs in that Action Semi but it was long ago and was ready made in that test boot img...
[HOW TO] 2-way network file sharing on Android
Hi everyone, just thought I'd write up some quick instructions on how to set up file sharing between Android and a PC - both mounting Windows shares on Android, and Android on Windows. I was always frustrated by iOS's inability to do this easily, and it was one of the major reasons I switched...
forums.androidcentral.com
Thanks. Finally, after some trials I used SSHDroid and it's quite decent...
Can you also tell me how to permanently edit build.prop file? Mine is reverted to original after reboot. Device is factory rooted.
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy Tab Active Pro 10.1 SM-T547U, SM-T547U1 and SM-T547W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download TWRP for Tab Active Pro 10.1: gtactivexl and extract to recovery.img
3. Download and install magisk stable
4. Press the Install button in the Magisk card
5. Make sure “Recovery Mode” is checked in options. In most cases it should already be automatically checked.
6. Choose “Select and Patch a File” in method, and select the recovery.img.
7. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
8. Use 7zip to compress the patched recovery.img to tar (rename it to recovery.img after patch).
9. Put the the patched TWRP tar for your device with Odin in the AP slot and click start.
10. Reboot to recovery via recovery key combo.
11. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.12. Go back to Wipe > Format Data > type yes.
13. Reboot to system, Enjoy.
Magisk in Recovery:
If your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.
Since Magisk now hijacks the recovery, there is a special mechanism for you to actually boot into recovery mode. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick search online should easily get you this info. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.
As a summary, after installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)
(Note: You CANNOT use custom recoveries to install or upgrade Magisk in this case!!)
Click to expand...
Click to collapse
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@jesec for unlock guide
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
28.05.2021 - Initial Release.
T547U – A Perfect Device for Android Auto Head Unit
Afaneh, thanks for your great work. SM-T547U is a very special device, manufactured in 2019, and ignored since then. What I mostly like about TWRP is its excellent and clean Backup & Restore of the entire Android Operating System, everything done outside of Android environment. I have tested this TWRP brought forward by Afaneh on my “Galaxy Tab Active Pro” and it works without flaws.
I have bought this special device to install it in my car as a head unit. Checkout the web and see for yourselves what guys are doing with their tablets to bypass the expensive head units manufactured by the OEM like Kenwood, Alpine, but these OEM head units lack full compatibility with Android devices. The current Android Auto is still in development stage, it takes so long to connect with Android devices and whenever it does so, only about five apps in your android device are synced; not worth it. Whenever these manufacturers create new things, they downgrade their innovations at the same time to save money. The new 10 inches screen sold by these manufacturers no longer come with DVD function, the offline GPS removed and Google map added so that you pay to navigate the streets, their WIFI-certified does not necessarily mean that you can use it to navigate the internet and update softwares, but just to connect your external devices,…the list is long. Below is a link to an example of what I want to do with my tablet…
According to the above video which was recorded in 2017, Root + Xposed are needed to carry out the project, and since Xposed was not yet available by then he recommended choosing SM-T825, most especially for those living in USA and for compatibility with AT&T.
Well, as for me, I am choosing T547U because its technical features are far better than that of T825. Also remember that T547U is a North American model and it is compatible with all registered telecommunication companies in the USA and Canada. When I bought T547U, it came with Canadian Android version, and after unlocking the bootloader, I installed the USA Android version. See the attached image called "CSC_Code", showing all the available companies in the USA that you can switch to, for their extra services if you want. Xposed is available for Android 10_Q and 11_R; I have it installed on my T547U (see the attached images below). For Root and Xposed contact Afaneh, the Admin. What I like about his project is the electrical connection and the software programming of the tablet to get information from the automobile. If you know of better programming softwares than the one he has used in the video, let me know. To install my T547U, I will use the Ram-mount specially made for my device as can be seen in the following link. It has POGO pins, which means I will be inserting my device to use in the car and removing it to use at home (theft-proof).
https://www.rammount.com/part/RAM-HOL-SAM52PD2U
The reasons why I have chosen T547U is as follows:
1. This is the only tablet that I can find in the market with 7600 mAh battery and it is removable like the old phones! I hope we all know the advantages of a removable battery.
2. It has a USB-C v3.1 with DEX function, compatible with HDMI. The HDMI which means Audio + Video + Data through the same port makes it easy for connection in the car and eliminating the use of so many adapters.
3. As a Samsung device, it has a very wide support groups that know how the firmware works.
4. It has 3.5mm jack. Many modern devices no longer have this.
5. It has LTE and a SIM-card slot. Its use for cars is explained in the link to the video.
6. Its ruggedness is fit for use in extreme conditions. P68 dust/water resistant (up to 1.5m for 30 mins). This means if you like you can permanently install it in your car and park it outside under -30 degree centigrade. This ruggedness is my warranty that is already built into the device. So I’m not worried about losing the Samsung warranty for unlocking the bootloader and rooting T547U. All my old devices that I no longer use are still working; this means if I take good care of this rugged tablet, it will outlive the Samsung 2-year warranty with so many conditions that hardly gives you a new device in exchange when something goes wrong.
7. I don't care about Wi-Fi calling that discourages so many people from unlocking and rooting their devices because it is not always a free service. Additional charges may apply – in case your Wi-Fi connection is lost for some reason, the call may switch to your data and cause you to pay extra. The best Wi-Fi calling are Skype, WhatsApp, etc.
Thanks for your attention. See all the attached images, and I will keep you informed as I progress.
https://www.samsung.com/ca/tablets/...ro-10-1-inch-black-64gb-wi-fi-sm-t547uzkaxac/
sunnyy15 said:
T547U – A Perfect Device for Android Auto Head Unit
Afaneh, thanks for your great work. SM-T547U is a very special device, manufactured in 2019, and ignored since then. What I mostly like about TWRP is its excellent and clean Backup & Restore of the entire Android Operating System, everything done outside of Android environment. I have tested this TWRP brought forward by Afaneh on my “Galaxy Tab Active Pro” and it works without flaws.
I have bought this special device to install it in my car as a head unit. Checkout the web and see for yourselves what guys are doing with their tablets to bypass the expensive head units manufactured by the OEM like Kenwood, Alpine, but these OEM head units lack full compatibility with Android devices. The current Android Auto is still in development stage, it takes so long to connect with Android devices and whenever it does so, only about five apps in your android device are synced; not worth it. Whenever these manufacturers create new things, they downgrade their innovations at the same time to save money. The new 10 inches screen sold by these manufacturers no longer come with DVD function, the offline GPS removed and Google map added so that you pay to navigate the streets, their WIFI-certified does not necessarily mean that you can use it to navigate the internet and update softwares, but just to connect your external devices,…the list is long. Below is a link to an example of what I want to do with my tablet…
Click to expand...
Click to collapse
My active pro came with Android 10, but I'm set on using 9 because of certain apps I want to use that interact with the clipboard, among other reasons. I just turned it on for the first time, and when I activated developer options the OEM unlock option wasn't there, so I reset the tablet to factory settings. Will I have to wait 7 days before I can install TWRP?
Also, can I just follow this tutorial to downgrade to android 9 after unlocking the bootloader (but before installing TWRP...?)?
This is my first time trying to root something (which I'm planning on doing after I've downgraded), but since it seems like there are pretty much no threads about the active pro (wtf!), except maybe this one about the tab active 2, any tips you have would be appreciated! I'm particularly worried about where to safely download Odin and the firmware (I'm just using the links in that video for now), but atm I'm stuck at the unlocking the bootloader phase...I'm a total noob tbh. Installing TWRP will make installing Magisk easier, right?
If I'm being honest, I'm not 100% sure about what steps to even follow...like to unlock the bootloader, can I follow the steps in this video? (I already have platform tools/fastboot/adb downloaded to my computer) Or does it depend on the device?
Since there are so many different guides for different devices (except the tab active pro 10.1 unlocked...), I'm just not confident I'm following the right steps for anything, you know?
mrlawrence said:
My active pro came with Android 10, but I'm set on using 9 because of certain apps I want to use that interact with the clipboard, among other reasons. I just turned it on for the first time, and when I activated developer options the OEM unlock option wasn't there, so I reset the tablet to factory settings. Will I have to wait 7 days before I can install TWRP?
Also, can I just follow this tutorial to downgrade to android 9 after unlocking the bootloader (but before installing TWRP...?)?
This is my first time trying to root something (which I'm planning on doing after I've downgraded), but since it seems like there are pretty much no threads about the active pro (wtf!), except maybe this one about the tab active 2, any tips you have would be appreciated! I'm particularly worried about where to safely download Odin and the firmware (I'm just using the links in that video for now), but atm I'm stuck at the unlocking the bootloader phase...I'm a total noob tbh. Installing TWRP will make installing Magisk easier, right?
If I'm being honest, I'm not 100% sure about what steps to even follow...like to unlock the bootloader, can I follow the steps in this video? (I already have platform tools/fastboot/adb downloaded to my computer) Or does it depend on the device?
Since there are so many different guides for different devices (except the tab active pro 10.1 unlocked...), I'm just not confident I'm following the right steps for anything, you know?
Click to expand...
Click to collapse
If device shipped with android 10 you cant go back to 9.
And its better to post your device model so I can check.
afaneh92 said:
If device shipped with android 10 you cant go back to 9.
And its better to post your device model so I can check.
Click to expand...
Click to collapse
It's model number SM-T547U (tab active pro unlocked) - but this device is supposed to support Android 9-11, no?
mrlawrence said:
It's model number SM-T547U (tab active pro unlocked) - but this device is supposed to support Android 9-11, no?
Click to expand...
Click to collapse
You can downgrade to android 9 if you are on v2 bootloader only.
afaneh92 said:
You can downgrade to android 9 if you are on v2 bootloader only.
Click to expand...
Click to collapse
My baseband version is T547UUEU4BUC1_B2BF
Does that mean I have bootloader version 4?
Do any devices even have a version that low in 2021? Or is it device dependent?
Anyway, I'd still like to root my tablet either way, but (assuming I don't have bootloader v2) that's really disappointing to hear about downgrading...
mrlawrence said:
My baseband version is T547UUEU4BUC1_B2BF
Does that mean I have bootloader version 4?
Do any devices even have a version that low in 2021? Or is it device dependent?
Anyway, I'd still like to root my tablet either way, but (assuming I don't have bootloader v2) that's really disappointing to hear about downgrading...
Click to expand...
Click to collapse
Yes its 4.
You cant go back to 2020 firmware too, and dont update to v5 if you want to root.
contact me for bootloader unlock
mrlawrence said:
My active pro came with Android 10, but I'm set on using 9 because of certain apps I want to use that interact with the clipboard, among other reasons. I just turned it on for the first time, and when I activated developer options the OEM unlock option wasn't there, so I reset the tablet to factory settings. Will I have to wait 7 days before I can install TWRP?
Also, can I just follow this tutorial to downgrade to android 9 after unlocking the bootloader (but before installing TWRP...?)?
This is my first time trying to root something (which I'm planning on doing after I've downgraded), but since it seems like there are pretty much no threads about the active pro (wtf!), except maybe this one about the tab active 2, any tips you have would be appreciated! I'm particularly worried about where to safely download Odin and the firmware (I'm just using the links in that video for now), but atm I'm stuck at the unlocking the bootloader phase...I'm a total noob tbh. Installing TWRP will make installing Magisk easier, right?
If I'm being honest, I'm not 100% sure about what steps to even follow...like to unlock the bootloader, can I follow the steps in this video? (I already have platform tools/fastboot/adb downloaded to my computer) Or does it depend on the device?
Since there are so many different guides for different devices (except the tab active pro 10.1 unlocked...), I'm just not confident I'm following the right steps for anything, you know?
Click to expand...
Click to collapse
Welcome to Galaxy Tab Active Pro. The process to get all what you want with this device is long, but don't be scared; step by step makes a long journey and most of what you want are possible. Answering your questions by adding to what Afaneh had already told you...
Only devices with Exynos chipset have the “OEM unlock” toggle button. Our Tab Active Pro has Qualcomm' Snapdragon chipset and even if you have bootloader unlocked and device rooted, you will never see "OEM unlock" in the Developer option.
No need to wait 7 days before installing TWRP. The only requirement is to get your bootloader unlocked. Afaneh will help you to do that. When it is advertised "Samsung Galaxy unlocked...", that only means "Network unlocked" so that you can use the LTE with any phone operator, but the bootloader is still very locked Before you unlock the bootloader make sure are on the bootloader version you like and available.
You told Afaneh that your baseband is T547UUEU4BUC1 ("_B2BF" for USA). When I bought mine it has the Canadian version T547UVLS4BUB1 on Android 10. Have a look at page 3 of the file attached...
T547UUEU2BTH6_B2BF (August 2020 update) Android 10
T547UUES2ATD1_B2BF (April 2020 update) Android 09
This is where a downgrade of OS is possible because Android 9 and 10 have the same bootloader version 2. So what Afaneh is telling you is that if you unlock your bootloader and later on downgrade with the same bootloader, you should have no problem. But if you downgrade or upgrade to a different bootloader, your bootloader will automatically lock up again and back to square zero, hahaha... So you decide.
I have the SM-540 (the wifi-only version) of the Galaxy Tab Active Pro 10.1, exact model is SM-540NZKAXAR. Is this device supported? I looked it up and it also has the Snapdragon chipset.
studentoflife said:
I have the SM-540 (the wifi-only version) of the Galaxy Tab Active Pro 10.1, exact model is SM-540NZKAXAR. Is this device supported? I looked it up and it also has the Snapdragon chipset.
Click to expand...
Click to collapse
Need to be exact chipset to work.
sunnyy15 said:
Welcome to Galaxy Tab Active Pro. The process to get all what you want with this device is long, but don't be scared; step by step makes a long journey and most of what you want are possible. Answering your questions by adding to what Afaneh had already told you...
Click to expand...
Click to collapse
Thanks for all the help. I actually stopped at the disable encryption step because I wasn't sure if it was necessary/safe.
I've been reading a little online about it and it sounds like maybe it's no longer necessary, but might speed up my device? Can you or @afaneh92 offer some more insight on that for this specific tablet? Like, is there any downside to keeping it enabled? Can I disable it later? What kinds of risks come with disabling it?
I hate to say it, but this one concern has been holding me back this whole time (I was able to get the bootloader unlocked with Afaneh's help), so if you could help me out with this I'd appreciate it. I honestly was just too embarrassed to ask before.
mrlawrence said:
Thanks for all the help. I actually stopped at the disable encryption step because I wasn't sure if it was necessary/safe.
I've been reading a little online about it and it sounds like maybe it's no longer necessary, but might speed up my device? Can you or @afaneh92 offer some more insight on that for this specific tablet? Like, is there any downside to keeping it enabled? Can I disable it later? What kinds of risks come with disabling it?
I hate to say it, but this one concern has been holding me back this whole time (I was able to get the bootloader unlocked with Afaneh's help), so if you could help me out with this I'd appreciate it. I honestly was just too embarrassed to ask before.
Click to expand...
Click to collapse
The disabler is just to make twrp stick after reboot and to diasable data encryption so you can read it in twrp and make internal storage readable.
@afaneh92 Could this process resolve an ex corporate Active Pro still locked down by MDM?
When I attempt to use Odin to apply the latest samsumg firmware I get the following error on the Download bootloader screen: MDM Mode. Can't download (PIT)
My model is a SM-T545
I'm not in the US/Canada region either.
I can perform factory resets, and if I let it go through the MDM/Knox Cloud setup I can enable developer features. If I enable flight mode at the correct stage I can enable OEM Unlock and USB debugging but to date that hasn't helped with the ability to apply the firmware via ODIN. I did also try nand erase and re-partition but it always fails before any changes are made to the device.
Jaffau said:
@afaneh92 Could this process resolve an ex corporate Active Pro still locked down by MDM?
When I attempt to use Odin to apply the latest samsumg firmware I get the following error on the Download bootloader screen: MDM Mode. Can't download (PIT)
My model is a SM-T545
I'm not in the US/Canada region either.
I can perform factory resets, and if I let it go through the MDM/Knox Cloud setup I can enable developer features. If I enable flight mode at the correct stage I can enable OEM Unlock and USB debugging but to date that hasn't helped with the ability to apply the firmware via ODIN. I did also try nand erase and re-partition but it always fails before any changes are made to the device.
Click to expand...
Click to collapse
No
is it possible to root Active pro SM-545 (gtactivexleaa), SMD 670, areno 615, android 10?
Thank you
edokk69 said:
is it possible to root Active pro SM-545 (gtactivexleaa), SMD 670, areno 615, android 10?
Thank you
Click to expand...
Click to collapse
No different device.
Thank's
Picked one of these up recently and looking to get root going. This is the USA Wifi+LTE version, T547U.
The unit came with Android 11 out of the box, and my baseband versoin is T547UUEU5CUI2_B2BF.
Am I completely out of luck? Would I be better off with the Wifi-only version?
Thank you