Hi,
I bought my 10.1v in July and I was very happy with it. Soon, I realised that HC 3.0.1 was a bit unstable and very basic...
I started looking for an update to 3.1 or above and found nothing (ad still there is no update).
So, 2 weeks ago I was looking for good guides for rooting my tablet and installing a Custom ROM.
And found many different and many good ones.
It's been a week since I last touched my tab, so I can't exactly remember what I did or who's guide I followed (a couple different ones actually).
The problem is: I'm kinda a noob at this. Well, a total noob actually...
But I got the bootloader unlocked and the I got root access, or the other way around...
Anyway I got it unlocked and rooted, erased all the user data and went back to factory settings.
Started the tab and got the setup and etc etc... (Last time it booted)
I activated USB Debugging and Unknown Sources as I was going to install HDBlogGalaxy ICS v2.2.
I (kinda) followed the guide with the ADB.exe in the cmd window.
Then CWM Recovery, install from SD Card, choose HDBlogGalaxy ICS v2.2 and it seemed to have it installed it okay.
Then it got stuck at the boot and I started playing in the CWM Recovery... (stupid of me...)
I might have changed the partition SD Card, wiped everything and more.
So now I'm left with a non booting tab with:
Access to fastboot
Access to Odin3
Apparantly no access to ADB
Unable to mount USB (in CWM) ->error: Unable to open ums lunfile (No such file or directory)
Unable to mount /efs (in CWM)
maybe more things, as I'm not very familiar with flashing android stuff
I tried flashing over a stock rom with Odin3 but it gets stuck at boot.
I can boot CWM Recovery with fastboot, but can't get access to internal memory to copy over a Custom Rom.
I tried nvflash but I keep getting the error: Nvflash started, rcm version 0X4, command send failed (usb write failed).
I'll accept any advice and I will be immensely grateful if someone could help me my fix my tablet.
Grtz, Aythamie
Bricked Galaxy Tab 10.1v
I'm in exactly the same situation and I'm looking for a hopeful Fix
Hopefully some genius developers on here can help us out.
I see you posted this a while ago did you get it solved? If so could you let me know how you fixed it?
Cheers
Related
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
Hello, I'll try to explain what happened to get where I am now, and explain with details the last errors of my GT-9100.
I had a stock room jelly bean 4.1.2 installed. I had Android encrypted + SDCARD encrypted, and decided to format, but I didn't undo the encryption. As result, after master reseting it, it asked for a password do decrypt (as always asked when I turned the phone on), but it wasn't recognizing my password anymore. So I tried to clean and wipe all possible things, which ended on the device stucking at boot (doing boot loops, not asking for password anymore). I got an error on CW Recovery E: Could not load emmc (sounds like my internal storage is gone)
Later on, I tried to re-install the ROM, but got alot of trouble with windows drivers. Couldn't get any rom installed again. My device was then stuck at start, not even showing the white Samsung Galaxy S II GT9100 screen. After trying a variety of MODEMs, Kernels, I always get stuck on boot.info, zimage (kernel) on ODIN (Both 1.85 and 3.07 versions).
The only thing that has worked so far is changing the bootloader to the stock version. After doing this, my smartphone turns on on Chinese language. The ROM loaded is a jelly bean, but it has no status bar, can't open camera/folder explorer, can't do calls, can't acess internet, doesn't even show the configuration menu. And everything is chinese. BTW Calculator was working lol.
So this is the situation. Has my internal storage been gone forever? Is there a way I can flash without being stuck at boot.info or zImage when trying to flash kernel, both on Odin messages? Or is my phone really bricked? Thansk alot, I'll pay close attention to this.
EDIT: I haven't found after a day of research anyone that did data wipes in an encrypted phone, so this can be a guide for any future similar case.
gerijeb said:
Hello, I'll try to explain what happened to get where I am now, and explain with details the last errors of my GT-9100.
I had a stock room jelly bean 4.1.2 installed. I had Android encrypted + SDCARD encrypted, and decided to format, but I didn't undo the encryption. As result, after master reseting it, it asked for a password do decrypt (as always asked when I turned the phone on), but it wasn't recognizing my password anymore. So I tried to clean and wipe all possible things, which ended on the device stucking at boot (doing boot loops, not asking for password anymore). I got an error on CW Recovery E: Could not load emmc (sounds like my internal storage is gone)
Later on, I tried to re-install the ROM, but got alot of trouble with windows drivers. Couldn't get any rom installed again. My device was then stuck at start, not even showing the white Samsung Galaxy S II GT9100 screen. After trying a variety of MODEMs, Kernels, I always get stuck on boot.info, zimage (kernel) on ODIN (Both 1.85 and 3.07 versions).
The only thing that has worked so far is changing the bootloader to the stock version. After doing this, my smartphone turns on on Chinese language. The ROM loaded is a jelly bean, but it has no status bar, can't open camera/folder explorer, can't do calls, can't acess internet, doesn't even show the configuration menu. And everything is chinese. BTW Calculator was working lol.
So this is the situation. Has my internal storage been gone forever? Is there a way I can flash without being stuck at boot.info or zImage when trying to flash kernel, both on Odin messages? Or is my phone really bricked? Thansk alot, I'll pay close attention to this.
EDIT: I haven't found after a day of research anyone that did data wipes in an encrypted phone, so this can be a guide for any future similar case.
Click to expand...
Click to collapse
Tried installing Android 2.3 stock bootloader / rom ?
jiboncom said:
Tried installing Android 2.3 stock bootloader / rom ?
Click to expand...
Click to collapse
No I haven't. Is there any online link here? I couldn't find it.
Solved
After a day looking for it, I solved my problem
I tried several kernels, roms with almost all odin versions. The best one for gt-I9100 was odin 1.87.
This was the deal: After cleaning the encrypted internal storage, it got corrupted. So one of the first steps to get my phone reacting again to ODIN when installing new ROMs was installing the original GT-9100 .PIT file and re-partitioning (Even with every forum/site telling me I should never do it).
So, if you ever do the same mistake as me, try this:
Install a new kernel, then .PIT original file. Get a proper MODEM file, and finally try flashing your ROM.
I also got alot of problem with my USB cable, which is kinda damaged, so out of 10 plug-ins, only a few would work for ODIN. Try getting a brand new cable.
That's it.
gerijeb said:
After a day looking for it, I solved my problem
I tried several kernels, roms with almost all odin versions. The best one for gt-I9100 was odin 1.87.
This was the deal: After cleaning the encrypted internal storage, it got corrupted. So one of the first steps to get my phone reacting again to ODIN when installing new ROMs was installing the original GT-9100 .PIT file and re-partitioning (Even with every forum/site telling me I should never do it).
So, if you ever do the same mistake as me, try this:
Install a new kernel, then .PIT original file. Get a proper MODEM file, and finally try flashing your ROM.
I also got alot of problem with my USB cable, which is kinda damaged, so out of 10 plug-ins, only a few would work for ODIN. Try getting a brand new cable.
That's it.
Click to expand...
Click to collapse
Add [SOLVED] to the title.
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
xFoCaLx said:
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
Click to expand...
Click to collapse
Fair play, at least you tried and you probably learnt a lot in the process.
You have nvflash backups so don't panic. It is fixable.
I am going to send you my google talk address now over PM. Add me by going to gmail on your PC in your browser and adding me in the bottom left hand corner to chat. I will try and talk you thru it.
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
puntxo said:
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
Click to expand...
Click to collapse
This was a new one on me and I have no idea how he got himself into it but we managed to fix it anyhow.
He was the first person I have helped tho that needed to restore unlock-token.img, factory-config.img and bricksafe.img as he had some error saying failed to inject certificate, unrecoverable bootloader.
As long as you have all your nvflash backups you will be fine amigo.
Here is a little background;
I'm new to the android world and this is my first tablet using it. I received the tablet under the terms that its mine, if I can fix it. THE TABLET So the research begins. The original problem with the tablet: everything would crash after unlock screen, including loader. The tablet does not have any kind of visual recovery mode using the hard buttons. At this time I did not know about any of the tools that I probably could of used to save the stock firmware. When I hit Google with "Cruz velocity micro t510" not much came up, so I spent about a day trying all sorts of different terms with that. There was not even a place to download firmware from cruz, they say wifi is mandatory to upgrade, from within the tablet... I finally ran into a post somewhere where someone said the cruz t510 is an allwinner a10 in disguise. They went on to say that all you need to do is use Livesuit and flash 'sun4i_crane_T05a_v1.5_mxc6225' img from eken website then from there you can use the compatability zip and upgrade to cm10.
So all was good. The t05a firmware there works perfect on it, like the guy said. I kept that on there for a day before I went on to CyanogenMod.
Here is where I am stuck; (Tired of googling, please help )
I decide to try AOKP and CM10 using http://forum.xda-developers.com/showthread.php?t=1821398 and one for AOKP too with t05a-v1_compatibility_1.2.x.zip. And http://forum.xda-developers.com/showthread.php?t=2189640 for recovery mode. I learned how to setup and use ADB with command prompt here.
So I install CWM using ADB shell and reboot into recovery using the sh file. I first folowed the steps to install AOKP and all goes smoothly until I reboot.
I get a notice saying "Damaged SD Card, You may need to reformat" and I realize that it is talking about the internal disk space. I try to reformat and the same notice will appear again or I will have to go in Settings>Storage and Mount SDcard, only to be told no, it is damaged. So I got scared and re-flash back to the eken stock firmware with livesuit. Guess what, sdcard mounted and working again. Then I go on to repeat the upgrade but with CM10 this time. Same result.
I have gone back to the stock image and retried many times. I tried with all three partition versions of that CWM I use, even though I knew it was 10, or so adb shows. I also tried partitioning and formmating with CWM, many times, each a little different.
Short, Sweet, and Simple version;
THE TABLET
Eken a90 stock firmware using livesuit -> SDCard works fine
CM10 or AOKP with t05a-v1_compatibility_1.2.x.zip using CWM 6.0.2.8 -> SDCard damaged
If anyone could help I would very much appreciate it. I need a break from all the research, I'm going to play gtav and hope someone has a solution for me.
I'm trying to upgrade my T510 from original manufacturers specs and could sure use whatever files uou have
***SOLVED***
I did attempt two. I was unable to sideload using TWRP because it was unable to mount. I decided to format data again. Then I put my flashdrive into the OTG cable and plugged it into the phone. I flashed CM 10.2 Stable and BOOM it worked. Moral is that if you cant mount, reformat it and try using an OTG cable if you cant sideload. Three days paid off. My phone works again!
-Donald
***SOLVED***
(Below is original question)
First of all, hello everyone. I just made an account and am glad I've done so. Seems like a website that's friendly to a mildly knowledgeable android user (well, im a bit of a noob).
Phone:
HTC ONE m7att, twrp recovery, unlocked bootloader (dont know what version, but latest im assuming b/c i got it off warrantee December) I think it isnt rooted anymore because when i reboot from TWRP, it asks me if I want to install SuperSU.
Description:
I was trying out CWM (latest one) to flash CM 11, and it worked, but I didn't like the look. So I flashed TWRP (latest one) to restore my TWRP CM 10.2 backup. I wanted to wipe 'dalvik cache' 'cache' 'data' and 'system' (advance wipe), but i ended up also wiping internal memory. Oops.
Attempts:
1.) I decided to try this http://forum.xda-developers.com/showthread.php?t=2251800
I ended up stuck where I am suppose to flash the ROM zip. My guess is that I have been flashing the wrong ROM files (I tried flashing a few after failed attempts) I guess the solution to this would be to find the right file, but I cant seem to find it after hours of searching, amongst other methods to add an OS. (Oh and I should note, my bootloader was LOCKED before I tried the RUU) Speaking of which...
2.) I decided to sideload a custom ROM. Ive never done this (First time rooting was late September 2013 with d2att Galaxy s3, which is MUCH easier to work with). I tried mounting it with data and later USB-OTG with little success. When I try to ADB Sideload, it is unable to mount. (Bootloader is UNLOCKED)
Questions:
If i was to do attempt 1, can someone please provide me with the correct link to the correct ROM.zip? Ive tried several download threads for the AT&T HTC One with no success.
If I was to do attempt 2, (which i prefer because I want to run CM 10.2) How do I fix the "unable to mount"? Ive tried reflashing the TWRP recovery through fastboot. And also, bonus points for showing me how to transfer zip with sideloading (bonus because I have found a few videos and threads, but they were not clear)
I have done about 4 to 5 hours of research with no luck. Please dont ridicule me for "not searching the threads," because I am frustrated after doing just that with little luck. I know this should be an easy fix, which adds to the frustration. Please help!! Thanks for reading.
I just looked this over, and my ignorance clearly shows, so please be respectful about that. Guidance is helpful, judgement is not, so dont post what I already know about my semi-lack of knowledge with using Android. Thanks.
UPDATE (Still need help):
Another problem I ran into was that the /sdcard would not mount for any recovery. Im guessing the /sdcard is corrupted. Any help with that would be appreciated. Also, I was able to sideload CM10.2 zip file with CWM on another computer, but when I reboot it, it got stuck in a boot loop.
Its been a whole days worth of trouble. First World Problems huh? Please help ASAP! Thanks again.