Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
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.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.
Reserved for possible FAQ in the future
@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?
Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.
Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.
@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV
I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!
[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.
aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?
ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one
@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again
aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.
Deleted
Related
Disclaimer: I cannot guarantee that this process will work for you as it did for me. If something goes wrong I will do everything I can to help you, but you are responsible. This is a guide for the I9000 international version.
If you think your phone is "bricked" or something goes wrong then use this guide to get your phone sorted.
If you would prefer to use Heimdall to flash or you are not using windows then use this guide.
All "" in this guide are for emphasis or highlighting purposes. All commands should be typed excluding these.
Before you ask, if you have any questions about what PIT file you should use then see this and realise that it really makes little to no discernible difference.
What you need (All links are direct download):
Firmware you wish to flash. Generally find them here.
Odin3 v1.85 (Contained in the firmware)
USB Cable
Backups
Ability to get into download mode
>65% Battery
Section 1: Backups
1.1 Backups:
Download the above file now while you backup using:
SMS using "GO sms", "SMS backup and Restore" or "SMS Backup +"(syncs with Gmail).
Apps using "Listables" or other preferred app. Due to a glitch that occurs with most app backups, market links are not maintained on restore, meaning some updates won't work properly. Using listables you can create an XML list on the SD card and later reopen this list. Then simply long press on each item to download again from market, insuring that updates function correctly. Alternatively you can make a html list, email it to your computer and just reinstall everything using the web market, quicker and simpler. If this is not a huge issue for you then I recommend just using "App Backup and Restore".
Contacts using "GO contacts" or other preferred app.
APN using "APN Backup & Restore" (internal SD save, handles duplicates)
Call logs using "Call Logs Backup & Restore" (internal SD save)
[*}Bookmarks using "Backup Bookmarks"
These will all be saved onto the internal SD card which WON'T be wiped during the update process. If you wish to backup your SD card as well, then be my guest.
Section 2: Download Mode
2.1 Download Mode:
In order to install the new firmware, it is imperative that you can get your phone into download mode. To do this, hold the HOME button + the VOLUME DOWN button + the POWER button until this screen comes up:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this button combination does not work then you probably need to install Android Debug Bridge (ADB) (See Appendix: Download Mode via ADB). If it does, go straight to section 3.
Section 3: Updating
3.1 Prepare Odin
At this point the phone should be in download mode, but have it unplugged from the computer. Extract the firmware and run Odin3, it should look like this:
In odin, there is a lot you don't really need to worry about. Just make sure that Re-Partition, Auto Reboot and F. Reset Time ARE ticked.
Click the button that says PIT, navigate to the folder you unzipped the firmware into, select the PIT file. Press the PDA button and select the CODE file. Press the PHONE button and select the MODEM file. Press the CSC button and select the CSC file.
Now (in download mode) plug in your phone. It may take some time for the phone to register with the computer and it may fail. If that's the case then see Appendix: USB Drivers.
Odin should now look like this with the yellow COM representing your phone connected.
3.2 Installing
Be extremely careful while Odin is flashing your device. Interrupting it is a surefire way to produce a $500 paperweight. I recommend holding your breathe and pretending you are a statue til it's done. Once your phone is connected properly and odin is prepared, hit install. This should take around 2-10 minutes depending on your computer etc. Once done, the phone should reboot and voila you now have gingerbread.
Section 4: Recovery
4.1 Start up
Once the phone starts up it should run you through the setup wizard. Go through this process and add gmail account etc. Then proceed to step 4.2.
4.2 Wipe Cache
Wiping the caches will remove any straggling data from previous installs. But don't stress this will only wipe data off the ROM partition area and not the SD card. While the flash has done most of this, sometimes things get left behind and this will clean them up.
Boot phone into recovery mode (Appendix: Recovery Mode)
You should no be in Clockwork Mod:
There are two options that we need to worry about "Wipe data/factory reset" and "Wipe cache partition".
You need to do both of these, in the order above.
Once these are done there should be an option to "Reboot system now". Do this.
Your cache should now be cleared.
4.3 Restoring
Open the market and download the same programs as before and use them to restore your data
Make sure that you turn off "Delete old messages" and notification settings in stock messaging app before restoring SMS.
Note that apps will not maintain a proper link with the market, it is recommended that you download all apps from scratch using the restore list as a reference.
4.3 APN Settings
If you backed up APN earlier then use the backup, alternatively:
Go to Menu --> Settings --> Wireless and Network --> Mobile Networks --. Access Point Names
Delete all present APN's via long press
Press Menu button --> New APN
Enter details appropriate to your provider which you should be able to find by searching for "<provider name> APN settings"
You may have to create more than one APN
Section 5: Extras
5.1 Rooting and Basic Kernel
Further modification usually requires a little something called root permissions. This is equivalent to administrator privileges in windows. While most custom kernels offer this, Chainfire's CF-Root kernel offers close to stock functionality with this feature added. Grab it here. The latest version should work for the firmware in this guide.
Put phone in download
Open odin
Plug phone in
Load kernel file as PDA
Install
This will install Clockwork Mod (CWM) as well. Having root permissions and CWM will help you modify your phone further (if you so desire).
5.2 SpeedMod Kernel
If you want to upgrade the phone just a tad more than download the latest version of Speedmod Kernel. It's a custom kernel that performs a little bit better than stock. To installs it, do the same procedure as above.
This will also install Clockwork Mod (CWM) Recovery.
5.3 Modem
To do this you need to have done step 5.1.
There are a heap of different modems you can use. The modem is basically the actual phone component of the phone that communicates with the network. Here is a list of available modems but not all of them are gingerbread compatible:
Modems
I would recommend downloading this one UGJL2 Modem. Good battery life and good reception. However, stock modems in gingerbread (JVP onwards) have comparable performance. This is only really something you should learn just in case it's more useful in the future.
You may have to adjust the modem to work on the right band. To do so see the end of the original post here: Modems
To install:
Download file
Copy it across to the phone SD card
Boot phone into recovery mode (see Appendix: Recovery Mode)
Navigate to install zip from SD card (see Appendix: CWM Navigation)
Find the zip you put there and select it
Choose Yes
Phone should install modem and reboot.
Appendix:
Recovery Mode:
Volume Up + Home + Power (until first galaxy s startup screen shows then release)
ADB (Appendix: Download Mode via ADB) "adb reboot recovery"
Download Mode:
Volume Down + Home + Power (until download mode screen shows)
ADB (Appendix: Download Mode via ADB) "adb reboot download"
CWM Navigation:
Use volume to go up and down
Power button to select an option
Back to go back
USB Drivers:
If your USB drivers aren't working then you can try reinstalling them with these:
32 Bit Systems
64 Bit Systems
2.2 Download Mode via ADB
To install ADB, download this and extract it to C:\SDK.
In My Computer, navigate to C:\SDK
In that folder there should be a folder labelled "android-sdk-windows", rename it to "SDK2"
In the second SDK2 folder, run "SDK Manager" and, after some time, this should show:
We only need to install the first one so for each item under the first one, click it and to the right click the reject button until your window looks like this:
Press Install
When finished it will ask to restart ADB, press yes.
Press Close
Once it has installed you need to run windows command prompt (press 'Windows key + R' then type "cmd" and hit enter)
Once in command prompt type "cd C:\SDK\SDK2\platform-tools"
Now type "adb reboot download"
You phone should now show this:
Download key combo should work after flashing.
Finished
Thanks to Hardcore and devz3r0, [Ramad], as well as other users in this thread which have helped to make this guide better. Original ADB Guide. Some reference to this guide also.
Please let me know if i have missed anything.
Think this is the most detailed explanation online... Very Usefull... THANKS in the name of noobs...
ha, i see this thread AFTER i flash my phone (just flashed yesterday)
hi,
you forget to leave password for extract the firmware !!
nicx said:
hi,
you forget to leave password for extract the firmware !!
Click to expand...
Click to collapse
It should be 'samfirmware.com'.
Sent from my GT-I9000 using XDA Premium App
The perfect guide. I am almost tempted to Flash mine but I am still too much a coward.
wow this is just what i need.
My girlfriend has been complaining about how slow her stock 2.2 galaxy is going. She is finally going to let me mod it
Is there another download mirror i can get the 2.3.4 fw from instead of hotfile?
cheers.
FarSight87 said:
wow this is just what i need.
My girlfriend has been complaining about how slow her stock 2.2 galaxy is going. She is finally going to let me mod it
Is there another download mirror i can get the 2.3.4 fw from instead of hotfile?
cheers.
Click to expand...
Click to collapse
You will find many firmwares here: http://forum.xda-developers.com/showthread.php?t=1102881 XXJVP is the first on the list and is only 147MB in size.
Thanks for the guide. There was some nervous moments when odin got stuck at factoryfs.rfs and my phone went green but I found http://forum.xda-developers.com/showthread.php?t=839556 and changed the USB port, and all went well.
Before you restore your previously saved precious SMS, make sure to disable the automatially delete older SMS messages because the limit is set to 200 SMS (same goes for MMS, limit of 20).
For SMS backup and restore, you may also use:
SMS Backup & Restore (internal SD save)
SMS Backup + (syncs with Gmail)
APN Backup:
APN Backup & Restore (internal SD save, handles duplicates)
Call Logs:
Call Logs Backup & Restore (internal SD save)
Bookmarks:
Backup Bookmarks
Applications, I did not find a solution that would "link" the apps back to the Market Place, so backing up downloaded apps did not make much sense, it did just speed up the restore. But if they are not linked and know to Market Place, the My Apps link does not do anything useful to me .
Cache clearing:
It is recommended to clear the cache as well after the firmware installation.
The guide says we don't have to tick repartition.
But i think it should, as it's a 3-file firmware.
And if you don't use repartition, there is no need to backup, cause you won't loose data.
Well since the Cache is recommended to be cleared after the flashing, it is recommended to backup. And I ticked the repartition, because I have seen this mentioned here: http://droidangel.blogspot.com/2011/06/guide-how-to-flash-updateupgrade_10.html
Better safe than sorry
Oh and don't forget to disable HSDP after the flashing in case you are fine with 3G UMTS internet speed: http://www.addictivetips.com/mobile...-for-better-battery-life-on-samsung-galaxy-s/
Easiest way for backing up SMS: the app called 'GO SMS'. Much better than the Samsung one. And there's a feature to back up SMS automatically.
Sent from my GT-I9000 using XDA Premium App
mathijs727 said:
The guide says we don't have to tick repartition.
But i think it should, as it's a 3-file firmware.
And if you don't use repartition, there is no need to backup, cause you won't loose data.
Click to expand...
Click to collapse
You don't need to use a pit or re-partition with 1-file or 3-files firmwares, and there is no point in selecting a pit file while having 're-partition' un-checked.
[Ramad] said:
You don't need to use a pit or re-partition with 1-file or 3-files firmwares, and there is no point in selecting a pit file while having 're-partition' un-checked.
Click to expand...
Click to collapse
True, regardless, I changed the guide to include PIT and re-partition. It's just a tad cleaner and some people get pedantic about that. Won't make a difference to those who don't.
jcspecs said:
It's just a tad cleaner and some people get pedantic about that. Won't make a difference to those who don't.
Click to expand...
Click to collapse
I have seen the changes, you need to prepare your self now for questions like 'which pit file must I use ?'
I have also seen that you are using a link from samfirmware, why don't you use the link from Darky's Forum who was the source for this leaked firmware: http://www.darkyrom.com/community/index.php?threads/odin-cwm-base-ficetos-jvp-base-rom.3519/ samfirmware have just downloaded the firmware from Darky's Forum like everybody else and just put it on there forum.
[Ramad] said:
I have seen the changes, you need to prepare your self now for questions like 'which pit file must I use ?'
Click to expand...
Click to collapse
Yay was just about to include a link to your PIT article and a thanks at the bottom for you.
hi
hi i can't find the speedmod-kernel ,i download the link how you said and i extract and when i am going to put them in odin on pda is empty the with speedmod,somebody can help me please!
Try getting the latest version here.
please somebody can help me! i did every thing like said the side and cant put the kernel in pda in odin ,when i start the odin and i put in pda the file with kernel is empty!what i am doing wrong?please help
Galaxy Tab GT-P1010 NooB Guide - Last Revised 2012-02-29
2013-03-09 - SEE POST 9 FOR IMPORTANT INFORMATION
Revisions
2012-02-27 - Initial Publication
2012-02-29 - Added Firmware Download, Thread Consolidation, Custom ROM's, Flashing Stock Firmware and Q&A Section(s)
Post Summary
In this thread I will attempt to outline the details I know of regarding the Galaxy Tab GT-P1010. I feel this is a necessary thread because this device is NOT the same as the various other devices that garner so much attention within this forum and I personally experianced quite a difficult time searching to find the questions to my answers as they releated to this device in particular. While it is my opinion that this device should have it's own sub-forum, I do not believe it is popular enough. This said I feel that it is a fairly solid device and if you are like me, you are somewhat lost in in finding the approriate information. Hopefully this thread will be informative and popular enough that it may get stickied so us lowly 1010 users can find the information they are looking for. I am an active XDA member and will do my best to keep this thread updated as new information & techniques become available. If you see some information that you feel should be included do not hesitate to bring same to my attention and I will update the OP's accordinglly. These Instructions are for use on Windows machines even though I personally use a Mac. If you are in the same boat, I recomend running windows within a Virtual Machine (VM). I use Parallels but VirtualBox is a free alternative. Mac and or Linux only instructions may follow at a later date, but honestly a majority of users use Windows so I'm starting there. Without further a do, let's get started.
GT-P1010 Device Specifications
The GT-P1010 is also know as the "Wi-Fi Only" 7" Galaxy Tab. It differs from a majority of the devices in this forum because it has NO 3G or cellular capabilities. The hardware of the device is also different enough from the 3G/Cellular versions, that the Development going on for these other devices will NOT work for it. The GT-P1010 is unfortunately considered a "forgotten" device and even Samsung has seemingly abandoned providing updates for it. This is particularlly evident within the United States (US), however other Countries, speciffically the United Kingdom (UK) have been seeing updates. For the record I am the owner of a US version and this guide was written using my experiance on that device.
A complete list of specifications can be viewed from Samsung's US Website HERE
MD5 Sums
When downloading files from the internet is extremly important that you verify the download was complete and not corrupted. Insuring this can avoid troubleshooting issues that may simply be because of a bad file. All files available from this post will have an MD5 sum next to them. To verify that your file is EXACTLY the same as the file on the server you will need to run it through an MD5 checker. These checkers are available freely over the internet and Mac OS X even has one built in. I'm not going to make this post about how to run these programs but have included a few links below to get you started. A complete explanation of MD5 Sums can be found at Wikipedia.
WinMD5Free
Drivers - Samsung KIES
In order to perform updates to your P-1010 you need to be able to communicate with the device via a USB cable. While there are stand-alone USB drivers available, I chose to install Samsung's "KIES" application so that I could see if any updates were being pushed directly from Samsung. The KIES program also offers additional functionality to allow you to sync various media on your device. This functionality may or may not be needed for all users but by installing the software you are also guaranteed that the drivers needed to communicate with the device are installed on your machine. The US Samsung KIES site can be accessed HERE but I have included a direct link to the latest Windows Version below.
Kies_2.2.0.12014_18_7 ---- MD5 Sum: 7116aa29ce9df3dc2e916128c9c0aa4c
Download the file and double click it to install KIES and the drivers to you system. Once this is acomplished running the program will present you with a screen similar to the one below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ODIN
ODIN is a utility that communicates with your device when it is in Download Mode (see below). This utility allows you to flash different firmware and other files to your Galaxy Tab. A screenshot of ODIN running is posted below.
To Run ODIN you will need to download and Un-zip the following file. Once this is acomplished you can run the program by simply double clicking the .EXE file "Odin3 v1.85.exe" which will be inside the un-zipped (extracted) folder. The program does NOT get "installed" and this section is just an overview of the tool. Additional steps on when to use it, and how, will be included in the appropriate sections below.
Odin3-v1.85.zip. ---- MD5 Sum: 414e3af7c4c01e21527aeaab65e68a75
Download Mode
Initiating Download Mode
To communicate with ODIN the device needs to be placed into Download Mode. This is accomplished (from an OFF condition) by holding the Volume Down button + the Power Button at the same time until Download Mode is activated. I have found that the easiest way to do this is to press and hold the Volume Down button and then press and hold the Power Button. Download mode will activate within a couple of seconds and your device will indicate such by presenting you with the following screen. As soon as that happens you can release both buttons.
Exiting Download Mode
If you flash any updated files to your Tab using the procedures outlined below, the device will accept the files and reboot on it's own thereby exiting download mode. If you find that you have entered download mode when you did not intend to use ODIN to flash files, you can EXIT download mode by Holding the Power Button for about 10 seconds. The device will then turn off and when you turn it back on it will boot normally. This can be a little scary considering the warning stating "Do Not Turn of the Target". This warning can be ignored and it is actually telling you not to turn it off while files are being written to it.
Connecting Device to ODIN
To play it safe, I recomend that you try connecting your device to KIES FIRST just to insure that the drivers have been installed properly. If KIES can recognize the device then so can ODIN. Simply open KIES and connect the device to your computer via the USB cable. Once you see that KIES is communicating with the Tab you can close KIES and disconnect the Device from the USB. This will only need to be done once, again, just to make sure the communication is working. Once you are satisfied that it is ....
Run ODIN by double clicking the executable file as outlined above. Place the device in download mode as outlined above. Connect the device to the computer using the USB cable. You will then notice that ODIN has found and is communicating with your device because the ID:COM field will turn yellow and assign a COM port to your device. This COM port will vary by user so don't be alarmed if you personally don't see "COM5" as shown in the screenshot below. As long as this field turns yellow you are good to go.
Recovery Mode - Stock
A stock Tab has a built in recovery mode that will allow you to perform a factor reset on the device and other "maintenance". This mode is entered (from an OFF condition) by holding the Volume Up button + the Power Button at the same time until you see the Samsung Logo, then Release the Power button but continue to hold the Volume up button until Recovery Mode is activated and your device presents you with the following screen. As soon as that happens you can release the Volume Up button. Once Recovery is activated you can toggle through the menu items by using the Volume up & Volume down buttons. To execute a selection use either the Power OR Home Button. It is the Power button on my device but this apparently varies on some models.
Rooting
If you are here on XDA then you are probably interested in "Rooting" your device. Rooting has many advantages and certain Market Applications will only work if you have these Root Powers. The US version of the Stock GT-P1010 is currently running the Froyo version of the Android Operating System. A Gingerbread version has not been officially released and may never be. We will deal with upgrading to Gingerbread later in the Tutorial. For now, if you want to Root your device running Froyo (My device had Build: Froyo.UEKC6), you can follow these steps:
1. Download the application Z4Root from the following link:
Z4Root.1.3.0.zip ---- MD5 Sum: 077974421412b25089289acdc763b1c1
2. Unzip the archive to Extract the file : "z4root.1.3.0.apk"
3. Connect your Tab to the PC and initiate "Mass Storage Mode"
Connect USB Cable
Drag down Status Bar and Click "USB Connected" under the ongoing tasks
Click "Turn on USB Storage"
Your device should mount and be available as a Removable Drive in Windows
4. Copy the .apk file from step 2 to your device
It doesn't matter where you put this file. Just remember where so you can find it in the next step(s)
The easiest place would be the "root" of the Removable Disk
5. Enable "Unknown Sources" on your Tab
Settings >> Applications >> Check Unknown Sources Box
6. Enable "USB Debugging" on your Tab
Settings >> Applications >> Development >> Check USB Debugging Box
7. Install Z4Root
Use any "file explorer" program on the Tab. You should have an application called "My Files". It will work fine
Navigate to the .apk file you put on the device in Step 4
Click the .apk file
Click Install
Application will install and you will have a Z4Root Icon in your app drawer
8. Setup Z4Root
Click the Z4Root Icon
You will be presented with two (2) Options. Temporary Root & Permanent Root
I chose Permanent Root but you could "try" it first if you like
In my case the device re-booted and I was rooted.
To test this I installed an application called Titanium Backup (see next Section).
Note: The Z4Root Icon will remain and if you open it again you will be given the option to"Un-Root".
Titanium Backup
Titanium Backup is a GREAT program that lets you backup all your applications as well as the user data that is used by them. For example your game progress, high scores, ETC. Titanium Backup REQUIRES Root access and in my opinion is reason enough to Root your device. There is a Free as well as a Paid version of this application. Let's install this program to verify that we have in fact "rooted" our device.
Installing and Checking for Root
Go to the market and search for Titanium Backup
Give the free version a try just to confrm Root. Simply install it from the market.
Once installed open the application and you should be presented with a dialog box stating that "Titanium Backup is requesting Super User Permissions".
Click allow and follow any on-screen instructions
You will eventually get to an "Overview" screen and should see that Root Access has a Green Checkmark next to it and that BusyBox was installed from the app.
Congratulations you are now rooted
Backing up Files
To backup your applications and user data using Titanium Backup follow the steps below:
Open Titanium Backup and click the Backup/Restore Tab near the top of the screen
A list of the applications installed on your device will appear
Click the Settings Drawer Hardware Key
Click Batch
Under the Backup section on the next screen click Run next to "Backup all User App + System Data"
On the next screen Select the applications you want to backup, They are ALL selected by default.
Make sure the "Pause Active App's" radio button is selected
Click "Run the batch operation" button
Congratulations. You have just performed an application Backup!
Saving your backup to your computer
There is no reason performing a backup if you are just going to leave it on your device. Obviously if something catastrophic were to happen, you would lose the backup as well. The backup files are located in the /sdcard/TitaniumBackup directory.
Initiate "Mass Storage" as outlined in the Rooting Section above.
Once the device is mounted navigate to the TitaniumBackup directory. Note: When mounted to the PC, the /sdcard directoy is the one mounted so TitaniumBackup should appear in the root of the Removable Disk.
Copy the entire TitaniumBackup Directory to your PC
You now have a folder that can be restored to your device allowing you to restore your applications without re-downloading them from the Market.
Remember to copy this folder to your computer after perfoming any future backups.
Restoring your applications
To restore your applications and user data using Titanium Backup make sure that the backup containing the files you wish to restore is located at /sdcard/TitaniumBackup and follow the steps below:
Open Titanium Backup and click the Backup/Restore Tab near the top of the screen
A list of the applications installed on your device will appear
Click the Settings Drawer Hardware Key
Click Batch
Under the Restore section on the next screen click Run next to "Restore missing apps with data"
On the next screen Select the applications you want to Restore, They are ALL selected by default.
Decide if you want to restore just the app, the app and it's data or just the data by clicking the appropriate radio button
Click "Run the batch operation" button
Follow the prompts to install each application
Congratulations. You have just perfored a restore
Note: Once we get into flashing custom Rom's in the sections that follow, sometimes restoring application "data" can be problematic. If you flash a new firmware or Rom and are experiancing issues with an application after restoring it's data, this may be the reason.
Custom Recovery - ClockWorkMod
In the section above we explained about the System Reovery that was built and installed by Samsung. This is great for restoring your system to an out of the box (OOB) condition but not for much else. In order to flash custom Rom's and perform Nandroid Backups we will need to replace the "stock" recovery with a Custom version. ClockWorkMod (CWM) is the recovery of choice for a majority of users and while there are "others" out there, only CWM has been made available for our devices. A Nandroid backup is an exact copy or "image" of your system and can be used to restore your system to the exact state it was in at the time you made the backup. So, lets get to installing CWM.
You will need to download the following file:
Skin1980_P1010_CWM-RECOVERY-BETA-1 ---- MD5 Sum: ca14360ee5f1eebd0efaec5adc77940e
Note: This file is only to be used if you are running the Froyo Version of Android
Using the information above put your device in Download Mode and connect it to ODIN
click the PDA button in ODIN and navigate to the file you just downloaded
Make sure your ODIN screen is setup and matched the screenshot below:
Click the "Start" button and watch your device and the "Message" section of ODIN. You will see some some text in the message center and your screen will show a progress indicator.
Once this completes your device will re-boot. It may boot directly to your new ClockWorkMod OR it might boot back into your operating system.
If it boots to the operating system you can get to CWM using the same procedure outlined in the "Stock" recovery section above. Volume up + Power.
Make sure you are booted into CWM and see the screen shown below:
Once you are in CWM the Volume Up / Down buttonas re used to navigate through the menu choices and the Settings Drawer Hardware ley is used to select an option. The Back hardware key also functions to go back to the previous menu but all screens also offer a "Go Back" choice. If you click the Power Button and are presented with a blank screen simply click it again and CWM will come back up. Now, lets make out first Nandroid Backup!
Making a Nandroid Backup
Navigate and Execute the "Backup and Restore" menu item
Navigate and Execute the "Backup" menu item
Sit back and wait for your backup to complete.
A progress indicator as well as some text will be flashing across the screen
When it completes you will see .. "Backup Complete"
That's it! Congratulations!
Saving your backup to your computer
Again, as with Titanium there is no reason performing a backup if you are just going to leave it on your device. The CWM backup files are located in the /sdcard/clockworkmod/backup directory. Inside this directory you will see a folder that is named based upon the date and time you performed the backup. For Example 2012-02-27.21.57.14 means that the backup was created on February 27, 2012 at 21:57:14. This is UTC time so make sure you add or subtract your UTC offset to get to "local" time.
Initiate "Mass Storage" as outlined in the Rooting Section above.
Once the device is mounted navigate to the clockworkmod/backup directory. Note: When mounted to the PC, the /sdcard directoy is the one mounted so clockworkmod directory should appear in the root of the Removable Disk.
Copy the folder containing your backup to your PC
You now have a folder that can be restored to your device allowing you to restore your system to the exact sate it was in at the time of the backup..
Remember to copy any future backups to your PC as Well.
Restoring a Nandroid Backup
To restore your system to it's nacked up state make sure that the backup containing the Nandroid you wish to restore is located at /sdcard/clockworkmod/backup and follow the steps below:
Boot into CWM
Navigate and Execute the "Backup and Restore" menu item
Navigate and Execute the "Restore" menu item
Sit back and wait for your restore to complete.
A progress indicator as well as some text will be flashing across the screen
When it completes you will see .. "Restore Complete"
Navigate to and execute the "Reboot System Now" menu item
Your device will reboot and you will be restored to the exact state your system was in when you made the backup
Mounting Mass Storage in CWM
In some instances you may be faced with a system that won't boot which makes getting your Nandroid Backup put back on your device problematic. Don't fear. Using CWM you can mount the USB Mass Storage without the need to be running the operating system. Here's how:
Boot into CWM
Plug your USB Cable into your PC
Navigate to and Execute the "Mounts and storage" menu item
Navigate to and Execute the "mount USB storage" menu item
The Device will mount and you will have access to it from your PC
Copy your Nandroid Backup to the clockworkmod/backup folder
Go "back"
Go "Back"
Go to "backup and restore"
Restore your Nandroid
Reboot
Welcome back to a running machine!!
Credit and Thanks
While I have compiled all the files, tested them, generated MD5 Sums and written this tutorial based upon my experiance, it should be noted that other users are responsible for the actual Development. If you think I have done a good job and find this information usefull Please click my "THANKS" button. It is not necessary to thank me by witing a seperate post and by not doing so you keep this thread clean and easy to find the information that others may be looking for You should also visit the following users, find a post or two from them and THANK them as well. Without them none of this would be possible.
Skin1980 for his Development of ClockWorkMod for the GT-P1010
RyanZA for his Development of Z4Root
motafoca for his Development of ClockWorkMod for the KPI Firmware
Donations
While I enjoy tinkering with devices and trying new methods, doing so can be time consuming. Compiling and witing this tutorial took me a considerable amount of time. I have also convieniently placed all the required files on an Ad-Free, Fast Download server so you can get them quick and don't need to hunt around. Mediafire was my server of choice but it is NOT free. I pay a monthly service charge to host on the server and this will also insure that the files are available now AND in the future. If you like my work and feel that it has helped you, I would appreciate a donation as a token of your appreciation. Simply click the button below or the "Donate to Me" button under my Username. Anything you can spare will be appreciated and go toward keeping the file sharing up and running as well as keep me interested in generating more tutorials. Thanks in advance!
Questions or Comments
If you have any questons or feel that certain information could be added or clarified, feel free to post them. I will do my best to check this thread often and assist you as best I can. Valid questions will be answered and added to the Q&A post below.
Firmware and Kernel's for P1010
This section will contain a list and download links for the various Firmware's available for the GT-P1010. As noted above the US version has been getting no love from Samsung with regard to updates. This is a shame and makes no sense to me considering the UK version HAS been actively updated. With this said however many users have been "flashing" the UK versions to their US Tab's with success.
SamMobile Firmware Page
Latest Firmware
Europe Firmware
Middle East Firmware
Compliments of Mod2Xtreme.com
Forum Post Link
Firmware Direct Links
P1010XWKC1_OXX.rar ..... MD5 Sum: 95bd7437271f3bee6eacb017d0ef45a1
P1010XXKPG_P1010XEUKPG_XEU.zip .... MD5 Sum: 3b0f63ccb0b42643d953fcba472eb5f2
P1010XXKPI_XEUKPI_Android_2.3.6.zip .... MD5 Sum: 4d33426db6cecdb48568adecf10bc8fd
Kernel's
P1010ZHKF1-kernel.ZIP .... MD5 Sum: 6dc467ff92fc676c1f61e59e893493eb
Custom Rom's
2/29/2012
Currently there are no Custom Rom's available for the GT-P1010. A Developer named Motafoca is working on a port of Cyanogenmod and information regarding progress can be viewed in the following thread.
Motofoca's Cyanogen Port
Motofoca is a member of the MadTeam and they have their own forum which can be viewed HERE.
The only other "Non-Stock" alternative at this time is CleanRom developed by scrosler There is also a website dedicated to this ROM viewable HERE.
I used the term "Non-Custom" because the CleanRom is based upon a Stock Gingerbread European firmware. From the Website they did the following:
Removed Samsung Bloat!
ADW Launcher or TouchWiz Launcher!
95% AOSP Gingerbread themed
All Apps up to date!
De-Odexed
Zip Aligned
Flashing Stock Firmware(s)
Flashing Stock Firmware(s)
We have said that updated firmware for the US version of the GT-P1010 has NOT been actively provided by Samsung however if you look in Post 2 above you will see that all is not lost. The Europe version of this device has been provided with an update as late as January 2012. I would recommend (and really it was the reason I wrote this tutorial) that you perform ALL the steps above BEFORE flashing any type of Firmawre update/upgrade. This will not only give you experiance running the "tools" but it will allow you to perform the various back-ups in case anything goes "wrong".
Quite simply, Firmware is "flashed" to your device using ODIN. I have searched for a complete guide explaining the vaious sections of ODIN to no avail. Honestly I don't know when certain fields (PIT, CSC), ETC need to be populated and when they don't. I believe, but am not 100% sure that when flashing a brand new Firmware (for example from a US to European version) that the PIT, PDA and CSC fields need to be filled in and the Re-Partition radio button needs to be Checked. I have ALWAYS had the Auto-Reboot & F. Rest Time boxes checked, but again, I can't say why. It is my belief that if the Re-Partition button is checked, that it has the effect of "wiping" all partitions on the device.The only guide I have found is the following:
P1010-Flashingguide.pdf
It is probably a fair statement to make that if a Zip or RAR file you download contains a PIT or CSC file, then you probably need to included them in your flash. Keep in mind that I have experianced an issue where a seperate ZIP file was compressed inside an overall ZIP container. Always make sure that you not only extract the main downloaded file but that you also look inside the extracted folder for another ZIP file that may need to also be extracted.
I will provide an example of my experiance upgrading my US version to the latest UK version below.
Upgrading US Version to Latest Rooted UK Version
First, I must give full Credit to Taney for developing the instructions from This Thread. I followed them and experianced no significant issues. I will be re-creating a portion of them, expanding (clarifying) on some areas that I felt would give NooB's difficulity and then taking the instructions a step farther to upgrade to what is known as the "KPI" version of the Firmware which is the latest one Available. PLEASE make sure that you "Thank" Taney because without the instructions that he provided none of this would be possible.
A. Upgrade / Downgrade to the Latest Froyo Firmware
Place your Device in Download Mode and connect it to ODIN as outlined in the tutorial above.
Download the P1010XWKC1_OXX.rar file from the link in Post 2 of this thread and check the MD5 Sum
Extract this rar file to create a folder called "P1010XWKC1_OXXKC1"
Within ODIN Click the PIT button and navigate to the file "p1wifi_20110128_r10_00.pit" within the folder you extracted.
Click the PDA Button and navigate to the file "P1010XWKC1-REV03-ALL-low-CL946441.tar.md5"
Click the CSC Button and navigate to the file "GT-P1010-MULTI-CSC-OXXKC1.tar.md5"
Make sure the Re-Partition, Auto-Reboot and F. Reset Time buttons are CHECKED
Click "Start". ****** NOTICE THIS WILL WIPE ALL DATA ON YOUR DEVICE*****
When these steps are completed and the process running your ODIN screen should look like this:
When the process Completes your Device will Re-boot. The first Boot could take significantly longer than normal. Just wait and when you see the lock screen open it and enter the OS. At this point you may be experiancing what is known as a "boot-loop". Simply stated the device will keep re-booting and not allow you to do anything without throwing "force close" errors, In his tutorial Taney says that this may or may not happen. It did for me and the fix is in the next section.
B. Flash updated Kernel
To fix the effects of the boot loop you need to flash another file known as a kernel. Like I said I personally DID experiance the boot-loops and had to perform these steps. Since my overall procedure was successful, it is my recomendation that you do it whether you experiance the boot-loop or not. This decision is entirely up to you but you have my suggestion. To flash the Kernel perform the following:
Download the file file "P1010ZHKF1-kernel.ZIP" from the Kernel's section in Post 2 of this thread and check the MD5 Sum
Extract the ZIP file to create the folder "P1010ZHKF1-kernel"
If ODIN is still open replace the file in the PDA field with the file "P1010ZHKF1-KERNEL-eng.tar" from the extracted folder OR
If ODIN was closed open it, repopulate the PIT and CSC fields as outlined in Section A above and select the new file for the PDA field.
UN-CHECK the Re-partition check box
Power off your Tab. NOTE: If it is stuck in a bootloop I found that holding the power button down finally was able to shut off the device.
Start the device in Download mode and connect it to ODIN
If everything is set-up as outlined and ODIN has found your Device.. Press Start
When the process completes your device will re-boot and the ODIN screen will look like this:
At this point you should have a bootable Device and not experiance any further boot-loops. Your About Device Information should read as follows:
Firmware: 2.2.1
Kernel: 2.6.32.9 ([email protected]_24 #1)
Build: Froyo.XXKC1
C. Flash KPG Gingerbread update
In this step we will flash our first Gingerbread update known as the "KPG Version". Follow these steps:
Download the file "P1010XXKPG_P1010XEUKPG_XEU.zip" from the Firmware section in Post 2 and Check the MD5 Sum.
Extract the ZIP file to create the folder "P1010XXKPG_P1010XEUKPG_XEU"
If ODIN is still open replace the file in the PDA field with the file "P1010XXKPG_P1010XEUKPG_HOME.tar.md5" from the extracted folder OR
If ODIN was closed open it, repopulate the PIT and CSC fields as outlined in Section A above and select the new file for the PDA field.
UN-CHECK the Re-partition check box
Power OFF your Tab
Start the device in Download mode and connect it to ODIN
If everything is set-up as outlined and ODIN has found your Device.. Press Start
When the process completes your device will re-boot.
At this point you should have a bootable Device running Gingerbread. Your About Device Information should read as follows:
Firmware: 2.3.6
Kernel: 2.6.35.7 - CL749223 ([email protected] #1)
Build:GINGERBREAD.XXKPG
D. Reinstall ClockWorkMod
The steps above have had the effect of returning your device to stock and therefore the Recovery Partition was overwritten with the "stock" recovery. We need to re-install ClockWorkMod at this point.
Download the following file and check the MD5 Sum
Skin1980-P1010-NEW-CF-ROOT-GB.tar .......MD5 Sum: 1cab6775d572c416371c09f9c3654823
Put your device in Download Mode and Connect it to ODIN
Navigate to the File you downloaded using the PDA field
Leave the PIT and CSC fields BLANK and Un-Checked
Un-Check the Re-Partition Check Box
Click RUN
When the operation completes the device will re-boot
At this point you will have a Rooted KPG Version of Gingerbread with a fully Functioning ClockWorkMod Recovery. You may wish to stop here but reports informed me that the KPI firmware was faster. I decided to Install it as outlined blelow/
E. Flash KPI Gingerbread update
Before Installing the KPI Update I did the following:
From within the running system went to CWM application and opened it.
Granted the application Superuser Permissions
Used the application to "Re-Boot to Recovery"
Device Re-Booted into CWM and I performed a Nandroid Backup
While still in CWM "Wipe Data / Factory Reset" AND
Wipe Cache Partition AND
Wipe Dalvik Cache
Power Off
Your Device is now ready to recieve the KPI Firmware Update
Download the file "P1010XXKPI_XEUKPI_Android_2.3.6.zip" from Post 2 and Check the MD5 Sum
Extract the the file to create the folder "P1010XXKPI_XEUKPI_Android_2.3.6"
Start you Device in Download Mode and connect it to ODIN
Navigate to the file "P1010XXKPI_P1010XEUKPI_HOME.tar.md5" in the PDA Field
Leave the PIT and CSC fields Blank and Un-cjecked
Make sure the Re-Partition checkbox is Un-Checked
Click Run
While the program is running your ODIN screen will look like this:
When the Process completes your Device will Re-Boot and your About Device Info will be as follows:
Firmware: 2.3.6
Kernel: 2.6.35.7-CL882382 ([email protected] #1)
Build: GINGERBREAD.XXKPI
At this point I performed the following:
Went Through Initial Setup Screens
Powered Off Device
F. Re-Install ClockWorkMod AGAIN
Same as before. The procedure has wiped out our Recovery and we need to Re-install it. This time however we will use a different file beause I do not Believe the Skin1980 Gingerbread Version is compatible with the KPI Firmware. Luckily we have another Developer working on this Device. Please visit and Thank Motafoca for providing the following file:
madteam-cwm-p1010-kpi.tar .......MD5 Sum: f868e789245ec3dae87efaf2e30b1165
Put your device in Download Mode and Connect it to ODIN
Navigate to the File you downloaded using the PDA field
Leave the PIT and CSC fields BLANK and Un-Checked
Un-Check the Re-Partition Check Box
Click RUN
When the operation completes the device will re-boot
At this point you will have a Rooted KPI Version of Gingerbread with a fully Functioning ClockWorkMod Recovery.
G. Final Steps (Optional)
Opened CWM Application and Granted SuperUser Permissions
Rebooted to Recovery Using "Reboot Recovery"
NOTE: This version of CWM uses different button mappings. Volume Up / Volume Down to navigate and POWER button to Select
Mounted Device using Mounts / Storage and connected to PC
Put Titanium Backup files back on Device
Reboot System Now
Setup Date and Time
Connected to WiFi
Went to Market and Added Google Account
Waited for Account Sync to complete
Re-Enabled "Unkonon Sources"
Downloaded and Installed Titanium Backup
Ran Titanium Backup and Restored app's and data
DONE and running PERFECT !!!! Enjoy!!!
Donations
While I enjoy tinkering with devices and trying new methods, doing so can be time consuming. Compiling and witing this tutorial took me a considerable amount of time. I have also convieniently placed all the required files on an Ad-Free, Fast Download server so you can get them quick and don't need to hunt around. Mediafire was my server of choice but it is NOT free. I pay a monthly service charge to host on the server and this will also insure that the files are available now AND in the future. If you like my work and feel that it has helped you, I would appreciate a donation as a token of your appreciation. Simply click the button below or the "Donate to Me" button under my Username. Anything you can spare will be appreciated and go toward keeping the file sharing up and running as well as keep me interested in generating more tutorials. Thanks in advance!
Thread Consolidation and Links
The following Threads have been found and pertain strictly to the GT-P1010. If you find another thread that you feel should be included either link it in a post or PM me. I will review same and add to this section as appropriate.
[WIFI Only] [How-to] GT-P1010 Gingerbread Update ........ Thanks Taney
[CWM][RELEASE] Clockworkmod recovery for P1010 ....... Thanks Skin1980
Galaxy Tab p1010 tweaks ..... Thanks s2h2golf
[Tool / Mod] - CleanMOD 1.0.1 for GT-P1010 Gingerbread 2.3.6! Mod the Tab! ..... Thanks scrosler
Omg. G-R-E-A-T thread. Soo cool. Well, maybe we can cm on the tab, but a lot of developers are selfish
thank you for creating this guide!!
I got one of these for my daughter to play with and I was having a hard time figuring out what information pertains to her model.
Question and Answer Section
***** Reserved for Questions and Answers *********
2013-03-09 - I have been away from these forums for awhile now and apologize if I haven't been around to answer any questions. Just been too busy with other responsibilities. While I still own this device, I have moved on to another and have not kept up with development on the GTP-1010. I hope that many users have had success but I know from reading the posts that a few have struggled. Thank you to those that have attempted to assist in my absence. Honestly, without doing much with this device, I don't know how to answer some of the PM's I have received. This device was at the time considered "Legacy" in my mind and over 1 year later I don't believe anything has changed. With this said I will not be providing additional information or files and it does not make financial sense for me to continue paying for the "Pro" mediafire account. I will be canceling it today but have paid for it through 2013-04-01 at which time it will revert to a "free" account. I have no idea at this time what will happen to the links in my posts on that date but suggest that anyone interested, download everything before then. If time permits I will attempt to move everything over to a new server but I make no promises. The "free" version of Mediafire may still work but I vaguely remember paying for "pro" for a reason. I just don't remember why. Thanks for all the "thanks". I'm glad this has at least helped some people. Again, I appologize for not being around and for any issues with the links after April, 1 2013
******* One More for Good Measure ********
Bravo
Thank you for your hard work. Sent donation. Saved me hours of searching and coordinating the info. C'mon guys, how much time has this post saved you?
Hi i followed your instructions until i got to "Rooting" section.. the little problem issue i have is that the device i have doesn't have the Android Market..(i know i was shocked too) it has the Samsung Apps online but even that doesn't have the Titanium Backup App... any suggestions of how to install the Android Market? (btw love the instructions, nice and clear)
apolonetics said:
Hi i followed your instructions until i got to "Rooting" section.. the little problem issue i have is that the device i have doesn't have the Android Market..(i know i was shocked too) it has the Samsung Apps online but even that doesn't have the Titanium Backup App... any suggestions of how to install the Android Market? (btw love the instructions, nice and clear)
Click to expand...
Click to collapse
Sorry about the late response. Honestly this forum gets very little attention and I haven't been checking as often as I should.
That said ... I think you need to review post 4 which is an extension of the lessons learned in post 1. The firmware files ALL have the market built into them and following those steps should return you to a STOCK ROM. Make sure you backup any user files that you need before you begin. An internet search should allow you to find the .apk file for titanium backup. If you enable "unknown sources" in settings and get the app onto your device, clicking it should install the application. I'm not sure though if you finished the rooting step of stopped short or it. You NEED root to run Titanium,
Also, Keep in mind that as stated I performed these steps on a US version of the hardware and I don't offer that devices from other regions will be 100% compatible. But, from my research I believe most should be.
In summary, please provide me with additional details regarding your device and it's history. I'm sure we can get you squared away. There is always a Google App's package (GAPPS) that could be flashed to your device to get the Market but I am concerned about the fact that your's doesn't have it. This makes me think that without starting from a fresh ROM we would ultimately just be chasing our tails trying to troubleshoot other issues.
Thank you so much for replying.. i didn't think you'll reply to my post... but before i go to the next step.. i was playing around with it.. following your instructions on updating drivers and rooting etc... i then got stuck on "rooting" section hence me posting for help on getting the Titanium Backup... anyway i decided to upload couple of rugby videos so i can watch it later... i was in the middle of one video when all of sudden it stopped and turned itself off, i turned it back on and it stuck on the Samsung logo and it has been stuck on that since 24+ hrs ago after turning it on/off... on/off - i think i might have f'd it up...
I got it as a prize from a competition last year (2011) in Oct, and ever since i've been having problems with it.. let me know what other info you need me to provide!
much appreciated for the help!
THANKS SO MUCH! You made my day!
-Redbearded Tyrant
"Sic Semper Tyrannus"
apolonetics said:
Thank you so much for replying.. i didn't think you'll reply to my post... but before i go to the next step.. i was playing around with it.. following your instructions on updating drivers and rooting etc... i then got stuck on "rooting" section hence me posting for help on getting the Titanium Backup... anyway i decided to upload couple of rugby videos so i can watch it later... i was in the middle of one video when all of sudden it stopped and turned itself off, i turned it back on and it stuck on the Samsung logo and it has been stuck on that since 24+ hrs ago after turning it on/off... on/off - i think i might have f'd it up...
I got it as a prize from a competition last year (2011) in Oct, and ever since i've been having problems with it.. let me know what other info you need me to provide!
much appreciated for the help!
Click to expand...
Click to collapse
Honestly in order to support you I believe you should start from scratch. You should be able to get the device to download mode even if it is stuck on the Samsung Logo. Hold the power button until the unit turns off completely and then use the instructions to enter download mode. Then follow all the instructions in Post 4.
This will of course wipe your device totally clean so make sure you have everything backed up. Even though you can't get the system to boot you may be able to access your files by hooking it up to the PC. This is certainly true if you have already installed CWM. Look in the tutorial and find the section where I discuss "Mounts & Storage" from within CWM. This will allow you to copy off any important files. Then perform all the steps in Post 4.
That is really all I can offer as I don't know what you have done on the device to this point.
hai there.
i have few questions regarding upgrade to gingerbread.
my OS is 2.2.1 Froyo.DXKG1
if i want to upgrade my device to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6, should i upgrade my device to the latest froyo (P1010XWKC1_OXX) then to gingerbread (P1010XXKPG_P1010XEUKPG_XEU) then to gingerbread (gingerbread P1010XXKPI_XEUKPI)??
or i can upgrade it straight away to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6??
Thank you
Hi, i can't find your Post 4, are you able to post a link here please... ta
totihut said:
hai there.
i have few questions regarding upgrade to gingerbread.
my OS is 2.2.1 Froyo.DXKG1
if i want to upgrade my device to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6, should i upgrade my device to the latest froyo (P1010XWKC1_OXX) then to gingerbread (P1010XXKPG_P1010XEUKPG_XEU) then to gingerbread (gingerbread P1010XXKPI_XEUKPI)??
or i can upgrade it straight away to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6??
Thank you
Click to expand...
Click to collapse
Yes! This is what worked 100% for me so I recomend all the steps. The first upgrade to latest froyo has repartition checked which essentially gives you a clean slate. The seperate GB steps insure you end up with root. Good luck!
apolonetics said:
Hi, i can't find your Post 4, are you able to post a link here please... ta
Click to expand...
Click to collapse
Its the 4th post in THIS thread. "Flashing Fimware" section.
OK I think I cleaned this up a bunch:
Go Here to get all the files, and instructions.txt documentation. (UPDATE: due to dropbox's unreliability, I mirrored all the files to my Google drive public folder. Please use either as long as they work. Feel free to PM me if one goes down.)
ALL users should back up their APNs. Use an APN backup utility to backup/restore.
Code:
[QUOTE=eyeconic]May I make a suggestion?
Actually, EVERYONE should back up their APN. Some user may need to use that backup to restore their APN. I used: [url]https://play.google.com/store/apps/details?id=com.riteshsahu.APNBackupRestore[/url][/QUOTE]
Correct. EVERYONE should backup. Some may meed to restore.
Sent from my U8800-51 using xda-developers app. BAWLZ!
This was discovered by watching the GB Update Forum. Thanks to eyeconic.
Thank You to the Following People. (I hope I didn't forget anyone)
Code:
savagehqfor providing the stock IMG
http://narod.ru/disk/45137127001.c41110d6962cdd0386662315635cdcc4/u8800-51.rar.html
skippedfor instructions on reverting to stock
http://forum.xda-developers.com/showthread.php?t=1589205
KayxGee1for Win7 Roadkil fix
http://forum.xda-developers.com/showpost.php?p=24618284&postcount=2
skippedfor instructions on backing up phone using "Roadkil's DiskImage"
http://forum.xda-developers.com/showpost.php?p=24408417&postcount=3
roadkil.netfor making DiskImage
http://www.roadkil.net/program.php?ProgramID=12
zchuxz3xfor making a Stock to GB Tutorial
http://forum.xda-developers.com/showthread.php?t=1698308
Somcom3Xfor making a Custom GB to Updated GB Tutorial
http://forum.xda-developers.com/showthread.php?t=1844442
Somcom3Xfor making a Updated GB to Aurora ICS Tutorial
http://forum.xda-developers.com/showthread.php?t=1844982
[email protected] providing Browser.apk to fix crashing browser
http://forum.xda-developers.com/showpost.php?p=26917631&postcount=3
hitaxasfor linking to [email protected]'s posting of Browser.apk
http://forum.xda-developers.com/showpost.php?p=31196713&postcount=18
Bad.Fishfor discovering that a factory reset was needed after backing up the phone.
eyeconicfor discovering that some people need to back up APNs.
*************NOT OPTIONAL!*****************
********Backing UP Working u8800-51********
****VERY IMPORTANT! Do in case of FAIL!****
Code:
Make a disk img recovery Using "Roadkil's Disk Image" (and Pink screen)
The procedure is easy and you just take about 8 minutes..
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Download the tool "Roadkil's Disk Image"
1.a Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button.
1.b Connect your phone to PC using USB
2.a Run "Roadkil's Disk Image" (from step 0.a)
2.b Click on the "Store Image" tab.
2.c In "Store Image to" click the combobox and choose "Physical Disk #" ("#" is a number) * If there are more than one "Physical Disk #", then you have to choose the one that is about 3.6gb.. This part is very important.. if you restore a backup from another disk, it will leave your phone unusable.
** To be sure that that Physical Disk you choose is the Huawei u8800-51, You can run the tool again (because it has to refresh) without the phone connected, then check which disks are available. Then, close the tool again, connect the device (in pink screen), run the tool, and check what physical disk was added. But it will be about 3.6gb.
2.d In "target file", save the file as "u8800-51.img" in a folder with more than 4gb of storage available.
** There is no risk for you, as it is just copying data, not writing. **
** The risk is when restoring a backup if you backed up the wrong Disk... **
** If you compress the "u8800-51.img" file into a "rar" file, the size will be about 700 mb, then put it in a safe place. (Like DropBox, and/or multiple hard drives, etc.) **
UPDATE:
I have used this method to restore my phone 3 times without problems, but I'm win7 so I had to use the win7 fix outlined above.
Stock Froyo to Custom GB
Code:
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Make a disk img recovery Using DiskImage (and Pink screen)
0.c Boot into recovery (Vol+ & Power) and do a factory restore.
1.a Download "U8800-51 a Gingerbread.rar"
1.b Extract the Archive.
2.a Transfer the "dload" folder to the root of your sdcard
2.b Turn the phone off completely
2.c Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button. (As though going into Pink Screen) Installation will start.
3.a After the phone finished installing and boots into Android choose the language.
3.b You will notice that you have no signal. This is Fine for Now.
3.c Open File Manager and delete the "dload" folder.
3.d you must also clear the Quick Start (labeled "Fast Boot") in settings> applications, then turn off the phone
4.a Boot Phone into Bootloader (Pink Screen, see step 2.c)
4.b Connect to the pc via USB.
4.c Replace the "boot.img" with the "boot.img" from the "Root para Gingerbread" folder.
5.a Turn on the phone and verify that you have super user.
5.b Turn off phone.
5.c Boot Phone into Bootloader (Pink Screen, see step 2.c)
5.d Replace the "boot.img" with the "boot.img" from the "boot original" folder.
6.a Install ToolBox5irom (step 0.a)
6.b Restore IMEI
6.c Reboot System
** System Should now boot with functional Data. **
Custom GB to Updated GB
Code:
This is a modified stock gingerbread rom for the u8800-51
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Make a disk img recovery Using DiskImage (and Pink screen)
0.c Download "ginger movida v1.1.zip"
0.d Download "CWMv5.5.0.4 recovery.img"
1.a Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button.
1.a Replace "recovery.img" with "CWMv5.5.0.4 recovery.img"
1.b Wipe Battery Stats/cache/dalvik cache in cwm
2.a Install "ginger movida v1.1.zip" using CWM. (From Phone off, Hold Vol+ and Press Power)
2.b Reboot system
** If there is a problem, revert it to stock 2.2 via disk image and start over again. **
Updated GB to Aurora ICS
Code:
This is a modified Aurora ICS Final Build.
Modified Gingerbread must be installed first!
Install at your own risk!
Instructions:
0.a Back up IMEI using ToolBox5irom
0.b Make a disk img recovery Using DiskImage (and Pink screen)
1.a Download "Aurora.zip"
1.b Download "gapps-ics-20120429-signed.zip"
1.c Download "UPDATED AURORA.zip"
1.d Download "CWMv6.0.1.0 recovery.img"
1.e Download "Browser.apk" (to fix crashing browser after everything)
2.a Install CWMv6.0.1.0 recovery (from step 1.d) (Install it via pinkscreen or root explorer.)
2.b Wipe Data/battery stats via CWM
3.a Install "Aurora.zip" (from step 1.a) via CWM
3.b Reboot System
3.c Install "UPDATED AURORA.zip" (from step 1.c) via CWM
4.a Reboot system.
4.b Install "gapps-ics-20120429-signed.zip" (from step 1.b) via CWM
4.c Reboot System
5.a Install Browser.apk (from step 1.e)
Note: It may take MANY attempts for it to start, it will constantly reboot. If it takes more than 1/2 hour, than you must restore the disk img recovery.
To enable mass storage install u8800 Aurora drivers and do not toggle mtp. If toggled you need factory reset.
Edit: Tested by me. Must install another keyboard since system keyboard does not exist.
Usb only recognized in recovery, seeking adb fix.
In order for back light you must select auto brightness then un select it.
It begins in Spanish but you need to select language and restart.
Must download poweramp to play music.
No radio
3g may or may not work
Download
You have been warned.
Stable for daily use.
***************OPTIONAL!*******************
*********Reverting to Stock Froyo**********
***ONLY DO THIS IF YOU MESS SOMETHING UP***
Code:
** This will not work on Entel users in Chile as it is a locked restore (it is for at&t users only)- **
100% of the time, You should always backup anything you change. Especially if you don't know what the change will do.
This instructional will help you recover from screwing up your phone (assuming you didn't make a backup image before messing with it.)
Instructions:
0.a Download "DiskImage_1_6_WinAll_Setup.exe"
0.b Use "LockDismount0300.zip" in case of WIN7 problems (see bottom of document)
0.c Download "U8800-51.rar" (about 400mb but its compressed, its really 3.9gb)
0.d Extract "u8800-51.img" from "U8800-51.rar" (Fail to do this and brick your phone)
1.a Open the tool "Roadkil's Disk Image" (from step 0.a)
1.b Hold both ends of the volume rocker (Vol+ and Vol- at the same time) and press the power button. (This puts you in Pink Screen)
1.c Connect to PC using USB.
2.a Run "Roadkil's Disk Image" (from step 0.a)
2.b Click on the "Write Image" tab.
2.c In "Write Image to" click the combobox and choose "Physical Disk #" ("#" is a number)
** If there are more than one "Physical Disk #", then you have to choose the one that is about 3.6gb. **
** This part is very important.. **
** If you use a backup from another disk, it will leave your phone unusable. **
** To be sure that that Physical Disk you choose is the Huawei u8800-51, You can run the tool again (because it has to refresh) without the phone connected, then check which disks are available. **
** Then, close the tool again, connect the device (in pink screen), run the tool, and check what physical disk was added. But it will be about 3.6gb. **
3.a In "source file", choose the file "u8800-51.img" that you Extracted from u8800-51.rar (in step 0.d) (remember it is about 3.9gb and extension is ".img")
3.4 Press Write Image.
3.5 After it is 100% ready, disconnect and do a factory reset and you will have 3g working.
** If you were smart enough to have backed up your IMEI at some point, you can install "ToolBox5iromV1.0.4.2.apk" and restore it at this point. **
** If you were smart enough to have backed up your phone prior to messing it up, you can replace any use of "u8800-51.img" in this instructional with your backup image. **
** I already went through one phone because I wasn't smart enough to do backups. Learn frommy mistakes. **
** This will not work on Entel users in Chile as it is a locked restore (it is for at&t users only)- **
*** FOR THE USERS ON WIN7 HAVING TROUBLE WITH "Roadkil's Disk Image" ERROR ***
4.a Download LockDismount to fix the issue (see step 0.b)
4.b Run LockDismount (Run compatibility XP3)
4.c Select the necessary 3.69 drive described above (check multiple times to ensure you're selecting the right drive, for me it was Physical Drive 1)
4.d Click Lock
4.e Keep LockDismount open
4.f Run "Roadkil's Disk Image" (from step 0.a) and then go through the downgrade process. (Start with step 2.a)
Error should be fixed now!
*** FOR THE USERS ON WIN7 HAVING TROUBLE WITH "Roadkil's Disk Image" ERROR ***
Please let me know if I missed anything.
your missing all the roms except for aurora btw.
Somcom3X said:
your missing all the roms except for aurora btw.
Click to expand...
Click to collapse
Yeah. Lol forgot that Dropbox says 14 more hours to complete sync.
Wow!
Sent from my u8800-51 using xda premium
Somcom3X said:
Wow!
Sent from my u8800-51 using xda premium
Click to expand...
Click to collapse
Okay all of the files finished uploading.
Updated aurora info.
Sent from my u8800-51 using xda premium.
Somcom3X said:
Updated aurora info.
Sent from my u8800-51 using xda premium.
Click to expand...
Click to collapse
Do I need to make any changes to my files/instructions, then?
Oh I see. You linked to my thread. Cool, Thanks.
OK. Here it is (so far...)
I backed up my imei. (5irom)
I backed up my Phone (Roadkil's DiskImage)
I installed GB (data didn't work after everything, so i said screw it and: )
Installed Updated GB. (After that my GF called and I couldn't install ICS right away, but phone and data was working.)
Going to install ICS now.
BTW Wifi was working too.
...And just finished. Everything seems to be working now.
Did you install?
Somcom3X said:
Did you install?
Click to expand...
Click to collapse
Yup. Also edited my build.prop so my device shows as U880-51 instead of pro...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my U8800-51 using xda app-developers app
interf sist error
Hello, :good:
thanks for the guide and roms from our device.
I installed the rom ICS on my u8800-51 from Brasil, but when I change the language to Portuguese the app "Interf sist" closes. Run ok only in English. Exists any correction for this problem?
Danielregis said:
Hello, :good:
thanks for the guide and roms from our device.
I installed the rom ICS on my u8800-51 from Brasil, but when I change the language to Portuguese the app "Interf sist" closes. Run ok only in English. Exists any correction for this problem?
Click to expand...
Click to collapse
I am sorry. I don't know much about anything non-english. I am just a typical english-only American. (Much to my chagrin.) I only gathered up guides others had made an put them together. You may have better luck asking in the forum specific to the Android version you installed up to. I can only share my own experience.
Sent from my U8800-51 using xda app-developers app
Danielregis said:
Hello, :good:
thanks for the guide and roms from our device.
I installed the rom ICS on my u8800-51 from Brasil, but when I change the language to Portuguese the app "Interf sist" closes. Run ok only in English. Exists any correction for this problem?
Click to expand...
Click to collapse
try to uncheck 24 hours format after changing the lenguage , in settings -> date and time.
I made a couple bootanimations
http://forum.xda-developers.com/showthread.php?t=1899090
[bootanimation] u8800-51
I made this Bootanimation in Powerpoint. I like it, so I thought I'd share.
U8800-51 bootanimation.zip
Thanks! Used it to unbrick my Ideos X5 PRO!
Thank you very much!
You unbricked a pro using a -51 rom?
freezes after dload reboot
phone reboots then freezes on startup going from stock to gb.... any suggestions?
there's anyone found any solution to the white screen in facebook and gmail?
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
For this problem i downloaded UL-K013-WW-12.10.1.36-user.zip file from asus site and i installed. But i get an error like "This package is for K013 devices..... bla bla" and i googled and i deleted 2 rows from updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
and new rom installed without any problem. But result was same, Asus logo and gray-or-black screen.
Anyway, i downloaded the older version UL-K013-WW-12.10.1.36_KK-user.zip and i installed
now i just see this message.
AFU: test IFWI BIOS update.
FV File Size is 0x00300260
I cant open recovery menu, I mean
VOLUME+ and Power => NotWorking
VOLUME- and POWER => Not Working
Just Volume(+) plus Volume(-) plus POWER is working, i mean fastboot menu.
Can i install my tablet from this menu? Or what can i do for my tablet? What is your advice guys?
Sorry for my english.
Thanks.
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
it's not related with this thread
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lambdadroid said:
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
Click to expand...
Click to collapse
Hi
thanks for your replay, i tried somethink with fastboot but i didnt success.
I hope somebody can help me.
Thanks again.
pojeck said:
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
Click to expand...
Click to collapse
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
lambdadroid said:
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
Click to expand...
Click to collapse
hi again
as you told me i did and recovery menu is working now.
C:\Temp>cd asus
C:\Temp\asus>
C:\Temp\asus>fastboot flash osloader efilinux.efi
sending 'osloader' (2009 KB)
fname=efilinux.efi...
2009 KB / 2009 KB
OKAY [ 0.085s]
writing 'osloader'...
OKAY [ 0.006s]
finished. total time: 0.094s
C:\Temp\asus>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
OKAY [ 0.001s]
finished. total time: 0.434s
C:\Temp\asus>
Click to expand...
Click to collapse
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
pojeck said:
hi again
as you told me i did and recovery menu is working now.
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
Click to expand...
Click to collapse
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
lambdadroid said:
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
Click to expand...
Click to collapse
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
Click to expand...
Click to collapse
Any idea?
pojeck said:
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Any idea?
Click to expand...
Click to collapse
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
I'm not sure why your device isn't booting anymore. Have you tried a factory reset (you can also do that from TWRP).
Hi
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
Click to expand...
Click to collapse
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
pojeck said:
Hi
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
Click to expand...
Click to collapse
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
lambdadroid said:
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
Click to expand...
Click to collapse
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
pojeck said:
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
Click to expand...
Click to collapse
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
lambdadroid said:
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
Click to expand...
Click to collapse
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
pojeck said:
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
Click to expand...
Click to collapse
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
lambdadroid said:
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
Click to expand...
Click to collapse
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
pojeck said:
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
Click to expand...
Click to collapse
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
lambdadroid said:
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
Click to expand...
Click to collapse
I'm so sorry about that
you can find the correct files in attachment
Thanks...
pojeck said:
I'm so sorry about that
you can find the correct files in attachment
Thanks...
Click to expand...
Click to collapse
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
lambdadroid said:
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
Click to expand...
Click to collapse
Hi
Thank you very much for your kindly notice
I deleted last img files and some pictures.
I'll wait for fixed files, Thanks again.
[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.