This guide will hopefully help people with minimal to zero knowledge or people which are very afraid to just try things on their own to upgrade their Samsung Galaxy Note GT-N7000 to a newer firmware, which might be a pre-release firmware, a leak from somewhere or which won't be or isn't yet available on KIES. The procedure outlined graphically and textually explicitly only takes care of firmware releases which don't come packed as a single .tar.md5 file of about 850mb, but to releases which are split up in several packages of varying size with the file extension .tar.md5. The same procedure applies to single-file releases as well, coming as a single packaged .tar.md5 file. When flashing a single file release, naturally some steps can or must be skipped, like extracting the image files or several selection dialogs in CWM, as there is one one choice to make when dealing with a single file.
The procedure outlined may not be the shortest possible or the least complex one. But I do judge it to be the probably most universal one and following the steps closely should avoid all kind of problems and lead to a seamless and trouble free update. All possible firmware combinations should be updateable this way, as long as the prerequisites are met and the instructions are followed closely. This procedure does not influence or trigger the custom binary flash counter or the yellow warning triangle.
Information: Please read instructions carefully, as it took me quite some time to structure and present them as they are. You may ask questions if problems arise, if important details differ from the steps presented here or you would like to add anything, but post's which clearly show that the author didn't read this message or the very clear instructions in their entirety and rather just puts up a post out of pure lazyness, will get deleted and I will ask moderators or admins to impose some sort of punishment on the poster. I will not let party poopers insult me with their lazyness.
The information presented is structured and numbered. All steps which follow a number are according to my judgement closely connected and form one step. This explains why not every single click or action gets it's own number. Numbers in brackets inside a paragraph, for example [3] means there is a picture existing for the information given in this step. In this example case, it would be picture with index number 3, as pictures as well will be numbered and labelled accordingly.
If you find this information helpful, you may hit the thanks button.
End of introduction. The procedure starts here.
Minimum prerequisites:
Pre-rooted firmware on the device *)
CWM app
SD card, ~1GB free space
*) If you come here without a pre-rooted device, go back and check the threads on how to obtain root. Do not ask here, this thread is for updating an already rooted device only.
1. Prepare the device:
You'll need to prepare your device in a specific way to be able to use this method. You will need an external SD card with at least about 1GB free storage. Access the SD card on the device or by mounting it on your desktop pc [1]. Create a folder in the root of the card named "firmware". Thus, when accessed through the device, the complete path to that folder should be "/sdcard/external_sd/firmware" [1]. This is the folder CWM checks for firmware parts to be flashed.
{
"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"
}
Image 1: Path on external SD card
2. Find the appropriate firmware you want to upgrade to:
Decide on a firmware you want to upgrade to. Download it from your source of choice. You may end up with a .zip or .rar. or generally speaking an archive file [2] you have to extract. Do so.
Image 2: archived firmware release
After the extraction you will most likely find a subfolder being created with several files inside. The content of the firmware you downloaded may differ from the content shown in the image below [3], this does not matter, as long as some central files which I will get to later are at hand. Once you got this far, you may minimise the window, as we will continue elsewhere.
Image 3: extracted firmware release
3. Find and flash the matching cf-root kernel:
Information: If you just rooted your device and did not change kernels since, there is a certain possibility that you already run a cf-root kernel. In this case, this step can also be left out. If you do not know or are unsure, continue to follow the guide.
In order to maximise compatibility with the CWM app, a cf-root kernel will be used for all flashing activities. Find the kernel matching the the firmware you chose to upgrade to in chainfires cf-root release thread. You find the thread here: http://forum.xda-developers.com/showthread.php?t=1331784
If there is no exact match, general rule of thumb use the one you read the best reviews about or just the newest one available. It does not matter if the kernel is two or three releases older than the firmware you want to flash.
Substeps 3.1 Download and extract the kernel image:
- 3.1 a) Download the corresponding kernel as instructed above.
- 3.1 b) The kernel comes pre-packed as a .zip file. Extract it [4].
- 3.1 c) Inside the .zip there will be a .tar file. Extract it.
- 3.1 d) You'll find a file named zImage, push it to the device into the folder created in step 1.
- 3.1 e) Unmount the SD card from the pc, in case you have it mounted.
Image 4: archived cf-root kernel (release shown: KL7)
Substeps 3.2 Flash the kernel on the device using CWM:
- 3.2 a) Launch the CWM app, select "Flash kernel" [5].
- 3.2 b) Navigate to folder from step 1 and select zImage.
- 3.2 c) Confirm the dialog [6], the device will reboot. *)
*) In case you encounter a bootloop, turn off the device, enter recovery with VolUp-Home-Power and chose to "wipe cache" and under advanced, "wipe dalvik cache". Reboot afterwards.
Image 5: CWM app, select [1] (left); Image 6: kernel flash confirmation (right)
4. Flash the firmware:
Navigate to the folder you minimised in step 2, containing the extracted firmware. Of interest are only 3 (three) files, which must be copied to the folder created in step 1. Depending on the firmware release, the names of the files of course differ. Below I will give the generic name of the three files in question and then list a couple variations, so everyone can figure out, which files are to be taken. After copying the files, make sure to unmount the SD card from the pc, it must be accessible on the device.
Files of release XXLA3:
CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5
MODEM_N7000XXLA3_REV_05_CL1095424.tar.md5
GT-N7000-MULTI-CSC-OXALA3.tar.md5
Files of release XXLA1:
CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
GT-N7000-MULTI-CSC-OXALA1.tar.md5
Abstraction: The files containing CODE, MODEM and MULTI-CSC are to be taken and put in the folder created in step 1.
Substeps 4.1 Flash the firmware on the device using CWM:
- 4.1 a) Launch the CWM app, select "Flash stock firmware" [5].
- 4.1 b) Confirm the dialog, also confirm the second dialog.
- 4.1 c) Select zImage as "Source file for: kernel" [7].
- 4.1 d) Select MULTI-CSC as "Source file for: cache" [8].
- 4.1 e) Confirm the dialog.
- 4.1 f) Chose "Keep CF-Root kernel" [9].
Image 5: CWM app, select [2] (left); Image 7: kernel source confirmation (right)
Image 8: cache/CSC source confirmation (left); Image 9: root options (right)
The device will now reboot twice, enter recovery each time and flash the firmware chosen. After the flash, you will be running an updated and pre-rooted Android build on a cf-root kernel. You may freely flash the kernel of your choice in case you do not want cf-root. It is highly recommended that you do switch over to cf-root when flashing to have maximum compatibility between kernel, recovery and CWM app.
You may hit the thanks button now
Message 2
Update overview
Update 19 January 2012, Revision 2
Added the information that the guide also applies to single-file releases coming as a single .tar.md5
Message 3
Outline for future updates
-Update procedure in guide where it differs from multi-file firmware to single-file firmware flashing.
-Information on how to create a nandroid/CWM backup and - provided the firmwares are compatible - restore data after a successful upgrade.
This guide works perfect and very easy to understand!!! Just flashed mine to latest firmware using this guide and it was a breeze!
Thanks
Sent from my GT-N7000 using xda premium
You're welcome. Damn I totally underestimated how long it takes to throw all this sh** together...
Schaggo You are Great
schaggo you are really great.
I was running all over the forum to check how should i upgrade my note from KL3 to LA1 or LA3 through CWm and Mobile Odin Pro.
I screwed my mobile twice with "Logo.*****" error when trying it through mobile odin. Literally i got panicked when my phone came with that "Logo *****error". So I went back to stock KL3 after my two attempts which didnt work.
Later i saw this thread and you know what.. it was crystal clear.... Newbee like me prefer your kind of tutorial to MOD our phones without screwing it.. Even a 10yr kid who knows english can upgrade his/her GN with your guide lines. i.e it is explained in such a way.
Thanks alot for your guidelines..
schaggo said:
1. Prepare the device:
You'll need to prepare your device in a specific way to be able to use this method. You will need an external SD card with at least about 1GB free storage. Access the SD card on the device or by mounting it on your desktop pc [1]. Create a folder in the root of the card named "firmware". Thus, when accessed through the device, the complete path to that folder should be "/sdcard/external_sd/firmware" [1]. This is the folder CWM checks for firmware parts to be flashed.
Click to expand...
Click to collapse
Hi, Thanks for the incredible tutorial.
I was just wondering why we should create the firmware folder under the /sdcard/external_sd/
Shouldn't it be working on the /sdcard/ only?. Sometimes I have problems with CWM and the external card, it gets unmounted e.g. while doing backups
Thanks
The reason is quite simple: it's hardcoded this way. The file(s) to be flashed must reside at /sdcard/external_sd/firmware.
I backup onto the internal memory and use the external card mainly for storing some MP3 and stuff I brought over from my previous Android...
Very clear and understandable, thanks for the great guide! I think one of the major issues with a lot of the other guides on here is the language barrier, for me at least. I say that in the most non-offensive way possible.
Sent from my GT-N7000 using XDA App
Hello Schaggo,
Sorry for cross posting this, but I just discovered your suggestion in the other thread that noob should really follow your guide here and avoid ruining their devices
So I rooted my note and am ready to upgrade it back to Debitel's LA4 firmware, using CWM instead of MobileOdin, and I'm stuck as shown in the attachment, I not only tried LA4, but also Debitel's KK9. It also turned out to be the same result, "can't mount firmwareflash.zip".
Do you have any suggestion to solve this issue?
Thanks a lot!
EDIT: SORRY, forgot to attach the quote of my own from that other thread "[STOCK ROMs]" by THE DOCTOR ;p
cswithxda said:
Please help me
I finished "downgrading to KJ4" and "Rooting", and now I'm on my way upgrading to XXLA4 (Debitel) (which I originally had).
I'm using CWM (tried to avoid Odin, even tho i know it's safe to flash factory ROM, but still, it will try to keep current Kernel). And I got this after I choose "Keep CF-Root Kernel" and the device restarts.
BTW, the firmware is on an external SD card itself. I saw a previous member addressed this issue by starting to use a physical external SD card, but I am already using one
EDIT: just edited the attachment, now it shows how it "aborted" the process ;(
Click to expand...
Click to collapse
Sometimes the ROM - zips is inside the original zip..
run it in Winrar and see what it shows..
cswithxda said:
Hello Schaggo,
Sorry for cross posting this, but I just discovered your suggestion in the other thread that noob should really follow your guide here and avoid ruining their devices
So I rooted my note and am ready to upgrade it back to Debitel's LA4 firmware, using CWM instead of MobileOdin, and I'm stuck as shown in the attachment, I not only tried LA4, but also Debitel's KK9. It also turned out to be the same result, "can't mount firmwareflash.zip".
Do you have any suggestion to solve this issue?
Thanks a lot!
EDIT: SORRY, forgot to attach the quote of my own from that other thread "[STOCK ROMs]" by THE DOCTOR ;p
Click to expand...
Click to collapse
OK. I just figured this out (in the process of flashing tho)
So here's what I did differently this last time from previous attempts (likely 50+ times in the past couple hours): when copying the firmware .tar.md5 file over to the phone from my computer, I dragged that SS_DL.dll file (provided that you have any) together this time. And the CWM recognized the firmware fine.
I'm just writing this down in case anyone else in the future have this issue. So keep this on record.
NOW, HOORAY! Debitel LA4 with Rooted KK9 Kernel!
Love this forum!
This is interesting, as I deliberatly leave out the .dll file. I did so when I flashed KK9. Also when I flashed LA4. In fact, every time. And I flashed them all since November (except LA6, which brings nothing new to the table).
Could it be the file(s) got damaged in the process of transferring it onto the device when you tried the first time round? As the .dll is of absolutely no value to Android.
Edit: but yeah, xda is a godsend...
#Tapatalk #Galaxy Note
Stareing at your screenshot again, it rather seems to me the recovery is/was unable to mount the sdcard and stalled. I also have to say, I never got the countdown your screenshot exposes. I mean its quite a while since I flashed LA4 but I'm quite sure my flashing activities went differently. Could it be that your sdcard is borked? Did you unmount it correctly (eject on pc, then unmount)? Quite hard to pinpoint, now that it worked...
#Tapatalk #Galaxy Note
Thanks for your reply!
Yes, I can't think of what I did differently besides copying that additional dll file.
I did try to copy files to SD card many times thinking that it could be the file was corrupted during the transfer. I also see people with this issue suggesting that the issue was due to the corrupted firmware file from download, so I downloaded it again and the issue persisted.
Also, there is no option on my computer to eject either the phone or SD card, so I always have to just unplug the phone, after which I unmount the SD card in the phone, and re-mount it.
Hopefully when next upgrade thru CWM is coming up and I can try it again, but for now, I definitely do not want to mess with it anymore, as I've spent nearly 10 hrs last night to solve this problem
May I flash Team Rocket Rom 1.1 (ICS 4.0.3) with CWM ?
cswithxda said:
Also, there is no option on my computer to eject either the phone or SD card, so I always have to just unplug the phone, after which I unmount the SD card in the phone, and re-mount it.
Click to expand...
Click to collapse
This way the card can get dirty. In case you're using Windows: sure it's there, at least since Windows 2000 if not longer. Right click the mounted drive, select "Eject". Wait for the confirmation. Otherwise in the systemtray, select the USB icon and unmount the (two) drives.
Hopefully when next upgrade thru CWM is coming up
Click to expand...
Click to collapse
I'm downloading LP1 right now. I'll flash it right when it's done and see what's what.
minhsu said:
May I flash Team Rocket Rom 1.1 (ICS 4.0.3) with CWM ?
Click to expand...
Click to collapse
I'm not aware of the format the Team Rocket ROM comes in. But if it's a .zip containing a couple files and a META-INF folder, then no, you can't flash it using this method. In this case it's an "update.zip" and you have to flash it using the "Flash update.zip" methon in CWM App.
I really don't have that
I don't have USB tray icon when the phone is connected either (i do see it when a flash drive or external hard drive is connected)
Please see the attachment ...
LOL... you access the device through KIES and MTP (Media Transfer Protocol), you don't mount it as a USB mass storage device. No wonder!
Oh my godness, KIES is such ****!
Oops! Noobility here...
How do I change to USB connection? I clicked on "USB connected" tab, but nothing happens, so I could only access MTP mode
Related
I was wondering if i was the only one who's a noob on this site because i have been trying (with no success) to root my using some good directions which i have posted below. The problem is... i only speak noob. I am so new to this stuff that i really dont know what to do. What i have already done is downloaded the update.zip and the SDK i dunno if i installed it properly but i know i have to go into my cmd and type something... from then on there i have no clue what to do. ANY HELP IS GREATLY APPRECIATED ^_^
Originally Posted by AllGamer View Post
Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volumen up down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box
Before you begin get some important info from the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
just glance through it, and look at the pretty pictures.
then to Root you phone follow this topic, which is also linked on the Wiki
Self Unlock SGS tutorial
http://forum.xda-developers.com/showthread.php?t=747235
which starts from the basic, to root, all the way to unlocking the phone
post back if you have any question or get stuck at any point
just in case you missed it, make sure your 3 buttons Recovery Mode is working, else keeps all your finger crossed for good luck
{
"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"
}
the update.zip that you seek is attached to the link of the rooting/unlocking topic linked above
if the 3 button recovery mode doesn't work
using the Android SDK you installed run the ADB.EXE command
it is inside one of the folders after you unzip the Android SDK package
k so the 3 button thing was a no go :/ do you think you could walk me thru (slowly) how to do the whole abd thing properly? Also the link you reffered me to is exactly what is on this thread and i just dont have enough experience to understand each of the steps, if u can just give me the main pointers in noob talk then i think ill be albe to figure out the rest
yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed
AllGamer said:
yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed
Click to expand...
Click to collapse
Can i do that while im on recovery mode or will that eff evrything up?
So i now have no idea how to put the update.zip file onto my internal sd card there is nothing on the phone i checked all the settings and i disabled the debug...
does the windows explorer shows the drive letters?
just copy and paste the update.zip file into the Internal SD card of your phone
when you connect via Kies mode to your PC
the windows explorers automatically pops up too
Bell root is not possible!
i may try samsung keys however i dont see how that helps you put the update.zip on your internal memory card or allows you to access anything in adb.exe in command promp.....my main question is acctually how the heck do you root the samsung vibrant with bell??? I have tried the thread in xda developers forum for bell saying it is the only way to get it to work....well it willl not work along with the million other ways i have tried, except 1clickroot it bricks alot of phones. Has anyone successfully rooted vibrant with bell! If so how?! I have even tried Z4Root which is the preferable method, well maybe i will just have to wait until some figures out a way that works. Boot with 3 button method "up vulume +menu+power" then apply sdcard:update.zip
E:signature verification failed
Installation aborted.
It says this everytime no matter what way i try!!! please someone have a solution!
Here you go...
This worked well for me.
http://forum.xda-developers.com/showthread.php?t=803682
Read all instructions carefully!
Rooted!
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?
aub_pro said:
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?
Click to expand...
Click to collapse
For my first phone, I tried RyanZA's OCLF (search for oclf in the app market). I did have it installed and working pretty decent but ran into some issues in the beginning trying to apply the lagfix.
On my new phone, I applied Darky's ROM 9.2 with SpeedMod Kernel. You can enable or disable lagfix from recovery mode using CWM (ClockWorkMod) Personally, I just left the lagfix disabled and my phone now is performing way better then my first phone when I had lagfix enabled. (Mind you, my first phone was bricked).
I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol
aub_pro said:
I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol
Click to expand...
Click to collapse
Do you have a Bell phone?
- In any case, I had flashed my kernel using odin first.
- Copied the ROM(the entire zip file. don't extract it) over to the root folder of my phone.
- Boot into CWM and selected install zip from sdCard
- Select "choose zip from sdCard
- find the ROM that you downloaded to your phone and select it.
- let the phone do its thing and your good to go.
That was probably the long way but I now see that you can apply the ROM through Darky's Configurator...
- Open up Darky's Configurator
- Select Wipe the device if you want a clean install
- Select your Kernel preference
- Select Modem options (this is why I asked if you were Bell user. Apparently there has been an issue where you loose 850 band if your flashing a new ROM using JL2. So in this option, I selected "no modem")
- Check Alternative WiFi driver
- For the rest of the options you can see you can choose for yourself.
Once you are done with the selection process, press the menu key button on your phone, then choose "Select Zip and Flash".
Follow instructions on phone and you are good to go.
awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....
aub_pro said:
awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....
Click to expand...
Click to collapse
No need to extract that file. Once it is downloaded on to your PC, use Odin and navigate to where the file is downloaded.
I will have to verify the kernel I downloaded when I get home but I'm certain that I did not extract anything.
kernel installed
ok speedmod kernel is installed but when i load up darkys config the wipe all is greyed out and i cant click it.....im assuming that i use boot phone into recovery and whpe/factory data reset from there? wont i lose the darky 9.2 rom then being as it is on the root of the internal card?
the bold parts below are confusing me....so on the internal sd i should have the update.zip and darky rom 9.2 or is it just refurring to darky rom everytime it mentions zip?
Now turn off your phone, and wait for it to shutdown completely. Then, boot into Recovery Mode. Press and hold Volume-UP + Home + Power at the same time, and let go of the buttons when the screen turns on (and says Galaxy S GT-I9000/I9000M Samsung), to enter Recovery.
7. Then using the volume keys to navigate and the Power button to select, do the following:
Select 'wipe data/factory reset', and then select 'Yes'. Important!
Select ‘Install zip from sdcard’.
Then select ‘choose zip from sdcard’.
Now navigate to the ROM zip, then select it.
Then choose ‘Yes’.
8. The ROM will now be installed. After it says install complete, select ‘Go Back’ twice, then select 'Reboot System now'.
There you go, Darky's ROM is now installed!
k i figured it out im at the last step installing update.....been at this screen for about 10 mins but im sure thats normal.?
k it was hanging way to long on the installing updates screen and appeared to be frozen so i press menu + vol up + power and after a few time of it hanging at the galaxy s screen it finally brought me to clockwork recovery....so i rebooted normally and now i have the speed kernal still installed still rooted but the phone is original hardware? what do i do now?
Hey
....when you go to the menu settings about on your phone, what does the build number say?
Do you have Darkys Configurator app installed? Use that to flash the new rom. If you have nothing on your phone I would choose wipe. Choose the itmes that you want in the configurator. Select the menu button on your phone then select the option Save zip and exit... the second button in the bottom right.
Then choose Darkys rom where you saved it on your phone.
Sent from my GT-I9000 using XDA App
This thread is primarily intended for n00bs.
I would like to say thanks to xda forum members: Noejn, Zecanilis, drellisdee, The_ERROR etc. Also thanks is due to Godlike! at tech-mania.com for his tutorials. Thanks is due especially to The_ERROR for proofreading the post and to other users for their suggestions written in the thread.[/SIZE]
---------------------------------------------------------------------------------------------
NEW - 3 May 2011 - Simplified Guide to Root & install version 1.2 of Custom Thunderg Recovery by AmonRa/modified by Drellisdee on LG P500
ALWAYS MAKE A BACKUP BEFORE CUSTOMISING YOUR PHONE.
[CUSTOMISING A PHONE USUALLY INVOLVES: ROOTING >>>> INSTALLING CUSTOM RECOVERY >>>> INSTALLING CUSTOM ROM]
The instructions written below have been tested by me using an Indian unbranded GSM model of LG P500 which came with stock Android 2.2.1 (V10C). The procedure to be followed for any LG P500 phone is the same.
This post is split into 4 major sections -
1. INSTRUCTIONS FOR ROOTING
2. INSTALLING ANDROID SDK ON A WINDOWS PC (This step is needed to install Custom Recovery on phone using adb from PC. Can be omitted if Recovery is installed from phone using Terminal Emulator)
3. INSTALLING A CUSTOM RECOVERY
4. INSTALLING CUSTOM ROMs
MUST READ: If you haven't read this thread already, please do read it - Dictionary for n00b - What is.../What does ...mean?
---------------------------------------------------------------------------------------------
1. INSTRUCTIONS FOR ROOTING
To know your present firmware version - Go to Settings/About Phone
Only phones which come with stock android 2.2 could be rooted till recently.
UPDATE - 24 April 2011 : A tool called 'GingerBreak APK' is able to root phones running stock android 2.2, 2.2.1 & 2.2.2. Read about it HERE. This tool enables rooting without the need for downgrading the firmware to 2.2. If 'GingerBreak APK' doesn't work out for you, continue reading to understand the procedure to root your phone after downgrading your firmware. Note: 'GingerBreak APK' permanently roots your phone. Also,GingerBreak might not install BusyBox and SuperUser apps properly on your phone. These apps are required by many rooted apps for their proper functioning. So, use Root Checker from android market to verify the proper installation of these 2 apps.
If your phone runs stock android 2.2, enable 'USB Debugging' on Phone (Settings/Applications/Development). Install z4root (copy the apk file to the sd card and open the file after browsing to the location using the phone's file manager), run it and root the phone. Find it HERE.
Choose the permanent root option as it is still possible to force unroot if needed.
Restart the phone and launch z4root to check the root status. A successful rooting should show 'Unroot' option when z4root app is opened.
{Note: z4root automatically installs Busybox and Superuser application(which appears as an icon in your app drawer) on the phone.}
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
For phones that came with stock 2.2.1 or 2.2.2 installed, rooting first involves downgrading the firmware to 2.2.
Downgrading the firmware can be done with KDZ-FW-UPD.exe (procedure outlined below)
(KDZ-FW-UPD.exe has been claimed to work best with windows xp 32bit.)
FIRST: DOWNLOAD THE Android 2.2 FIRMWARE FOR YOUR DEVICE. For this, go to: [ROMS] Original LG Firmware list and read about the procedure to download the original firmware.
{Tips: Use Ctrl+F in browser to search for Country name, Remember to change the alphabet in 2 places in the final link to download the firmware, Do not bother about the 'CDMA' tag attached to country code. It works for the GSM model phones too. If the link to find out the country codes doesn't work, use the 2nd method mentioned in the post to find out the country code using your phone's IMEI or ESN number }
Download the required Firmware onto your PC.
Links to Original firmware versions for Indian P500 are mentioned in THIS POST
Procedure to install original firmware using KDZ-FW-UPD.exe ( KDZ FIRMWARE UPDATER ) This procedure can also be used to restore the stock firmware and recovery onto your phone in case you want to give your phone to the service centre during warranty period as the phone will appear similar to as you bought it from the store.
[Note: This procedure was used to install V10B_00.kdz(android2.2) over V10C_00.kdz(android2.2.1) on an unbranded Indian GSM model of LG P500 using a Windows 7 Ultimate 64bit updated to date PC.]
1. Install LG PC Suite IV from SD card which came with phone by connecting the phone to PC through USB cable. This is done to install the drivers for the phone on the PC (the procedure is as follows)
- Enable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard & Phone Storage menu.
- Connect phone to PC with the USB Cable.
- Press the 'Turn on USB Storage' button which appears on phone.
- Browse to the folder containing the 'LG PC Suite IV' on the phone's SD card using Windows Explorer and run the LG Installer file. PC Suite will now install on your system along with the required drivers for your phone.
- Cancel setting up PC Suite or continue setting up PC Suite if you want to Sync or backup the phone data.
- After closing PC Suite, Safely remove the USB device from your system.
- Press the 'Turn off USB Storage' button on phone screen.
- Detach the USB Cable.
- Disable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard &Phone Storage menu.
Alternatively, I also tried installing the latest drivers via LG Mobile Support Tool from LG's website (available HERE) but KDZ-FW-UPD.exe (mentioned below) crashes when run. This could be happening only to me, so please try for yourself before writing off this method.
2. For my comfort more than anything else, I switched off the screensaver and other power saving features on the PC and also set the screen timeout delay on the phone to 30 minutes.(Settings/Display/Screen Timeout)
3. Charge the phone to the maximum.
4. Enable USB Debugging on Phone (Settings/Applications/Development).
5. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
6. Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.)
7. Unmount the SD card from the phone (Settings/SDcard & Phone Storage).
8. Open phone back and remove the SD Card.
9. Download KDZ_FW_UPD_EN.7z onto your PC and extract it to a folder. Available HERE.Direct Download Link. (MD5 of 7zip file - 813A28BE9182AB604A1D43E745CE7AD7)
10. Run the msxml.msi file and complete the installation.
11. Connect the phone to PC with USB Cable.( If you are using a desktop PC, make sure you use USB ports that are in the back of your PC, avoid the front ports.)
12. Run KDZ_FW_UPD.exe from the extracted folder.
13. Chose TYPE as 3GQCT & Phone Mode as DIAG.
14. In the 'KDZ file' space, browse for the firmware you want to install. (In this case V10B_00.kdz)
15. Press the 'Launch software update' button.
16. The firmware flashing process is now underway.
If all goes well, in 5-10 minutes the phone will be flashed with the new firmware.
I shall describe in detail what happened with my phone - 10-15 seconds after launching software update on PC, my phone screen turned blank and in a couple of seconds the phone entered the 'Emergency Mode'. During this mode the screen was yellow with Emergency Mode written along the middle of the screen. The phone stayed in the same way till the Software update procedure finished on the pc and the phone turned blank. I waited a while for it to reboot but after a minute or so, I manually switched on the phone. The phone came alive and following the LG boot animation, the android logo screen came up. The phone spent about 2 whole minutes in that state before booting up fully and entering the home screen. Update: Wait till phone reboots by itself or wait for a while before manually switching it on.
17. After booting up fully, detach the phone from the pc.
(If the phone gets stuck in the android boot logo screen during first boot, doing a hard reset by pressing and holding the VolDown+Home+Power buttons may resolve the problem.)
Go to 'About Phone' in Settings and confirm the change from 2.2.1 or 2.2.2 to 2.2.
Root the phone using z4root as mentioned before.
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
IN CASE OF PROBLEMS DURING DOWNGRADING FIRMWARE, read the following thread completely. Various types of errors and various measures to correct them including some innovative ones like shaking the phone etc. are mentioned here - [HOWTO] Phone not responding at all - last chance to repair. It is advisable to read this thread completely before attempting to downgrade the firmware using KDZ_FW_UPD.exe to become aware of all the possible problems you might encounter and their possible solutions.
PS: Here is the link to the phone drivers that came with my SD card. One user reported a problem wherein kdz updater would recognise the phone but the update process would fail during kdz unpacking. the problem was resolved by using the drivers i sent him. So, if anyone has the same issue, it might be worthwhile to try out the following drivers. I wouldn't advise everyone to follow this method, but those of you who are feeling lucky might try it out. Download Link
---------------------------------------------------------------------------------------------
2. INSTALLING ANDROID SDK ON YOUR WINDOWS PC
This step is required to install Custom Recovery on your phone using adb from your PC. Using a Custom Recovery, you can make a backup of your current ROM, restore backups, create partitions on your SD card, wipe your phone and the SD card and then also go on to install Custom ROMs using the Flash from Zip option.
Installing a Custom Recovery can also be done in other ways. Using Android SDK from your PC is just one method.
(Custom Recovery can alternatively be installed on your rooted phone using the commands given in the next section using a Terminal Emulator. This method removes the need for installing Android SDK on your PC and connecting your phone to PC. Download Terminal Emulator from Android Market. Install on phone. Run it and give it root permissions when prompted by the 'Superuser' application. As mentioned in the next section, copy the 2 files (flash_image & the custom recovery image file) needed to install Custom Recovery onto the root directory of SD card. Reboot phone. Open terminal emulator and type 'su' without the quotes and press Enter. This will take you to the root shell (#) from the default user shell($). Carefully type in the 7 commands mentioned in the next section one after the other. After typing in the last command (reboot recovery) and pressing enter, WAIT. The phone will reboot. Custom Recovery will have been succesfully installed on your device.
Hint: Copy the installation commands as a text file to phone & copy and paste the commands one by one into terminal emulator using a text editor. Please make the necessary changes to the installation commands depending on the recovery version used)
To install Android SDK on PC, there are a few requirements/downloads which have to be completed first:
JDK (Java Development Kit) - Download Here
JRE (Java Runtime Environment) - Download Here
Android SDK installer - Download here
So after all the downloads are completed, you are good to go. Run PC as Administrator.
First of all install the JDK, then the JRE and then the SDK Installer.
{If when android sdk installer is run, you get an error that JDK or JRE is not detected even after their installation, wait for a while, shut down the computer and restart and run the SDK installer once again.}
Make sure that while installing the android sdk, the installation directory should be the root of a partition i.e. it should be in the following form: C:\android-sdk, where you should replace the letter C with the letter you have assigned to the partition that you want to install it in.
Now that the Android-SDK is installed, go to the installation directory and start the SDK Manager. You need to add the components of the Android SDK to your installation. Before that I would like to inform you that you can save time if you download only what is necessary. If you are on Android 2.1 then you should download the 2.1 sdk, for 2.2 the 2.2 sdk and so on. You do not need to have all the versions for this thing to work. Just your version would do. So to start adding components, I recommend that you read THIS
After installing the desired components, you need to do perform some simple steps in order to use the adb terminal just like the cmd terminal for Windows.
For that purpose, here are the steps to be followed:
Right click My Computer, select Properties, and click Advanced System Settings. (Windows XP users - Right click My computer and just click Properties and select the Advanced Tab)
Click on Environment Variables, in the System Variables box, scroll down to the variable name 'Path' and double click to edit it
It would read something like " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static".
Here you need to add a semicolon ( ; ) and add the path of the tools folder in android-sdk.
It should finally be like this " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\android-sdk\platform-tools {or the location where adb.exe resides on your system}
Click OK wherever asked and then restart your computer.
Now open a command prompt window and type adb and hit enter. If a terminal window is displayed, you have done it all right.
If it gives some error message, read the article carefully and see what you have messed up with.
---------------------------------------------------------------------------------------------
Tip:
Using adb - How to install apps from PC without having to copy them first to the SD card?
If you want to install apps in one click, all you need to do is download the .apk file of your application to your PC and set the open with option to this batch file which you can download HERE
Save the batch file on the desktop of your PC before setting the option to 'Open With'.
---------------------------------------------------------------------------------------------
3. INSTALLING A CUSTOM RECOVERY
(Procedure of installing Custom Recovery using a terminal emulator from your phone instead of installing android SDK on your PC and connecting your phone to PC is mentioned in the last section.)
UPDATE - 3 May 2011 : Very simple way of installing Custom Thunderg Recovery by AmonRa/modified by Drellisdee version 1.2. Originally posted by ungaze in this post.
1. Download Android Terminal Emulator from Android Market. Install it on your rooted phone.
2. Download the file "amon_ra_recovery_installer.zip" from here or here. Check the MD5 hash value of the downloaded 'zip' file using tools like HashTab etc. before proceeding further. Correct MD5 value : 86db8a52b01f049cadb8f097a4c5bd9e
3. Extract the contents of the 'zip' file to the root of the sd card (ie. not inside any folder) using tools like 7-Zip or WinRAR or any other similar tool.
4. Open the terminal emulator app on your phone and type in the command 'su' without the qoutes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions to the terminal emulator app. Click 'Allow' and proceed. You will notice that the shell prompt has changed from the previous user shell '$' to root shell '#' in the emulator app.
5. While in the root shell '#', type in the following command and press Enter. Wait and the phone will reboot into the Custom Recovery.
Code:
sh /sdcard/rf.sh
Once you are up and running with a rooted phone, you will need to download the 2 files needed to install the Custom Recovery. They are:
Download No:1: flash_image - (This file is the same one needed to install any of the 3 versions of Custom Thunderg Recovery by Drellisdee given below)
Download Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link - requires registration at androidforums.com. (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Download No:2: Custom Recovery image file - Choose & download any version among the 3 available after reading what is written below.
Custom Thunderg Recovery by Drellisdee has versions 1.1, 1.2 and 1.2.1 at the time of writing this. I personally prefer version 1.2 as it supports backup & restoration of ext4 Partition on SD Card. Version 1.2.1 is a little experimental in nature & it may not fit all devices as it has a size near 5 MB.
Link to xda-forum thread for Custom Recovery P500/Thunderg - HERE.
The different versions of the Custom Recovery image files are available at the following pages
Custom Recovery P500/Thunderg v1.1
Direct Download link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Mirror Link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Custom Recovery P500/Thunderg v1.2
Direct Download link - (MD5 of zip file - 217FC9115899A41195CF124CAF07B880)
Custom Recovery P500/Thunderg v1.2.1
Direct Download link - (MD5 of zip file - 388aac16b1184ab15b5500b2b32d914c)
Please check the MD5 hash values of downloaded files to ensure that files are not corrupted using tools like HashTab etc.
Now to install Custom Recovery, Copy the two files [ the chosen recovery image file (*.img) & the flash_image file (flash_image) ] and paste in the root of your SD card (root means the directory L:\ where L is the letter for your Phone's USB Storage. In short, don't create a folder and paste the files inside it on your SD card).
{Note that the recovery image file should have an .img extension and flash_image file should have no extension when placed on the SD card}
Reboot the phone. Connect phone to PC.
The next step requires Android SDK to be installed on your PC.If you have installed the Android SDK, follow these steps:
Go to Start Menu & Run and type cmd (run as Administrator)
In the cmd window, type adb. If you have installed it correctly, you will see a lot of text on the screen. If you get an error message then you have probably not installed the Android SDK properly.
Type adb shell and hit enter
Type su and hit enter
See your phone at this time and touch the 'Allow' option which SuperUser shows you
Now the terminal window will have a # sign appended to it instead of the previous $ sign. See this screenshot for a better understanding
{
"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"
}
Now one by one, copy the following lines, in the serial order and paste it into the terminal window and press enter following each line(right click on window and paste, CTRL + V won't work)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (if it gives error message here, simply proceed to the next step)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (If the recovery version chosen is different from v1.2, type the appropriate file name of the recovery image here instead.)
reboot recovery
Click to expand...
Click to collapse
Wait. The phone will reboot now.
Note:{If you get this error after step 4
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
Simply move on to the next step.
If you get any errors other that those mentioned here, please do not proceed with the last command of 'reboot recovery'. If you do so, recovery may not be correctly installed and you will lose all data on the phone as the phone will be reset to factory defaults. Please go back to the instructions and see what you have done wrong.
NOTE: If on booting into the recovery you get the following message at the bottom of the screen -
E: 'Bad Boot Message'
Don't panic, it's perfectly normal and you can proceed with what you want to do from the recovery.}
Detach the phone from the PC.
To access the Custom Recovery, turn off the phone and then press & hold Home+Vol Down+Power buttons to boot into the Custom Recovery.
---------------------------------------------------------------------------------------------
Once you have booted into the recovery, the touch screen won't work. The actions assigned to the different buttons are given here. Use them to navigate through the different options in Custom Recovery.
Up & down: vol-up and vol-down key
Select: Menu key (left most)
Back: Back (3rd from left)
---------------------------------------------------------------------------------------------
What does Custom Recovery look like & What does it do?
Note: In Custom Recovery versions 1.2 and above, zips can be extracted from inside folders. So, save the zips in a folder named AAA and flash the zip after browsing inside the folder through recovery. The folder name should be named 'AAA' so that it appears among the first on the recovery screen, since scrolling is not an option in recovery.
Note: There is also an unofficial port of ClockworkMod Recovery availble. I do not recommend this recovery for newbies as it isn't compatible with all Custom ROM's out there.
---------------------------------------------------------------------------------------------
4. INSTALLING CUSTOM ROMs
BEFORE FLASHING ANY ROM, DO A NANDROID BACKUP FROM CUSTOM RECOVERY
Since all the ROMs have their own kinds of partitions to be created and other requirements, you can check them at the ROM specific pages.
General procedure to follow for installing a Custom ROM
Boot into Custom Recovery
Wipe your cache, dalvik cache, SD card
Make partitions according to the ROM requirement
Wipe cache again.
Connect Phone to PC
Toggle USB MS and paste the ROM zip file to a folder called AAA in the root of the SD card
Disable USB MS.
Detach phone from PC.
Select 'Flash from zip' option in Custom Recovery menu
Select the ROM file
Flash the ROM file
After flashing is finished, Reboot the phone.
Note: It will take some time to flash and reboot into your new Custom ROM. The phone may stay with the boot logo displayed for a number of minutes. Do not switch off phone during this period.
---------------------------------------------------------------------------------------------
In case of problems with phone, read: [HOWTO] Phone not responding at all - last chance to repair
Also read: [READ FIRST] [REF] Repository of howto's, roms, kernel, etc.
If you feel benefited by this thread, I humbly request you to rate this thread and vote it to the front page. The option to rate and vote is present in the title bar of the thread on the right side.
Please post your feedback. Also THANKS is always welcome. Use the THANKS button (below right) if you feel that I deserve it.
Update - 24 April 2011 - New rooting method without needing to downgrade firmware.
Update - 3 May 2011 - Very simple way of installing Custom Thunderg Recovery
Update - 3 May 2011 - Added Simplified Guide to Root & install Custom Recovery on P500
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
FnH84 said:
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
Click to expand...
Click to collapse
Have you installed the drivers for the phone on your computer? If you haven't, your phone will not be detected when toggling usb mass storage.
saileshchowatia said:
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Click to expand...
Click to collapse
Did you read the thread I have linked to at the end of the article? it may help you.
FnH84 said:
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
Click to expand...
Click to collapse
The procedure for downgrading the firmware is included in the article. The procedure is the same for installing any version of original firmware on the phone.
Procedure to change from one custom rom to another various with each rom.some may need a wipe while others might need repartitioning your sd card.
victortangocharlie said:
Have you installed the drivers for the phone on your computer?
Click to expand...
Click to collapse
Yes. It worked fine before. I tried to flash with CM7, and something went wrong. The whole SD-card is empty, works on another phone though. However, Windows will not recognize it no matter what I do
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
victortangocharlie said:
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
Click to expand...
Click to collapse
Both. I put the memory card on another phone and it said it was empty. Also, custom recovery says it's empty and from mount menu, I can see it keeps unmounting.
Have you tried another card on your phone?
victortangocharlie said:
Have you tried another card on your phone?
Click to expand...
Click to collapse
I managed to get the card work via another card reader. I put the zip files on it and trying again now. Hope it will work.
EDIT: It works!!!
nvm.....................
Glad to hear it.
Sorry for noob question, but after downgrade to 2.2, root, can I flash any rooted 2.2.1 ? And is there any?
Once you have rooted your phone, you can install any custom rom meant for p500. This includes all android versions. And, you don't have to apologise for being a noob, this thread is meant for noobs primarily. everyone has to start someplace. There are many rom's accessible on this forum including android versions 2.2 to 2.3.3. I suggest you try Nessy#Euridice ROM by Dookmatt. I am using it and it is easy to set up.it is based on android 2.2.2
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Guess, you will have to ask the people who make the rom's. I don't know about the cm7 rom.haven't used it myself.
IFLPI said:
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Click to expand...
Click to collapse
rooting a stock Rom is hard where as as rooting a custom made rom is easy because u only need the framework to create ur custom rom....
and about CM7 u can choose between many flavours.... its upto u ..
hi
hey man thanks for the wonderful tutorial!!
i just broght my phone 2weeks back. got it after lots of requests to dad!!
i wanna try all the stuff but im damn scared if i would brick my phone..
although i have the exact same phone as yours..unbranded indian optimus one with v10c
should i try it or is there a risk that ill brick it..?
if i brick it.. is there a chance that i can get it repaired? or will the lg ppl refuse to support me because i screwedwith it??
thanks in advance!!
UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.
rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.
electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem
Awesome!
ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.
boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP
bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium
chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294
electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?
[Resource/DevTools] TheCollectiveHelpPackageSCH-i800[everything you need & some]72813
{
"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"
}
TheCollective SCH-i800 Help package
http://wiki.cyanogenmod.org/w/P1c_Info
---------------------------------------------------------------------------------------------------------------------------------------------
TheCollective is Proud to present to you StockRooted-sch-i800 Verzion Galaxy Tab
For what ever reason we all need to get back to the default factory state.
soft brick
resale
loss of stablity
to name a few.
Here are the steps you will need to take.
First let's point out that this package contains EVERYTHING YOU NEED for this Except the windows PC to which it will be used on.
Before we begin Install Samsung usb device drivers located in the package.
**\tools-resources\drivers
Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
next is unpacking Hemdall 1.3.2 (The only one that worked for me on my SCH-i800)
**\tools-resources\Heimdall\
heimdall-suite-1.3.2-win32.zip
But here is a link to the developers page so you can download the original/newer if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ 2012 32bit [if 2013 32/64bit has already been installed you will need to remove it first to install 2012]
This needs installed on your machine because it has .dll files Heimdall uses.
**\tools-resources\MicrosoftC++12\
vcredist_x86.exe
Now you will need to install the drivers this is also needed for Heimdall.
unzip heimdall and go into the drivers folder where you will see /zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says, eg genirc serial device) (tho NOT massStorageDevice)
[good idea to remove any other usb devices as they can and sometimse do interfere with the packet data sending/receiving]
Click the button "replace driver" and let heimdall download/install the drivers. {libusb0 is the one that worked for me, but try another if it dont for you, there are three}
Run Heimdall-Frontend.exe as admin
Files provided To Flash Your Tab with
**\TheCollective-StockRooted-sch-i800.tar.gz >--TheStockRooted 2.3.5 that came on your tab.
**\tools-resources\HumberOS\heimdall-uses
boot.img >-- a CM10.1 kernel with TWRP for sch-i800
recovery.bin >-- CM10.1 twrp for sch-i800
if you need the pit file --> my-sch-i800.pit [extract it from the stock tar gz]
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder "Heimdall" and start " heimdall-frontend.exe" as ADMIN
4: Set up the file you are about to LoadPackage tab. [It should look something like image.]
5: After you have the file in place click load, it will change tab to flash with files listed, simply click start to flash.
ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
Tab should boot. [if not factory data reset in recovery e3 and reboot]
Click to expand...
Click to collapse
After this is should be just like you took it out of the box, and already rooted.
Hope this helps!
---------------------------------------------------------------------------------------------------------------------------------------
If you wish to unroot I've included SuperOneClick shortfuse.
just hit unroot
If you wish to install CM or other AOSP rom here is some helpfull info.
Heimdall command line
Flash boot.img with heimdall command line like this:
Press Power + VolDown untill you get the Download screen or PC <–> Tab screen.
on PC open CMD prompt in the folder of Heimdall and place boot image in same folder
type this command string:
Code:
heimdall flash --kernel boot.img --recovery boot.img
Or just replace boot.img inside the ROM ZIP with your desired kernel.
*TIPS
In case you get any strange symptoms.
Flash full TheCollective-StockRooted-sch-i800.tar.gz (with repartition) via Heimdall.
Flash the Kernel included in the package using the heimdall command above.
Boot directly into CwM Recovery, holding Power + VolUp.
Flash CM10.1 ROM, if it reboots by itself repeat the step above.
If you want Google’s stuff, flash latest GApps for Android 4.2.2.
Only Reboot after everything.
Wrong MAC? Wrong IMEI? Try restoring files from /sdcard/backup/efs*/* to /efs/. If you don’t have a backup, then start over with FULL Restock, and next time save your backup/efs folders, which are created everytime you install CM10.1.
Market problems? Clear Google Services Framework data and reboot.
No touch? That means you got the wrong kernel installed. A couple of builds had problems identifying the exact model. Just flash your kernel through recovery or heimdall / odin.
No boot? Stuck at the SAMSUNG logo? Flash the correct kernel using Download Mode using heimdall!
Deep Sleep not kicking in? Try wiping cLock’s data or freezing / removing it (com.cyanogenmod.lockclock).
--------------------------------------Highlights of What you get inside---------------------------------------------------------------
**\TheCollective-StockRooted-sch-i800.tar.gz
The Heimdall package
**\tools-resources\drivers\Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Samsung Mobile Drivers for usb
**\tools-resources\Heimdall\heimdall-suite-1.3.2-win32.zip
Heimdall
**\tools-resources\HumberOS\heimdall-uses\boot.img
CM10.1 humberOS Kernel P1c
**\tools-resources\HumberOS\heimdall-uses\recovery.bin
TWRP Touch Recovery 2.5.0.0
**\tools-resources\HumberOS\CwM_CM10.1-humberos_kernel_p1c-20130715.zip
CM10.1 humberOS Kernel P1c
**\tools-resources\MicrosoftC++12\vcredist_x86.exe
Microsoft C++ redisturbutial
**\tools-resources\ODIN-1.7\
Odin3 v1.7.exe
If you need it for modems or kernels
**\tools-resources\PartitionTool4microSD\pwhe8.exe
if you get encryption failed, you might find this usefull to partition your external sdcard [deeper instruction online at rootzwiki]
**\tools-resources\SuperOneClick\SuperOneClickv2.3.3-ShortFuse.zip
unroot/root what ever just good to have hard to find
DOWNLOAD
MD5 Sum: F0F9C9FA54219EDFA50E85163D9A7C54
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
robjective said:
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
Click to expand...
Click to collapse
F0F9C9FA54219EDFA50E85163D9A7C54
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Cellulah said:
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Click to expand...
Click to collapse
I had the some problem. Tried it at work with FF, Chrome, and Free Download Manager and all would fail at some point after about 2/3 done.
Came home and tried and got it first try.
tinpanalley said:
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Click to expand...
Click to collapse
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
I'll try again. The download was fine but I suppose I could try again.
No use.. same error every time . Tried with each driver as well. All I get is this:
tinpanalley said:
No use.. same error every time . Tried with each driver as well. All I get is this:
Click to expand...
Click to collapse
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
Windows 7, 64-bit
Intel i5-2400 3.10 GHz
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
tinpanalley said:
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
Click to expand...
Click to collapse
Yes. I had same issue on my captivate trying to restore stock from a cm7
To fix I had to flash in the kernel and recovery from cm and in cwm under advance mounts format data. Back then on that device speedmod kernel allowed users to select format method (fat32/ext4/etc)
But also hemidall should format with the repartition. But that is assuming it can read and mount the partition.
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Click to expand...
Click to collapse
I did try this but I still get the crash of heimdall.
Also what does "mount and format data" mean? I can format data, system and cache but I don't see "mount" at all.
The Collective DL Fails
So I am trying to download the package that is for this which would be most helpful for me as I'm trying to help out my pastors wife with her Galaxy Tab, I started the download and it got all the way up to 144MB and quit, and file won't work.
Is there somewhere else that you can put it so we can try downloading from there? Can I give you my dropbox and you can drop it in there?
Again just to say I don't have a problem with HEIMDALL I have a problem downloading your link for the files needed for the flash.
I would really like to try to get this working for her as I've been looking around for a solution for this thing for about 2wks already and its been blowing my mind.
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
chi_tilt said:
So I am trying to download the package that is for this which would be most helpful for me as .......
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
Click to expand...
Click to collapse
Try a direct download link
http://www.theandroidcollective.org/i800/public/TheCollective-HelperPackage_sch-i800.zip
Sometimes download errors like yours seem to happen when the user is behind a proxy.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
No 3G with alroger's latest kernel
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
arielja87 said:
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
Click to expand...
Click to collapse
Easiest way is to tar the modem.bin and Odin it into the device.
Load it into the phone slot
Sent from my GT-P5110 using Tapatalk 4
Help to download...
Hi... I have tried many times to download the package (TheCollective-RootedStock-Odin-sch-i800.tar.md5) but I can not , the download starts fine, but not complete!.
If you could upload to another server like 4shared, mediafire, dropbox... I would be very grateful..
Still not working as it should
So I have downloaded the package finally and I Have done all the steps according to your writeup. Still doesn't give me a fresh startup on the tablet, I still get many error popups and also all my apps are still there.
What could I be doing wrong? Could there be something wrong with the tablet?
Any help on this would be great, as I'm dumbfounded on this already.
Thank You
Lem
HARD BRICK NO MORE!!! Asus ZenPad S8.0 Fix
I made the sad retarded mistake in updating a manual zip file thru CMW... I know retarded... anyways this caused the tablet to Hard Brick bootloader only with very little options, you might even have your serial number showing up as all 1's.
Usually this isn't a big deal sadly this tablet gets little to no love on the internet it seems... This is a guide to help anyone un-brick their tablet
Step 1. First this is more of a windows 10 issue than anything but some driver installs thru the Asus Flash Tool might fail.. something to do about Driver Certificates, so you'll want to disable that on your Win 10.. here a tutorial link for more youtube link HERE
Step 2. Installing the proper Drivers if you haven't already, which will all be in this zip folder HERE
Make sure you installed the ADB-Setup | Intel Android Drv Setup | Asus Android USB Drivers | Asus Flash Tool Installer 1.14
Step 3. Next you'll want to download the .raw file for the ZenPad can be found HERE
Step 4. Open your Asus Flash Tool Installer, boot up your device in the boot mode. (Hold Down the Volume Up + Power ) till you see a little android man with a hardhat.
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .raw file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
{
"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"
}
Now you may still get on a bootloop when it restarts, if that happens simply again restart in boot loader screen and do a hard reset and you'll be good to go! Afterwards just throw that new Marshmallow update in the internal and restart .. and you'll device will ask if you want to update now u got your tablet back and Marshmallow!!! I hope this helps if you have any troubles with the links, images please feel free to let me know pm or reply to this post!!! Best of Luck!
.RAW File was provided by Portzebie! Thanks again bud!!
Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.
tfq535 said:
Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.
Click to expand...
Click to collapse
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessary but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.
portezbie said:
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessar but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.
Click to expand...
Click to collapse
Thanks again, it worked like a charm.
bert_747 said:
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .img file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
Click to expand...
Click to collapse
Thanks for the guide.
The link to your screenshot is missing.
PMikeP said:
Thanks for the guide.
The link to your screenshot is missing.
Click to expand...
Click to collapse
Sorry bout that, screen shots should be working.
a little question,
is it possible to get xfstk files to restore a corrupt bootloader?
thx,,,
ASUS Flashtool doesn't start flashing
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong
These instructions do not work for Ubuntu. I find it very hard to believe that there is only a Windows version of the flash tool available.
Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.
Yes you can upgrade
Servaas said:
Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.
Click to expand...
Click to collapse
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.
Servaas said:
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.
Click to expand...
Click to collapse
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work
edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
edu47 said:
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work
Click to expand...
Click to collapse
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.
Servaas said:
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.
Click to expand...
Click to collapse
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.
edu47 said:
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.
Click to expand...
Click to collapse
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.
Servaas said:
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.
Click to expand...
Click to collapse
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/
edu47 said:
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/
Click to expand...
Click to collapse
This zip file also doesnt register, nothing pops up and no, when pushing the update button it also does nothing.
It would seem that the OP provided a nice 5.0 raw file that renders your tablet un updateble.
I'll be returning this tablet and going for the only available option in the netherlands the samsung 8 incher.
Z580C tablet is bricked, it happened on update, I think battery was too low. Screen is black all the time, under windows device manager it connects as other devices, MOOREFIELD device with no drivers and I can hear from windows sounds that it reboots after some time. All post #1 drivers are installed.
Please help.
Thank you
magnus_bn said:
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong
Click to expand...
Click to collapse
Had the same problem and what I did to make it work was.
1. Lunch Asus Flash Tool
2. Connect device in download mode (volume up + power)
3. Wait for device to be visible in Asus Flash Tool ( Serial number + blue dot) - you may need to restart tablet using reboot droidboot
4. Select model number
5. Point to raw file and choose to erase data (accept the prompt )
6 Hit Start
What I also did prior to that was factory reset of tablet
hope that helps you