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+
Related
This thread is primarily intended for n00bs.
I would like to say thanks to xda forum members: Noejn, Zecanilis, drellisdee, The_ERROR etc. Also thanks is due to Godlike! at tech-mania.com for his tutorials. Thanks is due especially to The_ERROR for proofreading the post and to other users for their suggestions written in the thread.[/SIZE]
---------------------------------------------------------------------------------------------
NEW - 3 May 2011 - Simplified Guide to Root & install version 1.2 of Custom Thunderg Recovery by AmonRa/modified by Drellisdee on LG P500
ALWAYS MAKE A BACKUP BEFORE CUSTOMISING YOUR PHONE.
[CUSTOMISING A PHONE USUALLY INVOLVES: ROOTING >>>> INSTALLING CUSTOM RECOVERY >>>> INSTALLING CUSTOM ROM]
The instructions written below have been tested by me using an Indian unbranded GSM model of LG P500 which came with stock Android 2.2.1 (V10C). The procedure to be followed for any LG P500 phone is the same.
This post is split into 4 major sections -
1. INSTRUCTIONS FOR ROOTING
2. INSTALLING ANDROID SDK ON A WINDOWS PC (This step is needed to install Custom Recovery on phone using adb from PC. Can be omitted if Recovery is installed from phone using Terminal Emulator)
3. INSTALLING A CUSTOM RECOVERY
4. INSTALLING CUSTOM ROMs
MUST READ: If you haven't read this thread already, please do read it - Dictionary for n00b - What is.../What does ...mean?
---------------------------------------------------------------------------------------------
1. INSTRUCTIONS FOR ROOTING
To know your present firmware version - Go to Settings/About Phone
Only phones which come with stock android 2.2 could be rooted till recently.
UPDATE - 24 April 2011 : A tool called 'GingerBreak APK' is able to root phones running stock android 2.2, 2.2.1 & 2.2.2. Read about it HERE. This tool enables rooting without the need for downgrading the firmware to 2.2. If 'GingerBreak APK' doesn't work out for you, continue reading to understand the procedure to root your phone after downgrading your firmware. Note: 'GingerBreak APK' permanently roots your phone. Also,GingerBreak might not install BusyBox and SuperUser apps properly on your phone. These apps are required by many rooted apps for their proper functioning. So, use Root Checker from android market to verify the proper installation of these 2 apps.
If your phone runs stock android 2.2, enable 'USB Debugging' on Phone (Settings/Applications/Development). Install z4root (copy the apk file to the sd card and open the file after browsing to the location using the phone's file manager), run it and root the phone. Find it HERE.
Choose the permanent root option as it is still possible to force unroot if needed.
Restart the phone and launch z4root to check the root status. A successful rooting should show 'Unroot' option when z4root app is opened.
{Note: z4root automatically installs Busybox and Superuser application(which appears as an icon in your app drawer) on the phone.}
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
For phones that came with stock 2.2.1 or 2.2.2 installed, rooting first involves downgrading the firmware to 2.2.
Downgrading the firmware can be done with KDZ-FW-UPD.exe (procedure outlined below)
(KDZ-FW-UPD.exe has been claimed to work best with windows xp 32bit.)
FIRST: DOWNLOAD THE Android 2.2 FIRMWARE FOR YOUR DEVICE. For this, go to: [ROMS] Original LG Firmware list and read about the procedure to download the original firmware.
{Tips: Use Ctrl+F in browser to search for Country name, Remember to change the alphabet in 2 places in the final link to download the firmware, Do not bother about the 'CDMA' tag attached to country code. It works for the GSM model phones too. If the link to find out the country codes doesn't work, use the 2nd method mentioned in the post to find out the country code using your phone's IMEI or ESN number }
Download the required Firmware onto your PC.
Links to Original firmware versions for Indian P500 are mentioned in THIS POST
Procedure to install original firmware using KDZ-FW-UPD.exe ( KDZ FIRMWARE UPDATER ) This procedure can also be used to restore the stock firmware and recovery onto your phone in case you want to give your phone to the service centre during warranty period as the phone will appear similar to as you bought it from the store.
[Note: This procedure was used to install V10B_00.kdz(android2.2) over V10C_00.kdz(android2.2.1) on an unbranded Indian GSM model of LG P500 using a Windows 7 Ultimate 64bit updated to date PC.]
1. Install LG PC Suite IV from SD card which came with phone by connecting the phone to PC through USB cable. This is done to install the drivers for the phone on the PC (the procedure is as follows)
- Enable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard & Phone Storage menu.
- Connect phone to PC with the USB Cable.
- Press the 'Turn on USB Storage' button which appears on phone.
- Browse to the folder containing the 'LG PC Suite IV' on the phone's SD card using Windows Explorer and run the LG Installer file. PC Suite will now install on your system along with the required drivers for your phone.
- Cancel setting up PC Suite or continue setting up PC Suite if you want to Sync or backup the phone data.
- After closing PC Suite, Safely remove the USB device from your system.
- Press the 'Turn off USB Storage' button on phone screen.
- Detach the USB Cable.
- Disable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard &Phone Storage menu.
Alternatively, I also tried installing the latest drivers via LG Mobile Support Tool from LG's website (available HERE) but KDZ-FW-UPD.exe (mentioned below) crashes when run. This could be happening only to me, so please try for yourself before writing off this method.
2. For my comfort more than anything else, I switched off the screensaver and other power saving features on the PC and also set the screen timeout delay on the phone to 30 minutes.(Settings/Display/Screen Timeout)
3. Charge the phone to the maximum.
4. Enable USB Debugging on Phone (Settings/Applications/Development).
5. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
6. Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.)
7. Unmount the SD card from the phone (Settings/SDcard & Phone Storage).
8. Open phone back and remove the SD Card.
9. Download KDZ_FW_UPD_EN.7z onto your PC and extract it to a folder. Available HERE.Direct Download Link. (MD5 of 7zip file - 813A28BE9182AB604A1D43E745CE7AD7)
10. Run the msxml.msi file and complete the installation.
11. Connect the phone to PC with USB Cable.( If you are using a desktop PC, make sure you use USB ports that are in the back of your PC, avoid the front ports.)
12. Run KDZ_FW_UPD.exe from the extracted folder.
13. Chose TYPE as 3GQCT & Phone Mode as DIAG.
14. In the 'KDZ file' space, browse for the firmware you want to install. (In this case V10B_00.kdz)
15. Press the 'Launch software update' button.
16. The firmware flashing process is now underway.
If all goes well, in 5-10 minutes the phone will be flashed with the new firmware.
I shall describe in detail what happened with my phone - 10-15 seconds after launching software update on PC, my phone screen turned blank and in a couple of seconds the phone entered the 'Emergency Mode'. During this mode the screen was yellow with Emergency Mode written along the middle of the screen. The phone stayed in the same way till the Software update procedure finished on the pc and the phone turned blank. I waited a while for it to reboot but after a minute or so, I manually switched on the phone. The phone came alive and following the LG boot animation, the android logo screen came up. The phone spent about 2 whole minutes in that state before booting up fully and entering the home screen. Update: Wait till phone reboots by itself or wait for a while before manually switching it on.
17. After booting up fully, detach the phone from the pc.
(If the phone gets stuck in the android boot logo screen during first boot, doing a hard reset by pressing and holding the VolDown+Home+Power buttons may resolve the problem.)
Go to 'About Phone' in Settings and confirm the change from 2.2.1 or 2.2.2 to 2.2.
Root the phone using z4root as mentioned before.
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
IN CASE OF PROBLEMS DURING DOWNGRADING FIRMWARE, read the following thread completely. Various types of errors and various measures to correct them including some innovative ones like shaking the phone etc. are mentioned here - [HOWTO] Phone not responding at all - last chance to repair. It is advisable to read this thread completely before attempting to downgrade the firmware using KDZ_FW_UPD.exe to become aware of all the possible problems you might encounter and their possible solutions.
PS: Here is the link to the phone drivers that came with my SD card. One user reported a problem wherein kdz updater would recognise the phone but the update process would fail during kdz unpacking. the problem was resolved by using the drivers i sent him. So, if anyone has the same issue, it might be worthwhile to try out the following drivers. I wouldn't advise everyone to follow this method, but those of you who are feeling lucky might try it out. Download Link
---------------------------------------------------------------------------------------------
2. INSTALLING ANDROID SDK ON YOUR WINDOWS PC
This step is required to install Custom Recovery on your phone using adb from your PC. Using a Custom Recovery, you can make a backup of your current ROM, restore backups, create partitions on your SD card, wipe your phone and the SD card and then also go on to install Custom ROMs using the Flash from Zip option.
Installing a Custom Recovery can also be done in other ways. Using Android SDK from your PC is just one method.
(Custom Recovery can alternatively be installed on your rooted phone using the commands given in the next section using a Terminal Emulator. This method removes the need for installing Android SDK on your PC and connecting your phone to PC. Download Terminal Emulator from Android Market. Install on phone. Run it and give it root permissions when prompted by the 'Superuser' application. As mentioned in the next section, copy the 2 files (flash_image & the custom recovery image file) needed to install Custom Recovery onto the root directory of SD card. Reboot phone. Open terminal emulator and type 'su' without the quotes and press Enter. This will take you to the root shell (#) from the default user shell($). Carefully type in the 7 commands mentioned in the next section one after the other. After typing in the last command (reboot recovery) and pressing enter, WAIT. The phone will reboot. Custom Recovery will have been succesfully installed on your device.
Hint: Copy the installation commands as a text file to phone & copy and paste the commands one by one into terminal emulator using a text editor. Please make the necessary changes to the installation commands depending on the recovery version used)
To install Android SDK on PC, there are a few requirements/downloads which have to be completed first:
JDK (Java Development Kit) - Download Here
JRE (Java Runtime Environment) - Download Here
Android SDK installer - Download here
So after all the downloads are completed, you are good to go. Run PC as Administrator.
First of all install the JDK, then the JRE and then the SDK Installer.
{If when android sdk installer is run, you get an error that JDK or JRE is not detected even after their installation, wait for a while, shut down the computer and restart and run the SDK installer once again.}
Make sure that while installing the android sdk, the installation directory should be the root of a partition i.e. it should be in the following form: C:\android-sdk, where you should replace the letter C with the letter you have assigned to the partition that you want to install it in.
Now that the Android-SDK is installed, go to the installation directory and start the SDK Manager. You need to add the components of the Android SDK to your installation. Before that I would like to inform you that you can save time if you download only what is necessary. If you are on Android 2.1 then you should download the 2.1 sdk, for 2.2 the 2.2 sdk and so on. You do not need to have all the versions for this thing to work. Just your version would do. So to start adding components, I recommend that you read THIS
After installing the desired components, you need to do perform some simple steps in order to use the adb terminal just like the cmd terminal for Windows.
For that purpose, here are the steps to be followed:
Right click My Computer, select Properties, and click Advanced System Settings. (Windows XP users - Right click My computer and just click Properties and select the Advanced Tab)
Click on Environment Variables, in the System Variables box, scroll down to the variable name 'Path' and double click to edit it
It would read something like " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static".
Here you need to add a semicolon ( ; ) and add the path of the tools folder in android-sdk.
It should finally be like this " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\android-sdk\platform-tools {or the location where adb.exe resides on your system}
Click OK wherever asked and then restart your computer.
Now open a command prompt window and type adb and hit enter. If a terminal window is displayed, you have done it all right.
If it gives some error message, read the article carefully and see what you have messed up with.
---------------------------------------------------------------------------------------------
Tip:
Using adb - How to install apps from PC without having to copy them first to the SD card?
If you want to install apps in one click, all you need to do is download the .apk file of your application to your PC and set the open with option to this batch file which you can download HERE
Save the batch file on the desktop of your PC before setting the option to 'Open With'.
---------------------------------------------------------------------------------------------
3. INSTALLING A CUSTOM RECOVERY
(Procedure of installing Custom Recovery using a terminal emulator from your phone instead of installing android SDK on your PC and connecting your phone to PC is mentioned in the last section.)
UPDATE - 3 May 2011 : Very simple way of installing Custom Thunderg Recovery by AmonRa/modified by Drellisdee version 1.2. Originally posted by ungaze in this post.
1. Download Android Terminal Emulator from Android Market. Install it on your rooted phone.
2. Download the file "amon_ra_recovery_installer.zip" from here or here. Check the MD5 hash value of the downloaded 'zip' file using tools like HashTab etc. before proceeding further. Correct MD5 value : 86db8a52b01f049cadb8f097a4c5bd9e
3. Extract the contents of the 'zip' file to the root of the sd card (ie. not inside any folder) using tools like 7-Zip or WinRAR or any other similar tool.
4. Open the terminal emulator app on your phone and type in the command 'su' without the qoutes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions to the terminal emulator app. Click 'Allow' and proceed. You will notice that the shell prompt has changed from the previous user shell '$' to root shell '#' in the emulator app.
5. While in the root shell '#', type in the following command and press Enter. Wait and the phone will reboot into the Custom Recovery.
Code:
sh /sdcard/rf.sh
Once you are up and running with a rooted phone, you will need to download the 2 files needed to install the Custom Recovery. They are:
Download No:1: flash_image - (This file is the same one needed to install any of the 3 versions of Custom Thunderg Recovery by Drellisdee given below)
Download Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link - requires registration at androidforums.com. (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Download No:2: Custom Recovery image file - Choose & download any version among the 3 available after reading what is written below.
Custom Thunderg Recovery by Drellisdee has versions 1.1, 1.2 and 1.2.1 at the time of writing this. I personally prefer version 1.2 as it supports backup & restoration of ext4 Partition on SD Card. Version 1.2.1 is a little experimental in nature & it may not fit all devices as it has a size near 5 MB.
Link to xda-forum thread for Custom Recovery P500/Thunderg - HERE.
The different versions of the Custom Recovery image files are available at the following pages
Custom Recovery P500/Thunderg v1.1
Direct Download link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Mirror Link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Custom Recovery P500/Thunderg v1.2
Direct Download link - (MD5 of zip file - 217FC9115899A41195CF124CAF07B880)
Custom Recovery P500/Thunderg v1.2.1
Direct Download link - (MD5 of zip file - 388aac16b1184ab15b5500b2b32d914c)
Please check the MD5 hash values of downloaded files to ensure that files are not corrupted using tools like HashTab etc.
Now to install Custom Recovery, Copy the two files [ the chosen recovery image file (*.img) & the flash_image file (flash_image) ] and paste in the root of your SD card (root means the directory L:\ where L is the letter for your Phone's USB Storage. In short, don't create a folder and paste the files inside it on your SD card).
{Note that the recovery image file should have an .img extension and flash_image file should have no extension when placed on the SD card}
Reboot the phone. Connect phone to PC.
The next step requires Android SDK to be installed on your PC.If you have installed the Android SDK, follow these steps:
Go to Start Menu & Run and type cmd (run as Administrator)
In the cmd window, type adb. If you have installed it correctly, you will see a lot of text on the screen. If you get an error message then you have probably not installed the Android SDK properly.
Type adb shell and hit enter
Type su and hit enter
See your phone at this time and touch the 'Allow' option which SuperUser shows you
Now the terminal window will have a # sign appended to it instead of the previous $ sign. See this screenshot for a better understanding
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now one by one, copy the following lines, in the serial order and paste it into the terminal window and press enter following each line(right click on window and paste, CTRL + V won't work)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (if it gives error message here, simply proceed to the next step)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (If the recovery version chosen is different from v1.2, type the appropriate file name of the recovery image here instead.)
reboot recovery
Click to expand...
Click to collapse
Wait. The phone will reboot now.
Note:{If you get this error after step 4
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
Simply move on to the next step.
If you get any errors other that those mentioned here, please do not proceed with the last command of 'reboot recovery'. If you do so, recovery may not be correctly installed and you will lose all data on the phone as the phone will be reset to factory defaults. Please go back to the instructions and see what you have done wrong.
NOTE: If on booting into the recovery you get the following message at the bottom of the screen -
E: 'Bad Boot Message'
Don't panic, it's perfectly normal and you can proceed with what you want to do from the recovery.}
Detach the phone from the PC.
To access the Custom Recovery, turn off the phone and then press & hold Home+Vol Down+Power buttons to boot into the Custom Recovery.
---------------------------------------------------------------------------------------------
Once you have booted into the recovery, the touch screen won't work. The actions assigned to the different buttons are given here. Use them to navigate through the different options in Custom Recovery.
Up & down: vol-up and vol-down key
Select: Menu key (left most)
Back: Back (3rd from left)
---------------------------------------------------------------------------------------------
What does Custom Recovery look like & What does it do?
Note: In Custom Recovery versions 1.2 and above, zips can be extracted from inside folders. So, save the zips in a folder named AAA and flash the zip after browsing inside the folder through recovery. The folder name should be named 'AAA' so that it appears among the first on the recovery screen, since scrolling is not an option in recovery.
Note: There is also an unofficial port of ClockworkMod Recovery availble. I do not recommend this recovery for newbies as it isn't compatible with all Custom ROM's out there.
---------------------------------------------------------------------------------------------
4. INSTALLING CUSTOM ROMs
BEFORE FLASHING ANY ROM, DO A NANDROID BACKUP FROM CUSTOM RECOVERY
Since all the ROMs have their own kinds of partitions to be created and other requirements, you can check them at the ROM specific pages.
General procedure to follow for installing a Custom ROM
Boot into Custom Recovery
Wipe your cache, dalvik cache, SD card
Make partitions according to the ROM requirement
Wipe cache again.
Connect Phone to PC
Toggle USB MS and paste the ROM zip file to a folder called AAA in the root of the SD card
Disable USB MS.
Detach phone from PC.
Select 'Flash from zip' option in Custom Recovery menu
Select the ROM file
Flash the ROM file
After flashing is finished, Reboot the phone.
Note: It will take some time to flash and reboot into your new Custom ROM. The phone may stay with the boot logo displayed for a number of minutes. Do not switch off phone during this period.
---------------------------------------------------------------------------------------------
In case of problems with phone, read: [HOWTO] Phone not responding at all - last chance to repair
Also read: [READ FIRST] [REF] Repository of howto's, roms, kernel, etc.
If you feel benefited by this thread, I humbly request you to rate this thread and vote it to the front page. The option to rate and vote is present in the title bar of the thread on the right side.
Please post your feedback. Also THANKS is always welcome. Use the THANKS button (below right) if you feel that I deserve it.
Update - 24 April 2011 - New rooting method without needing to downgrade firmware.
Update - 3 May 2011 - Very simple way of installing Custom Thunderg Recovery
Update - 3 May 2011 - Added Simplified Guide to Root & install Custom Recovery on P500
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
FnH84 said:
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
Click to expand...
Click to collapse
Have you installed the drivers for the phone on your computer? If you haven't, your phone will not be detected when toggling usb mass storage.
saileshchowatia said:
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Click to expand...
Click to collapse
Did you read the thread I have linked to at the end of the article? it may help you.
FnH84 said:
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
Click to expand...
Click to collapse
The procedure for downgrading the firmware is included in the article. The procedure is the same for installing any version of original firmware on the phone.
Procedure to change from one custom rom to another various with each rom.some may need a wipe while others might need repartitioning your sd card.
victortangocharlie said:
Have you installed the drivers for the phone on your computer?
Click to expand...
Click to collapse
Yes. It worked fine before. I tried to flash with CM7, and something went wrong. The whole SD-card is empty, works on another phone though. However, Windows will not recognize it no matter what I do
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
victortangocharlie said:
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
Click to expand...
Click to collapse
Both. I put the memory card on another phone and it said it was empty. Also, custom recovery says it's empty and from mount menu, I can see it keeps unmounting.
Have you tried another card on your phone?
victortangocharlie said:
Have you tried another card on your phone?
Click to expand...
Click to collapse
I managed to get the card work via another card reader. I put the zip files on it and trying again now. Hope it will work.
EDIT: It works!!!
nvm.....................
Glad to hear it.
Sorry for noob question, but after downgrade to 2.2, root, can I flash any rooted 2.2.1 ? And is there any?
Once you have rooted your phone, you can install any custom rom meant for p500. This includes all android versions. And, you don't have to apologise for being a noob, this thread is meant for noobs primarily. everyone has to start someplace. There are many rom's accessible on this forum including android versions 2.2 to 2.3.3. I suggest you try Nessy#Euridice ROM by Dookmatt. I am using it and it is easy to set up.it is based on android 2.2.2
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Guess, you will have to ask the people who make the rom's. I don't know about the cm7 rom.haven't used it myself.
IFLPI said:
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Click to expand...
Click to collapse
rooting a stock Rom is hard where as as rooting a custom made rom is easy because u only need the framework to create ur custom rom....
and about CM7 u can choose between many flavours.... its upto u ..
hi
hey man thanks for the wonderful tutorial!!
i just broght my phone 2weeks back. got it after lots of requests to dad!!
i wanna try all the stuff but im damn scared if i would brick my phone..
although i have the exact same phone as yours..unbranded indian optimus one with v10c
should i try it or is there a risk that ill brick it..?
if i brick it.. is there a chance that i can get it repaired? or will the lg ppl refuse to support me because i screwedwith it??
thanks in advance!!
[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
{
"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"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy
Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk
This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
I see some Desire folks
Did u order one chromium?
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?
Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times
Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM
There seems to be a little confusion on how to do this and I've written down how to in many posts now so I figure I'd just write it down in a little guide.
What you need:
Firmware update.zip from http://pro-teammt.ru/firmware-database/
Windows only: Huawei Update Extractor
Linux/Mac(?)/(Windows too): splitupdate perl script (requires perl)
Direct link: https://mega.nz/#!4PBknJrK!iZQDI4ti6ERmQJC6afgUGTSvHHKcm9KFz9okmwwez3I
Source: https://github.com/marcominetti/split_updata.pl/tree/f5f415262be3487de28321b49dcb69d947897bf1
(Or my 'special' version https://mega.nz/#!NS4VnL7Q!5GMn-soCf_WMW6fZANd-TDzxjQkZW2LynEQtJ_TlUdU which extracts
to the same folder as 'splitupdate' instead of 'output/', and includes a mount script (Linux only, maybe Mac?) for extraction of files of the different images)
Archive extractor of your choice (7zip, winrar, winzip and so on.)
Firmware build
First you need to determine what your current firmware is, this can be done by going to 'Settings -> System -> About Phone' on your phone. Check 'Build Number'.
Mine says:
{
"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"
}
BLA-L29 8.0.0.132(C636) (Replace 8.0.0. with C636 and add a B infront of 132 )
This can be translated into BLA-L29C636B132.
Now we have our current firmware!
Info on Nougat -> Oreo
As of Oreo the partitions changed a little.
'Boot' partition was split into 'ramdisk' and 'kernel'.
'Recovery' partition was split into 'recovery_ramdisk', 'recovery_vendor' and 'recovery_vbmeta', and shares the 'kernel' partition with 'ramdisk'.
The one's you probably want to flash are 'ramdisk' and 'recovery_ramdisk'. (Ramdisk is where Magisk/SuperSU goes, recovery_ramdisk is where TWRP goes)
Firmware update.zip
In this example I will be using my firmware, BLA-L29C636B132.
First start by going to http://pro-teammt.ru/firmware-database/ and enter your full firmware in the 'Enter model', click on Find Model.
This is what it will look like after you have searched. Locate the row that says FullOTA-MF and click on the 'update' link in that row.
When it's downloaded, open update.zip in your choice of archive manager and extract UPDATE.app to your desktop or somewhere easy to find.
Huawei Update Extractor:
Download Huawei Update Extractor from the link above, it's attached to first post in that thread I linked to (v0.9.9.5).
Extract the zip to your desktop (Or Downloads folder).
Enter the newly created folder that should be named 'HuaweiUpdateExtractor_0.9.9.5', and run HuaweiUpdateExtractor.exe.
Start by going to the 'Settings' tab and uncheck 'Verify header checksum'.
(Something is wrong with the header of erecovery_ramdisk, also it's mispelled to erecovery_ramdis, or maybe character limit? The partition on phone is named correctly. This does not need to be unchecked on Nougat firmware)
Then go back to the 'Extract' tab and click on the button that says '...' and open your UPDATE.APP
Rightclick on the file you want to extract and click on 'Extract Selected', this will bring up a dialog where you choose where to extract to.
After this you can flash the file using fastboot. Take 'ramdisk' for example.
Make sure you have adb & fastboot installed (https://forum.xda-developers.com/showthread.php?t=2317790)
Open up a command prompt and connect phone, reboot to fastboot mode using: usb plugged in, power + vol down, release power when phone vibrates.
Or you can use the command 'adb reboot bootloader'.
Make sure phone is recognized in fastboot mode with the command: 'fastboot devices', it should show up as a fastboot device.
Next we can flash RAMDISK.img using: 'fastboot flash ramdisk RAMDISK.img'.
On Nougat you would extract 'BOOT' from UPDATE.APP and flash using:
'fastboot flash boot BOOT.img'
Linux/Mac(?)(and Windows with perl installed, I use Strawberry Perl)
First download the splitupdate zip from above.
Extract it and enter the extracted 'split' folder, open a terminal and:
'chmod +x splitupdate'
'chmod +x crc'
Now put your UPDATE.APP in the 'split' folder and open a terminal and use the following command:
'./splitupdate UPDATE.APP file_to_extract'. If you write 'file_to_extract' or anything that is or is not in the UPDATE.APP it will list all images in it.
Typing './splitupdate UPDATE.APP' will extract all files in UPDATE.APP
It will output files to the newly created 'output' folder. The filtering is not perfect. If you use './splitupdate UPDATE.APP RAMDISK', it will extract all images with RAMDISK in its name, so you will get RAMDISK.img and RECOVERY_RAMDISK.img. This is fine for me as the original script extracted everything, which takes long for the larger images.
And if you use the 'special' version:
'chmod +x simg2img'
'chmod +x mount.sh'
I edited the splitupdate script for the 'special' version just to make it easier for me as I like to check SYSTEM, VENDOR, PROCDUCT and those images for changes.
So it made it easier if it extracted directly to the root of 'split' folder instead of 'output', then I could run the mount.sh script directly.
To use mount.sh, first edit the script and replace YOUR_SUDO_PASSWORD_HERE with your password or remove 'echo YOUR_SUDO_PASSWORD_HERE | ' and input password manually when it asks.
Then simply extract SYSTEM.img (or Product, vendor, odm whichever you like) and './mount.sh SYSTEM' (yes, no extension).
This will convert SYSTEM.img to SYSTEM.raw and mount it to 'split_folder/SYSTEM/' as a loop device, it will also chmod 777 everything in SYSTEM/.
Linux ADB and Fastboot
Use google for this one. ADB usually works fine right away, Fastboot might get 'no permissions' and need to be run as sudo if it's missing udev permissions/entries.
You can make fastboot work without sudo but it's easier to google it as it might get lengthy and there are a lot of different distros of linux (I use Ubuntu)
Hi ante0, i have downloaded the bla a09 8.0.0.109 c567 which is the recent update for my US mate 10 pro version, i was using hisuite to update my phone which is failing but i was able to grab the update which it down loaded and it has the following files in it, bla-a09_hw_usa( which contains update_full_BLA-A09_hw_usa, public( which contains update_data_full_public), update.zip which contains update.app and other xml files, i have already bl unlocked and rooted with supersu but i wanted to install magisk and i installed twrp and tried sideloading magisk but it fails stating boot image already modified and advised flask stock boot, so which files do i need to flash and what are the fastboot commands to do so and i was also thinking about complete bl lock just to make it look like new phone and how do i do that, please direct me, thank you.
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
oslo83 said:
I think to update you'll need to:
A) Unroot your supersu.
B) Restore stock boot and restore your stock recovery with guide in OP and with the firmware files actually installed on your phone.
Then you could root oreo with magisk.
Click to expand...
Click to collapse
there lies my problem, i am trying to flash an updated stock firmware than the one that came with my phone, i have unrooted supersu and deleted supersu app and dont have root anymore confirmed by rootcheck apps, since my boot is already patched once magisk wont flash and advising me to flash stock boot image but i dont know which to flash as with oreo there seems to be different partitions and i dont know commands other than basic fastbbot commands to flash stuff.
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
lingarajug said:
ok so i was able to flash ramdisk, recovery and system and boot back to OS ( i have earlier erased system by mistake) and i have flashed system.img from updated firmware but version still shows old one, and i am trying to use funkyhuawei erecovery method to flash the updated firmware and when i boot to erecovery to update but the update button is missing and i just have rebbot, wipe date/fr and wipe cache, so what do i need to flash and commands for it in order to make erecovery work and i have update button enabled, thank you.
Click to expand...
Click to collapse
If you can, use the HWOTA method instead. It's free and found: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
If you can't use HWOTA and have to use Funky:
You seem to be in normal Recovery. You should see a button that says 'Download latest firmware', the one you're describing is showing buttons that are in normal Recovery.
Are you booting using Usb plugged in + vol up + power?
For some reason my phone would only boot to revovery and not erecocery, anyway i used hisuite method and was able to flash new firmware. Thank you.
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
elviss0812345 said:
I've just unbricked my Mate 10 pro via this method. Thank you Sir.
Click to expand...
Click to collapse
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Pretoriano80 said:
You bricked your device because you don't know what you are doing,not because of this guide.Oh,and i thought KangRom was responsible for bricking you device....anyone else to blame ?
Click to expand...
Click to collapse
elviss0812345 said:
My phone was bricked because of Lineage OS, and i unbricked with this guide. Read my post first.
Click to expand...
Click to collapse
lol,i've read "bricked"... .I apologize for that!:good:
There is no way at least for the US version to find firmwares shipped with phone until now, i figured it out by connecting phone to hisuite on PC and it showed update available and i clicked update and waited until download part of update process completed and then i went to documents folder and hisuite and the app stores the download there and it will have 3 zip files, u can copy them to a different place because once the update completes those files are deleted. Might be the same for other models if supported by hisuite.
Here https://playstoreappinstall.com/play-store-for-huawei/ more info
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
oslo83 said:
@lingaraguj not already listed there :
http://pro-teammt.ru/firmware-database/?firmware_model=ALP
?
Click to expand...
Click to collapse
US version firmware not listed, lots of international versions though.
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
lex71 said:
Not sure if this is the right place but where can I find the original Huawei OS it was shipped with? I installed Lineage and want to go back to Factory.
I just want to .img file. I have only unlocked the bootloader not rooted the phone.
Lack of camera and other features means I need to get back.
Any ideas?
Click to expand...
Click to collapse
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
dark3bod said:
can i flash everything in UPDATE.APP to go back to fully stock.
if i can what is the fastboot command for every one of them files like "fastboot flash ramdisk RAMDISK.img'?
ive mate 10 pro.
Click to expand...
Click to collapse
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
ante0 said:
It should say your current firmware (besides Lineage) in Settings -> (System?) -> About.
It's better to use:
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I'm not sure if symlinks will be set up correctly if you flash images directly. And some partitions can't be flashed from fastboot (like the erecovery ones)
Click to expand...
Click to collapse
@ante0
This man is a legend.........
I would like to express my gratitude in you answering my pms and assisting to get the device up and running.
If ever am in Sweden:silly: ill definitely buy you beeeeeeeeeeeeeeeeeeeeeeers
Thanks for the patience and the help you bring to us noobs bricking these bloody Mate 9's
Im now on lineage os. I didnt flash twrp and magisk. Can i only flash stock system.img to get fully stock. Or i have to flash ramdisk and boot first before system.img
WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.
Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.
Screenshot:
{
"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"
}
NOT WORKING:
- Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
- Samsung's Proprietary Apps
- In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
- Auto Brightness (The phone doesn't have the sensors for it anyway)
- On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
- VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....
WORKING:
- Everything Else
GITHUB:
Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
Kernel: android_kernel_samsung_universal3830-common
Instructions for Installation:
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.
- ROM
- Recovery / Recovery(for U6)
- Google Apps
- ADB
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.
<CONTINUED ON THE NEXT POST>
15. If everything goes right, the device should show "script succeeded: result was [1.000000]" While ADB may show errors such as "Failed to read command" at 47%, this is no problem as long as the device says that the script succeeded.
16. Now it is time to install Google apps. On the phone, tap on Apply from ADB again, and on the computer, type "adb sideload <the path where you saved Google apps to>" and press enter.
17. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon shown below.
18. Choose Wipe data/factory reset, and reboot the device.
19. If everything went well, the phone should reboot into LineageOS. Set up the device and Enjoy!
ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18
On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
Therefore, you DON'T need to use a version that has been modified for A21s.
If you want to have root, you can get the Official Magisk App.
1. Download & Install Magisk from the official source.
2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
3. Enable developer settings (Settings->About phone->Tap on build number)
4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
5. Connect the phone to the PC.
6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
" *** records in
*** records out
*** bytes (** M) copied, *** s, **M/s"
8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.
Good news. Thank you very much
Then, my friends, write here how it works and thank you for your observations
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Pharcanal40 said:
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Click to expand...
Click to collapse
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Gxzllen said:
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Click to expand...
Click to collapse
A217F on U5
Pharcanal40 said:
A217F on U5
Click to expand...
Click to collapse
Can i download it on u6?i'm afraid my phone brick if i do it
Gxzllen said:
Can i download it on u6?i'm afraid my phone brick if i do it
Click to expand...
Click to collapse
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
grccorps said:
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
Click to expand...
Click to collapse
nice thankyou bro
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Pharcanal40 said:
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Click to expand...
Click to collapse
Ohh okay its easy this way
Can I use adb fastboot instead of Odin?
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Thank you for your review. It's such a great news that it's working on U6.
Yes, PUBG is a hell of a game, Krafton has done such a great job with it The kernel has newer mali graphics driver (R26P0 -> R31P0), maybe that could've done the trick (or it may just be due to LineageOS being much, much lighter than One UI)
How is the battery? While I wasn't able to find any abnormal battery drains (both in standby and stress conditions), I'm concered about how it would perform in other devices.
NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exchange?
Phuc230204 said:
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exc(hange?
Click to expand...
Click to collapse
First look on A21s LineageOS 18.1
hi,so i get this message "only official released binaries are allowed''in download mode,after the vbmeta failed...
SM-A217F/DSN
and in frp hijacker i get ''check device connection or com ports''
Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?