Hi Guys,
I have an AT&T One X that I unlocked and flashed TWRP recovery on. I have been using this for quite some time with a stockish HTC Custom ROM. However I wanted to see what the latest Cyanogenmod was like. So I flashed the latest snapshot after first flashing the specific recovery software linked on the cyanogenmod page. So far so good. Device booted up and was ready for use.
I wanted to install Gapps afterwards so I went to OpenGapps to download the aroma installer. However the Cyanogenmod recovery software doesn't seem to support this. So I wanted to go back to TWRP. Instead of doing the usual flashing in the recovery I decided to use the TWRP Rommanager since it seemed like a quick fix. Ooh how wrong I was.
After installing the recovery through TWRP manager I accepted the request of TWRP manager to reboot to recovery. However my phone greeted me with a black screen afterwards. Up till now I haven't seen anything pop up onscreen anymore and I tried numerous things. The only strand of hope I still have left as that when connecting to my pc I'm still able to see the phone is in fastboot mode.
However when trying to execute a new flash of my recovery partition my phone keeps saying "fastboot error; remote not allowed". I've searched through numerous articles without a solution up till now. Is my phone too far gone to revive?
Doesn't seem like a straightforward fix as no responses are coming in. Maybe an indication if there would be a fix is appreciated as well.
Related
EDIT: For some reason, after several attempts, ROM Manager successfully flashed recovery. Should be able to figure this out now.
After going Cyanogen free for awhile, I decided to download the newest kang. Problem is, GAPPS wasn't included.
It seems that ROM Manager isn't allowing me to download ClockworkMod Recovery; perhaps because I am not logged in? Not sure, it simply doesn't seem to want to download. No errors, it just doesn't do anything when trying to flash it.
I try to reboot into recovery, but it just loads the ROM. Attempting to hold the volume up while booting gets me stuck at the folder with the arrow screen.
I'm pretty sure that it is highly recommended that you don't use the fake CWM via rom manager. It installs it to your sd card or something of the sort. The easiest way to install CWM I know of is using the tool this guy madeLink Here. I think that will take care of your problems, of course I'm a little intoxicated on the net so I could be reading it wrong <<---Alcoholic Disclamer
I ran into some trouble trying to install a new ROM, and now have a hard time getting things up and running again.
Just figured I'd share a solution that took me an hour or 2 to figure out.
The Problem
The system didn't boot up any more. At some points I got stuck in a boot reloop, at others in the HTC screen (for development use only)
The Basic Facts
S4
Unlocked
Hboot 1.06.0000
Radio 1.06es.50.02.31
I could always boot into bootloader and into recovery (TWRP 2.3.3.0 - although that one always asks for a password, but when I click on Cancel, it does seem to work
The Things I Tried
I tried to install a ROM by first pushing it with quick adb pusher to the sd-card that was mounted in twrp, I then tried to install that zip file but got all sorts of 'mount' errors
I then tried to fash a stock RUU (I found RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe), I relocked the phone with the one-in-all toolbox (which worked just fine), the phone went into bootloader, a White HTC sign appeared on the screen, it sent the file, then did 'updating signatures', but ended up with ERROR [130]: model ID error. I take it that is because it found a different Radio from the one expected
I then tried to flash the 'right' radio for the RUU I found (radio-1.08ts.50.02.16) by doing fastboot boot radio.img, but that gave the following error: "reproduce boot image with on-flash ramdisk error"
The Solution
I finally managed to install the ROM through the all-in-one toolbox. I selected under the 'ADB Sideload a ROM' option under 'Extras', the went into 'adb sideload' in twrp advanced and selected a rom I had downloaded (in my case ViperOneS). It started sending it properly (sending:'sideload' x%), it then showed the Team Venom logo and opened the aroma installer. I selected full install with a full wipe (to be on the safe side), and aroma then did its thing until it said "new ROM flashed successfully". I then rebooted and had to wait a few minutes for the first boot (as it had warned me), but I'm fully back up and running again! So If any of you experience a similar problem, you may want to try this out (and avoid the other things I tried.
Thanks for posting a solution. But I do want to point out that this is the development forum. As such, your post doesn't belong here. The General or Q&A forums are the correct ones.
Sent from my HTC One S using Tapatalk 2
Thanks Thanks Thanks !!!
I've been stuck on boot with every rom's that i've been trying to install!
I was becoming very concern about the problem !
I went from CM10 to the new Viper 2.0 but having troubles with WIFI I start testing others roms and than I become stuck!
Since I've TRW 2.3 and tool kit in my pc I give a shoot at your tutorial and it WORKS.
Thanks again,
Rui
[SOLVED]
So after having my Transformer for some time now (unlocked, rooted, and running CROMI) it began to get sluggish. I wanted to upgrade to something else, and decided to try PA HALO http://forum.xda-developers.com/showthread.php?t=2376927
I missed something somewhere, prob the fact that I installed TWRP over my CWM that I had from long ago, instead of upgrading to the new CWM, or the fact that I'm still on the 10.4.4.25 bootloader. I rebooted into recovery, flashed the PA zip, rebooted into recovery, flashed the new GAPPS, and wiped the cache and Delvik. When I went to boot it up the "ParanoidAndroid3+" text and neon jellybean/fish thing show up, then nothing.
I (stupidly) did not make a new backup before doing this change (though there is one from my CWM, but TWRP doesn't seem to recognize it).
ADB does not seem to be working. When I select the USB icon, while using the power+volDown, I get the message "starting fastboot usb download protocol" and ADB does not see the device. If I let the device try and boot (when it gets stuck at the neon jb/fish) ADB sees the device, but gives the error <waiting for device> when I try and flash the new CWM. I seem to be able to access the terminal from TWRP, so I know there is a way to load the old CWM restore files, I just don't know how.
Help is needed.
found a way to do it, but I guess it took away my root when I flashed the new rom. Now I get "su is not recognized" from the terminal..... I'm downloading http://forum.xda-developers.com/showthread.php?t=2107271 and will try to get the os to boot. I can always re root the device, but I kinda need the device to boot into something first.
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
berndblb said:
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
Click to expand...
Click to collapse
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
datboyc said:
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
Click to expand...
Click to collapse
The "kick" was really meant as a friendly slap upside your head which was probably unnecessary since I hope you did that yourself already extensively - so I apologize
Glad you got it working :thumbup:
Hi everybody.
I hope I will get some help here.
My phone is rooted but still with stock ROM (4.4.4).
Couple of hours ago I used APToide to update 7 apps, one of which was "Google Search". After updates had finished, I would constantly get a message telling me that "Google Search had crashed", thus after several times I decided to uninstall it from APToide: this brought back the "default" one.
Besides the above, SuperSU was updated as well and it told me to update its binary: I did this as well, rebooted the phone and it seemed ok. I was able to open Twitter and from there open a URL in Chrome. As soon as I wanted to go back to my homescreen, nothing would happen: none of the buttons would do anything! Thus I decided to shut the phone down.
Now restarting the phone brings it up, it goes past the Google word and gets stuck at the four colored balloons!!! Now if I keep the power button pressed long enough, the phone simply reboots...
The weird thing is that the phone is getting WLAN and IP and it reacts to incoming Hangout messages vibrating!!!
Any help will be very much appreciated!
Thanks in advance,
F.
Since you are phone is already rooted, install custom recovery. I recommend TWRP recovery. Because you cannot boot up your device, use Nexus 5 toolkit or push it via adb to flash custom recovery.
Once you are in custom recovery, clear cache and dalvik. Hopefully that should do the trick. If not you may have to flash stock kernel via adb or Nexus 5 toolkit.
badboy47 said:
Since you are phone is already rooted, install custom recovery. I recommend TWRP recovery. You cannot boot up your device, use Nexus 5 toolkit or push it via adb to flash custom recovery.
Once you are in custom recovery, clear cache and dalvik. Hopefully that should do the trick. If not you may have to flash stock kernel via adb or Nexus 5 toolkit.
Click to expand...
Click to collapse
Hi badboy... in the meantime I got into stock recovery and did a full wipe/reset... now it works again...
Why do you recommend TWRP custom recovery?
Thanks,
F.
Glad you fixed it! TWRp has the best and friendly user interface with great features. I never have any problems flashing ROMs / kernels. Things like phone stuck on logo, not booting up, can be fixed in seconds in custom recovery. There is also cwm recovery. I used it for years but I eventually switched to twrp. Its so much better. I would say try both.
No do not try CWM. Use TWRP or PhilZ touch.
I was finally able to unlock my bootloader today after the 72-hour waiting period, but am having a problem getting TWRP flashed. I can flash the stock ROM (perseus_images_8.12.13_20181213.0000.00_9.0_cn_21f4637335.tgz) no problem, get through setup, enabling ADB, etc, but as soon as I flash TWRP, the device stops booting. It flashes successfully, but then attempting a reboot always ends up with the device back at the bootloader. Key combos for other modes doesn't make a difference. I'm working on trying the Global ROM too, just to see how that runs, but I have not been able to get TWRP at all or get the device booted to anything other than fastboot after a TWRP flash (tried official & unofficial versions).
I've seen other posts with a similar issue, but that usually seemed to be about users accidentally ended up in Fastboot & not knowing how to get out of it. That's not the case here.
I've been using Android & custom ROM's for years, so I know my way around ADB, Fastboot, & everything rooting & custom ROM's entail, I just seem to be missing something here.
Thanks for any help you can provide.
EDIT:
Not sure why flashing the Global Dev ROM (perseus_global_images_9.5.17_20190517.0000.00_9.0_global_134d3070e5.tgz) made any difference, but after that, ran through the first run wizard, I was able to flash TWRP from the bootloader & actually boot into it so I could flash a custom ROM.