Database Develop

[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

[GUIDE] Easy upgrading your i9000 from 2.3.6 all the way to 5.1.1! [Updated 12.07.15]

{
"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]​

[UPDATED] [FIX] HTC Desire 626g+ update (no command error) fix!

Halo all
Most owners here have rooted (kingroot) their system and attempted to update the rom, forgetting OTA conflicts. Although the consequences are usually resolvable, not in the case of mediatek and our model.
To start, I highly recommend using Ubuntu linux off a flash drive running live, else I suggest using windows 7 (perhaps in a vm too) although it didn't work with me (mediatek driver issues) (users reported that it works fine with windows 10, set wifi connection as metered to prevent automatic driver updates)
Optional: Create a live Ubuntu (download the 64bit version!) stick using this tut: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
After booting into Ubuntu, remove modemmanager by typing in terminal : sudo apt-get remove modemmanager
Hit y and continue...
Download folder list:
1)spflashtool from http://spflashtool.com/, "Linux 64-bit"
2)CWM(626g+)
3)Scatter file(626g+)
4)Stock cwm backup ~800MB
Link to Download: me1ga.nz/#F!t1A1HJQJ (rename to "mega")
Decryption key:
Code:
!teT23YQ_1PH52USChW3k6g
Google drive mirror folder: https://drive.google.com/folder/d/0BwgllNFqdXuQMXR0a29mZms2VDA/edit
Skip 1,2,3 for Windows users
Flash time:
1)Extract the zip in Home directory, open Terminal again then cd SP_Flash_Tool_exe_Linux_v5.1520.00.100 (tip: type cd SP then hit tab to autocomplete)
2)then: chmod +x *
3) last: sudo ./flash_tool.sh
4)Choose the scatter file and recovery img downloaded like in the pic (checkboxes too):
{
"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"
}
5)Make sure your phone is off, click Download then plug in the phone using a USB2 port...
6)CWM installed!
7)extract the stock cwm backup zip to sdcard in this following order of directory: clockworkmod/backup/(the extracted contents here)
8)Reboot the phone by hold Vol Down + Power then leave it, due to the issue it will enter cwm automatically
9)navigate to "backup and restore" and choose restore then the folder your copied (in date format)
10)reboot, dun! :highfive:
Big Credits and thanks to: https://www.facebook.com/htc626gplusdev/info/?tab=page_info , for custom recovery...
Hit thanks if this has helped you, would motivate me to update the links lol

Hi, this is to install the cwm recovery... Right? But how do i flash my phone with an HTC stock rom? Because i don't have a back up to restore my phone. And htc already has a default recovery. Can't i use that to flash my phone with the stock rom file? Maybe via adb sideload?

diml0rd said:
Hi, this is to install the cwm recovery... Right? But how do i flash my phone with an HTC stock rom? Because i don't have a back up to restore my phone. And htc already has a default recovery. Can't i use that to flash my phone with the stock rom file? Maybe via adb sideload?
Click to expand...
Click to collapse
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...

tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
Sorry i though your link was an update to cwm, not the rom. Just saw the size of the file. Thanks i will try this. This is what I was looking for actually. Too bad i just deleted my arch Linux though ??

tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
can't download :
https://www.dropbox.com/sh/1oev7ymmh...mXInVs_va?dl=0
returns:
This account's public links are generating too much traffic and have been temporarily disabled!

diml0rd said:
can't download :
https://www.dropbox.com/sh/1oev7ymmh...mXInVs_va?dl=0
returns:
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse
Link updated

Hello, sorry, I have the same problem my phone is 626g, I do not know if this guide is, however, the link ww w.dropbox.com/s/drc102llim...atter.txt?dl=0 and the link:w.dropbox.com/s/wt0r1q8xqs...71609.img?dl=0[/url] not working.
Thank you there is nothing about this problem and service HTC wash their hands with this.

tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
sorry but the other two links are broken as well. i have the STOCK CWM.zip now

Hello again, I found the scatter file. But when you download and plug the USB, I get the following message.
PTM changed for ROM; it must be downloaded
Any help please? I read that this was solved by selecting all + download format rather than just download, but I have some fear in doing this.
Cheers
---------- Post added at 10:13 PM ---------- Previous post was at 09:53 PM ----------
Yes, unfortunately we need these files that are not found anywhere. They would be so kind as to re-upload?
Thank you
Cheers

I've been looking for 3 days and there is no way you're tpr0 alone gives a solution, could you please reupload the files? I am eternally grateful. Thank you very much Greetings.

reprono said:
I've been looking for 3 days and there is no way you're tpr0 alone gives a solution, could you please reupload the files? I am eternally grateful. Thank you very much Greetings.
Click to expand...
Click to collapse
Ch
Can you please be more specific about which file? Here's how it looks on my side : http://m.imgur.com/wKhtNtQ
I'll reupload to Google drive soon :good:

