Related
hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.
Hi All.
How Can I get my pictures off my poorly One X?
Really need help with my 1x. It switched itself off the other day in my pocket and now it hangs on the 'quietly brilliant' screen and wont start up. I have rooted it and it has clockworkmod recovery v5.8.2.7 on it- I didnt put a custom rom on it, just rooted it.
I am unable to mount USB storage through clockworkmod as I am getting 'unable to open ums lunfile (no such file or directory)' error. I had hoped that if i could mount the usb, i could at least access the sd through my pc to transfer pictures from my phone. I am really at a loss now. I was wondering if it could be a battery issue (i have had it on charge for sometime but on the hboot screen it says 'battery level is too low to flash'). I really dont know what to do now. if i cannot connect via usb to pc, then i have no way of trying to transfer pics and files or un-rooting or transferring and img files to try some sort of re-flash.
In CWM recovery, i have browsed for zip files and can see all the folders there so i assume all my pictures are also still present.
The pictures are the most important to me as they are holiday pics. I would, of course, just like the phone to work again but at the very least, be able to get my pics off it.
Any help much appreciated guys. Thanks, Pete.
Flash this recovery and mount it again !
http://db.tt/SPXdFfPw
It may take a while before it pops up !
Your recovery is out dated. It doesn't support ums.
Ah yeah you need to charge it first. 2 options to do that.
1: power down from the bootloader and charge it if that doesn't work you can try option 2
2: place this file in the fastboot folder on the pc
http://db.tt/aLqeTpPO
Then put the phone in the bootloader and execute the file with admin rights. It should continuuesly reboot the phone and charge it that way little by little !
Mr Hofs said:
Flash this recovery and mount it again !
http://db.tt/SPXdFfPw
It may take a while before it pops up !
Your recovery is out dated. It doesn't support ums
Click to expand...
Click to collapse
How will I be able to flash it? I cant get my phone to appear on my pc. Thanks for quick reply. Really stuck with this.
You need to charge the phone, flash the new recovery and mount again.
The recovery is flashed with the phone in the bootloader and flash via command on pc
Mr Hofs said:
You need to charge the phone, flash the new recovery and mount again.
The recovery is flashed with the phone in the bootloader and flash via command on pc
Click to expand...
Click to collapse
i'll try that if I can get my pc to see the phone. Will doing this keep all my pics on my phone memory? Really dont want to lose them. thank you
As long as you don't wipe the sdcard inside the recovery it will stay
Mr Hofs said:
As long as you don't wipe the sdcard inside the recovery it will stay
Click to expand...
Click to collapse
half done got new cwm flashed and got pics onto pc. big thanks. any idea where my contacts and sms would be stored? phone still wont boot so i'm thinking of a reset but want to rescue contacts n sms if poss 1st.
Dont know if they are in a file on the sdcard or in a system directory. I always stored my contacts on Google.
I am running my S3 on TMO, with 4.3 booloader & latest modem. I was also running a 4.3.2 TW rom.
This morning, I decided to wipe the rom, then restore it, as it was the one I had in backup. I was having stuttering problems, and thought that because I had added & deleted so much stuff in the past few days, restoring my clean backup would clear it up.
I have the latest TWRP recovery, and wiped the cache & dalvik, then went to restore the rom. But when it finished, and I rebooted, got stuck at the ktoonez (my kernel) logo. I did a battery pull, and went back into recovery, did a full wipe, then tried to restore the rom. This time, 3/4 of the way through, it rebooted on its own, and started to bootloop. When I tried to get back into recovery, it would only boot to the Samsung logo, so I knew that now my recovery was gone. I used Odin on my PC to restore it, but it does the same thing. I do a complete wipe, restore the backup, but it again reboots by itself out of recovery about 3/4 of the way through, then it gets stuck at the kernel logo.
I don't have anything other than the backup stored on the phone. Is there a way that I can load a rom from my PC through recovery so that I can just start over? Or will I probably have to Odin everything back to stock, and start from there (which I've never done from the PC. I have used mobile odin though)?
Update:
I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.
anyone?
Did you go into recovery and do a factory reset?
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you go into recovery and do a factory reset?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Yes, a couple times.
I have also tried taking the card out the phone and putting it into the pc to manually place the rom on it, then flash it, but my pc wont see the card. It makes the sound that something has been inserted to a usb port, but shows nothing on the computer.
What if you flash a recovery and then a ROM?
Sent from my SGH-M919 using Tapatalk
Kamau54 said:
Update:
I decided to do a odin back to stock. Now though, after setting for a few minutes, it says optimizing apps, goes through it, gets to the little android guy shooting upwards, goes to the Samsung logo, then starts all over again. It just keeps going through it again & again.
Click to expand...
Click to collapse
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:
Code:
adb sideload location/of/ROM.zip
This should transfer the ROM to your internal sd card.
You should make sure that your computer detects the phone before the transfer with the command:
Code:
adb devices
It should should return:
Code:
List of devices attached
phone id recovery
If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.
I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.
I hope you're able to get your phone booting again!
serio22 said:
What if you flash a recovery and then a ROM?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
The phone doesn't have a rom to start with I don't think. This is what I Odin:
http://www.androidfilehost.com/?fid=23212708291682181
It's the right one, as I have the TMO S3, and I already had it on my phone to begin with. I thought it came with the stock rom included, but when I rebooted, it just gets caught in a bootloop after it says optimizing apps. I can get the recovery back, but I don't know how to get a rom on the card to flash. I even tried to use a old card, but again, my pc won't see it, so I can't put a rom on it to flash.
VolcanicSkunk said:
In TWRP recovery there is an option to sideload a file. Go to Advanced>ADB Sideload. From here you should be able to use the command:
Code:
adb sideload location/of/ROM.zip
This should transfer the ROM to your internal sd card.
You should make sure that your computer detects the phone before the transfer with the command:
Code:
adb devices
It should should return:
Code:
List of devices attached
phone id recovery
If it returns the above, you know you're okay to transfer. If it doesn't show your phone's model, that means that the computer doesn't recognize your phone as being detected (probably driver related); therefore, your file will not transfer with the sideload command.
I saw your post in the S3Rx thread that your computer won't read your sd card either. I'm not sure if you're using Windows/OSX/Linux, but if you're using Windows, you might want to try installing Linux on a USB drive, booting from that, then plugging in your sd card. In the past, I have had success mounting drives on Linux that would not mount on Windows. I know that this is a little more effort than is probably necessary lol. But I'm not nearly as versed as others here. I just like to tinker a little.
I hope you're able to get your phone booting again!
Click to expand...
Click to collapse
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.
But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .
Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.
Kamau54 said:
I am on a windows, and have only used the command prompt once a couple years ago, so my experience with it is limited.
But when I tried the command "adb devices", I got an error message saying that it was not a recognized command .
Also, What is Linux? If it is bigger than a couple gigs, then I don't have any place to put it.
Click to expand...
Click to collapse
The reason you get the "adb is not a recognized command" is because you don't have the Android Software Development Kit (SDK) installed. The SDK contains an executable command called Android Debug Bridge (adb). You can download and install it from the developer.android.com website. But chances are, you aren't going to have the drivers installed for your computer to recognize your phone in recovery if you don't have the SDK already installed.
If you aren't familiar with Linux, then I would say that going with that route is far more work than you're likely to want to put in to get your phone functioning.
If you'd like to try it though:
Linux is free to use, it is designed and compiled by several different companies. The more well known are: Ubuntu, Mint, Red Hat, and Backtrack. There are many more.
You can visit any of those sites, download the software, and install it on a USB drive. It usually requires a 4GB USB drive. Instructions to install it to a USB drive are usually listed on the site.
After installing it, you can boot your computer from the USB and use Linux like a fully functioning OS right from the USB drive. You won't be required to install it.
You can then try downloading the ROM while on Linux and transferring it to your sd card.
Sidenote:
Linux is an open source operating system on which Android is based. That is why Android is open source, it is ruled by the same GNU General Public License that governs Linux.
VolcanicSkunk said:
The reason you get the "adb is not a recognized command" is because you don't have the Android Software Development Kit (SDK) installed. The SDK contains an executable command called Android Debug Bridge (adb). You can download and install it from the developer.android.com website. But chances are, you aren't going to have the drivers installed for your computer to recognize your phone in recovery if you don't have the SDK already installed.
If you aren't familiar with Linux, then I would say that going with that route is far more work than you're likely to want to put in to get your phone functioning.
If you'd like to try it though:
Linux is free to use, it is designed and compiled by several different companies. The more well known are: Ubuntu, Mint, Red Hat, and Backtrack. There are many more.
You can visit any of those sites, download the software, and install it on a USB drive. It usually requires a 4GB USB drive. Instructions to install it to a USB drive are usually listed on the site.
After installing it, you can boot your computer from the USB and use Linux like a fully functioning OS right from the USB drive. You won't be required to install it.
You can then try downloading the ROM while on Linux and transferring it to your sd card.
Sidenote:
Linux is an open source operating system on which Android is based. That is why Android is open source, it is ruled by the same GNU General Public License that governs Linux.
Click to expand...
Click to collapse
Sounds like I'm screwed then. I don't know why my pc is not seeing it now, because it always sees it when I'm copying files from & to it.
Kamau54 said:
Sounds like I'm screwed then. I don't know why my pc is not seeing it now, because it always sees it when I'm copying files from & to it.
Click to expand...
Click to collapse
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
VolcanicSkunk said:
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
Click to expand...
Click to collapse
When I insert it, and go to that, it shows up as removable disk E, but when I double click on it, it says to insert a disk into removable disk E. I think whats happening is that it's seeing the adapter, but not the card that's in it.
Kamau54 said:
When I insert it, and go to that, it shows up as removable disk E, but when I double click on it, it says to insert a disk into removable disk E. I think whats happening is that it's seeing the adapter, but not the card that's in it.
Click to expand...
Click to collapse
When you right-click on the E:/ do you have the option to format the drive? If so, you may want to try formatting it. That may fix your issue. Hopefully you don't have anything on the external sd that you can't put back on it.
VolcanicSkunk said:
When you right-click on the E:/ do you have the option to format the drive? If so, you may want to try formatting it. That may fix your issue. Hopefully you don't have anything on the external sd that you can't put back on it.
Click to expand...
Click to collapse
When I try that, it tells me there's no disk in drive E, to insert a disk and try again.
VolcanicSkunk said:
Have you tried going to your computer's device manager and seeing if it's picking it up, but just has an error?
Click to expand...
Click to collapse
This happened to me to after I installed the latest s3rx Rom...I haven't been able to recover my data or get anything to read my card.
After researching online a lot of people have had success running the chkdsk command... check it out here
http://www.ehow.com/how_7233441_restore-damaged-memory-stick-data.html
Ok, under Device Manager, the computer does see the phone as "MTP". I tried the troubleshooting process, and it went all the way through its thing, but at the end it said "failed" trying to install drivers. I just installed the proper drivers earlier today from Samsung, so I know they are correct. Also, this is as I am connected to the phone, not the card reader. The phone itself is flashing the Samsung logo, and that's as far as it has gone.
This is so frustrating because all I need to do is to get a rom onto the card. If I can get that, I can get into recovery and straighten this all out.
Anyone else with any ideas? I'm beginning to go a bit nuts thinking I have lost my phone just because I can't get a rom placed on my card.
Flash twrp or cwm, they have options to mount SD card, after that you can copy the zip and flash
Sent from my SGH-M919 using Tapatalk
serio22 said:
Flash twrp or cwm, they have options to mount SD card, after that you can copy the zip and flash
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I have the latest twrp, and have seen that option. You mean, I can copy from the pc to the card, because that's what I need to do.
Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..
Good morning guys.
I'm not really new to this forum, I've known you for years and I've always followed you for small "mods" or particular problems that I had over time with my devices.
I apologize, but I would like to ask you for help because I have big problems with an ASUS Nexus WiFi 32GB Tablet
Unfortunately, I can in no way connect it to the PC in order to install any rom (I wanted to install the rom stock). I tried everything, I even formatted an old PC and installed windows XP hoping for more compatibility (nostalgic).
The first time, I managed to install a ROM from TWRP recovery 2.8, enabling the USB-OTG and buying the appropriate cable, but then unfortunately, I wanted to try to change ROM and already I was there I wanted to update the recovery to 3.3 .1.0, but I must have been wrong to click somewhere in the recovery. I was convinced that the USB-OTG could always be enabled, so I had the security that I would always be able to install a S.O.
Now the S.O is no longer present in the device and from recovery I can no longer enable USB-OTG, and obviously in the device, no image is present that can help me, probably because I have eliminated everything with different wipes.
The PC in no way manages to see the device, whatever driver I try to install, it tells me that they have no information regarding the connected device, so I can't even use adb.
Please, help me, if needed, format a PC and install Linux or anything else I can use to resurrect this damn device.
Thank you so much for existing ...
Hello, did you try to reboot your tab in bootloader mode, and then install stock factory image from Asus? Maybe After that you will be able to reinstall twrp and custom rom you want... Your tab is unlocked? Did you try the wugfresh tool? Good luck
Thanks for the reply ichi-nii, I tried to reboot the device in bootloader mode (The menu with the open heart robot, Fastboot Mode, right?), Even if it doesn't give me many options, I can only choose whether to Turn off the device, Start it in Recovery (TWRP) or restart the Bootloader, nothing more, and from here I can't install anything anyway.
I believe the device is unlocked, or at least it was, and Fastboot tells me that it is unlocked, so ...
To use the Wugfresh tool, if I didn't err I have to be able to connect this Nexus to the PC and make it see it, but as I said ... No driver allows me to recognize this device from the PC ...
I don't know what to do ...
Isn't there a TWRP terminal way to do something? Some commands that can re-enable the USB-OTG ...
I think I inadvertently (because I didn't know what I was going towards) SELinux enabled, it was after this that the USB-OTG didn't work anymore (I think) ...
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
ichi-nii said:
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
Click to expand...
Click to collapse
Thank you so much for your help!
I tried to connect the device, both from TWRP and from Fastoboot mode but it is not recognized by Windows ... (Both Windows XP, Windows 7 and Windows 10) I tried to change USB ports and I also tried to change the cable, but nothing ...
The OTG cable is new, I used it on this device and it worked perfectly, I tried it on another device and it works, so the cable is ok, I must have done some **** myself.
Sending any file to the device is just what I'm desperately trying to do, I don't care how, I'm interested in doing it and fixing the damn thing.
If you tell me that your computer with Kali Linux sees it and you can access the memory, I try immediately.
Thank you so much !!
I'm not at all an expert on Linux, how does it work in this case? From Linux terminal? do I have to send commands? Or is it seen as a folder? ....
Forgive my humble ignorance ...
? I'm not an expert too? just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
ichi-nii said:
I'm not an expert too just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
Click to expand...
Click to collapse
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
IgNuReNt said:
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
Click to expand...
Click to collapse
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
ichi-nii said:
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
Click to expand...
Click to collapse
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
IgNuReNt said:
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
Click to expand...
Click to collapse
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
ichi-nii said:
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
Click to expand...
Click to collapse
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
Yessssss! Congratulations bro ! That's a very good news ?
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
ichi-nii said:
Yessssss! Congratulations bro ! That's a very good news
Click to expand...
Click to collapse
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
[email protected] said:
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
Click to expand...
Click to collapse
Congrats