Related
I've tried to install every possibile recovey for xoom , I've always get follow error:
E:Can't mount /cahce/
E:Can't mount /system
E:Can't open /sdcard
....
The only way to have a working recovey is to install it from rom manager, it installs v4.0.0.4 , and works... any help to understand why i get this error and how to fix it?
this way i've to root device to install a recovey .
The CWM Recovery installed by Rom Manager isn't really for the Xoom and doesn't recognize the external micro sdcard. You cannot flash successfully from internal "sdcard" using that recovery version. There's a Tearm Rogue recovery that uses v4.0.0.4, but it is modified and I think you have to flash it via external sdcard which means you need the R4c CWM version 3.2.0.0 developed by solarnz specifically for the Xoom.
okantomi said:
The CWM Recovery installed by Rom Manager isn't really for the Xoom and doesn't recognize the external micro sdcard. You cannot flash successfully from internal "sdcard" using that recovery version. There's a Tearm Rogue recovery that uses v4.0.0.4, but it is modified and I think you have to flash it via external sdcard which means you need the R4c CWM version 3.2.0.0 developed by solarnz specifically for the Xoom.
Click to expand...
Click to collapse
I've tried to install 3.2.0.0 developed by solarnz, i get that error, I've looked around my xoom but I can't found out any hole that could host a micro sd? where would it be? is it possible I don't have it ? my xoom is europe, wi-fi,3g,32 gb
I've flashed kernels or restored previous backup, on internal "sdcard", with this recovery(4.0.0.4) and worked well,by the way.
Do you have the original Xoom? If so, then look on the top edge and you will see a rubbery plastic cover that can be lifted right off. don't lose it. Under that cover is the micro sdcard slot. It's to the left, toward the screen. You need the sdcard mounted in the slot in order to flash the recovery file successfully. Be careful not to drop the card into the larger space... it just will click into its little slot but take it easy the first time.
I've found it, is in simcard slot just above it... impossibile to see... now all work well.
thanks a lot.
You're very welcome. I'm glad you got it working.
okantomi said:
You're very welcome. I'm glad you got it working.
Click to expand...
Click to collapse
So mine is doing the same thing with nightly build 36 of EOS. I can't install gapps or anything else...
Hi: I'm a noob and need help. I searched and found this thread.
Just bought a second hand Xoom WiFi with a 4.0.3 that was installed by the seller's friend.
I got home and connected to my WiFi and noticed an update to your system notice and I realised that it was an update to 4.0.4, an OTA update. Very happy.
However when the Xoom went into the discovery mode, I got the error messages that this thread starter mentioned. So, I'm still in 4.0.3 and I'm wondering what might have the previous 'updater' did to update the Xoom from 3.2 to 4.0.3 and how that is causing the error message.
If any one can help, I would greatly appreciate it. Thanks.
So ive been at this for 2 days. I finally got the micro sd card with both files to install rom but in clockworkmod recovery i cant mount sd card nor format or anything. I can mount and unmount in the normal settings of the device and see it in root explorer but thats it. Its formatted to fat32. also on rom manager where it says to install from sdcard it only takes u to the internal sdcard which makes no sense because i was told u cant install a rom from the internal sdcard.
PS. This is my first Android Device!!!!
yeah
I am in the exact same situation. I am rooted on 4.0.3 and I wanted to install 4.0.4 or one of the custom ROM's. This is not my first android device but I am at a loss. I can not enter fastboot, can't load anything from the SD card in CWM recovery (get the message E:Can't mount /sdcard/), can not connect via ADB on my PC.
I feel that I have enough skill to do all of this because I have done it in the past. My ADB works fine with my Galaxy Nexus (just updated that and installed new kernel) so I don't know what is causing the problem. I have tried different SD cards(3) as well and nothing.
The biggest problem is I can not get into fastboot and SBF if I wanted to. I have been having issues with drivers even though I have installed motohelper like 6 million times.
I have tried factory resets and wipes and everything. I tried to do the factory update that is being pushed to me and I get an error. Any help would be greatly appreciated.
Sorry if this is stealing your thread but I think we are having the same problems.
check out my thread at xoomforums:
I PM'd it to u cus it dont let me put it here
Read all 3 pages. I think it will help u. posted same question there and a guy suggested to install the rogue cwm 1.5 recory via adb fastboot or whatever. he says that will read your sdcards. if i were u id try and fastboot on a different pc cus it looks like thats what we both have to do unfortunately. it looks like a pain!!! u have a xoom?
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
platt said:
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
Click to expand...
Click to collapse
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
+1 i agree with the above, fixed this last night. I download a couple recovery images, which were blank for some reason, so i downloaded the zips and extracted the recovery image folder. Then opened the command window from the folder with the recovery image and flashed it with fastboot. Now it works perfect.
Sent from my MB855 using xda premium
Fastboot
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
TheAv8tor said:
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
Click to expand...
Click to collapse
Atleast you got it out, mines been acting up since i flashed cm9. I think i might have to do that
Sent from my MB855 using xda premium
okantomi said:
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
Click to expand...
Click to collapse
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
error mounting /internal_sdcard!
error mounting /internal_sdcard! pls help me it got stuck in boot loop tried to wipe cache and user data bt cwm says error mounting /internal_sdcard!
Ipse_Tase said:
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
Click to expand...
Click to collapse
Delete any zip files or IMG files from sdcard and reboot it this helped me ............ Hit thanks if helped
Sent from my HTC Desire C using XDA Premium 4 mobile app
This is my first attempt at unlocking and rooting. So far I did manage to get unlocked. Now I am stuck at: Can't mount/sdcard . . . . .
I have been following the thread: [HOW] Rookie Rooting, Flashing And UnRooting Under One Roof
It seems to be layed out quite well and well, I'd never have gotten this far if it weren't for following those directions. I'm not discouraged because I know this is just a stumbling block. I can't wait to kill the bloatware and see if I can O/C this beast just a little.
Good luck to the folks who posted above me. I will post my results here.
Mike P.
I think the solution is much more simple...
The recovery uses normally e: an external sd card , you just trying by d: internal sd card , so take another sd card and dun let it be internal sd card...
And the recovery back on working with you
Hi!
I'm on SGS2 with Resurrection Remix v2.0 w/ Siyah v 3.2.6+ kernel.
My version of CWM is 4.0.1.5.
For some reason, I can't longer flash anything from CWM.
Whenever I reboot into CWM and choose the "choose zip from sdcard", I only get this error message: "E: Can't mount /sdcard". I don't have any external SD card on my phone, I have always used this method.
I've already tried to wipe cache without luck. If I choose "mount /sdcard", I only get "Error mounting /sdcard!" (This however, may be because it's referring to any external sdcard?)
I appreciate any answers!
RealSpZ said:
Hi!
I'm on SGS2 with Resurrection Remix v2.0 w/ Siyah v 3.2.6+ kernel.
My version of CWM is 4.0.1.5.
For some reason, I can't longer flash anything from CWM.
Whenever I reboot into CWM and choose the "choose zip from sdcard", I only get this error message: "E: Can't mount /sdcard". I don't have any external SD card on my phone, I have always used this method.
I've already tried to wipe cache without luck. If I choose "mount /sdcard", I only get "Error mounting /sdcard!" (This however, may be because it's referring to any external sdcard?)
I appreciate any answers!
Click to expand...
Click to collapse
So, when you put the .zip on your 'sdcard', are you putting it on the internal memory, or the external SD card?
And yep you're right - it's looking for an extsdcard to 'mount'.
juzz86 said:
So, when you put the .zip on your 'sdcard', are you putting it on the internal memory, or the external SD card?
And yep you're right - it's looking for an extsdcard to 'mount'.
Click to expand...
Click to collapse
I'm putting the .zip file in my /mnt/sdcard directory. Btw, when I can boot into the stock recovery, I have an option called "install zip from internal sd card". When I choose this option, I can access all my files and install the update that I want, but in CWM I can't!
RealSpZ said:
I'm putting the .zip file in my /mnt/sdcard directory. Btw, when I can boot into the stock recovery, I have an option called "install zip from internal sd card". When I choose this option, I can access all my files and install the update that I want, but in CWM I can't!
Click to expand...
Click to collapse
Have you tried sticking the .zip on an external SD, and seeing if it shows up that way just to confirm? I remember having a similar issue on the Infuse a while back now, and I had to start flashing off the internal memory.
I think a re-install of CWM fixed things up, but that was a high-Development time, and we were getting new versions every day
Try the external thing, I reckon that's the problem. Might require an update to CWM in order to restore functionality. Alternatively, you may like to look into a replacement such as 4EXT or TWRP.
I found this kernel by Chainfire, which adds root and SU, and also CWM. You can flash it through ODIN as normal, very detailed instructions in there.
I also found this article, which may shed some light on the issue for you?
I cannot believe how hard it is to find a Recovery in the GS2 section. What a nightmare!
juzz86 said:
Have you tried sticking the .zip on an external SD, and seeing if it shows up that way just to confirm? I remember having a similar issue on the Infuse a while back now, and I had to start flashing off the internal memory.
I think a re-install of CWM fixed things up, but that was a high-Development time, and we were getting new versions every day
Try the external thing, I reckon that's the problem. Might require an update to CWM in order to restore functionality. Alternatively, you may like to look into a replacement such as 4EXT or TWRP.
I found this kernel by Chainfire, which adds root and SU, and also CWM. You can flash it through ODIN as normal, very detailed instructions in there.
I also found this article, which may shed some light on the issue for you?
I cannot believe how hard it is to find a Recovery in the GS2 section. What a nightmare!
Click to expand...
Click to collapse
Hi juzz86!
Thank you for your response!
I do not have an external sd-card to try atm. I will look into the CWM alternatives if this does not work.
I found out that I had replaced my stock recovery with the CWM touch version, and this version allows me to use the "internal sd card" menu. This however, only works when shutting down my phone, and holding volume up+power+home. When using the fast option "reboot into recovery" from my phone, I still get the ordinary CWM - and I'm facing the same problem over again.
When trying to "mount /sdcard" in CWM, I get a standard "failed to mount" message
After looking into the Directory-bind app, I see that all my data is stored in my /sdcard folder, and nothing in the /sdcard/external_sd folder, so I followed the guide just for fun (since it doesn't really describe my problem), but it didn't work, and I still can't mount my /sdcard folder in CWM.
I'm going to see over the forums about the mount sdcard error in the forums, and try the kernel as suggested if nothing else works BB!
EDIT: I see that in newer versions of CWM, there should be an option for installing a zip from the internal sd card. My question is: Is it possible for me to update my version of CWM, while using the same kernel? I can't do this in ROM Manager.
Should be, yes. You'll probably need to use Fastboot or ODIN to flash it, so.e devices get zips but I'm unfamiliar with the GS2 Development.
Your best bet will be to find the CWM thread in one of the GS2 forums, and follow the instructions in there.
I wasn't aware that flashing a recovery through ROM Manager changed your kernel?
juzz86 said:
Should be, yes. You'll probably need to use Fastboot or ODIN to flash it, so.e devices get zips but I'm unfamiliar with the GS2 Development.
Your best bet will be to find the CWM thread in one of the GS2 forums, and follow the instructions in there.
I wasn't aware that flashing a recovery through ROM Manager changed your kernel?
Click to expand...
Click to collapse
It didn't. My answer was a bit messy, sorry. I understand that you can flash a new kernel through odin or CWM, and therefore get a new version of CWM bundled - like the customized versions (like the link you provided). I only want to update my version of CWM, but stay on the same kernel as before. What Rom Manager is able to do, is updating your version of CWM (the official ones).
If I'm mistaking, please let me know.
No, that's right you can update CWM by flashing a kernel, but you can also find a standalone recovery.img, sometimes a flashable zip, or you can use ROM Manager. All three of these methods won't touch your kernel
I got the oposite problem...
Hi all i am new .. but basicaly my issue is:
I'm trying to install a custom ROM on my rooted Galaxy SIII I19300.
I've placed the rom inside an external sdcard, entered Recovery mode (clockworkmod CMW-based Recovery) and clicked "install zip from sdcard" then "choose zip from sdcard", after that the console presented me with an error "E:Can't mount /sdcard/".
I've tried to select "mount /sdcard" in the mounts menu and it errors:
"Error mounting /sdcard!"
The sdcard works fine and I'm able to read/write from/to it without any issues in GSIII and in others cellphones..
The SDCARD got 2 gb and its formated in FAT32.
Any one help plz?
Format your sd card !
respected sir,
format your SD card , since cwm, twrp, and other recovery mods require mostly 'FAT32' format.
so, please take a bkp and format it to go ahead without probs!
I need help installing a ROM, I know how to root and i have superuse and red recovery, however, everytime I install a ROM, i get soft bricked with a robotic woman's voice saying, "convert system partition, data not available... Convert data partion, system not available.
Any ideas? I use the ODIN-one-clcik KJ2 tar i believe.
Thanks in advance for any help.
Sent from my SGH-T839 using XDA Premium Apple
Finally Installed a ROM successfully, thanks guys for you help,
My solution:
Disable Anit-Virus from blocking important programs (SuperOneClick & One Click KJ2 ODIN)
SDCard needed to be partitioned to ext 2048 and swp 0 (backup card before doing so)
Place Recovery file in system/bin with root explorer, and update.zip on SDcard( Don't Flash !)
Delete any ClockWorkMod on your SDcard,
intsall Rom Manager,
Flash Rom Manager with Sidekick 4g,
reboot into recovery, by using 2click + power method, if still blue recovery, re-install packages; it should go to Orange recovery version 4.0.0.2
Make sure Mounts are correct before flashing ROM,
Thanks for all you help guys :good::good::good:
d9vabder said:
I need help installing a ROM, I know how to root and i have superuse and red recovery, however, everytime I install a ROM, i get soft bricked with a robotic woman's voice saying, "convert system partition, data not available... Convert data partion, system not available.
Any ideas? I use the ODIN-one-clcik KG2 tar i believe.
Thanks in advance for any help.
Sent from my SGH-T839 using XDA Premium Apple
Click to expand...
Click to collapse
The woman - aka: Linda
This is the voodoo/ext4 lagfix.
IIRC, and knowing krylon360, it uses the sd-ext partition on your sdcard to temporarily store your files while it converts your partition.
Backup your sdcard, go into recovery. Partition your sdcard. Give EXT 2048 and 0 for swp.
Then try Odin again.
Thank you, will do
Sent from my Inspire 4G using XDA Premium App
after I ODIN, I get stuck on SuperOneClick now, *daemon not running. starting now on port 5037* and when I look at my processes, I have two ADB.exe running, I end the one with the lowest memory (984kb) and one click pops up a window "Automatic version check failed. Is your OS version 2.0 or higher." (Yes) I click ok and then it gets stuck on waiting for device.
d9vabder said:
after I ODIN, I get stuck on SuperOneClick now, *daemon not running. starting now on port 5037* and when I look at my processes, I have two ADB.exe running, I end the one with the lowest memory (984kb) and one click pops up a window "Automatic version check failed. Is your OS version 2.0 or higher." (Yes) I click ok and then it gets stuck on waiting for device.
Click to expand...
Click to collapse
So, I'm guessing Odin worked and Linda talked a bunch and everything in that part worked.
If that is the case. When you boot to recovery, can you run 'adb shell' and get a root prompt?
If so, first mount /system
In adb shell:
Code:
mount /system
then close out of adb shell by typing 'exit'
Then download this zip.
extract it and cd to the directory it extracted to.
Then type:
Code:
adb push su /system/xbin/
adb push busybox /system/bin/
adb shell
back in adb shell, we just need to make sure su and busybox are set with the sticky bit:
Code:
chmod 4755 /system/xbin/su
chmod 4755 /system/bin/busybox
You now just need to reboot, go to the market, install supersu by chainfire and busybox by stericson and run them both (to mostly upgrade the su binary, but also to make the 'smart links' in busybox)
You are now rooted.
If you don't have adb shell in recovery, please point me to your recovery and I will fix it.
I was never very familiar with using ADB shell, is it, my cmd? Or is it in some kind of emulator?
After this , I think I'm will to have some one do it for me, I'll pay for shipping and everything
The recovery I have after ODIN restore is blue, with no mount options, advanced, etc. All it has is this:
Android System Recovery <3e>
Samsung Recovery Utils
- for BML -
reboot system now
reinstall packages
delete all user data
delete all user cache
delete cache data
I think my SD card is corruput, it doesnt show up when I plug it into an adapter to USB to computer; my 16gb does show up.
Im going to retry everything with the 16gb card and I found out how to ADB push, hopefully I'll be able to Root Again on the 16gb
d9vabder said:
I was never very familiar with using ADB shell, is it, my cmd? Or is it in some kind of emulator?
After this , I think I'm will to have some one do it for me, I'll pay for shipping and everything
The recovery I have after ODIN restore is blue, with no mount options, advanced, etc. All it has is this:
Android System Recovery <3e>
Samsung Recovery Utils
- for BML -
reboot system now
reinstall packages
delete all user data
delete all user cache
delete cache data
I think my SD card is corruput, it doesnt show up when I plug it into an adapter to USB to computer; my 16gb does show up.
Im going to retry everything with the 16gb card and I found out how to ADB push, hopefully I'll be able to Root Again on the 16gb
Click to expand...
Click to collapse
The recovery you have after ODIN'ing is the stock default Recovery. You'll need to root, and replace the recovery. You can use ADB like he said, or just use any old Root File Explorer (By the way, Root File Explorer is on the Market, pretty good but you have to pay.)
TheLastSidekick said:
The recovery you have after ODIN'ing is the stock default Recovery. You'll need to root, and replace the recovery. You can use ADB like he said, or just use any old Root File Explorer (By the way, Root File Explorer is on the Market, pretty good but you have to pay.)
Click to expand...
Click to collapse
When I copy the recovery file into the bin folder in system, and place the update on root of SD, it still comes up blue, however, if I take a recovery out of a ROM file and replace it, it still comes up blue, but, if I hit re-install packages on stock recovery. I was finally able to change my mounts, and now I get this after installing ROM in orange recovery, " Convert system partition, 2 min... back up operation." Wow, now I have a red VooDoo recovery. Wouldn't reboot, or install any ROM from SD because it wouldn't let me mount the SD CARD,
mount /sdcard
error
bhundven said:
The woman - aka: Linda
This is the voodoo/ext4 lagfix.
IIRC, and knowing krylon360, it uses the sd-ext partition on your sdcard to temporarily store your files while it converts your partition.
Backup your sdcard, go into recovery. Partition your sdcard. Give EXT 2048 and 0 for swp.
Then try Odin again.
Click to expand...
Click to collapse
After I did this to my 8gb micro sd, It is now unreadble, evene after setting back to defaults.
I'll test it on a 1gb, before my 16gb.
Right now I have the VooDoo recovery, but I can't install ROMS because it says, "can't mount sdcard," and when I try to mount it, it says:
E:Can't mount /sdcard
Error mounting /sdcard!
And Rebooting system takes me back to recovery or a boot loop.
TheLastSidekick said:
The recovery you have after ODIN'ing is the stock default Recovery. You'll need to root, and replace the recovery. You can use ADB like he said, or just use any old Root File Explorer (By the way, Root File Explorer is on the Market, pretty good but you have to pay.)
Click to expand...
Click to collapse
The stock recovery has voodoo lagfix?
d9vabder said:
After I did this to my 8gb micro sd, It is now unreadble, evene after setting back to defaults.
I'll test it on a 1gb, before my 16gb.
Right now I have the VooDoo recovery, but I can't install ROMS because it says, "can't mount sdcard," and when I try to mount it, it says:
E:Can't mount /sdcard
Error mounting /sdcard!
And Rebooting system takes me back to recovery or a boot loop.
Click to expand...
Click to collapse
Can you mount that sdcard with a card reader?
Run a filesystem check, make sure it is good.
bhundven said:
The stock recovery has voodoo lagfix?
Click to expand...
Click to collapse
No. I mean to say he's talking about a blue recovery..this could be the factory Samsung recovery. On the Sidekick the default CWM is Orange, and Voodoo CWM is Red.
TheLastSidekick said:
No. I mean to say he's talking about a blue recovery..this could be the factory Samsung recovery. On the Sidekick the default CWM is Orange, and Voodoo CWM is Red.
Click to expand...
Click to collapse
Don't just ask for colors, ask for versions
Does it say 3e?
Or is it version 3.0.2.8 (red or blue)?
bhundven said:
Don't just ask for colors, ask for versions
Does it say 3e?
Or is it version 3.0.2.8 (red or blue)?
Click to expand...
Click to collapse
Point well made haha, but for people who often times run into these problems don't know the versions. The only way I was able to establish versions were through color. Sorry if it doesn't make sense.
Sent from my SGH-T989 using Tapatalk 2
TheLastSidekick said:
Point well made haha, but for people who often times run into these problems don't know the versions. The only way I was able to establish versions were through color. Sorry if it doesn't make sense.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Well, the version number is on every screen in recovery. It's always easy to find, because it says v3.0.2.8 or similar.
The point is, in the future, there maybe newer versions, and if you get in a good habit of knowing the version number, it helps to differenciate between different versions of CWR and other recoveries:
2x from Stock Android Recovery (v2 is from donut to eclair)
3e from Stock Android Recovery (v3 is from froyo to jellybean)
v2.5.1.x from Froyo CWR
v3.0.2.8 (Stock CWR- blue or Voodoo CWR- red) from early Gingerbread
there was a v4.x.x.x, but I don't remember how long that lasted...
v5.0.x.x from newer Gingerbread CWR
v6.0.1.x from ICS and Jellybean CWR.
It helps you to know where the recovery comes from. This info is useful for any phone you are on
No, I had stock recovery, I would place a recovery from the Glorious+Overdose ROM into the system/bin, and it would still come up blue, however, when I choose install packages on blue recovery, it takes me to Orange recovery, I'll check versions. And yes, I have an adapter for the sdcard, I checked it, nothing comes up, its done/fried. I'm afraid to try changing the ext and swp on my 16gb 10class because I don't the same results.
d9vabder said:
No, I had stock recovery, I would place a recovery from the Glorious+Overdose ROM into the system/bin, and it would still come up blue, however, when I choose install packages on blue recovery, it takes me to Orange recovery, I'll check versions. And yes, I have an adapter for the sdcard, I checked it, nothing comes up, its done/fried. I'm afraid to try changing the ext and swp on my 16gb 10class because I don't the same results.
Click to expand...
Click to collapse
Sounds like you had a bad sdcard and did something wrong with the overdose rom stuff. I wouldn't be afraid of the 16G sdcard. Go for it.
Repartitioning your sdcard doesn't fry sdcards.
Maybe TheLastSidekick will chime in and help out with your recovery issue, but I'd still suggest moving to the 16G, partition with 2048M of ext and 0 swp and odin again. try the glorious+overdose rom directions again.
Cool, so I re-did everything (ODIN, rooting) I deleted the clockwork that was already on the SD with RootExplorer, put the Update.zip on root of sdcard, and the recovery in the system/bin and rebooted into recovery successfully with Rom Manager, I have Orange CllockworkMod Recovery v4.0.0.2, now I am going to partition the SD card.
Just one more question, Can I use the same 16gb SD card on my rooted HTC Inspire 4G for ATT? Or do I need to re-partition the sdcard?
d9vabder said:
Just one more question, Can I use the same 16gb SD card on my rooted HTC Inspire 4G for ATT? Or do I need to re-partition the sdcard?
Click to expand...
Click to collapse
I'd repartition, but don't forget to backup first.
(Now, I know this is not in the right section or even in the device's page, but...)
Forewarning: I am NOT responsible for any damages caused by running this tool. (You ran it, not me.) Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Pio_masaki and I have been working hard for almost a year to get root on the ICS version of the Toshiba Thrive 10.
Last night, I was able to finally sneak past sealime.ko and have it work.
It uses the "root any ICS device" tool, with special modifications specifically for the Thrive 10.
(can't post any links, so it's on the "thrive-hackers" github page.)
Special note: While it is set up for OSX ADB, I have not been able to find any binaries.
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
rohads said:
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
Click to expand...
Click to collapse
Saying there is a method to root it now, yes, we got around sealime.ko. This means we can flash the HC bootloader which is unlocked, which allows custom recovery and kernels/ramdisks (boot.img) to be used.
BTW the link is https://github.com/Thrive-Hackers
congrats guys ! very awesome work !
jdsingles deodexed ROM w/ agat63's 1.3 kernel Suped up w/ CB 6.26.13
More specifically, it bypasses sealime to flash the unlocked bootloader. What we did was we MVd /dev/block/mmcblk0p6 to 0p9. It's a pure fluke Pio and I found out that it works. We found out that sealime was explicitly blocking write to 0p6, so he semi-sarcastically said to move it. I ran the mv command, whadda ya know? It worked!
'Course, getting the tool completed wasn't as simple as that...
PS: Could we get this moved to the Toshiba Thrive Development section?
Have instructions been written for the process?
worked for me
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
navyguy said:
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
Click to expand...
Click to collapse
Try fastboot flash:raw.
Is there any need to do a backup before rooting?
TubaMeister said:
Is there any need to do a backup before rooting?
Click to expand...
Click to collapse
Not explicitly, but it wouln't hurt in case your tablet got into contact with allspark.... er, the bootloader didn't flash, and you're stuck in a bootloop.
easy root and CWM recovery
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Uh oh
robyn402 said:
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Click to expand...
Click to collapse
I installed the drivers, used the root tool, the restore was successful, but now the tablet is stuck in a boot-loop mode.
The root tool was running, there was a line that said the screen would go blank, which it did, and it stayed there for several hours. When I came back to check on it, the tablet was off, so I turned it on. That's when I found the boot loop. It'll get to the home page, tell me that nova launcher has stopped, then loop back to the moving stars section of the boot screen.
Any ideas on what to do now?
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Kyonex said:
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Click to expand...
Click to collapse
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
DLeach4512 said:
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
Click to expand...
Click to collapse
also make sure you open the zip and place the update.zip on your card -
From my GSIII - jd's Stock/Rooted/Deodexed 4.3
Kyonex said:
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
Click to expand...
Click to collapse
Excellent!
1) I had to extract "update.zip" from the ROM I had downloaded.
2) I re-formatted the card I was using to FAT32 instead of FAT.
3) I was able to get the install started with no trouble after following your directions.
BIG THANK YOU FOR THAT!
I got a successful install message, and then it booted!
Thanks a million!
Problems after Mount Changes
I changed the mount as described on thriveforums.org to allow apks and data to go to the external sd rather than "shared" internal memory.
I now have the situation with less free memory available on the sd card than on internal. The CWM backups went on the physical card- a 32 G one almost full. Will look for a major mfr 64 Gig.
One or so issues with the revised mounts where the external sd card is now internal. They relate to making backups with dalepl's latest CWM 6.0.1: where to put CWM backups for now and are they being made correctly with the revised mounts?
The backup made prior to the mount change looks normal: a single, dated/numbered folder about 2.6 Gb, 6 files: boot.img, cache.ext4.tar, data.ext4.tar, nandroid.md5, recovery.img and system.ext4.tar. However, the one made after the mount change also has a dated, numbered folder of only 15.8 Mb and 7 files: .android_secure.vfat.dup, boot.img, cache.ext4.dup, data.ext4.dup, nandroid.md5, recovery.img and system.ext4.dup. There is a second folder associated with the later bu called "blobs", which is huge --2.76 Gb, 3292 folders and 6581 files. Is this an expected result and any one think it might be a valid bu?
Also, it went on to the external SD (now "internal") and total storage use is now almost 28 Gb out of 30.2. I now have the situation with less free memory available on the sd card than on internal. The stuff there looks ok, pix movies and music plus CWM bups of 5.5 G and App_Backup_Restore archived apks at 2.8 Gb. So, I copied the cwm backups folder to the real internal memory, now sdcard2. I assume this true internal memory might get wiped during a restore so, this is not a valid storage site for this? And, if I put copies on a spare card, will that really work if my downloaded apps are on the original card, eg does the CWM backup copy the external card apps?
As I note, for some reason this 'blobs' folder won't copy easily to a USB via the Thrive or Win 7 pc. It also won't copy to a Win 7 HD partition where I store my Thrive stuff. (Update: I was able to do a wireless transfer to my pc and then, from there, to a spare SD card.)
Any thoughts? Should I go back and change the mounts to default?
BTW, I find FolderMount has no real use with the changed mount on the Thrive unless someone tells me otherwise. With the Thrive mounting the external card as internal, files go to the physical card.
gberpa,
I don't understand your question - it is very long. But I know that custom recovery (CWM / TWRP) itself remounts sdcard and internal memory before wipe process so it will wipe correct memory (only internal memory). If you need to change the ROM you don't need to worry about mounting paths because after wipe mounting paths will be restored to original.
Partition layout of Toshiba Thrive 10.1" ICS
AmEv said:
Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Click to expand...
Click to collapse
Can you give us information on the Toshiba Thrive 10.1" ICS partition layout and their names, please?
We would like to compare it to ours Toshiba Excite Pro (AT10LE-A, tostab12BA). A Dirty Cow enabled KingoRoot has given us a temporary root.
[Q] How Root Toshiba Excite Pro AT10LE-A-108 by dexxxZ
https://forum.xda-developers.com/showthread.php?t=2583677&page=6
Sent from my takee 1 using XDA Labs