How to root an Aus Telstra Tab - Galaxy Tab Q&A, Help & Troubleshooting

Folks,
I just got my Telstra Galaxy Tab and while actually getting Root was easy had some issues when going into recovery mode. Process a bit different from my HTC Desire ( extra steps ) .
After rooting, Titanium Backup, Rom Manager, Adfree confirmed I had root, but when I booted into recovery ( either manually or via Rom Mgr ( manual or backup ) I was getting errors like:
Install from package
Finding update package
Opening update package
Installing update
E:Error in /cache/update.zip
(Status 2 )
and I didn't have access to any of the options like Install zip from SD card or Nandroid.
I spend hours both on XDA and the net trying to work out and this morning it dawned on me . This is how I did it and there might be easier or more ways but (eventually ) this worked for me. So hopefully this helps people out:
1. Root your Tab using Superoneclick ( http://forum.xda-developers.com/showthread.php?t=812367 )
2. Download Rom Manager
3. Open Rom Manager and click on Download Clockwork Recovery. A little menu comes up and you need to download "Galaxy Tab ATT"
4. Reboot into Recovery mode and leave while it does it's thing.
5. Done.
I actually am not that worried about alternate roms at the moment as the Telstra version actually feels pretty good, but I wanted to do nandroid backups and have SU access for a couple of utilities ( Titanium, adfree etc )
Good luck and no responsibility taken if the above doesn't work for you

I have an telstra tab, and only superoneclick worked for me

Related

[GUIDE] upgrade / root Gingerbread / Froyo, flash custom roms July/05

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 .. .

[SOLVED] EU GT-P1000 w/ CM9 RC0: "Signature verification failed"

Dear valued Android and Samsung experts,
it is my first post in this forum. I waited until the flashable ROM etc. was released, so today I tried humbertOS' CM9 (RC0) from 02.02.2012. It is only my second time doing this, after initially upgrading von Android 2.0 or so to 2.3.3.
My Device Info (after wiping, while stuck now)
European SAMSUNG GALAXY TAB (GT-P1000)
Android 2.3.3
Current baseband version: P1000XXJPZ
Current kernel version: [email protected]#2
Build No : GINGERBREAD.XXJQ1
Rooted with Super One Click (Maybe. Can't remember anymore, but it is rooted.)
Installed ROM Manager Pro.
Backed up with TitaniumBackup (Premium I think) to my Dropbox (via Wifi). I hope that is correct this way.
I get the following error:
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
Installation aborted.
Click to expand...
Click to collapse
What did I try to solve the issue?
I redownloaded the ROM.zip, but it didn't help. As there are no md5 hashes available (why?) for the online files, I couldn't compare if there is a problem on my download side. But I used Google Chrome, Internet Explorer 9 and jDownloader now, they can't all be faulty. Of course I re-wiped the cache every time after I had to start the phone or transfer the files!
I read 3+ threads that I found via search, but there was no solution. By the way I was unable to find this forum (Samsung Galaxy Tab) in the forum scroll-down list? Am I blind? I triple-checked! ... In one of the threads I read there I should go go back to the stock version (2.1 or so), is that true? How do I force my Tab to do so?
Now what I think could be the problem source is that I'm wondering why the path /sdcard is showing all the other folders and stuff and why before I put the files on the flash partition of the Galaxy Tab it didn't initially show up! What I try to say is: It seems to me the bootloader accesses NOT the SD-card, but the Tab's flash (all while calling it /sdcard), how can that be!
My SD card is basically empty asides of the ROM, kernel and GApps, but (how) can it even happen that the bootloader choses the internal flash over the SD card?
The last time (2.1 to 2.33) I upgraded I used Odin. This time this is not an option? I only follow the procedure you outlined and ask no questions. I mean in the other thread I read "you will need to flash via odin first because stock rom of gtp1000 have limited options in the recovery mode." (source) - well why is this then not mentioned in this thread or on humberos website? As said, I just followed the directions, thus avoided Odin this time!
And here I read a lot about "Clockwork Recovery", do I really need it? *confused* I mean I already own and payed for ROM Manager and Titanium Backup, should be fine right? I mean it is almost absurd how much I read about it...I can assure you I bought the above tools because back then those were the ones in the talk!
I also heard about "disabling of signature verification", but as it involves a lot of steps, is it really necessary?
I also read about "3e Recovery" but what is that? I would be happy if everyone could stop throwing around with abbreviations that yield no helpful Google results and instead write out and describe what tool or method they use exactly. For the above example my open question is obviously if this recovery method also applies to me with a different brand (Samsung) and model (Galaxy Tab "classic") compared to where I found this method....
Finally do I need to / should I replace my bootloader / recovery menu with another one maybe? ... In conclusion I hope you see I did my research, but there are so many ways to get a solution, so right now I simply need a hint from more experienced pro's about in which direction I have to go!
Thank you for your help in advance!
ClockworkMod Recovery
Ok, I noticed now my mistake probably is that I was missing an installed "ClockworkMod Recovery".
But: When I try to install CWM from within the ROM Manager (v.5.0.0.6, Premium) it only displays a choice of two models - "Samsung Epic4G" and "Samsung GalaxyS i9000" - in the list and not my model (Galaxy Tab EU) or any other model! What is going on there, why does ROM Manager Premium not display an array of other devices?
And is there any alternative way to download and install CWM on my Tab?
PS: The "Euro bootstrap recovery" app mentioned in other threads is not available anymore in the market either.
PPS: I also found this directory full of clockwork builds: http*//download.clockworkmod*com/recoveries/, which one of those would be right for the GT-P1000? The "recovery-clockwork-tab.img" & "*.zip" from 04-Jun-2011 17:37?
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Thanks priyana
Thanks priyana, that hint really made it for me!
Successfully made it through!
Now only the GApps don't show up even though I installed them.
Will browse the forum here and Google for solutions...
reset to factory default and re-install gapps once more?
seems to happen now and then to some flashes
Hey priyana, I didn't update the thread, yes I'm done with that already!
A question though: Is it normal that the internal + external storage show "as one" drive or is the SD card actually not mounting on my Windows laptop? (I assume.)
The problem is, even though I activated UMS with the toggle, I can only put the data on the "12,8 GB" drive, from which I also installed GApps.
But it seems I can't install *.apk files from this location and I also have difficulties restoring my Titanium backup files from there (I put them in the TB subfolder).
So far my progress. I only want my backup back and mount my SD card, then I'm done.
can't help you there yet. I am not yet on ICS
But in slimdizzy's latest built he confirms that both cards visible from windows.
remember one is on /sdcard (internal) and the other is /mnt/emmc (external) because that is CM standard.
One of these days I will follow you guys into ICS.
Tried once earlier before the wifi speed was fixed and didn't like it.
I mean looking from the Windows / PC perspective.
There, I have neither of those paths. I hope that is not unusual.
Another point maybe: As I can't use Kies now, how to manage music? I succeeded in putting videos into the "video" folder, but the same doesn't work for music files (in "Music" as *.mp3 files). Probably I'm lacking the basics (I self-teach them to myself ), so a link to a tutorial about all this is more than welcome. But as said, asides from restoring my backup (I'm still looking for a solution...) and the music issue, all is fine. I even managed to install the apps from within the internal storage with the pre-installed file-manager.
Dont know much about the kies and music.
For TB, there is a setting in there for backup folder.
Have you explore the options?
I can put my my backups anywhere and point TB to it and restore.
Sent from my GT-P1000 using XDA App
Actually, now after another restart it did recognize both the music and the missing TB backup files! I'm really a bit sloppy. Now I'm actually restoring successfully.
Now I will only try to find how to remove a few apps (not selected for restore!) from the backup (job). Apps that I actually don't ever want to see on my tablet again.
I'm sure I'll be able to find out myself...
same problem
priyana said:
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
please help .... im new to this but having the same problem .n i didnt understand what is overcome n how will it solve this issue..please reply
I have replied the same way many times in this forum too
Here goes again:
Overcome ROM is a GB 2.3.6 custom ROM based on Samsung ROM.
We use it a lot because:
1) it has very clear step by step fool proof way to "re-stock" your TAB in a good clean stock condition, upon which you can then install most ROM
2) its kernel, Overcome Kernel 4.0 comes in ODIN flashable and gives you a CWM Recovery 5.x, which is needed to flash other ROMs
3) When flashed, the kernel performs conversion(and support) of RFS filesystem to EXT4 which is better and faster filesystem. This is sometimes desirable.
Go to overcome site
http://www.teamovercome.net/p1000/
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
But please read it many times until you get what it is saying.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
Next step if you want, just continue following the guide.
Basically flash Overcome Kernel tar using ODIN, and it will reboot and converts your filesystem (you hear female robotic voice).
At the end of it, you get CWM recovery (access it while off : press volume-up and power button)
From CWM recovery you can flash any custom ROM you want.
You will find most of them ask you to flash from CWM.