tpr0 said:
Hello, sorry for late, I'm also surprised why this solution isnt popular as many users faced the same issue
Can you please be more specific about which file? Here's how it looks on my side : http://m.imgur.com/wKhtNtQ
I'll reupload to Google drive soon :good:
Click to expand...
Click to collapse
please upload these files to your google drive folder:
2)CWM(626g+): https://www.dropbox.com/s/wt0r1q8xqs...71609.img?dl=0 (source and developer in the credits section)
3)Scatter file(626g+):https://www.dropbox.com/s/drc102llim...atter.txt?dl=0
---
just saw that you already did! :good: thanks

Any guidelines for people who are stuck with windows?

Thanks this worked but now my phone is being recognised as "HTC Desire 320" and every time I boot up it says incorrect CID

alvi.mahmud said:
Any guidelines for people who are stuck with windows?
Click to expand...
Click to collapse
You can use VirtualBox to boot linux, use ubuntu 14.04 iso as 'cdrom', install guest additions then follow the procedure. ill post a quick guide soon :good:

tpr0 said:
You can use VirtualBox to boot linux, use ubuntu 14.04 iso as 'cdrom', install guest additions then follow the procedure. ill post a quick guide soon :good:
Click to expand...
Click to collapse
Mine worked on Windows 10

ahmedshauq said:
Mine worked on Windows 10
Click to expand...
Click to collapse
It 'should' work on windows, though at certain settings Windows updates the driver with incorrect version. I recomended Linux to avoid problems with drivers

ahmedshauq said:
Thanks this worked but now my phone is being recognised as "HTC Desire 320" and every time I boot up it says incorrect CID
Click to expand...
Click to collapse
Anyone know a fix?

I just tried it with same result. But I also noticed that I can use only one sim now (SIM management in settings is gray) and language is mixed english with czech (my default).

Awaraine said:
I just tried it with same result. But I also noticed that I can use only one sim now (SIM management in settings is gray) and language is mixed english with czech (my default).
Click to expand...
Click to collapse
I can use both Sims though

.backup file

Hello,
So my phone was stuck in bootloop and thus, I created a backup in my SD card. The files are shown as 13 files of 2GB size each with an extension ".backup" Anyone has any idea on how to combine these files and access the data inside on PC. The data is very important. Thank you!

deadmanspeaks said:
Hello,
So my phone was stuck in bootloop and thus, I created a backup in my SD card. The files are shown as 13 files of 2GB size each with an extension ".backup" Anyone has any idea on how to combine these files and access the data inside on PC. The data is very important. Thank you!
Click to expand...
Click to collapse
Crosspost from https://forum.xda-developers.com/t/moto-e4-plus-restart-loop.4241427/
I've had numerous Moto devices and have never seen any backup options in stock recovery., so I haven't any idea what format these are using.

readback stock recovery from SP Flash Tool and flash TWRP. also readback metadata partition (crypto footer). do not unlock bootloader because encryption is bonded to bootloader state. if you are lucky TWRP will work on locked bootloader. TWRP will decrypt your data so you can backup everything

aIecxs said:
readback stock recovery from SP Flash Tool and flash TWRP. also readback metadata partition (crypto footer). do not unlock bootloader because encryption is bonded to bootloader state. if you are lucky TWRP will work on locked bootloader. TWRP will decrypt your data so you can backup everything
Click to expand...
Click to collapse
How to do this? USB debugging and OEM are not ON in my phone. I saw some tutorial on YouTube, but it requires USB debugging.
Can't I use those userdata_*****.backup files?

usb-debugging is another option to access your data (can be enabled in boot.img)
SP Flash Tool is for preloader mode, no usb-debugging required
https://android.stackexchange.com/q/203283

wait, you did factory reset already? in that case crypto footer is reset too. backup is encrypted and therefore useless unless crypto-footer is restored.
you said you restored backup, are you sure? does the phone boot into lock screen like before and is pattern still the same?

aIecxs said:
wait, you did factory reset already? in that case crypto footer is reset too. backup is encrypted and therefore useless unless crypto-footer is restored.
you said you restored backup, are you sure? does the phone boot into lock screen like before and is pattern still the same?
Click to expand...
Click to collapse
Yes, the password is still the same. It's like the phone is again in the same condition with the same issue of boot loop.
I saw some tutorial on SP flash tool and what I did was:
1. Downloaded the SP flash tool
2. Downloaded TWRP recovery specific to my phone
3. Opened flash tool, went to download, clicked on scatter loading, selected the file and then clicked on download and connected my switched off device to the PC via USB
But, nothing happened after that.
My phone started charging, but nothing else happened.
I thought drivers weren't installed, so I went Driver Autoinstaller folders (there were 2 of them) and clicked on Driver Install, but it showed me 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"
}
Then I clicked on finish and it showed this
When I went to the second folder, it showed me this
Is it because of this, that my device is not detected by this flash tool, and if yes, what can I do?

