I ran into a problem before: but my solution ended up breaking my system more:
Old issue: https://forum.xda-developers.com/android/help/rooted-phone-root-apps-t3708044 - hoping this will help solve that also
what happened:
I went to Reflash my SuperSU.zip: with an updated version: via Sideload: which ended up failing at 78% and putting me in bootloop: So i went to do a Reset with my TWRP: i must have selected the wrong section because now it says i have no Android: Still in bootloop too:
My phone died since then and my TWRP recovery seemingly will not load up, perhaps i just haven't given it the time to, however i looked up a stock Rom to flash if i can get my TWRP running again
Question is: How can i FORCE it to load bootloader, even though it is in bootloop, So i can Reflash my TWRP then proceed to Flash my ROM with this Rom "BLOX2core" which the site says " - This is the ideal stock ROM for anyone wanting a thinned out version of stock. Comes pre-rooted, busybox installed, deodexed (to be able to theme and easy modding), and debloated like crazy. Comes with a Pixel style launcher, new boot animation, and sounds. Roughly HALF the size of the original stock. Simply flash the ROM and start modding the device to your liking."
EXT site i found rom is http://blox2.com/flashablelife-one-x2-stock-roms/
I really am only worried about it having BusyBox since i couldnt install busybox originally: I do doubt ill do much other modding on it, except a bootanimation possibly: but i digress.
The Questions:
How can i FORCE it to load bootloader, even though it is in bootloop?
From what i understand Flashing a rom replaces your operating system: is this right?
Is this possible?
if so: can i get at least a half-dummed tutorial?
(i dont need button Combos or the terminal commands IE Power + Vol Down or Fastboot flash recovery TWRP-recovery.img unless its a completely odd button/command that isnt normally used)
i didnt expect it to fail to update SU so I didnt use NanDroid before hand: I should have though
NOTE I am using Windows ADB not Linux because i do not have a Linux machine:
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.
Background:
Rooting and flashing roms since the HTC Hero, continued with the HTC Evo 4G, and currently on the GNexus. I am not a programmer, but very comfortable with several rooting methods and I understand the ins’ and out’s of backups, nightlys and bugs and glitches.
I bought an Asus Transformer Prime (Tf201) as soon as I could. I resisted the urge to root because its lightly skinned ICS Rom was really good. Once JB came out, I started getting antsy and started researching root methods.
I was on build version .28, and after a couple of failed root attempts Debugfs Root v1.8 worked.
I tried several roms, CM 10, Team EOS, AdroWook- and things were good, until….
Current State:
I think it was CM 10, things were just OK.. not great, and I missed some of the stock Asus apps which I liked and used often. I was previously on AndroWook, which was awesome because it had stock apps, plus many more customizations. So I Nandroid via TWRP as my recovery. And flashed CM 10. Didn’t like it so I flashed the nandroid backup of the Androwook ROM.
Now here is where things went bad. I didn’t factory reset wipe before flashing the nandroid. I did wipe cache and davlik.
Everything was fine. Until I noticed a few bugs, and I chalked it up to not fully wiping before the restore. So I tried to go back into recovery and wipe and re-flash the restore file. But no recovery found.
Nothing is left of a recovery file. And while loading up Titanium Backup it says I am not rooted.
I spend a lot of time trying to fix it. Trying to re-root via debugs, getting busy box, Super user, nothing works, I can’t get to recovery, I am not rooted anymore and none of the root methods work. I have a custom rom on, AndroWook, working fine, but I am stuck, no recovery no updates, no titanium backup, nothing!
Recap:
• Was unlocked, rooted, and on custom roms. TWRP was recovery image.
• Was on CM 10, didn’t like it, flashed back to ArndoWook via Nandroid backup restore
• Did not factory reset before flashing back to nandroid, but wiped cache and davlik
• Now the rom is no longer rooted, can’t use any of the root methods, always says SU not found
• I think it has something to do with superuser, at least that what every app that needs root can’t find.
• NO recovery image available,
Any Ideas? Thanks for the help
You should be able to flash a recovery from fastboot mode.
to get into fastboot mode, press and hold volume down while turning the prime on, when it says press up to enter recovery... dont.
wait for that to time out, you shouls then get a few icons on the screen. navigate to the icon that has a USB image and press volume up.
your tablet should now be in fastboot mode.
you will need the fastboot driver, android SDK and twrp image for the tf201 to continue, you will find the answers to these bits on the forum if you are missing any.
you can then flash the recovery with the following command:
fastboot -i 0x0B05 flash recovery recovery.img
(Replace the recovery.img name with the correct name of the img file)
Steve
lowertar said:
Background:
Rooting and flashing roms since the HTC Hero, continued with the HTC Evo 4G, and currently on the GNexus. I am not a programmer, but very comfortable with several rooting methods and I understand the ins’ and out’s of backups, nightlys and bugs and glitches.
I bought an Asus Transformer Prime (Tf201) as soon as I could. I resisted the urge to root because its lightly skinned ICS Rom was really good. Once JB came out, I started getting antsy and started researching root methods.
I was on build version .28, and after a couple of failed root attempts Debugfs Root v1.8 worked.
I tried several roms, CM 10, Team EOS, AdroWook- and things were good, until….
Current State:
I think it was CM 10, things were just OK.. not great, and I missed some of the stock Asus apps which I liked and used often. I was previously on AndroWook, which was awesome because it had stock apps, plus many more customizations. So I Nandroid via TWRP as my recovery. And flashed CM 10. Didn’t like it so I flashed the nandroid backup of the Androwook ROM.
Now here is where things went bad. I didn’t factory reset wipe before flashing the nandroid. I did wipe cache and davlik.
Everything was fine. Until I noticed a few bugs, and I chalked it up to not fully wiping before the restore. So I tried to go back into recovery and wipe and re-flash the restore file. But no recovery found.
Nothing is left of a recovery file. And while loading up Titanium Backup it says I am not rooted.
I spend a lot of time trying to fix it. Trying to re-root via debugs, getting busy box, Super user, nothing works, I can’t get to recovery, I am not rooted anymore and none of the root methods work. I have a custom rom on, AndroWook, working fine, but I am stuck, no recovery no updates, no titanium backup, nothing!
Recap:
• Was unlocked, rooted, and on custom roms. TWRP was recovery image.
• Was on CM 10, didn’t like it, flashed back to ArndoWook via Nandroid backup restore
• Did not factory reset before flashing back to nandroid, but wiped cache and davlik
• Now the rom is no longer rooted, can’t use any of the root methods, always says SU not found
• I think it has something to do with superuser, at least that what every app that needs root can’t find.
• NO recovery image available,
Any Ideas? Thanks for the help
Click to expand...
Click to collapse
Me too!
So I'm in the same trouble you are in only got there a little differently. For me without thinking I had accepted the Firmware update for the keyboard dock. After that installed my keyboard is bricked. The Tablet sees it and sucks from its battery, but none of the keys or track pad work. So I decided to do a complete full wipe of everything (Also on Androwook 1.3) and cleared out everything. It all looked like it went good, until I noticed no root. I tried to get back into recovery and cannot. Can't even get into Fastboot. Here is the details of what I'm looking at.
When I try to get into Recovery/Fastboot - Holding PWR and Volume Up will make the tablet buzz like its going to turn on but then never does. I will only see something on screen if I don't hold volume down and let it boot normally. If I try to reboot into Recovery from power menu, it goes to the dead Android screen (Android laying on his back with red exclamation).
So I tried to recover root and kept noticing that all the methods were giving 'access denied' or 'could not copy file' messages. Finally drilled this down to missing SU. When I ADB Shell in and try to SU it give me a 'SU: not found'. Unfortunately I don't have a backup of this anywhere and the only once I've been able to find is in the System/Xbin/ folder. However when I go to Xbin and SU it gives me the same 'SU: not found' message even though I see it in there.
Is there a way to download the SU and put it somewhere else to be able to get full access so I can then try the other steps of recovery?
Any help would be greatly appreciated, I'm going a little crazy here. Thanks in advance!
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
Hey,
I'm kind of a newbie developer so please bear with me!
I have a WileyFox Storm, that runs Cyanogen OS 13 (kipper) as stock. A while back, I tried rooting it, and in the process installed TWRP Custom Recovery (which is a custom one made for the Storm). Well, the process of rooting didn't work (multiple times), so I gave up.
Right, it comes to today where my device can receive an OTA update. I pressed install, where it rebooted back into recovery. As it turns out, I forgot about the TWRP CR which was still there, thus, I could not update my device.
I now want a way to install the stock recovery (just the recovery), without having root access, and preferably without factory resetting my device (I have done this too many times and it just pisses me off!).
I assume I just install the .zip from CM's website, and side load the recovery.img using ADB but I simply do not know enough.
Please help, thank you!
)
Root has nothing to do with flashing ADB so you can go ahead and sideload it as long as you have the correct drivers for your phone
And my phone won't factory reset if I just sideload the recovery.img?
Yep you are correct