Hello there everyone, I hope all are having a nice day.
I am asking here because I do not want to cause more "harm" than I already did. I rooted the tablet successfully and it is on Lollipop.. sadly. The whole reason I am doing this is to downgrad the version back to the original 4.4.2. I tried to install CWMR with rashr on my LG V400 and I ended up getting an error and CMWR not working. Thankfully it booted inside the system normally after, so I thought that be best would be to use Flashify's backed up recovery. After doing so, flashify restarted the tablet. Ever since it will just boot in recovery mode and no matter what won't boot normally. I do not know what to do.
-Edit-
After using the [HOW-TO] The easiest way to unbrick your LG G Pad 8.3 guide, I managed to restore the tablet to it's normal condition and the bootloop stopped. I am sorry for creating an extra thread before trying to look in various threads first, but when panicked I did not think to calmly first look. Thanks for everyone on here for all the helpful threads you provide for many many many years
Thank you for starting the thread. It is often difficult to find the needed thread and your's it what came up with a search. It was what I needed to fix the boot loop problem with my v400 tablet. Again, THANK YOU!!
SciFiJim said:
Thank you for starting the thread. It is often difficult to find the needed thread and your's it what came up with a search. It was what I needed to fix the boot loop problem with my v400 tablet. Again, THANK YOU!!
i have the same problem . it problem is the tablet not put download mode . power in but only fastboot mode
Click to expand...
Click to collapse
Related
Hey guys,
Long time reader and flasher, first time poster.
I just recently made a huge mistake (lack of sleep) and loaded Android Revolution HD for i9500 on my i9305.
I don't know what I was thinking, like I said lack of sleep. Anyway I went through with the process and got to a prompt asking to install SuperUser from the Recovery after Android Revolution successfully installed.
The device then rebooted and has been stuck at the Downloading... screen, I have tried rebooting into Recovery mode, it just goes to the same screen. I can boot into odin mode.
I have tried using heimdall to flash the recovery with something else. But I keep getting the following error: ERROR: Protocol initialisation failed!
I'm having a stab in the dark but I am guessing I have stuffed the partition tables or lost the IMEI.
I have done about 3 hours googling and searching theses forums and can't find an answer.
I have given up and was hoping someone could help me.
P.s. I'm running Ubuntu on my PC and do not have access to a windows or mac system.
Thanks for your help in advance!
Delete
Please Delete, I have fixed the problem.
I have no idea why it all of a sudden worked... but it did yay!
Thanks in advance
Does it boot into download mode?
Thats good, i was just going to say that if you can get into download mode then you should be able to flash the stock rom back
Hello everyone,
I tried looking for a solution to this problem, but either can't understand the suggestions or it doesn't really fit with my situation...
For some reason I managed to soft brick my TF701, trying to go back to stock after a CM install.
Anyways, I get stuck on the ASUS logo. I can access fastboot buf if I select RCK I get an error message. I can also connect in APX.
Any ideas on how I could flash a ROM on this device?
Many thanks in advance and sorry if there was an answer somewhere I missed...
I feel a bit ashamed now, I actually found a solution on my own and it wasn't that hard...
My main issue was not being able to access recovery. So I ended up doing the recommended steps here :
http://forum.xda-developers.com/showthread.php?t=2425581
up to the flash part and instead flashed this version of CWM
http://droidbasement.com/db-blog/?p=3568
This actually got me a working recovery, which I used to successfully flash a rom and my tablet is running again, as well as recovery mode.
Sorry for the thread, I could have managed on my own. If there's a way to delete it?
Hey people, I have been on this forum and using the CM12.1 ROM by New Maclaw since it came out, but I'm afraid my S3 Mini is dead now Saturday night it turned off by itself while charging, and it wouldn't turn on again. I let it charge a little, and after a while it turned on again, but was stuck on the CM12.1 boot animation. I tried rebooting multiple times, but it always got stuck on the boot animation. I tried booting into TWRP, but it got stuck on the Galaxy SIII Mini splash screen and wouldn't even go any further.
I was getting my hopes up when I saw download modus still working, so I flashed TWRP again with Odin, but nothing changed. I flashed the entire CM12.1 package again with Odin, but it had no effect whatsoever, can't boot into TWRP and regular boot is stuck on CM boot logo.
Since I had no options left, I decided to follow this guide: [GUIDE] Unroot / Unbrick, Flash official stock firmware on Galaxy SIII Mini GT-I8190 to flash original ROM again, first flashing the original recovery as linked in the thread, then the ROM itself, and checking after each step if anything changed. But even after I flashed the stock ROM, it would show the CM 12.1 boot animation on boot, and recovery was still not working at all. I continued by flashing the params.tar as linked in the post, but my phone still shows the CM 12.1 boot animation, and I can't get any further
What's really concerning to me is the fact that all the flash operations via Odin are going through, I get a PASS every time, but it doesn't seem to have any effect, so I'm afraid the memory chip on my phone has died There are so many great minds in here that know everything about this phone, maybe someone has an idea to help me get my trusted S3 mini back
Super weird. It's not soft bricked, it's completely f#cked up:laugh: OK, have you tried to remove the battery for some minutes!? Or go in recovery through adb instead!? If you have a backup (that's why, we always need a backup) maybe you can restore it through adb. Search on XDA for adb tutorials or something like that or some case like yours. I want to believe that you're not the first one with that issue. I know that's frustrating when we don't know what's going on. Good luck
mauam said:
Super weird. It's not soft bricked, it's completely f#cked up:laugh: OK, have you tried to remove the battery for some minutes!? Or go in recovery through adb instead!? If you have a backup (that's why, we always need a backup) maybe you can restore it through adb. Search on XDA for adb tutorials or something like that or some case like yours. I want to believe that you're not the first one with that issue. I know that's frustrating when we don't know what's going on. Good luck
Click to expand...
Click to collapse
I don't really care about backups, all my important data is on the SD anyway, I just want to bring the phone back to life if possible at all.
While on the CM12.1 boot screen I can find the phone with adb, but since I never set up adb my computer is unauthorized, and I can't authorize it without being able to boot. I'm not all that familiar with adb, I asked some people, but nobody has an idea how I can authorize my computer without having access to the phone system.
I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.
It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result
Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.
Edit:
Finally installed Magisk for root... Issue closed.
help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me
amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader
I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again
Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below
Hello, first of all sorry for my lack of tech knowledge.
So, I rooted my phone and tried to use Magisk for Gcam. Could not make it work so I was going to unroot my phone and started by unistalling magisk.
When I did it, it went to restart and I got the "no command" massage. By reading articles I first went to factory reset. I didn't work.
Later I tried Installing the TWRP, firstly it got me a black screen, but now I used adb to try to get to fastboot again to unistall it got stuck with a Android One logo freeze and I can't get to the fastboot.
No idea on what to do.
Edit: got to fastboot again by pressing power and vol down for a couple of seconds
A guy on Reddit solved it. All I had to do was to flash the stock boot.img I had before the root. I tried a couple until It was the right one and my phone resurrected.
FOR OTHER USERS WITH THE SAME PROBLEM: IF YOU GET "NO COMMAND" AFTER UNROOTING WITH MAGISK : flash the stock boot.img
If you are bricked with magisk then dont waste your time on flashing via fastboot sideload because nothing can unbrick.
The only way to recover your phone is via EDL mode ,
Search in the fourm and go through test point , your phone will be alive .
luizfernandosc said:
I tried a couple until It was the right one
Click to expand...
Click to collapse
This is probably one of the reasons why you bricked it in the first place. Don't just "try some", but read the forum over and over again until you're 100% sure you flash the right thing (rom, recovery, boot,..) for your particular phone version from the first time!
You were lucky to be able to resurrect it now, but flashing wrong things doesn't always give you that second chance!
That being said, rooting your phone with magisk and getting gcam to work is pretty easy, if you find the right tutorial for your specific device and follow their steps.