Related
I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.
I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.
Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.
I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.
I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2
Hey guys:
I recently wiped my tab clean because it kept bootlooping, but I accidentally wiped my ROM as well as my storage. So right now, my tab is stuck at the unlocked screen, and I'm not sure what could have caused the bootloop problem in the first place.
Rooted, unlocked, running CleanROM 2.7.2 with Data2SD and Clemsyn kernel. I kept fsync enabled precisely so that my system would be more stable, but it appears not to be the case. Right now, my priority is flashing any OS/ROM onto my tab so I can get it to start booting. Any help? I'm really hoping this isn't a brick scenario.
Hohumhurrdurr said:
Hey guys:
I recently wiped my tab clean because it kept bootlooping, but I accidentally wiped my ROM as well as my storage. So right now, my tab is stuck at the unlocked screen, and I'm not sure what could have caused the bootloop problem in the first place.
Rooted, unlocked, running CleanROM 2.7.2 with Data2SD and Clemsyn kernel. I kept fsync enabled precisely so that my system would be more stable, but it appears not to be the case. Right now, my priority is flashing any OS/ROM onto my tab so I can get it to start booting. Any help? I'm really hoping this isn't a brick scenario.
Click to expand...
Click to collapse
Can you still access recovery? From recovery I've able to reload the stock update files which extract and load a blob that completely rewrites my system.
If not, can you access fastboot? Load it into fastboot and then re-install a recovery, and then from there use that to either install the update or reload your rom.
d01100100 said:
Can you still access recovery? From recovery I've able to reload the stock update files which extract and load a blob that completely rewrites my system.
If not, can you access fastboot? Load it into fastboot and then re-install a recovery, and then from there use that to either install the update or reload your rom.
Click to expand...
Click to collapse
I can still access recovery, but am not sure how to or which stock files I'm supposed to extract. I've been looking into fastboot right now, but don't have the SDK installed on my computer and frankly, I'm just not sure what to do with it.
Ideally, accessing the stock files and loading a blob would be the best solution, but I'm unsure how to proceed. Thanks for the advice, as I'm frantically trying to find a solution as the tab won't shut off and I'm afraid it's going to overheat.
Hohumhurrdurr said:
I can still access recovery, but am not sure how to or which stock files I'm supposed to extract. I've been looking into fastboot right now, but don't have the SDK installed on my computer and frankly, I'm just not sure what to do with it.
Ideally, accessing the stock files and loading a blob would be the best solution, but I'm unsure how to proceed. Thanks for the advice, as I'm frantically trying to find a solution as the tab won't shut off and I'm afraid it's going to overheat.
Click to expand...
Click to collapse
I don't understand your issue, if you still can access your twrp, then just reflash your cleanrom 2.7? If you want to bypass data2sd for now, just flash clemsyn_data2sd kernel, you should able to boot up.
buhohitr said:
I don't understand your issue, if you still can access your twrp, then just reflash your cleanrom 2.7? If you want to bypass data2sd for now, just flash clemsyn_data2sd kernel, you should able to boot up.
Click to expand...
Click to collapse
Like a fool, I wiped both internal and external storage. So I don't have the zips or backups I had on my sds. I've tried removing the sd and putting backups and zips I have on my computer, but TWRP doesn't recognize the device since I have no OS.
Hohumhurrdurr said:
Like a fool, I wiped both internal and external storage. So I don't have the zips or backups I had on my sds. I've tried removing the sd and putting backups and zips I have on my computer, but TWRP doesn't recognize the device since I have no OS.
Click to expand...
Click to collapse
make sure you format your sdcard with fat32 using your pc, then copy the rom zip file on to it, make sure your device if OFF,put the sdcard back into your device, boot up into twrp, select mount and and put a check on everything, then try to install, it should see your zip file.
buhohitr said:
make sure you format your sdcard with fat32 using your pc, then copy the rom zip file on to it, make sure your device if OFF,put the sdcard back into your device, boot up into twrp, select mount and and put a check on everything, then try to install, it should see your zip file.
Click to expand...
Click to collapse
Also, my tablet kept bootlooping when trying to install the same setup (2.7 w/ data2SD) when using an SD card formated with minitool...using GParted worked like a charm the first time.
buhohitr said:
make sure you format your sdcard with fat32 using your pc, then copy the rom zip file on to it, make sure your device if OFF,put the sdcard back into your device, boot up into twrp, select mount and and put a check on everything, then try to install, it should see your zip file.
Click to expand...
Click to collapse
Thank you, good sir. Worked like a charm. Only problem is a boot loop that persists when I try to flash CleanROM 3.0.1, but I'll probably figure out what's wrong eventually.
Hohumhurrdurr said:
Thank you, good sir. Worked like a charm. Only problem is a boot loop that persists when I try to flash CleanROM 3.0.1, but I'll probably figure out what's wrong eventually.
Click to expand...
Click to collapse
Hey, during the install, did you selected nexus boot animation? if you are, try to clear cache and dalvik cache then reinstall, but this time select Asus stock boot animation see if it's ok.
buhohitr said:
Hey, during the install, did you selected nexus boot animation? if you are, try to clear cache and dalvik cache then reinstall, but this time select Asus stock boot animation see if it's ok.
Click to expand...
Click to collapse
Reverted back to Stock and flashed CleanROM 3.0.1 with Asus Stock boot animation this time. Yes, I was using the Nexus boot animation before, but Asus Stock isn't making a difference. Same boot loop. Reverting back to Stock until I can figure out what's wrong. I've been checking to make sure all my stuff is updated and nothing seems to be out of order...
Hohumhurrdurr said:
Reverted back to Stock and flashed CleanROM 3.0.1 with Asus Stock boot animation this time. Yes, I was using the Nexus boot animation before, but Asus Stock isn't making a difference. Same boot loop. Reverting back to Stock until I can figure out what's wrong. I've been checking to make sure all my stuff is updated and nothing seems to be out of order...
Click to expand...
Click to collapse
I think if you flash cleanrom 2.7.2, then flash 3.01, it should work.
buhohitr said:
I think if you flash cleanrom 2.7.2, then flash 3.01, it should work.
Click to expand...
Click to collapse
It does work, much appreciated.
Is there any way to do this without having to do a factory wipe?
It may be possible, however it is HIGHLY recommended to do a factory reset in recovery. If you choose not to, I do not even want to think about what will crash going from Honeycomb to JellyBean 4.2/4.3
Here is what I would do. First, install GooManager from the play store. Update the recovery to TWRP 2.3.2.3. I have seen a LOT of users with issues using CWM on android 4.2 and later. Some swear it works great, but I would not trust it myself. After installing the GooManager, tap the menu button in the top right and choose the Install OpenRecovery Script.
Next, use Titanium Backup to back up your user apps. Do not back up system apps. Restoring these can cause some issues on newer versions of Android, especially since there are no Jelly Bean ROMs based on stock Asus Firmware.
Download your ROM of choice, and any GAPPS or kernels that you want to install.
Boot to recovery.
Backup your current setup as a fail safe.
Next, wipe the following partitions:
Cache
Davlik Cache
System
Data (Factory Reset). This will wipe the /data/ partition without wiping /data/media/ (aka /sdcard/) so your files on the internal storage will still remain. I would HIGHLY recommend doing a FORMAT DATA and fully wiping the /sdcard/ to help your device run faster. The files on /sdcard/ are not backed up by recovery's backup function so if you choose to do this be sure you backed up your entire /sdcard/ to microSD/SD/USB/PC/Cloud storage before formatting it.
Now go to the Install menu and install the ROM. Also install GAPPS and kernel if required.
I always wipe cache & davlik again after flashing then reboot. Set up the new ROM and then install TiBu and restore your apps. Once again, be sure not to restore any system apps or data as it can cause random reboots, SOD and app crashes.
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
thorin33 said:
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
Click to expand...
Click to collapse
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Plus 1. I hesitated to upgrade because I was "comfortable" with the ROM I was on (Megatron). I decided to update to KatKiss 4.3 mostly cause I was bored and wanted to flash something. Glad I did as it's a big different.:good:
Thanks again. I am using ADW and saved my configuration. I may just have to bite the bullet and just do it.
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
thorin33 said:
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
Click to expand...
Click to collapse
MUCH greener - Honeycomb is an ancient slow laggy build of Android, Jellybean is a fast smooth build
The user experience using Jellybean is immensely improved
Its the difference between Vista and 8.1, if not more, maybe XP > 8.1
Just make a Nandroid backup with TWRP recovery, then wipe everything, flash KatKiss #226 and Gapps and play around with it
Guarantee you will not want to return to HC
On the off chance you do want to return, just boot back into TWRP and restore your backup, you'll be back to exactly the state you were in when you made the backup, nothing lost
frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
thorin33 said:
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
Click to expand...
Click to collapse
I don't know anyone using HUBS myself. I am not sure how ADB works with JB. I moved on to APEX myself.
I think the BEST option is to make a backup of PRIME. Install, restore your apps (I would restore ADW last after all widgets and such are restored) and test it out.
If it does not work like you wanted, restore the PRIME backup in recovery and you will be right where you left off.
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
*Detection* said:
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
Click to expand...
Click to collapse
I was thinking the same thing.
See here:
frederuco said:
Since this tool has not been updated for newer recoveries, I repacked the zip with the two latest versions of TWRP:
EasyFlasher with TWRP 2.3.2.3
EasyFlasher with TWRP 2.5.0.0
EasyFlasher with TWRP 2.6.0.0
EasyFlasher with TWRP 2.6.1.0
EasyFlasher with TWRP 2.6.1.0-b This version has the microSD mounted as /MicroSD/ instead of /sdc/
EasyFlasher with TWRP 2.6.1.0-c This version has the the storage mounted as sdcard0 for internal storage and microSD is mounted as sdcard1
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
NOTE - It STILL has the TWRP version listed as 2.2.1.1 in the dropdown, but it WILL INSTALL 2.3.2.3, 2.5.0.0 or 2.6.X.X I cannot update the dropdown.
I have tested all of these on my TF101 and all of them worked successfully.
Click to expand...
Click to collapse
You can follow my rooting guide here for detailed instructions on how to use EasyFlasher: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
frederuco said:
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
Click to expand...
Click to collapse
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Theziggy said:
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Click to expand...
Click to collapse
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
frederuco said:
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
Click to expand...
Click to collapse
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Theziggy said:
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Click to expand...
Click to collapse
EasyFlasher is mainly to install a custom recovery when you are still stock so you can root and/or ROM and also to flash the stock firmware if you bricked your tablet and it won't boot to recovery or to a ROM.
It can be used to update to a newer version of TWRP or other recovery, but it is much easier to just flash the zip file in recovery as you do not need to have a PC to make it happen.
That's what I was kinda thinking Frederuco, thanks for clarifying it for me :good: :good: :good:
Finally found some time to do a little bit more on my upgrade path (Having a 5 month old sucks up most of my free time). I was able to just install the zip from sidneyk. Did my nandroid and hopefully will find time to flash Katkiss.
Thanks for all the help so far everyone.
I noticed that when I went to do my backup I got the following message:
Updating partition details
E: Unable to locate ui.xml in zip file
E: An internal error has occured.
It proceeded to backup and said it was successful. Is this normal?
TIA
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.
Having not learnt my lesson from previous Android adventures, I decided update CyanogenMod installation from 10.1.3 to 10.2.0 on my Nexus S. I did the sideload from ClockworkMod recovery, rebooted, and got stuck on the loading screen. Having read suggestions to update GApps as well, I went back into ClockworkMod recovery, sideloaded the GApps, and, again, no joy. I understand that the next step to recover the phone is to factory reset it, but I forgot to backup everything beforehand.
I have some important information that I really don't want to lose in a factory reset. Complicating matters is that I've turned on encryption, so I can't simply use the ClockworkMod backup system and/or access the SD card. I'm running Linux with adb, so I can shell in if someone tells me how to dump the saved data off the phone. Even if I just get raw data and I have to enter it back in myself, that's better than losing it.
I know that downgrading back to 10.1 without a wipe is generally frowned upon. Is it worth gambling with the 10.3 nightlies to see if I can get a stable Android (there's an oxymoron!) boot going long enough for me to get everything off my phone before wiping it and reverting back to 10.2? If the issue is a corrupted apk, can I manually remove them to figure out what the problem is?
Borden Rhodes said:
Having not learnt my lesson from previous Android adventures, I decided update CyanogenMod installation from 10.1.3 to 10.2.0 on my Nexus S. I did the sideload from ClockworkMod recovery, rebooted, and got stuck on the loading screen. Having read suggestions to update GApps as well, I went back into ClockworkMod recovery, sideloaded the GApps, and, again, no joy. I understand that the next step to recover the phone is to factory reset it, but I forgot to backup everything beforehand.
I have some important information that I really don't want to lose in a factory reset. Complicating matters is that I've turned on encryption, so I can't simply use the ClockworkMod backup system and/or access the SD card. I'm running Linux with adb, so I can shell in if someone tells me how to dump the saved data off the phone. Even if I just get raw data and I have to enter it back in myself, that's better than losing it.
I know that downgrading back to 10.1 without a wipe is generally frowned upon. Is it worth gambling with the 10.3 nightlies to see if I can get a stable Android (there's an oxymoron!) boot going long enough for me to get everything off my phone before wiping it and reverting back to 10.2? If the issue is a corrupted apk, can I manually remove them to figure out what the problem is?
Click to expand...
Click to collapse
1. why are you side loading instead of flashing normal?
2. have you tried wiping everything minus sd and data and returning to 10.1.3?
3. when jumping versions, you need a full wipe..
Setting.Out said:
1. why are you side loading instead of flashing normal?
Click to expand...
Click to collapse
I sideload the update because you can't access an encrypted SD Card (which mine is) from recovery mode. I'm not aware of any other way to do upgrades.
Setting.Out said:
2. have you tried wiping everything minus sd and data and returning to 10.1.3?
Click to expand...
Click to collapse
Is there a way to do this? My understanding is that a wipe will clear the data and the SD Card unless you're lucky. If I could revert back to 10.1.3 without touching the data, that would be great, but I'd want to be linked to a tutorial so I'm sure not to mess up.
Setting.Out said:
3. when jumping versions, you need a full wipe..
Click to expand...
Click to collapse
Yeah, I'm an idiot. I've gotten away with sideload updates in the past, but Android caught me this time and left me in limbo.
Borden Rhodes said:
I sideload the update because you can't access an encrypted SD Card (which mine is) from recovery mode. I'm not aware of any other way to do upgrades.
Is there a way to do this? My understanding is that a wipe will clear the data and the SD Card unless you're lucky. If I could revert back to 10.1.3 without touching the data, that would be great, but I'd want to be linked to a tutorial so I'm sure not to mess up.
Yeah, I'm an idiot. I've gotten away with sideload updates in the past, but Android caught me this time and left me in limbo.
Click to expand...
Click to collapse
If you boot into CWM and do a format/wipe on everything MINUS the SD and DATA, you won't lose anything, but it may not fix your issue.. If you get your phone back up and running take off the encryption and back up your files, FULL WIPE and try again..
Thank you for the quick reply.
Setting.Out said:
If you boot into CWM and do a format/wipe on everything MINUS the SD and DATA, you won't lose anything, but it may not fix your issue.. If you get your phone back up and running take off the encryption and back up your files, FULL WIPE and try again..
Click to expand...
Click to collapse
When I go into ClockwordMod, version 6.0.4.3, the 'wipe data/factory reset' is the only option that I see, but it then warns me that all data will be wiped, which, I'm guessing, includes the /data partition. Is this correct or should I look some place else?
Borden Rhodes said:
Thank you for the quick reply.
When I go into ClockwordMod, version 6.0.4.3, the 'wipe data/factory reset' is the only option that I see, but it then warns me that all data will be wiped, which, I'm guessing, includes the /data partition. Is this correct or should I look some place else?
Click to expand...
Click to collapse
Mounts and storage / format
Sent from my Nexus S using XDA Premium 4 mobile app
---------- Post added at 11:34 PM ---------- Previous post was at 11:31 PM ----------
Also go to advanced / wipe dalvik... Are you sure you've flashed Roms before?
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Mounts and storage / format
Click to expand...
Click to collapse
OK, found it there, and formatted /storage, /cache, /boot, and /system. Reflashed CM 10.2 and GApps 4.3 with no success. However, I did manage to dd dump the contents of mmcblk0p2 and mmcblk0p3 to my Linux hard drive, so if I ever figure out how to mount those images in Linux, I should be able to recover everything.
Setting.Out said:
Also go to advanced / wipe dalvik
Click to expand...
Click to collapse
Yep, I did that, too.
Setting.Out said:
... Are you sure you've flashed Roms before?
Click to expand...
Click to collapse
I don't understand this question. How else could I have gotten CM onto my phone in the first place if I never flashed a ROM?
With few other options, I did a factory reset which, predictably, wiped everything but the SD card and put me into a fresh phone. It's also not mounting the SD. So, since all of my data on my phone is gone, I'll just have to hang onto the dumps that I have and hope and pray that someone can tell me how to mount them to get all of my files back.