First Sorry for my Bad Englisch. I am German.
I have brick my Tablet wth LCD Screen Resolution App
I Chance the Value, now on Boot the Homesceen crash.
I have make a Facory Reset, now the Tablet Say
OLS Terminated
Press ok
The Recovery will not work signed-nbx03_007-ota-120803058.zip
Erohibit update as a result of checking version or base sku
The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell do nothing.
4.0.3r1a
the _hack_recovery.zip tell me
assert failed: file_ getprop /system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2/THMAS11001/11001.003:user/release-keys"
file.getprop/system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys-keys
E:Error in /tmp/desklunvr/desklunvr.zip
status 7
I can not put the Device in USB MODE.
False recovery.zip?
adb devices say nothing in Recovery mode
Same problem
Koto99 said:
First Sorry for my Bad Englisch. I am German.
I have brick my Tablet wth LCD Screen Resolution App
Chance the Value now om Boot the Homesceen crash.
I have make a Facory Reset not the Tablet Say
OLS Terminated
Press ok
The Recovery will not work signed-nbx03_007-ota-120803058.zip
Erohibit update as a result of checking version or base sku
The ADB Shell on Sony AIO Tool not work. Option 6 Run Shell do nothing.
4.0.3r1a
the _hack_recovery.zip tell me
assert failed: file_ getprop /system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2/THMAS11001/11001.003:user/release-keys"
file.getprop/system/build.prop "ro.build.fingerprint" ="Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys-keys
E:Error in /tmp/desklunvr/desklunvr.zip
status 7
I can not put the Device in USB MODE.
Click to expand...
Click to collapse
I'm having the exact same problem after using FLASHER 2.1. Tablets gets stuck on the S.O.N.Y logo and I can enter the recovery screen, however no access through the USB to my files, already try the factory reset and still nothing. I would even consider installing the official firmware even if a lose root. I don't have the_hack_recovery.zip or any key. What can I do? I've been looking for solutions for over two days now.
I will appreciate any suggestions. :crying:
Now a have testes this
As long as your 'region.zip' file is not damaged, then for 99% your tab can be fixed.
Firstable try to flash this: 3.2.1r2 firmware
if not works, then try this:
signed-nbx03_016-ota-120803071.zip,
in fot works, then try this:
signed-nbx03_001-ota-120803002.zip
In most cases it works. If it will fail then:
1. Boot into RECOVERY;
2. Try to flash the update again - it will fail - thats ok;
3. Wait for 2-3min to get adb available;
4. Use 'adb pull /tmp';
5. Post your recovery.log and region.prop files.
http://forum.xda-developers.com/showthread.php?t=1515720
Hooray, Horray is a Glory Day (for me and i Hope your can this Help again)
The Flashing signed-nbx03_016-ota-120803071.zip will work vor me. Now i have 4.0.3 r1
The Link for http://info.update.sony.net/ST002/nbx03_001/contents/0016/signed-nbx03_001-ota-120803002.zip
are Down.
Dammed
Is it possibel to improve the Backup for future Times again?
Possibel to make a Backup that aways Restore the System if it fail`?
The LCD Screen Things can simpel Brick a Unit is dammed
I have Rootet an set up Boot Loop Protection. What do this Option without USB Debugging?
Please help me to improve the Recovery for the Future
$40 to the person that helps me fix my tablet S
Koto99 said:
Now a have testes this
As long as your 'region.zip' file is not damaged, then for 99% your tab can be fixed.
Firstable try to flash this: 3.2.1r2 firmware
if not works, then try this:
signed-nbx03_016-ota-120803071.zip,
in fot works, then try this:
signed-nbx03_001-ota-120803002.zip
In most cases it works. If it will fail then:
1. Boot into RECOVERY;
2. Try to flash the update again - it will fail - thats ok;
3. Wait for 2-3min to get adb available;
4. Use 'adb pull /tmp';
5. Post your recovery.log and region.prop files.
http://forum.xda-developers.com/showthread.php?t=1515720
Hooray, Horray is a Glory Day (for me and i Hope your can this Help again)
The Flashing signed-nbx03_016-ota-120803071.zip will work vor me. Now i have 4.0.3 r1
The Link for http://info.update.sony.net/ST002/nbx03_001/contents/0016/signed-nbx03_001-ota-120803002.zip
are Down.
Dammed
Is it possibel to improve the Backup for future Times again?
Possibel to make a Backup that aways Restore the System if it fail`?
The LCD Screen Things can simpel Brick a Unit is dammed
I have Rootet an set up Boot Loop Protection. What do this Option without USB Debugging?
Please help me to improve the Recovery for the Future
Click to expand...
Click to collapse
Hello Koto99
Thanks for your reply, I tried running the signed-nbx03_016-ota-120803071.zip and it didn't work, I'm looking everywhere for the signed-nbx03_001-ota-120803002.zip which should work for me, since my tablet was bought in the U.S. but it isn't available anywhere. I can't access the tablet through the ADB Shell, I press option 6 on the main menu and it does nothing. When I'm in the recovery mode I can see windows asking for drivers for a device named Sony, but none of the adb drivers work. If I go to the Sony logo I have it recognizes the MTP USB device and it looks ok for about 40 sec. and then it puts the yellow exclamation mark. I really need to get this tablet fix, I'm willing to donate $40.00 to the person that helps me restore it.
signed-nbx03_001-ota-120803002.zip.
Have you See the Cordi Mirror?
http://forum.xda-developers.com/showthread.php?t=1515720
First Cordi Posting down the Posting
Files mirror - My Google Drive
Good Luck
Koto99 said:
signed-nbx03_001-ota-120803002.zip.
Have you See the Cordi Mirror?
http://forum.xda-developers.com/showthread.php?t=1515720
First Cordi Posting down the Posting
Files mirror - My Google Drive
Good Luck
Click to expand...
Click to collapse
I also uploaded (not realizing condi had an upload).
he tried the file and it did not help him (so off to Sony it goes )
Stifilz
Help
Find attached my build prop and recovery. What files do I need to recover my bricked tablet.
Can you give me your build.prop (I mean the one in /system/) and can you enter the system at all?
Sent from my Sony Tablet S using xda premium
Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
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.
Hello,
I've got a LG L5 II that is stuck at LG screen. This happen because maybe I've deleted the update of google apps in order to have disk space left.
I've done a lot of research before posting a new thread but now, I ask for your help.
Useful Information :
LG L5 II E460, firmware stock, not rooted, firmware V10F
Try on USB 3.0 and USB 2 with cable microUSB -> USB because computer is an ASUS Transformer
Connection information in device manager :
Normal boot : MT65xx Android Phone
Download mode : LG AndroidNet Phone
Recovery mode : Android laying on the floor with red exclamation mark but nothing happen.
Guide used and results :
Official LG method :
Power on : when connected, still waiting for connection in the LG Update window
Download mode : Connection OK but when trying to upgrade from recovery, failed @ 4 or 5 %, phone disconnected
LG Flashtool 2014 :
Download mode : failed @ 4 or 5 %, phone disconnected
TOT Method: Unable to find TOT file but trying with bin and dll from kdz firmware
Download mode : Error at step flashing SCI.
If possible, I'd like to do a normal flash without losing data on the internal. I know I can do it but I need your help, please
If more information wanted, do not hesitate to ask, I'm trying to be the more accurate possible. Sorry for my English, it''s not my native language.
Thanks
I'm trying to get the tot file from my firmware KDZ.
Extracting KDZ give me DLL and bin file.
I don't know what to do with this bin file. Is it possible to convert it in tot file ?
Thanks
Midask said:
I'm trying to get the tot file from my firmware KDZ.
Extracting KDZ give me DLL and bin file.
I don't know what to do with this bin file. Is it possible to convert it in tot file ?
Thanks
Click to expand...
Click to collapse
any luck on recovering, im suffering the same. but i formated my system and now when i flash kdz the phone boots but goes to an android guy with a red triangle over its tummy
Hi !
I was hoping an answer but it isn't the case.
I'll try to help you, I've spent a lot of hours to recover my phone.
Try to follow this How-to :
http://forum.xda-developers.com/showthread.php?t=2409308
-----------------------
About my problem, I think I don't have any possibilities. Even a factory reset fail.
USB debugging not activated --> Trying by ADB --> ADB need to install Superuser.apk in /data/local/tmp --> This directory has been erased because I've tried a complete flash and all my data are gone but my phone is still bricked.
Trying to Root to flash recovery --> USB debugging not activated --> Unable to root my phone
KDZ Updater fail (maybe because of USB debugging not enabled ?)
I think I'm f**ed (sorry for this bad word but I don't see any possibilites ...)
----------
Dear mudster, if I can help you, I will do my best
Midask said:
Hi !
I was hoping an answer but it isn't the case.
I'll try to help you, I've spent a lot of hours to recover my phone.
Try to follow this How-to :
http://forum.xda-developers.com/showthread.php?t=2409308
-----------------------
About my problem, I think I don't have any possibilities. Even a factory reset fail.
USB debugging not activated --> Trying by ADB --> ADB need to install Superuser.apk in /data/local/tmp --> This directory has been erased because I've tried a complete flash and all my data are gone but my phone is still bricked.
Trying to Root to flash recovery --> USB debugging not activated --> Unable to root my phone
KDZ Updater fail (maybe because of USB debugging not enabled ?)
I think I'm f**ed (sorry for this bad word but I don't see any possibilites ...)
----------
Dear mudster, if I can help you, I will do my best
Click to expand...
Click to collapse
thanks bro we need more people like you in the world
I am going nuts. The recovery crashes at 4 - 5%
Hello my dear fellow community of XDA
I’m asking you for help, I found myself in a tough situation because I damaged system in tablet Nexus 9. Bootloader was already unlocked in my device when I bought it. I assume that the system was original. I didn’t notice any modifications. I damaged this system by uploading a file in a fastboot mode connected by ADB. This file is for rooting. I used this guide on the YouTube:
After doing everything step by step in this guide and switching my device on there was a sign of launching - vibration. The next thing I saw was white Google logo and after that the animation of loading appeared. It was loading without any success.
Before uploading the root file I also tried to upload TWRP file via ADB but it didn’t make any difference. After uploading TWRP files system launched properly, there is no new app in the app list and no combination of buttons such as power + volume that launches TWRP. Please tell me if I’m doing something wrong…
I tried to fix this bootloop by cleaning files via Hboot - factory reset but it didn’t change anything. I was searching for guides that would help me solve my problem but I couldn’t find anything useful. Each of them was old. They were from 2014 or 2015.
I would like to have a working tablet with TWRP, root and other unofficial system (you can give me some suggestions, I was thinking about Android 9). I don’t know where to start or what should I do first. Fix bootloop or upload TWRP ? What is correct order ? How to upload TWRP eligibly ? I rooted devices only several times so please excuse me, I am not a professional. I know that guide on YouTube mentioned before was for Android „L” not „N”.
Summary:
> Tablet Nexus 9 OP82100 WiFi version 32GB
> I use PC with Windows 10
> After connecting the tablet to the PC via USB cable in fastboot mode the tablet is visible in ADB console on the list of devices.
I hope that each information I gave you is clear enough. This is my first post on this forum. I hope somebody will find some minutes for reading this post. I’m counting on you. Thank you in advance for any help.
Ok, I honestly didn't read everything, but if you have and can access fastboot, flash TWRP, transfer a ROM to the internal memory, wipe data (not storage) and flash your ROM.
Try getting Wug's Nexus Root Toolkit, it's a graphical UI for adb and fastboot, might be a little friendlier for you.