Yes it's driver issue. Disable driver signature enforcement and reboot. open device manager, connect phone and immediately select yellow triangle. install inf manually with let me pick option
you should not flash TWRP without a backup of stock recovery. Do a readback first. Also it is important the scatter file is matching your current partition layout. therefore you should analyze the result. if you are able to extract ramdisk with AIK then you have successfully dumped stock recovery (and can proceed with next step flashing twrp)

aIecxs said:
Yes it's driver issue. Disable driver signature enforcement and reboot. open device manager, connect phone and immediately select yellow triangle. install inf manually with let me pick option
you should not flash TWRP without a backup of stock recovery. Do a readback first. Also it is important the scatter file is matching your current partition layout. therefore you should analyze the result. if you are able to extract ramdisk with osm0sis' AIK then you have successfully dumped stock recovery (and can proceed with next step flashing twrp)
Click to expand...
Click to collapse
Understood before the readback thing. What is readback? I saw the tab in flash tools, but didn't get what it was? Can you please tell how to do that? (sorry for irritating, as I said I am a noob )
And how to analyse the result part? I didn't get the "extract ramdisk with osmosis AIK"
Is there any tutorial video that you know of, if yes, kindly send the link please coz I don't understand these terms.
And thanks a ton for this!!!

on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done

aIecxs said:
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
Click to expand...
Click to collapse
Okay, thank a ton!
I'll do all of this and get back to you.

aIecxs said:
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
Click to expand...
Click to collapse
So, what length and start address am I supposed to enter in hex?
And you shared the link AIK, in that there are so many options, which one do I have to select?

What can I do now?

deadmanspeaks said:
So, what length and start address am I supposed to enter in hex?
Click to expand...
Click to collapse
refer to scatter file
check your model name owens (XT1774 XT1775 XT1776) or nicklaus (XT1771 XT1772 XT1773)
download scatter file matching to your device model
https://motostockrom.com/motorola-moto-e4-plus-xt1770
https://motostockrom.com/motorola-moto-e4-plus-xt1771-dual-sim
https://motostockrom.com/motorola-moto-e4-plus-xt1772
https://motostockrom.com/motorola-moto-e4-plus-xt1773
https://motostockrom.com/motorola-moto-e4-plus-xt1775
deadmanspeaks said:
And you shared the link AIK, in that there are so many options, which one do I have to select?
Click to expand...
Click to collapse
Android.Image.Kitchen.v3.7-Win32.zip
Code:
S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] can not pass bootrom start command! Possibly target power up too early.
deadmanspeaks said:
What can I do now?
Click to expand...
Click to collapse
pretty much self explaining.
why flash boot.img? are you sure that scatter matches your partition layout (you will erase wrong area if not)!?

aIecxs said:
refer to scatter file
View attachment 5281905
check your model name owens (XT1774 XT1775 XT1776) or nicklaus (XT1771 XT1772 XT1773)
download scatter file matching to your device model
https://motostockrom.com/motorola-moto-e4-plus-xt1770
https://motostockrom.com/motorola-moto-e4-plus-xt1771-dual-sim
https://motostockrom.com/motorola-moto-e4-plus-xt1772
https://motostockrom.com/motorola-moto-e4-plus-xt1773
https://motostockrom.com/motorola-moto-e4-plus-xt1775
Android.Image.Kitchen.v3.7-Win32.zip
Code:
S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] can not pass bootrom start command! Possibly target power up too early.
pretty much self explaining.
why flash boot.img? are you sure that scatter matches your partition layout (you will erase wrong area if not)!?
Click to expand...
Click to collapse
Thanks a lot here it is written nma26.42-169/300 and my phone is xt1770. The link you gave shows the file can't be downloaded, can you please give any other link. I googled the same, it gave me NMA26.42-169 INDIA something but those files are paid

drive.google.com links working fine to me

aIecxs said:
drive.google.com links working fine to me
Click to expand...
Click to collapse

tested all links. must be something about your country. you should get something like
Couldn't preview file. You may be offline or with limited connectivity.
click on -> Download
Google Drive can't scan this file for viruses
click on -> Download anyway

aIecxs said:
tested all links. must be something about your country. you should get something like
Couldn't preview file. You may be offline or with limited connectivity.
click on -> Download
Google Drive can't scan this file for viruses
click on -> Download anyway
Click to expand...
Click to collapse
Yes, I did that, after that only it shows this.
I am about to cry, it's been 14 months trying to get those files. Every time, I get too close and then bam! back to square one. Can't access those userdata***.backup files, can't access the phone, as soon as it starts, it gets stuck in a reboot loop, can't flash TWRP because not able to download the file. You have no idea how painful this is. Still thanks a lot, you helped me a lot, but I guess it's a lost cause now. Earlier lost the person, now lost the memories. Thanks anyways

deadmanspeaks said:
can't flash TWRP because not able to download the file.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoe4plus.html