Hi, I'm almost ready to release a working version of the recovery for this tablet.
It works properly with adb, but it has a UI glitch, as the stock kernel does not fully support framebuffering swaps.
It will probably be released within the next couple of days... just waiting for some final touches.
Sent from my HTC Desire using XDA App
Awesome! Ty! Will eagerly wait.
Sent from my Ideos S7 using XDA App
Lets do it
Sent from my Ideos S7 using Tapatalk
Sweet.
Sent from my HTC Vision using XDA App
Just got my S7 and dying to unlock and flash! Looking forward to all the fun hidden in this monster!
Sent from my Ideos S7 using XDA App
some news about recovery ?
Sent from my S7 using XDA App
Is this similar to ClockWorkMod?
Topic seems dead, no more news about the tools...
Sent from my X10i using XDA App
Any update?
Sent from my HTC HD2 using Tapatalk
I put together a partially working version of Clockworkrecovery that works better, but it renders only around 50% of the screen. It on my external + internal SD version of S7:
http://www.multiupload.com/0JBBOE4NAL
Changes were made to graphics.c in the recovery source code to workaround the framebuffer issues.
I was able to make a successful nandroid with this.
I am not a developer, so this is not just unfinished, but buggy.
I posted details here: http://www.androidtablets.net/forum...-recovery-help-needed-lcdc_panel-s70-c-2.html
I want to know if there is a good way to deploy this to pre-rooted users. If not, it might be better if we put together something.
This can be flashed in fastboot, or with a flash_image binary. .
xaueious said:
I put together a partially working version of Clockworkrecovery that works better, but it renders only around 50% of the screen. It on my external + internal SD version of S7:
http://www.multiupload.com/0JBBOE4NAL
Click to expand...
Click to collapse
THANK YOU! (pointless comments but i know our battle here!)
Loading though fastboot would be a pain for most new users, I wonder if we can get something simular to the archos SDE running on the huawei then we could load the custom rom and ditch the main kernel. ideas?
Someone will figure something out.
For now, you can fastboot boot this recovery image to make a working nandroid and restore as well.
I have tested nandroid now, and it works. Not tested for apps2sd though, because I do not have that setup.
I recommend that everyone would this first though: http://forum.xda-developers.com/showthread.php?t=968850
this is working on my s7 too
i tested today and recovery is working the fact that it only uses a third of the screen is not an issue in my view.
i did a nandroid backup of my system and have all mtd files saved on my desktop
my device get on a zombie state after power off the 18d1:d00d google inc appears on lsusb but the device doesnt do anything i had to reboot and do the volume and power aggain for it to respond.
on ubuntu 64 at least on my system i had to run fastboot as root
this is nice work thanks xaueious
I fixed the weird misc bug. I was using razor950's device files, which has BOARD_HAS_NO_MISC_PARTITION := true defined. My Singapore ROM has the misc partition.
Anyhow, working S7 recovery now for BestBuy version:
http://www.androidtablets.net/forum...lockworkmod-recovery-port-xaubeta-0-11-a.html
Hello there.
I own a Kyocera M6000. I believe our recovery partitions act in a similar way, in that upon reboot to recovery (of the stock recovery, that is), the device will wipe data/cache.
This is preventing clockwork recovery from loading when flashed to our recovery partitions.
I was wondering if someone here would be able to explain this issue in more detail, and any steps taken for a work around?
Much Appreciated.
Related
Hey folks,
I installed Helly Bean a few months back and just downloaded an updated version of the ROM - when I went to flash it I discovered that I can no longer get to Recover, when I choose 'Reboot' and select 'Recovery' the phone reboots but just lands on a black screen. The touch buttons at the bottom of the phone light up when you touch any of them - but otherwise nothing happens; I have to hold the power button to reboot the phone again and it just starts up as normal.
I tried using CWM ROM Manager to flash a new recovery (Choosing 'Samsung Vibrant (MTD)') - but it says there's no officially supported CWM Recovery yet for my device, and asks if I have installed one manually. I've looked into it...but I can't seem to find HOW to install one manually.
It's really not a pressing thing as my current ROM works well enough...but it'd be nice to figure out a solution. I'm still pretty much a noob at all of the Android development stuff...so please bear with me. Any advice would be most appreciated!
There was a build of helly that caused this issue. What is the build date you are running?
Sent from my SGH-T959 using xda premium
samsgun357 said:
There was a build of helly that caused this issue. What is the build date you are running?
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
Looks like Sept 27th - thought I thought it was older than that.
It was actually the kernel that caused the issue, I'll look into the build date/number.
Edit:that is the build, flash the latest .tar kernel in Odin, then boot to recovery and flash new ROM.
Sent from my SGH-T959 using xda premium
Thank you for checking!
Quick follow-up! Back when I flashed the ROM (and previous ROMs) I had a PC - so I'm familiar with Odin, but since then it crapped out and now I'm saddled with a Mac. I've investigated a Mac alternative...but all the threads I've found have dried up download links and don't quite explain the process of setting it up. Any advice there?
Worse case scenario I boot up the PC and try to get through the process of using Odin - but as the problem is that the graphics card is dying; the thing could crap out again at any moment - which I assume could brick my phone if it happened mid-flash.
Thanks!
Not real familiar with Mac. Heimdall is the only program I'm aware of, Im not sure if you can flash a kernel with it. Sorry
Sent from my SGH-T959 using xda premium
Got it solved with Odin. Thanks for the point in the right direction!
If you are rooted (assuming you are) with busybox and Android Terminal Emulator installed I was wondering if the flash_image binary could actually flash a recovery image to the device, of course there is no recovery image for our device yet BUT maybe we can start building it if this flasher alternative does work.
yes,i think it is possable
and there is some flash recovery in official roms,it named as hidden.img
and hidden.img have more than one version
hidden.img will be flash to partion 6 (mmcblk0p6 UP)
by now, we can not decrypt it's content
Well, we can't create an standard type of recovery as we wouldn't be able get that to boot. However there are ways to hi-jack the Android boot process and start a recovery that way, look at Safestrap for Motorola RAZR.
This way we can boot another rom from the internal storage (image files) and keep the original safe.
I'm very interested an trying to port it over to the XTS, however when playing with the hi-jack there is a risk of bricking so I need to first find out how to un-brick the tablet when the system partition is broken (boot partition would still be fine).
We can even boot to a custom kernel using kext however that one can be quite difficult to get working properly.
But just the ability to boot an Paranormal Android rom would be fantastic (I don't know if that rom requires changes in the kernel. But CM and AOKP doesn't).
If anyone could assist in Safestarp work it would be great. At this stage it's mostly to find out how to un-brick.
I haven't even been able to boot the tablet into recovery or bootloader mode. I have tried both ADB (reboot recovery, reboot bootloader, reboot-bootloader) and holding volume up on boot but whatever I do it still boots into Android.
With this technique I would also expect to be able too boot into the backup system partition or whatever mmcblk0p3 is (contains the system of the firmware the device where preloaded with, mmcblk0p4 is the current system that gets updated) I would hope Sony have built a whay to boot to this partition using the standard bootloader but I can't seem to find any.
EDIT: I were able to reach the recovery by mashing the volume up button on boot so now I feel much better. However I'm still interested in any information that might be interesting.
pajn said:
Well, we can't create an standard type of recovery as we wouldn't be able get that to boot. However there are ways to hi-jack the Android boot process and start a recovery that way, look at Safestrap for Motorola RAZR.
This way we can boot another rom from the internal storage (image files) and keep the original safe.
I'm very interested an trying to port it over to the XTS, however when playing with the hi-jack there is a risk of bricking so I need to first find out how to un-brick the tablet when the system partition is broken (boot partition would still be fine).
We can even boot to a custom kernel using kext however that one can be quite difficult to get working properly.
But just the ability to boot an Paranormal Android rom would be fantastic (I don't know if that rom requires changes in the kernel. But CM and AOKP doesn't).
If anyone could assist in Safestarp work it would be great. At this stage it's mostly to find out how to un-brick.
I haven't even been able to boot the tablet into recovery or bootloader mode. I have tried both ADB (reboot recovery, reboot bootloader, reboot-bootloader) and holding volume up on boot but whatever I do it still boots into Android.
With this technique I would also expect to be able too boot into the backup system partition or whatever mmcblk0p3 is (contains the system of the firmware the device where preloaded with, mmcblk0p4 is the current system that gets updated) I would hope Sony have built a whay to boot to this partition using the standard bootloader but I can't seem to find any.
EDIT: I were able to reach the recovery by mashing the volume up button on boot so now I feel much better. However I'm still interested in any information that might be interesting.
Click to expand...
Click to collapse
Well there is two system partitions and you can use the backdoor thingy from Condi's tools to avoid a soft brick BUT if it writes to the bootloader then we have ourselves a brick.
Sent from my Nexus 4 using xda app-developers app
;42754576 said:
yes,i think it is possable
and there is some flash recovery in official roms,it named as hidden.img
and hidden.img have more than one version
hidden.img will be flash to partion 6 (mmcblk0p6 UP)
by now, we can not decrypt it's content
Click to expand...
Click to collapse
I have the hidden.img BUT the MD5Sum is badf0628deff7f47b1148e5ae662aa26
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Well there is two system partitions and you can use the backdoor thingy from Condi's tools to avoid a soft brick BUT if it writes to the bootloader then we have ourselves a brick.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Of course as the boot partition requires a signature. Safestarp only writes to the system partition and it only does that once under install, after that in only touches the storage. You can have four ROM slots in the storage where you can installed custom ROMs, the system partition shall always contain the stock system. If I can get kexec to work there aren't any noticeable problems with having a locked boot loader.
Sent from my XT910 using Tapatalk 4 Beta
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
pajn said:
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
Click to expand...
Click to collapse
Holly crap, you got the recovery installed, will this work with the original Sony Tablet S and how did you manage to do such thing?
EDIT: I see you used Safestrap but from where?
Sent from my Nexus 4 using xda app-developers app
pajn said:
Prof of concept, or whatever.
https://plus.google.com/u/0/103062670878521097360/posts?partnerid=gplp0
I'm able to boot the recovery and system images on the SD card.
However the recovery isn't working yet (touchscreen working, reboot working, everything else not working)
And I haven't had the guts to try the hijack yet (I've only had the tablet for about a week and can't risk to brick it)
so I'm using scripts to reboot it from adb into recovery or other system.
Click to expand...
Click to collapse
What device are you using? STS or XTS?
Sent from my GT-S5830 using xda app-developers app
jumper62 said:
What device are you using? STS or XTS?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
That is the Sony Xperia Tablet S, I can tell by the branding near the screen and the IR Blaster plastic cover is smaller.
Sent from my Nexus 4 using xda app-developers app
jumper62 said:
What device are you using? STS or XTS?
Click to expand...
Click to collapse
Definitely an XTS. Notice the Multi Port connection at the bottom center of the tablet.
WOW! coooool. btw, how did you manage to boot safestrap in XTS? probably same method could be done on STS
As some saw it's a XTS. The recovery is safestrap and it works using 2nd-init. I found a good text describing it using normal language here http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
It should be portable to STS aswell. Every rooted Android should be able to run it. I can't promise anything as I'm working but when I'm done I can take a look at the STS aswell but I would need help from someone with at least basic adb and linux knowledge as I don't have a STS.
It wore actually easier to get this far than I expected so that's good but there are more work needed so I can't relax yet.
Sent from my XT910 using Tapatalk 4 Beta
Just contacted Chainfire on Google+ for any ideas how this is going to work.
UPDATE: Nothing yet...
Sent from my Nexus 4 using xda app-developers app
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i think you need to contact Hashcode, original developer of Safestrap for that
andyabc said:
Looks like Chainfire is not going to reply, any ideas how to get Safestrap working or use the 2nd init method?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I do have recovery working on XTS, should be quite simple to port to STS. Things left is hijack (simple but scary) and manager app (simple but can ne time consuming)
Sent from my XT910 using Tapatalk 4 Beta
pajn said:
I do have recovery working on XTS, should be quite simple to port to STS. Things left is hijack (simple but scary) and manager app (simple but can ne time consuming)
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
How did you do it though?
Sent from my Nexus 4 using xda app-developers app
andyabc said:
How did you do it though?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Studied safestrap to see how it worked and applied the same
techniques to the XTS. Where things don't work I work around them
by googling, studying others work or just testing. A pretty good
knowledge of Linux, it's boot process and programming does
help quite a bit
pajn said:
Studied safestrap to see how it worked and applied the same
techniques to the XTS. Where things don't work I work around them
by googling, studying others work or just testing. A pretty good
knowledge of Linux, it's boot process and programming does
help quite a bit
Click to expand...
Click to collapse
Can't wait for recovery on sts good job on the xts dude!
Sent from my LT28i using xda app-developers app
it all started when i installed a faulty launcher
my phone's in a boot loop
when i try to slide the key into the lock on the lockscreen, it reboots.
otherwise touch is working fine (emergency call, status bar etc)
but since i can't open the lock, i can't access the home screen and apps and stuff..
obviously i tried recovery, but it doesnt have a factory reset option (strange). the recovery mode only has some phone tests and calibrates
the other hard key combination opens up some black screen with "fastboot mode" written. and that's it.
my phone is gingerbread 2.3.5, unrooted. the company is a less popular and cheap one but it's not china.
long story short, i cant get outta boot loop coz recovery doesnt have factory reset option
plz help!
thanks
i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.
fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
deadbunny said:
thanks
i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.
fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
Click to expand...
Click to collapse
In recovery, try to wipe cache and dalvik cache. If still, then you need to flash stock ROM
deadbunny said:
thanks
i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.
fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
Click to expand...
Click to collapse
That is because when you ran those commands you wiped the rom on your phone completely so now when it tries to boot it has nothing to boot into. Please give the name of the phone so we can help you more.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Erasing the user data and cache was good, but erasing boot erases your kernel, just find the one that came with your ROM and as long as its in .img format use fastboot to flash it and all should work great
Sent from my Nexus 4 using xda premium
yo, the prob is, it's a recent phone, but from qmobile
it's qmobile bolt a2 lite. i cant find the stock rom (it was released in 3 july 2013, i believe)
so, can't i install some other ROM that all gingerbread phones support? it has 1 ghz processor, 256 mb ram, and 200 mb internal storage
thanks
i have a 2gb micro sd card as well
Then you have an issue, right now it sounds as you have no kernel maybe if your lucky the manufacture will respond to a request to release the kernel source or have a copy of factory firmware you can download.
Otherwise try to find someone with the same phone and see if they can get you a copy of the kernel
Sent from my Nexus 4 using xda premium
since i can't find the exact stock ROM for this lesser known brand, isn't there some universal gingerbread 2.3.5 stock rom? the manufactureres obviously use a modified version of google's stock gingerbread 2.3.5
It won't work, you can't just flash some generic aosp ROM to your phone, if it were that easy every phone would have tons of ROMs
You need a device tree that contains all the proprietary drivers etc to build from source and just flashing a random kernel or ROM won't do you any good (possibly make things worse)
You need to contact the maker of your phone and request this or find someone who can get you a ROM dump
Sent from my Nexus 4 using xda premium
okay thanks
Simple just claim ur warranty man!!
Sent from my A2 using xda app-developers app
im not in pakistan dude. i moved to canada. that's the prob
deadbunny said:
im not in pakistan dude. i moved to canada. that's the prob
Click to expand...
Click to collapse
That's sad
Sent from my A2 using xda app-developers app
I have a Nexus 4, and my ultimate goal is to get a custom kernel running on it. After the first attempt failed (predictably), I tried to boot a stock boot.img - one pulled from my device's boot partition, and the other downloaded from the Google stock images.
I am using 'fastboot boot' to boot the image, on Windows 7 64-bit. The command outputs that the downloading and booting process went OKAY, and the phone continues booting, but after the Google logo disappears I just get a black screen. The phone does start though, since my computer then picks up the adb interface, and I set up an SSH server to start when the phone starts. So the phone still works, just I get a black screen with backlight on.
Obviously the first step is to get a stock image booting properly. After that I can attempt to get a custom-built kernel working, but that is a whole other problem. Is there any way to figure out what is going wrong during boot? I can get any log files from the device if needed. It is running stock Android, rooted, with CWMR v6.0.2.3.
Thanks!
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Click to expand...
Click to collapse
Well ideally I want to keep the stock ROM - while the N4 is supported by Google I don't want to mess with it too much. The kernel can be 'easily' tested without flashing, which is why I don't want to flash just yet. Are you saying though that the ROM could be to blame for this? Surely though, if the kernel, initrd and configuration are identical the boot should just work straight away? It works fine booting normally - just when fastboot is used graphics don't work.
So you are saying you are running a stock ROM and kernel and when you take the exact kernel from this ROM and use fastboot to boot that kernel you have no GUI?
Something is wrong here then as this should cause no issues. Well first step is to pull a logcat and see if it will show you why there's only a black screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
My exact procedure:
Get a boot.img by cat'ing the boot partition
Start adb logcat
Use fastboot boot boot.img to boot the image
Hopefully I got that right. Unfortunately since I'm under 10 posts I can't post links, but if you put this at the end of the Pastebin URL you can access the logcat: C2Q0eR4k
I'm not sure what cating the boot partition means and logcat hast to be started after booting the kernel, but here is what I would do
Take stock ROM source and take boot.img from it
Be sure I'm using the exact same stock ROM as this kernel
Boot to fastboot
fastboot boot boot.img
Now it will start booting and in the terminal/cmd I would then run adb logcat (probably define my logcat more but whatever)
And then see what happens
But again, there is no reason that an untouched stock kernel won't boot through fastboot or give you issues as its the exact same kernel you are currently using so with this I'm confused as there must be something else missing here, either using a different ROM that the kernel booting is not meant for (different versions or whatever) or really not to sure whatelse.
Try the above again and when I get near a PC I'll peek at your logcat
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have already tried using a boot.img taken directly from the Google Nexus 4 stock, but with exactly the same results. I could post a logcat of that if you want, but I strongly suspect it will be exactly the same. It wouldn't be the recovery changing something, would it? CWMR asked me if I want to prevent Android from overwriting it - I answered 'yes', naturally, but I don't suppose it broke something?
I can rule out the software on my PC being a problem, since both Linux and Windows do the same thing. It could possibly be the USB cable, but I highly doubt it.
'cat' is a utility on Linux that reads files - that's why logcat is called what it is, since it reads the logs. By cat'ing the boot partition I literally read the boot partition, then saved the result into a file - boot.img. A form of copy, if you will.
Recovery should have no effect when booting a kernel through fastboot, I highly suspect the kernel you are trying to boot is for a different stock ROM than you are running right now. Feel free to post logcats and I can look when I'm near a pc
Sent from my Nexus 4 using XDA Premium 4 mobile app
It is the identical stock ROM to the one I'm using on my phone at the moment. For that reason, and based on the fact that the symptoms are exactly the same, I can guess that the logcats will be identical.
How is the logcat looking, by the way? I wish I knew more about Android...
Still haven't gotten near a PC, most of the time I'm mobile but hopefully tonight if I don't get back too late
Is your phone running properly when booting normally then? Or if you flash rather than boot the kernel.img with fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app
The phone works perfectly normally - using the same boot.img that I have been unsuccessfully trying to fastboot. It is really strange, almost as if the phone is rejecting the fastboot. And I don't dare flash using fastboot, in case my phone boots without graphics and forces me to flash a new ROM. Although it wouldn't be disasterous, I don't have the time at the moment to go about fixing it if something does go wrong.
Just make a backup of ROM in recovery, then fastboot flash the kernel you've been trying to boot, if there is an issue then just wipe clean and install the nandroid
This whole process will take less than 10 min and will let you know if there is an issue with your kernel.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hmm, assuming fastboot isn't lying to me, it seems to have worked. I ran 'flashboot flash boot boot.img' (to which fastboot reported OK) and then continued with the boot in the bootloader. It booted, graphics work, along with all other basic functions like wireless and touch input. To confirm, that is with the boot.img that previously did not work with 'fastboot boot', and the one that I pulled from the device itself.
Any ideas why 'fastboot boot' isn't working properly, while 'fastboot flash boot' works? I guess I can test my custom kernel by seeing if the device boots without graphics, but ideally I would like to test the whole system, not just the kernel after booting. Besides, what happens if my kernel change does in fact break the graphics - I would assume that the fastboot broke the graphics, but when it comes to flashing it would still be broken.
I'm not marking this thread as solved until some kind of answer is to be had over this problem, but I will give 'thanks' to you for giving me the courage to properly mess with my phone and come out of the other side unscathed. Having that backup there will certainly give some reassurance in case something does go wrong!
This is indeed very strange and I can't attest to why flashing the boot works while booting it doesn't as I've never experienced this issue
Its possible you may need to update fastboot on PC but I doubt this
Maybe try to boot another kernel, a recovery would do
Grab a compatible recovery.img for your phone but different than the one you currently have installed and do the same procedure you did for the kernel
fastboot boot recoveryname.img
Now see if it boots you to a different recovery temporarily
Sent from my Nexus 4 using XDA Premium 4 mobile app
I just tried with TWRP 2.6.3.0. Same issue - it seems like the recovery has booted (Windows starts trying to install device drivers) but I just get a black screen.
Then this issue is baffling, never seen it before. I would update or reflash bootloader and update or reinstall fastboot.exe, the issue seems to lie in here but I can't say what it is off hand
Sent from my Nexus 4 using XDA Premium 4 mobile app
As mentioned earlier, I doubt it is the fastboot binary, since I get exactly the same problem on both Windows and Linux (different binaries, from different places). I don't really want to start messing around with the bootloader since as far as I'm aware if something goes wrong with that the only method of recovery is JTAG on the board.
True but it is hard to brick a nexus.
the phone side of fastboot resides within the bootloader so if your issue is here flashing a new one will be the only remedy I can think of, I will say I have flashed bootloader literally hundreds of times (used to buy and sell android phones) and never once bricked one. I used fastboot most every time for this purpose as it is the safest method and even though you seemed to be having an issue with fastboot I can't imagine flashing an appropriate bootloader through fastboot will cause you a brick but it also may not fix anything
But of course this choice is yours to do (I have flashed bootloaders many of times on my n4 without fail) and I can't think of anything else that would cause the problems you're having
Sent from my Nexus 4 using XDA Premium 4 mobile app
Where should I get the bootloader image from? Just from the Google stock ROMs, or is there a thread here on XDA?
In related news, by using the 'fudge' testing method (the kernel works if Windows starts installing drivers and the backlight fluctuates), I have managed to create a working custom kernel! At last I should be able to run LXC on it. Just need to work out why the display keeps tearing...
Great news!
Either extract the hboot from stock ROM (linked at Google dev) or look in the nexus 4 threads for someone who posted it ( they usually do) just be sure to check md5sum or sha1 first
Another note i see I never posted this
http://forum.xda-developers.com/showthread.php?t=2277112
May not help you much anymore but there will be a few tips for fastboot for ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
I was reading similar stories in previous posts but I can't find any that directly relate to me. If I boot into the phone normally, I get to a screen that says "DemiGod Crash Handler: Kernel Crash!". It gives me three options, Dload Mode, Reboot and Fastboot. I can use Fastboot to get into TWRP recovery. The screen prior to this is just the Google logo with a lock at the bottom of the screen.
I'm pretty new at unlocking phones, I've only done it once with my Galaxy S2. I don't know how to fix it. I feel like I'm better off since I can access "Dload Mode" as well as TWRP just fine. I don't know what to do after this though. Everything is backed up already since I replaced this phone only a few days ago due to a large crack on the screen. A complete reset is doable. I can provide any information you need.
Related to previous posts, this seems to have been caused by using FreeGee in an attempt to unlock the phone.
Get your device into Fastboot mod and flash the stable kernel and flash the stable ROM on your device in the recovery on your bootloader unlocked device.
Sent from my Xperia E using XDA Premium 4 mobile app
JiMiTVAiDYA said:
Get your device into Fastboot mod and flash the stable kernel and flash the stable ROM on your device in the recovery on your bootloader unlocked device.
Hit Thanks if I helped.
Peace. :thumbup::beer:
Sent from my Xperia E using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will any kernel for the device work, or does it have to be the stock kernel?
Any kernel will work but the condition is it should have to be designed only for your device and have to be a stable one.
If you have a nice stable ROM for your device with it's own kernel and you are pretty sure that they are stable then use them.
This cases only applies for bootloader unlocked devices.
If you are not sure about any other kernels then you can also use the stock one but the ROM should be then used of a stock android ROM or the ROMs those are supported by the stock kernel.
Sent from my Xperia E using XDA Premium 4 mobile app
JiMiTVAiDYA said:
Any kernel will work but the condition is it should have to be designed only for you device and have to be a stable one.
If you have a nice stable ROM for your device with it's own kernel and you are pretty sure that they are stable then use them else.
This cases only applies for bootloader unlocked devices.
If you are not sure about any other kernels then you can also use the stock one but the ROM should be then used of a stock android ROM or the ROMs those are supported by the stock kernel.
Hit Thanks if I helped you.
Peace. :thumbup::beer:
Sent from my Xperia E using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just went through TWRP and apparently it does not recognize that I have an external SD card, only the internal storage. This means I can't get the ROM on there then right? Not sure what to do now...
If it's any consolation I have a version of CWM on the internal SD, maybe there's a chance I can install that and it will recognize the SD card?
wpcvenom said:
I just went through TWRP and apparently it does not recognize that I have an external SD card, only the internal storage. This means I can't get the ROM on there then right? Not sure what to do now...
Click to expand...
Click to collapse
Remove
external SD card
battery
once
and then again insert them after few minutes.
Make sure you have mounted the ext SD card in the device.
Go to Recovery > Mount > check ext sd card
Make sure your ext SD is in working condition. Test in on any other device.
Make sure you have installed recovery in clean way or just reinstall or try any other recovery.
Some times it is also a bug of a kernel so make sure you are using a right one.
If all of the above are done right way...and still you are getting problem then go to Customer Care and if you give up then relock the bootloader and comeback into stock Android.
Sent from my Xperia E using XDA Premium 4 mobile app
JiMiTVAiDYA said:
Remove
external SD card
battery
once
and then again insert them after few minutes.
Make sure you have mounted the ext SD card in the device.
Go to Recovery > Mount > check ext sd card
Make sure your ext SD is in working condition. Test in on any other device.
Make sure you have installed recovery in clean way or just reinstall or try any other recovery.
Some times it is also a bug of a kernel so make sure you are using a right one.
If all of the above are done right way...and still you are getting problem then go to Customer Care and if you give up then relock the bootloader and comeback into stock Android.
Hit Thanks if I helped you.
Peace. ☯ ✌ ♡ ☮
Sent from my Xperia E using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I actually did a bit of research and used LGNPST to reflash the stock rom and it worked! I'm so glad I was able to fix it!
If anyone else is having this trouble, I definitely recommend looking at user autoprime's guide in the Android Development section.
Thank you for your help, much appreciated!
wpcvenom said:
I actually did a bit of research and used LGNPST to reflash the stock rom and it worked! I'm so glad I was able to fix it!
If anyone else is having this trouble, I definitely recommend looking at user autoprime's guide in the Android Development section.
Thank you for your help, much appreciated!
Click to expand...
Click to collapse
You're storngly welcome.
I'm glad you you made it.