Hi,
trying to root (trying to remove the pin) a clients x2 which contains important documents and information within sms messages.
device is stock and has never been rooted.
sitting on v2.3.4
cannot seem to find a way past permissions issues short of using some sort of hardware to dump /data directly from the chip.
cant dd through abd, trying any of the scripts wont work becuase usb debugging is not enabled.
any help is appreciated!
-J
Anybody?
I need to extract the mmssms.db somehow. nothing more than that really.
ideally, i would like to get root so that i can unlock the alpha pin/too many unlock attempts situation, but this would just be best case scenario.
this is my first delve into android forensics, and its very frustrating. everything i read requires usb debugging
any help or insight or if you'd like to vent your frustrations, would be appreciated!
jdigitL said:
Anybody?
I need to extract the mmssms.db somehow. nothing more than that really.
ideally, i would like to get root so that i can unlock the alpha pin/too many unlock attempts situation, but this would just be best case scenario.
this is my first delve into android forensics, and its very frustrating. everything i read requires usb debugging
any help or insight or if you'd like to vent your frustrations, would be appreciated!
Click to expand...
Click to collapse
in your case bud,from what i know,unless your already rooted,or you have a clockworkmod recovery alreaady installed,you really cant do what you need,theres a zip file which will flash and unlock the screen,but you need cmw,which you need root to get. sorry
can anyone recommend a data recovery center who uses a JTAG or similar to extract and disseminate device data for clients?
Related
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Hello all,
I am a total newbie with mobile technologies, but know my way around a linux-box alright.
I just got a Samsung Rugby Pro through an upgrade at ATT.
My goal is to run Ubuntu touch as my main OS. I know some people think this is a silly aim, but its my money, so for the sake of simplicity, can we just agree that it is a goal?
I have been doing every backflip I can find to root this thing. Or flash it. Or do whatever is necessary to enable fastboot via the linux terminal.
The adb install I have works just fine (i.e. it detects, can restart it, etc). I have tried messing with the 51/71/99 android.rules in udev many, many times. Fastboot will not recognize the device. I have loaded the device into the bootloader screen various ways (via adb, via volumedown+home+power before and after plugging it in) ; no luck.
I figured it may be because the phone isn't rooted. This has led for my current root quest.
Using linux, and not having current access to any other OS's, I haven't been able to use Odin, or any of the other (likely scan) knock-offs. I have heimdall installed, and for the bloody life of me, though it says its working, even when the phone is in boot-loader, it doesn't do anything once the b*stard restarts.
I have tried downloading what feels like a hundered update.zip scrips, cwm.zip's...etc, etc. No luck! Whenever I try to install the update from the SD, it says there is an error in verification. As far as I can tell, there isn't a way to do it during normal operation; not that that would particularly help.
I have also tried a zRoot application, and a host of others...most of which all require root access?
Perhaps this is a simple deficiency in my understanding of this whole process, but there seems to be a bit of a loop of which one is needed first; root or cwm. I am spinning round and round; my cat is looking at my chain smoking funny and my gf says I stink.
So here I come to you all. How the hell's this done? If anyone has successfully rooted the Rugby pro on linux, I would be eternally greatful for the help. If you know how to go all the way to ubuntu-touch, you will have a cat and a lovely lady also eternally greatful.
Please...help.
Hello I bought this product http://www.staples.com/Nobis-7-inch-8GB-Tablet/product_1052513
But I cant find anything to root it can anyone please help?
darkphate83 said:
Hello I bought this product http://www.staples.com/Nobis-7-inch-8GB-Tablet/product_1052513
But I cant find anything to root it can anyone please help?
Click to expand...
Click to collapse
As an alternative, is there a way to install CM-10 or CM-11 on it? (yeah, I expect if no developers have one here, it might be difficult to develop an image for it). For now I haven't needed to root it, as it's doing what I need for now, but if I want to start moving apps (or app data) off to a microSD card, I may need a root or CM1x version (and Google needs to be *smacked* for disabling SDcard functionality in later Android versions).
I have just purchased one of these NB7022S tablets from Staples as well. I have unsuccessfully been trying to root it for the last couple of days. Any help would be greatly appreciated
I have one of these Nobis NB7022s tablets as well, but the screen has been broken. So since the tablet isn't usable in it's current state, would it be of use to someone to do a teardown/analysis of the device in order to make a CyanogenMod port to it?
success
Just rooted the nb7022s using kingo root. First download the android software developer kit on your pc then open the sdk manager and download every possible update in order to have the correct drivers, not sure which one did the trick because i just downloaded everything. Then in your tablet go to settings-about tablet- then scroll down to build number and click 7 times to unlock developers options on the main settings screen. Go to developers options and turn it on and enable usb debugging. Plug tablet into your PC and install and run kingoroot. Should connect and root your tablet and automatically install superuser. Now I just need to figure out what version of clockworkmodrecovery to flash as recovery because this tabket does not have a supported cwmr, any help on that would be awesome because i dont want to brick my very first rooted device lol. Hopefully this info might help another newbie like myself.
thanks buzzdb666 for the tip on rooting. However, now every time I turn off the tablet and on, it always does a factory reset/wipe so I have to reinstall everything . Wondering if you've encountered the same thing?
Would be an interesting experiment to try, but again, the tablet has a broken screen, and I can't have a mouse *and* a connection to the computer at the same time. I had thought I could at least get the debug info from the tablet in case someone wants to develop an image for a non-broken unit. Once again, it's available if any XDA developers would like to use it for tear-down or testing, since I can't do much with it otherwise. Unless there's a way to extract what someone would need via a microSD card.
Mine is doing the same thing after using Kingo Root. Not sure what can be done since I can't go backwards now.
I am currently in communication with Alcatel's U.S. support (which may be outsourced, who knows?), and they have made it clear there is no OTU (OneTouchUpdate) available for the AT&T Alcatel Allura 5056O device. Their current advice is limited to performing a factory reset via the GUI, which of course isn't possible for a softbricked phone.
This means that as of this writing, there is no known way to restore this device from a softbrick.
I am explaining carefully the issue I and and a number of others here on XDA have experienced with this phone to Support, specifically asking for some method to reload the stock ROM, and will report any constructive suggestions they may have. But the OTU I made available at:
https://www.multcloud.com/share/0377ab37-15ed-4bcd-be3b-dbe8c7eb2cc8
...that lists the 5056 simply will not work on the 5056O.
Received this from the Contact Center:
The firmware is information that would only be available at the repair center. We would recommend you to perform a factory reset...
Click to expand...
Click to collapse
Still trying, but it isn't looking very good for those of us with softbricked 5056Os...
Yup I wanted to root the phone, so I did but then it bootlooped and it's bricked lol.
Haven't heard anything else from Alcatel's Customer "Support," so I've resent my questions to see if I can get some answers out of someone. There are enough of us affected by this issue that I'm not going to let them off quite so easily...
More bad news; the most recent reply from Alcatel CS:
At this moment it would be to send in the device into the repair center to get it repaired for you.
Click to expand...
Click to collapse
Clearly they are going to be less than helpful for those of us with the 5056O. Unless some kind soul here who has this phone is willing to image and post a copy of the Allura ROM, or someone knows a tech working for Alcatel who can supply the ROM, those of us with soft-bricked phones are completely screwed.
Am getting same info from Twitter CS...the ROM is only available inside their repair center.
(*sigh*) So unless someone else manages to liberate this device's ROM, guess we all might as well throw the devices in a drawer and move along. Just remember that the next time you're phone shopping, and bypass the Alcatel/TCL offerings.
Friends here I leave a link for you to download a copy I made to the Alcatel Allura 5056O, I did it through the flashfire application, I think if some advanced developer could work it, it would solve the problem we have. Https://mega.nz/#!01NDVR5K!rPPYEd87ndmg5Q9jmQ3qWjm1qGD3Rm7ge83yIsezSSQ
Excuse my bad English, I'm from Venezuela.
sanpuyon said:
Friends here I leave a link for you to download a copy I made to the Alcatel Allura 5056O
Click to expand...
Click to collapse
That is excellent, thank you very much!
Now let me make sure I understand; is this a copy of a softbricked ROM, or a functional one? Is it rooted or non-rooted?
CharlieSummers said:
That is excellent, thank you very much!
Now let me make sure I understand; is this a copy of a softbricked ROM, or a functional one? Is it rooted or non-rooted?
Click to expand...
Click to collapse
It is a copy of a functional rom, has root access and has modifications that I did before the device would damage me, but I have all my data in it.
sanpuyon said:
It is a copy of a functional rom, has root access and has modifications that I did before the device would damage me, but I have all my data in it.
Click to expand...
Click to collapse
So, if we can figure out how the Alcatel OTUs push the ROM to the phone, we might be able to get a softbricked phone to the point of performing a system reset...
Time to start reading up on how...
CharlieSummers said:
So, if we can figure out how the Alcatel OTUs push the ROM to the phone, we might be able to get a softbricked phone to the point of performing a system reset...
Time to start reading up on how...
Click to expand...
Click to collapse
The problem with my phone is that I made a modification to the build prop and upon restart I just showed the logo and then black screen, connect it to the adb and try to carry a custom recovery of a 6040A alcatel I had before and the result was that too Delete the recovery stock, now the phone when I connect it to adb appears to me as unauthorized, so I have not been able to repair it
sanpuyon said:
now the phone when I connect it to adb appears to me as unauthorized, so I have not been able to repair it
Click to expand...
Click to collapse
Keep trying. I've noticed that my 5056O does the same thing, but if I keep trying (restarting the phone, plugging in-and-out, etc.) I can eventually get adb devices to show it as "device" at which point I can acquire a shell, which can be SU'd.
Not guaranteeing this will work for you, but it has worked for me quite a few times so far. Beginning to think this phone is just magic, not science.
Just a quick bump to remind folks there are a bunch of soft-bricked 5056O phones out here in desperate search for a ROM...
Another bump to see if anyone has additional information on 5056O ROMs...hope springs eternal!
Still nothing, eh?
Hoping for someone with info on how to unbrick an Alcatel OneTouch Allura (5056O) - a stock ROM and means for recovery would be great!
Dear friends, after suffering for more than a year with my damaged phone, find a solution, I hope you can also solve it.
Here is a guide and the link to download the tool.
In the completely off phone will press the volume up and down keys at the same time and connect it to the pc so enter the download mode
1) Download the tool from this link https://mega.nz/#!NpkhnCoT!q5LxwJdWfIjcIY2tl99eGbhvRtrSY8bk-GQcDji7Rhs
2) Then unzip it install it on the pc
3) They execute it and they place the user and the password that he left in the attached note, when the update comes out they tell him not to
4) They look for the model of the team and they give to the option of flash and enjoy the magic
The only bad thing is that in the process the network release is lost
sanpuyon said:
Dear friends, after suffering for more than a year with my damaged phone, find a solution, I hope you can also solve it.
Click to expand...
Click to collapse
Um, last time I checked, the 5056O didn't have available ROMs outside AT&T. Is this the phone you repaired?
Also, latest version of SUGAR I found is v11.6.9R, which I placed in the MultCloud shared folder at https://www.multcloud.com/share/0377ab37-15ed-4bcd-be3b-dbe8c7eb2cc8 in the Misc folder. Same credentials as listed in the older README:
Region: All
Username: SU_IN.Panasonic
Password: KoD8naL2
Dongle authorization: unchecked
sanpuyon said:
The only bad thing is that in the process the network release is lost
Click to expand...
Click to collapse
My fault being unfamiliar with this stuff, but can you explain what was lost?
Oh, and I don't suppose this got you any closer to installing a custom recovery to root the phone?
does anyone have a link to the stock firmware? for an ALcatel onetouch Allura 5056O, I've been browsing the thread and seen none of the links provided for the stock firmware are all dead.
Better late than never: https://www.androidfilehost.com/?fid=10620683726822061932
I had hat on a HDD from a while back and never had a way to use it until I found edl. I'm currently flashing it now and I have no idea if it's gonna work or not. I don't think it will but who knows.
Also, its probably gonna take a few days or more to flash...
Edit: It failed at some point just a few hours in. Maybe it was just my device because I have disassembled it in the past looking for test points. I wish everyone else good luck.
So, I am currently having this Samsung Galaxy J2 TV (SM-J200BT, Android 5.1x) that I have been locked out for a couple of months now and I still have some important data there to be fetched out from the device, therefore leaving the factory reset option as the last resort. I have tried using Dr Fone and iMyFone but my device is not listed on their supported devices at the moment. I also have tried using ADB but unfortunately, USB debugging is disabled on the phone. At one point, I even have considered to apply the method which involves copy-pasting a long list of numbers and pasting it into the password field then crashing the lockscreen, but unfortunately again, the phone does not even allow me to copy nor paste anything while it is locked. I also have considered using the GSD tool to install the phone's boot.img file for this matter but the file that I have downloaded for my device seems to be unsupported or corrupt according to the software and carrying the next step into Odin just doesn't do anything either (TWRP included, since the 'galaxy j2lte' file was the closest one I could find).
The only possible solutions that I could think of, at least to some extent, that is still giving hope at the moment is to somehow find a roundabout method in activating USB debugging while the phone is locked or have a proper firmware/file that can help me succeed in installing into the phone and unlocking it using Odin or some other method, while at the same time, NOT LOSING ANY DATA. Any help or suggestion is widely appreciated, thanks in advance.
To access internal storage media ( userdata ) in case of a FRP lock phone's Android must be rooted and USB-Debugging must got enabled.
jwoegerbauer said:
To access internal storage media ( userdata ) in case of a FRP lock phone's Android must be rooted and USB-Debugging must got enabled.
Click to expand...
Click to collapse
It seems that I don't have much choices to select from here at the moment, do i?