I have a few Blackberry Privs to play around with atm. I have one that was exhibiting some unusual things before I flashed it, It seems like it was in some sort of test mode. I am not sure how to revert back to it, it seems like it was boot image AAC603 which allowed such testing to go on. sadly I didn't throw any Fastboot/ADB commands at it nor did I see if there was any diag ports open before I installed an OS on top of it. It doesn't seem to have an IMEI and now it just goes straight into bootloader mode.
if there was someway to get it back into testmode what commands should i throw at it ?
e.g. backup rom/partitions, "fix imei"
Is there a way to boot from the bootchain software backup version of the AAC603 ?
http://imgur.com/a/5gaqJ
How were you able to flash anything on this device? I know booting up still won't work, but maybe thisn could be helpful for eventual root access and flashing other ROMs?
Related
I installed TWRP bootloader onto my OEM Unlocked Samsung Galaxy Core Prime G360P Via Odin, and afterwords attempted to boot into Bootloader.
Upon doing so the phones screen goes black, and it acts like its turned off. My computer can't detect it with ADB, and I can't boot it back on without removing the battery and then inserting it again, after which it boots normally.
So yes my phone is working, but I need to get the bootloader working, I don't even have the normal android one right now because of this odd bug, i have rooted phones and tablets before both via Kingroot, and ADB depending on the needs of the device, and have some slight experience with it but limited technical knowledge, i have found seemingly similar problems but all said to solve via ADB, which doesnt really work as my ADB cant detect my phone when it is in this dead state it goes into instead of bootloader.
I would like a fix that will allow me to have TWRP installed, nothing that requires root as i have attempted all one-click rooters and none work for my phone, and i cannot install a custom OS as I am on textnow wireless and getting it to work with one is the biggest pain on earth (plus my calling would become sh^te without the custom textnow rom calling)
So basically i need to fix the bootloader without installing a new OS altogether, without deleting any of my inbuilt apps, and without factory resetting as I cant get to the bootloader to factory reset anyway, honestly i just need a way to get TWRP to work. If the answer involves another way of rooting my phone via Odin (yes i can still get to the odin downloader) and then running a root requiring app to fix my recovery thats fine but i dont know how to do that or what it would entail
im using: twrp-3.0.2-0-cprimeltemtr
Textnow wireless uses a custom os that is slightly modified from the default, I don't know what that entails but i know that affects what fixes may/may not work so i am mentioning it
before i get the same answers i have tried:
redownloading TWRP and flashing the new copy instead in case of corrupted image
removing the battery after flashing and then booting directly into bootloader so as to stop it restoring anything
I have tried flashing other recoverys, however upon doing so found that when i tried to boot into the bootloader it would then boot to Odin instead and give me an error saying it was unable to boot normally, so i reflashed the TWRP one and it gave me the same blackscreen once again.
Any advice would be very helpfull, im at my wits end and id like to be able to recover my phone should it have problems later, id much prefer i not get stuck
Software Version: G360PVPS2APE2
Hardware Version: G360P .03
Model #:SM-G360P
Android Version : 4.4.4
Android Security Patch Level: 2016-06-01
Kernel Version:2.10.28-675169
Build #: TNG360PVPS2APE2
SOLVED
http://forum.xda-developers.com/gal...ime-sm-g360p-root-t3217885/page2#post70113291
I found something that worked highly reccomend this autoinstaller for Odin
Search the forums for stock rooted deodexed sm-g360p, thats the TWRP that I use ... almost to much. The rom is also alot more susceptible to root,mods,and tweaks. The rom is sprint, boosts a sprint partner. Its helped me get the 4glte i couldnt pickup with the boost. But definitely find that post. Twrp isn't official to our variant(that i know yet) but it works the same tho a lil dated.
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
Hi all,
I'm just about at my wits end here. I have a Note 4 (N910W8) with a failed USB connection and I would really like to root it. The underlying goal is to remove/disable all samsung bloatware.
WRT the USB, I have tried adjusting developer options, *#0808#, updating drivers, changing cables, changing PC's, etc. I've tried everything I could find online. Recently, I took it to a local shop and learned that the problem is not with the USB port/board, but the motherboard itself. I'm not going to pay to replace it. I have googled far and wide. As far as I can tell, this phone will never again connect to a PC via USB. So, download mode and Odin are out.
I have tried TowelRoot, KingoRoot, and other apk's, but I am on Android 6.0.1 (MMB29M/GLW-N910W8VLS1DPK1) so all of these exploits have been patched.
I am able to boot into (stock) recovery mode, so I thought I'd try recovering via SD card, however that doesn't work either. First I get a loading screen of the mascot with a spinning wireframe polygon in his belly and the message "installing system update". Then after ~15 seconds, the mascot is on his back with a red warning symbol over his belly, and the text "No Command." is displayed. I'm not sure what that's all about, because I have the latest update installed.
Any attempts to install CF-Autoroot or another recovery firmware (ie https://samsung-firmware.org/model/SM-N910W8/region/GLW/ , or https://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538, etc) from SD (in recovery mode) have been met with the same error messages:
E:footer is wrong
E:signature verification failed
I'm not sure why because at least some of these recovery firmwares claim to be official builds. Granted, they are older versions (downgrades), but are signed nonetheless.
I have tried installing TWRP or CWM so I can disable signature verification, but AFAIK the device must already be rooted to install these (which seems like a bizarre catch-22, but maybe I'm confused) so that's a no-go.
It certainly feels like I have explored every possible avenue, but I have one remaining idea. Perhaps if the phone doesn't want to downgrade, I could force its hand by carefully soft-bricking the current rom in a controlled manner, then performing a recovery from SD with an official 4.4.4 KitKat build, and finally, using the towelroot/kingoroot/etc exploit to gain root access.
I mean, why else would there be a recover-from-SD option in the stock recovery menu? There must be a way to get it to accept a recovery build...
It's a last resort. But I'm willing to try it. The phone boots up, but is so bloated and laggy that it's practically unusable. Still. Am I missing anything? Surely there's some way to skip the USB / Odin method. What do you guys think? Is it time to go hulk on this thing? Is there any hope left? Curious to see how much further this rabbithole can go.
Cheers and thanks guys.
I've searched for ways to soft-brick, but have not come across anything. The bootloader appears to be locked, which is odd because I thought that only applied to Verizon variants.
I have recently downloaded an ADB/fastboot package for windows so I could attempt ADB over WiFi, however I can't establish a connection. I thought I'd do some more poking around on the phone side, so I installed some Wireless ADB apps. They all indicate a root is required, so I think that might be a dead end. I also connected to a ubuntu machine. Nothing. The phone charges, but both the PC and Ubuntu machine show zero signs of any connection at all.
There has to be some kind of SD-based solution to this. You can boot a computer from an SD card / USB stick and use that to access files (on an unencryped partition), and I'd be happy to do that here and delete those bloatware APK's directly... but I guess phones don't behave like other computers.
I've picked all the low hanging fruit. A part of me believes that there are some sneaky hacker ways to get at this without USB (ie some sort of rootkit) but that's way beyond my abilities. I'm going to take a break and attack this again once I have fresh ideas.
I'm in the same boat (busted usb port), does your phone still fast charge? Mine stopped fast charging.
I too have the same problem, except with the Note 10.1 2014. I know that is a different forum, but if you find a solution, it might be adaptable to my problem. I too have exhausted all other options as described above. Please someone, there must be a way to root via SD card instead of Odin. Help us please!
Me too. I have a Note Pro 12.1 running Lollipop. USB is busted and I've already replaced the port and ribbon, so it must be the motherboard. I mainly need it for Titanium backup, so I don't have to reinstall large games over my limited connection.
I have the same problem. Note 4 N910H. Not recognized by pc, stopped fast charging shows usb charging in battery settings. AFAIK I just re-rooted the phone before it went bust. There is no solution except changing the motherboard. Also this problem seems to be quite common.
I have had my Essential Phone for almost two years now and one day last week when I turned the phone on I saw the following error message.
You device is corrupt. It can't be trusted and may not work property.
Visit this link on another device:
gc.o/ABH
Press Power Key to Continue
There is a red exclamation point at the top that looks like this <!>. I contacted Essential Support and they told me the only way that message gets displayed is when someone has unlocked the bootloader at some point. I have never connected my phone to a USB cable for anything other then charging it with a power outlet and I have certainly never heard of ADB before this error occurred.
I would like to know how this error has happened if all I do is install a few apps from the Play Store and install OS updates when the are officially available OTA. Essential Support has said its my fault and will not help.
I tried to reset the phone back to factory settings several times. I have used the reset from within the Settings, I have used ADB to side-load the latest OTA OS from Essentials website and I have also tried some kind of flashing reset but no matter what I did I could not get this error to go away. These methods are described on the Essential site linked below.
Here is the link to Essentials website that I used. Since this is my first XDA post it will not let me post the whole URL. (essential.com/developer/current-builds)
I eventually ran the following command which did remove the error.
Code:
adb reboot "dm-verity enforcing"
From what I can tell this just prevents the error message from being displayed, correct? If the reason for the error is still there then what are my options? Should I worry about this error? Is it possible for me to reset the phone in someway to get this error message to go away and put the phone back into a secure and safe state? I don't care about any user data on the phone. The whole thing can be erased, which I think I have done sever times already trying to fix this.
Any suggestions would be greatly appreciated because beyond trying to fix this error I have no experience with ADB or modifying a phone in anyway.
Thanks,
-eric
Is there anyone who can offer help?
EricAndroid said:
Is there anyone who can offer help?
Click to expand...
Click to collapse
You can unlock your bootloader and unlock critical partitions than flash the latest bts (back to stock) from the link below. Make sure to read the directions and use a quality type c USB 3.0 or 3.1. you basically download the zip and unzip it, then run the flash-all-wipe.bat from fastboot mode. This will fix the actual problem. Good luck and make sure to ask in that thread if you get stuck.
Almost forgot, make sure to download the Essential Window's drivers(from thread below as well). You don't need to worry about setting up adb and fastboot because it's Automatic when you run the commands from the zip you download. Also make sure you first uninstall any instance of adb or fastboot that may already be on your computer.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .