Dear Community,
I am a real noob when it comes to Android, flashing ROM, root and so on.
I got a Oneplus here where supposedly root rights are on it and another ROM.
Current problem, as soon as I turn it on it hangs when booting. (Bootloop - red dot with 2 running white dots)
I already tried it with power + volume+. Unfortunately unsuccessful.
Is it correct when I press Power + Volume- that you get into fastboot?
I can't get into the recovery mode either.
I would like to get the device running, but without root rights, OEM lock and the Oxygen OS from Oneplus.
So far my attempts to get it running have been unsuccessful.
Update: after 4h in the bootloop, it booted successfully. *yeah*
So how i can see, if the phone is rooted and how can i lock it?
I tried it with adb, i can find the phone with adb devices.
Then adb reboot fastboot, after that i tried to find it with fastboot devices but then he finds nothing more. the drivers are installed. also fastboot oem lock doesnt work, because the phone is not found.
Related
***
SO I AM RENDERING THIS NEXUS 5 DEAD (BRICKED FOREVER)
***
My daughter was using this Nexus 5 device and the power button started causing her problems.
Well I removed the power button and ordered a new one. So now the power button is not an issue.
But I guess during the time that the phone constantly kept rebooting due to the bad power button, something got corrupt.
Now the device gets to the boot animation and never goes any further.
There are no options in recovery for me to use.
I have working ADB and Fastboot on my PC. I can see the device with Fastboot but not ADB because I can't get the device to boot into the OS for me to enable USB debug.
But I know ADB works because I used it just the other day on a Galaxy S5.
I have tried to run fastboot oem unlock, it unlocks the device then once you reboot the boot loader, it says locked again.
I have tried using Nexus Root Toolkit and hit unlock and it unlocks then says the phone will reset itself and just be patient. It may appear to bootloop but just wait.
I waited for an hour and still just sits at the boot animation.
What are my options without being able to enable USB debug since the device will not boot to the OS?
I am able to Temporarily boot to a custom recovery, but I can't mount data!!!
With Temporary TWRP, I am able to use ADB and I get a success message when I push a new system image to it, and when I push twrp recovery to it, but when the phone reboots, I find out that neither the system image or recovery were actually installed.
I looked into bad partitions, tried some fixes, and nothing works. I am so far beyond frustrated with this thing. I guess I will wait one more day to see if anyone else has any other ideas for me to try, then I am just going to put it in the trash.
- Bootloop
- Bootloader doesn't stay unlocked
- Unable to mount storage
- USB Debugging is not enabled and can't be enabled
- Can't install OS image
- Can't install Recovery
- Can run TWRP temporary
- Can use ADB when TWRP Temporary is running, still can't mount anything
Hello, I'm new here. I have rooted my new fire 7in 5th gen tablet. I used the flashfire beta app to flash a rom which I found out that the rom had bugs, so I decided to install cm12.1 using the same app, but the app glitch when it started installing the rom meaning it didn't finish and kept installing. I decided to power it down and reboot it back up. It showed the cyanogemod logo booting with animation but nothing booted up. It kept booting like a bootloop. I restarted it multiple times and the same errors keep happening. I tried go into recovery mode by holding the volume up + power button at the same time when i was boot it up. it only went to amazon logo and not recovery. I also plugged in the device to the computer using my factory cable to see if I'm able to enter fastboot mode. It worked, but it wouldn't allow me to flash anything. The tablet greeted me a message saying flash not allow, but the commands were able communicate with fast-boot and cant get it into adb because the boot loop. I had actually enter fastboot mode using commands which worked. Sometimes when i type a different command it said failed remote. Some commands actually worked but I don't what other commands to use to fix it. It has been 10 months since this happened to me. I'm not willing to give up on it because their has to be alternative ways of bypassing these issues. Is their any way you guys can tell me how to fix this? Thank you.
Afternoon
I have a Lenovo 7" tablet which is sticking on boot...to describe:
tablet off, charge screen working fine (green battery)
can get into menu to select fastboot mode or recovery
fastboot works, at least screen appears!
recovery shows dead android/no command screen - how to access recovery?
booting up, get inital orange logo then a 'bing' and start of boot but then freezes on the second logo
tablet not visible on PC, even in fastboot mode (have installed drivers)
I'm looking to get this going but am a bit stumped. I tried reinstalling firmware but can't get SPF Tools to work with any available scatter files; I would like to install TWRP (I found a potential image file on XDA) but can't do this until the PC recognises it....and I'm going round in circles now....any suggestions gratefully received. :good:
Update
OK, post was maybe a bit premature - I've kinda fixed my issues.
Managed to get into recovery after watching many videos (most of which were wrong, but hey-ho, got me on the right path!). At dead android screen, press and hold in power + vol up + vol down together (there is a bit of knack, turn it on its side with buttons facing up seems to be easiest) - this fires up the recovery screen (android standard recovery).
I managed to get over my bootloop issue by performing a data wipe/factory reset and cache wipe, then restarted fine.
As this was a secondhand tablet (my usual purchases - good condition bootloops!) - once it booted up I got into the set-up screens only to discover a Google lock issue. I ran the FRP unlock from here: https://androidfilehost.com/?fid=11050483647474832839 using the instructions from here: http://forum.gsmhosting.com/vbb/f958/lenovo-tab-4-7-essential-tb4-7304f-frp-remove-2322527/ (Voltrans second post, not the original one which has a 404 error on the download site). This removed the FRP lock straight off and now I have a functioning tablet.
I'm probably going to try getting custom recovery on so will see how that goes - I'll post back
and...that's all folks....
OK, despite finding a TWRP recovery online https://twrpbuilder.github.io/downloads/twrp/#441 and downloading it, can I get the fastboot unlocked? no.
Apparently Lenovo locked them all up and threw away the key, so nothing more can be done here.
I tried various iterations of fastboot oem unlock and fastboot flashing unlock, and nothing works, just get an error - and yes, I did put developer options on, OEM unlocking ticked and USB debugging active.... :silly:
So, unless someone can point me in a direction on how to unlock it - I've reached the end of the road with this one
Hello. H830 owner, unlocked, rooted with Magisk, TWRP installed with 30C stock ROM. Today I got a notification to upgrade the Magisk Manager app, which I did. After installing and starting MM, it showed a Magisk update available - I clicked install and specified direct install (like I have many times before). The phone rebooted and I believe got to the T-Mobile splash screen then went into a loop with the apostophe triangle page "Your device software cannot be checked for corruption. Lock the bootloader"...
The only two things I can do are: 1) Pull the battery to power it off, and 2) hold down vol up +vol dn+power to get the IMEI barcode screen. Normal methods of booting into recovery do nothing. Attached it to PC and ran ADB devices and nothing shows up, so trying to run ADB reboot or ADB reboot bootloader yields "error: device '(null)' not found".
This seems bad. I have multipled devices rooted and with custom ROMs and recoveries and I've never seen anything like this. Since this phone is running stock Oreo, I never really need to do much other than perhaps an occasional TWRP backup. The phone has been pretty much flawless, until this Magisk upgrade attempt.
Anyone have any insights or solutions? I don't know what to try next.
did you solved the problem?
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
It's always risky to apply mods.
To get rid off of all mods you applied re-flash tablet's Stock ROM.
If this doesn't work for you then take it to authorized service center and let them try to fix it.
jwoegerbauer said:
take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
They never fix anything. The only thing they do is charge you an absurd price and replace the motherboard or the entire tablet.
I'm on the same boat. Tablet can't get into download mode, just shows "This device has unauthorized software on it and is locked". Tried all possible button combinations to no avail.
SmiffyJ said:
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
I have the exact same problem, did you manage to recover the tab?
Thanks heaps