[GUIDE] Easy upgrading your i9000 from 2.3.6 all the way to 5.1.1! [Updated 12.07.15] - Galaxy S I9000 Q&A, Help & Troubleshooting

{
"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"
}
I decided to write this quick guide to condense what took me the better part of 8 f**king hours trying to do. The time it took was probably due to a mostly faulty USB port on the phone, AND on my laptop too...
Long story short, I was given this phone after my S5 decided to go for a swim with me. My first Android phone was the Galaxy S+. I then upgraded to the S2 -> S3 -> S4 and thus S5.
I had never used the regular 'S' (non '+' version) before today and sadly there is little support for it. So I thought I would add my first and last guide here on how to get this phone all the way from Android 2.3.6 (latest stock official) right up to 5.1.1. I owe a lot to XDA, so this is my way of helping out. This phone unfortunately is OLD, and thus requires outdated methods of flashing/upgrading that I was not very familiar with. Hopefully this will help you save a lot of time.
It is important to note that not all of these steps will be mandatory! I will try and mark the ones that I don't think are mandatory (and that you may skip). However I will just outline the full steps I took.
First you will need this package that I am going to upload here. Feel free to make as many mirrors as you want.
My apologies in advance if I do not have permission to upload copies/etc. of these files but AFAIK I am allowed to upload these files.
Code:
Files:
https://mega.co.nz/#!PU0xkbrJ
Key:
-Mwl7Ga-FAqAenVC9MDoOadYA0RTcDskQSsKFggZaVM
What we are trying to accomplish!
If needed, downgrade/upgrade your i9000 to Android 2.3.6. This is the latest stock Android version released for this phone. Doing this should fix any corruption issues or any other BS that you may have done to your phone. This still may not be necessary at all.
Install the Semaphore_2.7.4 Kernel & Recovery package (bundled). This is the best Kernel for your i9000 and it also gives you the most stable working Custom Recovery I have found. (I have tested TWRM, CWM & PhilZ and found this bundled CWM to be by far the best (and in this case the only thing that worked for me)).
Flash whatever new Custom Rom that you want. You can flash any firmware even up to 5.1.1 currently.
So let's do this quick, so you don't have to waste 8 hours like I did yes? Hopefully you don't have malfunctioning USB ports like I did too.
Step 1. - Download the file package above.
Step 2. Uninstall Kies if you have it installed. Then reboot your computer. (Step may not be mandatory but I did it)
Step 3. Run the "USB_Drivers_1.5.49.0.exe" installer from the "THESE FIRST" folder. Then reboot your computer again.
Step 4. Put your i9000 into DOWNLOAD MODE (Volume Down + Home + Power) and plug it into your PC. It should be detected, and Windows driver install popup will show up etc.
Step 5. Run "Odin3 v1.83.exe" and hopefully you'll see it connected in COM "X". If not, then try and sort out the driver/cable/port issue. Try another USB port, and don't use any HUBs etc.
Step 6. Extract the "I9000XXJVU CFROOT.rar" and put the contents somewhere. Put the largest file in PDA, the CSC file in CSC and the remaining file in MODEM/PHONE (this is all in ODIN (also we are ignoring the CFROOT file))
Step 7. Hit start and wait. (You may need to add the s1_odin_20100512.pit file in the folder to the PIT section in ODIN if it won't flash. (I didn't have to)
Step 8. Wait for your phone to reboot into old Android 2.3.6. Then shut it down, because we are going to upgrade it AGAIN now that it is fully stock.
Step 9. Boot into download mode AGAIN and connect to your PC.
Step 10. Open up an ELEVATED CMD Prompt (With Admin Privledges) and navigate to the "THESE SECOND\Heimdall Suite + Kernel" folder. Using the command "cd <yourfilepath/Heimdall Suite + Kernel folder>"
Step 11. Run the command: " heimdall flash --kernel zImage --no-reboot " (without quotes). You may have to make the 'kernel' part of the command in CAPITAL letters, for it to work.
Step 12. If (AND ONLY IF) you get an error -12 or something. Then go into the folder "Driver Change For Kernel Flash" and run the "zadig.exe". Choose Options > List all Devices > Serial/etc/device and try one of the 3 drivers and click Replace/Reinstall etc. Then try step 11 again. Keep trying with each driver until it works. <--- THIS STEP ONLY IF STEP 11 DIDN'T WORK THE FIRST TIME!!!!
13. Reboot your phone into RECOVERY MODE! (Volume Up + Home + Power).
14. Wipe Data (Factory Reset). Clear Dalvik etc. etc.
15. Flash whatever .zip of the new ROM you want baby!!
Edit: Here is a second set of instructions that may help with the Heimdall part!
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Note, that I flashed the unofficial OMNI from here (it's Android 5.1.1. and it works beautifully) My thanks to humberos + others:
http://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rom-t3054101
It asked me to reboot recovery many times and complained with a bunch of errors but basically you just ignore all of those errors and keep rebooting and flashing the same .zip again. Eventually you won't see those errors any more at all and the rom will flash flawlessly with the included Aroma/TWRP etc. and voilá! You will have upgraded your old i9000 from 'x' firmware to 'y' firmware (hopefully better). Congratulations on breathing life back into your i9000! Galaxy S! Now you can give it to your mum or something!
Please just hit 'THANKS' if this helped you. I don't need any more, or any less.​Edit: Added some pictures for proof that this works.
The attached CMD picture is what it should look like when the command executed properly and the Semaphore_2.7.4 Kernel was installed. Also it shows the error I got in Step 12 before I used the driver program to change the libusbx drivers so I could flash it properly.
The other pictures show how the installation process looks for Unofficial OMNI ROM, including the Boot logo, and the top image is just a readout of the 'About Device' pane.
========= QUICK FAQ: =========
Q Can I PM you for help?
A: I'd rather not. I don't use the forums much. Post here and maybe I or others can help you out. Also check the README.txt files in the package you downloaded.
Q: The files aren't available any more, can you reupload them?
A: Maybe, ask in the thread. Everything in the package was downloaded from other places: Old 2.3.6 Firmware from Sammobile + Kernel from the above Wiki link etc. Heimdall from Google.
Q: Does this work for the i9001 (Galaxy S+)?
A: Probably not. Try it yourself at your own risk.
Q: Does Wi-Fi/Something else work?
A: Wi-Fi does, see the top picture. As for other stuff, I don't know, try it for yourself and see!
Q: I prefer using TWRP Recovery for this phone an-
A: I don't care. I tried 4 other custom recoveries and none of them worked except the one I listed.​

Hallo I have a galaxy s2 model i9100 which was on stock official android 2.3.6 gingerbread and I upgraded it to CWM 12.1 ANDROID 5.1 Custom rom....and then got these bugs.....
1.....the BACK button, OPTIONS button dont work...also the MENU/HOME [middle] button works as back button. .....its not a hardware problem coz they worked very well on Gingerbread the previous rom
2....when I call some one...he doesnt hear me and I also dont hear him....its the same issue when I activate loud speaker or insert HEADSETS.....
ITS NOT A HARDWARE PROBLEM because things were working well when on official android 2.3.6 stock......and also all the speakers work well on other apps....also, people dont hear me during calls and yet the mic WORKS VERY WELL FOR VOICE and VIDEO RECORDING FOR OTHER APPS including camera and voice recorder.....BUT STILL PEOPLE DONT HEAR ME DURING CALLS......
I then took it back to official android 4.1.2 jellybean AND I STILL HAVE THE SAME ISSUES......STILL THE BUTTONS DONT WORK and also i dont hear people during calls and they dont hear me either......PLEASE HELP ME...this is a software problem.....I have tried factory reseting the phone and wiping all data on phone and still the same issue. ........AM NOT AN EXPERT TO ANDROID
THANKS....
[email protected]​

Related

[Q] Neeed Halp with rooting samsung galaxy s vibrant on bell

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

[REF][GUIDE] How to: update firmware with CWM app and clockworkmod recovery

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

[Q] Market Problem..

Hi
I deleted some programmes on my rooted TAB
Cant recall exactly what
Now Market fails with message 'The application Market (process com.android.vending) has stopped '
I deleted the cache but still it wont work
Can I restore the tab to an earlier date?
Can I somehow restore missing files?
PLEASE HELP need basic instructions as no expert
zalanz said:
Hi
I deleted some programmes on my rooted TAB
Cant recall exactly what
Now Market fails with message 'The application Market (process com.android.vending) has stopped '
I deleted the cache but still it wont work
Can I restore the tab to an earlier date?
Can I somehow restore missing files?
PLEASE HELP need basic instructions as no expert
Click to expand...
Click to collapse
Hmm... if you knew exactly which apps you deleted, you might be able to find them in another ROM and just adb push them back to the tab.
Otherwise, at this point, I would suggest a re-stock (take the tab back to factory settings via re-flash).
Which tab do you have exactly, and what Android OS were you running? For example, I have a Galaxy Tab 7" P1000 GSM (T-Mobile) and I used to run Gingerbread (2.3.3)
thanks
mine is a Galaxy Tab 7" P1000 GSM (ORANGE) on Gingerbread (2.3.3)
I know I uninstalled z4root but honestly cant recall what else.
How easy is it to restore?
Not sure how I reflash it?
Hmm, I'm not too sure if you need root or not to do an adb push, but it's pretty much:
Download app to computer, plug tab to pc, open cmd and do adb push FILE.apk
You'd need android SDK though prior to that and platform tools.
As for re-stocking, you can either use Odin (samsung's phone/tab flashing tool) or Heimdall (open-source flashing tool). In any case though, Team Overcome made a nice guide for restocking that should work with Odin.
http://forum.xda-developers.com/showthread.php?t=1317384
In short, you want to have Samsung's drivers installed, reboot your tab and put it in download mode, download the files needed to re-stock from that thread, open Odin, enter the gt-p1000 pit for pit, GB-stock-safe-v5.tar for the pda, and a modem for modem, then start flashing
I also made a nice guide involving Heimdall re-stocking here: http://forum.xda-developers.com/showthread.php?t=1508703
wow
bit too complicated for me I am afraid.
I am grateful for your reply, but I could not do that.
Looks like my TAB is useless now
It's not really too hard I'd hate to see your tab useless though.
If you had some sort of instant messenging service, I could maybe guide you through the process
thanks but I do not use Instant messaging.
@yyalanyy on twitter is all, but doubt tht could help?
If you could email me any simple [and I mean simple] help to [email protected]ltrans.co.uk I would be very grateful.
I can make you a package zip that will pretty much only require you to install drivers and then run 1 file (I can give you a small walkthrough on how to setup the drivers in email)
It'll take me a little bit to upload it though (I would say 40mins :/). Otherwise, if someone else feels like offering some simple instructions, feel free to do so
That would be great
many many thanks
Actually, download this: http://www.rosanoscorner.com/p1000/downloads/GB-Stock-Safe-v5.zip
And i'll upload my batch file in a bit. You'll just have to extract some things though
---------- Post added at 12:35 AM ---------- Previous post was at 12:16 AM ----------
Here's a guide (it's a bit long, but the steps are really quick)
- You'll also want 7zip installed (WinRAR might also work if it can open .tar), it's a free program for unzipping archives
1. Download that .zip file above and unzip somewhere
2. Download my archive here and unzip somewhere: http://www.mediafire.com/?pdpy59z6bdej6wb
3. In my folder, there is a Drivers folder, go in it
4. Run SAMSUNG_USB_Driver_for_Mobile_Phones (if it says drivers are already installed, then close it)
5. Reboot tab into Download Mode (shut it off and unplug from charger/computer, hold Vol-Down button and power)
6. Plug tab into computer
7. Go to the Drivers folder in my folder and open zadig
8. Options > List All Devices
9. Select Samsung USB Composite Device
{
"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"
}
10. Hit Install Driver (accept any prompts you see about unsigned drivers)
11. If it's successful, close it
12. Unplug tab and plug it back into computer (on the same USB port)
13. Go to the folder you extracted GB-Stock-Safe-v5.zip at
14. Find the folder called JPZ Modem (for anyone else following this, use the modem of preference)
15. Go into it, take the modem.bin, put it into my folder (my folder with the .bat and heimdall stuff)
16. Go back to the GB stock folder
17. Open GB_Stock_Safe_v5.tar (7-zip should open this like an archive)
18. Drag every file in that .tar to my heimdall folder
19. Run flash.bat in my folder
20. Do not do anything with the tab until it's done
21. Once the tab is done, you should be in recovery. You have to (i think) use the volume buttons to scroll up and down in the menu, but you have to wipe data, and then reboot to system
22. Done
I'll be here if you need any help still
hi
i have followed your instructions. when I run the flash,bat a cmd window opens, tells me to press any key but nothing happens?
zalanz said:
hi
i have followed your instructions. when I run the flash,bat a cmd window opens, tells me to press any key but nothing happens?
Click to expand...
Click to collapse
Hmm, it should be starting Heimdall and starting a 1-2min flashing process. Not too sure why it wouldn't actually work though
Try running it again and then when it says press any key, Right-click anywhere in command prompt > select all, and then when everything is selected, press Enter. Then copy/paste that into a post here
C:\Users\alan acer\Desktop\helpsamsung\Re-stock (Heimdall)>heimdall flash --repa
rtition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryf
s factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --sec
ondary-boot Sbl.bin --kernel zImage
C:\Users\alan acer\Desktop\helpsamsung\Re-stock (Heimdall)>pause
Press any key to continue . . .
its approaching 1.00am here so I must get some sleep.
Thanks for your help
I will have another try tomorrow
Thanks you
Hmm, how many files are in your Heimdall folder and how big is the folder? I think you should have about 15 files in the folder total, equaling 391MB
Edit: Just saw your message about you heading to bed, night
think thats the problem.
After using 7zip on your download there are only 6 files totalling 28mb ?
Hi
Tried it again and it worked!
So pleased thank you for all of your help
Problem now is different as it is now NOT rooted.
and it seems very laggy now.
I have tried Z4 root and it fails
I have tried superone click and that fails at stage 6
Any ides?
Would it be best via ODIN?
Hmm, thought I hit reply earlier but guess not :/
Anyway, with Odin, the only thing that is different is that it automatically wipes data/factory reset and wipes internal SD instead of you having to manually do this. Generally, Odin is slower as well too, but it does work
As for Root, hmm, not too sure what can be done about this. I can't recall me actually rooting Gingerbread (maybe someone else can shed some light on this?) I always flashed a custom ROM right after I re-stock, and most (if not all) custom ROM's offer Root instantly
No worries. At least my tab is useable again now. I would once again like to thank you for the help and time that you have given to me.
Sent from my GT-P1000 using Tapatalk
zalanz said:
No worries. At least my tab is useable again now. I would once again like to thank you for the help and time that you have given to me.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
No problem

[ROM][GT-P7510][WiFi Only] Speckfree ROM (Honeycomb 3.1)

This is a project of mine to create near-clean ROMs for the GT-P7510 Galaxy Tab. This is my first ever ROM. If you have any feedback or requests, I'll read it if it's posted as a reply.
This ROM is based on the Honeycomb 3.1 OTA for the Galaxy Tab 10.1 Wi-Fi. This version removes some components; next version which will be version 1.1 will remove more if I missed any.
The Regular Edition removes Samsung's bloatware apps.
The Plus Edition removes most of Google Apps, except for the market so you can still get apps from there.
I am not responsible if something breaks, related to the tablet or not.
Before you flash a version of this ROM, you will need the following:
ODIN 3 (if you don't have ClockWorkMod)
ClockWorkMod (if you don't have ClockWorkMod)
Samsung USB Drivers (if you don't have ClockWorkMod, or aren't downloading the ROM via the tablet)
One of the ROMs at the end of this post
At least a half hour of battery power.
Follow these instructions if you don't have ClockWorkMod, once the ROM is on the tablet:
1. Extract ODIN into a new folder.
2. Extract ClockWorkMod into the ODIN folder.
3. Start ODIN.
4. Click "PDA" and select the ClockWorkMod file.
5. Turn off your Galaxy Tab 10.1.
6. Plug your tablet into your computer.
7. Turn on your tablet, pressing the Power and Volume Down buttons.
8. Press Volume Up once the two icons appear. It will auto-select the right icon. Press Volume Down if the left icon is selected.
9. It will ask for confirmation. Press Volume Up.
10. It will then connect to the computer. Press Start on ODIN. Do not remove the cable as it is overwriting the recovery!
It will automatically reboot after it finishes the process. The remaining parts don't need the computer.
Now that you have the ClockWorkMod recovery, follow the instructions in the next section of this post.
Installation Instructions with ClockWorkMod installed:
1. Shut down your tablet.
2. Turn it back on, holding down the Power and Volume Down
3. Press the Volume Down button to select the recovery option. Press Volume Up to select.
4. Select "install zip from sdcard" using the volume buttons, selecting using the power button.
5. Select "choose zip from sdcard" using the volume buttons, selecting using the power button.
6. Locate the file you copied to your tablet, and select.
7. Select Yes to start the process.
8. Once the install finishes, you'll be at the main menu.
9. Select "Wipe Data/Factory Reset".
10. Confirm, and it will wipe /data and /cache.
11. Select "Reboot System Now".
12. It'll go through the setup process as normal.
Regular Edition Changes:
Rooted.
Deleted:
Amazon MP3
Bluetooth Test
CSC
Factory Test
Kindle
LCD Test
Music Hub
Pulse
QuickOffice
Samsung Apps
Polaris Office
Service Mode App
Weatherbug Tablet
WLAN Test
Plus Edition also Changes:
Removes:
YouTube
Google Books
Street View
Google Talk
Google Mail
Quick Search Box
Voice Search
Maps
Links are disabled.
Awesome... Will give this a run... Thanks!
!!!!!??????????????!!!!!
so ummm... dude.... what are you posting here? there are no installation instructions and your file system in the zip you provided looks like some sort of really messed up nandroid backup. this is a horrible thing to do to others considering they are going to try and flash in CWM. whats going on here??? im not trying to be hard on you because i know this is your first rom. but with your OP in conjunction with the files you've provided it's just asking for trouble. you really shouldn't be posting things like this bro. it's dangerous.
What is this???
{
"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"
}
task650 said:
so ummm... dude.... what are you posting here? there are no installation instructions and your file system in the zip you provided looks like some sort of really messed up nandroid backup. this is a horrible thing to do to others considering they are going to try and flash in CWM. whats going on here??? im not trying to be hard on you because i know this is your first rom. but with your OP in conjunction with the files you've provided it's just asking for trouble. you really shouldn't be posting things like this bro. it's dangerous.
What is this???
Click to expand...
Click to collapse
Saw that as well after downloading and didn't flash...
task650 said:
so ummm... dude.... what are you posting here? there are no installation instructions and your file system in the zip you provided looks like some sort of really messed up nandroid backup. this is a horrible thing to do to others considering they are going to try and flash in CWM. whats going on here??? im not trying to be hard on you because i know this is your first rom. but with your OP in conjunction with the files you've provided it's just asking for trouble. you really shouldn't be posting things like this bro. it's dangerous.
What is this???
(image removed for brevity)
Click to expand...
Click to collapse
I'm in the process of uploading the CWM-flashable zip without the other two files (ODIN and CWM itself) now. I've added instructions as well. I assumed others would understand what I was doing... :/
Thank you for your feedback on my packaging (and my total lack of instructions).
raqball said:
Saw that as well after downloading and didn't flash...
Click to expand...
Click to collapse
The speckfree-1.zip file is the image. I brought down the original file, and that file will be the sole download from now on.
aroni125 said:
The speckfree-1.zip file is the image. I brought down the original file, and that file will be the sole download from now on.
Click to expand...
Click to collapse
I understand that but I downloaded to Tablet and had I not opened the zip and had just flashed in CWM it would have been trouble...
I will DL again and test it out for you..
Thanks, welcome, and best of luck!
Sent from my swiper using xda premium
aroni125 said:
I'm in the process of uploading the CWM-flashable zip without the other two files (ODIN and CWM itself) now. I've added instructions as well. I assumed others would understand what I was doing... :/
Thank you for your feedback on my packaging (and my total lack of instructions).
Click to expand...
Click to collapse
Just a thought.... you forgot to say you're not responsible if folowing your guide kills the family cat.... hey every other ROM says things like that...lol Choice is usually good and improves every ones experience so I wish you luck in this endeavor.
If you can read this it was sent using my GT-P7510.
aroni125 said:
I'm in the process of uploading the CWM-flashable zip without the other two files (ODIN and CWM itself) now. I've added instructions as well. I assumed others would understand what I was doing... :/
Thank you for your feedback on my packaging (and my total lack of instructions).
Click to expand...
Click to collapse
no problem. but expecting others to just "understand" isn't really the thing to do when we have newcomers coming in everyday that don't yet understand a ton of things. so i was just pointing that out basically. even the people who do know what's going on would like to know what and how they need to flash before they waste their bandwidth on a 200mb plus download ya know. good luck.
Benzoman said:
Just a thought.... you forgot to say you're not responsible if folowing your guide kills the family cat.... hey every other ROM says things like that...lol Choice is usually good and improves every ones experience so I wish you luck in this endeavor.
If you can read this it was sent using my GT-P7510.
Click to expand...
Click to collapse
I added a brief message about that when I posted the new links.

Hard Brick on Asus ZenPad S8 (Z580CA) or Z580C

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

Categories

Resources