Related
Universal Xoom Root
Thats right, this method will work for any xoom on any update - Including future updates!!!
Note: Unlike the similar method floating around on here, this also gives you an unsecured boot image.
-- Please Note: this thread is still a work in process and has been sped up by the arrival of the 4g Xooms --
Current requirements: adb & fastboot have been setup and you have an external sdcard for your xoom.
1. Setting up adb & fastboot
Coming Soon! (If you want to write this section for me and pm me it, thats fine !)
2. Downloading the rooting-update zip file.
Download the zip file from here.
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
3. Flashing recovery
1. Download this Recovery image.
2. If your device is locked, now is a good time to unlock it.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
Downloads
Universal Xoom root - version 1.0
This was also tested on a 4G Xoom and is working 100%.
I'll take this one as well....
Came just in time, sol. My friends' Xoom needs a-rootin'.
solarnz said:
This was also tested on a 4G Xoom and is working 100%.
Click to expand...
Click to collapse
Will run this when I get home. After root would it be safe to reload tiamat hammerhead.
jsa11ey001 said:
Will run this when I get home. After root would it be safe to reload tiamat hammerhead.
Click to expand...
Click to collapse
Went smooth just ran home on lunch and ran adb. took like 10 min. you the man. Still wondering about Hammerhead.
By any Xoom... does that mean the country of the Xoom doesn't matter? Because I am currently still working on my Xoom Heaven stickied thread, and this would be an amazing addition to my thread. It will be much less confusing for all when it comes to rooting. I was working on adding Euro models rooting guides next, but an any Xoom and any model rooting method is awesome! And it would result in a lot less semi bricks.
Correct. As long as the xoom can be unlocked and cwm works, this tool should work!
solarnz said:
Correct. As long as the xoom can be unlocked and cwm works, this tool should work!
Click to expand...
Click to collapse
Awesome! Thank you. I just wanted to make sure of this before I linked it up on my thread. It's good to know this will work for future releases. Finally, a real rooting method that will always stay current. Team Tiamat wins!
Correct. As long as the xoom can be unlocked and cwm works, this tool should work!
Click to expand...
Click to collapse
Are all zooms unlockable or can some not be unlocked?
HTC wildfire cyanogenmod nightly
hboot -1.01 s-off xtc clip
banny7000 said:
Are all zooms unlockable or can some not be unlocked?
Click to expand...
Click to collapse
All XOOMs are unlockable, just need to get into fastboot, run fastboot oem unlock, press volume down then up, then press volume down then up again and now your XOOM is unlocked.
@solarnz - if no one did the adb setup and configuring yet, I won't mind typing it up and send it your way.
Nice. Worked perfectly. Cipe Niw.
I'm going to sound real noob here even though I've flashed and rooted a few times with various ROMs but...
If I root a stock ROM will it prevent the OTA updates from working?
Cheers
Works fine on a 3.1 Canadian Xoom thanks. I was looking at the script and was wondering does this patch the current boot partition on the fly, just curious.
WOW!!!
This is HUGE!
You've just obsoleted probably 15 - 20 percent of the entire Xoom development section!
Thanks so much for continuing to make it easier to get other Xoomers on board the Root Express train to Android Awesomeness!
scsa20 said:
All XOOMs are unlockable, just need to get into fastboot, run fastboot oem unlock, press volume down then up, then press volume down then up again and now your XOOM is unlocked.
@solarnz - if no one did the adb setup and configuring yet, I won't mind typing it up and send it your way.
Click to expand...
Click to collapse
Someone has already PM'd me text for this on xoomforums. I just haven't had a chance to copy it in yet.
Lakota said:
I'm going to sound real noob here even though I've flashed and rooted a few times with various ROMs but...
If I root a stock ROM will it prevent the OTA updates from working?
Cheers
Click to expand...
Click to collapse
Yes.
woolmonkey said:
Works fine on a 3.1 Canadian Xoom thanks. I was looking at the script and was wondering does this patch the current boot partition on the fly, just curious.
Click to expand...
Click to collapse
Yes, this does the modifications on the fly.
Wipes Xoom
I think the answer is yes, but I'll ask to make sure. Since this is changing the recovery/boot images, should I assume that it wipes the Xoom?
silvinoa said:
I think the answer is yes, but I'll ask to make sure. Since this is changing the recovery/boot images, should I assume that it wipes the Xoom?
Click to expand...
Click to collapse
Only if you haven't done fastboot oem unlock before.
Good, you make this work.
Are you inspired by my method, or you think of it all by yourself?
eddielo said:
Good, you make this work.
Are you inspired by my method, or you think of it all by yourself?
Click to expand...
Click to collapse
I had actually intended to write this since the release of Android 3.2 on the wifi Xooms.
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
What does stock stand for?
udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.
El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App
Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.
I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.
Hi,
I managed to screw up just about really bad with my Defy+ after flashing it with Waikiui which i afterwards noticed doesnt work with the Defy+ so now im in some hard packed poo here.
I have come to the conclusion that RSD Lite should do the trick if im lucky but i need to find a good SBF to flash the Defy+ with. Originally this phone rolled with a Nordic (GB?) so im looking for either that or something else that could be a good exchange for it.
Would it be possible to flash it with for an example Cyanogenmod or something?
Regards.
//FlashTec80
On the CM webpage, under the Devices - > Motorola Defy it says says there is no official support for defy+ ... on the other hand on the CM forums there are numerous posts by people claiming it runs just fine, seems like some run into a bug where the battery doesnt charge to 100% or something, you might want to stick to a ROM thats officially approved for your device or do a little bit more reading before you take the plunge. I would have posted links to forums and official page but apparently I cant since Im a noob and I need at least 8 previous posts
Tried to run CM 7 in RDS Lite, but it said that files mentioned in the XML file was missing, is that normal?
You can't flash CM7 using RSDlite. RSDlite is used for flashing of .sbf files!
To get your phone back to life, follow this steps:
1. Phone off, battery out
2. Hold Volume Up and Power Button and put the battery back in while holding the buttons - phone will boot into it's bootloader - you will see some white letters saying Bootloader Version 09.10 etc..
3. Install latest USB drivers - found here - http://developer.motorola.com/docstools/USB_Drivers/
4. Start up RSDlite on your PC (you need version 5.3.1)
5. Use this sbf - link (put the .sbf file in root C:/ and rename it to something short (e.g. defy235.sbf)
6. Select that sbf file in RSDlite and press START
7. Wait until the process reaches 100%, by that time your phone will be completely turned on > it's alive again
Can't write more, need to get going to classes, but will help you with everything else, as well. It's easy, just be patient.
P.S. Ignorance killed your defy+, not awesomeness
Cheers!
niksy+ said:
You can't flash CM7 using RSDlite. RSDlite is used for flashing of .sbf files!
To get your phone back to life, follow this steps:
1. Phone off, battery out
2. Hold Volume Up and Power Button and put the battery back in while holding the buttons - phone will boot into it's bootloader - you will see some white letters saying Bootloader Version 09.10 etc..
3. Install latest USB drivers - found here - http://developer.motorola.com/docstools/USB_Drivers/
4. Start up RSDlite on your PC (you need version 5.3.1)
5. Use this sbf - link (put the .sbf file in root C:/ and rename it to something short (e.g. defy235.sbf)
6. Select that sbf file in RSDlite and press START
7. Wait until the process reaches 100%, by that time your phone will be completely turned on > it's alive again
Can't write more, need to get going to classes, but will help you with everything else, as well. It's easy, just be patient.
P.S. Ignorance killed your defy+, not awesomeness
Cheers!
Click to expand...
Click to collapse
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
FlashTec80 said:
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
Click to expand...
Click to collapse
Decompress .gz
And yeah i u get stuck at the Motorola Bootanimation pull the battery and goto stock recovery and wipe data that should boot it...
Sent from my MB526 using xda premium
FlashTec80 said:
You are so true, my most serious side of ignorance put me here and your best side of awesomeness seems to save my ass, i hope
Noticed that the file that im downloading was namned .gz as a file ending, should i just delete that part or do i need to do something with it, decompress or something?
I cant try this before i get home from work but i will try it later, a quickie, would u suggest CM7 or MSginger do be installed over this in the ending? Or would u suggest something else
that u know works good
Hope classes going great and have a safe day
Regards.
Click to expand...
Click to collapse
Had a safe day Some bloody hooligans were on the bus home, though... Goddamn idiots. Anyway, on the brighter side of life...
You got your phone working again, mate? I suggest you stick with your stock ROM until tomorrow, then I'll walk you through the ROM's I've used and that'll help you make your pick and I'll help you with installing them, as well.
The fact that it's midnight here and that I get up at 6 for classes tomorrow is the reason you will have to wait for me
niksy+ said:
Had a safe day Some bloody hooligans were on the bus home, though... Goddamn idiots. Anyway, on the brighter side of life...
You got your phone working again, mate? I suggest you stick with your stock ROM until tomorrow, then I'll walk you through the ROM's I've used and that'll help you make your pick and I'll help you with installing them, as well.
The fact that it's midnight here and that I get up at 6 for classes tomorrow is the reason you will have to wait for me
Click to expand...
Click to collapse
Bloody hooligans should just go home and stay there
Yepp its working now but in a rush as i always is, its now running MS2Ginger 3.0, thought i´ll go that route till there is a proper ICS version of something out there
Thanks for all the help, with it i would for sure still be in pure panic mode
Know anything about overclocking the Defy+?
FlashTec80 said:
Know anything about overclocking the Defy+?
Click to expand...
Click to collapse
SetVsel
King_Rat said:
SetVsel
Click to expand...
Click to collapse
Ok i´ll try that, how high is it possible to go to still be stable?
FlashTec80 said:
Ok i´ll try that, how high is it possible to go to still be stable?
Click to expand...
Click to collapse
I'm glad you got to MS2G by yourself
I think the best way is to overclock in Recovery. You'll find the CPU menu when you open it and there you'll see 3 or 4 different settings. Every setting has a clock option and a vsel option. vsel sets the amount of electrical power that the CPU gets at a certain clock.
Best way to overclock would be to go step by step. Increase the highest clock setting by 50MHz, then reboot your phone and see if it works OK If it doesn't boot successfully or it hangs while you're using it - increase the vsel by 1. Then if it's stable, go on, another 50MHz+ and testing again...
Other than that, you can just set it to 1200MHz at once and increase the current vsel for that clock setting by 3-4, that would probably work as well
I have never overclocked mine, though Well, actually, the WIUI ROM come's with overclocked setting itself, it was at 1.1GHz, but it was slower than Pikachu at 1.1GHz So, overclocking doesn't help as much as a good ROM does At least that's my opinion.
P.S. CM9 (ICS) is wonderful But, you should wait for a couple more builds, while the things get even better. For me, CM9 and stock ROMs (including ms2ginger) are the best! You can always test, anyway I've come down to CM7 from CM9 and I'm truly sad
Defy+ stuck at boot amnimation
Hello everyone, my Defy+ stuck at Motorola boot animation. And I have the message below when Volume Up + Boot key :
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB
My sbf is :
DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTFR004.0R_PDS03C_USAJRDNGIBRRTFR_P020_A024_M002_Service1FF.sbf
With the others it just doesn't work.
Please help me.
Well, why don't you flash that sbf to get it back to life?
FlashTec80 said:
Ok i´ll try that, how high is it possible to go to still be stable?
Click to expand...
Click to collapse
I'm on 300 - 19, 700 - 33, 1200 - 54...
just don't set your tweaks @ boot until you've fully tested them ^^ yet a cache clear would rectify being stuck in b/l
That sbf is the only one to make at least my phone stuck in the boot loop.
The others just don't show me anything, I got a black screen.
Maybe the sbf isn't the good one ?
I have done a backup of my system before I used rsd lite. How can I restore it as it's not a sbf file but a directory with .img ... files ?
Good replies every1, i dont know if im doing anything wrong here.
I first installed SetVsel app and changed the values in there, then when running stabilitytest it said i had the value i had chaged to. Uninstalled the app and tried to change value directly in 2ndinit but now when running stabilitytest it sais i only have 1000Mhz, thou in 2ndinit it clearly sais that vsel4 is set to 1200, any idea?
Cheers and have a safe day every1
Edit: "vsel sets the amount of electrical power that the CPU gets at a certain clock", so how high is it possible to push it before i see smoke coming out of my phone?
FlashTec80 said:
Good replies every1, i dont know if im doing anything wrong here.
I first installed SetVsel app and changed the values in there, then when running stabilitytest it said i had the value i had chaged to. Uninstalled the app and tried to change value directly in 2ndinit but now when running stabilitytest it sais i only have 1000Mhz, thou in 2ndinit it clearly sais that vsel4 is set to 1200, any idea?
Cheers and have a safe day every1
Edit: "vsel sets the amount of electrical power that the CPU gets at a certain clock", so how high is it possible to push it before i see smoke coming out of my phone?
Click to expand...
Click to collapse
You need to enable overclock in 2ndinit or load all modules enabled for it to take effect of your changes..
farsight73 said:
You need to enable overclock in 2ndinit or load all modules enabled for it to take effect of your changes..
Click to expand...
Click to collapse
Good post
Could someone with an non overclocked Defy+ make some runs in Quadrant Benchmark, i only made one run before i started changing things
Would also be fun to see some figures on an ordinary Defy
Just two hours left of work this week, then Top Gear Live is the thing for the evening
I did solve my problem. Thanks to anyone
godbod said:
Hello everyone, my Defy+ stuck at Motorola boot animation. And I have the message below when Volume Up + Boot key :
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB
My sbf is :
DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTFR004.0R_PDS03C_USAJRDNGIBRRTFR_P020_A024_M002_Service1FF.sbf
With the others it just doesn't work.
Please help me.
Click to expand...
Click to collapse
go to recovery mode and wipe to the factory setting.
this happened because your phone is confused between the old and new firmware..
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
And actually it might even be a safer approach to revert to stock from a stock like rom http://forum.xda-developers.com/showthread.php?t=1439916
Bricked beyond all recognition baby!
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
putney1477 said:
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
Click to expand...
Click to collapse
Even if you want to go back to pure stock, keeping/reinstalling both TWRP and FFF are the safest and smartest things to do.
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
putney1477 said:
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
tamaker said:
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
Click to expand...
Click to collapse
I have the same problem, but my battery was 100% when flashing back. Is this good night for the kindle then?
It boots in to the 6.2.2 software, but these errors pop up and force close then eventually does a restart. Dammit!
putney1477 said:
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Dasanko said:
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Click to expand...
Click to collapse
oh ok, thanks
Just a side note after restoring to stock you need to then perform a factory restore as well which will wipe your sd card if all goes well it should smooth out from there
Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
putney1477 said:
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
Click to expand...
Click to collapse
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Dasanko said:
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Click to expand...
Click to collapse
OMG! I can't thank you enought for taking the time to answer all of my questions!!! It worked!!!! I am back to stock! (I had no doubt, thanks to you!) THANK YOU!!!
Heather
**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930A_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930A_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Will it work for g935a? And does it fix lag?
Sent from my SAMSUNG-SM-G935A using Tapatalk
Awesome!
Ok how many folks have successfully flashed this?
It's still using eng boot? And will I be able to update super su script once installed? Also curious if maybe deodexed means I can get v4a running on this bad boy sorry for the question blast just excited to see the att s7 taking off into #root =D in Texas it goes "y'all got root?!"
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Can you fix the URL? I get a 404 when clicking it.
Thanks,
Aaron
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
smknutson said:
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
Click to expand...
Click to collapse
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
I think I am. It's either this Rom or the eng bootloader, but it runs hotter. It's running in interactive governor but cpu temperature is averaging idle at 45°c whereas on stock it felt much cooler. Something about this installation is causing this thing to heat up.
Carlos Terán said:
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
I'm not sure what lag you're referring to?
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
noobtxtech said:
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
Click to expand...
Click to collapse
Haven't tried v4a but Wanams modified Xposed is working and I have several modules operational.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
dirtydodge said:
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
Click to expand...
Click to collapse
Modified Odin for both EngBoot and this threads addon .zip
smknutson said:
Modified Odin for both EngBoot and this threads addon .zip
Click to expand...
Click to collapse
Ok thank you. Figured so but just wanted to make sure. I'm downloading the Rom now. Glad you found the fix and debloat from the Verizon thread, I seen that the other day and used it and his other guide on how to set up Greenify and amplify. My phone is running awesome on the stock rooted but I always like to grab muniz's deodex versions and run them.
Also, if you want to get rid of the Custom icon on boot and reset it to Official in status, use the XTouchWiz xposed module.
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
joe3681 said:
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
Click to expand...
Click to collapse
You have to be rooted prior to flashing this.
Clearly. I meant post flash
joe3681 said:
Clearly. I meant post flash
Click to expand...
Click to collapse
" To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy! " is copy pasted from the OP so that would imply that it isn't rooted until you root it, as for why you would want a deodexed Rom (which is a performance hit) without root is beyond me. From what I gather reading this short thread you will need root and possibly even xposed to get it running right. In order to do that you would have to do some more reading. Hope this helps.