Related
Hello all..
So I picekd up a t-mobile tab off craigslist yesterday, which was pre-rooted (no superuser though) and has the Roto JMI rom (if that's what it is) installed with the 2.6.32.9 [email protected] #1 kernel.
Last night I tried rooting/installing CWM with the one click thing, run.bat or run.sh in my case since I'm on a mac. It wouldn't work and got stuck in a recovery loop. Every time I would boot, it would go straight to recovery. So I managed to get a data wipe done and now I'm back to the way it was before.
I rooted it with SimpleOneClick and it's rooted with superuser now. I've installed rom manager, tried to flash CWM, but when I do it just says successfully installed CWM.
When I try to boot to recovery, it just stops at the 'Galaxy Tab' loading screen. No stock recovery, no CWM, no nothing. The only way to get it out of this mode is to issue an ./adb reboot bootlaoder command. After I do that, it works fine. Can start up, shut down etc.
What did I do??? Is there any way to flash the recovery via adb push like I did the first time I rooted my phone? I can't seem to find the recovery to push to the phone, so yeah.. I'm confused here.
Thanks!!
sanchez said:
Hello all..
So I picekd up a t-mobile tab off craigslist yesterday, which was pre-rooted (no superuser though) and has the Roto JMI rom (if that's what it is) installed with the 2.6.32.9 [email protected] #1 kernel.
Last night I tried rooting/installing CWM with the one click thing, run.bat or run.sh in my case since I'm on a mac. It wouldn't work and got stuck in a recovery loop. Every time I would boot, it would go straight to recovery. So I managed to get a data wipe done and now I'm back to the way it was before.
I rooted it with SimpleOneClick and it's rooted with superuser now. I've installed rom manager, tried to flash CWM, but when I do it just says successfully installed CWM.
When I try to boot to recovery, it just stops at the 'Galaxy Tab' loading screen. No stock recovery, no CWM, no nothing. The only way to get it out of this mode is to issue an ./adb reboot bootlaoder command. After I do that, it works fine. Can start up, shut down etc.
What did I do??? Is there any way to flash the recovery via adb push like I did the first time I rooted my phone? I can't seem to find the recovery to push to the phone, so yeah.. I'm confused here.
Thanks!!
Click to expand...
Click to collapse
Not sure about t-mobile tabs (I've heard they can be a bit tricky) but if you can install Modaco/paulobrian kernel (thread in the dev section) then that has a fully working CWM built in. Backups and restores work perfectly with this. The "official" one from koush (sp) is abandonware...
paulshields said:
Not sure about t-mobile tabs (I've heard they can be a bit tricky) but if you can install Modaco/paulobrian kernel (thread in the dev section) then that has a fully working CWM built in. Backups and restores work perfectly with this. The "official" one from koush (sp) is abandonware...
Click to expand...
Click to collapse
I actually just got it all set up after trying many things using this thread:
http://forum.xda-developers.com/showthread.php?p=11713685
Worked like a champ.
sanchez said:
I actually just got it all set up after trying many things using this thread:
http://forum.xda-developers.com/showthread.php?p=11713685
Worked like a champ.
Click to expand...
Click to collapse
Excellent .
I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?
bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.
Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?
Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.
bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.
So, I had to replace my HTC One.
The new one is 1.55 -- I am still S-On.
Today I flashed CWM 6043 using fastboot after unlocking the bootloader through HTC.
I flashed SuperSU.
I attempted to flash two of the newer roms (InsertCoin and Renovate) because I wanted Sense 6.
After successfully going through the flash, the phone reboots and goes straight back to Fastboot. If I go into the Bootloader and try to go into Recovery, it just kicks me back to the bootloader. I can then use fastboot to reflash CWM 6043 again and do it all over.
Same thing.
Every time.
Thoughts?
So.
I flashed 42One through Sideload and it launched fine. The only difference I can see (since this one is 4.4.2 as well) is that it didn't use the fancy rom installation package (can't remember the name) -- is there an incompatibility?
Or, maybe not. After booting I get to the unlock screen but after unlocking, all I see is the HTC splash screen but can still interact with the notification tray and the long press power menu...
Hmm.
Flashed a new kernel that has sense 6 support, still no luck. It has to be the AROMA installer.
Read somewhere that CWM Touch interferes wiht Aroma -- trying TWRP.
No luck, the aroma installer on both of those roms is killing the custom recovery. I don't know what else to do, any other ideas?
loxish said:
No luck, the aroma installer on both of those roms is killing the custom recovery. I don't know what else to do, any other ideas?
Click to expand...
Click to collapse
What recovery and version are you using
Which Rom are youu currently trying to flash (Sense 6?)? Which Kernel?
@bored_stupid -- I used TWRP 2.7 and 2.7.0.3 as well as CWM 6.0.4.3
@R34LY - I flashed the teaMSeven-sense-4.4.2-6th-v2.3.6 kernel.
For what it's worth, I just used the Guru Reset 3.04 rom to flash back to stock -- it's an Aroma installer as well -- and it worked fine, is booting now, not stuck on the bootloader/didn'e lost custom recovery.
Hmm.
However, I'm having the same issue of just having the HTC splash screen on this rom as well, I'm going to reflash the stock kernel.
Actually, it's just boot looping now. I've got to bounce and pick someone up from the Airport, so I'll pick this up later, I suppose. Arf.
Can I flash a RUU on 1.55 S-On? Maybe I'll just do that and try to go all the way back.
loxish said:
For what it's worth, I just used the Guru Reset 3.04 rom to flash back to stock -- it's an Aroma installer as well -- and it worked fine, is booting now, not stuck on the bootloader/didn'e lost custom recovery.
Hmm.
Click to expand...
Click to collapse
Well at least you now have a working phone, i noticed with ARHD 51 and 52 that the phone would just go to a black screen. A hard reset solved it and it boots fine after that. ARHD 53 does not suffer from the issue.
By the way Kit Kat requires TWRP 2.6.3.3 or newer
I'm using TWRP 2.6.3.3 and Elementalx 13.5.1 and it works perfect for me. Have you tryied this combination? Assuming you are up to a custom kernel.
No, it's not working -- still doing the looping showing the HTC splash, but I can still access the long-hold power button menu. I'll try @r34dy suggestion.
Post your feedback when you tryied it!
Sent from my HTC One using Tapatalk
Tried to flash 2.6.3.3 -- when I booted itno recovery, it showed a black screen and restarted.
So i flashed 2.7.0.3. -- it worked fine.
Flashed InsertCoin, didn't reboot, immediately flashedElementalX 13.5.1. Rebooted.
Same thing, straight to fastboot, if I go in bootloader and try to boot recovery, it loops back and I have to re-flash recovery.
I'm at a point now where I am trying CM11/SlimKat/Etc. using ElementalX 13.5.1 kernel.
It seems to work... but as it gets to the 'setup screen' in CM or SK, reboots the phone ~7 seconds in, every time, just looping.
I used factory reset, same thing.
Tried ElementalX 11.7 -- same thing, the rom runs for ~10 seconds or so, it gets the apps upgraded, even boots to the main screen -- I can literally see the home screen on the SlimKat installation with ElementalX 11.7 -- then it restarts itself.
Even in safe mode, it's looping after ~10 seconds post boot. Hmmmm.
I have spent a day and a half trying to fix all of my issues before I finally turned here but I am at my wits end.
This all started with my attempt to flash Viper to my HTC one. I installed clockwork touch loaded Viper to the drive and went to install. During the install process something happened and my install failed. When I rebooted the phone it returned to the fasboot screen and there was no recovery present. I had heard that sometimes TWRP works better for installing some ROMs so I decided to switch courses and try that. Before installing I went and formatted cache, data, ect. When I tried to install Viper this time it appeared to be a successful install. However, I was once again I was returned to the fastboot screen and no recovery was present. I tried this a few more times with either clockwork or TWRP using sideload with no luck. I also trried using fastboot to flash a sprint stock recovery boot and image. When the phone rebooted it showed the white HTC Screen but nothing happened for a half hour so I restarted the phone again only to be dropped into the fastboot. I also tried locking and unlocking the boot loader and tried a Sprint HTC one RUU with no success.
So at this moment this is where I stand:
I am on the fastboot screen with no recovery.
HBOOT 1.56.0000
S-ON
Any help you can provide would be GREATLY appreciated. Thanks for your time.
Betraythesway said:
I have spent a day and a half trying to fix all of my issues before I finally turned here but I am at my wits end.
This all started with my attempt to flash Viper to my HTC one. I installed clockwork touch loaded Viper to the drive and went to install. During the install process something happened and my install failed. When I rebooted the phone it returned to the fasboot screen and there was no recovery present. I had heard that sometimes TWRP works better for installing some ROMs so I decided to switch courses and try that. Before installing I went and formatted cache, data, ect. When I tried to install Viper this time it appeared to be a successful install. However, I was once again I was returned to the fastboot screen and no recovery was present. I tried this a few more times with either clockwork or TWRP using sideload with no luck. I also trried using fastboot to flash a sprint stock recovery boot and image. When the phone rebooted it showed the white HTC Screen but nothing happened for a half hour so I restarted the phone again only to be dropped into the fastboot. I also tried locking and unlocking the boot loader and tried a Sprint HTC one RUU with no success.
So at this moment this is where I stand:
I am on the fastboot screen with no recovery.
HBOOT 1.56.0000
S-ON
Any help you can provide would be GREATLY appreciated. Thanks for your time.
Click to expand...
Click to collapse
You probably should RUU and stay over.
Sent from my Slim Photon using xda app-developers app
So I have my phone up an running on a stock RUU but I seem to have the same issues with and error when installing Viper. Any ideas as to what the issue could be?
Betraythesway said:
So I have my phone up an running on a stock RUU but I seem to have the same issues with and error when installing Viper. Any ideas as to what the issue could be?
Click to expand...
Click to collapse
... now that its up and running, i recommend you get s-off 1st. it eases many things. then flash twrp 2.7.0.4 recovery and try to flash viper :victory: ...
I was in this situation myself. If you can adb twrp recovery onto your phone. Dont try to flash viper with cwm it will mess stuff up. After you have a recovery loaded flash the viper rom. If it boots up be sure to check about phone section in the settings and see if there is a baseband version present. If not just flash the latest firmware and you should be good to go. This was what i had to do.
Same here, about a month ago. They really need to just remove that option to flash CWM. I managed to get a recovery installed, but now it seems like half the ROMs I try to flash won't boot. I don't even know what Rom I am using, because it has disappeared from XDA. It's a 4.4.2 Sense 5.5 ROM, and it is odexed and came with Xposed Installer. It's the only ROM that seems to work anymore, so I have to wonder if my firmware got messed up. I'm S-On, with no way to S-off for the foreseeable future until I can fix my laptop. Since my laptop is unavailable, I'm a bit hesitant to mess with the phone much more, since I can't fix it again without the computer.
Sent from my HTCONE using Tapatalk
I've read a number of these threads, and many have Viper in common. Viper by itself is an amazing ROM. Maybe too amazing... Incredible amount of customization. I have to remind myself occasionally that as much as I flash ROMs and lurk around here that I am not a dev.
I would do my best to achieve S-OFF if you have any plans for custom ROMs. It's always useful. I would also suggest trying one of the Sense 6 ROMs. They are all amazing.
Sent from my One using Tapatalk
S-OFF is necessary for some ROMs to work, although I'm not sure about Viper. Use firewater.
greywolf928 said:
S-OFF is necessary for some ROMs to work, although I'm not sure about Viper. Use firewater.
Click to expand...
Click to collapse
I am very sorry I know this is a slow response. So I tried to first root my phone so I could use firewater but I ran into issues. First, I tried to place supersu on the internal hard drive via windows but when I rebooted into recovery I was not able to find any of the folders I had access to. So i tried using side load but got errors that I could not mount cache and could not mount system. Do you have any suggestions on how to proceed?