[Resource/DevTools] TheCollectiveHelpPackageSCH-i800[everything you need & some]72813
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TheCollective SCH-i800 Help package
http://wiki.cyanogenmod.org/w/P1c_Info
---------------------------------------------------------------------------------------------------------------------------------------------
TheCollective is Proud to present to you StockRooted-sch-i800 Verzion Galaxy Tab
For what ever reason we all need to get back to the default factory state.
soft brick
resale
loss of stablity
to name a few.
Here are the steps you will need to take.
First let's point out that this package contains EVERYTHING YOU NEED for this Except the windows PC to which it will be used on.
Before we begin Install Samsung usb device drivers located in the package.
**\tools-resources\drivers
Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
next is unpacking Hemdall 1.3.2 (The only one that worked for me on my SCH-i800)
**\tools-resources\Heimdall\
heimdall-suite-1.3.2-win32.zip
But here is a link to the developers page so you can download the original/newer if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ 2012 32bit [if 2013 32/64bit has already been installed you will need to remove it first to install 2012]
This needs installed on your machine because it has .dll files Heimdall uses.
**\tools-resources\MicrosoftC++12\
vcredist_x86.exe
Now you will need to install the drivers this is also needed for Heimdall.
unzip heimdall and go into the drivers folder where you will see /zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says, eg genirc serial device) (tho NOT massStorageDevice)
[good idea to remove any other usb devices as they can and sometimse do interfere with the packet data sending/receiving]
Click the button "replace driver" and let heimdall download/install the drivers. {libusb0 is the one that worked for me, but try another if it dont for you, there are three}
Run Heimdall-Frontend.exe as admin
Files provided To Flash Your Tab with
**\TheCollective-StockRooted-sch-i800.tar.gz >--TheStockRooted 2.3.5 that came on your tab.
**\tools-resources\HumberOS\heimdall-uses
boot.img >-- a CM10.1 kernel with TWRP for sch-i800
recovery.bin >-- CM10.1 twrp for sch-i800
if you need the pit file --> my-sch-i800.pit [extract it from the stock tar gz]
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder "Heimdall" and start " heimdall-frontend.exe" as ADMIN
4: Set up the file you are about to LoadPackage tab. [It should look something like image.]
5: After you have the file in place click load, it will change tab to flash with files listed, simply click start to flash.
ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
Tab should boot. [if not factory data reset in recovery e3 and reboot]
Click to expand...
Click to collapse
After this is should be just like you took it out of the box, and already rooted.
Hope this helps!
---------------------------------------------------------------------------------------------------------------------------------------
If you wish to unroot I've included SuperOneClick shortfuse.
just hit unroot
If you wish to install CM or other AOSP rom here is some helpfull info.
Heimdall command line
Flash boot.img with heimdall command line like this:
Press Power + VolDown untill you get the Download screen or PC <–> Tab screen.
on PC open CMD prompt in the folder of Heimdall and place boot image in same folder
type this command string:
Code:
heimdall flash --kernel boot.img --recovery boot.img
Or just replace boot.img inside the ROM ZIP with your desired kernel.
*TIPS
In case you get any strange symptoms.
Flash full TheCollective-StockRooted-sch-i800.tar.gz (with repartition) via Heimdall.
Flash the Kernel included in the package using the heimdall command above.
Boot directly into CwM Recovery, holding Power + VolUp.
Flash CM10.1 ROM, if it reboots by itself repeat the step above.
If you want Google’s stuff, flash latest GApps for Android 4.2.2.
Only Reboot after everything.
Wrong MAC? Wrong IMEI? Try restoring files from /sdcard/backup/efs*/* to /efs/. If you don’t have a backup, then start over with FULL Restock, and next time save your backup/efs folders, which are created everytime you install CM10.1.
Market problems? Clear Google Services Framework data and reboot.
No touch? That means you got the wrong kernel installed. A couple of builds had problems identifying the exact model. Just flash your kernel through recovery or heimdall / odin.
No boot? Stuck at the SAMSUNG logo? Flash the correct kernel using Download Mode using heimdall!
Deep Sleep not kicking in? Try wiping cLock’s data or freezing / removing it (com.cyanogenmod.lockclock).
--------------------------------------Highlights of What you get inside---------------------------------------------------------------
**\TheCollective-StockRooted-sch-i800.tar.gz
The Heimdall package
**\tools-resources\drivers\Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Samsung Mobile Drivers for usb
**\tools-resources\Heimdall\heimdall-suite-1.3.2-win32.zip
Heimdall
**\tools-resources\HumberOS\heimdall-uses\boot.img
CM10.1 humberOS Kernel P1c
**\tools-resources\HumberOS\heimdall-uses\recovery.bin
TWRP Touch Recovery 2.5.0.0
**\tools-resources\HumberOS\CwM_CM10.1-humberos_kernel_p1c-20130715.zip
CM10.1 humberOS Kernel P1c
**\tools-resources\MicrosoftC++12\vcredist_x86.exe
Microsoft C++ redisturbutial
**\tools-resources\ODIN-1.7\
Odin3 v1.7.exe
If you need it for modems or kernels
**\tools-resources\PartitionTool4microSD\pwhe8.exe
if you get encryption failed, you might find this usefull to partition your external sdcard [deeper instruction online at rootzwiki]
**\tools-resources\SuperOneClick\SuperOneClickv2.3.3-ShortFuse.zip
unroot/root what ever just good to have hard to find
DOWNLOAD
MD5 Sum: F0F9C9FA54219EDFA50E85163D9A7C54
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
robjective said:
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
Click to expand...
Click to collapse
F0F9C9FA54219EDFA50E85163D9A7C54
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Cellulah said:
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Click to expand...
Click to collapse
I had the some problem. Tried it at work with FF, Chrome, and Free Download Manager and all would fail at some point after about 2/3 done.
Came home and tried and got it first try.
tinpanalley said:
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Click to expand...
Click to collapse
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
I'll try again. The download was fine but I suppose I could try again.
No use.. same error every time . Tried with each driver as well. All I get is this:
tinpanalley said:
No use.. same error every time . Tried with each driver as well. All I get is this:
Click to expand...
Click to collapse
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
Windows 7, 64-bit
Intel i5-2400 3.10 GHz
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
tinpanalley said:
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
Click to expand...
Click to collapse
Yes. I had same issue on my captivate trying to restore stock from a cm7
To fix I had to flash in the kernel and recovery from cm and in cwm under advance mounts format data. Back then on that device speedmod kernel allowed users to select format method (fat32/ext4/etc)
But also hemidall should format with the repartition. But that is assuming it can read and mount the partition.
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Click to expand...
Click to collapse
I did try this but I still get the crash of heimdall.
Also what does "mount and format data" mean? I can format data, system and cache but I don't see "mount" at all.
The Collective DL Fails
So I am trying to download the package that is for this which would be most helpful for me as I'm trying to help out my pastors wife with her Galaxy Tab, I started the download and it got all the way up to 144MB and quit, and file won't work.
Is there somewhere else that you can put it so we can try downloading from there? Can I give you my dropbox and you can drop it in there?
Again just to say I don't have a problem with HEIMDALL I have a problem downloading your link for the files needed for the flash.
I would really like to try to get this working for her as I've been looking around for a solution for this thing for about 2wks already and its been blowing my mind.
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
chi_tilt said:
So I am trying to download the package that is for this which would be most helpful for me as .......
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
Click to expand...
Click to collapse
Try a direct download link
http://www.theandroidcollective.org/i800/public/TheCollective-HelperPackage_sch-i800.zip
Sometimes download errors like yours seem to happen when the user is behind a proxy.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
No 3G with alroger's latest kernel
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
arielja87 said:
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
Click to expand...
Click to collapse
Easiest way is to tar the modem.bin and Odin it into the device.
Load it into the phone slot
Sent from my GT-P5110 using Tapatalk 4
Help to download...
Hi... I have tried many times to download the package (TheCollective-RootedStock-Odin-sch-i800.tar.md5) but I can not , the download starts fine, but not complete!.
If you could upload to another server like 4shared, mediafire, dropbox... I would be very grateful..
Still not working as it should
So I have downloaded the package finally and I Have done all the steps according to your writeup. Still doesn't give me a fresh startup on the tablet, I still get many error popups and also all my apps are still there.
What could I be doing wrong? Could there be something wrong with the tablet?
Any help on this would be great, as I'm dumbfounded on this already.
Thank You
Lem
Related
I was wondering if i was the only one who's a noob on this site because i have been trying (with no success) to root my using some good directions which i have posted below. The problem is... i only speak noob. I am so new to this stuff that i really dont know what to do. What i have already done is downloaded the update.zip and the SDK i dunno if i installed it properly but i know i have to go into my cmd and type something... from then on there i have no clue what to do. ANY HELP IS GREATLY APPRECIATED ^_^
Originally Posted by AllGamer View Post
Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volumen up down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box
Before you begin get some important info from the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
just glance through it, and look at the pretty pictures.
then to Root you phone follow this topic, which is also linked on the Wiki
Self Unlock SGS tutorial
http://forum.xda-developers.com/showthread.php?t=747235
which starts from the basic, to root, all the way to unlocking the phone
post back if you have any question or get stuck at any point
just in case you missed it, make sure your 3 buttons Recovery Mode is working, else keeps all your finger crossed for good luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the update.zip that you seek is attached to the link of the rooting/unlocking topic linked above
if the 3 button recovery mode doesn't work
using the Android SDK you installed run the ADB.EXE command
it is inside one of the folders after you unzip the Android SDK package
k so the 3 button thing was a no go :/ do you think you could walk me thru (slowly) how to do the whole abd thing properly? Also the link you reffered me to is exactly what is on this thread and i just dont have enough experience to understand each of the steps, if u can just give me the main pointers in noob talk then i think ill be albe to figure out the rest
yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed
AllGamer said:
yeap, you need to copy the update.zip into the phone internal SD card
you can do that by simply connecting the phone to the PC on the USB cable
instead of USB debugging mode, just choose USB Kies mode
make sure Kies is installed
Click to expand...
Click to collapse
Can i do that while im on recovery mode or will that eff evrything up?
So i now have no idea how to put the update.zip file onto my internal sd card there is nothing on the phone i checked all the settings and i disabled the debug...
does the windows explorer shows the drive letters?
just copy and paste the update.zip file into the Internal SD card of your phone
when you connect via Kies mode to your PC
the windows explorers automatically pops up too
Bell root is not possible!
i may try samsung keys however i dont see how that helps you put the update.zip on your internal memory card or allows you to access anything in adb.exe in command promp.....my main question is acctually how the heck do you root the samsung vibrant with bell??? I have tried the thread in xda developers forum for bell saying it is the only way to get it to work....well it willl not work along with the million other ways i have tried, except 1clickroot it bricks alot of phones. Has anyone successfully rooted vibrant with bell! If so how?! I have even tried Z4Root which is the preferable method, well maybe i will just have to wait until some figures out a way that works. Boot with 3 button method "up vulume +menu+power" then apply sdcard:update.zip
E:signature verification failed
Installation aborted.
It says this everytime no matter what way i try!!! please someone have a solution!
Here you go...
This worked well for me.
http://forum.xda-developers.com/showthread.php?t=803682
Read all instructions carefully!
Rooted!
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?
aub_pro said:
Thanks worked like a charm good thing only way I had left to root my phone. Any ideas how to apply the lag fix? One click lag fix will not work "error installing device busy" I tried moving all Apps to external and still wont work? Is there another way?
Click to expand...
Click to collapse
For my first phone, I tried RyanZA's OCLF (search for oclf in the app market). I did have it installed and working pretty decent but ran into some issues in the beginning trying to apply the lagfix.
On my new phone, I applied Darky's ROM 9.2 with SpeedMod Kernel. You can enable or disable lagfix from recovery mode using CWM (ClockWorkMod) Personally, I just left the lagfix disabled and my phone now is performing way better then my first phone when I had lagfix enabled. (Mind you, my first phone was bricked).
I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol
aub_pro said:
I have downloaded darkys rom 9.2 and cwm recovery in rom manager also downloaded darky configurator from market for 9.2 and enabled speed work kernal in the configurator .do I flash rom with that app or use the flash rom from SD in rom manager? I will read more and try and figure this out....thanks a million for everything but if you could help me with this confusion that would be great lol
Click to expand...
Click to collapse
Do you have a Bell phone?
- In any case, I had flashed my kernel using odin first.
- Copied the ROM(the entire zip file. don't extract it) over to the root folder of my phone.
- Boot into CWM and selected install zip from sdCard
- Select "choose zip from sdCard
- find the ROM that you downloaded to your phone and select it.
- let the phone do its thing and your good to go.
That was probably the long way but I now see that you can apply the ROM through Darky's Configurator...
- Open up Darky's Configurator
- Select Wipe the device if you want a clean install
- Select your Kernel preference
- Select Modem options (this is why I asked if you were Bell user. Apparently there has been an issue where you loose 850 band if your flashing a new ROM using JL2. So in this option, I selected "no modem")
- Check Alternative WiFi driver
- For the rest of the options you can see you can choose for yourself.
Once you are done with the selection process, press the menu key button on your phone, then choose "Select Zip and Flash".
Follow instructions on phone and you are good to go.
awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....
aub_pro said:
awesome those are much less confusing instructions then others....im stuck on the kernal part download it and extract it and there is no .tar file it is just zimage....file.....i have tried downloading it ten times same result....its the recommended odin 500 kernal
i have tried mounting that file in odin pda and it must not be a .tar cuz it doesnt even see the file....
Click to expand...
Click to collapse
No need to extract that file. Once it is downloaded on to your PC, use Odin and navigate to where the file is downloaded.
I will have to verify the kernel I downloaded when I get home but I'm certain that I did not extract anything.
kernel installed
ok speedmod kernel is installed but when i load up darkys config the wipe all is greyed out and i cant click it.....im assuming that i use boot phone into recovery and whpe/factory data reset from there? wont i lose the darky 9.2 rom then being as it is on the root of the internal card?
the bold parts below are confusing me....so on the internal sd i should have the update.zip and darky rom 9.2 or is it just refurring to darky rom everytime it mentions zip?
Now turn off your phone, and wait for it to shutdown completely. Then, boot into Recovery Mode. Press and hold Volume-UP + Home + Power at the same time, and let go of the buttons when the screen turns on (and says Galaxy S GT-I9000/I9000M Samsung), to enter Recovery.
7. Then using the volume keys to navigate and the Power button to select, do the following:
Select 'wipe data/factory reset', and then select 'Yes'. Important!
Select ‘Install zip from sdcard’.
Then select ‘choose zip from sdcard’.
Now navigate to the ROM zip, then select it.
Then choose ‘Yes’.
8. The ROM will now be installed. After it says install complete, select ‘Go Back’ twice, then select 'Reboot System now'.
There you go, Darky's ROM is now installed!
k i figured it out im at the last step installing update.....been at this screen for about 10 mins but im sure thats normal.?
k it was hanging way to long on the installing updates screen and appeared to be frozen so i press menu + vol up + power and after a few time of it hanging at the galaxy s screen it finally brought me to clockwork recovery....so i rebooted normally and now i have the speed kernal still installed still rooted but the phone is original hardware? what do i do now?
Hey
....when you go to the menu settings about on your phone, what does the build number say?
Do you have Darkys Configurator app installed? Use that to flash the new rom. If you have nothing on your phone I would choose wipe. Choose the itmes that you want in the configurator. Select the menu button on your phone then select the option Save zip and exit... the second button in the bottom right.
Then choose Darkys rom where you saved it on your phone.
Sent from my GT-I9000 using XDA App
This 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
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
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Credits
@social-design-concepts for his great work and exploit for Intel Tab Devices
@vampirefo for CWM binary for Intel devices + Linux scripts
@vache for the full Repacked CWM image
Devices Compatible
A1-840FHD
A1-840 (HD)
A1-830
B1-810
A1-850
A1-860
B1-820
A3-A30
Requirement
Install the official Generic Google USB Drivers on your Desktop (http://developer.android.com/sdk/win-usb.html) - Also available in the TOOLKIT Package
Enable USB Debug on your Device
Guide 1 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.042_AV0K1_RV0MRC02_WW_GEN1 and older)
A1-830
Download
myKIT_BATCHv1.1.2.7z available at http://forum.xda-developers.com/showthread.php?t=2681783
myKIT_BATCHv1.1.2d_PATCHKIT.7z at http://forum.xda-developers.com/showthread.php?t=2681783
INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z at http://forum.xda-developers.com/showpost.php?p=51090059&postcount=3
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip myKIT_BATCHv1.1.2.7z and move myKIT_BATCHv1.1.2d_PATCHKIT.7z & INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z in the mykit-downloads directory
Start run-me.bat and type ACCEPT, press Enter. The toolkit is upgraded to 1.1.2d.
Close it, plug your Tab with USB Cable and start run-me.bat again
Type ACCEPT, press enter, type "2", press enter,
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
On your deskop, the script should auto detect the Tab like 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"
}
Type A2, press enter, type 1 for INTEL_TRIAL_TETHERED_CWM_PKGKIT and press enter
Type ACCEPT, press enter
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 2 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.057_AV0K1_RV0TRC01_WW_GEN1 or more recent)
A1-840 (HD)
B1-810 [confirmed by @alexys77]
A1-850 [confirmed by @Darrian]
A1-860 [confirmed by @edotcom]
Download
IntelAndroid-FBRL.7z available at http://forum.xda-developers.com/showpost.php?p=57505512&postcount=2375 thx to @social-design-concepts
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip IntelAndroid-FBRL.7z
Plug your Tab with USB Cable and start launcher.bat
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
Type ACCEPT ont the cmd screen, press enter
On your deskop, the script should auto detect the Tab like this (device status online + color blue) :
Type "T3", press enter
Note: if the T3 exploit doesn't work on your device, you can try T2 or T1
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
/!\ Please note that the tethered CWM has just boot, it has not be flashed, we can't flash a custom recovery while our bootloader are locked. /!\
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 3 - Boot Tethered CWM or TWRP
Compatible with
B1-820 (LP 5.0)
A3-A30 (LP 5.0.2) confirmed by @paugustin
Procedure
Follow all steps described by @social-design-concepts on his updated thread :
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Advice/FAQ for Acer Tab Device : :
You should use the CWM recovery and the T4 exploit
TWRP boots, but no touch available
CWM runs fine, but cannot mount internal storage or /data, you MUST use an external SDCard
Flashing SuperSU and Installing Xposed Framework for LP is working great on B1-820 !
Guide 4 - Flash CWM Recovery (permanent)
vache said:
CWM for A1-840 FHD (only) based on Dell Venue 8 one. (http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925)
Tested successfully.
ADB_Fastboot.zip for Intel Devices (use this to flash)
CWM-v6.0.3.7_A1-840FHD.img.zip
stock_recovery.zip
To flash it :
Code:
fastboot flash recovery CWM-v6.0.3.7_A1-840FHD.img
Then use droidboot menu to reboot in recovery.
Click to expand...
Click to collapse
Thx @vache & @vampirefo
Firmwares
Flashable via (stock) Recovery
A1-830
SDs_Acer_AV0K0_A1-830_1.007.00_WW_GEN1.zip
SDs Acer_AV0K0_A1-830_RV01RC02_WW_GEN1.zip
SDs_Acer_AV0K0_A1-830_RV01RC05_WW_GEN1.zip
A1-840
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0ERC02_WW_GEN1
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0LRC01_GC_GEN1
SDs_Acer_AV0K1_A1-840_RV0XRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840_RV0ZRC03_WW_GEN1.zip
A1-840FHD
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0BRC01_WW_GEN1.zip
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0MRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840FHD_RV0TRC01_WW_GEN1.zip
B1-810
SDs Acer_AV0K0_B1-810_RV02RC03_WW_GEN1.zip
SDs_Acer_AV0K0_B1-810_RV02RC04_WW_GEN1.zip
A1-850
SDs Acer_AV0K0_A1-850_RV00RC01_WW_GEN1.zip
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
stari_alca said:
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
Click to expand...
Click to collapse
We can't flash it for now
This exploit only can boot it
We need to unlock the tab to be able to flash something
Envoyé de mon A1-840FHD en utilisant Tapatalk
Great Guide!
Unfortunately it doesn't work with the very similar A1-840HD:
http://forum.xda-developers.com/showpost.php?p=56580827&postcount=2158
Hi there,
How did you guys manage to install the MTP device drivers (the one that pops up in Device Manager when you enable the USB debbugging)? I´m on a Windows 7 (32 bits) and the folder we are instructed to download and unzip apparently does not contain the required files/driver.
Any help is appreciated as I can´t manage to pass that initial point.
Thanks in advance,
Mix
EDIT: I eventually got it to install correctly by using the USB Driver package from Acer:
http://global-download.acer.com/GDF...ep3=A1-840FHD&OS=ALL&LC=en&BC=ACER&SC=EMEA_27
I used the option in the toolkit which installs the drivers. If I remember correctly once you run the .bat file and ACCEPT you are given this option. I used 32 bit version of Win 7 as well.
Sent from my A1-840FHD using XDA Free mobile app
Works on A1 830
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
retroben said:
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
Click to expand...
Click to collapse
Did you try this guide?
I'm not sure I understand your post and what you want to do.
My product and safety information booklet says FHD on it despite mine only having 1GB of RAM.
Is there a root method working on the A1-840HD?
I may try Kingo since they still get updates and just added an exploit for Nexus Android 4.4.4 as well.
I hope it has support for this device.
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
borisgregoris said:
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
Click to expand...
Click to collapse
Well... I don`t have this tablet but think of buying one and I think that this could be done.
CWM has backup feature so I think that you could try backup current ROM and after you did that then root your device and if the problem pops you load CWM again and then restore original state.
If you already rooted then I think that someone that hasn`t rooted the device could make backup of ROM and upload it somewhere on the Internet.
Here is a full UPDATE zip ROM for A1-840 only (not compatible with A1-840FHD), flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
borisgregoris said:
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
Click to expand...
Click to collapse
It means that my image is older than yours (which make sense, it's not the latest firmware)
But I think you can get some file from it and make your tab working fine again.
If it doesn't work, you can try to full flash the update zip to "downgrade" to a stable version (and then, you should get some OTA updates to get back to the latest version)
Here is some OTA manual download if needed :
Code:
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0TRC01 227,47MB http://global-download.acer.com/GDFiles/Application/OTA/635537141647405935_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0RRC02 227,33MB http://global-download.acer.com/GDFiles/Application/OTA/635526789434977662_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0BRC01_AV0K1_RV0MRC02 45,86MB http://global-download.acer.com/GDFiles/Application/OTA/635490499381942196_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV09RC01_AV0K1_RV0MRC02 49,69MB http://global-download.acer.com/GDFiles/Application/OTA/635469761667577586_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0JRC02_AV0K1_RV0MRC02 42,13MB http://global-download.acer.com/GDFiles/Application/OTA/635469757626803549_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV08RC01_AV0K1_RV09RC01 37,53MB http://global-download.acer.com/GDFiles/Application/OTA/635402969903280635_OTA_Acer_1.0_AV0K1_A.zip
Enjoy
Hi, thanks for the image. Custom recovery fails for me:
assert failed: getprop("ro.product.model") == "A1-840"
Error in /cache/sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
stari_alca said:
Hi, thanks for the image. Custom recovery fails for me:
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Click to expand...
Click to collapse
Hi, same error here.
After flashing in stock recovery give me the assert failed error.
Its secure to flash the OTA files? I'm curious if they send me the same error that the update.zip. I'm afraid to brick the tab .
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Shreps said:
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Click to expand...
Click to collapse
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
borisgregoris said:
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
Click to expand...
Click to collapse
You should also set the right permissions and owner to the files like other file in the same directory.
Envoyé de mon One+
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