I was wondering if anyone else has run into this problem and perhaps could help me out...
Kernel source compiles fine, without errors, using the defconfig (actually inspire4g, but no real differences)
whenever I try to boot with it (first tried a cwm zip and now just using fastboot), The first HTC splash screen appears but it never gets to the second one. It is obviously hanging, but it is before adb ever comes up so I can't really troubleshoot it, and have been basically trial and error up till now.
Any suggestions would be greatly appreciated,
Chris
Related
Hi all,
I'm new to trying to root the E4GT and I've gotten in a bit of a jam. I don't think I'm completely borked because I can still easily get the phone into download mode or Clockwork recovery, but I'm stuck on what to do next and I want to proceed carefully so I don't accidentally turn this into a hard brick.
Because I'm on Linux, not Windows, after reading up on rooting the E4GT I installed heimdall. It's not the most intuitive program in the world but I eventually worked out rooting it using "heimdall flash --kernel ~/path/to/zImage" where the "zImage" in question belonged to Zedomax v3 as linked from epic4gtouchroot.com. That seemed to work brilliantly as I was able to boot into what appeared to be a reset phone, now with a generic Android boot animation rather than the default Sprint advert, and I had the Superuser app.
From there, I decided to try Strongsteve's Odex blue and I booted into Clockwork. Without even thinking about it I wiped the factory data and cache partition, and then started looking into what I needed to do, only to learn that my external SD was going to be inaccessible from here so I had the .zip file in the wrong place. I proceeded to reboot my phone to set things right but I was shocked when the phone simply appeared to turn off after the (new, rooted) boot animation played. The phone then becomes unresponsive until the battery is pulled, at which point it becomes responsive again.
Because it boots the Samsung logo (with the yellow warning triangle) and part of the boot animation, I have plenty of time to get it into download mode or Clockwork, but I don't know what my next move is. I guess (based on a bad experience with trying to root a Kindle Fire) that this is still recoverable, though. Should I just flash a stock/stock rooted ROM? Reflashing the Zedomax kernel doesn't seem to work like it did before. Has anyone encountered this? Does anyone have a link to a recovery method that should be reliable in this situation? Thanks in advance and please remember LINUX -- i.e., no Odin.
[[ PS - I pretty much described the whole process above, but in case anyone was wondering, let me explicitly state I do not have a working nandroid backup. I only got Clockwork after rooting successfully, and I didn't think wipe data/cache was potentially a brick! :\ ]]
UPDATE: Solved! I was able to successfully flash the zImage from the stock rooted kernel here. Phone is working (and rooted) once again!
i just installed cm-10-20120802-UNOFFICIAL-primou.zip on an HTC One V and now it fails to boot.
from what i've seen in other threads and through my own experience, these devices are particularly fussy when it comes to boot.img files... either they don't push out properly during updates or they require manual teasing, etc etc.
there were one or two articles online which mention a special jbboot.img file that someone had created and if any of the links worked, i'd gladly push that onto my device.
i have tried pulling the boot.img out of the zip mentioned above and flashing it to my device using fastboot. that did not work.
does anyone have a link to the proper boot partition image?
i may be on target to fix this myself...
grabbing a HELLBOY kernel here...
http://www.mediafire.com/?lo2ctaplonbdh
... as mentioned in threads like this one here...
http://forum.xda-developers.com/showthread.php?t=2101726
http://forum.xda-developers.com/showthread.php?t=1954967
http://forum.xda-developers.com/showthread.php?t=2105616
ah... positive developments.
after flashing boot-HELLBOY-CM10-201212251747.img i am seeing Android booting. strangely, however, it is a CM9 boot animation, but i flashed a CM10 rom. weird! now i get to figure THAT part out.
EDIT: aaaaaaannnnd... stuck at the android boot animation. again, i have NO IDEA why this is a CM9 animation, but that's neither here nor there. i'm more than willing to entertain anyone's notion as to what could be holding up the boot process now.
yes, after installing cm-10-20120802-UNOFFICIAL-primou.zip i did a wipe of all userdata as well as cache and dalvik cache.
i went back into my recovery environment (i use TWRP and have become a total fan of that, but i'm sure that working in ClockworkMod would be just about the same result) and performed another full wipe: data, caches, even system.
then i re-installed the cm-10-20120802-UNOFFICIAL-primou.zip rom and rebooted.
now the phone will stay stuck at the HTC logo. should i try re-flashing the boot image again? i'll take a whack at that.
EDIT: boot-HELLBOY-CM10-201212251747.img flashed. again with the CM9 boot animation and failure to fully boot into an android environment. ugh.
well, if this device wants so badly to run CM9 (the whole boot animation is a mystery to me) i'm going to just let it.
i've wiped yet again, and then flashed CM9PrimoUB3.zip and then used fastboot to push boot-HELLBOY-CM9-201212251747.img onto the device.
i'm at the android boot animation (CM9 animation, of course) and seemingly stuck there. what a goddamn pain in the ass.
EDIT: well, after a LOOOONG boot animation process, it appears that the Android O/S has started. praise jeebus and pass the beer.
EDIT 2: looks like the pDroid patch process was successful, and the phone is booting much faster now, too.
B3 sh!t that's old...... where did you find that? Also seeing your from america im going to assume you have a CDMA device not a GSM device, you should be flashing PRIMOC rom's not PRIMOU if this is the case.
Hey all,
First of all, I'm not that well known with this stuff like ROMs etc, so please don't complain if I don't understand a part/your whole solution / help, furthermore, English isn't my native language, so sorry if any grammatical mistakes.
My prob:
A long time ago I managed, as a total noob as I didn't knew what I was doing, to get my phone stuck at the HTC One screen, which shows when starting your phone up.
I somehow fixed it, and since then I had the ROM SuPrimo v23.0
Lately, I experienced a lot of battery problems with my phone, so I tried, with a bit more knowledge about all this, to solve this problem by flashing another ROM.
After I did that it got stuck at the ''This build is for development purposes... etc.'' screen. I tried a lot of ROMs and eventually I came through this screen, but now it gets stuck at the next screen.
Please, help!
R: [Q] HTC keeps getting stuck
Did you flash the kernel ??
Hm, my brother came over for the weekend but I didn't knew. He managed to fix it, luckily. Still thanks for trying to help.
R: [Q] HTC keeps getting stuck
Anyway when you flash a rom you will always have to flash kernel otherwise it won't boot.
maybe try...
mr_nooby said:
Anyway when you flash a rom you will always have to flash kernel otherwise it won't boot.
Click to expand...
Click to collapse
I had an issue like this. I still use this method to this day because i have s-on. I extract the rom and put the boot.img from the rom i want to flash into my fastboot folder, flash the boot. then flash the rom through twrp recovery. I know tons of other methods but all return with remote failed w/e rubbish. fastboot is your friend at this point with the one v cdma. At least until the devs crack that sucker. hope that helps someone out there, I sure could have used that info for about 5 hours.
New to XDA, so hopefully this is in the right place!
My problem
I tried to install a new ROM and it's gone badly wrong. First, I couldn't get the recovery bootloader to launch or to re-install. Then suddenly ADB wasn't working any more, and I was unable to boot up into the system.
Now I get boot loops with the Oppo logo. If I hold down volume up + power, I have access to Fastboot. I can use my Mac to send commands with Fastboot, but I cannot get ADB to find my device. Typing Fastboot getvar all gives me 'All: ' in response, which is not a good sign.
Attempted solutions
I've tried installing TWP and CWM, but both of them just end up booting to a black screen. At one point I tried to flash stock Oppo recovery and got a black and white flickering recovery screen for my trouble, which was unresponsive..so I wiped it and started over. I suspect it was not the correct recovery file, as I really struggle to find what are definitely the correct files now the OppoStyle Forums where I used to download recovery files no longer seem to be active.
After two days of reading various threads and trying solutions, I am really out of ideas now. So any help would be greatly appreciated!
Before embarking on this journey I cleared my phone of anything important, made sure it was rooted and enabled USB debugging. I also wipe everything from Fastboot whenever attempting any fresh flashes.
More context
I've had problems with my Find7 ever since I tried to unify my storage a couple of years back. In the end, I got unified storage to work but on a very old version of ColorOS. I had a lot of problems getting to that point, so from then I decided to just live with the outdated OS. But finally, the frustration of apps not being compatible got to me a few days ago and so I decided to try and install a new ROM. That's when my recent troubles began! I think legacy issues from my initial problems years ago may have contributed to the mess my phone is in now.
So what next?
Ideally, I'd love to get my Find7 completely wiped clean and a modern, stable ROM with unified storage working on it. But at this point, I'd settle for original ColorOS with non-unified storage again if I had to!
Hoping someone here has some suggestions I can try! Can't get worse surely
So my phone has been this way since Nov 2017, there are files that I need access to and would truly appreciate some guidance
I was experiencing issues with the bluetooth on nextbit previously so I installed a new rom after flashing the device. Once the rom also gave issues I decided to revert back to the Nextbit 7 OS and one fine day when the phone restarted it wouldnt go past the "nextbit" splash screen. Tried installing the OS again however the PC wouldnt recognize the phone anymore, switched laptop to a Mac and got the same issue
Any help would be greatly appreciated
It wont let me post a URL link. I have taken www out hopefully it allows to view the video, shows exactly whats wrong
youtube.com/watch?v=ImIk5CErWf0
It looks there's something wrong with the system boot, since it's reaching the blue boot-animation and it stays there (probably before loading the adb stuff). Fortunately u did unlock the bootloader and that annoying initial screen may be helpful this time, did u try to reach recovery or fastboot mode from there (pressing some volume key)? It's pretty hard for it to be broken there too and in such a case I would think about some hardware fault. Anyway from the recovery (I hope u have TWRP, if not install it with fastboot) you should be able to do whatever u want, including recovering your files or (re)installing a rom