Seen as there was no reply to my last thread ( question too complicated!? ) here's an easier one, is there a temporary CWM Recovery that can be used on an unrooted Xoom WiFi version JB 4.1.2???
Related
Hello,
I'm back in home after 2 months trip in India & Nepal
My TF is still alive and I had it at Thorung La (5416m)
My tab is rooted and also CWM recovery is installed.
Before trip I frozen DMClient app, in order to omit upgrade notifications,
of course I can unfroze it now.
Two questions:
It is good idea to upgrade to ICS ? During my trip i red few posts about problems with ICS i.e. battery draining problem. My tab works perfectly now with 8.6.5.21
I know, I have to back to oryginal recovery before update, it can be done, flashing zip file from CWM, but I can't find zip file with oryginal recovery, full bersion name is HTK75.WW_epad-8.6.5.21-20111216
thanks.
Why not just flash a rooted ICS ROM? That way you don't have to install stock recovery just to do an update.
I dont realize that is possible I'll try to find thread about this at evening. What about my first question, upgrade or not? Did Asus fix any issues? Maybe best idea is to wait some time?
Sent from my HTC Desire using Tapatalk
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
marclabrosse said:
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
Click to expand...
Click to collapse
no, u need to flash su, gb or ics its still the same process, maybe w/oneclick but i never tried that method
but whats the problem using cwm, its very safe todo and its y we can do so many things with our phones, and if need b u can always flash back to stock ics w/sammobile.com firmware files
afraid to say you'll have to have a cumstom recovery. SuperOneClick wont work. It actuallt will only work on GB 2.3.5. 2.3.6 wont. And I'm pretty certain ICS wont either.
Thanks guys, yeah I tried GB methods or rooting without CWM Recovery before posting, no go...should have rooted before upgrading her phone via Kies...
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store.
I've had mine running CWM recovery from day one, but I can restore it to stock without a problem, she's not technical at all... its her "Facebook" phone...
I guess CWM recovery will be going on there shortly...
marclabrosse said:
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store...I guess CWM recovery will be going on there shortly...
Click to expand...
Click to collapse
You can flash back to 3e recovery without losing root. Unrooting is covered in post #10 here: http://forum.xda-developers.com/showthread.php?t=1726445
Hi all, bit of help if you can please.
Just bought a XOOM Wifi 32GB 2nd hand and it has come with JB on it and I know nothing about rooting/flashing the Xoom and want to revert to stock ICS, then learn how to do it.
Details are
Android version 4.1.1
Kernel 2.6.39.4-Eos3-g91a0873
Build No Eos JR003L Nightly 135
It has clockwork recovery 3.2.0.0 on it which I can get into via recovery but if I do the power off and volume down in gets stuck in fastboot
It has a app on it called goomanager but no idea what to do next and works fine but I would really like to stop beeing a noob and get this back to latest stock ICS, root it and then go from there - is there an easy instruction on how to do this (with explanations of each step etc)?
Many thanks
Simon
Hi,
I apologize in advance for any "noobish" questions, but I'm new to rooting... and if a solution to my issue is out there, please point me in the right direction - I've seen many people having different approaches to this type of issue, therefore I would like some help getting on the right track
I have a Samsung Galaxy S3 I747M which I have successfully rooted ( I think! ) and installed a custom recovery, but I am still encountering issues flashing custom ROMs...
To get in details to what I did ( chronological order )
- I followed all steps given in this site - http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
( looked simple enough in comparison to other processes I've found )
All went has planned until I had to install a custom ROM - CM10 wouldn't install at all and LiquidSmooth would install, but multiple apps wouldn't work properly.
Lucky me, I had done a backup of my current ROM before flashing a custom ROM, therefore I was able of going back to the Rogers ROM.
I assumed the issue would be due to the CWM version not being compatible with CM10 ( and maybe that ws the case with Liquid ) so I ended up installing GooManager and changing my Recovery Mod to TWRP. The issue of not being able of flashing custom ROMs persisted.
So I ended up following what Mr. Robinson posted on http://forum.xda-developers.com/showthread.php?t=1739426
-With Odin I flashed my phone with root66_RWC_I747MVLDLK4.tar.md5
-after reboot GooManager was still installed ( obvious ) so I attempted multiple times to flash custom ROMs without success.
I have removed my external SD card, rebooted and removed battery, etc.
I have been getting in most cases "Status 7" as a error message when trying to flash custom ROMs.
I have SU installed, I have done the "fix permissions",...
What am I doing wrong and/or what am I missing in this process to be able of flashing custom ROMs?
Help would be greatly appreciated!
Thanks in Advance!!
I've also noticed that I have multiple "0" folders in the SD card. For my understanding this is due to trying to install a 4.2 with an old CWM version...
Is it possible that this is what initiated the whole issue?...
So, after searching for a bit I resolved all my issues.. I'm going to post what I did and my current setup in hopes to help other people who have been having trouble getting their Canadian galaxy S3 rolling with a custom ROM. This should apply to any i747m devices, but I have the Rogers one...
For my understanding the beginning of my issues was flashing an old version of CWM. Try to always flash the latest version of CWM or TWRP. I'm currently using the TWRP 4.3.3 WITHOUT ANY ISSUES.
I then flashed AOKP on JB 4.2.1. My phone has been working perfectly since then (besides for some minor known bugs) - make sure to do all the wipes advised on any ROM instructions and you should be fine. You will also need to change the Internet provider settings to reflect your speed and provider.
Sent from my SGH-I747 using xda app-developers app
Just wanted to say thanks for posting a follow-up on how you solved your issue. I'm looking into rooting and custom-rom-ing my Koodo GS3 and so many threads are started and then abandoned. So cheers to you good-guy OP!
fishy007 said:
Just wanted to say thanks for posting a follow-up on how you solved your issue. I'm looking into rooting and custom-rom-ing my Koodo GS3 and so many threads are started and then abandoned. So cheers to you good-guy OP!
Click to expand...
Click to collapse
you can always just hit the "thanks" button
Cheers!
fishy007 said:
Just wanted to say thanks for posting a follow-up on how you solved your issue. I'm looking into rooting and custom-rom-ing my Koodo GS3 and so many threads are started and then abandoned. So cheers to you good-guy OP!
Click to expand...
Click to collapse
Something else. Consider changing your custom recovery from d2can to d2att. The number of ROMs out there for d2att is way higher that d2can ROMs.
Good luck!
Sent from my SGH-I747 using xda app-developers app
Headphone socket issue
There is no sound coming out from the headphones when i insert them....and when i unplug the sound on the speaker doesnt work too..It's NOT A HARDWARE ISSUE cuz i checked that it worked perfectly on the stock rom...but when i flash Roms it doesn't work at all...
PLS HELP!!!!
@Mikyno
First of all, big thanks for your work, your ROM is great!
Now, to the questions part. First time I upgraded to Gnabo Rom V2 from stock 4.1.2, and I did't change bootloader. I just flashed from CWR Gnabo V2 ROM + SU, so after the reboot Wi-Fi detected networks but couldn't connect. Then I flashed Wi-Fi-Fix for N8013 (http://forum.xda-developers.com/atta...7&d=1401120355) and everything was fixed and worked almost perfectly (could not start(find) Wi-Fi-access point to share 3G-internet).
Now, as V3 was released, I tried the same route, but it was different from the start - I couldn't even activate Wi-Fi, and above-mentioned Fix did nothing.
Questions are:
1) Do I have to update the bootloader to make Wi-Fi work with V3 ?
2) What version of bootloader I need to use for my N8000 ?
3) Will it be possible to downgrade(restore from backup) back to 4.1.2 with the new bootloader ?
4) Will it be possible to restore the old stock bootloader after using the new one ?
5) Does Wi-Fi access point work on Gnabo V3 ?
1) No you do not need to update bootloader
But you do need to install the WiFi fix and also the kernel for v3 in order to allow the wifi to work.
Stratos
stratism said:
1) No you do not need to update bootloader
But you do need to install the WiFi fix and also the kernel for v3 in order to allow the wifi to work.
Stratos
Click to expand...
Click to collapse
Thanks for the answer.
In the Gnabo V3 topic there is a link to kernel (http://forum.xda-developers.com/attachment.php?attachmentid=2764247&d=1401120355) , but it somehow confusing: the file name states, that it is for N8000 (Stock-GT-N8000-leaked-KK-Boot.img-CWR-installer.zip), but then there's a description for this link there, and it says "Kernel for N8013 (and N8010 maybe?)".
In the Gnabo ROM topic people always mention this link for N8010 and N8013 ... Is it OK to use that kernel for N8000 ?
Also, please help me understand - flashing the kernel is only affecting the ROM-part ? If I flash it, will it be possible to restore old backups (made from CWR) ? It's the "Boot.img" part of the file name that bothers me. I somehow afraid that if it changes bootloader it will be impossible to restore from older backups (made with the stock loader). I really hope that my concerns are unfounded, but I'd like to be sure
Chieftain486 said:
Thanks for the answer.
In the Gnabo V3 topic there is a link to kernel (http://forum.xda-developers.com/attachment.php?attachmentid=2764247&d=1401120355) , but it somehow confusing: the file name states, that it is for N8000 (Stock-GT-N8000-leaked-KK-Boot.img-CWR-installer.zip), but then there's a description for this link there, and it says "Kernel for N8013 (and N8010 maybe?)".
In the Gnabo ROM topic people always mention this link for N8010 and N8013 ... Is it OK to use that kernel for N8000 ?
Also, please help me understand - flashing the kernel is only affecting the ROM-part ? If I flash it, will it be possible to restore old backups (made from CWR) ? It's the "Boot.img" part of the file name that bothers me. I somehow afraid that if it changes bootloader it will be impossible to restore from older backups (made with the stock loader). I really hope that my concerns are unfounded, but I'd like to be sure
Click to expand...
Click to collapse
That is correct. You can use the kernel for N8010. I do also have the N8010 but somehow it is "shown as" N8013...