Universal Gingerbread Root & Unroot 2.3.3 -> 2.3.7+

UNIVERSAL GINGERBREAD ROOT SAMSUNG GALAXY MODELS: GT-S5570, GT-S5570B, GT-S5570I, GT-S5570L, GT-S5571, GT-S5578 (Chinese Mini), GT-S5660, GT-S5660M, GT-S5660L, GT-S5660V, SHW-M290K (Korean Gio), GT-S5670, GT-S5670B, GT-S5670L, GT-S5830, GT-S5830B, GT-S5830C, GT-S5830D, GT-S5830F(La Fleur), GT-S5830i, GT-S5830L, GT-S5830M, GT-S5830T, GT-S5830V(new), GT-S5830Z, GT-S5839i, GT-S6802, GT-B5330, GT-B7510, GT-B7510B, GT-B7510L, GT-B7800, GT-B5510, GT-B5510B, GT-B5510L, GT-B5512, GT-B5512B, GT-S6102, GT-S6102B, GT-S5300, GT-S5300B, GT-S5302, GT-S5360, GT-S5360B, GT-S5360L, GT-S5360T, GT-S5363, GT-S5369, GT-S5690, GT-S5690M, GT-S5690L, GT-I8150, GT-I8150B, GT-I5510, GT-I5510B, GT-I5510L, GT-I5510M, GT-I5510T, SCH-i509, SGH-T499(new), SGH-T589(new), SGH-T589R(new), SGH-I827(new), SGH-I837(new), SGH-I857(new).
DISCLAIMER: ---You will have sucessfully rooted Samsung phone only for the models that are mentioned above. Any other phone model is incompatible at the present time. Phone models like GT-S6500, GT-S7500, GT-I9000 have a diferent structure from diferent point of view. Diferent certificate pass key to the signed zip files, diferent update binary in the zip file and so on. If anything new comes out you will be informed untill then it is strictly on the models that are presented.---
This is only for the people that they are using Gingerbread and can't root their phone with SuperOneClick. You can root your phone with universal_gb_root_v24.zip file for your phone model.
Question: How do I Root Gingerbread on my phone?
Answer:
- First enable Unknown sources on your phone (Settings -> Applications -> Unknown sources)
- Download the universal_gb_root_v24.zip file and put in your SD card.
* How do I transfer universal_gb_root_v24.zip on my SD card?
(You can tranfer the universal_gb_root_v24.zip to your phone via Wifi, Bluetooth, SD micro Adapter or USB cable. To transfer it via USB cable you need first to download KIES from the offical Samsung Web Site and after installing restart your PC so the USB drivers can be recognized properly.Enable USB debugging on your phone, Settings -> Applications -> Development -> USB debugging. Plug in the USB cable and enable the connection on you mobile phone like the picture in the bottom. After couple of seconds your SD card will be showed on your PC like Removable disk. Copy universal_gb_root_v24.zip to your SD card.)
{
"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"
}
- After transferring your file on your phone disable the USB by pressing "Disconnect storage from PC" after that remove the USB cable and turn off your phone "Power off".
Entering recovery mode on Samsung Galaxy: (Young CDMA SCH-i509 and Chinese Version CDMA SCH-i509)
- Make shure you start the phone like this : Long press and hold the (Volume up Button) + (Power Button)
Entering recovery mode on Samsung Galaxy: (551 GT-i5510/B/L/M/T) (Pro GT-B7510)​
- Make shure you start the phone like this : Long press and hold the (T Button) + (Power Button)
Entering recovery mode on Samsung Galaxy: (Ace GT-S5830/B/C/D/L/M/T) (Gio GT-S5660/M/L/V) (Fit GT-S5670/B/L) (Mini GT-S5770/B/L, GT-S5771)
- Make shure you start the phone like this : Long press and hold the (Power Button) + (Home Button)
Entering recovery mode on Samsung Galaxy : (Ace GT-S5830i) (Mini GT-S5570I) (W GT-I8150/B) (Xcover GT-S5690/M/L) (Young GT-S5360/B/L/T, GT-S5363, GT-S5369) (Y-Duos GT-S6102/B) (Y-Pro GT-B5510/B/L) (Y-Pro Duos GT-B5512/B) (M-Pro GT-B7800) (Pocket GT-S5300/B)​
- Make shure you start the phone like this :
Method 1:
Long press and hold the (Volume up Button) + (Home Button) + (Power button)
* If for some reason with Method 1 the phone reboot always when entering recovery mode (depends on the models) please use the Method 2 option
Method 2:
Long press and hold the (Volume up Button) + (Home Button) + (Power button) when you see the samsung logo for the second time release (Home Button) and press again the (Home Button) and after that release the (Power button)
- After couple of seconds you will see your phone booting in recovery mode
- Move in the menu with the Volume - Volume + to scroll up and down and choose "apply update from sdcard" with the Home button and choose the universal_gb_root_v24.zip and press once again the Home button to apply it.
- You will see a message "Install form sdcard complete".
- Then press on the "reboot system now"
- When you open SuperSU it will ask you to upgrade the SU binary just press continue your phone will reboot once and you are done!
Download link for Universal Gingerbread Root (by StoneBoyTony) :
universal_gb_root_v24.zip
What's new in this version:
- SuperSU Application v0.94 (new)
- SuperSU binary v0.93 (new)
- Root Validator
- BusyBox binary v1.20.2 (new)
- New signed release key of the zip files for better compatibility on the phone models (new)
IMPORTANT: Root and Unroot method is designed to work in recovery mode on Stock ROM's. CWM Recovery and Custom ROM's are not supported! And never try to unroot your phone when you are using Custom rom!
FAQ​
AFTER ROOTING I SEE ONLY ROOT VALIDATOR BUT NOT THE SUPERSU APPLICATION?​
As some people reported there is sometimes problem with the rooting procedure files can't be extracted properly (applications,binaries) so from today (04.08.2012) in every new update there will be an extra second alternative root zip file recognized with the letter "b" in the end of the version number. As always in life we must have a B PLAN. In this root zip file package it will be only the SuperSu application and the supersu binary, no Busybox, Rootvalidator or anything else. So if the rooting procedure from above didn't work for you then you should run again in recovery mode the universal_gb_unroot_v8.zip to delete all the half extracted files from the root procedure previously done. After that you can apply universal_gb_root_v24b.zip known as Root Only.
IMPORTANT: If for some reason after rooting with the universal_gb_root_v24b.zip want to install Busybox then when you open the application it will give you a location to install busybox to /system/bin (this is for the reason becouse there is no busybox binary in this root zip file) you just need to simply relocate the installation to /system/xbin (to relocate the path simply press on the text /system/bin it will open a new window and change it to /system/xbin) . This is for a reason becouse in the future you might want to remove busybox and many times happend that it can't be uninstalled properly leaving all the applets in bin folder mixing the files with the system files from your Android OS. Then you need to install root explorer and delete all the applets manualy and trust me is a painful job. So the problem it will be solved very quickly by installing in /system/xbin. if you don't like it to have anymore later just use the procedure for unroot (READ: HOW CAN I UNROOT MY PHONE?) universal_gb_unroot_v8.zip it will delete all the remaining stuff from busybox in /system/xbin and use again the universal_gb_root_v24b.zip to root.
Download link for Universal Gingerbread Root ONLY (by StoneBoyTony) : universal_gb_root_v24b.zip
THERE IS NO SU BINARY AFTER ROOT?​
From today (02.04.2012) I can proudly present the third update zip universal_gb_c.c.b.s.f_v7.zip. C.C.B.S.F stand for "Cleanup Carrier Branded System Files" What makes this package very interesting is allowing you to cleanup your System files (applications) from your branded carrier provider such as Shops, Music, Web Launchers, Widgets...Games: Tetris,Sims3 etc ...making free space in the system partition ROM (not internal memory) so later the root installation can take place and have a sucessfully rooted phone. This package will clean up most of the carrier providers like:
What's new in this version:
Added Carrier Network Providers:
- 3 (new)
- Aircel (new)
- Airtel
- Asda (new)
- Axis (new)
- Banglalink
- BT Mobile (new)
- Cellone (new)
- Dialog
- Dolphin (new)
- E-Plus
- Etisalat
- Globe
- Grameenphone
- H3G (new)
- Hutch
- IDEA
- Indosat (new)
- IR MCI (new)
- IRANCELL (new)
- Loop Mobile (new)
- M1
- Meteor
- Mobitel
- Movistar
- MTCE (new)
- NCELL
- NepalTelecom
- O2
- Optus
- Orange
- Poland Plus
- Reliance (new)
- Robi
- SFR
- STEL (new)
- Taliya (new)
- Talkmobile (new)
- TataDOCOMO (new)
- Telcel
- Teletalk
- Telkomsel (new)
- TelstraOne
- TESCO (new)
- TKC (new)
- T-Mobile
- tuenti
- Uninor (new)
- Videocon (new)
- Virgin
- Vodafone
- XL (new)
- New signed release key of the zip files for better compatibility on the phone models (new)
IMPORTANT: The universal_gb_c.c.b.s.f_v7.zip can be applyed in recovery like the rest of the zip files for root and unroot. It will delete all Carrier Branded System Files (Applications) without to interfere with the system files of Samsung Stock ROM's all functions will work normaly only the applications from the carrier branded apps will be deleted. In order to bring them back you need to unroot your phone and make a Factory Reset and all will be back as usual. This zip file should be only applyed if you have Carrier Provider Phone (like the above list already mentioned) and can't root the phone becouse of the carrier apps making a full capacity of the Android OS (system partition).
Download link for C.C.B.S.F (by StoneBoyTony) : universal_gb_c.c.b.s.f_v7.zip
I HAVE TRY ALL THE ABOVE METHODS NOTHING IS WORKING?
Chapter I
-Removing Quickoffice-​
Well some Stock Firmwares have been made that in the system partition you can not even copy via recovery a single file. So my task search begin and finaly I found the bug to solve the problem. In many Stock Firmwares they put Quickoffice application, this stock firmwares in some cases are very problematic to make root on them. So finaly here is the solution and very simple to make a free space for rooting. Apply in recovery the universal_gb_remove_quickoffice.zip and then you can use the universal_gb_root_v24b.zip to finaly root your phone. So Quickoffice will be deleted from your system partition but you can always install the Quickoffice.apk whenever you want and it will be installed on your SD card (you can have the rooted phone and using again the Quickoffice). If for some reason you need to take your phone to the samsung service center problem with hardware,software or anything like that you can reverse the process to install Quickoffice back to the system partition (if you have installed the Quickoffice.apk uninstall it first from the Task Maneger)using first the universal_gb_unroot_v8.zip to unroot and after that use the universal_gb_install_quickoffice.zip to install Qucikoffice back to your system partition and all will be back as normal.
Download link to Remove Quickoffice (by StoneBoyTony): universal_gb_remove_quickoffice.zip
Download link to install Quickoffice application: Quickoffice.apk
Download link to install Quickoffice back on your system partition (by StoneBoyTony): universal_gb_install_quickoffice.zip
Chapter II
-Removing Thinkfree Office-​
Same as Chapter I in many Stock Firmwares we find the application Thinkfree Office, this stock firmwares in some cases are very problematic to make root on them. The solution is very simple we just need to make a free space for rooting in your system partition and remove Thinkfree Office. Apply in recovery the universal_gb_remove_thinkfreeoffice.zip and then you can use the universal_gb_root_v24b.zip to finaly root your phone. Thinkfree Office will be deleted from your system partition but you can always install the ThinkfreeOffice.apk whenever you want and it will be installed in your internal memory (you can have the rooted phone and using again the Thinkfree Office). If for some reason you need to take your phone to the samsung service center problem with hardware,software or anything like that you can reverse the process to install Thinkfree Office back to the system partition (if you have installed the ThinkfreeOffice.apk uninstall it first from the Task Maneger) using first the universal_gb_unroot_v8.zip to unroot and after that use the universal_gb_install_thinkfreeoffice.zip to install Thinkfree Office back to your system partition and all will be back as normal.
Download link to Remove Thinkfree Office (by StoneBoyTony): universal_gb_remove_thinkfreeoffice.zip
Download link to install Thinkfree Office application: ThinkfreeOffice.apk
Download link to install Thinkfree Office back to your system partition (by StoneBoyTony): universal_gb_install_thinkfreeoffice.zip
HOW CAN I REMOVE ROOT VALIDATOR I DON'T NEED IT ANYMORE?​
- You need to open SuperSu application and under "Apps" press the icon or the text for RootValidator. A new window will open and press "Forget". Power off your phone and enter in recovery mode to apply universal_gb_remove_validator_v3.zip file.​
Download link for Remover of RootValidator (by StoneBoyTony) : universal_gb_remove_validator_v3.zip ​
HOW CAN I UNROOT MY PHONE?​
- First thing you need to remove all the applications that they are depended from root, after that open SuperSU -> Settings -> Full Unroot and press Continue. Your phone will reboot once and after that enter Recovery mode and use the universal_gb_unroot_v8.zip to delete all the traces remaining. If you were having Superuser app (the older one) just get in the Recovery mode and then apply the universal_gb_unroot_v8.zip
You can download the UNROOT (by StoneBoyTony) from here: universal_gb_unroot_v8.zip
What's new in this version:
- Deleting all traces of Superuser
- Deleting all traces of Suhax
- Deleting all traces of Busybox and Busyboxpro (and all applets created in xbin that they are symlinked causing sometimes Busybox to fail of uninstalling them so that problem is solved i add them all to be deleted and for the leatest version 1.20.2. )
- Deleting all traces of Superoneclick
- Deleting all traces of SuperSU and SuperSU Pro
- Deleting Root Validator
- New signed release key of the zip files for better compatibility on the phone models (new)
*NOTE* - FOR ALREADY ROOTED PHONES WITH SUPERUSER​
For those who already have root with Superuser or any other kind of root method and want to update your root with the new SuperSU package you need first uninstall all app that they are depended from root then apply in recovery mode the universal_gb_unroot_v8.zip and enter again in recovery mode to apply the universal_gb_root_v24.zip or you can use Only Root universal_gb_root_v24b.zip .
This is how it looks rooted phone you will have application SuperSU​
​
This post is good for noobs lik me. . But a similar post abt apps is already posted in themes and apps section...here --
http://forum.xda-developers.com/showthread.php?t=1569607
JoK€R said:
This post is good for noobs lik me. . But a similar post abt apps is already posted in themes and apps section...here --
http://forum.xda-developers.com/showthread.php?t=1569607
Click to expand...
Click to collapse
The diference is providing root and unroot for more phones that they didn't have any luck untill now.
hello
Newbie here,
Rooting my froyo with a tutorial whitout problems but now i have a new one with
gingerbread 2.3.6
It's a mt 6573 dapeng A7 and no real solution ar found to root.
Will this update zip also works on this device or not or is it just for the samsung bootrom.
I have boot into recovery an made a full backup.
So if i apply this update and it's not work for some reason can i still be enter the recovery mode or not to restore my backup from sdcard or is my phone bricked.
just learning so sorry if there are noob questions because there is no real tutorial for 2.3.6
grts b,
hi op you should know soc support rooting gb from a long time but this method is more easy
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
have you checked it manually I have open the script and found that you have written a command which will format /system
and without how mobile will boot
Samsung Galaxy GT-S7500
Does not work with the s7500.
I got the following:
E: failed to verify whole-file signature
E: signature verification failed
Also downloaded the file again three times and got the same message
dhlalit11 said:
hi op you should know soc support rooting gb from a long time but this method is more easy
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
have you checked it manually I have open the script and found that you have written a command which will format /system
and without how mobile will boot
Click to expand...
Click to collapse
You should know what is the sign before format command is "#" that mean that the command is not in function
sab65 said:
Does not work with the s7500.
I got the following:
E: failed to verify whole-file signature
E: signature verification failed
Also downloaded the file again three times and got the same message
Click to expand...
Click to collapse
Sorry about that it was experimental for Ace Plus removed from the Tutorial.
rcbadboy said:
hello
Newbie here,
Rooting my froyo with a tutorial whitout problems but now i have a new one with
gingerbread 2.3.6
It's a mt 6573 dapeng A7 and no real solution ar found to root.
Will this update zip also works on this device or not or is it just for the samsung bootrom.
I have boot into recovery an made a full backup.
So if i apply this update and it's not work for some reason can i still be enter the recovery mode or not to restore my backup from sdcard or is my phone bricked.
just learning so sorry if there are noob questions because there is no real tutorial for 2.3.6
grts b,
Click to expand...
Click to collapse
My friend you have mixed the pots. This is for Samsung Galaxy phones and nothing to do with Mediatek phones; Need to search for the forum about your phone.
StoneBoyTony said:
My friend you have mixed the pots. This is for Samsung Galaxy phones and nothing to do with Mediatek phones; Need to search for the forum about your phone.
Click to expand...
Click to collapse
hey
ik know this is the samsung sub but because i saw "universal gingerbread" it's maybe works for other phone's also.
But now i think not
i could just try because i have try everything to root my phone to get rid of this unwanted chinese apps.
grts b,
I know adding # before any line will tell system not to read that line but why take risk when we can remove that
StoneBoyTony said:
Sorry about that it was experimental for Ace Plus removed from the Tutorial.
Click to expand...
Click to collapse
Yes it is a pity. Have not been able to find a way to root the Ace Plus. It is very frustrating. This was the closest I got to doing it.
This worked perfect on samsung galaxy mini.
Thank you.
doesnt work on 2.3.4 galaxy ace
Gyku said:
This worked perfect on samsung galaxy mini.
Thank you.
Click to expand...
Click to collapse
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
oldernerd said:
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
Click to expand...
Click to collapse
It not support in script. Just edit update-script and change something to GT-S5830T from GT-S5830 and flash
Sent from my GT-S5570 using XDA
oldernerd said:
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
Click to expand...
Click to collapse
Redownload v14 now is fixed problem was that I forgot to put the script it in Unix Format...see if you have any luck now
tried this method with galaxy s6102 and worked with no issues.
thx
worked perfect on samsung galaxy y dous
Rename zip file
<THOR> said:
You have try to rename the package zip in upd_1.zip and then flash from recovery? if not, try.
Click to expand...
Click to collapse
Thor,
Thanks for your reply...
Rename it to what ??
Already called upd_.zip
---------- Post added at 12:30 PM ---------- Previous post was at 11:52 AM ----------
Hi,
Just downloaded V14 and whilst it says it is rooted and superuser app is loaded, i do not believe the phone is rooted.
Is there a definitive and SIMPLE way i can test
to see if it is actually rooted and that the software i am trying to use is incorrect ??
OR maybe, i dont have the latest V14....
Can i get a link to the latest V14 ??
oldernerd said:
Thor,
Thanks for your reply...
Rename it to what ??
Already called upd_.zip
---------- Post added at 12:30 PM ---------- Previous post was at 11:52 AM ----------
Hi,
Just downloaded V14 and whilst it says it is rooted and superuser app is loaded, i do not believe the phone is rooted.
Is there a definitive and SIMPLE way i can test
to see if it is actually rooted and that the software i am trying to use is incorrect ??
OR maybe, i dont have the latest V14....
Can i get a link to the latest V14 ??
Click to expand...
Click to collapse
install root apps like root explorer, titanium backup or freespace.. if these apps prompt you to allow or deny SU access, choose allow.. if you're phone is rooted, SuperUser app will display that these apps were granted superuser permissions.. simple..
new version
would be great of we could get a new version cut (V15 ??) with Thor's recommendations as well....
I am nearly at wits end with this S5830T rooting issue.
Hi,
I want to root my phone, a Galaxy Mini, but before I do that I have some noob questions, because I don't want to do something stupid...
1. This should work on android 2.3.6 S5570XWKT2, right?
and...
2. Is there any risk that this can brick my phone?
Thanks!
Sent from my GT-S5570 using XDA

