Related
So, I've been banging my head against the wall for a few days now, and though I usually don't post questions (90% of the time I find the answer somewhere on the interwebs) I'm a bit stuck.
So I'm trying to get used to creating my own boot images, and have found the article android-dls article among others very helpful in understanding everything (would post the link, but can't yet)
It was easy enough to find the boot image on the Fire, and I have been using the unpack_bootimg.pl to unpack the boot image, then make the necessary changes, and mkbootfs to pack up the ramdisk. Everything goes swimmingly.
The problem arises when using fastboot to boot the new boot image using the command below:
fastboot boot boot.img-kernel.gz boot.img-ramdisk.cpio.gz
It loads it to the Fire fine, but never boots. My guess is it has something to do with offsets, but to be honest, it's a bit of a blind guess. I have also attempted to repackage the boot image into a testboot.img with the same results. I've even tried just unpacking an re-packing the known good image thats already there, without changes.
Also, not sure if this is relevant information, but mkbootfs and mkbootimg was compiled in OS X (10.6.8 for those that care) directly from the android 4.0.3 source.
Does any one have any suggestions on what to try next? Or even better, any additional articles, threads, etc. that I may have missed. Any help would be appreciated.
Oh, forgot to mention, I also have the firefirefire bootloader installed (1.2) and TWRP. Don't think it matters though.
This may not apply as I do not own a KF...
Have you ever successfully used fastboot in that manner with the KF? Any kernel I mean...
I was never able to use fastboot like that with my inspire 4g... but could use it to flash the very same image quite successfully.
Dont know if that helps or not...
I've found that those scripts do not play nicely with the Fire's boot images for whatever reason, and repacking with them renders all of my images unbootable as well. I've ended up using dsixda's ROM kitchen just for the boot image scripts because those work fine. I'm not entirely sure where the disconnect is on the perl scripts, but I haven't looked at them truly extensively.
Unpacking and re-packing boot images
gumbi2400,
Have you tried loading another boot.img/rom and going back to the one you have edited? I am only asking for my own stupidity. with your post it has my mind going places, well it should not go just yet in the Kindle. I am pretty sure it not much different then myself building GhostBSD. Let me know please!
Thanks,
JohninLex
Changed the Boot Logo and now stuck at boot
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
wayoung said:
I edited the fire_start_000??.png (5 total 43 though 48) to add some text. Re-loaded the zipes into the bootscreen zip file. When I used TWRP to install a factory rom (Gr6-update-modacocustomrom-kindlefire.zip)
It installed fine, and i wiped the cache and the other (Davoric?).
Now when I re-started the Kindle, it shows the "kindle fire" logo, flashes, and then re-displays the logo, but freezes there
I am in fastboot mode according to the Kindle fire utility, and cant change back to normal.
Says no device found.
I have the Android adb device in Device Manager
I can boot and reboot using ADB
But anytime I try to use the fastboot command I get the no device error
If I type in ADB DEVICES, it doesnt show up
If you can help it would be appreciated.
Click to expand...
Click to collapse
you could try to get to twrp by issuing:
fastboot oem idme bootmode 5001
fastboot reboot
in the case it says <waiting for device> power off the kf by holding pwr ~20sec
power on again - at some point the command gets finished
power off and on again
once in twrp you have adb available and can copy a good file over the bad one
take care of the permissions !
or just restore a backup or flash a new rom
maybe you have to check your drivers in device manager:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Sorry it took me so long to reply, got distracted by other modding projects.
@JohninLex:
I actually tried simply unpacking and re-packing the stock image that was already on there, just to make sure I was packing it back properly, but got no love.
@eldarerathis:
I think I had stumbled across the ROM Kitchen previously, but wasn't sure if it was what I was looking for. I'm fairly new to this low level of messing with Android, I have a tad bit of experience with Linux proper, but I know things can get pretty murky. I may end up ripping the scripts apart and seeing whats actually in there. Thanks for the tip!
Life is busy right now, and I haven't gotten a chance to mess around with modding my Kindle more, may be time to start again.
Hello!
I turned on my MK802III and went to: Settings -> Video -> Scaling options -> 100%, and the screen started showing some odd pixel lines, mouse and keyboard stopped responding. After a few minutes, I unplugged the device, and now it just won't boot.
Now, the blue led turns ON and the TV recognizes that there is a signal, but goes to EnergySaving mode, and absolutely nothing else happens.
Any ideas? There is not much information around the internet about this.
Cheers!
PS: It was the device first boot! I had just received it.7
__________
UPDATE:
I guess I might have reached a conclusion...I think that the device might be boot looping. So I googled about how to restore/update firmware, but a needed a way to do this without having access to any of the device's UI. So I found a recovery method by short circuit at Armtvtech and there is also OFFICIAL information about this.
After downloading everything needed, I proceeded to short circuit the device. Everything ended up OK: drivers installed successfully, Rikomagic's tool detects the device, BUT after chosing the .img from Rikomagic's files and clicking 'update', the tool returns an error.
SCREENSHOT
Now I'm stuck here...can someone please help?
Hmm. Just got one myself Google rikomagic forum there is a sub forum with ROM list thread. Most roms include flasher im using finless 1.7a. you can reflash nand from windows. Unless was a hardware damage?
There's a reset button same side as USB otg. You have to have flasher prog on PC running and hold in reset while device connects like 10 secounds . install driver rinse and repeat run flasher
Sent from my Nexus 4 using XDA Premium HD app
Nanopane said:
Hello!
I turned on my MK802III and went to: Settings -> Video -> Scaling options -> 100%, and the screen started showing some odd pixel lines, mouse and keyboard stopped responding. After a few minutes, I unplugged the device, and now it just won't boot.
Now, the blue led turns ON and the TV recognizes that there is a signal, but goes to EnergySaving mode, and absolutely nothing else happens.
Any ideas? There is not much information around the internet about this.
Cheers!
PS: It was the device first boot! I had just received it.7
__________
UPDATE:
I guess I might have reached a conclusion...I think that the device might be boot looping. So I googled about how to restore/update firmware, but a needed a way to do this without having access to any of the device's UI. So I found a recovery method by short circuit at Armtvtech and there is also OFFICIAL information about this.
After downloading everything needed, I proceeded to short circuit the device. Everything ended up OK: drivers installed successfully, Rikomagic's tool detects the device, BUT after chosing the .img from Rikomagic's files and clicking 'update', the tool returns an error.
SCREENSHOT
Now I'm stuck here...can someone please help?
Click to expand...
Click to collapse
Could it be possible you are useing wrong version of the rockchip flash tool? The version you are useing may see the device. But wont flash. Try different one for your version of windblows and the device itself. Good luck.
Sent from my A200 using xda app-developers app
Here's attempt 2 at me trying to make a ROM from source, and just like the first time I tried (back with the R1 HD) I'm running into problems. I am following this guide by the way, but just substituting everything for cm13 where it says cm14.1.
I've decided to try and compile Lineage 13 for the G4 Play, using the device tree for Cyanogenmod 13 provided by squid2. When I tried to add the device tree created specifically for the G4 Play (harpia cm13.0) I get an error running "breakfast harpia" saying there is no msm8916.mk file. I downloaded the other msm8916-common device tree and put it in a separate directory in the device folder, and aftewards I was able to run breakfast for the harpia just fine.
Now, after running croot and "brunch harpia", I am getting more errors during the build process:
/bin/bash: mvn: command not found
make: *** [/home/administrator/android/system/out/target/common/obj/JAVA_LIBRARIES/ambientsdk_intermediates/com.cyngn.ambient.ambientsdk-1.6.0-147069776-39fe2d07.aar] Error 127
Any idea how to clear these up? I am running ubuntu 14.04.5 with openjdk 7 by the way.
The build error is that you're missing Maven (the mvn command line utility)
squid2 said:
The build error is that you're missing Maven (the mvn command line utility)
Click to expand...
Click to collapse
Thanks for the help, the build was running for about 40 minutes so far without stoppage from error. I'll wait and see if anything else comes up.
EDIT: Built successfully. Going to test soon on my own device, but I'll upload to XDA once I can get home and upload the source as well.
After flashing the ROM I built to my device, I get stuck at the boot logo (the BOOTLOADER UNLOCKED warning). I don't think the boot process gets as far as starting ADB because ADB on my computer won't detect my device, so I can't use that to pull logs. Any idea what to do here?
EDIT: Turns out my cable was faulty, and I got some logs. This folder also contains the non-functioning Lineage13 build:
https://drive.google.com/open?id=0BxupjEjigG4tcGNJZmcxMVJidWs
I'm thinking of downloading squid's CM13 and flashing the boot image from there on top of a Lineage13 flash. I can't download it now (mediafire is blocked here) but I should get around to it later tonight
UPDATE: When I replaced the boot.img with the one from squid2's CM13 it still gets stuck on the boot logo, but it vibrates after a couple of seconds of turning it on. After waiting maybe 40-50 seconds the device reboots and repeats the process. This is further than I got with Lineage's boot image, as with that it would just sit on the boot logo with no response or signs of activity whatsoever.
The problem lies in the boot image, but now I have to find what specifically in it is the problem.
jasonmerc said:
After flashing the ROM I built to my device, I get stuck at the boot logo (the BOOTLOADER UNLOCKED warning). I don't think the boot process gets as far as starting ADB because ADB on my computer won't detect my device, so I can't use that to pull logs. Any idea what to do here?
EDIT: Turns out my cable was faulty, and I got some logs. This folder also contains the non-functioning Lineage13 build:
https://drive.google.com/open?id=0BxupjEjigG4tcGNJZmcxMVJidWs
I'm thinking of downloading squid's CM13 and flashing the boot image from there on top of a Lineage13 flash. I can't download it now (mediafire is blocked here) but I should get around to it later tonight
Click to expand...
Click to collapse
Had the same problem with Moto G³ (2015) and I just use squid kernel. People seem to like squid kernel more anyway.
Hi all,
this is a dedicated thread for gaining access to the recovery on the QF001 head units. All other infos and general discussions are posted here: https://forum.xda-developers.com/t/...d-units-with-uis-7862s-not-fyt-based.4525675/
What we have got so far:
the whole firmware as flashable zip file
adb access with root user via wireless on port 9876
reboot bootloader brings up a screen which says "fastboot mode" but thats worthless without a working usb connection
reboot recovery boots for a second into a kind of recovery screen and than automatically reboots into normal mode
What i have tried myself so far:
flashing the device with a self cooked firmware (SuperR) with integrated magisk recovery. The device went into flash mode but did not accept the file due to signature issues
several method to push the reset button to get into recovery. no success...
Every info is very wellcome. Happy trying to all!
Cheers
I tried this. It didn't work but I'm not sure I was doing it right.
There is a link to a text file with instruction in the YouTube comments.
Rebooting into recovery from system shows this briefly, then boots back into the system.
I found something interesting. It's from the FYT device, but it's done very similarly with us.
Maybe it would be possible to make Usb Otg working
Motherboard on photo - our device
Vėžys said:
I found something interesting. It's from the FYT device, but it's done very similarly with us.
Maybe it would be possible to make Usb Otg working
Click to expand...
Click to collapse
Can you please link the post on the FYT device that talks more about USB OTG capability?
It's from the 4Pda forum, it's on Russian language
Головные устройства Unisoc на процессоре UIS7862 / SC9863a (UIS8581A) Android 10 - 4PDA
Головные устройства Unisoc на процессоре UIS7862 / SC9863a (UIS8581A) Android 10, [Головное устройство][Автомагнитола][Android]
4pda.to
Hello, people. I have good news for the owners of bricks: my seller kindly provided me with the tools to repair a device with a damaged operating system - a flasher and the necessary files for the S8 1024x600. Download all the contents of the folder and sort it out. I don't have time yet. Good luck!
Восстановление_кирпича-S8_1024х600 - Google Drive
drive.google.com
Great, everything works. A big thank you. Finally unbrick my device
And-S said:
Hello, people. I have good news for the owners of bricks: my seller kindly provided me with the tools to repair a device with a damaged operating system - a flasher and the necessary files for the S8 1024x600. Download all the contents of the folder and sort it out. I don't have time yet. Good luck!
Восстановление_кирпича-S8_1024х600 - Google Drive
drive.google.com
Click to expand...
Click to collapse
Looks like we have at minimum an USB driver now to connect the HU to pc... looks like it is included in the package for recovery tool...
Is there anyway to get into recovery mode if I'm stuck at the boot logo?
super_paws said:
Is there anyway to get into recovery mode if I'm stuck at the boot logo?
Click to expand...
Click to collapse
Not directly but there is a software solution mentioned in the other thread. Someone could revive his head unit with that software.
Thanks to everyone that helped! I have a working unit again!
Figured I'd write a few things here to help anyone else that might have a bricked device.
My device had a corrupt build.prop, so it was not able to boot the system partition at all. On the screen, it was stuck on the initial boot logo screen with the "Powered by Android" logo.
1) Download the above posted package for 2 assets: a) PAC file containing the stock firmware, and b) drivers for the SPD interface of the device
2) For a non-4G device which I had, I went to spdflashtool.com to download the Research Tool. This will allow you to flash firmware onto a non-4G device.
3) Ensure you have enough disk space (~3-4GB) on the same partition as the Research Tool app.
4) Open Research Tool and load the PAC file.
5) Follow the .doc file in the posted package for wiring up the USB interface to the SPD interface. Essentially, you are connecting USB to the 8-pin header on the device, and accessing data via the UART pins. Pin 1 on the 10-pin connector needs to be grounded in order to get the device into the mode for flashing.
6) Press start on Research Tool, and once completed, you should have a freshly flashed device
Hi, I have the same problem being stuck on Powered by Android logo.
I tried this technique without any success, I have a S3, 4G+Wifi version. Any idea how to solve this problem ? Thanks !
super_paws said:
Thanks to everyone that helped! I have a working unit again!
Figured I'd write a few things here to help anyone else that might have a bricked device.
My device had a corrupt build.prop, so it was not able to boot the system partition at all. On the screen, it was stuck on the initial boot logo screen with the "Powered by Android" logo.
1) Download the above posted package for 2 assets: a) PAC file containing the stock firmware, and b) drivers for the SPD interface of the device
2) For a non-4G device which I had, I went to spdflashtool.com to download the Research Tool. This will allow you to flash firmware onto a non-4G device.
3) Ensure you have enough disk space (~3-4GB) on the same partition as the Research Tool app.
4) Open Research Tool and load the PAC file.
5) Follow the .doc file in the posted package for wiring up the USB interface to the SPD interface. Essentially, you are connecting USB to the 8-pin header on the device, and accessing data via the UART pins. Pin 1 on the 10-pin connector needs to be grounded in order to get the device into the mode for flashing.
6) Press start on Research Tool, and once completed, you should have a freshly flashed device
Click to expand...
Click to collapse
there is a complete instruction.
You're doing something wrong.
Write what and how you do
Guys, after trying an update of firmware, display went blank(led light still on). Now, it is working, but no image on screen.
Tried my old firmware, could not see on screen the process of updating, but how usb was flashing and screen light was going on and off, I presume it was updating.
Anyway, where to find a display config file for this platform? I tried to update couple of display config files from internet, but non of them is working. Maybe someone know for this msm8953 platform how to revive the image on screen and to make it work. Many thanks in advance
Try a full reset from recovery mode. Look this video (maybe help you). Recovery mode