How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
ZiggyJapheth said:
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
Click to expand...
Click to collapse
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
O
SubwayChamp said:
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
Click to expand...
Click to collapse
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
ZiggyJapheth said:
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
Click to expand...
Click to collapse
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
ZiggyJapheth said:
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
Click to expand...
Click to collapse
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
SubwayChamp said:
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
Click to expand...
Click to collapse
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files. That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin. So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
ZiggyJapheth said:
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files.
Click to expand...
Click to collapse
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
ZiggyJapheth said:
That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin.
Click to expand...
Click to collapse
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
ZiggyJapheth said:
So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
Click to expand...
Click to collapse
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
K
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse
Ok, thanks so much,I'm about to download mobile Odin first , altho i think i tried that and it needed SuperSU permissions which the moto E5 isn't rooted...so looks like I'm about to research your other suggestions. It gives me a direction to experiment in. Again,thanks so much. Oh one last thing.. but it is sending files to the phone in sideload form. Because before it aborts, the phone I'm sending files from goes through a percentage until 100% of any given file is sent. And on the galaxy i see it received because it says installing this or that zip file before saying...updates fron external sources disabled and aborting mission. I'll be back. Thanks for the time bro
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse
Related
AARRRGGHHH! <whew>
Before it gets said, I *have* been reading. Reading, reading, reading. I'm trying to understand the whens, whys, and where-to-fors.
Specifically, this is about flashing the Tab 2 7.0:
Is it developer's preference that determines which we (users) need to use?
Is there any rhyme or reason (or differences) to which USB drivers to use?
Is there a consistent and reliable method for getting into a consistent and reliable starting state on both the tablet and the PC?
There are almost as many written procedures as there are .md5, .pit, and .img files. Some work - sometimes. Some don't work - sometimes.
I've booted, re-booted, and restarted so many times - I'm afraid I'm wearing this thing out.
I'm on my third Tab 2, and here is what I did to root every time:
1. Do not update the stock fimrware.
2. Open up Odin. Put your tablet in download mode (Power + volume down). Drivers are automatically installed.
3. Load CWM recovery through Odin.
4. Install the root zip or a custom rooted ROM through CWM.
Honestly, the type of files you're given tells you what to use to flash. I think odin only flashes md5/tar files and with heimdall, you get to choose what to flash. So yeah, this depends on developer preferences. You don't NEED to set up ADB, unless you wan't terminal access to your phone through your PC. If you do, install Kies from samsung's website. ADB drivers should automatically install once you plug in your tablet. You can then uninstall kies.
That's pretty much it. I do agree with you though, it can be quite confusing to newbies to sort through the mess and figure out what to do. heimdall/odin/recoveries/unsecured boot files etc etc.
nphil said:
1. Do not update the stock fimrware.
Click to expand...
Click to collapse
Too late! But thanks just the same.
nphil said:
You don't NEED to set up ADB, unless you wan't terminal access to your phone through your PC. If you do, install Kies from samsung's website. ADB drivers should automatically install once you plug in your tablet. You can then uninstall kies.
Click to expand...
Click to collapse
My story starts with my first root which left me with a crappy tablet. So I flashed it back to IML74K.P3113UEALCB with CWM and took the OTA to IML74K-P3113UEALD3, which left me rootless. Then, to restore root, I flashed it with ML74K_P3113UEALD3_unsecuredboot.img through Heimdall. A couple of the write-ups specify using Zadig.exe to install the USB drivers. And since the next step uses Odin, the only way I could get the tablet recognized was to let Kies connect to it first. That left me convinced that Heimdall has to use the same drivers that get installed by Zadig, and Odin has to use the Samsung drivers.
Maybe it's only on my ancient PC, but in the course of all this I discovered that Odin is picky about which USB port I use. Heimdall doesn't care. (Just one more thing to drive me nuts!) So maybe I don't need two sets of USB drivers - just the Samsung drivers? Now that I'm a *little* more experienced with the GT2, maybe I won't need Heimdall or ADB at all.
Based on what you said, I'm going to try removing all the crap I've installed and start over. I didn't know until this morning that I didn't have to install the entire freaking ADK (Just ADB.zip).
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html
doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow
Did you install those libraries properly?
Freshly baked from my Nexus 5
This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.
Hi there,
Today i've received this tablet. All good and dandy until it notified me it has an update so obviously i've gone and do the update. Surprise.. after reboot, update installment and so on the device won't boot anymore at all, and recover mode doesn't work to enter.
I've found official ROM package on their site:
ftp.vonino.org/public/Firmware/Vonino_Tablets/Pluri%20Q8/Orange%20Version/Android%206.0/
Tablet can connect to the PC, but it isn't recognized because "some drivers" missing. How can i install this ROM on the tablet from my pc ?
Thank you.
Hi,
I can't find anything about it on xda or anywhere. You'll need to contact the manufacturer for drivers and instructions on flashing their firmware.
Good luck!
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
denede said:
After i tried like almost the entire day i got the tablet in rescue mode or fastboot mode..
I've wiped/data or factory reset and the same happens... it stays in a loop when boot at logo.
I've let it to do so until the battery went dead from 100% and still the same.
I have official ROM but can't install it at all. I think the bootloader is locked?! And it doesnt even unlock it when using some fastboot commands
Also can't install nothing from SD card and when tryin to use ADB the PC can't see the device, but when using fastboot I can work on it.
In rescue mode i've done some root integrity check and at the end of the check some /system files are modified. I believe this is causing the entire problem.
Click to expand...
Click to collapse
Typically, on devices I know of, it's fastboot that you would use to flash factory images. So you should be good there. But again, I don't know if that is how your device works too. And it would also typically not matter what's been altered on your device, system wise, you would simply flash the appropriate images with fastboot.
So I'd still say you need to determine the correct procedure to flash the files you got from their site. Perhaps there site has instructions? Or a support number for help of its not working as it should?
I've talked with the support. They gave me a link with an official ROM, a different one that the one that was from the site. But they didn't even told how to use it, LOL.
Have the damn files and don't know what to do with them, OMG.
I've placed the zip archive on SD card and tried to use the option from rescue mode with 'update via sd card". The zip archive is visible but after i select it says Installation aborted :|
I've googled around and maybe my tablet needs to be at over 50% power... but it was plugged into the wall it should've worked.
edit: 100% and no good...
edit2: they sent me another e-mail with a pdf file in which it is explained how to flash their device.
I installed some cyanogen rom on my tablet and now everytime I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile odi n(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically its useless and I do now know what do to... Please, someone just help me out here >.< :crying:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
ashkineeeeee said:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
Click to expand...
Click to collapse
Yes I tried to enable debugging still did not work... I can not flash it because it doesn't get recognized by any computer.
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
john99ap said:
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
Click to expand...
Click to collapse
I tried already the root app simply keeps trashing no matter what-
dionex2k said:
I installed some CyanogenMod on my tablet and now every time I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have Samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile Odin(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically it's useless and I do now know what do to... Please, someone just help me out here >.<: crying:
Click to expand...
Click to collapse
Basically, because what you get is a CyanogenMod, which does not relate to any piece of the Samsung Driver. All you need is Google USB Driver which supports almost all Android phones in the world. A thread in XDA talks about 15 seconds Google USB Driver Program for Windows which can be found somewhere in the XDA thread world.
And more here, for the problem about root access, have you tried installing a SuperSu flashable zip through your recovery yet? That should work a lot. Then, if you update your firmware using recovery without using an OTA update manually, apps may not be compatible and will crash. Reinstalling all your crashing apps from the Google Play Store should help.
Finally, if you want to update your phone through recovery, not an OTA-received ROM, please make sure not to install many apps on it, because when it crashes, you can do nothing but to reinstall it. although, all add-ons (Such as GApps, SuperSu, Xposed Framework, et cetera) need to be reinstalled so you don't lose them during a manual update, so don't delete your flashable add-on zips once you installed, you might need them forever.
Recovery is like a mobile version of Odin, use a Desktop version of Odin so you can get yourself out. A tutorial might be found somewhere on YouTube.
Hope you have a good day,
Shippo
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
dionex2k said:
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
Click to expand...
Click to collapse
There is a tool called Forget Windows Use Linux in which all necessary drivers come preinstalled and your tab should be recognised from your pc with no problem if it's a driver issue. Try it
Try this slide down from upper left of the screen. If the window indicates charge only, click on it. It should then offer file transfer. In order to get adb to see the tablet turn on deveper options and enable USB debug mode. Hopefully that works for you.
hello
there is something very very very very very old which is called cf autoroot
every needed is in the zip use it
regards