Related
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Ssunyoto said:
Hi all,
When I am browsing market then decide to press the back or home button. Sometimes my phone will reboot for no reason, this happens maybe 3/5 times when I'm browsing market. I'm running the bionix rom with 1.3ghz Trinity kernel. This happened while I was running bionic with 1.2 ghz Trinity kernel.
Thanks!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Does it happen specifically with the market? Or does it also happen with other apps too? Also, are there any other common factors among your random reboots (the colloquial term for what you are referring to)? My best advice would be to wipe your dalvik cache, cache, and data and then reflash the rom and kernel. Restore your apps the long way and see if that solves your problem.
(the reason I'd recommend this is that it sounds like there is an issue with your flash and a clean flash might clear that up)
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Ssunyoto said:
Hey thanks for the fast reply, I actually went to clockwork and wipes every single option avaible except dalvick. Also it only seems to happen while closing or switching from market. I have not experienced the reboot during calls issue like other users. So if I do wipe Dalvick cache, does it uulnable root? Sorry, my first android phone here.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Its no problem man, everyone has "silly" questions when they start. =)
Basically, the Dalvik cache (found in advanced in Clockwork Recovery mod, aka CWM) is a list of things to boot. It speeds up the booting process but it also can cause issues during boot if there are conflicts between an old rom and a new one so wiping this is always good.
When you flash a new rom, you don't need to wipe everything, just wipe the Dalvik Cache (again found in the advanced section of CWM), Cache (found in mounts and storage and the actual action you'll be selecting will be "format cache"), and Data (found in mounts and storage and the actual action you'll be selecting will be "format data"). Once you do this flash your rom. Now if you're going to flash a kernel that you have never used before, I generally suggest allowing the phone to boot to make sure everything is fine, get myself all setup, to do a NANDroid backup before adding the kernel. That is my preference and is by no means necessary. Once you flash the kernel you can reboot and re-add your apps.
Now, I mentioned Titanium Backup and I'm still not sure you 100% know what that is so let me explain (as it is a very useful tool). It is a program that backs up your applications all with their data (IE preferences and the like). It does a great job (with the one exception that due to the way Android is built it cannot restore widgets) but it does require some work so it gets tedious when you have to use it a lot. I generally only use it the first time I'm flashing a new ROM. If you want to have a variety of roms you can easily access and switch between here is something I posted in another thread that can make it very, very easy to do:
kenvan19 said:
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).
Click to expand...
Click to collapse
I apologize for the huge wall of text but I hope it helps! Always remember that we're here to help you (as long as you search before you post a question, not applicable to this but it makes everyone's lives easier hehe)
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Ssunyoto said:
Woah thanks. I really don't mind not backing up haha. So I did what you said and wiped cache/data and dalvik but this time I used stock kernel with bionix. The problem I have now is that the rom manager bundled with bionix says I don't have clockwork installed and when I try to install from there, it just hangs and I have to force close, not a big deal but I can't even backup I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm. Try this: turn off your phone and then once its off hold the volume up button and then press the power. This should boot you into the bootloader. Now using the volume rocker to scroll and the power button to select, select recovery. Let it boot into that then tell me what color the text is in recovery.
Sent from my Nexus S
Fixed
Hey Kenvan,
Thanks for the help, I decided to revert back in to stock Android with no root and I have stopped having problems with anything! I also do not experience the rebooting during calls bug.
Thanks!
Hi,
My Xoom was encrypted. I did flash the Tiamat 2.1 Hammerhead via CWM. It is now keep rebooting, and I'm stuck without any backup.
Can someone please advise me what to do?
Damn sad now...
After reboot, Xoom as me for password, then it stuck keep rebooting. Damn... I did wipe in CWM also useless.
Hope someone can help me in this.
On the bright side there is no reason why this should not be fixable. First you said you tried to wipe in cwm. Try to wipe data/cache/dalvik-cache, which is in the advanced settings and then reflash the entire rom. If this does not work, I have more suggestions, so please reply.
Hi all,
I have a quick question, how come the max RAM shows only 768+MB? Isn't it supposed to be 1GB?
Also, Do I still need to run the SetCPU app to oc the speed to 1.7Ghz?
Thanks.
It is just like most devices were they have close to, but not exactly as much ram as advertised. The xoom has realisticly 768 megabytes of ram while a Full gig of ram is 1020 megabytes. Rounded the xoom is close enough to a full gig to be advertised that way. Like your phone, it probably says it has 512 megs of ram, but is somewhere around 312. Now to the CPU tuner question. Yes, to be over locked you have to use that app. The best setting for over all performance is to leave the minimum as low as possible, the maximum as high as possible, and the governor on interactive. If you set it to performance for to long your device will suffer CPU damage and you will have random reboots. So if you do not have CPU tuner your device runs at stock speeds.
Remember to thank me, it will help my family understand why I'm on here so much
Solution for encryption and Tiamat reboot loop problem
For all out there having the same problems as op, here is the solution which worked for me (ALL YOUR DATA GETS LOST OF COURSE!):
fastboot erase userdata
fastboot erase cache
in CWM do a "wipe data/factory reset" and now flash the Tiamat release you want to (should work on anything else, too).
Now your device is unencrypted again. Hope I could help
Works!!!!!
Lypsis said:
For all out there having the same problems as op, here is the solution which worked for me (ALL YOUR DATA GETS LOST OF COURSE!):
fastboot erase userdata
fastboot erase cache
in CWM do a "wipe data/factory reset" and now flash the Tiamat release you want to (should work on anything else, too).
Now your device is unencrypted again. Hope I could help
Click to expand...
Click to collapse
I worked for me thanks!!!!!!!!!!!!!!!
Xoom in reboot loop!!!! HELP!!!!
Hi, my Xoom was(?) rooted, installed Tiamat 2.2 on it, which then killed my 3G connection, as well as it was being unstable and would reboot often.... but I overwrote my backup, so it's screwed, and found a forum that told me how to flash back to original 3G image. I did everything there, but now my Xoom is in a constant reboot loop (showing the Honeycomb startup images) and I don't have root anymore because of it, and I can't even get my device to fully boot up....
I have the Samsung Nexus S, Unlocked using it on Tmobile.
I have the Gummy Crespo V0.7.2 rom
Mart1x kernal
l9020xxkl1 ?
on 4.0.3
did not over clock or anything.
My phone is literally rebooting every time i pick it up...I know this is happening to other phones too but i know that it is way too much for me to handle if it is happening like every two minutes.
please let me know what i can do?
U can try flashing a new kernel (just don't forget to wipe dalvik cache), if that won't work then u can try flashing another rom instead (before anything go into recovery mode - mounts & ... - usb .. so u could get your data from your phone or just perform a backup from recovery and transfer it to u're pc before modifications)
cheers
You need to use nstools or setcpu to raise your arm voltages by 25mv.
That will fix your reboot problems.
THank you! i have changed roms to CM9 and so far i have not seen any boots...if i see more then ill follow your advice.
thanks again
Hi,
I tried searching for an answer to this but couldn't find one so I'd thought I'd post it here. Whenever I flash a rom other then stock (like cm10 or paranoidandroid) the phone will go about a day or two then randomly reboot at many times during the day. It doesn't seem to be a full reboot but more of a hot boot. The bootloader is unlocked and I always wipe the device (including dalvik) before flashing a rom. If I manually reboot it will stop doing it on it's own but only last a day or two then begin again.
Any ideas? It's getting really frustrating especially when in a call or using an app for this to happen. Thanks!
wenzer said:
Hi,
I tried searching for an answer to this but couldn't find one so I'd thought I'd post it here. Whenever I flash a rom other then stock (like cm10 or paranoidandroid) the phone will go about a day or two then randomly reboot at many times during the day. It doesn't seem to be a full reboot but more of a hot boot. The bootloader is unlocked and I always wipe the device (including dalvik) before flashing a rom. If I manually reboot it will stop doing it on it's own but only last a day or two then begin again.
Any ideas? It's getting really frustrating especially when in a call or using an app for this to happen. Thanks!
Click to expand...
Click to collapse
What kernel are you using? Do you have your processor overclocked/Underclocked? Is it undervolted at all?
Sent from my Secret Base in Outer Space
I'm just using the basic kernel which came with paranoidandroid (or cm10 when trying that) and I do use SetCPU for the performance governor. Not overclocking per se.
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
ocstew said:
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
Click to expand...
Click to collapse
Download the latest stock firmware from asus, extract it once then flash it with twrp. But this could be unnecessary. You might wanna try flash _thats kernel and see if it shows any difference.
ocstew said:
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
Click to expand...
Click to collapse
You maybe selected your sleep mode with a 15 second in your system setting. You can go to your system setting and select display. Your sleep mode will pop up and pick a different time for your sleep mode..
JoinTheRealms said:
Download the latest stock firmware from asus, extract it once then flash it with twrp. But this could be unnecessary. You might wanna try flash _thats kernel and see if it shows any difference.
Click to expand...
Click to collapse
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
LetMeKnow said:
You maybe selected your sleep mode with a 15 second in your system setting. You can go to your system setting and select display. Your sleep mode will pop up and pick a different time for your sleep mode..
Click to expand...
Click to collapse
I don't think so, I'm actively touching the screen and then the tablet will be unresponsive and shut down.
ocstew said:
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
I don't think so, I'm actively touching the screen and then the tablet will be unresponsive and shut down.
Click to expand...
Click to collapse
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
ocstew said:
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
Click to expand...
Click to collapse
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
LetMeKnow said:
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
Click to expand...
Click to collapse
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
LetMeKnow said:
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
Click to expand...
Click to collapse
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
JoinTheRealms said:
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
Click to expand...
Click to collapse
No I didn't select that option. I suspect you're right. It always happens within a certain time interval, which is why I'm trying to completely erase everything on my tablet and start from stock. I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2223918
....And now it's been on "android is upgrading - starting apps" for 5 minutes now
ocstew said:
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
It always happens within a certain time interval.
Click to expand...
Click to collapse
Use the method i just posted to get back to stock, twrp's factory reset doesn't do that, it wipes /system and cache partitions to remove android completely.
JoinTheRealms said:
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
Click to expand...
Click to collapse
Thanks for the information. I am using the balance mode most of the time and it is max out around 51C. I think that I have a better luck than some people so far without any problem with Cromi X and Hund. About the throttle information on Hund's kerneI, I just want to mess around with it. I think that Hund sets it at level 0 onTegra_table0...
JoinTheRealms said:
Use the method i just posted to get back to stock, twrp's factory reset doesn't do that, it wipes /system and cache partitions to remove android completely.
Click to expand...
Click to collapse
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
ocstew said:
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
Click to expand...
Click to collapse
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Im assuming your in the US if so make sure you use the US version. Yes where people here might say "flash" they mean install. Flash is the terminology of writing data to ROM memory
ocstew said:
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
No I didn't select that option. I suspect you're right. It always happens within a certain time interval, which is why I'm trying to completely erase everything on my tablet and start from stock. I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2223918
....And now it's been on "android is upgrading - starting apps" for 5 minutes now
Click to expand...
Click to collapse
If you want to reset, you need to boot into the TWRP and select Wipe, then Advance Wipe. In Advance wipe, you need to check Dalvik, Cache, and Data to do a factory reset. I hope that helps.
Edit:
Do you have an external SD in your device?
LetMeKnow said:
If you want to reset, you need to boot into the TWRP and select Wipe, then Advance Wipe. In Advance wipe, you need to check Dalvik, Cache, and Data to do a factory reset. I hope that helps.
Edit:
Do you have an external SD in your device?
Click to expand...
Click to collapse
Yes I do. I think I did something stupid though, I flashed the ROM in the link using my external sdcard. It all worked fine until it stayed on "Starting Apps" for 5 minutes, at which I used the hardware reset buttons. My tablet cannot go beyond the spinning circle thingy and TWRP seems to have disappeared. My ignorance of Android is astounding haha :laugh:
I selected the "wipe" option when you hold down power and volume down. And it seems to have booted into the original start up screen, yay!
ocstew said:
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
Click to expand...
Click to collapse
I see absolutely no reason why you should flash the stock firmware. You'll just loose TWRP and root and have to start all over again.
Try this:
Put the your CROMI-X zip on a microSD.
Boot into TWRP and choose Wipe > Advanced > Format Data. This will erase your entire data partiton, so make sure everything is backed up.
Flash CROMI-X from the microSD. The Aroma installer will format your system partition before installing the new rom, wiping cache and Dalvik is the default selection as well.
Choose the stock kernel or _that's kernel for stability.
Oh, btw, what bootloader/recovery are you on? If you're not on 10.6.1.14.8 and TWRP 2.5/2.6, flash the package from the OP first, boot back into system, then proceed as described.
Sent from my DROID4 using Tapatalk 2
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
ocstew said:
Yes I do. I think I did something stupid though, I flashed the ROM in the link using my external sdcard. It all worked fine until it stayed on "Starting Apps" for 5 minutes, at which I used the hardware reset buttons. My tablet cannot go beyond the spinning circle thingy and TWRP seems to have disappeared. My ignorance of Android is astounding haha :laugh:
I selected the "wipe" option when you hold down power and volume down. And it seems to have booted into the original start up screen, yay!
Click to expand...
Click to collapse
Jeez! Just saw this! You chose Wipe Data from the bootloader menu?? Consider yourself lucky that you're not hard bricked! Slow down! Don't do anything else before you're sure what you're doing!
Sent from my DROID4 using Tapatalk 2
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
ocstew said:
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
Click to expand...
Click to collapse
I am glad that you got your tab working again.. :good: What berndblb said is correct. People have had brick their devices using Wipe from the bootlloader if their bootloader and custom recovery are not compatible. The good practice is not using it because when the bootloader is not working, you can do anything unless you can update the bootloader binary.
ocstew said:
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
Click to expand...
Click to collapse
Guys don't get paranoid about the Wipe Data option . That option caused bricks only when the users used a custom recovery which wasn't compatible with the device's bootloader. Using Wipe Data when no custom recovery is actually the only easy way to do a Factory Reset (especially for people on stock firmware and locked bootloader) and personally it also helped me repair a corrupted partition, so my advice is to read first and flash after.
Pretoriano80 said:
Guys don't get paranoid about the Wipe Data option . That option caused bricks only when the users used a custom recovery which wasn't compatible with the device's bootloader. Using Wipe Data when no custom recovery is actually the only easy way to do a Factory Reset (especially for people on stock firmware and locked bootloader) and personally it also helped me repair a corrupted partition, so my advice is to read first and flash after.
Click to expand...
Click to collapse
Best advice yet never be hasty when flashing stuffs. By the way im confused at how that would cause a soft brick? im not sure how or why it would affect fastboot access
JoinTheRealms said:
Best advice yet never be hasty when flashing stuffs. By the way im confused at how that would cause a soft brick? im not sure how or why it would affect fastboot access
Click to expand...
Click to collapse
AFAIK an incompatibility between a custom recovery and the bootloader was only causing a bootloop to recovery and also some corrupted partition, but the bootloader was ok. The bad part was that the user couldn't reach the fastboot mode anymore because the device always restarted to recovery (so no bootloader menu when pressing Volume Down + Power) but about two months ago _that managed to find a way to kick the device out of the recovery bootloop and once you did it you can recover the device just fine.
Pretoriano80 said:
AFAIK an incompatibility between a custom recovery and the bootloader was only causing a bootloop to recovery and also some corrupted partition, but the bootloader was ok. The bad part was that the user couldn't reach the fastboot mode anymore because the device always restarted to recovery (so no bootloader menu when pressing Volume Down + Power) but about two months ago _that managed to find a way to kick the device out of the recovery bootloop and once you did it you can recover the device just fine.
Click to expand...
Click to collapse
Note that this unbricking method *requires* a working rooted Android image, which the user whom I helped luckily still had. In other cases it is still a hard brick (because the recovery cannot access the eMMC so it is impossible to remove the reboot-to-recovery command or flash anything), so I recommend never using "wipe data" from the bootloader menu, or "install update" from within Android with a custom recovery.