my method for updating successfully to zv8 with root from GV2.0 (zv7)

hello well first off i just finished troubleshooting the **** out of my phone and i see lots of others are having issues as well and its all scattered. so i am going to post my method which should get you updated with MT's AIO which also includes a fix for those who are having permission problems with the AIO.
(this is optional and for those who were having problems with permission errors using AIO on GV 2.0) (skip below for first step of getting to zv7)
first off the main thing that I figured out is that if you are on GV2.0 the kernel by default (at least for me) disables logcat which gives many problems with MT's AIO solution with the error cannot open dev/log/main with all the permission problems with rooting / unrooting on GV2.0. So for those who are having that issue here is the fix:
open root explorer
go into /system/etc/init.d/12gvtw
long click then open up text editor
go to where it says rm /dev/log/main and change it to
#rm /dev/log/main
then save and then reboot which should fix the permissions errors.
now doing that enabled me to be able to have success with the AIO to prepare for the update to zv8 while on GV 2.0 ...
but then I ran into another problem after that was that the OTA update would fail. most likely because the boot.img was not stock (this is just a guess, probably other reasons as well)
----------------------
but what worked for me was going completely stock gingerbread.
so for this fix I simply went to this thread to get completely to stock zv7
http://forum.xda-developers.com/showthread.php?t=1348637
I then downloaded the nandroid and followed MT's instructions steps 1-6
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
3.) I recommend to wipe data to prevent any problems
I want to emphasize that you SHOULD WIPE DATA NOW AT THIS STEP IN CWM BEFORE IT GETS TO STOCK RECOVERY.
4.) Go to install zip from sdcard
5.) Select RevoZV7GBStock.zip
6.) Reboot
then after that my phone booted up completely stock (with stock boot.img) and wiped data with root still enabled.
then I went to this thread to get MT's AIO zv8 and followed the steps 1-5 (steps 6 and 7 will be completed later)
http://forum.xda-developers.com/showthread.php?t=1566729
1) Download zip and extract
2) Install drivers if not already installed
3) Make sure you are on stock ZV7
4) Click Root&RecoveryAIO.bat
5) Select "Prepare for Update"
then the phone rebooted and was at stock recovery and unrooted and was completely stock but with the added the data/local.prop edits.
so then I went to this thread to download Broken Out Rom from my computer and followed steps 1-2 (steps 3-9 will be completed later) before i completed the AIO process steps 6-7 stated earlier.
http://forum.xda-developers.com/showthread.php?t=1577423
1.) Download the .zip & make sure 4g is enabled.
2.) Place zip in external sdcard
So now you should have your phone completely unrooted with stock recovery with Broken Out Rom downloaded on your phone's sd card (not installed yet).
You are now ready to go to get the OTA update. (step 6)
go to settings > about phone > software update > check new
then you should have the OTA update successfully installed when it reboots.
you now have zv8 installed with no root or cwm.
then i went to MT's AIO for zv8 and clicked option 7 which is too root zv8.
then the phone gave me an error on AIO when trying to root but then CWM still got installed at the end of the AIO process.
so the phone then booted up with no root but CWM was installed but could not get into recovery mode using quickboot to recovery option on the phone due to no root access..
for this fix I then opened up MT's AIO for zv7 found here under step 2 of "How do I completely Return to Stock"
http://forum.xda-developers.com/showthread.php?t=1348637
and then clicked option 7 which is reboot recovery. this booted my phone into recovery.
then I went to continue the process of installing Broken Out Rom (steps 3 and 4 are skipped because we already wiped data initially above)
5.) Go to install zip from sdcard
6.) Select BrokenOutRevo1.1.zip
7.) Do not wipe data after flashing!!!
8.) Reboot!
9.) To Block CIQ Logs Requires Reboot After Initial Boot
You should now have a fully rooted zv8 phone with CWM and can give yourself a pat on the back.
if i forgot to mention things please let me know. this was just my process which worked after much troubleshooting so i thought i'd share it with you all.
My method
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
LeadPharmer said:
Just for people who might be looking for other ways or are a few steps into it and wondering how to proceed, here is my successful method (GingerVolt -> BrokenOut 1.1):
All of the apps, files, and such are found in the various other threads so I will just summarize without links:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Using the OLD AIO, root it.
3 - Using the OLD AIO, install STOCK recovery.
4 - Use Terminal Emulator to echo/create the /data/local.prop
5 - Go to settings->about phone->update and check for new update (and then let it update)
6 - Once you have updated via OTA, use Root&Recovery from the NEW AIO.
7 - Reboot recovery and wipe data
8 - After wiping data and without exiting CWM, flash BrokenOut.
That is what worked for me, I hope it might help others because BrokenOut is frickin awesome (thanks again MT).
Click to expand...
Click to collapse
Looks good.. although if you did step 1 using LGNPST you don't need step 3. The .tot contains the stock recovery.
I had every problem you could think of (all problems liste here) and this is my method that finally worked:
1 - Using LGNPST, push the ZV7 .tot file.
2 - Factory reset, just in case
3 - Using the OLD AIO (Root&RecoveryAIO), root it (option 1 only!).
4 - Use Check Root app to make sure you have root
5 - Use fileslick app to Change folder permissions and move local.prop file app to
- Open fileslick, click actions, and click show root
- Swipe all the way left until you are at root and see /data folder
- Tap the data folder so it has a green check and then hit actions and select "permisions"
- Check everything in that menu (This will make it so you don't has any permission denied menus when moving the local.prop)
- Put the local.prop file from the "data" folder in the ZV7toZV8Root.zip by tapping it in fileslick, navigating back to the "/data" folder you just set permissions for, clicking "actions" and clicking "copy file to this location"
6 - Go to about this phone in the settings app and check for updates to update ZV8
7 - After reboot use ZV8CWMRecovery.bat (option 1) to install clockwork
8 - After reboot go back and use OLD AIO (Root&RecoveryAIO) to reboot to recovery (option 7)
9 - Reboot recovery and wipe data
10 - After wiping data and without exiting CWM, flash BrokenOut.
11 - DON'T WIPE DATA AFTER FLASH

Easy steps to root, Recovery and flashing of Roms WITHOUT PC (5 min Tut)

Fist of I wanna say a big thanks to - Developers of Kingroot and Flashify
Now - I don't know why nobody ever uses this method but it works all the time on almost all phones both new and old if you can gain root using an apk app even if its temp root it works and its fairly easy and fast.
Straight to the point.
1. Install kingroot ( search for it on google download and install )
2. Use the kingroot app to root your device it works - and its good.
3. Download the latest recovery of TWRP image from their site it must contain in the name wls since its a sprint version.
put the recovery on the root folder of your device.
4. Install flashify - from playstore - Grant root access and flash the recovery you downloaded it should take a few seconds then reboot to recovery and vuala ... You now have a fully functional recovery without the hassle of fastboot ( Which i f**king hate and consider a total waste of energy and a drag for the need of a PC and installation of drivers blah blah blah ...)
Now download any custom ROM of your choice and install - i use viper one 9.0.0 - its amazing.
Thank you and bye bye ...
Now if you are have troubles with invalid sim card its simple just download the latest ruu the .exe for format - install htc drivers and double click on the ruu plug your device and then follow the dialogue and install ( that simple too no fastboot :silly: ).
Then follow the he step 1 to 4
1. flash this - https://forum.xda-developers.com/attachment.php?attachmentid=2402764&d=1384892279 - via you twrp and
2. Install this "SIM Unlock Helper" - open press the back press start and grant root access.
3. Scroll down and tap on Sim Lock - it should freeze for 5-10s and then you should see your none sprint sim card.
And now you can flash any ROM without the need to sim unlock again .
That's all , Thank you.
Nice guide!

Categories

Resources