Related
★ [ROM] ICS alpha ★ Latest update: 14/01/12 ★ [TUT] Unbrick ★ Kernel sources ★
Instructions, as given by NotionInk via support mail, to bring your Adam back to life.
For the latest official rom-update & kernel source refer to the second post.
(Advanced users can directly jump to its last paragraph!)
How to flash your Adam and get it working again
WARNING
This fix is recommended only if your Adam has stopped booting up after installing the over-theair
system update on 24 January. Please don't use the method indicated to flash your Adam
with any ROM not from Notion Ink, as it would probably damage your Adam irreparably.
Please read this whole document before proceeding.
PRE-REQUISITES
You need to have the following items
1. A Windows or Linux PC
2. The Notion Ink Adam you wish to flash
3. A mini-USB to USB cable for connecting the two
(It's not included in the Adam package, but you
might have one lying around. If not, it's readily
available in any electronics shop)
4. The appropriate Adam Recovery Kit which you
can download from the URLs below. (About
80MB)
DOWNLOADS
1. Windows PC, LCD Adam http://api.notionink.com/fix/windows/LCD.zip
2. Windows PC, Pixel Qi Adam http://api.notionink.com/fix/windows/PixelQi.zip
3. Linux PC, LCD Adam http://api.notionink.com/fix/linux/LCD.zip
4. Linux PC, Pixel Qi Adam http://api.notionink.com/fix/linux/PixelQi.zip
OVERVIEW
Here's a summary of what you'll be doing:
1. On your PC, extract the Adam Recovery Kit.
2. Restart your Adam in “Force Recovery” mode and connect it to the PC.
3. If you're on Windows, install the USB drivers from the Recovery Kit.
4. Run the ROM flash utility from your PC, and wait for it to complete.
1. EXTRACT
Using your favourite ZIP extraction tool, uncompress all the files in the Adam Recovery Kit to
any folder on the hard drive of your computer.
2. RECOVERY MODE
Before proceeding, ensure that your Adam has at least 50% battery charge or is connected to
power and charging. Also make sure that your computer will not turn off during the flashing
process.
Turn off your Adam and enter force recovery mode by pressing and holding both the Volume
Down (-) and Power buttons for two seconds. The orange (charge) and red (CPU) indicators on
the right side of your device will light up, indicating that your Adam is in force recovery mode.
Release both buttons, and connect the mini-USB port on your Adam to any free USB port on the
PC using your cable.
3. INSTALL DRIVERS (Windows only)
Your Windows PC will show a notification that a device “APX” has been detected. If you get a
“Found new hardware” dialog box asking where to install drivers from - choose “list or specific
location”. If you don't get this dialog, open the Device Manager via System in the Control
Panel, find and double-click the “APX” device, and click the update driver button.
Select the “usbpcdriver” folder inside the extracted Adam Recovery Kit as the driver location.
You may receive a warning that the driver is not certified or signed by Windows – choose to
install it anyway.
4. FLASH
You're now ready to flash your Adam. Make sure that the USB cable is connected securely. To
begin the process under Windows, run the “download.bat” batch file from the folder where you
extracted the Recovery Kit. If you're using Linux, open a console window at the folder
containing the extracted Recovery Kit, and run ./download.sh. Your device screen will show that
it is being updated, and the console window will show the progress.
IMPORTANT: Do not close the console window or stop the update before it is complete. If the
update is interrupted mid-way, your Adam will be damaged irreparably.
Hopefully all goes well, and in a couple of minutes your Adam will boot up with the new
software. Congratulations! If at any point you find that things aren't going according to plan,
please send an email to [email protected] rightaway.
Thanks for your continued support
Team Notion Ink
Click to expand...
Click to collapse
Latest official rom update & instructions as given by NotionInk support:
Greetings from Notion Ink!
We are glad to inform you that an update for your Adam is now available.
Please click on the appropriate link provided below, based on your Adam variant and your current Operating System to download the update file.
LINUX
http://notionink.com/45-flash/flash_3gAUO.zip For LCD WiFi 3G
http://notionink.com/45-flash/flash_wifiAUO.zip For LCD WiFi
http://notionink.com/45-flash/flash_wifiPQ.zip For Pixel Qi WiFi
http://notionink.com/45-flash/flash_3gPQ.zip For Pixel Qi WiFi 3G
WINDOWS:
http://notionink.com/windows/flash_3gAUO-W.zip For LCD WiFi 3G
http://notionink.com/windows/flash_wifiAUO-W.zip For LCD WiFi
http://notionink.com/windows/flash_wifiPQ-W.zip For Pixel Qi WiFi
http://notionink.com/windows/flash_3gPQ-W.zip For Pixel Qi WiFi 3G
In order to update your Adam, you would have to follow a few simple steps detailed in the manual below.
You can download the manual here http://notionink.com/45-flash/Instruction-Manual.pdf.
All the necessary information required to update your Adam are present in these files.
Please note, that after this update, you would be able to install all subsequent updates using the 'Update Adam' feature under Settings.
A summary of the fixes in this update can be found here http://notionink.com/45-flash/Update-Summary.pdf.
In case you need any assistance, please contact us at [email protected]
Warm Regards
Notion Ink
Click to expand...
Click to collapse
The above update will enable the inbuilt Adam update feature.
From here onwards all coming updates can be done directly by Adam OTA (Over The Air).
Just follow the instructions below.
Dear Customer,
Greetings from Notion Ink!
We are glad to inform you that an update for your Adam is now available.
In order to update your Adam, you would have to follow a few simple steps detailed below.
Your Adam will need to be connected to a wi-fi network in order to download your update.
CHECK! Navigate to Settings > About Adam, and check the 'Build Number. Is it NIA20270111 / NIA20040211 / NIP20270111 / NIP20040211 (or higher)
If yes, then proceed.
If no, please install the previous update we had made available.
IMPORTANT! Please back up all your data on the Adam before attempting this update. We also recommend that you connect your Adam to the mains power supply during the update process.
CHECK! Please make sure that you have set the correct date and time on your Adam before your proceed with this update. (Settings > Set Date & Time)
Please follow these steps to update your Adam.
1. Restart your Adam.
2. Navigate to Settings > Update Adam and tap on it.
3. Now, a dialog box will open saying there is an update available for download. You can choose whether to start the download or cancel it.
4. Once you tap on 'Start' in the dialog box, your Adam will start downloading the update file. You can view the progress of this download in the notification bar.
5. Once the download is finished, a message will appear in the notification bar saying that your update is ready for installation. You can either choose to apply this update or choose to install it at a later time, in which case you can do so following the same steps above.
6. The update will now install and your Adam will restart.
You can also pause / resume your download by tapping on the download progress bar under notifications.
In case you need any assistance, please contact us at [email protected]
Warm Regards
Notion Ink
Click to expand...
Click to collapse
Latest official rom (NIxx20080611):
http://notionink.com/updates1/a0/update.zip For LCD WiFi
http://notionink.com/updates1/auo/update.zip For LCD WIFI & 3G
http://notionink.com/updates1/update.zip For Pixel Qi WiFi
http://notionink.com/updates1/PQ/update.zip For Pixel Qi WiFi & 3G
Kernel Source:
https://github.com/notionink
Gingerbread pre-alpha ROM (nvflash only):
http://developers.notionink.com/testimage23/2.3prealpha/nvflash.zip
UPDATE:
ICS Android 4.0 Alpha:
https://github.com/rrathi/adamICSImage
Gapps (flash after ROM for market access, gmail etc.):
http://www.multiupload.com/A2M9OB4FSS
Kernel:
https://github.com/EnJens/android-tegra-nv-2.6.39
Adam ICS Source:
https://github.com/rrathi/adamICS
It probably makes more sense to keep the first post up to date with the latest links... in case someone comes here from a Google search, you wouldn't want them flashing their Adam with old firmware if they were just quickly reading through the thread.
There is a file called "microboot.bin", which is only present in the "fix-rom" and not in the "update-rom".
I don´t know about its importance to properly revieve a semi-bricked adam, but that´s why i was hesitant to just update the links and made a second post instead.
If someone could maybe clarify it´s importance in the "fix-rom"?!
THX ;-)
Good stuff, thanks for your work in gathering this info.
Need help... Recovery may be borked
Got my adam yesterday... booted it up, connected to wifi, and installed the OTA update. Played around a bit, everything working ok, then copied some files over via usb to see if I could side load some apps.
Adam did not recognize my new microsd card, so I removed the microsd and powered down, then booted into recovery.
I got an error message in recovery:
E:Can't mount /dev/block/mmcblk3p1
(no such file or directory)
E:Can't mount SDCARD:recovery/command
Then, put the new sd card back in, rebooted to recovery again, got the same messages, and an additional "Can't mount SDCARD2".
Took the sdcard out, rebooted, surfed the net, etc... Then rebooted to recovery again and got:
E:Bad boot image
"ions"
E:Can't mount /dev/block/mmcblk3p1
(no such file or directory)
E:Can't mount SDCARD:recovery/command
So... I find this thread, followed the directions to a tee. Saw all the right things on the computer and on Adam.
Adam rebooted at the end and went back to the home screen. Surprise! Nothing was overwritten... same bookmarks in browser, same wifi connection, etc...
So I boot into recovery and get the same error as the top one above.
Did NI change / lock the recovery? ...it says (3e) and/or did something get sideways here that I don't know about? Why did I not get a clean install after following the steps above?
Is there a way to just re-push the stock recovery (or clockworkmod) via adb or nvflash?
Any help would be appreciated...
ssmithri said:
Is there a way to just re-push the stock recovery (or clockworkmod) via adb or nvflash?
Any help would be appreciated...
Click to expand...
Click to collapse
You should be able to update to ClockworkMod even with those error messages. You can either copy the update.zip to your SD card or copy it directly to the root of the Adam memory. Then run the update using the stock recovery via Volume + and Power.
joshua.lyon said:
You should be able to update to ClockworkMod even with those error messages. You can either copy the update.zip to your SD card or copy it directly to the root of the Adam memory. Then run the update using the stock recovery via Volume + and Power.
Click to expand...
Click to collapse
Agreed... but I have tried that.
When I do apply internal sdcard:update.zip, a little droid just sits there staring at me... forever...
ssmithri said:
Agreed... but I have tried that.
When I do apply internal sdcard:update.zip, a little droid just sits there staring at me... forever...
Click to expand...
Click to collapse
I had the same thing happen to me. If I remember correctly, I actually had to use the power button as the "select" button. Using the menu button would just give me the blank screen with just the droid staring back.
Additionally, after doing the update to ClockworkMod (and subsequently installing EdenX), I had to use the Clear Cache feature of ClockworkMod to get the tablet to boot into the regular OS. Before clearing the cache, each time I would power on the device it would just boot into recovery mode.
PS. I was in the latest batch that was shipped -- just got mine yesterday. In the original Dec 9 order and "shipped" Feb 14.
joshua.lyon said:
If I remember correctly, I actually had to use the power button as the "select" button. Using the menu button would just give me the blank screen with just the droid staring back.
Click to expand...
Click to collapse
That was it!!!
Thank you so much
I tried unbricking but after the formatting part I get the following error.
sending file: bootloader.bin
| 941356/941356 bytes sent
bootloader.bin sent successfully
sending file: mbtdata.img
- 1024/1024 bytes sent
mbtdata.img sent successfully
sending file: recovery.img
| 3860480/3860480 bytes sent
recovery.img sent successfully
sending file: boot.img
- 3184640/3184640 bytes sent
boot.img sent successfully
sending file: system.img
| 458752/128154048 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Any idea what this means? Any help anyone?
Sounds like your image is corrupted. Would try to redownload the files. ;-)
halcyon13 said:
I tried unbricking but after the formatting part I get the following error.
sending file: bootloader.bin
| 941356/941356 bytes sent
bootloader.bin sent successfully
sending file: mbtdata.img
- 1024/1024 bytes sent
mbtdata.img sent successfully
sending file: recovery.img
| 3860480/3860480 bytes sent
recovery.img sent successfully
sending file: boot.img
- 3184640/3184640 bytes sent
boot.img sent successfully
sending file: system.img
| 458752/128154048 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Any idea what this means? Any help anyone?
Click to expand...
Click to collapse
Happen to have links to the update.zip files for each?
when trying to run download.sh in ubuntu, i get this error...
./nvflash: command not found
Internal SD card
joshua.lyon said:
You should be able to update to ClockworkMod even with those error messages. You can either copy the update.zip to your SD card or copy it directly to the root of the Adam memory. Then run the update using the stock recovery via Volume + and Power.
Click to expand...
Click to collapse
Mine did the same until I had Win 7 repair the internal SDcard. Others had told me to wipe it. After that no problemos.
First post updated with Ice Cream Sandwich pre-alpha ROM incl. kernel & source
Post 1, as seen on here as well http://notioninkhacks.com/forums/viewtopic.php?f=63&t=327&hilit=unbrick does what you want. The bin file in here has nvflash. I did roughly the same as you, hadn't turned on the Adam for ages, had to nvflash it before doing the ICS update. Make sure you put the ICS files on the internal SDCARD, I got those mount errors as well all the way through
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!!
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.
This is the well-established way to flash factory images without waiting for the OTA, using a Windows computer.
You can have a custom recovery, but you must otherwise be stock.
Your bootloader must be unlocked.
You should not lose apps (except for non-stock system apps) or data, but don't hold me responsible if you do.
You will have to reload non-stock system apps like Xposed framework (in fact, I uninstalled the Xposed framework using the Xposed framework installer before starting this process).
This is a modification of the process explained here, which I have mostly cut-and-pasted:
http://forum.xda-developers.com/nexus-4/general/flash-android-4-3-build-clean-flash-t2376681
(Credit to mc704.)
1. You must have ADB, fastboot, and USB drivers for the N4 on your PC. Not hard to find; the thread referenced above tells you one way to get them. Put adb.exe, fastboot.exe, AdbWinApi.dll, and AdbWinUsbApi.dll in a folder on your PC - let's call it C:\N4Update
2. Enable USB Debugging via Developer settings on your phone.
3. The Nexus 4 (mako) 4.4.3 image can be obtained from Google
Image Link: https://developers.google.com/android/nexus/images#occamktu84l
Step 1: Use 7zip or an equivalent compression program to extract the stock 4.4.3 image file that has extension .TGZ
Step 2: You should see a stock image file that has extension .TAR...extract this once again with 7zip (or equivalent) into C:\N4Update
Step 3: Plug your device into the PC (USB debugging should be enabled)
Step 4: Launch command prompt from C:\N4Update, or alternatively start a command prompt (start --> run --> "cmd") and cd to it (cd C:\N4Update)
Step 5: Verify that the PC is detecting your device by typing in command prompt "adb devices" (you should see a code representing your device, and then "device" following it); if not, recheck usb debugging, and unplug and replug the phone back into your PC
Step 6: Turn your N4 off and go into fastboot (bootloader) mode (hold power button + Volume Up & Down all together)
Step 7: Type in the command prompt each step one at a time and wait for it to complete (obviously, don't enter the quotation marks):
"fastboot flash bootloader bootloader-mako-makoz30d.img"
"fastboot reboot-bootloader"
"fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img"
"fastboot reboot-bootloader"
"fastboot update image-occam-ktu84l.zip"
Step 8: At this point, your N4 will reboot. This will take some time as your apps are re-initialized, but it should be clear what's going on.
Step 9: You will now have 4.4.3. You will be unrooted and have stock recovery. If you want, you can stop here.
If you want to install the TWRP custom recovery and regain root:
Step 10: Download the new version of SuperSU onto the N4 from here: http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Step 11: Download TWRP onto your PC in C:\N4Update from here: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.7.0.0-mako.img
Step 12: Boot N4 back into fastboot (bootloader) mode while connected to the PC.
Step 13: With the command prompt from Step 4 above, type "fastboot flash recovery openrecovery-twrp-2.7.0.0-mako.img"
Step 14: Boot from the bootloader into Recovery by pressing volume up to display "Recovery" and then the power button to select.
Step 15: Use TWRP to install the zip (SuperSU) file from Step 10 to regain root.
Step 16: Reboot system.
You should now have a rooted system, with all of your old apps and data (except for system apps, which need to be reinstalled), and the latest TWRP custom recovery.
Don't wanna sound rude, but is there point in creating another how-to thread, along the other threads which some(link) are even mentioned in sticky roll-up threads? Plus it's 99% copy/paste, which you even mention so that's nice from you.
It's nice that someone have will to write(or even copy/paste/edit) tutorials, but by having more threads help is harder to find(search).
Just my humble opinion and experience
Also you can jsut remove the recovery img from the update package to keep your custom recovery
well I for one appreciate you posting this as now I don't have to search all over gods creation to find the old thread
Nevermind
i did all steps... but im spammed google now launcher has stopped
will factory reset help?
Night5talker said:
i did all steps... but im spammed google now launcher has stopped
will factory reset help?
Click to expand...
Click to collapse
Factory reset seems extreme. How about just uninstalling and reinstalling the launcher? (I assume the stock launcher still works.)
NYZack said:
Factory reset seems extreme. How about just uninstalling and reinstalling the launcher? (I assume the stock launcher still works.)
Click to expand...
Click to collapse
i did factory reset but apps did left on my phone storage and when i turned it on google play started to download it everything again
ps couldnt do anything it was poping right back up wheni press ok even if i go to another launcher
Night5talker said:
i did factory reset but apps did left on my phone storage and when i turned it on google play started to download it everything again
ps couldnt do anything it was poping right back up wheni press ok even if i go to another launcher
Click to expand...
Click to collapse
Well, sorry, don't quite understand: you could always just uninstall the Google Now launcher, make sure everything else is working, and then reinstall it once you confirm there's no other problem.
Anyone could just mention the procedure for doing same thing but through Wug toolkit.
In general I prefer to avoid fastboot commands and flash everything though pc.
Unleashed by my Nexus 4
No need to do all these steps (flashboot). They included scripts that will run all things
On Windows you can just run "flash-all.bat" or on Unix "flash-all.sh".
DarsVaeda said:
No need to do all these steps (flashboot). They included scripts that will run all things
On Windows you can just run "flash-all.bat" or on Unix "flash-all.sh".
Click to expand...
Click to collapse
Yeah but edit it with notepad and remove the -w flag to disable the wipe also remove the recovery.img from the zip to keep the custom recovery !
mashedbymachines said:
Yeah but edit it with notepad and remove the -w flag to disable the wipe also remove the recovery.img from the zip to keep the custom recovery !
Click to expand...
Click to collapse
Yeah, this is the key point - if that -w flag is not removed, you will lose all apps/data. One of the reasons I put this up is that I think the step-by-step method is interesting, instructive (you can see what's actually happening), not much more time-consuming than running the automated script, and lets you have more granular control.
(And I apologize if it's littering the forum and semi-plagiarism, but I thought a very detailed, confirmed step-by-step guide with up-to-date precise download links might be useful to people who haven't gone through the process before.)
What the ....
So I edited my flash-all.bat and removed the -w
It looks like this:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-occam-ktu84l.zip
echo Press any key to exit...
pause >nul
Click to expand...
Click to collapse
And yet my phone was wiped.... sigh
** Update **
Nevermind, it was Notepad++ that screwed me over. The changes to the bat file was not written to the file, only kept in Notepad++'s temporary memory. ****ing bull**** feature.
Erroneus said:
What the ....
So I edited my flash-all.bat and removed the -w
It looks like this:
And yet my phone was wiped.... sigh
** Update **
Nevermind, it was Notepad++ that screwed me over. The changes to the bat file was not written to the file, only kept in Notepad++'s temporary memory. ****ing bull**** feature.
Click to expand...
Click to collapse
so in order to run this comand you only need to unzip the tar(?) file downloaded and then you are done, you don't have to unzip the actual factory image, correct?
fdg59 said:
so in order to run this comand you only need to unzip the tar(?) file downloaded and then you are done, you don't have to unzip the actual factory image, correct?
Click to expand...
Click to collapse
Actually, you have to run the unzip program twice:
For example, when updating to Android version 4.4.4 (Yes, a new version has already been released since this post):
Here is the downloaded file
occam-ktu84p-factory-b6ac3ad6.tar
Unzipping it will give you this:
occam-ktu84p-factory-b6ac3ad6
And unzipping that one more time will give you the directory "occam-ktu84p" containing the following files:
bootloader-mako-makoz30d.img
flash-all.bat
flash-all.sh
flash-base.sh
image-occam-ktu84p.zip
radio-mako-m9615a-cefwmazm-2.0.1701.03.img
WARNING: As was mentioned many times, remove the -w from the following line in the flash-all.bat file unless you intend to wipe your phone clean. I don't understand the issue with Notepad++ noted in a previous post, as you have to hit "save" like any other program (It is the program that I use as well).
fastboot -w update image-occam-ktu84p.zip
If what you were really asking is whether you need to unzip the file image-occam-ktu84p.zip.......The answer is no.
ah ah yes 4.4.4, that's why i am asking, because i always used to unzip everything and the flash items individually using fastboot which i always liked. The problem however was that my nexus 4 has 16gb and after flashing and wiping everything clean the memory showed up at 8gb so i had to factory reset through stock recovery which i didn't enjoy as much. thanks for all the help!
Read this whole guide before starting.
This is for the 2nd gen Fire TV (sloane)
Current relase: amonet-sloane-v1.1
NOTE: This process does not require you to open your device if you're already rooted or you have TWRP.
NOTE: If something goes horribly wrong and your device gets bricked, you'll have to open it and unbrick it through bootrom (post 2).
NOTE: This process will modify the partition-table (GPT) of your device.
NOTE: Your device will be reset to factory defaults (including internal storage) during this process.
NOTE: Flashing prerooted ROM will disable unlocked TWRP. It's recommended to flash an stock update.bin until that gets sorted out.
To update to the current release if you are already unlocked, just flash the zip in TWRP.
What you need:
A Linux installation or live-system
A a-a cable
1. Download the attached zip-file "amonet-sloane-v1.1zip".
2. Copy the zip-file to the internal storage of the box or copy the zip-file to an external SD/USB storage and connect it to the box.
3. Reboot the FireTV to rbox's TWRP recovery and flash the zip-file.
NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you need to continue with bootrom-step-minimal.sh:
NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip once you're in TWRP.
Once the zip-file finished flashing, disconnect the device and run:
Code:
sudo ./bootrom-step-minimal.sh
Then plug the device back in.
The device will reboot to hacked fastboot mode (Static Amazon White Logo + white blinking LED).
Then run:
Code:
sudo ./fastboot-step.sh
After that, the device will reboot to unlocked TWRP. Then go to Wipe > Format Data and type "YES".
You can now install Magisk from there.
Important information
NOTE: This has nothing to do with the unlock process.
You have 10 seconds to force TWRP to keep ADB over USB active by using
Code:
adb wait-for-recovery && adb shell setprop twrp.usb.mode 0
In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)
Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
Very special thanks to @k4y0z and @t0x1cSH for making all this possible by porting the LK exploit to sloane and implementing the RPMB-key derivation for sloane.
Special thanks also to @xyz` for making all this possible and releasing the original amonet exploit for karnak.
Special thanks also to @retyre for porting the bootrom-exploit to mt8173.
Special thanks also to @Sus_i and @DanielF50 for testing.
Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
Unbricking / Unlocking with non-rooted Firmware
Prepare the environment, disable modemmanager and install the required packages:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip linked in the first post (OP).
If FireOS is still accessible there are other means of recovery, don't continue.
If your device shows one of the following symptoms:
It doesn't show any life (screen stays dark)
You see the white amazon logo, but cannot access FireOS.
If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
Unplug the device from the wall
Start bootrom-step.sh
Plug in the power source and then the USB
NOTE: If you have issues running the scripts, you might have to run them using sudo.
Also try using different USB-ports (preferably USB-2.0-ports)
1. Extract the attached zip-file "amonet-sloane-v1.1.zip" and open a terminal in that directory.
2. Start the script:
Code:
sudo ./bootrom-step.sh
It should now say Waiting for bootrom.
3. Connect the USB A-A cable, short the board according to the picture (DAT0 with GND), and connect the power supply.
4. When the script asks you to remove the short, remove the short and press enter.
5. Wait for the script to finish.
If it stalls at some point, stop it and restart the process from step 2.
6. Your device should now reboot into unlocked fastboot state.
7. Run
Code:
sudo ./fastboot-step.sh
8. Wait for the device to reboot into TWRP.
9. Format data and use TWRP to flash a custom ROM, Magisk or SuperSU.
Checking USB connection
In lsusb the boot-rom shows up as:
Code:
Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.
dmesg lists the correct device as:
Code:
[ 6383.962057] usb 2-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
Unlocking with ADB + root
NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
1. Extract the attached zip-file "amonet-sloane-v1.0.1.zip" and open a terminal in that directory.
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
2. Enable ADB in Developer Settings.
3. Start the script:
Code:
sudo ./step-1.sh
Your device will now reboot into recovery and perform a factory reset.
NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you need to continue with bootrom-step-minimal.sh:
NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip once you're in TWRP.
Once the zip-file finished flashing, disconnect the device and run:
Code:
sudo ./bootrom-step-minimal.sh
Then plug the device back in.
The device will reboot to hacked fastboot mode (Static Amazon White Logo + white blinking LED).
Then run:
Code:
sudo ./fastboot-step.sh
After that, the device will reboot to unlocked TWRP. Then go to Wipe > Format Data and type "YES".
If you used this method (brick), you're done with the unlock. Skip the step 4.
NOTE: Make sure you re-enable ADB after Factory Reset.
4. Start the script:
Code:
sudo ./step-2.sh
The exploit will now be flashed and your device will reboot into TWRP.
You can now install Magisk from there.
There are three options for interacting with TWRP:
A mouse/keyboard via USB
ADB over ethernet/USB
TWRP commandline via adb: https://twrp.me/faq/openrecoveryscript.html
Via /cache/recovery/command
Example for /cache/recovery/command:
Code:
echo "--update_package=/path/to/zipfile" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
If you somehow end in a bootloop you can boot into hacked fastboot or recovery using.
Code:
sudo ./boot-fastboot.sh
Code:
sudo ./boot-recovery.sh
NOTE: This will only work if the boot-exploit is still there.
Source Code:
https://github.com/chaosmaster/amonet-sloane
https://github.com/R0rt1z2/android_device_amazon_sloane
https://github.com/chaosmaster/android_bootable_recovery
Reserved
Nice to see this released - it's been a while in the making... just glad that me and my multiple sloanes could be of service to the community
edit: obviously Magisk works with a full unlock, but as Rortiz2 states above this must be flashed to boot_x - I would advise you pull your ROM's boot.img, patch it with MagiskManager & then flash this manually via hacked fastboot, otherwise it won't work & you'll probably brick your device again.
DanielF50 said:
Nice to see this released - it's been a while in the making... just glad that me and my multiple sloanes could be of service to the community
Click to expand...
Click to collapse
Yeah I'll second that, It works perfect and flawlessly. Be sure to follow the guide to the letter ..... .... It's good to see development continue to make progress on what I would say is the best amazon device of them all.
Well done. All your hardwork is greatly appreciated. @k4y0z , @Rortiz2 , @t0x1cSH, @Sus_i , @retyre , @diplomatic @DanielF50 without you guys continued attention and testing of these sticks/boxes we would be stuck with plain old boring devices.
Cheers again
regards
DanielF50 said:
I would advise you pull your ROM's boot.img, patch it with MagiskManager & then flash this manually via hacked fastboot, otherwise it won't work & you'll probably brick your device again.
Click to expand...
Click to collapse
Don't worry, magisk flashing in TWRP works (now).
Time to pull the Sloanes out of the drawer!
Ok, so I ran into some issues. I flashed the zip in the pre-rooted TWRP. No errors and reboots into unlocked TWRP. From unlocked TWRP i format data and type yes, then reboot. Now i am at the black amazon fire logo and nothing happens. I think i missed or didnt understand the downgrading part to older than 5.2.7.3. So, i think i have to do the shorting method now? Also, does anyone know where i can find a old version <5.2.7.3 .bin to flash? Is there anyway to get back into unlocked TWRP now?
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.7.0-rooted_r1.zip
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.6.7-rooted_r1.zip
All here, scroll down
Fire TV & Fire TV Stick Downloads: APKs von Apps & Games
Fire TV Downloads Sammlung von Android Apps (APK-Dateien), die man herunterladen und auf dem Amazon Fire TV und Fire TV Stick 4k installieren kann.
aftvhacks.de
0815hoffi said:
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.7.0-rooted_r1.zip
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.6.7-rooted_r1.zip
All here, scroll down
Fire TV & Fire TV Stick Downloads: APKs von Apps & Games
Fire TV Downloads Sammlung von Android Apps (APK-Dateien), die man herunterladen und auf dem Amazon Fire TV und Fire TV Stick 4k installieren kann.
aftvhacks.de
Click to expand...
Click to collapse
Thanks, great resource. I am looking for stock though...
" NOTE: Flashing prerooted ROM will disable unlocked TWRP. It's recommended to flash an stock update.bin until that gets sorted out. "
Michajin said:
Ok, so I ran into some issues. I flashed the zip in the pre-rooted TWRP. No errors and reboots into unlocked TWRP. From unlocked TWRP i format data and type yes, then reboot. Now i am at the black amazon fire logo and nothing happens. I think i missed or didnt understand the downgrading part to older than 5.2.7.3. So, i think i have to do the shorting method now? Also, does anyone know where i can find a old version <5.2.7.3 .bin to flash? Is there anyway to get back into unlocked TWRP now?
Click to expand...
Click to collapse
If the zip flashed fine forget about the downgrading part. Are you able to boot unlocked TWRP using boot-recovery.sh?
Here's an stock update.bin: https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.4.8_user_648594820.bin
Rortiz2 said:
If the zip flashed fine forget about the downgrading part. Are you able to boot unlocked TWRP using boot-recovery.sh?
Here's an stock update.bin: https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.4.8_user_648594820.bin
Click to expand...
Click to collapse
yes, boot-recovery works perfect. That is exactly what I needed thanks!
In case someone needs some newer 'full OTA update' packages of the stock rom, only for sloane:
Fire OS 5.2.7.3 (652614020).
https://d1s31zyz7dcc2d.cloudfront.net/7af0a9a31621db60bf48d23e680751d3/update-kindle-full_sloane-36.6.5.2_user_652614020.bin
Fire OS 5.2.7.4 (656638420).
https://d1s31zyz7dcc2d.cloudfront.net/7758ad70f668023cc93ddee2655c6226/update-kindle-full_sloane-36.6.5.6_user_656638420.bin
Fire OS 5.2.7.6 (659654620).
https://d1s31zyz7dcc2d.cloudfront.net/c5b513d2116f5ad2942426ab79bb437b/update-kindle-full_sloane-36.6.5.9_user_659654620.bin
5.2.7.6 is the latest OS (as of today).
Don't forget to rename the file, i.e. .bin to .zip.
Sus_i said:
Don't worry, magisk flashing in TWRP works (now).
Click to expand...
Click to collapse
Oh, awesome news!
Hey guys, So do users of the new unlocked twrp to only use the clean update.bin files provided by @Sus_i and not the rbox prerooted stock (supersu) roms? Just to clarify for the sake of Magisk clashing with Supersu prerooted firmware incase it throws some nasty surprises.
Regards
Next OTA update incoming...
Full OTA update package (latest stock) for sloane:
Fire OS 5.2.7.7 (662663720).
https://d1s31zyz7dcc2d.cloudfront.net/b9f7c8f9a8a4ba1f34da8ce7a8077474/update-kindle-full_sloane-36.6.6.2_user_662663720.bin
Sus_i said:
Next OTA update incoming...
Full OTA update package (latest stock) for sloane:
Fire OS 5.2.7.7 (662663720).
https://d1s31zyz7dcc2d.cloudfront.net/b9f7c8f9a8a4ba1f34da8ce7a8077474/update-kindle-full_sloane-36.6.6.2_user_662663720.bin
Click to expand...
Click to collapse
5.2.7.7 yipeee
Seconds later bootloader is locked lol
I'm currently on 5.2.7.4 I think I'll stay there. This is the os before big A started messing with adb and accessibility (launchers) you can just disable launcher and firehomestarter apk provided there is a settings apk installed (hoffis is great).
lol