Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
This is a step by step guide to install ClockworkMod v08, a ROM of your choosing, Flash, and the Android Market fix. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
I do NOT accept responsibility for anything good, bad, or indifferent that may come from following this guide. This includes and is not limited to completely destroying your tablet. I highly recommend leaving your tablet plugged in while doing anything like this with your device. I have no idea what will happen if the battery dies in the middle of flashing a ROM (if anything…but better safe than sorry).
ALL THE FILES NEEDED FOR THIS GUIDE EXCEPT FOR THE ROM ITSELF CAN BE FOUND AT THE BOTTOM OF THIS GUIDE.
ROM XDA Pages (Look at these to pick what ROM you want to use.)
TnT Lite
VEGAn-Tab
CyanogenMod 7 (Gingerbread)
Notion Ink Adam ROM Port
You do NOT need to root your tablet to install a ROM on this device using this guide. All the after-market ROMs come pre-rooted so you don't need to root after installing either.
Part One – Install ClockworkMod v08
ClockworkMod is what will ultimately be used for all your flashing of ROMs, backing up, clearing cache, etc.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.) There are two versions available; one for installing ClockworkMod from the internal memory, one for installing it from external memory (microSD/microSDHC card).
Step 2.
Unzip the file you chose (cwmod_internal.zip OR cwmod_microsd.zip) to the root folder on the storage option of your choice.
So, for example, if the storage option you chose has the drive letter “F:” assigned to it when hooked up to your computer, you would want it to look something like this…
A folder located at “F:\recovery”
A file located at “F:\update.zip”
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch ClockworkMod install. This will not take long. Your tablet will reboot when installation is complete.
Step 6.
Enter ClockworkMod:
To get into ClockworkMod you need to shut down your device, then press the Power and Volume+ button (the same way you did to install ClockworkMod).
Navigating ClockworkMod: Vol+ and Vol- are to scroll up and down, the home button selects an option, and the back button backs up.
Step 7.
Re-Partition your Tablet:
In order to make sure the Android Market works correctly after installing any ROM, we must re-partition the device.
Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared.
Part Two – Install a ROM.
A ROM (explained in very basic terms) is like Windows on your computer (assuming you’re not running Linux or Mac OS). Each ROM contains a customized version of Android that comes packaged with software, themes, and everything else you actually see when the device powers up. You install any additional apps you would like to use after installing the ROM. Beware, ROMs are device specific. You cannot reliably install ROMs designed for another device.
Step 1.
Now that your device is essentially empty, we need to be able to put files on it. ClockworkMod can do this for us. Connect your tablet’s USB cable from your tablet to your computer. Go to the ClockworkMod main menu, then navigate down to “mounts and storage”, and then select “mount USB storage”. The tablet’s internal storage will then be accessible from your computer. You will want to open it, and create a folder called “ROMs”.
Step 2.
Download whatever ROM you want to use. The links to the ROMs are located above. Click on the link to see what that ROM looks like. The most popular ROMs for this device are TnT Lite and VEGAn Tab.
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is).
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
Step 4.
Turn off your device.
Step 5.
Boot into ClockworkMod. (Press the power button and the volume+ button at the same time until the Viewsonic splash screen pops up, release, then you should see “Detect a recovery key pressed”. After that it will think for a few seconds and then it should boot into ClockworkMod)
Step 6.
Stand up and do a dance. Sitting too long isn't good for you.
Step 7.
Back up to the main menu, then navigate down to “mounts and storage”. When that is highlighted press the home button to select it.
Step 8.
We want to mount “/system” and “/data”.
The goal is to see the following:
“unmount/system”
and,
“unmount/data”
If either one says “mount” instead of “unmount” you need to navigate to that line and press the home button to mount it.
Step 9.
This is the step that we actually flash the ROM in.
From the ClockworkMod main menu, navigate down to “install zip from sdcard” and press the home button to select that option at the menu.
Then, navigate to “choose zip from sdcard” and press the home button to select that option.
Navigate to the line that reads “ROMs” and press the home button to select that option.
Navigate to the line that reads whatever .zip file you wish to install and press the home button to select that option.
Navigate to the line that reads “Yes – Install yourzipfile.zip” and press the home button to select that option.
You will now see it do its thing. When complete you will see something along the lines of “install zip from sdcard complete” at the bottom of the screen.
Press the back arrow over and over again until you get to the Clockwork’s main menu.
Step 10.
Here is where we prepare the system to run the new ROM.
Navigate down to “mounts and storage”, select it, and mount “/system” and “/data” again as in steps 7 and 8.
Back up to Clockwork’s main menu.
Navigate to “wipe data/factory reset”, select it. Navigate down to “Yes – delete all user data”, and select it to wipe out user data and all the cache. (You need to do this for the new ROM to function correctly)
Now, navigate to the top option “reboot system now” and select it. Your tablet will now reboot. It may take up to 15 minutes to start up the first time as it rebuilds the user data and cache for this ROM.
If your tablet boots to UID errors, or has force closes (known to fix a few of them)…
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, and then go to “Fix Permissions”. Afterwards, back out to the main menu, then select “reboot system now”. If that is unsuccessful then boot back into Clockwork and redo steps 7-10.
Part Three – Install Flash and fix Android Market
This is needed to view websites with Flash based content, and to download apps from the market. (Fairly obvious, I know, but just in case somebody doesn't know.) Log in/set up your Google Account before trying the market fix (steps vary on the ROM you are using…in most cases you can access the web accounts by opening the Contacts app, pressing the menu button (the one above the back button), and selecting accounts).
Step 1.
Download “Adobe Flash Player 10.1.120.1.apk” which you will find attached at the bottom of this post and save it on your tablet (I recommend creating a separate folder to save .apk files in).
Step 2.
On your tablet open up whatever file explorer comes pre-installed with the ROM you’ve selected. In there, open up where you saved your .apk, then select Adobe Flash Player, and follow the on screen instructions to finish installing that.
Step 3.
Open the Market app. Once it loads close it (press the home button).
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy. You should now have Flash and the Android Market.
This is the Titanium Backup method. Thanks to roebeet, xguntherc, and KorbenD.
http://forum.xda-developers.com/showthread.php?t=845175
Part Four – Show your appreciation! (First, be sure to play some Angry Birds)
I encourage everybody to take the time to send a kind message, or a small donation, to everybody that helped make this device what it is. This is not me saying "HEY HEY DONATE TO ME!!!!"...like some developers for other devices do. I just feel like the great ROM developers for this device don't get the credit they deserve, so please at least send them a quick thank you note. Keep in mind that ROMs, utilities, and yes (even guides), take a considerable amount of time to plan, compile, test, fix, and distribute.
With the following link you can donate as much or as little as you would like to me (even a dollar helps). Thanks and enjoy your tablet!
Donate Here
Thank You. This is exactly what we need. One thread with all the info consolidated into one will help many new users understand what to do. People otherwise may have come here and just been blown away by the different threads, I sure was when I first decided to Root my Eris.
scsione889 said:
This is a step by step guide to install ClockworkMod v08, TnT Lite 2.2, Flash, and get the Android Market working. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
...
Part Three – Install Flash and fix Android Market
Step 1.
Create a folder on your SD card called APKs. Download “Adobe Flash Player 10.1.120.1.apk” and "TitaniumBackup_latest.apk" which you will find attached at the bottom of this post and save them in that “APKs” folder on your SD card.
Step 2.
On your tablet open up “ES File Explorer”. In there, open up the “APKs” folder, then select Adobe Flash Player, and follow the on screen instructions to finish installing that. After that, select Titanium Backup in that same folder, and install the same way.
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps.
Step 4.
Open up Titanium Backup, go to Backup/Restore and look for Google Services Framework, select it, then select “Wipe Data”
Step 5.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 3 and 4 until you do.
Step 6.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 7.
Open the market again and enjoy. You now have Flash and the Android Market. (Keep in mind, this is not the FULL market, it just makes around 99% of it available. It is unknown which apps are not available. There is a full market fix, but it is MUCH more complicated).
Click to expand...
Click to collapse
Extremely Well Done!
Would be Nice to get this Stickied to keep easy for newbies to find...
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Also I only needed the first reboot in Step 6, wait a few minutes then tried Market and all was fine! No multiple reboots needed for me at least...
Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.
LTL11 said:
Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.
Click to expand...
Click to collapse
This technically isn't needed for TnT Lite...but if people were to use this guide as guidelines for installing other ROMs (as I hope people would do...you know...following directions is good, but learning what your doing is GREAT), step 8 is something that is always good to get in the habit of doing before a flash.
With many other ROMs, on this device and others, not mounting /data and /system before flashing causes headaches.
jtbnet said:
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Click to expand...
Click to collapse
I did it using 'Clear Data' as well...but this was my way of getting newbies to use TB (and to get more familiarized with side-loading apps). It's a great utility that I feel Android users should be familiar with.
Great guide, added clarifications
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.
Tommunicator said:
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.
Click to expand...
Click to collapse
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.
omnifox said:
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.
Click to expand...
Click to collapse
Sorry about this guys. Editing it now.
FIXED.
After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin
kevin stone said:
After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin
Click to expand...
Click to collapse
Does it display an error? Please be a little bit more specific. Did you try restarting the tablet (not just putting it into standby and bringing it back up)? Also, were you sure to force close the apps before clearing the data?
I did all these steps last night and everything seemed to work as expected. When I woke up this am and actually started to play with the Market, I realized that even though the Market looked good last night, all the important apps are gone this morning. I followed the instructions on the forms and on youtube videos and got the exact same results that were to be expected. I got all the errors and rebooted when asked and thought I was ok. When I opened Market after the Fix Process, all the same apps I would see on my HTC Evo are there. HOWEVER !! once I try to search or change the category to Apps or Games, or go to the sub catagorys 90% of the apps disappear. My app / game selection is now only 1 page long
When Market first opens up, I see Angry Birds and other apps I want, in the category description, but when I try to navigate to them, the screen simply says "loading" and never come up. It will stay that way for over an hour. The only thing I can do is change another catagory. When I do that, the loading text goes away and apps will show up, but alot are missing. Even the category description like for "Action Games" no longer lists Angry Birds in it. And if I try to search for an app I know is in the market like Advanced Task Killer... it says it can't be found.
I repeat the Market Fix process over and over and over again with the exact same results. Any Idea? Everything else seems to be working fine. Flash and Titanium Back up work perfect. Just can't get Market to show all the content.
I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\
You guys rock!
Picked up my GTab today @ Staples. 45 minutes later it's ready to go with TnT 2.2, full Market access and Flash using this guide! So far...so good!
Thanks for taking the time to write up this guide. Saved me from the slower-than-molasses-out-of-the-box-os-setup they shipped the tablet with.
Can't access Gtablet VIA USB cable from PC
I installed CWM 8, TNT lite 2.2 and performed market fix. Now my Gtab is working great. Prior to this thread I was stuck in a loop. My gtab is running great thanks a lot for posting this tutorial.
My only issue now is I can't access the internal SD from PC. Nothing shows up on my PC when I connect the USB cable to my Gtab. I have tried unmounting and mounting SD several times in CWM.
Prior to this update I was able to access and sideload APK's on my gtab running stock software with Viewsonic update.
any help would be greatly appreciated.
Wyngnut
Well after booting up a couple of times it just started to work (my Gtab showed showed the SD card option). I have downloaded several programs and they all install automatically and every one of then worked. No sideloading no additional steps for install this is amazing. I was coveting the windows 7 tabs on the horizon but the free programs available through the market are amazing and when they are Combined with the Gtab hardware its amazing.
Thanks again for posting this there is no way I would have tried to put this software on my system if I had not seen this guide.
Wyngnut
sano614 said:
I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\
Click to expand...
Click to collapse
The tablet doesn't seem to like giving the PC access to the microSD card. As far as I know this is a feature that is not available in any ROM. Also, it is my understanding that for this sort of thing to be possible we need to have the device's source code so we can make the hardware/software mesh better.
That is...unless I'm missing something very obvious...which is totally possible.
Thank you so much for taking the time to write this, worked perfectly for me
It's AMAZING!
Thanks to everyone on the site - from Roebeet and pals who pulled it together to scsione889 and others who did the walkthrough. For an absolute newbie (didn't know what "root" meant) to be able in one day to turn an absolute clunker into what I have now is unbelievable.
If you're new like me, and wondering whether you can pull it off, you can. Just make this the one time in your life when you read and follow the instructions exactly, without your usual improvisation!
The Problem
The HTC Droid Incredible shows a "Low on space: Phone storage space is getting low" warning despite having gobs of space free because the "Application data storage" folder (also known as /data/data) that is shared by all apps on the phone is only 150mb in size. As soon as only 10% of this folder is available, the warning appears. If it gets too much lower, apps stop responding and the phone crashes.
The Story
After many months of clearing app data, uninstalling apps, resetting my phone, and generally walking on eggshells trying to keep my data storage under the limit, I was getting ready to upgrade my device. I would search every few weeks to see if anyone had solved the problem, but all I found were more people stuck in my boat, and I was ready to give up. But then I stumbled across a series of threads on xda-developers.com that gave me new hope. In the course of one night, I learned from scratch how to root my phone, and I applied a fix that increased the "Application data storage" folder to a whopping 750mb. I am now able to download as many apps as I'd like and not have to worry about clearing out app data ever again.
However, it took a bit of scouring the forums and reading various guides to figure out how to do all this. Some of the items are quite technical in nature, and some of the guides skip steps that more experienced users would know how to do already. So I joined the forum to write this guide for the "regular" users out there like myself. My goal is to explain in plain English how to fix this nagging issue once and for all and to consolidate all the relevant info and files into one place. If you find this useful, please share this with others so we can all fully enjoy our phones!
The Credits
I did not invent any of the steps, tools, or methods I am about to describe. Hats off to the following people for supplying all the info and files I needed to fix the problem and write this how-to thread. Please let me know if I've missed anyone that should be mentioned and I will add them.
vbhines for the "New to Modding/Rooting" guide
The unrevoked team for their excellent one-click rooting software and drivers
dreamersipaq for the guide to rooting an Incredible
scotty1223 for the guide to rooting a 2.3.4 Incredible
jermaine151 for the "no data limit" mod that actually fixes the problem
cmlusco and tiny4579 for all their help answering questions and troubleshooting in this thread
The Ingredients
Here's what you'll need to perform this fix:
An HTC Incredible (obviously) with an SD card
A micro USB cable (you can use the one you charge your phone with)
A computer with a USB port and internet access (PC, Mac, or Linux)
An hour of free time
The Fix
Step 1: Read the "New to Modding/Rooting" guide so you know what you're getting into and can understand the terminology: http://forum.xda-developers.com/showthread.php?t=744807
Step 2: Back up your contacts, pictures, etc. This guide is safe for your phone and will not erase any of your data if you follow it correctly, but it never hurts to back things up just in case.
Step 3a: Make sure your phone is decently charged. (at least 50%)
Step 3b: Make sure your phone isn't currently showing the "low on space" error. Delete some apps or data until the error goes away. You don't want to go through all this effort only to have your phone crash halfway through!
Step 4: Uninstall HTC sync software from your computer. Also make sure you are not running any software that communicates to your phone using USB, such as PDANet or DoubleTwist. If you haven't had to plug your phone into your computer to do anything prior to now, you're probably OK.
Step 5: On your phone, go to Menu -> Settings -> Applications -> Development and put a check in the "USB debugging" box.
Step 6: Plug your phone into your computer, select "Charge Only", select "remember my selection", click "Done", and then unplug your phone.
Step 7: If you are on a Windows PC, follow this user-friendly guide to install the USB drivers you'll need: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
When I did this step, I actually found my Android entry from the first screenshot in the guide under "Android Phone" and it did not say "Android 1.0". Don't worry, you can still use this entry to continue with the next step in the guide to "Update Driver Software".
Mac and Linux users can skip this step.
Step 8: Root your phone. This step is a bit more involved, so be sure to read the directions carefully. On your phone, go to Menu -> Settings -> About phone -> Software information and look at what it says under "Android version" at the top.
If it says 2.3.4, do this:
Download Clockwork 5.0.2.0: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip (link updated 6/22/12)
Extract the recovery-clockwork-5.0.2.0-inc.img from the zip file and put it somewhere you'll remember.
Download Unrevoked 3.22 (this is intentionally NOT the latest version): http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe (link updated 6/22/12)
Run Unrevoked_3.22.exe
Inside the program, go to File -> Custom Recovery and select the .img file from above. At the bottom of the program window, it should now say "Recovery: Custom" and "Waiting for device"
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
Once it's done, unplug your phone and ensure that a "Superuser Permissions" application is inside your app drawer. Don't run it. Instead, go to Menu -> Settings -> Applications -> Manage applications -> All, scroll down to "Superuser Permissions", click it, then click "Clear data". Return back Home.
If it says anything other than 2.3.4, do this:
Download Unrevoked 3.32: http://www.unrevoked.com/recovery/
Run reflash_package.exe. It may start up right away, or it may ask you to extract the files. Put them somewhere you can find, and once the extraction is done, find and run reflash.exe.
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
After the above steps, everyone should do this:
Launch the Android Market and search for "ROM Manager". The first result should be "ROM Manager" by ClockworkMod and it should have a picture of a top hat above a gear as its icon. Click it, then click "Download", then "Accept & download". If it is already installed, you can just return Home.
Once ROM Manager has finished installing, launch it and select "Flash ClockworkMod Recovery" (the first option). Confirm your phone model (HTC Incredible). A window will pop up asking for root permissions - click to allow it.
Optional: After the download completes, scroll down and click "Backup Current ROM". You may need a lot of space free on your SD card to perform this backup depending on what you have on your phone. Once you create this backup, you can use ROM Manager to fully restore your phone (including all apps, data, and settings) in case anything goes wrong. This can take a significant amount of time, so again, be patient!
If all went well, your phone should be exactly the same as it was before, except you now have a couple new apps, and more importantly, root access!
Step 9: On your phone, go to Menu -> Settings -> Applications -> Development and uncheck the "USB debugging" box.
Step 10: Apply the Fix. This is the step you've been waiting for!
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1623038, click the link for the EXT4All files in the first post, download "Convert2Ext4_no_data_limit_normal_dalvik.zip", and put it somewhere you'll remember. You can also go directly to this URL to download the file: http://dinc.does-it.net/EXT4_Mods/ (links updated 6/22/12)
Plug your phone into your computer, bring down the notification bar, select the "USB connection type" item, select "Disk drive", and click Done.
On your computer, find your phone's SD card. If you're unsure which drive is your SD card, look at how big each drive is. The drive that has a size of 6.59GB is the phone's internal memory, so the other drive is the SD card. The SD card that comes with the Incredible is 1.83GB in size, but yours may be different if you bought your own SD card.
Move "Convert2Ext4_no_data_limit_normal_dalvik.zip" from your computer to the SD card. Do not put it inside any folders.
After the file has finished moving, bring down the notifications bar, select the "USB connection type" item, select "Charge only", then click done.
Unplug your phone from your computer.
Launch ROM Manager from your app drawer and click "Reboot into Recovery" (the second option). Click "OK" to proceed.
After the phone reboots, you will now see a black screen with some blue options on it. Use the volume buttons on the left to scroll down to "install zip from sdcard" and click the optical trackpad button at the bottom of the phone to select it.
Click "choose zip from sdcard" (the first option)
Scroll down to the very bottom and select "Convert2Ext4_no_data_limit_normal_dalvik.zip"
Scroll down to "Yes - Install Convert2Ext4_no_data_limit_normal_dalvik.zip" and click it. This step will take some time to complete, and the progress bar may not move at all. Be patient!
Once it is done, click the power button at the top of your phone until you're back at the main menu, then select "Reboot system" (the first option). If you hit power too many times and end up with a blank screen, just hit power one more time and you'll see the menu.
When the phone is done rebooting after this last step, verify that the fix worked by going to Menu -> Settings -> SD & phone storage and look at the "Application data storage" section. It should now say that the "Total space" is 748mb!
At this point you can run happily through an open field, shout from the highest mountaintop, or just shed a tear of joy, because you can now install tons of apps and let them accumulate all the data they want. Enjoy!
P.S. Please let me know if any of these steps are incorrect or unclear so I can fix them. Thanks!
Troubleshooting
Here are a couple of issues people have come across while doing the steps in this guide, along with the solutions. Thanks to cmlusco for these helpful answers!
The guide says my phone should have rebooted back to the main screen, but I'm on a black screen with a bunch of blue options!
If you're on this step and the guide doesn't say you need to be here yet, just use the volume buttons to scroll to the "Reboot System Now" option and click the optical trackpad. Then you can continue on with the guide!
I'm stuck on a black screen with white bars on the side!
If your phone is "s-off", reflash the recovery-clockwork-5.0.2.0-inc.img file from Step #8 using hboot. To get to hboot, turn your phone off, hold the "volume down" button, and turn it back on. Keep holding the "volume down" button until you get to the menu where you can flash the .img file.
If your phone is not "s-off" or you have no idea what "s-off" means, run Unrevoked again with the same .img file from Step #8.
In either case, you should be able to continue using the guide from where you left off!
My phone keeps rebooting over and over and I can't do anything!
Pull out the battery, wait for 15 seconds, and put it back in and turn the phone back on. If it still keeps rebooting, pull out/re-insert the battery again, go into hboot (see above answer) and try the following steps. You can stop as soon as one of them works!
1. Restore a backup that you made in a previous step (if you have one).
2. Reflash the .img file from Step #8.
3. Flash the .img file here: http://dinc.does-it.net/wildstang83_inc_4.08.605.2_11232011.zip (note: this one will take you back to stock, so you'll have to start the guide over).
I'm still stuck!
If all else fails, please post your issue in this thread so someone can help you out. You can also try restoring your backup (you made a backup, right??) and starting over from the top. Good luck!
Potential Alternate Solution
Soniclude that was a great very detailed write up. Here is another option that I found that seems to also solve the dreaded low disk space...
Since you clearly outlined the steps for rooting your device, I wont go into that. But, why stop at fixing one of the most annoying stock problems. Rooting is half the battle to flashing a new rom - which is precisely what I did to stop the LDS issue.
I used to use CM7 and then flashed over to MIUI but recently I flashed the best rom I have used to date - ICS-Dinc AOKP (]http://forum.xda-developers.com/showthread.php?t=1475936) which is a full fledged ICS port for your OG Dinc.
Since then I have not received any LDS errors (although I have not been using this ROM that long) but I would assume that it would be similar to my lengthy experience with CM7, in which I never got the LDS warning.
Here is what my device displays as available space for applications
View attachment 895332
As you can see I have used 144MB with 604MB free for a total of 748MB, identified as internal storage.
Also, just so you can see that this ROM is not an ICS overlay and is truly a port, here is the device info
View attachment 895331
72ls1's (the dev for ICS-Dinc AOKP) has some really good directions and make the process very easy.
For those that are interested and need a few more additional details, here are a few things that helped me:
1. Make sure you have backup your device data, this includes your apps, contacts (you should be just setting all contacts to sync with your gmail account to begin with), messages and email settings. Use an app like Titanium Backup for apps; Backup and Restore app for messages; Call Log Restore for calling
2. Download the zip files outline in the ROM posting of your chocie to your sdcard; They should be placed at the top level of your sdcard, meaning not in another folder. The zip files for ICS-Dinc AOK include the ICS-Dinc zip, Gapps (use this one gapps-ics-20120207-signed.zip - http://goo-inside.me/gapps/gapps-ics-20120207-signed.zip), and Tiamat Kernel
3. In Recovery make a backup of your device (in case you need to flash back due to an error)
4. Within Recovery prior to flashing the rom make sure to unmount data, sdcard and cache
5. Then clear cache and dalivik-cache (this one is under the advanced options)
6. Do a factory reset
7. Install from zip in the following order: ICS-Dinc AOK V.02, Gapps, Tiamat
8. Reset your device
Now go enjoy the goodness of a fresh ice cream sandwich!
Hope this helps anyone else out there in either the low disk space issue or that is having questions about flashing a rom.
Where is Unrevoked 3.22?
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan
Captainjerky said:
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan
Click to expand...
Click to collapse
You can actually acomplish that without rooting.
Open dial pad and type ##778# and hit call.
Select edit mode and enter six zeros (000000) as the password.
Select security and look for S.IP DUN username, it should look something like this [email protected]. Change it to be [email protected], just remove the "dun.".
Back out to the main menu and select M.IP Default Profile. Look for DUN NAI and change it to be [email protected], remove the "dun."
Hit the menu button and select commit modifications. Your phone will reboot.
Now just use the stock 3g mobile hotspot app. When you first open it it will say you have to have a subscription and pay, just procede you will not be charged, and verizion is none the wiser. I have been doing this my self for over a year now.
Compass sensor broken
Somebody has the same issue? after flashing the zip i cannot use correctly the compass sensor, for example in SkyMaps app.
This is by far the best tutorial out there to gain root and achieve s-OFF I've come across. Thank you SIR for your time and tutorial. Just EXCELLENT!!
for me the issue was my data/data folder (hint dont sync 1500 facebook friends and never do it with high res pics and with two differant apps haha) =] jsut removed all the contacts i didnt need and turned off the sync from normal facebook app and working perfect now
stuck in loop
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here
scals37 said:
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here
Click to expand...
Click to collapse
If you made or have a previous roms backup. Just wipe everything in mounts and storage menu except sdcard and emmc, then restore your backup. If you dont have a backup flash a fresh rom.
You kind sir are a gentleman and a scholar. That "low space" bug has been annoying me since July 2009. I greatly appreciate you breaking down the l337 sp33k to plain English.
THANK YOU THANK YOU THANK YOU THANK YOU
Captainjerky said:
Does anybody have a working link to 3.22?
Click to expand...
Click to collapse
downloads.unrevoked.com/recovery/3.22/reflash_package.exe
---------- Post added at 01:19 PM ---------- Previous post was at 01:11 PM ----------
Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?
[/COLOR]Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?[/QUOTE]
I agree that this was an excellent how to. Thanks for the effort.
I used the no_data_limit_dalvik_moved mod and for some reason, my phone became really laggy. I'm on Pons CM7. 2. Now I'm a little hesitant to use any of the ext4 mods b/c I don't understand them too well. I'm not clear on why there is a partition in the first place. Why htc devs made it so small... Homework to do.
Sent from my ADR6300 using Tapatalk
Thanks cmlusco I used your method to unlock the 3G Hotspot on my phone and it worked like a charm.
Issue in Step 10
Thank you very much for the easy to follow directions soniclude. I went through all the steps and when I got to step 10, I ran into an issue. After clicking on "Reboot into Recovery" the phone restarts and goes to the white htc screen. After that the screen just goes black with thin white lines down the sides and stays like that. So I never see the blue options. Has anyone come across this? If so, what do I do from there?
I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.
joeyz400 said:
I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.
Click to expand...
Click to collapse
If your on 2.3.4 you need to follow this guide http://forum.xda-developers.com/showthread.php?t=1306400 to root and get s-off.
I understand I could downgrade to 2.2 to get s off but only after I gain root. It seems I can't get rooted because I am running 2.3?
---------- Post added at 06:58 PM ---------- Previous post was at 06:53 PM ----------
It looks like the only step diffrent from the link you posted and this one is to run unrevoked as admin
I think I know what is wrong. The link to Unrevoked 3.22 is not working so I googled it and 3.22 came up but it was actually 3.32 that was downloaded and I can't find 3.22 anywhere. Does anyone have a copy of 3.22?
I found the correct 3.22 and now my Incredible is Incredible!!!! Rooted and it feels so good
Thanks for such a great thread!!!!
SWEEEEEET This worked awesome.
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.
JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!
jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...
pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.
[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1
[GUIDE/TUTORIAL/HOWTO] HTC One M7 any version (m7, m7ul, m7spr, m7vzw) stock to Android 11 R / LineageOS 18.1
This detailed step-by-step guide helps you transform your HTC One M7 (any version) to a powerful one with Android 11.
Make sure you have the One M7 model, in Android, go to Settings > About phone and check the model.
CHANGELOG
v8. Upgrade to Android 11, improve readability, update pack
v7. Updated pack with MagiskManager 8.0.7 and Magisk 21.4
v6. Infos in case of Simlock
v5. Moved to Android 10 thanks to @tarkzim, updated pack with Magisk 20.4
v4. Moving to Android 9. I was wrong in v3 ;- Thx @tarkzim), good for all M7 versions
v3. Reverted back to Android 7.1. No stable ROM for Android 8 or 9 (and will never be)
v2. Tutorial updated for Android 8.1 Oreo, updated pack with TWRP 3.3.1-0
v1. Initial release
1) DOWNLOAD
- djibe HTC One M7 pack (44.3 Mo) v2 : http://bit.ly/djibe-onem7-v1
(includes HTC drivers, recovery TWRP 3.6.1_9-0 for all m7 by Xeno1, Magisk Root 23 adb & fastboot.exe).
Unzip the djibe folder from the zip on root folder of C: drive.
- ROM Unofficial Lineage OS 18.1 for M7: https://forum.xda-developers.com/t/rom-11-0-unofficial-m7-all-lineageos-18-1-stable.4454219/
Download latest build for M7 here: https://androidfilehost.com/?w=files&flid=334598&sort_by=date&sort_dir=DESC
+ BitGApps ARM 11 v1.4+: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Charge phone to 100 %
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe -> click on Run as administrator and continue the setup.
Then install HTC_BMP_USB_Driver_x64.msi (or *_x86 if you have a 32bits Windows edition).
### Install doesn't work ? Try these drivers for Win10 : https://htcusbdriver.com/download/htc-usb-driver-v4-02-0-001
Now go to my folder flash, and right click the adb 15seconds installer > Run as administrator.
During install, every time the command asks you a confirmation, enter Y and confirm with Enter.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
Collect all personal photos, videos, etc ... and copy these on PC.
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is not accessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock in 1 zipfile flash, follow this tutorial: https://tcg96.github.io/m7gurureset
3) UNLOCK BOOTLOADER
In Android, go to Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to the About menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Toggle on the USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
### Then navigate to my flash folder (if it is on desktop) with this command :
Code:
cd /d C:\djibe\flash
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT35****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Authorize ADB commands on phone.
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type :
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
Type :
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website : https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, chose HTC One (M7), click Begin unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you : Token Submitted Successfully.
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type :
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return :
Code:
unlock token check successfully
Back to phone, press Volume+ to select "Yes, unlock bootloader", then Power button to confirm flash.
Now wait while phone is going to Factory reset.
Don't let Android restart by holding both Power + Volume- to enter bootloader immediately.
FASTBOOT menu is overlined in red.
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter :
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.1_9-0-m7univ.img
Command returns :
Code:
finished. total time: x.xxxxs
##€ If it fails, tries with a Windows Powershell shell.
Now on phone, press Volume- to select Bootloader, confirm with Power button.
You are back to the booloader screen (UNLOCKED is written on top line), press Volume- to navigate to RECOVERY, and confirm with Power button.
Phone reboots in TWRP recovery.
5) WIPE PARTITIONS
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Go to Wipe > Advanced wipe.
Select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
6) FLASH ROM, GAPPS AND ROOT (OPTIONNAL)
We first have to get our zips on the phone.
Still on TWRP Home screen, tap on Mount > deselect all partitions except Data, then connect phone to PC.
In Windows Explorer, you can see MTP Device, copy the zips of ROM, GApps, Magisk + Magisk Manager right in the Internal Storage folder.
Tap on Disable MTP once copy is finished.
Then back to Home screen, tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> Magisk*.zip,
then Add more Zips -> bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
When completed successfully, tap on Reboot.
Tap on Do not install when TWRP asks for the app install.
Wait during long first boot.
Setup Android.
7) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, LineageOS team, tarkzim, zsoerenm, alray, ., Flyhalf205, icxj1, R1ghtC, gimmeitorilltell, All M7/MSM8960 contributors.
Just my 2 cents
Just my 2 cents if it can help
djibe89 said:
- a microSD card (FAT32 format). Copy the zips of ROM, GApps, addonsu and deviceid*.apk (both in my pack) on the root folder of microSD, then insert it in phone.
Click to expand...
Click to collapse
The M7 is not equipped with a mircoSD card slot, only a virtual /sdcard (symlink to /data/media/0) ... So they'll either have to adb sideload or adb push the files to internal memory which is pointless at this stage since it will be wiped during bootloader unlock. Or drag n drop the files using mtp from twrp once it's installed on the phone.
3 ) UNLOCK BOOTLOADER
[...]
Now wait while phone is going to Factory reset.
Setup Android again on next boot.
4 ) FLASH RECOVERY
Now re-enable USB debugging in Android.
Using the same Windows command prompt, type
Code:
adb reboot bootloader
again.
Click to expand...
Click to collapse
You could save a lot of time just force rebooting to bootloader (power + vol down) right after BL unlock/factory reset are completed so you don't have to setup the system you're going to wipe 2 steps later. USB debug anyway isn't required to fastboot flash recovery so it's not like booting back in system is mandatory before flashing recovery.
:good:
@alray : Thank you so much for help.
I'm lazy with baby waking up every night and did some awful copy-paste.
I correct all these right now.
Thanks.
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
Because you are a senior member you know where to download everything.
But everyone is not like you.
So I tried to compile a ready-to-go pack for the newcomers, like I did for many devices by know.
This allows noobs to profit from custom ROMs and don't keep it esoteric.
Like you say, many downloads are just hacks, so I tried to bundle lowest size safe files.
saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
For the official LOS ROM, tell LOS to store official builds. As they don't do it anymore, we must rely on personnal builds.
A lot of guides out there ? Made extensive search for cracking this phone, never found a step by step one.
Five year old device ? Still so good once unleashed. Custom ROMs are for these devices isn't it ?
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
.:B:. said:
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
Click to expand...
Click to collapse
Thanks for your explanations.
Any trouble following this tutorial guys ? How to enhence it ?
802D device supported?
M.Z.F said:
802D device supported?
Click to expand...
Click to collapse
Hi, no idea, does your model has another model name/code ?
djibe89 said:
Hi, no idea, does your model has another model name/code ?
Click to expand...
Click to collapse
Model name & code like?
PRI Version= 4.22_001
PRL Version = 10012
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Rafay106 said:
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Click to expand...
Click to collapse
All the custom roms mentioned above are NOT for your phone variant.There were almost no development for the 802 branch at the peak of it's popularity and I didn't see anything new for this variant in the past 2 years or so. I wouldn't expect a 7.1 roms for this variant...
Maybe you'll have better luck searching on Asian forums
skovatov said:
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
Click to expand...
Click to collapse
Here you have answer:
https://forum.xda-developers.com/showthread.php?t=2522762
---------- Post added at 05:30 PM ---------- Previous post was at 05:20 PM ----------
Hi.
After installing Android 7.1 Google Pay stop working on my phone. I have torn on NFC communication but terminal don't read my card from app. I don't turn on access to root. Any aidia how to solve this issue?
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Bazooka said:
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Click to expand...
Click to collapse
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
alray said:
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
Click to expand...
Click to collapse
Thanks for that. I tried to go through it nice and slow making sure I understood each step. I got to where I needed to open a command window on the "flash" folder to which I must have powershell(?) installed as it gave me that option. After inputting 'adb devices' it listed a device but stated it was offline. This is where I am stuck as the steps after this do not work.
drivers win10
Hi, I have a basic ask. Do you know where to get Win 10 drivers? I can't run the installer HTCDriver_4.2.0.001 on my Windows 10 (version 1803).
It gives me the error: The driver installer is not supported for your operating system. Thanks for your help.