After the OTA 3.2.1 update, CWM Recovery would just not install. After flashing the CWM recovery image on stock 3.2.1 and rebooting into recovery, I get the android guy with the exclamation mark. I saw another person in the CWM thread having the same issue.
I did flash CWM before on HC 3.2 successfully, but for some reason it is not working after the last OTA update.
Any thoughts ?
Any luck on this? I'm trying to root my Xoom 3.2.1 and have no idea what to do and looks like the one click tool has been removed...any direction is better than no direction ;-)
Thanks!!
Faslane
I had this same issue yesterday.
Use adb and fastboot to manually install clockwork again...and then if you need to root you can use one click root.
I would give you the code for fastboot command but I'm not home.
Sent from my ADR6350 using xda premium
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
okantomi said:
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
Click to expand...
Click to collapse
Thank you okantomi that's what I meant.
Sent from my ADR6350 using xda premium
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
That is exactly right.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
these instructions seem to work
http://forum.xda-developers.com/showpost.php?p=17832798&postcount=78
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Yazan76 said:
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Click to expand...
Click to collapse
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
.
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
okantomi said:
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
Click to expand...
Click to collapse
Even simpler... fastboot flash just boot, system, and recovery stock images. Leave userdata alone. Allow the update. Don't worry about letting it fully boot.. let it.. no harm.. but no root.
Then flash CWM (using fastboot).. boot to recovery.. CWM univ root. Good to go. Or CWM a different kernel
CARLITOZ18 said:
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
Click to expand...
Click to collapse
You need to have an exernal sdcard for the recovery images to work.
Chipster0 said:
... Fastboot flash just boot, system, and recovery stock images.
Click to expand...
Click to collapse
Do you (or anyone else) have any (US VZ 3G MZ600) stock images later than HMJ37? Moto stopped carrying at HRI66 for some reason
Related
UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up
RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra
jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra
raffica, what version of CWM worked for you?
MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.
lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1
i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.
jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!
RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?
i wanted to know if i can downgrade from 3.1 stock to 3.0.1 using acer recovery tool. I want to downgrade because some of the apps that i would like to use keep force crashing on 3.1. i have tried reinstalling the apps and nothing works.
brewmaster said:
i wanted to know if i can downgrade from 3.1 stock to 3.0.1 using acer recovery tool. I want to downgrade because some of the apps that i would like to use keep force crashing on 3.1. i have tried reinstalling the apps and nothing works.
Click to expand...
Click to collapse
see this: http://forum.xda-developers.com/showthread.php?t=1113878
i dont see why you wouldn't be able to.
brewmaster said:
i wanted to know if i can downgrade from 3.1 stock to 3.0.1 using acer recovery tool. I want to downgrade because some of the apps that i would like to use keep force crashing on 3.1. i have tried reinstalling the apps and nothing works.
Click to expand...
Click to collapse
If you made a nandroid backup using clockworkmod (you should have), just do a full restore. ba-da-bing.
The acer recovery tool you mention is just for installing clockworkmod, it won't install a rom itself. clockwork mod does that.
i didn't create a backup so i guess i'm out of luck.
brewmaster said:
i didn't create a backup so i guess i'm out of luck.
Click to expand...
Click to collapse
Maybe you are not... Dexter provided a stock rom on his first post here:
http://forum.xda-developers.com/showthread.php?t=1121790
Check this post. flashing those 4 files (don't forget itsmagic), will put you at version 1.104.02_GEN1_COM (U.S. Stock).
Skip flashing the recovery if you don't want to lose ClockworkMod.
http://forum.xda-developers.com/showpost.php?p=14967064&postcount=206
If you want a specific version, ask someone to uplaod a ClockworkMod backup of boot, system and flexrom and use ClockworkMod to restore it.
thanks euclid. I might try this later but i can't figure out itsmagic. I installed the clockworkmod recovery with acer recovery installer. Can i just boot into recovery after that and have itsmagic work?
edit: i got its magic running then did the steps in the post minus the recovery. when it was done the device rebooted and got stuck on the acer logo. after that i booted into clockwork and installed the 3.1 update.zip and now my tablet is working fine again.
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Mine was gone when i unrooting the device
Sent from my Nexus 4
EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?
Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4
That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
jimmyco2008 said:
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
Click to expand...
Click to collapse
are you mounting system first? never used CWM on this device, but in TWRP, they install just fine. I believe that most devs use TWRP (although, it should not make a difference).
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
jimmyco2008 said:
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
Click to expand...
Click to collapse
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
jcxmej said:
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
Click to expand...
Click to collapse
are you sure you uninstalled SS via the app (and not via the android system)?
jco23 said:
are you sure you uninstalled SS via the app (and not via the android system)?
Click to expand...
Click to collapse
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
jcxmej said:
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
Click to expand...
Click to collapse
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
jco23 said:
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
Click to expand...
Click to collapse
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
jcxmej said:
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
Click to expand...
Click to collapse
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
jco23 said:
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
Click to expand...
Click to collapse
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
jcxmej said:
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
Click to expand...
Click to collapse
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
jco23 said:
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
Click to expand...
Click to collapse
Just installed SS and unnistalled it thru the app. I ll wait for any reboots before I reflash the ROM. Hope this works. (finger crossed)