Hi guys.
Im caught on a very difficult situation.
My Phone an HTC ONE X (Evita) is stuck in bootloader and has no OS. I have a recovery installed (TWRP 2.6.3.0) and Im able to access it BUT when I mount the sd card my PC is unable to recognize it. Its a Win 7 64 bit OS with the HTC 4.2.0.001 driver installed, It has worked fine in the past, I have adb and bootloader drivers installed and still unable to detect it VIA fastboot.
The error I get is USB Device Not Recognized.
I have no way of flashing a new rom since I cant even access my phones storage.
Here are the details of my Phone.
****TAMPERED****
****UNLOCKED****
EVITA PVT SHIP S-OFF RL
CID-1111111
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
AND Yes I didn't knew and did a factory reset VIA Bootloader.
That ****ed up my storage BUT I was able to fix that and Im able to mount ir VIA Recovery, Still mine and a friends win 7 PC get the USB Not Recognized Error.
So what options do I have??
Hope U guys can Help me.
Wrong forum mate.need to go to htc one xl forum.
khairulez said:
Wrong forum mate.need to go to htc one xl forum.
Click to expand...
Click to collapse
I know dude, it was originally posted there, but an admin moved my tread for somw unknown reasson :/
DillingerErick said:
Hi guys.
Im caught on a very difficult situation.
My Phone an HTC ONE X (Evita) is stuck in bootloader and has no OS. I have a recovery installed (TWRP 2.6.3.0) and Im able to access it BUT when I mount the sd card my PC is unable to recognize it. Its a Win 7 64 bit OS with the HTC 4.2.0.001 driver installed, It has worked fine in the past, I have adb and bootloader drivers installed and still unable to detect it VIA fastboot.
The error I get is USB Device Not Recognized.
I have no way of flashing a new rom since I cant even access my phones storage.
Here are the details of my Phone.
****TAMPERED****
****UNLOCKED****
EVITA PVT SHIP S-OFF RL
CID-1111111
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
AND Yes I didn't knew and did a factory reset VIA Bootloader.
That ****ed up my storage BUT I was able to fix that and Im able to mount ir VIA Recovery, Still mine and a friends win 7 PC get the USB Not Recognized Error.
So what options do I have??
Hope U guys can Help me.
Click to expand...
Click to collapse
Hey bro, it was happened with one of my frnds nxs7 , and on our research somehow partition were being deleted due too which now there is no system partition nor for memory. Srry bro but emmc chip had been destroy... Discuss it with recognized dev. If they can help u again in creating partitions may b it would wrk. Bst of luck
veer.killerboy said:
Hey bro, it was happened with one of my frnds nxs7 , and on our research somehow partition were being deleted due too which now there is no system partition nor for memory. Srry bro but emmc chip had been destroy... Discuss it with recognized dev. If they can help u again in creating partitions may b it would wrk. Bst of luck
Click to expand...
Click to collapse
Thanks bro, Ill Give that a try, Im going to start looking for a new phone in the meantime u_u
DillingerErick said:
Thanks bro, Ill Give that a try, Im going to start looking for a new phone in the meantime u_u
Click to expand...
Click to collapse
what do you mean by not recognized? can't find phone storage in windows explorer when connected? that's normal (or at least was) when being in recovery. you need to use "adb sideload rom.zip" to copy a rom onto your phone and install it. don't forget to flash the boot.img in fastboot too. make sure the rom is made for your device!
reaper90 said:
what do you mean by not recognized? can't find phone storage in windows explorer when connected? that's normal (or at least was) when being in recovery. you need to use "adb sideload rom.zip" to copy a rom onto your phone and install it. don't forget to flash the boot.img in fastboot too. make sure the rom is made for your device!
Click to expand...
Click to collapse
Ive already tried adbsideload and I get a "device not found" message.
And yeah, windows does not recognize my device, but I can access my storage via recovery and all seems to be fine there.
I get a USB not recognized message everytime I plug my phone in a computer, I ve tried several computers without success .
Thanks for Your help.
DillingerErick said:
Ive already tried adbsideload and I get a "device not found" message.
And yeah, windows does not recognize my device, but I can access my storage via recovery and all seems to be fine there.
I get a USB not recognized message everytime I plug my phone in a computer, I ve tried several computers without success .
Thanks for Your help.
Click to expand...
Click to collapse
it takes some time to recognize the phone, start adb with "adb devices" for example, then wait some minutes and try again
Try installing TWRP 2.8, it has better support to show it in windows.
Kinda off-topic, how did you manage to mount the SD card? I can't seem to be able to do that.
reaper90 said:
it takes some time to recognize the phone, start adb with "adb devices" for example, then wait some minutes and try again
Click to expand...
Click to collapse
Tanks for replying, I tried that already without success, also I tried restarting the adb server, same result on multiple win 7 64 bits PCs
I cant flash another recovery, my phone is not recognized by my PC o I dont have a way of copying twrp 2.8 to my sdcard and flash it.
I can access TWRP 2.7 and im able to mount the SD card, or at least the phone says that it mounted it, but its not recognized by my PC.
I can access my sd card on the phone via the recovery file explorer.
Related
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Help. I have a Superpad 8 Chinese tablet that will not boot.
At first, it would boot only as far as the "Andrtoid" boot animation and just hang there.
Then I started trying to restore a different ROm to it.
ADB sees it, and I was able to pull the /system directory from the tab.
After trying to flash a ROM to it using this "Livesuite" app I found, , which completed successfully, but since then, when the tab boots, it displays absolutely nothing.
ADB still sees it, but whatever command I send (adb reboot recovery or adb reboot bootloader), it just reboots and does nothing...
Can ANYBODY help, please?
I am still very new to ADB & troubleshooting Android, so I need all the help I can get!
Thanks in advance, and if you manage to get this tab working for me, I'll buy you a beer or 5...
skoop99 said:
Help. I have a Superpad 8 Chinese tablet that will not boot.
At first, it would boot only as far as the "Andrtoid" boot animation and just hang there.
Then I started trying to restore a different ROm to it.
ADB sees it, and I was able to pull the /system directory from the tab.
After trying to flash a ROM to it using this "Livesuite" app I found, , which completed successfully, but since then, when the tab boots, it displays absolutely nothing.
ADB still sees it, but whatever command I send (adb reboot recovery or adb reboot bootloader), it just reboots and does nothing...
Can ANYBODY help, please?
I am still very new to ADB & troubleshooting Android, so I need all the help I can get!
Thanks in advance, and if you manage to get this tab working for me, I'll buy you a beer or 5...
Click to expand...
Click to collapse
Is youre problem solved??
cejean said:
Is youre problem solved??
Click to expand...
Click to collapse
Hi Have the same problem if anyone can help Please. I'm still new to all this
same problem any ideas
any ideas to fit the problem?
Hello, I had a very similar problem which I had which might help with a BC1003 user.
first was the internal LCD cable came loose.. common problem...
Another was it would not boot at all. So I used Livesuit with "sun4i_crane_bc1003.img" dated August 2012... November 2012 did not work!.
It does appear to matter which .img file you use (unfortunately), because the WiFi does not work with the November version.
hi ... same tablet, some problem...
skoop99 said:
Help. I have a Superpad 8 Chinese tablet that will not boot.
hi ... same tablet, some problem...
after 3 days trying every possible firmware, and booting them from external sd card
all i could do was change de logo at boot start from (mapan to kosaco, to oem etc..)
than i had the idea of removing the internal sd card to look at it ...
and guess what it still runs the same with out no sd card in or out
so i thought ... the sd card was never read in the first place cause is damage or corrupted...
so on the 4th day im trying to format and partition the new internal sd card... hoping for the best.
by know u may not even have that tablet anymore but is food for thought for a next android promblems.
:good:
Click to expand...
Click to collapse
Hi everyone,
So I bought my friends HTC ONE X PLUS off him even though he had boot loop following a botched Custom ROM installation.
Stupidly I thought I could fix it.
It is an international device locked to O2. It loops at the HTC logo and allows boot into bootloader and CWM. The problem I have is that the PC doesnt even recognise it as a USB MASS (even after downloading the latest drivers - several times ) CWM wont even mount the storage.
Ive tried sideloading and everything else but no joy. The RUU I need to flash back to stock isnt out yet ? 1.17.206.1 and I cant ( as mentioned ) just dump an img/zip into the root as I cant get access to the storage. Its shows on the PC as removable storage but when I click it it asks me to insert a disk.
When I adb device/fastboot device it gives a number and says fastboot. ADB shows nothing in list of attached devices.
Any suggestions? If anyone in the UK would be happy for me to post it to them so they can have a go Id be happy to fund a beer or 2 in return
Thanks all.
mikejasonsmith said:
Hi everyone,
So I bought my friends HTC ONE X PLUS off him even though he had boot loop following a botched Custom ROM installation.
Stupidly I thought I could fix it.
It is an international device locked to O2. It loops at the HTC logo and allows boot into bootloader and CWM. The problem I have is that the PC doesnt even recognise it as a USB MASS (even after downloading the latest drivers - several times ) CWM wont even mount the storage.
Ive tried sideloading and everything else but no joy. The RUU I need to flash back to stock isnt out yet ? 1.17.206.1 and I cant ( as mentioned ) just dump an img/zip into the root as I cant get access to the storage. Its shows on the PC as removable storage but when I click it it asks me to insert a disk.
When I adb device/fastboot device it gives a number and says fastboot. ADB shows nothing in list of attached devices.
Any suggestions? If anyone in the UK would be happy for me to post it to them so they can have a go Id be happy to fund a beer or 2 in return
Thanks all.
Click to expand...
Click to collapse
The reason why the phone does not boot up anymore is that you friend probably forgot to flash the proper kernel/boot.img for the rom he installed. The kernal can't be flashed in recovery because the phone is still S-ON. In the HTC One X+ General forum you will find two tutorials with everything you need to know about unlocking/rooting/flashing using this phone. If you read both of them carefully, you should be able to solve your problem. Don't forget to press Thanks for the two guys who made these guides!!!
Also here you should be able to find the correct RUU for your CID. But since it needs relocked bootloader, you probably will have to read the to guides anyway and it is probably much easier to stay with unlocked bootloader and do the right flashing procedure.
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
combsco said:
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
Click to expand...
Click to collapse
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
.torrented said:
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
Click to expand...
Click to collapse
It made the file location, I'm waiting to see if it finishes copying it, as it's just sitting still at the moment.
Got it to work. Mods, you can delete this thread.
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.