it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
catcatjpg said:
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
Click to expand...
Click to collapse
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
aimsjahan said:
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
Click to expand...
Click to collapse
I do flash the custom recovery so I can flash the ROM. I never had an issue before but now I do even though I have done everything correctly.
How do I clear cashe partition and dalvik cashe? The rest of the steps I have done but have not worked unfortunately. even with the different roms.
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
nothings working so far guess ill stick with graphene until i get a new phone or a solution pops up
catcatjpg said:
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
Click to expand...
Click to collapse
To manually boot recovery on a custom rom just hold power button down , keep holding it down and once your screen goes black hold volume down till you are in bootloader/fastboot mode, then use volume to select recovery and hit power. That should get you in recovery on custom roms. Or you can plug in to a PC with adb and enable USB debugging and dev options on device, disable screen lock and type: sudo adb devices (for Linux ) and when the box pops up on your phone check mark it really quick. Now your device can have commands sent to it. If on a custom rom from cli type: sudo adb reboot recovery or sudo adb reboot bootloader then use volume keys to go to recovery and power to select it.
The best way to get out of a bootloop is hold power and volume down until you are in bootloader/aka fastboot mode then execute the ./flash-all.sh script that's in factory image and let it flash and wipe your device. You can always sideload a rom again but the factory image script will get everything to normal. There are tons of videos on YouTube about flashing device's. Everything changed a few years ago when Google started making android A/B partition devices but if you check out YouTube just do a quick search for whatever it is and more than likely you'll find what you're looking for there. Lots of pixel 6 videos!!!
Please explain your "exact " installation technique step by step. The more details the better the answers you'll get. What rom are you installing and exact steps you are doing to get in a boot loop.. While there are some highly intelligent people here nobody can read minds. Every detail helps to get a solution that works. Must be specific.. For me I rarely have issues but i don't flash nearly as often as I used to but when I have had a loop I hold power and volume down then from bootloader screen plug up to PC and I flash factory image using the flash-all.sh script that comes in factory image. Check out YouTube for visuals. Lots of good videos there.
This will hopefully provide more information on my situation
Currently I am trying to install RiceDroid for the pixel 6.
How I am in stalling it is I extract the images from the payload bin using a guide. Get the vendor boot image. Flash it with 'fastboot flash vendor_boot 'path/to/vendor_boot.img' then I try to boot into recovery which doesn't work it loads into the the warning screen then to the Google boot up screen but I never get to the Andriod 'no command' screen I only get taken back to the warning screen then back to the boot screen again untill I manually boot into bootloader again (power button and volume down) and flash my stock firmware.
Other Roms are not working for me either and it started happening after I tried to flash calyxOS and that failed. Now I can't even flash lineageOS or Evolution X rom only web flashing with GrapheneOS and Android Flash Tool can successfully flash my device.
im not sure what i did but things are working again
Related
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
Hello there
I've tried it for a while now: Getting a working recovery on Paranoid Android 6 (MM). As it seems, Marshmellow has some problems in general with rooting etc.
Back some time, i've had some troubles getting the Stock MM rootet and a working custom recovery installed. But with this thread, it worked: https://forum.xda-developers.com/xperia-z2/general/stock-t3355768
But on Paranoid Android, it bricked my phone. (Black screen and flashing LED)
So I tried:
https://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 (flashing the .zip and execute the .bat on Windows). No effect, can't boot into Recovery (either over the Volume buttons or the "reboot menu")
and then again a "modified" version of TWRP, but I can't find the thread to this anymore. However, this file took no effect too. I'd make an attachment with the file, but i can't as it seems.
Then I flashed the official TWRP .img from their webiste and the phone bricked again. The same happened with this: https://forum.xda-developers.com/xperia-z2/general/twrp-recovery-collection-t2999078
Now I'm on Stock again (and Bootloader locked ), but my goal is to get my phone google-free and as much opensource as possible. So, is it possible to get a working recovery on the newest Paranoid Android or do I have to downgrade back to PA 5? Or do you have a recommendation for another, more actual, Custom-Rom? I liked PA 4 and 5, so I'd like to install 6 too.
What did I miss in this mayhem of threads, scripts and files?
Thanks for the help
Try to flash by fastboot twrp 3.0.0 from rcstar6696, https://mega.nz/#F!TRRjgICI!D4WON2JY7Lunrx7W-LSaww!uVoB0TYL
Make sure you typed "fastboot flash recovery..." not "fastboot flash boot..." in cmd.
DiogoSilva48 said:
Try to flash by fastboot twrp 3.0.0 from rcstar6696, https://mega.nz/#F!TRRjgICI!D4WON2JY7Lunrx7W-LSaww!uVoB0TYL
Click to expand...
Click to collapse
Thanks for the answer, but unfortunately it doesn't work too. (I turned off the device. Hold Vol-Up, plugged the phone an ran the command: "fastboot flash recovery twrp-3.0.0-0-sirius.img". CMD says it's all okay)
The phone didn't brick, but i can't boot into TWRP. (May I ask, where you got this modified TWRP from?). The phone doesn't give me even the opportunity to press a volume-button. After the Sony Logo, AOSPA boots without a little vibration or flashing LED (like it did before on Stock or AOSPA 5). And if I try to "force" a reboot into recovery from the advanced reboot menu, the phone stays completely black and I've to wait some time, until I can turn it on again. (Happens too, if I press vol-up/down all the time)
I did some research and found some threads, which were about Custom-Kernels like "advanced kernel" or "DooMLoRD". Perhaps I have to do something with these? (example: https://forum.xda-developers.com/xperia-z2/development/kernel-advanced-stock-kernel-t3347413 )
I ask myself, why this doesn't work "out of the box". In AOSPA 5, there weren't any troubles. But since Marshmellow, custom ROMs and Stock-ROMs seem to have many problems (with customization).
Any Idea, why the official TWRP aren't running "out of the box"? Or why it only doesnt work for me, since it seems that I'm the only one with these problems.
EDIT:
I got it!!! I flashed the official TWRP 3.0.2-0 from their website via fastboot. With the advanced reboot menu from AOSPA i managed to boot into TWRP. (But i can't boot into it with the volume-buttons, which is kinda sad for a "recovery menu". Any ideas, how i manage to get this working? Because, if the phone doesn't boot anymore I can't access TWRP... :/
So I bought a stock Xperia Z5 Compact E5823 on which I want to use LinageOS. I managed to set up Cyanogenmod and, later, LinageOS on my previous two phones, but I am not very confident about what I am actually doing, so please excuse if I express myself unclear or if I lack basic understanding. My main problem is that I cannot access recovery mode, neither via volume-down + power-button, nor via ADB.
Phone info: Android version 5.1.1, Kernel version 3.10.49-perf-g6b847e2, Build no. 31.0.A.4.11 (do you need something else?)
I followed the LinageOS guide: https://wiki.lineageos.org/devices/suzuran/install but I fail to flash TWRP.
I unlocked the bootloader, I am able to access my phone using ADB (I'm on a Linux machine) and I can boot into fastboot mode. There I should be able to flash a TWRP recovery in order to flash LinageOS, but if I do, nothing changes.
At first I tried the newest TWRP version (3.2.1): https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050 - is this version even compatible?
When running fastboot flash recovery <twrp321-recovery.img>, it says target didn't report max-download-size (what does that mean?) and finishes without errors. However, booting to recovery is not working, the phone just boots normally.
When running fastboot boot <twrp321-recovery.img>, it says FAILED (remote: dtb not found) (what's "dtb"?)
Trying around with different TWRP versions, I found that version 2.8.something works for booting (fastboot boot recovery.img), so I end up in TWRP, but flashing this recovery still does not work, as above: Max-download-size note, no errors, no recovery mode, just normal boot.
I did several factory resets and tried to flash LinageOS using the booted recovery, but then it says something about missing partitions that I don't understand (I could do it again if this information is useful).
Generally: Shouldn't I be able to boot into recovery mode, irrespective of what I did? I did not try it before I started messing around, so I do not know if it had worked out of the box ...
Could I have accidentally messed up my recovery mode? Maybe when I tried to flash TWRP 3.2.1? If so, how do I revert this - how do I set up a working recovery? Do I need to erase/wipe anything specific? I fear bricking this phone ...
I also tried around with FlashTool (https://xperiafirmware.com/), trying to set up a new kernel, thinking that TWRP might need that, but I seem to be too unacquainted with Android OS architecture for this - actually, I do not even know what exactly a kernel is ...
Thank you very much in advance
Fred
fredduh said:
So I bought a stock Xperia Z5 Compact E5823 on which I want to use LinageOS. I managed to set up Cyanogenmod and, later, LinageOS on my previous two phones, but I am not very confident about what I am actually doing, so please excuse if I express myself unclear or if I lack basic understanding. My main problem is that I cannot access recovery mode, neither via volume-down + power-button, nor via ADB.
Phone info: Android version 5.1.1, Kernel version 3.10.49-perf-g6b847e2, Build no. 31.0.A.4.11 (do you need something else?)
I followed the LinageOS guide: https://wiki.lineageos.org/devices/suzuran/install but I fail to flash TWRP.
I unlocked the bootloader, I am able to access my phone using ADB (I'm on a Linux machine) and I can boot into fastboot mode. There I should be able to flash a TWRP recovery in order to flash LinageOS, but if I do, nothing changes.
At first I tried the newest TWRP version (3.2.1): https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050 - is this version even compatible?
When running fastboot flash recovery <twrp321-recovery.img>, it says target didn't report max-download-size (what does that mean?) and finishes without errors. However, booting to recovery is not working, the phone just boots normally.
When running fastboot boot <twrp321-recovery.img>, it says FAILED (remote: dtb not found) (what's "dtb"?)
Trying around with different TWRP versions, I found that version 2.8.something works for booting (fastboot boot recovery.img), so I end up in TWRP, but flashing this recovery still does not work, as above: Max-download-size note, no errors, no recovery mode, just normal boot.
I did several factory resets and tried to flash LinageOS using the booted recovery, but then it says something about missing partitions that I don't understand (I could do it again if this information is useful).
Generally: Shouldn't I be able to boot into recovery mode, irrespective of what I did? I did not try it before I started messing around, so I do not know if it had worked out of the box ...
Could I have accidentally messed up my recovery mode? Maybe when I tried to flash TWRP 3.2.1? If so, how do I revert this - how do I set up a working recovery? Do I need to erase/wipe anything specific? I fear bricking this phone ...
I also tried around with FlashTool (https://xperiafirmware.com/), trying to set up a new kernel, thinking that TWRP might need that, but I seem to be too unacquainted with Android OS architecture for this - actually, I do not even know what exactly a kernel is ...
Thank you very much in advance
Fred
Click to expand...
Click to collapse
Hi Fred,
while searching for a similar (or maybe the same) problem on my new Z5 compact I came across your post.
I was trying to install LineageOS and therefore started with TWRP 3.2.1 linked from the LineageOS installation manual(link)
It failed. Many times. The only workaround was booting to recovery mode with the phone booted to stock rom via:
Code:
adb reboot recovery
but NOT ONCE it worked with the given key combination. Trying to install LineageOS from that resulted in a completely unusable phone, not even showing the sony logo on boot.
What helped my was flashing the phone with the sony tool "emma" with the latest custom rom (for me 32.4.A.0.160). Whatever magic this does (firmware upgrade maybe), it brought my device back to live and now I can install and boot into TWRP recovery, installed LineageOS.
You can do so by
1 installing and starting emma, just follow screen instructions
2 activate developer mode (tapping on the build number 7 multiple time (under settings/about phone)
3 activate adb debugging under settings/developer settings and authorize phone
4 power off the phone
5 connect the phone to the pc
6 press and hold volume down button until the led becomes green
The device will appear in Emma and you can flash it back to life.
Let me know how it worked for you,
Frank
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
If anyone can help that'll be great!
Phone Info:
Android Version: 10
Baseband Version: J600GDXSACVB1
Knox version: Knox 3.5 (idk if this is needed)
"OEM Unlocking" option in developer setting is enabled
"USB Debugging" is also enabled
ThatUnknownDude said:
So uhm first time posting in XDA, and also first time rooting a phone in my life...
Anyways apparently twrp doesn't have an official custom recovery for the J6... and despite searching for the J600G (specificaly: J600GDXSACVB1), I was unable to find any proper website for my model (ive heard I need the exact file for my exact model)... maybe you guys know any twrp custom recovery for it....
Click to expand...
Click to collapse
TWRP =/= root. Root means you have SU access in Android system. Recovery mode is a separate environment; the difference between TWRP and stock recovery is that TWRP allows you to flash unsigned images.
If you just want to root your phone with Magisk, you can follow these instructions.
Otherwise, if you want to be able to flash custom ROMs, you can use this to patch your stock recovery to enable Fastbootd which will allow you to flash partitions directly instead of using Odin.
ThatUnknownDude said:
And after that... some are saying just flash magisk, some are saying I need to disable VaultKeeper to really unlock Bootloader to then root the device... so I am getting confused
Click to expand...
Click to collapse
Yes, see the Magisk instructions I linked. Samsung likes to make things complicated, so when you've unlocked the bootloader, it still won't let you flash custom images until Vaultkeeper has been disabled.
Hmm ok thanks.. I saw the Magisk installation help page and I am getting stuck in this part:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Click to expand...
Click to collapse
I am long pressing volume up button in download mode however nothing is happening...
(Edit) Oh and KG State (which I assume is another word for RMM Lock) is just showing 'checking' and not 'prenormal' or anything...
I think TWRP may be the cause of the bootloop. I flashed a stock firmware of J600G to completely reset it (factory reset of sorts) and then flashed TWRP, and entered the recovery screen. After that the bootlooping issue started... is there any other good custom recoveries?
Hi TUD, fellow J600G user here, I'd recommend you to start off easy by installing TWRP 3.2.3.
Requirements -
Odin installed on your computer.
USB cable
TWRP tar file
To install TWRP -
1. Switch your phone off and hold volume up and down buttons at the same time while connecting your phone to the computer by cable.
2. Open Odin and go to options, switch off auto reboot, now click on AP and select your TWRP tar file.
3. Now after Odin says PASS disconnect the cable from your phone and hold Volume down + power button for 7 seconds and as soon as the screen goes black hold Volume up + power button. This will boot you into your newly installed TWRP.
When it comes to custom roms J6 has some limitations for a few good ones. In my opinion you can install EvolutionX 4.0 (made by @adi_ss) that is based on android 10 as its the easiest rom to install. All you have to do is follow the instructions given by the developer.
Happy Flashing.