Related
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
K so I have searched the net for days about this, with no success. what I want to know is it possible to transfer a backup of a stock rom, from one tablet to another of the same kind for recovery? if so can you post instructions or a tut, I've lost my original due to currupt data. and I want my Dolby digital sound back.
acer iconia minimalist rom
edit: I do have access to another tablet running stock.
thundercub88 said:
K so I have searched the net for days about this, with no success. what I want to know is it possible to transfer a backup of a stock rom, from one tablet to another of the same kind for recovery? if so can you post instructions or a tut, I've lost my original due to currupt data. and I want my Dolby digital sound back.
acer iconia minimalist rom
edit: I do have access to another tablet running stock.
Click to expand...
Click to collapse
Using cwm do a full nandroid backup, transfer the backup to microsd, put the microsd into the other Iconia and use cwm to do a nandroid restore.
At least, that's my guess.
well that's a start, I was about to start ripping my hair out over this simple sound issue lol but thanks.
thundercub88 said:
well that's a start, I was about to start ripping my hair out over this simple sound issue lol but thanks.
Click to expand...
Click to collapse
Hmmmmm. Can't you use use a full update.zip and flash a copy of the stock rom? Never tried using a nandroid backup on a system it was not created on - it might work, but it might not, I really am not sure.
But just flashing a full update.zip or installing Acer recovery tool to flash a stock rom sounds easier and more likely to work to me - am I missing something and is this not an option?
I tried flashing two or three times before, sent it into a bootloop, I even tried the Acer update decrypter but my laptop is 32 bit, and until today when I finally decided to post the question is when it occurred to me about possibly transferring it. btw, is there a set destination for the nandroid back up?
thundercub88 said:
I tried flashing two or three times before, sent it into a bootloop, I even tried the Acer update decrypter but my laptop is 32 bit, and until today when I finally decided to post the question is when it occurred to me about possibly transferring it. btw, is there a set destination for the nandroid back up?
Click to expand...
Click to collapse
Nandroid backups go to the external SD by default (I think) - have you tried using Acer Recovery Installer on the tab with the issue? Assuming you can still boot it and have root you may be able to go back to stock using it.
acer recovery
Tonto the market. Download the new version of Acer recovery installer.install third recovery. Go back into Acer recovery got last box .choose a rom for your location.let it download then install.point and click simple and will fix your issue.if you have failed attempts. You might want to try a different SD card.good luck
This did work for me
.
Erica Renee
Urban geeky blonde like me can do it surely a strong man like yourself willnfigure it out. Giggles
I have tried Acer recovery installer as well, I have 2.3 in fact I tried just a moment ago, and I get boot screen with android the triangle and the exlimation point.
confusion
OK Acer recovery installer is not the recovery just a means to install and work within it and run pre defined scripts.as in there backup and so on
If you are getting that.you need to
1.open Acer recovery installer
2.Install Recovery.the first black box acroos screen.it will askbifnyoubwant to back up stock recoverybdo so.(this is the recovery program only not the system) .
3.boot into recovery and backup your whole tablet.or use the far right black button to d/load and install a new rom from his list.fallow the instructions there clickishly simple
Good luck
So what Acer recovery installer does is replace the stock recovery. To allow you to install non stock decryptedand other. Zip files of course it will install stock recoveries as well.read the Acer recovery install thread under Dev section it's al in there
Again Google luck
OK so here is what I did and it worked like a charm, installed cwm did a custom restore (everything but data) mounted the SD card on other tablet restored and voila I have Dolby mobile back! thank you guys for all the help and info, now I can truly mess with roms and be safe knowing I have a non currupt back up
thundercub88 said:
OK so here is what I did and it worked like a charm, installed cwm did a custom restore (everything but data) mounted the SD card on other tablet restored and voila I have Dolby mobile back! thank you guys for all the help and info, now I can truly mess with roms and be safe knowing I have a non currupt back up
Click to expand...
Click to collapse
SWEET! Glad you got it figured out!
i called accer and they were no help pay for shipping i think not, so i know yall can fix anything, i get a unrecoverable bootloader error (0x00000004) and none of the power and volume combinations work i have a $400 paper weight now lol any help would be greatly appriciated
you can try this update, I solved a problem of boot failure http://www.megaupload.com/?d=4CWLBDDN
if it works, you can install the latest version of 3.2, http://forum.xda-developers.com/showthread.php?t=1113878
then looks back at 3:01 this guide to make the root and install a cooked ROM http://forum.xda-developers.com/showthread.php?t=1276227
i tried the zip file and the tablet seems to not except the update zip? any suggestions
brycepaymaster said:
i tried the zip file and the tablet seems to not except the update zip? any suggestions
Click to expand...
Click to collapse
How about some info, like which version of HC were you on, and what were you doing when you bricked it?
hc 3.1 sorry im new to this whole forum thing i was using a custom rom when all this happen not the hc 3.1 cant recall the name entirely i used gingerbreak or bread cant recall to root it then i installed cwm on the tablet and flashed a rom from my sd card once again not sure what it was called because ive been trying to fix this thing for 2 weeks and ive seen 100s of files i flashd a rom from the sd card and when i did the tablet said acouple of errors something about a boot img. i think but dont take my word on it cwm was still working fine when i did the flash then when i restarted the tablet it was bricked central lol also i remember when i did clockwork recovery i remember i flashed the clockwork recovery i used the htc desire for my tablet which is the same as my rooted htc inspire it worked fine but i think that played a big part in why its bricked thats all the info i got if any helps it would be awesome
brycepaymaster said:
hc 3.1 sorry im new to this whole forum thing i was using a custom rom when all this happen not the hc 3.1 cant recall the name entirely i used gingerbreak or bread cant recall to root it then i installed cwm on the tablet and flashed a rom from my sd card once again not sure what it was called because ive been trying to fix this thing for 2 weeks and ive seen 100s of files i flashd a rom from the sd card and when i did the tablet said acouple of errors something about a boot img. i think but dont take my word on it cwm was still working fine when i did the flash then when i restarted the tablet it was bricked central lol also i remember when i did clockwork recovery i remember i flashed the clockwork recovery i used the htc desire for my tablet which is the same as my rooted htc inspire it worked fine but i think that played a big part in why its bricked thats all the info i got if any helps it would be awesome
Click to expand...
Click to collapse
Umm let me see if I understand. You flashed a ROM, but you can't remember which one, you don't remember what you used to root it with, then you installed a version of CWM that is used for the HTC Desire? Is that it in a nutshell?
ok so ive been trying to remember exactly what rom it was i was running hc 3.1 and it was a stock rom i used the new gingerbreak to root it, the one where its like one button tap and its rooted, also im almost sure the custom rom i flashed to the tablet was ROM][JULE8]-=Virtuous Picasso v. 1.1.0=- [Honeycomb 3.1][Kernel: UNITY V5] and i used the htc desire clockwork recovery when i flashed my a500 hopefully this helps more than the other info
brycepaymaster said:
ok so ive been trying to remember exactly what rom it was i was running hc 3.1 and it was a stock rom i used the new gingerbreak to root it, the one where its like one button tap and its rooted, also im almost sure the custom rom i flashed to the tablet was ROM][JULE8]-=Virtuous Picasso v. 1.1.0=- [Honeycomb 3.1][Kernel: UNITY V5] and i used the htc desire clockwork recovery when i flashed my a500 hopefully this helps more than the other info
Click to expand...
Click to collapse
OK great here's your solution:
You need this!
lol is there a way to fix it at all i dont care if its back to stock and i lose everything i just dont want a paper weight
Sorry, I couldn't resist. Seriously though, I think this may be your only solution if you can follow directions very carefully:
http://forum.xda-developers.com/showthread.php?t=1276227
It's gotten quite a few ppl back to 3.1!
Good luck!
is a stupid question (I was wrong as well ), the update. zip is on the SD and not on a USB stick
brycepaymaster said:
lol is there a way to fix it at all i dont care if its back to stock and i lose everything i just dont want a paper weight
Click to expand...
Click to collapse
I just thought of three more options and messaged them to you. Check your messages!
hi guys,
i want to root and flash custom rom on my acer iconia with 3.2 OTA.
Correct me if i'm wrong...
i understand that i have to:
1. revert to 3.0.1 via http://forum.xda-developers.com/showthread.php?t=1276227
2. root my iconia via http://forum.xda-developers.com/showthread.php?t=1055354
then i don't know whats next? can i already install custom rom after root?
or do i need to install some kind of recovery to flash this custom roms..
Please help.. thanks!
exactly my friend revert first then root, then download acer recovery app install recovery start flashin
jhannbernas said:
hi guys,
i want to root and flash custom rom on my acer iconia with 3.2 OTA.
Correct me if i'm wrong...
i understand that i have to:
1. revert to 3.0.1 via http://forum.xda-developers.com/showthread.php?t=1276227
2. root my iconia via http://forum.xda-developers.com/showthread.php?t=1055354
then i don't know whats next? can i already install custom rom after root?
or do i need to install some kind of recovery to flash this custom roms..
Please help.. thanks!
Click to expand...
Click to collapse
Once you root install this:
Acer Recovery Installer
That will install CWM (recovery).
thanks for you both. i will try all of this on weekend.
but before doing this.. how can i backup my current rom? it is possible? thanks
You should install the Acer recovery installer first, then boot into CWM. When you are in there you will have the option to perform a full backup. This backup function will become your best friend.
thanks.. can't wait for the weekend to do this.
lastly, can anyone give me suggestion on what rom should i try in our opinion? thanks
jhannbernas said:
thanks.. can't wait for the weekend to do this.
lastly, can anyone give me suggestion on what rom should i try in our opinion? thanks
Click to expand...
Click to collapse
IMHO the stock based ROMs are the most stable, and trouble free. Head over to the DEV section and pick one out
There are plenty of ROMS to choose from. Some are better than others, and some work better for others. Taboonay seems to be the most popular. I liked Lightspeed because it basically removed EVERYTHING that I didn't need. Citvao seems to be gaining momentium. There is also another guy by the name of THOR who created a custom ROM that incorporates some files from the transformer stock ROM that is pretty good too.
I'd try them all and see what one you like best
Steps to using CWM?
If there's a thread to using CWM please direct me to it.
I have taken a short cut in using it by watching a YouTube video for installing a custom ROM and not learned all the in's and out's of using CWM.
I had installed the OTA HC 3.2 over a rooted 3.1 and lost my rooting as I expected. I decided I wanted to have root capabilites but with HC 3.2, so I found the (Oct 5 )version here and started over again.
I started with the Method 2 approach to install HC 3.2 update (that was already rooted here on this web site) to get to HC 3.0.1. However, initially when I got to installing the HC 3.2 zip it just booted afterwards and then went to a blank screen. So I tried it again only not doing all the clearing of user data, caches, etc., that was mentioned in the YouTube Video for installing a custom ROM. That worked. I now have a Acer Iconia 16 GB A500 rooted with HC 3.2 on it which what I wanted.
I would like to try some other ROMs and still go back if I could but I'm not sure about what exactly has to be cleared every time you load a new ROM. I don't want to have it hang again to a blank screen and maybe screw it up so I can't fix it.
Any directions?
Oh, BTW, when I installed the HC 3.0.1 from Method 2, it was so unstable that I couldn't make a WIFI connection. I had to go right to 3.1 to be able to use WIFI and get Acer Recovery Installer and continue on to installing HC 3.2 rooted.
Thanks
Redevil06 said:
If there's a thread to using CWM please direct me to it.
I have taken a short cut in using it by watching a YouTube video for installing a custom ROM and not learned all the in's and out's of using CWM.
I had installed the OTA HC 3.2 over a rooted 3.1 and lost my rooting as I expected. I decided I wanted to have root capabilites but with HC 3.2, so I found the (Oct 5 )version here and started over again.
I started with the Method 2 approach to install HC 3.2 update (that was already rooted here on this web site) to get to HC 3.0.1. However, initially when I got to installing the HC 3.2 zip it just booted afterwards and then went to a blank screen. So I tried it again only not doing all the clearing of user data, caches, etc., that was mentioned in the YouTube Video for installing a custom ROM. That worked. I now have a Acer Iconia 16 GB A500 rooted with HC 3.2 on it which what I wanted.
I would like to try some other ROMs and still go back if I could but I'm not sure about what exactly has to be cleared every time you load a new ROM. I don't want to have it hang again to a blank screen and maybe screw it up so I can't fix it.
Any directions?
Oh, BTW, when I installed the HC 3.0.1 from Method 2, it was so unstable that I couldn't make a WIFI connection. I had to go right to 3.1 to be able to use WIFI and get Acer Recovery Installer and continue on to installing HC 3.2 rooted.
Thanks
Click to expand...
Click to collapse
This has been posted in another thread by another member, and I saved it. I just can't remember who posted it again.
It's how I do EVERY flash and NEVER have problems.
"Before installing:
Boot into CWM
1/wipe cache
2/wipe data/factory reset
Advanced Menu:
3/wipe dalvik
4/wipe battery stat
Mount and Storage Menu
5/format (system, data, cache )... leave SD card alone.
install the zip ( new rom ) file !
Once done installing... repeat steps #1 - #4 only ( this is to assured that you are cleaned 110% in regard to the NEW rom that you have just installed )
DO NOT DO THE STEP #5 AFTER THE INSTALLATION !
Reboot system into initial Android greeting screen."
Some would say it's a bit on the "overkill" side, but better safe than sorry.
Thanks for the quick reply.
I think I also found where some of the information I wanted was in:
http://forum.xda-developers.com/showthread.php?t=1205204
I should have done more searching.
Thanks again
Oh, BTW, I have read your other posts on this site and like what you have to say. Also, the last step you have, Step 5, isn't in the YouTube video. Maybe that's where I fouled up and somehow recovered by doing again without some of the clearing. I think I just lucked out and got it working. Initially, without WIFI, I was stuck on how can you install Acer Recovery Installer without going to the "Market"? I had to go to 3.1 to get WIFI and then install it from the Market. I searched the internet with a computer for it, but couldn't find the apk to download so I could move it to a SD card and the Acer. Anyway it's working now and looking forward to more new ROMs and maybe Ice Cream if that's going to be the way to go in the future.
hardslog said:
You should install the Acer recovery installer first, then boot into CWM. When you are in there you will have the option to perform a full backup. This backup function will become your best friend.
Click to expand...
Click to collapse
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Right on!
drkalo said:
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Click to expand...
Click to collapse
+1
Some people don't read before posting
kjy2010 said:
+1
Some people don't read before posting
Click to expand...
Click to collapse
MY BAD!
I thought I read that he rooted it already and wanted to make a backup of that......
drkalo said:
Unfortunately he cannot use Acer Recovery Installer as long as he does not have root and that is why he cannot backup his current configuration i.e. OTA 3.2. Taking the risk of reverting is in first place if he insists on using a custom ROM.
Click to expand...
Click to collapse
got it. thanks!
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
You might have root but from the sounds of it the tab does not like the insecure kernel hence the yellow triangle on the logo screen. On a tab, I am not sure how to get around this.
Why not run stock and use TiBu to get rid of the bloatware until you can find a solution? Keep a Nandroid of bone stock then another for your custom settings...
Mardenator said:
So I recently rooted my LTE Tab 10.1 after some errors on my part. I finally got root, and the bootloader unlocked (thanks to six5alive's post here) Here's what I have:
CWM recovery
unlocked bootloader
Rom Manager installed
SU permissions
I've tried flashing two different ROMs, and both flash without a problem. But when I attempt to reboot, I get the Samsung logo and a yellow triangle below it, and then the tablet shuts down. At first I thought it was just the ROM, but after flashing two, I'm getting suspicious. I have a Nandroid backup of the stock rooted ROM, and that restores & boots properly every time.
What am I doing wrong?
Click to expand...
Click to collapse
What roms did u flash...?
Sent from my GT-P7500 using XDA App
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
ZangetsuNX-01 said:
Strange, when I flashed the ISI-Galaxy rom on my P7100 i got then same thing as you, when i turned the device off it automatically went back on with the same result. I had the idea that i was going to have to bring it back to the shop for repairs but... This happened while i was at work. So i placed the Tab in my backpack but when i got home a half an hour later the device was functioning again. So maybe yours needs some time to get over this 'boot up'.
Click to expand...
Click to collapse
Tried this, got the same result I've been getting..
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Mardenator said:
I flashed these, wiped after flashing each one obviously.
http://forum.xda-developers.com/showthread.php?t=1372432
and
http://forum.xda-developers.com/showthread.php?t=1155023
Both caused the triangle issue, so I just restored the rooted stock ROM I'm running.
Click to expand...
Click to collapse
Next time please use the edit button.
I think I have an explanation as to why its crashing. The ISI-Galaxy Rom and P7500XWKK4 Galaxy Tab 10.1 / HC 3.2 ROM are for the P7100 model. Yours is the SCH-I905 model so the roms you tried to flash are incompatible.
Just realized that ZangetsuNX-01 is right, I've been flashing WiFi-only ROMs, not ROMs for the Tab 10.1 LTE. Downloading http://forum.xda-developers.com/showthread.php?p=17858660#post17858660 now, will flash and post results here asap.
UPDATE: got a leaked TW ROM to install via Odin and boot, posting this from the tablet. Added a screenshot for kicks.
BTW, for anyone with an LTE Tab, flash this via ODIN NAO!!!!
http://rootzwiki.com/topic/10463-ro...x-leak-build-for-vzw-galaxy-tab-101-lte-only/
It's unrooted, with stock recovery, but you can follow the directions on the page to get root, it's simple. Just Odin a recovery .tar file, go to recovery, flash SU zip, and voila. Running it at 1.4GHz max, 1GHz min, and it's awesome. TouchWiz is also a nice step up from stock HC.
@Mardenator
your screenshot a looke liek from my adwluncher from my tab...
Lol I'm using ADW Ex.
ok i dont untersant waht you with them post, sorry.
Conan179 said:
ok i dont untersant waht you with them post, sorry.
Click to expand...
Click to collapse
I'm not sure what the question here is, but I was suggesting that if you have an LTE Galaxy Tab 10.1, you should flash the ROM that I provided a link to. It's a good ROM, and I've been running it for 2 days now.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General