Related
Hello all.
I've compiled the latest ClockworkMod recovery for the Tattoo. In addition to the normal features it has, this is using a custom smaller font, so the text fits better on a QVGA screen.
If you're already rooted, you can flash it with "flash_image recovery recovery.img" (after running "su" first) from a terminal shell prompt, or from adb shell.
v2.5.1.8 is the last version included in CyanogenMod 6 sources
v3.0.0.5 is the new recovery from CyanogenMod 7 sources
How to flash instructions
Credits:
CM Team/Koush
KalimochoAz
NForce2506.02.2011 - Repack of 3.0.0.5 with advanced backup and wipe all function. Wipe all will completely format and erase all partitions.
Can you please tell me, in what way exactly is this Recovery better than Amon-RA?
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
arco68 said:
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
Click to expand...
Click to collapse
Is possible to add Ps3 Jailbreaking?
francians said:
Is possible to add Ps3 Jailbreaking?
Click to expand...
Click to collapse
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
arco68 said:
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
Click to expand...
Click to collapse
I asked a couple of weeks ago, but no answer.. I realy like clockworkmod and I'm afraid to change recovery.
Thanks. Good job!
Amazing recovery
Thank you very very much for this recovery. ROM Manager now works properly. BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
sunitknandi said:
BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
Click to expand...
Click to collapse
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
ClockworkMod recovery for the Tattoo isn't added to ROM Manager yet. Until now Tattoo owners had to use the Wildfire/Buzz recovery. I'll contact the author and ask if he can add this recovery for the Tattoo, so it's available from ROM Manager.
Downloading images
arco68 said:
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
Click to expand...
Click to collapse
If I knew where the images were hosted, I could fetch them through PC.
sorhe said:
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
Click to expand...
Click to collapse
Press menu button and select "manually installed clockworkmod" or similar option.
sunitknandi said:
Press menu button and select "manually installed clockworkmod" or similar option.
Click to expand...
Click to collapse
That doesn´t help!
With clockworkmod recovery I cannot flash some roms which flashed fine with maverick recovery. The installation aborted with this error:
E:Board does not support mtd utils.E:Failure at line 420:
write_raw_image PACKAGE:boot.img BOOT:
The rom is actually flashed, and only boot.img not. So I can boot the rom after manually flash the boot.img.
Is there any way to include mtd utils future in this recovery, or must to return to maverick?
I think it's a bug in clockworkmod. They changed some detection routines in the latest versions, which seems to have broken flashing to mtd when rom is using update-script instead of updater-script. I've heard that 2.5.0.9 is the latest which it worked correctly with. I'll look into it at some point unless they release a new version which fixes it.
clockworkmod 2.5.1.4 seems to be already out!
arco68 please could you take a look here: https://github.com/klutsh/android_bootable_recovery
or here: https://github.com/klutsh/psfreedom-kernels-patch
could you add psFreedom support?
edit: please fix also the font size for the tattoo screen
I suppose it can be done, so I'll take a look. Thanks for the links.
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
arco68 said:
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
Click to expand...
Click to collapse
I think is very hard find what's missing to make it works.. can you do it?
I know you are workin' also on a wonderful rom, but also psfreedom is a nice project that need a skilled man
I see the kernel patches for the Tattoo is no longer there. When he adds a working patch I'll try again.
I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress
What you need if you want to root your Gingerbread rom:
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .
Final Update 1.21.2014 » Changelog.
For support beyond this guide, please look in another thread. I no longer have this product.
Thanks for all your support in this thread!
Bulletin Board
If your ROM has issues with root, see Fixing Root How-To for the solution.
-----------------------------
Common ICS issues FAQ by fred_be9300 here
------------------------------
NOTE: If you ever experience screen issues with the included CWM Recovery in the Toolkit, please flash the alternate version here or even better, flash TWRP (but be warned this guide's based on CWM).
Click to expand...
Click to collapse
This guide covers the following for models GT-P7300 and GT-P7310 in FAQ and How-TO sections:
Root/Unroot, Bootloader Mode, Odin, Recoveries & NANDROID Backup.
--------------------------------------------------
Greetings people. The main focus of this guide is centralizing information and files about the title contents to help bolster this community. I'll be as clear as possible in this little guide and excuse me if my English isn't perfect (it isn't my native language) and this is my first XDA guide. Oh and a little disclaimer: I AM NOT RESPONSIBLE IF YOU IN ANY WAY DAMAGE YOUR TABLET. BY FOLLOWING THIS GUIDE YOU ACCEPT FULL RESPONSIBILITY FOR YOUR ACTIONS. ALSO PLEASE NOTE THIS GUIDE HAS BEEN WRITTEN WITH A WINDOWS PC IN MIND. IF YOU DON'T HAVE A WINDOWS PC AVAILABLE, GET ONE, BORROW ONE, I DUNNO, but you need one. That said, let's begin.
--------------------------------------------------
FAQ Section
About Root
What exactly is root and what does it do in my Galaxy Tab 8.9?
XDA user phonic covered the technical details in this post, but basically root allows you to access and control (through applications) the device's internal system files, therefore making you a "superuser". Some apps require root. Advantages such as ad-blocking and more are only available if your device is rooted.
About Bootloader, Recovery & Download Modes
What is Bootloader Mode and how can I access it?
Bootloader Mode is a menu where you manage core functions in your device. In order to access Download Mode (needed for ODIN) and/or Recovery Mode (needed to flash ROMs and more), you will need to enter Bootloader Mode by holding VOL- when turning ON your Gtab, selecting the mode using VOL-, and entering by using VOL+. The box icon represents the Recovery Mode and the other one the Download Mode. While inside Recovery Mode, the Power button will act as an "Enter" button while the volume buttons will move the cursor.
I read something about Stock Recovery and CWM Recovery. What are those?
There are two types of recoveries. The default one that comes with your GTab (Stock Recovery which looks like this) and the CWM (Clockwork Mod) one which has cyan-colored letters for our GTabs. To flash ROMs and manage your device a bit more, you need the CWM one.[/U][/COLOR][/B]
Can I flash the CWM Recovery using the ROM Manager app? Oh and which file format is compatible?
Refrain from that. As of this writing, the ROM Manager app does not have a CWM Recovery compatible with our specific GTabs. If you still proceed, you will softbrick your device and your device will have to do a trip to ODIN in order to work properly once more. CWM-flashable files are .zip files.
About NANDROID Backup
What's NANDROID and why is it recommended?
Simple, a NANDROID is a master backup tool which is available through the CWM Recovery's "backup and restore" menu. It stores everything in the ROM except the kernel and your SDcard contents such as pictures, music, documents, etc (so always backup those elsewhere). It's more like this analogy: a photograph which captured the exact state of your ROM, apps and all at the moment of backup. It is recommended in case of emergency and in case you need to go back to the latest working ROM. How-To section below.
About ODIN
What's ODIN?
ODIN's a troubleshooting/emergency tool in case your GTab bootloops (eternal restarting of a device, i.e. softbrick). Please note that if your device's screen doesn't even turn on (an example of a hardbrick) then you may be out of luck. This tool can save your GTab if you follow instructions, or can hardbrick your GTab if you don't follow instructions.
Where can I find ODIN? Do I need something like a driver to make it work? Also, which file format is compatible?
Yes you do need a driver first (provided at the end of this guide) and a Windows PC. The ODIN program is inside the zip inside the Toolkit provided at the end of this guide. As suggested by developer alterbridge86, use ODIN version 1.85. Regarding file compatibility, generally the .tar files are the ones for ODIN.
Does it remove Root and custom recoveries such as CWM in case of a warranty claim?
Yes. There are two ways:
[*]Flashing an ODIN image to go back to stock defaults (easier in my opinion). If you want to use ODIN then you have options in the Development forum, specifically this thread.
OR
[*]Flashing a CWM zip file (CWM, which is a Recovery, will be discussed in the Recovery FAQ below) after doing all wipes and restoring Stock Recovery (Restoring Stock Recovery How-To is below these FAQs)
Ok, so how do I use the tool?
The How-to section is below the FAQs.
How-To Section
Remember, all files mentioned in this section this way are included in the Toolkit at the end of this guide.
[ Rooting ]:::::::::::::::::::::::::::::::::::::::::::
Make sure to download the Toolkit from the link at the end of this post and put the "Root" .zip in your device's internal memory. You will enter Bootloader Mode, and then Recovery Mode as detailed in the About Bootloader FAQ above. You will now select "install zip from sdcard" then "choose zip from sdcard" and look for the Root.zip which you previously put in your SDcard. Select it with the Power button to flash it and then reboot your device. When your device finally boots, check if the SuperSU app is available, if it is then you're rooted now.
[ Fixing Root ]:::::::::::::::::::::::::::::::::::::::::::
In some cases a ROM can come with a broken root due to the superuser binary being located in the wrong system folder. Please flash the Root.zip package in CWM Recovery. The Root package will delete the offending binary from the wrong place and install it in the right place. For more instructions, see Rooting How-to.
[Unrooting]:::::::::::::::::::::::::::::::::::::::::::
For unrooting, proceed to Bootloader Mode and select the Recovery icon (detailed in the About Bootloader FAQ above) please flash the CWM Recovery flashable file provided in the Toolkit link at the end of this guide called "Unroot". Now reboot your device. If there is no app called SuperSU or Superuser in your apps list, then your device is now unrooted.
[Installing the CWM Recovery]:::::::::::::::::::::::::::::::::::::::::::
First, you need the file called either "7310_CWMR" or "7300_CWMR" depending on your model, inside your device's SDcard. The procedure is very similar to Rooting and either procedure can be done first. Go to Bootloader Mode (as detailed in the FAQ above), then Recovery (assuming you've Stock Recovery), select "apply update from /sdcard", then look for the file you put in the SDcard. Select it with the Power button to flash it. Now, reboot once more to Bootloader Mode, go to Recovery Mode and now you will see the CWM Recovery Mode. You are now ready to flash stuff. Please note you don't need root to flash a ROM, just this CWM Recovery. Be sure to follow the ROM thread's instructions precisely.
[Restoring Stock Recovery]:::::::::::::::::::::::::::::::::::::::::::
For this one you will need to use ODIN. Locate the file "Stock Recovery", which is a .tar file, perfect for ODIN's PDA section. Follow the ODIN 1.85's HOW-TO below.
[Doing a NANDROID Backup/Restore]:::::::::::::::::::::::::::::::::::::::::::
You need CWM Recovery for this one. Once you're in CWM Recovery, the process is straightforward. Look for the "backup and restore" menu, access it and you will see two options: "backup" and "restore". Select "backup" and wait until the system gathers all data and packs it as a backup located in your internal memory, inside a folder called "clockworkmod". Once more, remember this will not backup your SDcard contents such as your documents, music, pictures, etc (so always have a backup of those elsewhere).
For restoring the process is the same. You need to do the following to ensure a proper restore and prevent issues that might pop up: Wipe your system using CWM Recovery's "wipe data/factory reset" and after that go to "advanced" and now "wipe dalvik cache". Now go to the "mounts and storage" menu and select "format /system". That was a full wipe. Now proceed to the "backup and restore" menu, select "restore" to select your backup. Remember to reflash the kernel if you had one that didn't come with the ROM (like _motley's for example).
[Using ODIN 1.85]:::::::::::::::::::::::::::::::::::::::::::
Enter Bootloader Mode and then Download Mode as detailed in the FAQ above. Be sure to have installed the drivers (included in the zip at the end of this guide) in your Windows computer along with the ODIN program anywhere in your PC (also included in the Toolkit at the end of this guide). Open ODIN 1.85 in your PC, look for the "PDA" button, press it and look for the right file (which usually is the biggest-size file inside the downloaded and unzipped ROM .zip). THE FOLLOWING THREAD OFFERS MOST ODIN IMAGES. IF AVAILABLE, put the CSC, PIT and whatnot files in their corresponding places by pressing the corresponding buttons (IF these files aren't available, ignore this sentence). The PIT file is only necessary in case you want to have the Repartition option available and want to repartition the device (this is an alternative that can work in case of a really borked tablet full of bootloops even after a normal ODIN session without Repartition). Now, assuming you have the drivers installed in your PC, connect the device while in Download Mode, and you will see that ODIN will see it in a yellow rectangle in the upper section that says COM# (# being any number). BEFORE CLICKING "START" MAKE SURE "F. RESET TIME" IS CHECKED ON THE LEFT SIDE. Now, click the START button inside ODIN and it's flashing time. Wait until the blue meter fills. After ODIN says PASS in a green square, you can then reboot the device (long pressing the Power button is an alternative if it doesn't auto-reboot).
Toolkit Link: shorturl.at/pqCIY
SHA-1: 4DC13D60280ECA6352704AA72153E5E4EDF875E0
MD5: 59CC2548FC76D93075FDF8B392DAA1AE
Contains essentials such as: Drivers, Root, Unroot, Stock Recovery, CWM Recovery & ODIN files. Remember to unzip the package. Also, with drivers being included, you don't need to install KIES.
[CREDIT GOES TO]:::::::::::::::::::::::::::::::::::::::::::
alterbridge86 (For his ROMs and the first CWM Recovery for our tablets)
_motley & Team Galaxian Soup (For their excellent kernels and deodexed ROMs)
kallt_kaffe (Pioneer in bringing the newer CWM Recovery to our tablets along with CyanogenMod ROMs)
suwandiapr (For the flashable unroot file and ODIN image thread)
phonic (Great rooting explanation and manual unroot post)
lufc & sudec123 (For the past mirror links)
Chainfire (For making SuperSU)
SamHaLeKe (For the Samsung USB drivers)
...and to anyone I might have forgotten, do say in a PM .
Click to expand...
Click to collapse
Changelog
Code:
[B][COLOR="Red"][I]1/21/2014 - FINAL UPDATE[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated SuperSU to v1.91 for Root.zip - Important fix for Android 4.4.x
[B][COLOR="DarkOrange"][I]1/19/2014[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated SuperSU to v1.89 for Root.zip
[B]TOOLKIT[/B] - Updated Adobe Flash Player to last release v.11.1.115.81
[B]TOOLKIT[/B] - Updated Samsung USB drivers to v1.5.29.0
[B]BULLETIN BOARD[/B] - Suggested TWRP Recovery with a warning.
[B]GUIDE[/B] - Deleted Mirror Link for Toolkit due to HotFile's shutdown.
[B][COLOR="DarkOrange"][I]4/20/2013[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Replaced Superuser with SuperSU (v1.25) for Root.zip
[B]TOOLKIT[/B] - Updated Unroot.zip to remove either Superuser or SuperSU
[B]TOOLKIT[/B] - Updated Adobe Flash Player to version 11.1.115.54
[B]TOOLKIT[/B] - Updated Samsung USB drivers to version 1.5.18.0
[B]GUIDE[/B] - Modified Rooting, Fixing Root and Unrooting How-to to reflect Toolkit changes.
[B]BULLETIN BOARD[/B] - Redirected users having root issues to the right place, reflecting Toolkit changes.
[B][COLOR="DarkOrange"][I]1/13/2013[/I][/COLOR][/B]
[B]GUIDE[/B] - Unroot How-To - Added solution for ROMs that have the root binary
in the wrong place. See [B][COLOR="Red"]red[/COLOR][/B] note.
[B][COLOR="DarkOrange"][I]1/9/2013[/I][/COLOR][/B]
[B]GUIDE[/B] - Corrected error in the manual Unroot command (thanks trekker99!)
[B][COLOR="DarkOrange"][I]11/17/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated Root.zip and Unroot.zip
[B]TOOLKIT[/B] - Updated Adobe Flash Player to version 11.1.115.27
[B]TOOLKIT[/B] - Updated MD5 and SHA-1 checksums.
[B][COLOR="DarkOrange"][I]10/12/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Suggested Common ICS issues FAQ by fred_be9300
before the introduction.
[B][COLOR="DarkOrange"][I]10/07/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Updated & Fixed Root.zip. Independent file [URL="http://forum.xda-developers.com/showpost.php?p=32496433&postcount=257"]here[/URL].
[B]TOOLKIT[/B] - Updated USB drivers to v1.5.15.0.
No need to reinstall if you installed a previous version.
[B]TOOLKIT[/B] - For convenience. Added Adobe Flash Player 11.1.115.17
(latest version for ICS and Jelly Bean ROMs).
[B][COLOR="DarkOrange"][I]8/04/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added MD5 and SHA-1 of the Toolkit in its section.
[B][COLOR="DarkOrange"][I]7/25/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - CWM Recovery v.6.0.0.8 included.
[B]GUIDE[/B] - Alternate version link also [URL="http://forum.xda-developers.com/showpost.php?p=21194554&postcount=2"]included[/URL] in case
of screen issues in some units.
[B][COLOR="DarkOrange"][I]7/22/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Major redesign. Users can now choose what to view.
[B][COLOR="DarkOrange"][I]7/21/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor, simpler redesign using the Roboto font.
[B]TOOLKIT[/B] - PIT file for ODIN now included
[B]TOOLKIT[/B] - Drivers updated to v.1.5.6.0
[B]TOOLKIT[/B] - CWM Recovery v.6.0.0.0 included
[B][COLOR="DarkOrange"][I]7/1/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - *Fixing Root* How-To section updated and further simplified.
[COLOR="DarkOrange"][I]6/17/2012[/I][/COLOR]
[B]GUIDE[/B] - Added one important detail in Nandroid FAQ/How-To and Toolkit sections.
[B]CHANGELOG[/B] - Format revised for consistency.
[COLOR="DarkOrange"][I]6/10/2012[/I][/COLOR]
[B]TOOLKIT[/B] - Updated Drivers to v.1.5.5.0.
[COLOR="DarkOrange"][I]5/19/2012[/I][/COLOR]
[B]GUIDE[/B] - Reorganized contents for ease of use.
[B]TOOLKIT[/B] - Changed the CWM Recovery to a fixed one by kallt_kaffe due
to several getprop status7 flash errors with the one provided by alterbridge86.
[COLOR="DarkOrange"][I]5/8/2012[/I][/COLOR]
[B]GUIDE[/B] - Minor redesign.
[COLOR="DarkOrange"][I]4/24/2012[/I][/COLOR]
[B]TOOLKIT[/B] - USB Driver version 1.5.4.0 now included.
[COLOR="DarkOrange"][I]4/8/2012[/I][/COLOR]
[B]GUIDE[/B] - Included suwandiapr's ODIN images thread link in both ODIN FAQ & How-To
as reference.
[COLOR="DarkOrange"][I]4/7/2012[/I][/COLOR]
[B]GUIDE[/B] - Minor revisions in "Fixing Root" and manual "Unroot" commands.
[B][COLOR="DarkOrange"][I]2/25/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor redesign.
Fixed manual Unroot commands.
[B][COLOR="DarkOrange"][I]2/23/2012[/I][/COLOR][/B]
[B]TOOLKIT[/B] - Discarded model specific CWM Recoveries and
replaced them with an universal flashable
for convenience. Credit goes to alterbridge86.
[B][COLOR="DarkOrange"][I]2/16/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Deleted ODIN image suggestions.
[B][COLOR="DarkOrange"][I]2/5/2012[/I][/COLOR][/B]
[B]GUIDE & TOOLKIT[/B] - Updated with the newer CWM Recovery along with instructions where needed.
[B]TOOLKIT[/B] - Unroot flashable included along with a newer driver (not necessary if you already installed the previous one).
[B]GUIDE[/B] - Suggested firmware KHA for the 7310 instead of the KL2 one at ODIN FAQ's third question due to better feedback.
[B][COLOR="DarkOrange"][I]1/30/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added newer KL2 ODIN firmware link for the 7310 in the FAQ.
[B][COLOR="DarkOrange"][I]1/27/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Minor reorganization/cleanup.
[B][COLOR="DarkOrange"][I]1/25/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved ODIN How-To with one little but very important detail in red.
[B][COLOR="DarkOrange"][I]1/23/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Removed Filesonic mirror due to them shutting down their file sharing services.
[B][COLOR="DarkOrange"][I]1/20/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved 3rd question of ODIN FAQ and also replaced links with the right ODIN images (had mistakenly put CWM links instead of ODIN image links).
Added a little disclaimer in the Bootloader FAQ in red.
[B][COLOR="DarkOrange"][I]1/19/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Removed the non-working Megaupload mirror link because of [URL="http://gizmodo.com/5877612/feds-kill-megaupload"]this[/URL].
[B][COLOR="DarkOrange"][I]1/14/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Added 3 new mirror links (thanks sudec123!).
Replaced KK5 (7300) ODIN firmware link with KL4.
[B][COLOR="DarkOrange"][I]1/12/2012[/I][/COLOR][/B]
[B]GUIDE[/B] - Improved Unroot How-To.
[B][COLOR="DarkOrange"][I]12/28/2011[/I][/COLOR][/B]
[B]GUIDE[/B] - Added Fixing Root How-To and updated ODIN FAQ with a new question.
[B][COLOR="DarkOrange"][I]12/26/2011[/I][/COLOR][/B]
[B]GUIDE[/B] - Added NANDROID FAQ and How-To.
[B][COLOR="DarkOrange"][I]12/22/2011[/I][/COLOR][/B]
Initial guide.
Thank for create this thread.
Nice work mate
Thanks for all the info, Will give it a sticky
Did a Mirror on File Sonic if you want to use it
mynewuser said:
Thank for create this thread.
Click to expand...
Click to collapse
No worries!
lufc said:
Nice work mate
Thanks for all the info, Will give it a sticky
Did a Mirror on File Sonic if you want to use it
Click to expand...
Click to collapse
Thanks a lot, lufc. I've put your provided link at OP along with credit.
Hi, I've installed the clockwork Recovery, I wiped everything because I wanted to turn back to factory defalut and now the tab is bricked.
I can turn on it, I see the galaxy tab logo but nothing happens.
So I turned to the default system recovery, wiped again but it is the same: after 10 minutes the screen shows only the logo and nothing else.
Any advice?
Thanks
HarryCustom said:
Hi, I've installed the clockwork Recovery, I wiped everything because I wanted to turn back to factory defalut and now the tab is bricked.
I can turn on it, I see the galaxy tab logo but nothing happens.
So I turned to the default system recovery, wiped again but it is the same: after 10 minutes the screen shows only the logo and nothing else.
Any advice?
Thanks
Click to expand...
Click to collapse
Flash a rom and you will be fine.
Done! Now it works perfectly.
Now i'll retry to install clockwork recovery...
Overcome_CWM_Recovery_v5.1.2.6_P73xx,Can use with the other galaxy device such as galaxy S plus?
somboons said:
Overcome_CWM_Recovery_v5.1.2.6_P73xx,Can use with the other galaxy device such as galaxy S plus?
Click to expand...
Click to collapse
I don't know. This guide is focused on the 7300/7310 variants of the Tab 8.9 as specified in the OP.
Sent from my GT-P7310
thanx nirogu for the guide..
all the steps is correct rite?
im going to try soon.... ^^
install CWM, backup stock rom using nandroid,
and then root....its better this way rite?
about root, it will void the warranty rite?
how about CWM? did we need to instal stock recovery back before claim for warranty or no need?
Thanx..^^
slaughterer0206 said:
thanx nirogu for the guide..
all the steps is correct rite?
im going to try soon.... ^^
install CWM, backup stock rom using nandroid,
and then root....its better this way rite?
about root, it will void the warranty rite?
how about CWM? did we need to instal stock recovery back before claim for warranty or no need?
Thanx..^^
Click to expand...
Click to collapse
Yes, you are correct. You can root while being in Stock ROM (the system that comes with your device) or after flashing a custom ROM. Yes, root will void it, but you can always go back to the factory image (hint: ODIN) and that removes everything, including CWM Recovery and Root. If you're staying with Stock ROM, then yes, you need to flash the Stock Recovery and Unroot (both How-Tos in the guide).
nirogu325 said:
[Restoring Stock Recovery]:::::::::::::::::::::::::::::::::::::::::::
For this one you will need to use ODIN. Locate the file "Stock Recovery" (in the zip included at the Download Link at the end of this post), which is a .tar file, perfect for ODIN's PDA section. Follow the ODIN 1.85's HOW-TO above.
[Doing a NANDROID Backup/Restore]:::::::::::::::::::::::::::::::::::::::::::
You need CWM Recovery for this one. Once you're in CWM Recovery, the process is straightforward. Look for the "nandroid menu", access it and you will see two options: "backup" and "restore". Select "backup" and wait until the system gathers all data and packs it as a backup located in your internal memory, inside a folder called "clockworkmod".
For restoring the process is the same. You need to do the following to ensure a proper restore and prevent issues that might pop up: Wipe your system using CWM Recovery's "wipe menu", do a "wipe data/factory reset" and after that "wipe dalvik cache", now go to the "storage menu" and select "format /system". Then proceed to the "nandroid menu", select "restore" to select your backup. Remember to reflash the kernel if you had one that didn't come with the ROM (like _motley's for example).
.
Click to expand...
Click to collapse
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------
taiger78 said:
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
Click to expand...
Click to collapse
Hmm, for some reason I did not see page 2 before posting my questions, Got answers to most already, Only the Restoring stock recovery question left, how doest it really work?
taiger78 said:
Hello All,
Maybe a stupid question but, I did not find any clear answer to my question.
I have taken a backup with NANDROID and got the backup into the folder clockworkmod as told in the instruction. Now as I Understand this does not include the ROM or does it?
Also the Restoring stock recovery, how does that work, I put the "recovery.img.md5" file into Odin and flash, but from where does the stock firmware come? Most probably it's not in the 4MB "recovery.img.md5" Do I need to prepare something before using this or does it work without any preparation?
Does it also erase Overcome CWM Recovery that I installer earlier?, It did not say anywhere in the post if I need to have Root permissions to use this?
Hmm, for some reason I did not see page 2 before posting my questions, Got answers to most already, Only the Restoring stock recovery question left, how doest it really work?
Click to expand...
Click to collapse
A Nandroid, as stated in the guide (FAQ section), is an exact copy of the ROM you were using with all its settings and apps you had. For the Stock Recovery, you just need the file you mentioned, and as stated in the guide, use ODIN and put the file into the PDA section. Yes, it overwrites the CWM Recovery, and no, Root is a process inside the ROM (once your device boots into it), it doesn't have any effect in Bootloader Mode.
Okay, don't know if it's me that is just stupid or what the problem is. I have tried to root my device and it does not seam to work as I'm not able to install any new kernel. Picture attached of when I try to install root.zip
It complains about: "Can't access to '/system/csc/NEE/system/'.
I have successfully installed Android 3.2 (http://forum.xda-developers.com/showthread.php?t=1410887) At least in About it says that I'm running Android 3.2. From new it was running 3.1
taiger78 said:
It complains about: "Can't access to '/system/csc/NEE/system/'.
Click to expand...
Click to collapse
This error doesn't have anything to do with root or kernel. It is just trying to set your CSC and fails because the folder is not there. It happens if you flash firmware that is not intended for your region, it doesn't effect anything else, so don't worry about that.
poisike said:
This error doesn't have anything to do with root or kernel. It is just trying to set your CSC and fails because the folder is not there. It happens if you flash firmware that is not intended for your region, it doesn't effect anything else, so don't worry about that.
Click to expand...
Click to collapse
+1 Okay, thank you for your answer, the firmware I flashed, included all European languages that's why I used it.
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
taiger78 said:
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
Click to expand...
Click to collapse
Okay got it now, problem was that "Overcome_CWM_Recovery_v5.1.2.6_P73xx" had been removed when installing HC 3.2
taiger78 said:
+1 Okay, thank you for your answer, the firmware I flashed, included all European languages that's why I used it.
Anyhow any ides to why I can't install a custom kernel after I have installed the Root.zip file? I get following screen when installing:
But after rebooting I still have the original kernel from flashing 3.2
Click to expand...
Click to collapse
The picture you posted shows stock recovery and you can't flash a kernel with stock recovery.
You need to install CWM recovery and then you can flash the kernel from there. I'm using CWM recovery from there http://forum.xda-developers.com/showthread.php?t=1321142
I used the Overcome_CWM_Recovery_v5.1.2.6_P73xx.zip and flashed it using stock recovery.
If you know how to use Odin then you can download the Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar and flash it using Odin.
It doesn't matter which you use, the end result is the same. Only flashing method is different.
When you have CWM recovery installed, then you can boot to CWM recovery and flash the kernel from there.
If you at any time flash stock rom back using Odin, then it will overwrite all, including the recovery. So you have to start all over.
I registered to say THANKS!!
I'm fairly new at this, and did something rather stupid this morning.
Thought my tab was hosed, but following the excellent instructions provided here I was able to recover it, what a relief...
It was actually a pretty good learning experience, although a bit traumatic.
That's right, Just got done building an app that can install TWRP & my External Data Kernel mod for you all from within an app!
Details:
Simple easy to user interface
Simple backup of current boot & recovery images
Reboot to Recovery button
Install TWRP
Install My /data to /ext_sd kernel mod (Still requires a manual re-partition of the SD Card to work properly.)
Warnings:
You are using this app at your own risk, it does have the possibility of BRICKING your device if not used properly
It is ONLY FOR THE METRO PCS VARIANT OF DEVICES, OTHER DEVICES HAVE NOT BEEN TESTED YET
You have been warned!
Installing:
Just download the apk to the phone and open it with a file manager of your choice.
Note: You need root in order to access the features of this app. I built this app so that OTA updates or installing TWRP or installing my kernel mod would be easier. Please enjoy.
**LINK TAKEN DOWN AS THERE HAVE BEEN REPORTS OF THE SOFTWARE SOFT-BRICKING DEVICES**
I am working on a bug fix now.
Please submit any bugs you find here. I suggest that after you run a command copy the backup files off your phone (Under "/sdcard/ASTools/backups") so that in case of something happening, you can restore using fastboot later.
Simple Restore: Put your phone into Download mode (Black screen, red text)
"fastboot flash recovery recovery.img"
"fastboot flash boot boot.img"
Hi everyone, my name is Mirko and I am an italian student and first of all sorry for my bad english, fiddle with ROMS and Kernels is an hobby for me and i really enjoy it.
I would make a tutorial for anyone who can not unencrypt OnePlus3 with any ROM. READ EVERYTHING BEFORE START.
I AM NOT RESPONSIBLE FOR WHAT COULD HAPPEN TO YOUR DEVICE. PAY ATTENTION.
DOWNLOAD
VIRUSTOTAL
Open and extract the zip file where you want.
Install USB drivers
Install ADB drivers by open adb-setup-1.3.exe, Y, Y ,Y and close.
Copy fastboot adb drivers 1.0.36 to C:\adb and overwrite.
Open CMD in the same file folder by pressing Shift+right click and type "adb", if it say nothing match reboot your pc.
Plug your phone to PC and allow adb access, then type "adb devices" and you should see your phone id.
We have to unlock bootloader, THIS ACTION PERFORM A FULL, FULL (EVEN INTERNAL MEMORY) OF YOUR PHONE, BACKUP EVERYTHING. Tick on OEM Unlock in developer option (nothing here will happen). Type "adb reboot fastboot" and your phone will reboot in fastboot mode. Use now "fastboot devices" for recognize your phone and "fastboot oem unlock" for unlock bootloader.
Do not restore backup cause we are gonna wipe again, back into fastboot mode (AFTER OEM UNLOCK FROM DEV OPTIONS) and flash twrp using fastboot flash recovery multiboot....img.
If phone reboot back again into fastboot and type fastboot format userdata. Reboot into recovery.
Now on recovery start MTP and copy OOS/HOS and supersu zips into your phone, flash the ROM, DO NOT REBOOT, flash supersu. Your device is now unencrypted.
Type adb shell chown -R media_rw:media_rw /data/media on CMD for avoid problems after flash.
You can now flash multiboot.zip and you have to inject boot sector every time you will install/update ROMS. OOS/HOS OTA ARE NOT COMPATIBLE WITH TWRP, YOU HAVE TO FLASH THE ENTIRE ZIP FILE FOR UPDATE IT.
You will see a slide menu on top right side of TWRP and from here you can install new roms on INTERNAL MEMORY. In advanced option select "no-kexec workhound" (important).For gapps go to ROM list, select the interested rom, then flash zip, >gapps.zip. NOT ALL ROMS ARE COMPATIBLE WITH MULTIROM.
Every OTA (i think) except (for sure) stock roms will update without problems.
Reboot your phone and it will boot on multiboot menu, here you select rom you want boot.
YOU ARE DONE.
I tested it on my phone and it works really fine, OOS can be installed as secondary rom BUT FLASH SUPERSU BEFORE REBOOT.
Installing secondary ROMS are slower than primary, cause it will create virtual disks.
If you have problems with pattern after reboot, back into twrp, advance, filemanager, /data/system and delete locksettings.db, locksettings.db-shm, locksettings.db-wal and reboot. Pattern will be deleted.
Installing Kernels wich are not compatible with MULTIROM will softbrick the phone, and you have to wipe.
Installing Kernels on virtual ROMS will softbrick the ROM.
I think my guide is done.
If you have problems
FOR ANY PROBLEMS AND DOUBTS WRITE HERE OR PM ME.
Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk
slothdabski said:
Wow, there's a lot of misinformation in this post.
No "virtual disks" are created. Mount points are changed to point to the secondary ROM.
You don't have to use a multi ROM capable kernel, you should read up on the no kexec workaround before you write up a post like this
Also, you can flash kernels to secondary ROMs. I'm not sure what gives you the impression that you can.
You don't have to flash the multi ROM zip Everytime you write to the system partition. Mutirom is on the "SD card" on the data partition
Aside from the incorrect parts, the rest of the tutorial is poorly written and very difficult to follow
Why don't you leave the tutorials to the people who actually know how things work on the back end.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?
mirko8054 said:
First of all thank you for reply, i totally missed to enable no-kexec workhound function...
I want to clarify that it is my first guide I do, I started in make some because I want to help people like me who have had difficulties in carrying out certain passages. I accept ANY advice and I will try to improve with time. I admit I made a mistake forgetting the previously mentioned feature. I can tell you, however, that the multi-boot every time you install a new ROM is removed. Going blind I specified / system because it is the main partition is rewritten during a flash. But I have a doubt. The Kernel for secondary ROM, should not be predisposed to function properly?
Click to expand...
Click to collapse
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk
slothdabski said:
I assure you, you do not have to reflash the mutirom zip Everytime. I have flashed dozens of times on my phone and have not had to flash mutirom again. The only exception is if you wipe internal storage, BC it wipes your "sdcard"
Mutirom patches the kernel when you flash to to secondary, hence almost any kernel will work
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
When my CM13 (Internal rom) installs OTA, after reboot multiboot menu won't appear, and i can't select secondary roms for boot them, i solve by re-flash multiboot.zip...
What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk
slothdabski said:
What you have to do in that case is go into the mutirom menu from twrp , then hit " inject boot sector"
That patches the new kernel from the OTA. You dont need to reflash the entire mutirom zip
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Ok thank you, i will update the guide.