[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
Related
Being a noobie and learning a lot recently, I wanted to lay out step-by-step instructions, for all of us other noobs, on how I went from GB (Gingerbread) 2.3.4 with custom rom to stock ICS (Ice Cream Sandwich) 4.0.3 via T-Mobile OTA (Over the Air) upgrade. These are steps for my T-Mobile Amaze 4G with S-on and written in noobie language. I found some variations but none were in great detail or explained everything. I wanted to write this to save all other noobies all the lost hours I’ve spent reading forums after forums.
For background purposes, T-Mobile Amaze will not receive its update to ICS if the phone has a custom rom so you’ll need to get the phone back to its original software. Likewise, if you have a warranty issue and need to send your phone back, you’ll want to bring it back to stock.
In my instructions, I’ll try to answer all the questions I had myself (from a noobie’s perspective) so forgive me if you’re a pro.
Disclaimer: Do this at your own risk. I will not be liable for any damages whatsoever. If you’re unsure, then do your own research for supporting evidence. These are the steps I did to my phone and how I accomplished getting stock ICS on my T-Mobile Amaze 4G. These steps may not apply to you or your phone.
Terms and definitions:
•RUU (ROM Utility Update): For the purposes of this posting, this is the original software (operating system) issued for the phone. GB 2.3.4 is one RUU and ICS is another RUU.
•Custom ROM: For the purposes of this posting, this is a modified RUU not from T-Mobile/HTC but customized by someone else a lot smarter than me.
•OTA (Over the Air): For the purposes of this posting, this is an upgrade to your phone’s operating system. In these steps, an OTA will be used to go from GB to ICS. OTA’s get pushed to the phone directly from the provider (T-Mobile) by using the phone’s software updates.
•S-on (Security on): With Security on, you’re limited to what you can flash (i.e. install) on your phone. For this purpose, you can flash a stock RUU with S-on as long as you’re staying on the same operating system or upgrading, however, your bootloader must be locked (see below). You cannot flash a downgraded RUU with S-on. For example, if your phone is S-on and you’re on GB (with bootloader locked), you can flash a GB RUU or ICS RUU. However, if you’re on ICS, you cannot downgrade to GB with S-on. To downgrade, you’ll need S-off.
•S-off (Security off): With Security off, you are much less limited and can flash just about any compatible software (i.e., roms) including stock RUUs. To get S-off, you’ll have to do the wire trick method along with a helpful program. For the purposes of this posting, having S-off doesn’t matter so I won’t go into how to get S-off.
•Bootloader locked/unlocked: Bootloader is a program executed on your phone before your operating system (i.e. GB or ICS) runs. Locked bootloaders will not allow custom roms (unless S-off, I believe), but will install stock RUUs. If you have a custom rom, you’re bootloader is probably unlocked.
•How to check if you’re S-on/off and locked/unlocked: Power on the phone into bootloader by holding the volume down rocker and power button at the same time. In bootloader, look at the top and it will say, “Locked”, “Relocked” or “Unlocked”. Below that, it should say S-on or S-off somewhere.
With these steps, you’ll backup the phone (just in case something goes horribly wrong), flash stock GB 2.3.4 RUU, and upgraded to stock ICS 4.0.3 with HTC/T-Mobile OTA software update. As a side note, the stock ICS RUU can be flashed instead of GB RUU, thus, skipping the upgrade step. However, my research shows a lot more successful upgrades by doing the following method. So that’s the route these instructions will take.
1.You’ll need at least one microSD card for these steps. With the phone off, eject the microSD card in your phone if you have one in there. If you have multiple microSD cards, then set this one aside, if not, copy any information from the card onto your computer if you want to save it. Then format the card.
2. Turn on the phone and wait for it to boot up. Connect your phone to a computer with a USB cable, select data disk on the phone, and use your computer to backup or copying anything on your phone that you would like to keep. Pictures, music, videos, etc… What you’re about to do will wipe your phone clean as if it’s from T-Mobile out of the box. Think of it as going from Windows XP to Windows 7.
3. Next, turn off your phone, unplug USB cable, and make sure to have your phone well charged. Now is a good time to charge it with a wall plug.
4. On your computer, download T-Mobile’s original GB RUU. If the link doesn't work, do a search on XDA’s site and you should find it. The file name is: “PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed”. http://forum.xda-developers.com/showthread.php?t=1617644
5. After the download is complete, rename this file to PH85IMG Make sure your computer sees this as a .zip file. Keep it as a .zip file. You’ll need to copy this later so know where you saved it.
6. On your computer, download and install Hasoon2000 toolkit for Amaze. Make sure it’s for Amaze. There are several toolkits available. If the link doesn't work, do a search. You’ll also need WinRAR to extract the software. http://forum.xda-developers.com/showthread.php?t=1493905
a.Note: I do not personally know Hasoon2000, I only used his toolkit. During all my readings, he appears to be a reputable person who has helped thousands of people and noobs. With that said, whenever I attempted to install his toolkit, my Norton antivirus gave me a virus warning and would not install. This could be a false warning, but I have no idea. To play it safe, I took my extra laptop and made a system image on an external hard drive. System image will duplicate your entire computer including operating system at the current time. Once completed, I disconnected the external hard drive, unplugged my internet (or turned off WiFi antenna), disabled my antivirus software, installed the toolkit, and did the remaining steps below. Finally, once I finished using the toolkit, I reimaged my laptop to where it was before. If you decide to go this route, make reimaging the very last thing you do. You may need the toolkit if you run into problems. I had no problems.
7. Make sure your phone is well charged. I had mine over 95% charged.
8. If you have a custom rom, then you’re phone is probably unlocked. Look above under “terms and definitions” to see how to check if you haven’t done so already. If unlocked, go to step 10. If locked, continue on.
9. To flash a stock RUU with S-on (i.e. install stock GB or stock ICS), you’ll need to have your phone’s bootloader locked; however, if you want to backup you phone first, you’ll need to unlock your bootloader. Follow Hasoon2000 video instructions to unlock your phone. To watch his video, go to youtube.com and searched for “Hasoon2000”. You’ll see two videos. Watch the 11 minute video. You can stop watching after flashing the custom recovery. http://www.youtube.com/watch?v=9b-BReM6HF8
a. Steps to unlocking bootloader at a high level: Install HTC drivers. Request a token ID (a request to unlock your phone from HTC). Submit and receive your unlock.bin (code to unlock your bootloader), and unlock bootloader. All seen in the video.
10. If you skipped step 9, you need to watch hasoon2000 toolkit tutorial video. In the next few steps, you will be installing HTC drivers and flashing a custom recovery. The video will go over these steps. Don’t worry about anything else if you’re unlock. If you’re still locked, go back to step 9. To watch the video, go to youtube.com and searched for “Hasoon2000”. You’ll see two videos. Watch the 11 minute video. http://www.youtube.com/watch?v=9b-BReM6HF8
11. With your bootloader unlocked, power on your phone normally, have the toolkit open and connect your phone to your computer via USB cable.
12. Right here, my computer automatically installed drivers. I waited for the process to finish.
13. In the toolkit, select “Install HTC Drivers” and click “Go”. This will install drivers on your computer to run your HTC Amaze.
14. At anytime in these steps, if you see the cmd screen (black command screen) pop up, then wait for all the command lines to stop writing. Once done, close the cmd screen. The toolkit cannot run future commands if this window is open.
15. On your Amaze, make sure you’re phone settings are connected to PC as “charge only”. For GB go to, settings>PC Connections (I believe, I already upgraded to ICS so I can’t confirm)
16. Next make sure “Enable USB debugging” is selected: For GB it’s: Settings>Apps>Development>USB Debugging
17. After that, you will flash a custom recovery onto the phone so that you can make a backup. 4EXT is the custom recovery that was highly recommended and is the one I flashed. To flash 4EXT, use the toolkit, select “4EXT”, and click “Flash Recovery”. Watch the video to see the flashing process, your computer’s reactions, and your phone’s reactions. As a side note: I already had a custom recovery flashed on my phone from the previous owner but it was out-of-date. After I flashed 4EXT, it appeared to have flashed over my out-of-date custom recovery.
18. Once the flashing process is complete and after 4EXT is installed, power off your phone and unplug the USB cable.
19. Powered on the phone as normal and make sure everything is working as it should. If not, you may want to re-flash 4EXT. I didn’t have any problems.
20. Power off the phone.
21. Pull battery
22. Insert a decent size formatted microSD card to store your phone’s backup. Mine was 4GB. I believe it took over 2GB of space.
23. Reboot into Bootloader by holding the bottom volume rocker and power button at the same time.
24. In Bootloader, use your volume rocker to highlight “recovery” and hit the power button to select. This will boot you into your newly flashed 4EXT custom recovery program.
25. Once in 4EXT, navigate to “backup” and use the option to backup to an external card.
26. After the backup is complete, unmount your card if that option is available. I can’t remember. Then select the option to power off your phone.
27. With the phone off, pull battery, and eject microSD card. If you still have an extra microSD card, put this one aside, if not, copy the backup onto your computer with a card reader. You’ll need this microSD card again later.
28. Put the battery back in (and back cover if you want), power on the phone as normal, and make sure you’re still good.
29. With the toolkit open and the phone on, connect the Amaze back into the computer with the USB cable.
30. Right here, my computer starting making the USB connection/disconnection sounds. I waited until the beeps finished.
31. Next, you need to relock the phone. To do this, go back to the toolkit and select “relock” and click “do command” and let the toolkit do all the work. If you see the cmd screen (black command screen), then wait for all the command lines to stop writing and close the screen.
32. After it’s done and if your phone is on, then power off the phone.
33. Power on the phone into Bootloader by holding the bottom volume rocker and power button at the same time.
34. Look at the top of your screen in Bootloader and it should say, “Relocked”. You must be either “Relocked” or “Locked” to go any further (for S-on). If you’re not, try to relock again.
35. Power off the phone
36. Unplug USB cord from computer
37. Now get a formatted microSD card and copy the PH85IMG file you download earlier. Put this file on the root of a microSD card. Root means directly on the card with no folders. This file is T-Mobile’s stock Ginger Bread 2.3.4 RUU in .zip format.
38. Put the microSD card into the phone
39. Power on the phone into bootloader by holding the bottom volume rocker and power button at the same time.
40. Upon starting up, it should start extracting the files from the SD card. Once complete, it will ask you if you want to install updates. Select “yes” by using volume UP rocker. If you accidently hit down, then you just cancelled it. No worries. Power off and then go back to step 39.
41. While it’s installing updates, it will say, “No image or wrong image” on the first two files. That’s okay. You’re still good.
42. Now you’ll need to wait awhile. For each file, you should see a status bar on the right. The “System” file takes awhile so be patient.
43. You should get a “complete” message once complete. Select “Reboot”
44. This reboot will take you into your newly flashed stock T-Mobile GB 2.3.4 RUU. The first boot up takes longer than normal so be patient.
45. Now the phone will act like it’s new out of the box so you’ll have to go through a few setup procedures. Just go through the forced screens and don’t worry about anything else because it’s all about to get wiped and upgraded to ICS.
46. Now while the phone is on, setup your WiFi so you’ll get a fast download.
47. On your phone, check for software updates: Settings>About Phone>HTC updates (software updates). I saw both HTC updates and Google updates. I went with HTC updates and selected “check for updates” at the bottom.
48. After going through the update process, my phone rebooted and installed ICS. You’ll see a hard drive image and some arrows during the reboot and installation process.
49. After installation, the phone will begin to boot up. Remember this is the first boot on ICS so it’ll take awhile. Be patient.
50. Once your phone is on, go to settings>About Phone>Software information. Under Android version, you should see 4.0.3. If so, you’re done! Enjoy! If not, go back to software updates, and click “check now” again.
Hit the thanks button if you appreciate these steps. I’m sure I maybe technically incorrect on some bits. Remember, I’m a noob trying to help other noobs so please take it easy on me.
Wow. Pretty long lol. You added extra info that was not really necessary, but it's still fine and it works!
Thanks.
hasoon2000 said:
Wow. Pretty long lol. You added extra info that was not really necessary, but it's still fine and it works!
Click to expand...
Click to collapse
Thanks Hasoon2000. That means a lot coming from you. Us noobies couldn't do it without your toolkit.
hi
Mine is unbranded simfree amaze when its done it says Model id incorrect.
Can anyone explain what to do?
talpur1 said:
Mine is unbranded simfree amaze when its done it says Model id incorrect.
Can anyone explain what to do?
Click to expand...
Click to collapse
there should be a manual method somewhere around here that would probably work better for you. im not sure where it is exactly but f i come across it ill tell you
@ OP
{
"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"
}
No but seriously that is really long
EclipzeRemix said:
@ OP
No but seriously that is really long
Click to expand...
Click to collapse
i died!!!!
talpur1 said:
Mine is unbranded simfree amaze when its done it says Model id incorrect.
Can anyone explain what to do?
Click to expand...
Click to collapse
You would have to s-off then superCID, then you can flash it
sent from my
NRGized amaze
powered by Faux
I have been trying to S off but cannot get it to work.
The adb keeps giving me errors.
I tried to turn off firewall and antivirus.
But cannot get it to work.
Tried to flash through RUU but to no avail.
Lets see.
If anything can be flashed on s on do let me know.
I am rooted and bootloader is unlocked.
Regards
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.
Update:This tutorial might no longer be valid. It was meant for stock to lollipop beta. Now there is a stable update. Please check needrom website for latest updates.
Disclaimer: This is a lengthy process with downloads of up to 2GB or more required. This is based on my understanding of machine translated Chinese web pages and forums. This process was done on my own ZTE Nubia Z7 Max and it now successfully runs the Google Play Store on Lollipop. The Lollipop version is only 5.0. Please take caution in reading instructions, I take no responsibility if you end up with a bricked phone due to various reasons (improper downloads, power failure or thermo-nuclear war)
Note: You cannot easily go back to Kitkat after this process, please be sure that you want Lollipop. I have not faced any issues with the Lollipop Update, but just letting you know.
Background:
I have a Z7 Max with Nubia OS v1.59 (Kitkat 4.4.2) and I found out from another forum that a Lollipop version v2.13 (Official) is available. This is the process I followed:
Pre-requisites:
A ZTE Nubia Z7 Max (model: NX505J, Hardware Version: NX505JMB_A)
Windows PC (I did this on Windows 7 64-bit)
Drivers installed (When the phone is connected, it will appear under device manager as "Android Sooner Single ADB Interface")
Step 1: Upgrade to v 1.64
The update to V 2.13 can only happen from v 1.64. So first you have to get to v 1.64, if you are not already on it.
Download the v1.64 update zip (requires sign up at Need ROM)
Using the stock recovery update the phone through normal process
Copy update zip to SD Card
Apply update from SD Card etc. etc.
There will be no reset of data and apps, however you will lose Google Play Store/ Services connectivity and Root. It hardly matters as the phone will be reset in the next few steps.
Your phone must be on v1.64 now.
Step 2:Enable ADB and Factory ports
Open your dialer and input *#7678#
You will see two check boxes Factory[] and Adb[]
Check both
Step 3: Download the update file and update tool
Extremely Important: The update from Kitkat to Lollipop will reset the device as the partition is re-written. This is why the tool is required. (No the update cannot be flashed using a custom recovery)
Updater Tool
Download Link
Password: uslf
The v2.13 Lollipop update
Download Link
Password: 5u93
Note:
The above file might require you to sign up to Baidu and install their application to download large files. While registering for Baidu, you might be faced with a Chinese CAPTCHA. Use LINE Dict to draw the characters you see and solve the CAPTCHA
This will be a .tar file (use a utility like 7zip to extract the entire contents into a single folder "NX505J_CNCommon_V2.13")
Step 4: Using the update tool to update v1.64 to v2.13
Run the "nubia NX505J Updater V1.5.7.exe" installer
It will install the updater tool on your PC under "nubia NX505J Updater"
Run the updater tool from your All Programs menu
If you have all the drivers installed and ports enabled, the phone icon in the bottom will have a white tick mark in green bubble, else it will show an exclamatory mark (!) in red bubble. If red, please check drivers (use the driver installer that comes with phone, appears as CD Drive) and that ports are enabled
{
"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"
}
Click the top button after "C:\Nubia Backup" and browse to the NX505J_CNCommon_V2.13 folder
Only when you have a tick icon and the folder selected, press the bottom button (to the right of "0/100")
This click will reset the device so please proceed with caution
The process will start and the phone will restart several times.
After this process you should have a working Lollipop Installation. (about 3-4 minutes)
Note:The process will stop at 92% for some time, don't worry about this, don't touch the phone or computer!!
I have linked to the Chinese official instructions from the Nubia marketing team below
Step 5: Using Temporary Recovery to Flash Gapps
On the Computer
Download the Recovery exe from This link here (Filename: Z7max_2.13_Android _5.0_CWM recovery.exe)
Running this file will give you a terminal screen with 10 options.
Press Option "2" - I don't know what it does, but the phone will reboot - Probably the bootloader is unlocked.
Connect your phone and copy to the SD card the Gapps package: I used the pico pack from Paranoid Android thread here
After copying the file to SD card, press option "5" - This boots the phone into temporary recovery
In the recovery:
Second option is to flash zip from SD card
Select your file from the SD card
Select the second line on next screen (This is probably - No, - Yes, Flash Zip options)
Gapps gets installed
Go back to main screen of recovery and select first option, you will be presented with two options, Reboot and Reboot Recovery, choose second option to get to Lollipop with Google Play store installed.
Root
Follow the same process to get root by flashing the SuperSu zip through the temporary recovery
Link to the SuperSu: Here
Reference
Lollipop Update Thread: http://bbs.nubia.cn/thread-419364-1-1.html
How to use the Update Tool: http://bbs.nubia.cn/thread-418088-1-1.html
Need ROM Page for v2.13: http://www.needrom.com/download/z7-max-2-13-android-5-beta_eng_chi/
Another recovery article (which I did not use): http://bbs.nubia.cn/thread-417675-1-1.html
Thanks
To Google: For all the wonderful Android ecosystem and For Google Chrome's translate option that helped me understand Chinese website (A few laughs at some of the translations)
The bbs.Nubia.cn forum where all the action happens
Need ROM for some of the crucial downloads in this article
XDA Forum for teaching me a lot about ROMs, Recoveries, and Roots
This is my first elaborate tutorial, I hope you like it. Please help out with "Thanks"
Things I have noticed over two days of usage :
Good:
Pretty good battery life
Smooth transitions
Bad :
The infrared control app is no longer available, nor do the apps from the play store work. Due to lack of permissions to the IR blaster.
Missing one - hand setting that allowed to use the large screen as small screen to left or right.
Home screen looks like from a small screen phone. Fonts in apps like Whatsapp etc. Look very large. Making the phone not feel like full HD resolution.
craagz said:
Things I have noticed over two days of usage :
Good:
Pretty good battery life
Smooth transitions
Bad :
The infrared control app is no longer available, nor do the apps from the play store work. Due to lack of permissions to the IR blaster.
Missing one - hand setting that allowed to use the large screen as small screen to left or right.
Home screen looks like from a small screen phone. Fonts in apps like Whatsapp etc. Look very large. Making the phone not feel like full HD resolution.
Click to expand...
Click to collapse
sure，the ppi was changeed to 400
Good tutorial. But Nubia v2.13 still pretty much need a lot of improvements. I will wait for CM12 to be ported over properly than going for Nubia OS.
When flashing the 2.13 using the flashing tool, i get stuck at 15% where it says switching to download mode. My phone turns off and only the right backlit dot is lighted up. I looked over on the nubia forums and the said it could be because i hadnt turned off my antivirus software, so I went ahead and turned it off but it was the same. I even tried on another computer but same error.
Anyone know whats wrong?
Happened upon your post while I was looking to resolve my gapps issue from my upgrade to 1.64 and now 2.13. Had someone translate the chinese menu for me earlier today when I needed to use the stock recovery. Hope this helps everyone else.
Did not realize the bootloader needs to unlocked before can apply the gapps again. -_- Going to give it a shot now, thanks!
encountering data problem
I have data connection problem in ZTE Nubia Z7 max. I put 2 sim cards in 2 slots. When I change my default data connection to second sim slot, 1st sim carrier signal is lost. 1st signal is recovered when I changed the data connection to sim 1. Does anyone encounter this problem? In HTC Desire 826 dual sim phone, they are no encountering that problem. What is the cause of the problem? If anyone knows how to fix this, please help me.
pilililo2 said:
When flashing the 2.13 using the flashing tool, i get stuck at 15% where it says switching to download mode. My phone turns off and only the right backlit dot is lighted up. I looked over on the nubia forums and the said it could be because i hadnt turned off my antivirus software, so I went ahead and turned it off but it was the same. I even tried on another computer but same error.
Anyone know whats wrong?
Click to expand...
Click to collapse
Did you enable the fastboot and adb mode?
craagz said:
Did you enable the fastboot and adb mode?
Click to expand...
Click to collapse
How do I enable fastboot?
What i did enable was factory port and adb port.
Isnt fastboot supposed to be enabled by default on all phones?
pilililo2 said:
How do I enable fastboot?
What i did enable was factory port and adb port.
Isnt fastboot supposed to be enabled by default on all phones?
Click to expand...
Click to collapse
Did you go up to 1.64 before trying to flash the 2.13?
I know it is a bit late, but how is your phone doing?
Yes i did go to 1.64 before flashing. Didnt work though.
Right now im on the 14/4/2015 version of Cm12 which is very nice. Although i couldnt merge partitions which i would like to be able to do.
8Gb
Hi, here is the thing, i flash stock recovery 5.0 and make manual update to 3.08 (first guide on needrom), after flash TWRP v2.8.6.0 gaps etc. I have only 8gb memory ROM+ apps. And finnaly my question is: when i will use this Updater Tool, may i get full 32gb space please? Thx a lot for every help.
can this be done from 1.64 custom such as bb72 or must it be stock
Help please
Help me I can not seem
craagz said:
Disclaimer: This is a lengthy process with downloads of up to 2GB or more required. This is based on my understanding of machine translated Chinese web pages and forums. This process was done on my own ZTE Nubia Z7 Max and it now successfully runs the Google Play Store on Lollipop. The Lollipop version is only 5.0. Please take caution in reading instructions, I take no responsibility if you end up with a bricked phone due to various reasons (improper downloads, power failure or thermo-nuclear war)
Note: You cannot easily go back to Kitkat after this process, please be sure that you want Lollipop. I have not faced any issues with the Lollipop Update, but just letting you know.
Background:
I have a Z7 Max with Nubia OS v1.59 (Kitkat 4.4.2) and I found out from another forum that a Lollipop version v2.13 (Official) is available. This is the process I followed:
Pre-requisites:
A ZTE Nubia Z7 Max (model: NX505J, Hardware Version: NX505JMB_A)
Windows PC (I did this on Windows 7 64-bit)
Drivers installed (When the phone is connected, it will appear under device manager as "Android Sooner Single ADB Interface")
Step 1: Upgrade to v 1.64
The update to V 2.13 can only happen from v 1.64. So first you have to get to v 1.64, if you are not already on it.
Download the v1.64 update zip (requires sign up at Need ROM)
Using the stock recovery update the phone through normal process
Copy update zip to SD Card
Apply update from SD Card etc. etc.
There will be no reset of data and apps, however you will lose Google Play Store/ Services connectivity and Root. It hardly matters as the phone will be reset in the next few steps.
Your phone must be on v1.64 now.
Step 2:Enable ADB and Factory ports
Open your dialer and input *#7678#
You will see two check boxes Factory[] and Adb[]
Check both
Step 3: Download the update file and update tool
Extremely Important: The update from Kitkat to Lollipop will reset the device as the partition is re-written. This is why the tool is required. (No the update cannot be flashed using a custom recovery)
Updater Tool
Download Link
Password: uslf
The v2.13 Lollipop update
Download Link
Password: 5u93
Note:
The above file might require you to sign up to Baidu and install their application to download large files. While registering for Baidu, you might be faced with a Chinese CAPTCHA. Use LINE Dict to draw the characters you see and solve the CAPTCHA
This will be a .tar file (use a utility like 7zip to extract the entire contents into a single folder "NX505J_CNCommon_V2.13")
Step 4: Using the update tool to update v1.64 to v2.13
Run the "nubia NX505J Updater V1.5.7.exe" installer
It will install the updater tool on your PC under "nubia NX505J Updater"
Run the updater tool from your All Programs menu
If you have all the drivers installed and ports enabled, the phone icon in the bottom will have a white tick mark in green bubble, else it will show an exclamatory mark (!) in red bubble. If red, please check drivers (use the driver installer that comes with phone, appears as CD Drive) and that ports are enabled
Click the top button after "C:\Nubia Backup" and browse to the NX505J_CNCommon_V2.13 folder
Only when you have a tick icon and the folder selected, press the bottom button (to the right of "0/100")
This click will reset the device so please proceed with caution
The process will start and the phone will restart several times.
After this process you should have a working Lollipop Installation. (about 3-4 minutes)
Note:The process will stop at 92% for some time, don't worry about this, don't touch the phone or computer!!
I have linked to the Chinese official instructions from the Nubia marketing team below
Step 5: Using Temporary Recovery to Flash Gapps
On the Computer
Download the Recovery exe from This link here (Filename: Z7max_2.13_Android _5.0_CWM recovery.exe)
Running this file will give you a terminal screen with 10 options.
Press Option "2" - I don't know what it does, but the phone will reboot - Probably the bootloader is unlocked.
Connect your phone and copy to the SD card the Gapps package: I used the pico pack from Paranoid Android thread here
After copying the file to SD card, press option "5" - This boots the phone into temporary recovery
In the recovery:
Second option is to flash zip from SD card
Select your file from the SD card
Select the second line on next screen (This is probably - No, - Yes, Flash Zip options)
Gapps gets installed
Go back to main screen of recovery and select first option, you will be presented with two options, Reboot and Reboot Recovery, choose second option to get to Lollipop with Google Play store installed.
Root
Follow the same process to get root by flashing the SuperSu zip through the temporary recovery
Link to the SuperSu: Here
Reference
Lollipop Update Thread: http://bbs.nubia.cn/thread-419364-1-1.html
How to use the Update Tool: http://bbs.nubia.cn/thread-418088-1-1.html
Need ROM Page for v2.13: http://www.needrom.com/download/z7-max-2-13-android-5-beta_eng_chi/
Another recovery article (which I did not use): http://bbs.nubia.cn/thread-417675-1-1.html
Thanks
To Google: For all the wonderful Android ecosystem and For Google Chrome's translate option that helped me understand Chinese website (A few laughs at some of the translations)
The bbs.Nubia.cn forum where all the action happens
Need ROM for some of the crucial downloads in this article
XDA Forum for teaching me a lot about ROMs, Recoveries, and Roots
This is my first elaborate tutorial, I hope you like it. Please help out with "Thanks"
Click to expand...
Click to collapse
Bro after flashing version 1.64 using custom rom my phone not detecting any cdma/gsm network on first slot . I also tried to downgrade it with version 1.29 fastboot rom from needrom but still it don't show network.
Do you have any idea how to enable my first slot working.
Also I am unable to install v2.13 because update tool show modem version mismatch and don't proceed I want to resolve my network issue please share something to help me..
sandycool123 said:
Bro after flashing version 1.64 using custom rom my phone not detecting any cdma/gsm network on first slot . I also tried to downgrade it with version 1.29 fastboot rom from needrom but still it don't show network.
Do you have any idea how to enable my first slot working.
Also I am unable to install v2.13 because update tool show modem version mismatch and don't proceed I want to resolve my network issue please share something to help me..
Click to expand...
Click to collapse
You probably lost your IMEI. Read this Chinese tutorial to restore it.
Yes I have lost my meid now my phone showing only 2 imei no meid -00000
I reached at last of your tutorial link but i am unable to create meid for my handset as i don't. No my meid also its no where on phone and box as well .so can i create my meid using the 2 imei.
I have backup its nv.qcn but not understanding this how to edit nv.qcn to write meid .
Please help me . I have 3 phones in this condition.
Thanks.
Thanks! did it and everything works good.
it seems now that the CWM is flashed on my device.
If there will be a newer version, will I be able to update it via FOTA?
or I should flash stock recovery?
entdoc said:
can this be done from 1.64 custom such as bb72 or must it be stock
Click to expand...
Click to collapse
No need to be on 1.64 stock
Actually I was able to do the upgrade from 1.64 bb72. I used the nubia tool which resizes the partitions and 2.13 stock. Then to 3.08 bb72.
It may even be possible to skip the step with 2.13 using the tool . If anyone has done it please advise
So I was poking around all over and there really isn't a good guide on how to Root the Dell 7840 after the Lollipop update. So I figured i would make one so others don't have to piece together info like i did.
NOTE: Dell just released LL 5.1 to the 7840!!! You can root it using xBIGREDDx's method here http://forum.xda-developers.com/showpost.php?p=62013578&postcount=43
You can use this guide for social-design-concept's method that xBIGREDDx mentions in his new method! PLEASE SHOOT HIM A THANKS!!!!
Before we start:
A. the info in this article is collected from several other users hard work I am just trying to make the process simple i would like to thank the developers/testors that have gotten us this far
Especially social-design-concepts and his work here:
http://forum.xda-developers.com/showthread.php?t=2975096
Please shoot him a thanks! We owe him for the mad skill!
B. If your device gets bricked for some strange reason or overheats and burns your house down again, for some strange reason. I TAKE NO RESPONSIBILITY, DO THIS AT YOUR OWN RISK.
So to start, download this:
https://www.androidfilehost.com/?fid=23991606952604606
And this:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
And this:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Install the Intel Android Drivers first, worked fine for me on Windows 10, should work fine on 8 and 7.
Plug your 7840 into your computer and do three things:
1. COPY the UPDATE-SuperSU-v2.46.zip to your devices EXTERNAL SD CARD not the internal memory!!!
2. Enable USB Debugging after enabling debug mode (tap the Build Number under About Tablet til it says your a developer)
3. Disable MTP mode by going into the Storage setting menu option clicking the options button at the top right and unchecking MTP
Extract the IntelAndroid-FBRL-05-16-2015-PTR archive to your desktop (or where ever you want to open it from)
Open the folder and run the Launcher.bat file
Everything should be installed correctly as long as the Intel Drivers installed properly.
It will bring you to this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just type T4 and hit enter
Your device should reboot to this screen:
This is where it gets tricky, if you go into the device manager on your computer you should see this:
You will need to right click it and click Update Driver Software
Then click this:
Then this:
Select the one in the list that says this:
Then select the one that says Intel Android Bootloader Interface:
It should install properly, close all the windows and if you go back to your command prompt (the thing you typed T4 into and hit enter) you will notice it is already copying stuff:
When its done you will see it setting up the temporary recovery, looks like this:
Your device will boot into Clockwork Mod Recovery using the Up and Down Volume buttons and the Power button to select, select "Install Zip"
Then "Choose Zip from External SdCard"
Select the SuperSu Zip you put on here earlier
When it gets done go back to the first menu and select "Reboot System Now"
it will ask if you want to "Fix Root"
select yes
When you get into Android you will need to install Busybox for root to work:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
And you should be rooted!! Worked for me no hiccups. I'm definitely no programming wiz but I'll try to help if something isn't working.
BTW just tested after rooting and Xposed and GravityBox both work just fine.... Thank you Dell for making this thing mostly AOSP
You may want to credit some folks in your original post, for example (at a minimum) link to the place where you got the androidfilehost link, and mention the developers who created the tool.
Chyrio said:
So I was poking around all over and there really isn't a good guide on how to Root the Dell 7840 after the Lollipop update. So I figured i would make one so others don't have to piece together info like i did.
Before we start:
A. the info in this article is collected from several other users hard work I am just trying to make the process simple i would like to thank the developers/testors that have gotten us this far
B. If your device gets bricked for some strange reason or overheats and burns your house down again, for some strange reason. I TAKE NO RESPONSIBILITY, DO THIS AT YOUR OWN RISK.
So to start, download this:
https://www.androidfilehost.com/?fid=23991606952604606
And this:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
And this:
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Install the Intel Android Drivers first, worked fine for me on Windows 10, should work fine on 8 and 7.
Plug your 7840 into your computer and do three things:
1. COPY the UPDATE-SuperSU-v2.46.zip to your devices EXTERNAL SD CARD not the internal memory!!!
2. Enable USB Debugging after enabling debug mode (tap the Build Number under About Tablet til it says your a developer)
3. Disable MTP mode by going into the Storage setting menu option clicking the options button at the top right and unchecking MTP
Extract the IntelAndroid-FBRL-05-16-2015-PTR archive to your desktop (or where ever you want to open it from)
Open the folder and run the Launcher.bat file
Everything should be installed correctly as long as the Intel Drivers installed properly.
It will bring you to this screen:
Just type T4 and hit enter
Your device should reboot to this screen:
This is where it gets tricky, if you go into the device manager on your computer you should see this:
You will need to right click it and click Update Driver Software
Then click this:
Then this:
Select the one in the list that says this:
Then select the one that says Intel Android Bootloader Interface:
It should install properly, close all the windows and if you go back to your command prompt (the thing you typed T4 into and hit enter) you will notice it is already copying stuff:
When its done you will see it setting up the temporary recovery, looks like this:
Your device will boot into Clockwork Mod Recovery using the Up and Down Volume buttons and the Power button to select, select "Install Zip"
Then "Choose Zip from External SdCard"
Select the SuperSu Zip you put on here earlier
When it gets done go back to the first menu and select "Reboot System Now"
it will ask if you want to "Fix Root"
select yes
When you get into Android you will need to install Busybox for root to work:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
And you should be rooted!! Worked for me no hiccups. I'm definitely no programming wiz but I'll try to help if something isn't working.
Click to expand...
Click to collapse
Please update your post
social-design-concepts said:
Please update your post
Click to expand...
Click to collapse
Updated, sorry man I had to run out the door right as I finished the post didn't look over the thing well enough. Please let me know if I missed someone else, I'll add them in there!
Sent from my Venue 8 7840 using Tapatalk
Chyrio said:
BTW just tested after rooting and Xposed and GravityBox both work just fine.... Thank you Dell for making this thing mostly AOSP
Click to expand...
Click to collapse
How do you install xposed?
Flash the zip for the x86 based device located here http://forum.xda-developers.com/showthread.php?t=3034811 in social-design-concepts recovery, reboot and install the apk in that forum as well.
Sent from my Venue 8 7840 using Tapatalk
I just got this tablet yesterday and updated to Lollipop (it arrived with Kitkat still loaded) and then headed over to the forum to find out it was a 5.1 update that had just came out!
Saw this thread, got really happy, and now I'm bummed to hear people are having a little trouble getting rooted on 5.1. Chyrio, I'm really new at this but I've rooted a Galaxy S4 and a Oneplus One by unlocking and flashing TWRP and installing custom roms from there. I don't know anything about the Intel architecture at all, how does this differ in terms of unlocking and rooting?
3itmn said:
I just got this tablet yesterday and updated to Lollipop (it arrived with Kitkat still loaded) and then headed over to the forum to find out it was a 5.1 update that had just came out!
Saw this thread, got really happy, and now I'm bummed to hear people are having a little trouble getting rooted on 5.1. Chyrio, I'm really new at this but I've rooted a Galaxy S4 and a Oneplus One by unlocking and flashing TWRP and installing custom roms from there. I don't know anything about the Intel architecture at all, how does this differ in terms of unlocking and rooting?
Click to expand...
Click to collapse
I'm kinda new to it as well, but as far as I can tell, there isn't to much of a difference with how the android file structure is built. The hardware is different (obviously) creating the need for different drivers and new software. I know there is some kind of emulator for ARM architecture based apps in the OS itself but Recoveries and bootloader exploits are going to require redesign from the standard ways. Which social-design-concepts is hard at work on. Hopefully he can cook up something for us soon. I'm holding off on the 5.1 update for now waiting for the devs to work their magic.
Sent from my Venue 8 7840 using Tapatalk
Any root method for Mac osx or linux?
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
---------- Post added at 11:17 PM ---------- Previous post was at 10:48 PM ----------
testastrettaR6 said:
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
Click to expand...
Click to collapse
the launcher shows:
Device Status: FASTBOOT - ONLINE
Why is this differ than the screen shots? could this be the reason why it can not get past this stage?
Same here... Device state: Locked.
Have you solved your problem?
Anyone had the same issue?
UPDATE: Bootloader unlocked. Device State: Unlocked. But know when I try to insert T4 it copies the files and on the tablet is says "Okay." The cmw does not open. Please help!
testastrettaR6 said:
NEED HELP!
when launching "launcher.bat, its giving me a message that states "the device can not work in this locked state"
not sure what is locking it from advancing. no passcode, debugging is on
Any suggestions would be greatly appreciated?
---------- Post added at 11:17 PM ---------- Previous post was at 10:48 PM ----------
the launcher shows:
Device Status: FASTBOOT - ONLINE
Why is this differ than the screen shots? could this be the reason why it can not get past this stage?
Click to expand...
Click to collapse
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.