For starters, NOTHING but AutoRec managed to finally get TWRP installed. Finally got it flashed onto stock rooted 20u...
So now no matter which version of TWRP I use 2.7.0.0, 2.8.0.1, 2.8.1.0 none of them work. Namely 2.7 can't access Data. No matter which version I use I cant even make a backup because it cant create the folder.
Fix permissions you say? Nope, "Unable to chown '/data"
Flash a ROM you say? hahahaha you got jokes. "Error opening '/data"
Any ideas what I can do to get this running properly on this ****box? Previous G2's I've messed with it all works JUST FINE
Related
I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help
I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.
ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.
OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help
ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?
OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?
herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.
One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.
Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App
Hello, I am having some problems installing a working recovery, here is my story... So first the device was 10.6.1.27.5 and its unrootable, so i downgraded to 10.6.1.15.3, where I installed TWRP recovery, and flashed CM 10.2 ROM, but it was too glitchy, so i wiped all data, and fastbooted 10.6.1.15.3 build and stock ROM. So I am now stock,
I am rooted using MottoChop method, and I cant install a custom recovery... I tryed to install TWRP 2.5.0.0 thats the version I was on before, and also tied 2.6.3.0, when flashing the .blob My device turns unresponsive, even when rebooting it with fastboot.
So left with no choice i tried flashing the .img one for JB, (Note: It is currently NOT a OTA update, but manual, so i used the 4.2 first)
I was Able to Flash the custom recovery 2.6.3.0 JB.img and it booted up and worked fine, but then it couldnt mount anything,
I was getting error message:
E: Cant mount /data
and so on... I then tried to flash 2.5.0.0 and got the same result.
GooManager cant find a recovery script for this device...I flashed the TF300T, since thats the kind i have not TF300TG
Im really lost now... I tried ClockworkManager to find a recovery and it said the same thing, I dont want to flash a CWM with flashboot since i here It is terrible.
Any Help Is greatly Appreciated
I notice that alot of these problems, I end up fixing myself... I fixed the issue
But If anyone ever comes into the same situation, heres the fix...
UPDATE to 10.6.27.5 (Yes newest version) Im using US...
Install openrecovery-twrp-2.5.0.0-tf300t-4.2.blob IMPORTANT dont flash the JB version because its only for OTA updates
Open recovery and TWRP will prompt you to install, and beleive it or not, but apparently you can root the newest version,
Just not With MottoChopper and other quick root methods!
If you have any more question, post!
lets get down to business,
I'm currently running CM10.2.0 with TWRP 2.5.0.0 as recovery, I recently tried updating to latest CM11 M4 snapshot but received the following error:
"error executing updater binary"
I read that i need to update recovery (2.6.3.0 latest) but encountered a roadblock.
I downloaded the .img to internal memory in root directory and used the terminal emulator as per TWRP instructions, rebooted into recovery but it still showed 2.5.0.0. I then tried using ADB but ran into the same issue
I've thought about using CWM but when I install ROM toolbox it says only tf200 is officially supported.
lastly tried Goomanager but it gave me an error saying recovery not found.
any thoughts on this?
any ideas would be appreciated
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
n00b1c1d3 said:
ok, tried a different version of TWRP (4.2 as opposed to JB) and it worked though cm11 still wont flash
Click to expand...
Click to collapse
What is your bootloader version is it 10.1.6.27.x
The last digit really does not matter...
If so you need this recovery here http://forum.xda-developers.com/showthread.php?t=2691886
Let me know if I can help you with anything else..
Thx Josh
ended up using that method and all went well.
thanks
Hi, after updating to 5.0, I've had some issues with SD card.
I flashed 5.0 using the google factory image, it was a clean flash too.
basically adb reboot bootloader, then flash-all.bat
After that, I figured i should make a EFS copy, so i flashed the script on xda, it worked, everything is perfect, except the SD card(?)
When I am using ES file explorer (and a lot of other root explorer, nothing worked), i have to go back to /data/media/0 to actually see the EFS_Backup folder.
Same with TWRP backups.
In /sdcard you simply cannot see it, no matter what i do.
How do I fix this problem? I am rooted stock rom, flashed SU via http://forum.xda-developers.com/showthread.php?t=1538053 using zip file and TWRP 2.8.1.0
EDIT: figured i'll add the details here as well
i have SU 2.37, latest elementalX kernel for 5.0 (also have the same issue with stock kernel so i doubt the issue is this), 2.8.1.0 TWRP because 2.8.2.0 boot loop, stock rom
EDIT #2: I just flashed SU 2.38 BETA, since someone said they fixed the issue with that, no luck for me.....
EDIT #3: Just made 2.8.2.0 boot, turns out i just need to boot into rom before going into recovery first......never had to do this but oh well, now i know.
I have the exact same problem as you do. Files just disappear one fine day. I have tried every possible custom ROM out there, every possible recovery and different versions of SU.
Will try what you recommend and report back.
Thanks for starting this thread. i'm just surprised how more people don't have the same issues.
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Scoobydumb said:
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Click to expand...
Click to collapse
Are you rooted? if so, with flashify, flash another custom recovery. I'd recommend TWRP 2.8.5.0. Its here, http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117/ and its on the latest posts as zip attachment (you need to extract the zip, because it contains an *.img).
If not, (I have not tried this because I haven't got the need to do it)
you can flash TWRP 2.8.5.0 via fastboot, but you need to unlock the bootloader.
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Scoobydumb said:
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Click to expand...
Click to collapse
You could do the second solution. But I have never done it, so I cant help you with that, just with what I theoretically know.