Here's an updated version from my earlier patch of thor's 1.7 recovery for the A510. This one has the proper mapping for the data partition (mmcblk0p10). I set the version number as 1.7b.
To recap:
Thor's 1.7 cwm recovery repacked with A510 stock kernel. itsmagic is disabled. overclocking does not work, since it's a stock kernel.
This is exactly the same as the one I repacked for the A200, but with the A510 stock recovery kernel and edited the kernel string to show when it boots. And also changed the fstab for /data to use mmcblk0p10.
You MUST unlock your bootloader before flashing this.
You can rename it to recovery.img and put it on your microsd card and use Acer Recovery Installer to flash it. Or you can use the following command in a terminal emulator or adb shell.
Code:
dd if=thor_recovery17b_A510.img of=/dev/block/mmcblk0p1
Give it a try and see if it works.
***Link Removed***
Cheers!
WARNING: If you downloaded the link I posted earlier that has MD5 of 1ded94b4b4f0522ca14b7070146d9a49, DO NOT USE IT! Download 1.7b above instead.
Edit: Updated to 1.7c to fix some mounting issues.
You MUST unlock your bootloader before flashing this.
please tell me how unlock A510.
thank you
Updated OP with new image to fix some reported mounting issues. Please give this a try. Also remember, that I do not have this device, so I rely on you guys to let me know what doesn't work. So far, the only feedback i've gotten is from NoThrills (Thanks buddy).
Euclid's Brother said:
Here's an updated version from my earlier patch of thor's 1.7 recovery for the A510. This one has the proper mapping for the data partition (mmcblk0p10). I set the version number as 1.7b.
Click to expand...
Click to collapse
This is awesome! Thank you. Will install now.
Dave Burbank
asdf20003 said:
You MUST unlock your bootloader before flashing this.
please tell me how unlock A510.
thank you
Click to expand...
Click to collapse
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
Then follow the on screen instuctions very quickly.
Sent from my SPH-D710 using Tapatalk 2
Euclid's Brother said:
Updated OP with new image to fix some reported mounting issues. Please give this a try. Also remember, that I do not have this device, so I rely on you guys to let me know what doesn't work. So far, the only feedback i've gotten is from NoThrills (Thanks buddy).
Click to expand...
Click to collapse
LOL... And there I was fixing it myself this afternoon I think we both noticed that 1 line that was missing in the fstab
After changing tab to use the named devices like the stock recovery, it seemed like it was having even more trouble, so I reverted back to the original fstab and just changed data to mmcblk0p10.
Is it working okay now?
is only for A510 ? if i try for A501 is can be?
euclid, what has changed with the new recovery kernel, i can't get twrp to boot.i sent a gtalk request.
D3v17 said:
is only for A510 ? if i try for A501 is can be?
Click to expand...
Click to collapse
strictly for the A510. It will not work on anything else! The data partition is in a different place.
ibsk8 said:
euclid, what has changed with the new recovery kernel, i can't get twrp to boot.i sent a gtalk request.
Click to expand...
Click to collapse
Who knows. try repacking it with the stock recovery kernel. You'll also need to update the partition device for Data in recovery.fstab
Euclid's Brother said:
You must have the ability to send adb commands to the tablet.
adb reboot-bootloader
fastboot oem unlock
Then follow the on screen instuctions very quickly.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Brother,
Is the above applicable to A500 OTA ICS 4.0.3 bootloader?
Sent from my A500 using Tapatalk 2
wcrov said:
Brother,
Is the above applicable to A500 OTA ICS 4.0.3 bootloader?
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
NO
He stated already. JUST for the A510 which is the new Tegra 3 tablet. Replacement for the old 500 series
recovery successfully installed.
and now? what is the next step ;-)
how to help people from there to go further in rom cooking and all that stuff ?
anyway, thanks a lot euclid's brother,
I thought this version of thors recovery was not GPL compliant. If it is not be careful, the angry hordes will decend on this thread and you will get banned. Even mentioning of the name of thor is enough to cause you grief.....oh wait, its recovery, not his rom, so those who have a bone to pick turn a blind eye...carry on.
If this is based on the work of a banned developer then I'm afraid we do not wish for it to be posted here.
I'd suggest taking an alternative recovery to amend.
Related
Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help
Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!
FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.
Is there a method for Rooting/Changing Kernal of Stock 3.2 3G Verizon Xoom yet?
I got this xoom for a steal (400$ for someone else's contract cancellation) and it's stock on 3.2. Any advice?-AT
I think it is the same as 3.1. You have to go backwards. And then manually updated to 3.2.
Sent from my ADR6400L using XDA Premium App
Not directly, but you can downgrade the firmware quite easily. First make sure you have adb and fastboot working. There are guides out there on how to do that. Then go into fastboot and type in without quotes "fastboot oem unlock". That will wipe your data so backup if necessary. After that, download the stock images for 3.0 here. All these images are for 3.0, just make sure you pick the right model. Once you have downgraded, let motorola update you to 3.1, from there you can then follow a guide for rooting 3.1 stock on verizon 3g xoom.
Thanks for the info. I will try to root from unlock from 3.2 stock using fast boot and let you know how it goes.-AT
Neofury212 said:
Thanks for the info. I will try to root from unlock from 3.2 stock using fast boot and let you know how it goes.-AT
Click to expand...
Click to collapse
Can someone please provide me with a working link to download xoom root toolz? Thanks-AT
In the end what you you want to have?
If you are going to the rom, its already rooted.
Fastboot OEM unlock
Fastboot flash recovery recovery.img (cwm from the forums)
[Install tiamat kernel and superuser.apk and su binary] or [just Install tiamat rom.]
Sent from my Xoom
bwcorvus said:
In the end what you you want to have?
If you are going to the rom, its already rooted.
Fastboot OEM unlock
Fastboot flash recovery recovery.img (cwm from the forums)
[Install tiamat kernel and superuser.apk and su binary] or [just Install tiamat rom.]
Sent from my Xoom
Click to expand...
Click to collapse
I know I can fastboot root while on 3.2 ota, but I would LIKE to have a ROM/kernal to install instead of just rooting. I cant seem a tutorial on how to start from 3g 3.2 and get to custom kernal/rom. I really appreciate the direction you are providing.
Neofury212 said:
I know I can fastboot root while on 3.2 ota, but I would LIKE to have a ROM/kernal to install instead of just rooting. I cant seem a tutorial on how to start from 3g 3.2 and get to custom kernal/rom. I really appreciate the direction you are providing.
Click to expand...
Click to collapse
also I cant find root toolz anywhere.-AT
Neofury212 said:
I know I can fastboot root while on 3.2 ota, but I would LIKE to have a ROM/kernal to install instead of just rooting. I cant seem a tutorial on how to start from 3g 3.2 and get to custom kernal/rom. I really appreciate the direction you are providing.
Click to expand...
Click to collapse
I just told you. You just need to OEM unlock, install recovery, then install rom in recovery. You don't need a root.zip. Roms are already rooted.
Sent from my Xoom
bwcorvus said:
I just told you. You just need to OEM unlock, install recovery, then install rom in recovery. You don't need a root.zip. Roms are already rooted.
Sent from my Xoom
Click to expand...
Click to collapse
I know I am beating the dead horse to death here but I just want to clarify everything one last time:
1.OEM unlock - I understand!
2. Install Recovery - Which versions of recovery are 3G 3.2 compatible? or are all recovery images the same?
3. Rom in Recovery - Again, I just want to make sure I am selecting a 3G compatible rom. I know that all roms have root access. What I am unsure of is if a custom kernal is included in the rom (never had to worry about this on my bootlocked DX).
Thank you so much for being patient with me and my new Xoom 3g. I how you can remember how frustrating it was when you first got you Xoom. I already love my Xoom and I know I will love it even more once I OC 50%+ and have root access Adam
It really only matters if it is wifi it 3g. It is not that hard on the xoom.
Sent from my ADR6400L using XDA Premium App
Neofury212 said:
I know I am beating the dead horse to death here but I just want to clarify everything one last time:
1.OEM unlock - I understand!
2. Install Recovery - Which versions of recovery are 3G 3.2 compatible? or are all recovery images the same?
3. Rom in Recovery - Again, I just want to make sure I am selecting a 3G compatible rom. I know that all roms have root access. What I am unsure of is if a custom kernal is included in the rom (never had to worry about this on my bootlocked DX).
Thank you so much for being patient with me and my new Xoom 3g. I how you can remember how frustrating it was when you first got you Xoom. I already love my Xoom and I know I will love it even more once I OC 50%+ and have root access Adam
Click to expand...
Click to collapse
Grab cwm 3.2.0.0 from the forum for your recovery. Grab tiamat 2.1 for your rom. It has 3g and oc kernel.
Sent from my PG86100 using Tapatalk
bwcorvus said:
Grab cwm 3.2.0.0 from the forum for your recovery. Grab tiamat 2.1 for your rom. It has 3g and oc kernel.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I have Adb unlocked my device...
I have adb push installed cwm boot using method 2 here: http://forum.xda-developers.com/showthread.php?t=1074979
Now I am installing a ROM! will let you all know how it goes! (i need to finish up before my wife gets home and sees her xoom _
Neofury212 said:
I have Adb unlocked my device...
I have adb push installed cwm boot using method 2 here: http://forum.xda-developers.com/showthread.php?t=1074979
Now I am installing a ROM! will let you all know how it goes! (i need to finish up before my wife gets home and sees her xoom _
Click to expand...
Click to collapse
Ok, here is where i am stuck now.... I have CMW 3.2.0 installed via adb fastboot. I still don't have any root access so I can't boot into cwm to install a Rom.... I guess there isn't a root image out for 3g on 3.2 yet...only wifi I guess I will weight with my STOCK kernal til someone smarter figures this one out
Neofury212 said:
Ok, here is where i am stuck now.... I have CMW 3.2.0 installed via adb fastboot. I still don't have any root access so I can't boot into cwm to install a Rom.... I guess there isn't a root image out for 3g on 3.2 yet...only wifi I guess I will weight with my STOCK kernal til someone smarter figures this one out
Click to expand...
Click to collapse
I was able to install a rooted rom over stock 3.2g. I have written down how i did it: http://forum.xda-developers.com/showthread.php?t=1211020 Hope it helps someone else! gl-AT
PLEASE READ
Cornea, the universal toolkit tool I promised following XOOT's discontinuation, has been released! It's free, and tons better. Please check it out rather than downloading XOOT. Click here to go to the thread page. Thanks.
(XOOT will still be available for download if you want it for whatever reason.
Bugs
XP not supported properly. This will not be fixed. It has been fixed in the new version of XOOT, Cornea.
Changelog
1.1 (CURRENT VERSION)
XP x86 compatibility! (not working)
Compressed file changed from RAR to ZIP so that users don't need WinRAR or equivalent to extract XOOT
1.0
Initial release of XOOT
Sorry that this isn't in Android Development, I have less than 10 posts and I can't wait to share this...
XOOT is the easiest tool you can use to root your XOOM! It works for XP 32bit, Vista, 7 and 8 flawlessly. In fact, it does more than root. Here's the grand list:
Bootloader lock/unlock (WIPES DATA)
Root your XOOM (thanks solarnz)
Convert from a region XOOM to a GED XOOM
Flash non-flashable boot animations
Includes ADB and FASTBOOT for all your Android developing needs!
Brick your device if you are ruthless and unplug it during the progress.
HONG KONG USERS SHOULD STAY AWAY. PLEASE?
IF YOU'VE DONE OTA UPDATES READ THE POST ON THE SECOND PAGE ABOUT THE GREEN ANDROID OF DEATH.
XOOM ADB drivers are required to benefit from XOOT! Please download them and install.
Hope you guys benefit from this. It definitely works because I used it to root, flash recovery, unlock bootloader and flash boot animations.
If you're amazing at ADB, try adding more commands! All ya need is a bit of batch programming experience. If you plan to just use this and enjoy, OK! Just open and go!
FAQ included in the ZIP.
Please read: Now that XP compatibility has been added, XOOT is harder (but still easy) to open.
If you are running XOOT on Windows XP or Server 2003, rename choice_xp.exe to choice.exe. Then proceed.
If you are using XOOT on a version higher than XP, open XOOT.bat without renaming Choice_XP.exe
Have fun with your XOOM!
PLEASE NOTE THAT I AM NOT RESPONSIBLE FOR ANY ISSUES CAUSED
~Epic118
i am not responsible if this goes cockeyed, btw
has any1 tried this? cheers
Region xoom to ged xoom? What does that mean?
Sent from my MZ601 using XDA App
Region/GED Xooms
A region XOOM is one that's not in the US. It may have changes made by Motorola, and get updates slower. This is why UK Xooms have SD card read/write officially.
A GED XOOM is a XOOM that's in the US. It's known as a Google Experience Device, and cannot be modified my Motorola. This is why US Xooms have SD card readonly officially - they are not allowed to add the hacked mod to enable write.
I read this on a website. Sorry but I can't find out which one, I will give you the URL link soon...
Anyone tried yet? Am contemplating.
Will it work on a Singapore version of Motorola Xoom MZ604 on 3.2?
Hi, will it work on my Hong Kong MZ601 3G Xoom
BlueEditionE6 said:
Hi, will it work on my Hong Kong MZ601 3G Xoom
Click to expand...
Click to collapse
Be careful with your Hong Kong Xoom. They seem to have different partition set-ups and have been known to lose (misplace) 28 gb of their internal storage when rooted/modded without a particular patch made by solarnz. Have you seen this thread: http://forum.xda-developers.com/showthread.php?t=1203128 ?
Anybody with a VZW Zoom use this to unlock and root?
Sent from my LG-P925 using xda premium
Zacky32 said:
Will it work on a Singapore version of Motorola Xoom MZ604 on 3.2?
Click to expand...
Click to collapse
Should do. I think mine is a Singapore XOOM because when I first turned it on the language was set to English (Singapore).
HONG KONG XOOM owners STAY AWAY. I have read that solarnz's universal root thing doesn't work wonderfully well on those.
Sorry new on here and to root (rooted my htc magic ages ago)
Is this the real deal and will this work on my uk wifi XOOM?
Thanks
Sent from my xoom using xda premium
This for WIFI only model? or LTE/4G devices?
the green bot of !
Ok this thread is missing some things.
* Fastboot OEM Unlock Wipes your Tablet. backup first!
* The green bot of !
there is one problem that exists with all xoom roots/cwm hacks.
I had this problem as well as a bunch of other people when trying to flash CWM.
If these files are present after a OTA update then your xoom when entering recovery will show the green android robot with a explanation point instead of CWM.
if you have applied a official ota update.zip then you have one of the following two files on your xoom that will prevent CWM from working.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
If you already have root and your not trying to root with CWM then you can fix this issue with the following commands before flashing the recovery.img
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
If you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
This Wipes your Xoom also
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
after your xoom boots back up and goes into the setup screens skip setup and enable usb debugging. ( do not install a ota update! )
and restart xoot to root the stock rom.
joe ferreira said:
Ok this thread is missing some things.
* Fastboot OEM Unlock Wipes your Tablet. backup first!
* The green bot of !
there is one problem that exists with all xoom roots/cwm hacks.
I had this problem as well as a bunch of other people when trying to flash CWM.
If these files are present after a OTA update then your xoom when entering recovery will show the green android robot with a explanation point instead of CWM.
if you have applied a official ota update.zip then you have one of the following two files on your xoom that will prevent CWM from working.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
If you already have root and your not trying to root with CWM then you can fix this issue with the following commands before flashing the recovery.img
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
If you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
This Wipes your Xoom also
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
after your xoom boots back up and goes into the setup screens skip setup and enable usb debugging. ( do not install a ota update! )
and restart xoot to root the stock rom.
Click to expand...
Click to collapse
Thanks, didn't know about that. I'll be adding some more code to XOOT soon to tackle this.
XOOT does notify you that locking/unlocking bootloaders does wipe the device. However I will modify the main post to show this.
Can anyone tell me where to get the ged files from, I've searched for them but really don't know what I'm looking for.
Thanks in advance
@joe ferreira,
I have quoted you in my adb/fastboot/rooting guide, as I didn't know why so many newer Xoom owners are having issues flashing CWM recovery.
@epic118, I'm also really interested in whether the Xoot method works safely...it would make life a whole lot easier for a lot of people! The Xoom community is a little shy about one-click rooting methods, since one last spring bricked a whole bunch of tabs, but if proven effective and safe, folks would eat it up.
---------- Post added at 10:57 PM ---------- Previous post was at 10:47 PM ----------
toori88 said:
Can anyone tell me where to get the ged files from, I've searched for them but really don't know what I'm looking for.
Thanks in advance
Click to expand...
Click to collapse
Your stock files are available in a couple of threads pinned to the top of the General forum, or from the motodev site.
What is the best way to backup without having root capabilities yet to utilize an app like Titanium?
Sent from my Xoom using XDA App
Never mind, I was under the impression that rooting the Xoom wipes it right off the bat. It seems this is only when you unlock the boot loader.
Sent from my Xoom using XDA App
just using xoot to root my device,
i have unlocked te bootloader,
currently flashing with cwm recovery but its stuck on starting fast boot protocol support. should it stay on that for a while the first time?
EDIT:
never mind when i rebooted holding vol up and power to try go into fast boot all i get is "starting RSD protocol support 3"
i don't know what this means but it will power up normally
I've got a couple ICS 8GB A500's I'm trying to flash so I can do the memory swap thing with 16gb microsd's. I'm stuck at the very beginning trying to get an unlocked bootloader and clockworkmod installed.
I've followed several of the guides and they all seem to be failing at the same spot. I've done blackthund3r and afterota and V8-UNL-ICS-HC-bootloader-MULTI-cwm script with no luck.
I'm pretty sure the problem is something to do with my BCT. Running afterota to flash or blackthund3r w/o custom BCT each puts the tablet into the recovery mode but nvflash errors on a bunch of partition commands and fails to upload the images (afterota sticks on 3/5 for instance or blackthund3r hangs uploading the bootloader).
My guess is that it's because my BCT is different from the majority of every elses because I'm using the little 8gb version.
I tried blackthund3r using the extract BCT, but it simply hangs immediately after loading the bct and never gets the tablet into recovery mode. I looked at the extracted bct.dec, and it looks like the same few bytes repeated over and over (nothing like the default bct's) so I'm pretty sure that blackthund3r is failing to extract my BCT properly.
Can anyone assist me in getting a valid bct.bct for my 8gb devices so I can make some forward progress? (calling Blackthund3r if you're out there...)
Version info according to afterota. I also have the serial, cpuid, and sbk according to afterota:
Android Build: Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS
The only way to fix bct errors usually is to roll back to HC via timmydeans v4 or with srbeens direct nvflash command... if u have Ubuntu try nvflash with it
One thing tho is I don't know if the partitions, bct are the same for the 8gb - guess only one way to find out aye
U myt wanna look at jdgment3ls easy pass thread regarding reverting to stock
Let us know how u get on, good luck!
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
The only way to fix bct errors usually is to roll back to HC via timmydeans v4 or with srbeens direct nvflash command... if u have Ubuntu try nvflash with it
One thing tho is I don't know if the partitions, bct are the same for the 8gb - guess only one way to find out aye
U myt wanna look at jdgment3ls easy pass thread regarding reverting to stock
Let us know how u get on, good luck!
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I tried using jdgment3ls method and that failed (I got the acer icon with the red letters about failed validation or something...can't remember).
I went with timmydeans v4 and boom...back on honeycomb. From there acer recovery got me clockwork. I also ran blackthund3r's upgrader with default bct and it worked perfectly this time so now I have a hacked ICS bootloader and clockwork recovery. As soon as the ICS rom finishes I should be back to ICS and can restore my data.
Thanks for the help.
ybarra said:
I tried using jdgment3ls method and that failed (I got the acer icon with the red letters about failed validation or something...can't remember).
Click to expand...
Click to collapse
oh, "boot recovery failed"?? thanks for testing it out, was worth a go
I went with timmydeans v4 and boom...back on honeycomb. From there acer recovery got me clockwork.
Click to expand...
Click to collapse
just a note, tdv4 has cwm pre-installed
I also ran blackthund3r's upgrader with default bct and it worked perfectly this time so now I have a hacked ICS bootloader and clockwork recovery.
Click to expand...
Click to collapse
Fantastic, pleased it worked for u
As soon as the ICS rom finishes I should be back to ICS and can restore my data.
Click to expand...
Click to collapse
ICS???? Stock???? this will overwrite yr recovery with the stock recovery??
The procedure requires u to put a rom on yr card to flash straight into after patching the BL - most folk flash one of the many custom roms - let us know please how u get on with this!!!
Thanks for the help.
Click to expand...
Click to collapse
nps thanks for posting back, will help others who may be in similar situation!!!
dibb_nz said:
oh, "boot recovery failed"?? thanks for testing it out, was worth a go
just a note, tdv4 has cwm pre-installed
Fantastic, pleased it worked for u
ICS???? Stock???? this will overwrite yr recovery with the stock recovery??
The procedure requires u to put a rom on yr card to flash straight into after patching the BL - most folk flash one of the many custom roms - let us know please how u get on with this!!!
nps thanks for posting back, will help others who may be in similar situation!!!
Click to expand...
Click to collapse
Sure, I was just trying to figure out what did or didn't work after I used tdv4. It appears that it returned my system to "normal" so all the usual tools worked like acer recovery, blackthund3r, etc. I can only speculate that maybe the out-of-the-box 8gb had a different BCT and tdv4 has set it like everyone else's now.
Yes, I returned the system to ICS Stock after validating that blackthund3r worked (it of course overwrote the bootloader). From there I rerooted it with blackthund3r and removed the .sh script that deletes custom recoveries. I then reused blackthund3r to put a patched bootloader and recovery back on. I'll probably look at custom roms later, but for now I just wanted to get to stock w/ the custom bootloader & recovery and root and then use cwm to flash the memory swap mod.
For the record, I used Titanium backup. It failed to backup and restore the Minecraft maps, pictures/videos, and one or two game settings so I lost all of that. Is there a better backup program to use before tdv4? I usually just use the one built into CWM, but obviously I couldn't get to that one before tdv4 on this unit.
Hey guys!
I am trying to downgrade my current Stock 4.2.1 Rom to either 4.1.1 or 4.1.2 either stock or custom if possible even factory original.
How would I go about doing this as there is no clear cut instructions I could find....not sure if I can use NVFlash???
I previously had root performed using the VoodooOTA Method. Now I have unlocked the bootloader and also managed to install the TWRP Custom Recovery....although I do not think it has been installed correctly as it is unable to mount certain directories...../cache or /data and /system are some examples.....not sure if that is because of version or because of changes done to root enabler by new firmware upgrade.
If anyone has clear instructions or could point me in the right direction I would highly appreciate it!
Thanks
There might be a few issues with the new OTA update and recovery, if you already have a backup with nvflash from when you had ICS then yes there is a guide you can use to go back,
http://forum.xda-developers.com/showthread.php?t=1894867
if not then you should either try to flash one of the stock ROMs mentioned in the sticky in the Android Development section
http://forum.xda-developers.com/showthread.php?t=1697227
or if you think twrp is not working well you should wait just in case you do damage to your device. There is a chance some partitions have been altered in the new update and twrp needs to be updated, by whoever is responsible for our version, to be able to function properly.
If the reason you want to go back is the launcher then there is an option to switch to the 4.1 launcher in the options, not sure where exactly but if you look a bit further down in this section you'll find someone else posting something about it.
And a last suggestion is that when you have a question better post it in the appropriate section
Sent from my ASUS Transformer Pad TF300TG using XDA Premium HD app
hahahaha! funny u mention that coz i think I screwed up :silly: ...What I did was download the official bootloader from the Asus Website ASUS Transformer Pad TF300T Firmware: V10.4.2.20 Only for US SKU (Android 4.1) and use fastboot to flash the blob file.....now the only thing it does is spin at ASUS (boot loop)....The funny thing is it did affect how the fast boot option loads though it now shows up with the option of USB....and does not automatically go to fastboot.....my comp recognizes both in fastboot and adb the device so there is something......just performed a cache and dalvik wipe but to no vail and prior did a fix permission.....ALSO I do not receive any error with regards to mounting like before....
btw....which section would this fall under??? Development?
OKAY!!!!!! Im back in business.....WOOT!!! It worked just had to perform a factory reset to stop boot loop
rakesh219 said:
btw....which section would this fall under??? Development?
Click to expand...
Click to collapse
this belongs to the q&a section
rakesh219 said:
OKAY!!!!!! Im back in business.....WOOT!!! It worked just had to perform a factory reset to stop boot loop
Click to expand...
Click to collapse
Glad you fixed it but try not to do things you're not sure of in the future so as not to brick it :victory:
Wow, you managed to downgrade. Can you post a proper instruction?
Sent from my LT22i using xda premium
ilyuha1108 said:
Wow, you managed to downgrade. Can you post a proper instruction?
Sent from my LT22i using xda premium
Click to expand...
Click to collapse
wait what? he downgraded backwards with out unlock or with unlock?
details please im sorta lost on what happened here.
Yup sure can do it just give me a few hours trying to fix the dishwasher :good:
rakesh219 said:
Yup sure can do it just give me a few hours trying to fix the dishwasher :good:
Click to expand...
Click to collapse
any chance your running WW and not US and could now grab us the WW OTA update file
ilyuha1108 said:
Wow, you managed to downgrade. Can you post a proper instruction?
Sent from my LT22i using xda premium
Click to expand...
Click to collapse
Ashcunak said:
wait what? he downgraded backwards with out unlock or with unlock?
details please im sorta lost on what happened here.
Click to expand...
Click to collapse
I am pretty sure he said that he is unlocked and running twrp, you can flash whatever rom you want from recovery but it will not bring back the ICS bootloader and the ability to have NVFLASH or even the 4.1 BL, so in reality he flashed a new rom and not actually downgrade to the previous state of the tablet.
Ashcunak said:
wait what? he downgraded backwards with out unlock or with unlock?
details please im sorta lost on what happened here.
Click to expand...
Click to collapse
crossmission said:
I am pretty sure he said that he is unlocked and running twrp, you can flash whatever rom you want from recovery but it will not bring back the ICS bootloader and the ability to have NVFLASH or even the 4.1 BL, so in reality he flashed a new rom and not actually downgrade to the previous state of the tablet.
Click to expand...
Click to collapse
That is actually correct, I dont know if itwill work in general but I previously had my OS rooted and backed up using Voodoo OTA Rootkeeper. The only thing that I did new from here on is
1. Backup an Nandroid using ADB Terminal Access -
Code:
adb backup –apk –shared –all –f C:\Android_Asus_4-2-1.ab
Ofcourse in-order to perform this feat you would need Android SDK Tools Package and Google USB Drivers installed on the drive
2. Perform the unlock bootloader using the apk found on the Asus Website
3. Flash Stock Rom that can be downloaded from Asus or here
using fastboot
4. Flash TWRP for JB using fast boot with help of link
5. Go into recovery Wipe Dalvik and Cache and Factory Restore
6. And boot!
Okay I know this is no GUIDE as I am press with time....I will try to make a proper one. but in all honesty I would just wait for the REAL DEV's to post the solution to 4.2.1
rakesh219 said:
That is actually correct, I dont know if itwill work in general but I previously had my OS rooted and backed up using Voodoo OTA Rootkeeper. The only thing that I did new from here on is
1. Backup an Nandroid using ADB Terminal Access -
Code:
adb backup –apk –shared –all –f C:\Android_Asus_4-2-1.ab
Ofcourse in-order to perform this feat you would need Android SDK Tools Package and Google USB Drivers installed on the drive
2. Perform the unlock bootloader using the apk found on the Asus Website
3. Flash Stock Rom that can be downloaded from Asus or here
using fastboot
4. Flash TWRP for JB using fast boot with help of link
5. Go into recovery Wipe Dalvik and Cache and Factory Restore
6. And boot!
Okay I know this is no GUIDE as I am press with time....I will try to make a proper one. but in all honesty I would just wait for the REAL DEV's to post the solution to 4.2.1
Click to expand...
Click to collapse
Hi,
I need to downgrade my tab as my touch doesn't work and need to flash other firmware it. It was told to me to downgrade and it should work, but was said I need TWRP because with CWM I could brick my tab. Without touch it's impossible to use TWRP. I have ulocked bootloader and rooted. Your guide doesn't seem to need of use exactly TWRP as Wipe Dalvik and Cache is worked when I rooted tab.