Database Info

[Q] I can't install custom recovery. It just reboots.

Hi guys! I am stuck with a dilemma if I should format my phone. I am quite aware of the dev tools as an IT student but this is the first time I've experienced this problem:
First I stupidly installed Nexus 5's Ambient Display mod without making a backup of the apk's affected resulting for I guess maybe a coincidence but I cannot install the 5.01 OTA as when I went back to the original recovery, I get the green Android logo and "Error" under.
So I flashed via the flash-all.bat the 5.01 stock firmware from Google but removed the userdata.img as I don't want to lose any of my files. It worked seamlessly. No lags, no crashes, bootloops, nothing.
Now, my problem is I want to get the Ambient Display 5.01 to run again, but this time when I tried installing CWM/TWRP via fastboot, it says okay then when I select recovery, it goes back to the Google logo then it boots normally.
What do you guys think is the problem? Should I re-flash the whole firmware? BTW I was able to root my phone the other day. So I don't know what's up. Any suggestions would be great. Thanks!

Remove the scripts in the ROM that flash stock recovery on boot. Then, fastboot flash the recovery of your choice.
http://forum.xda-developers.com/google-nexus-5/help/flash-recovery-stuck-dead-android-t2978052

[SOLVED] Stuck in a bootloop/nothing has worked

Hello all!
I was running stock 5.1 rooted when I rebooted my phone and it got stuck in a bootloop. I've faced this with many Android phones so I wasnt concerned until I tried everything and still have yet to find a solution.
I have tried to fully flash the stock images, use Wugfresh's toolkit to return to stock, format system and data, and even try to go back to kiKat all without luck. The bootloop is still present.
I used the one-click unbrick tool that took me back to an early Kitkat build and the phone booted but everything kept crashing. Screenshots say they can't be saved which is weird.
I just want to get back to stock lollipop and I'm at a loss. Any help is appreciated!
EDIT: I followed the instructions here here and was able to repair my /persist partition.

babalonius508 said:
Hello all!
I was running stock 5.1 rooted when I rebooted my phone and it got stuck in a bootloop. I've faced this with many Android phones so I wasnt concerned until I tried everything and still have yet to find a solution.
I have tried to fully flash the stock images, use Wugfresh's toolkit to return to stock, format system and data, and even try to go back to kiKat all without luck. The bootloop is still present.
I used the one-click unbrick tool that took me back to an early Kitkat build and the phone booted but everything kept crashing. Screenshots say they can't be saved which is weird.
I just want to get back to stock lollipop and I'm at a loss. Any help is appreciated!
Click to expand...
Click to collapse
My advice if you already have not tried clean flash.
Download right factory image from https://developers.google.com/android/nexus/images and rund flash-all.bat. ( if adb is already installed, if not then install it also ) . If after flash you get again bootloop try to boot in recovery and wipe cache only.

Thanks for the response, Mairo. I tried that out and I'm still getting a bootloop. When I try and flash a zip in recovery or factory reset I get an error in mounting /persist and then the script will finish. I'm not sure if this will help diagnose the problem...

That was fast

Device won't boot, tried rayglobe, tried fastboot flash, no firmware downloads availa

I have an NXT-L29 (432). I've really loved this phone besides the headaches of modding. I've been doing this for years, am well acquainted with fastboot and ADB. I promised I've searched and read as much as I can, I keep getting dead ends.
I'll try to recount what I've done but I've tried so many things I'm probably a bit mixed up. Was using b180 and and Ephemeral Rom for months, decided to go to b321 for black pyramid. Trouble began. Tried dload method (button method wouldn't work,used dialer), it rebooted back to the custom rom. Went to recovery, still TWRP. Wiped, it booted into stock EMUI. Was still rooted, with kangtools somehow. Tried using supersu unroot, failed. Flashed stock recovery from bootloader hoping to update to nougat (gave up on b321), since then it won't boot and I can only get into bootloader and eRecovery. Tried downloading latest version and recovery, getting package fails. Tried reflashing TWRP in bootloader, shows success but brings me back to Erecovery. Tried rayglobe knife unbrick with extracted images from what I believe is my stock firmware. It completes, I press any key to reboot and get stuck on the 'your device is unlocked and can't be trusted' screen. I let it sit there overnight. Tried relocking bootloader but it can't because of root type. Tried manually flashing cust, boot, system, recovery, which is successful, yet I still get stuck at the 'your device has been unlocked and can't be trusted'. Tried using HRK tool but ADB isn't authorized? USB debugging was allowed before I got locked out. I'm stuck, don't know what else to do. I've thought to download another stock firmware but none of the links in the stock thread work anymore. Any help would be greatly appreciated.
One thing that is really racking my brain, why does Erecovery remain after fastboot flashing twrp?

Somehow got back into twrp, flashed 7.0 files and now running nougat. Cannot get back to twrp for the life of me and it doesn't always boot but it's progress. This phone is crazy.

Hello.
I unbricked my phone few. Weeks ago. Now it's fully fonctionnal. But I still can't boot to TWRP. The only manner I found, it's using srktool to reboot in TWRP... The official manner start erecovery too.

hi friend,have you problem....
help meeeee.
have flash a lot rom with fastboot unbrick
but no star sistem
have rom 192 emiui 4

Lenovo Tab 4 10 plus 30 second boot loop

How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?

I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.

pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/

SM-G610F Soft Brick happens after TWRP flash

Hello people,
I just tried flashing TWRP to my J7 Prime phone. Odin flash was successful and I could boot into recovery. I followed through normal procedure(data format and no-verity-opt-encrypt flashed). I did not flash any other zips and when i tried to boot back into System my phone didn't get through the Galaxy Prime logo. It wouldn't even show the boot animation. Before this happened, I did root my phone and everything was fine, I accidentally deleted google play once and also wanted to flash stock firmware so I did. After I flashed the stock firmware, when I wanted to root it again it would work after flashing magisk and booting into the system but after some time passes the apps one by one would begin to freeze and at last no app would even load. When i try to reboot at this point, the phone wouldn't boot back into the system anymore. It would get past the Samsung logo but the boot animation wouldn't even play as i was stuck in a black screen. I tried to restore with TWRP then, (Only restoring Boot, System and Data but I didn't wipe anything on the system before restoring. I think that this might be the issue but I just recently got into rooting.) but when i rebooted to use my phone it wouldn't get past the Samsung logo. The Samsung J7 Prime logo would show up, then 1-2 seconds pass and then reboot. This was a loop.
I was able to reflash stock firmware and get it to work normally. Since I can't risk bricking the phone as I can't get a new one after this experience I didn't flash anything again. Because after i restored with TWRP back then and now my phone bricking just because of a TWRP flash I think if I just give it some more tries (even with difference in procedure) it might just get hard bricked. I think flashing firmware so often might brick it. I really don't know but I can't risk bricking this phone.
The phone right now is OK. I just want to learn why this might happen, what would cause this and how to fix this. I will not flash anything because again I can't risk getting this phone bricked.
Just getting some information for me is enough as I am also curious about this problem,
Thank you.