Related
So I am trying to follow the instructions found on the wiki (I'd like to it but the forums are preventing me from posting URLs at the moment) for installing Android on my HTC AT&T Tilt device and I was wondering, where do I download the system.img for Android from? I've been searching around online and cannot find it anywhere...
Many Thanks,
~Jeff
www.androidonhtc.com should have everything for your device
more specifically http://www.androidonhtc.com/wiki/Latest_Builds_(Kaiser) for kaiser http://www.androidonhtc.com/wiki/Latest_Builds_(Polaris) for polaris and http://www.androidonhtc.com/wiki/Latest_Builds_(Vogue) for vogue
R3TR3C said:
should have everything for your device
Click to expand...
Click to collapse
Thanks, I had downloaded the files from that page. It was just confusing because the step by step reads like you need to download a system.img from somewhere when this file in generated when you install Android. Got it loading... Now on to figuring out why it won't boot!
~Jeff
JeffHoogland said:
Thanks, I had downloaded the files from that page. It was just confusing because the step by step reads like you need to download a system.img from somewhere when this file in generated when you install Android. Got it loading... Now on to figuring out why it won't boot!
~Jeff
Click to expand...
Click to collapse
What do you mean when you say "won't boot"? Does your phone show the Linux logo and rolling text, does it show a boot logo animation. Give us some hints and we'll try and sort this out for you.
edit: I see you started another thread, I guess you are working out your issues in that one instead.
binlabin said:
edit: I see you started another thread, I guess you are working out your issues in that one instead.
Click to expand...
Click to collapse
Yea, sorry. One issue for one thread. Keeps things more organized.
~Jeff
linux logo and scolling txt
well, i will hijack her thread since i am at that point.
i did follow the wiki and downloaded the files for the kaiser. i looked at the files and noticed a zimage but no system img file. do i need to compile the package on my linux box then put it on the sd card to run the haret file?
System.IMG/SQSH is deprecated. Use a androidinstall.tar build such as myn warm android. Everything there work including BT and camera.
As thebulletfromhell said, the system.img/sqsh file method of installing Android is now very outdated, and the more mature builds are using the Androidinstall.tar method, this method has several advantages, a menu driven installer, easier updating, greater stability, less problems caused by mis-matched rootfs/system/zimage files.
The two main builds at the moment are; Myns Warm Donut : http://forum.xda-developers.com/showthread.php?t=619980
And Polyrhythmics Eclair 2.1 : http://forum.xda-developers.com/showthread.php?t=600154
Both of these are probably the best supported and most widely used ports to Kaiser hardware.
There are other builds of course, but as a newer user of android I'd recommend these two first.
Hello. I had some troubles running Android on my HTC TyTN II.
The system boots but I see on the console an error message saying "can't find system.img" or something similar.
I downloaded the latest versions of everything but androidinstall.tar is not enough.
i have same problem
Its due to the kernel's Sys & Data boot parameters. Just use any of the newer kernels which carry support for both NAND and SD
Hi guys im unsure if you would call me a noob since ive been playing with androids and custom ops for a while, however my girlfriend purchased an lg d855 (stock as a rock)and "all of a sudden" it failed to reboot, now from what i have found it appears to be quite unusual for this to happen but common for the os to crash into a boot freeze or boot loop, i have no complete load of download mode, it comes up with the little blue dots and the picture of the phone or whatever the symbol is. i can get it into fastboot for use with the adb or fastboot apps, i have obtained the stock LAF.img for the 32gb variant, the issue is that after the phone is connected and ready to send operations
i send the command
c:\adb\fastboot erase recovery >
erasing recovery>
FAILED <remote: failed to erase partition>
and on the phone it says
<start>
fastboot: processing commands
fastboot: getvarartition-type: recovery
fastboot erase: recovery
partition getsize 16777216 bytes
erasing card: 0x48000:0x8000
error: command never completed
error: command timeout error
error: command completed with errors
failed to send erase grp start address
mmc erase failed
<end>
so the question, what the hell does that mean, also if i try other commands it also failes to complete them such as erasing the laf file and or replacing it, i feel like i am mostlikely not the only one with this issue, i do have all the correct drivers installed, using the adb that i have which is 1.3 and one that comes with a kit of the sdk tools and all that, i feel like it is a phone issue more than computer as its failing to erase the mmc, i am wondering if there is other commands i could put in the phone to figure this out or if anyone knows what it all means i would greatly appreciate any help Thanks guys an gals.
iv tried also to load a custom recovery but cant do that because it comes up with incomplete bootloader on the phone, is anyone even able to help? i have no idea what the hell i am doing and nobody seems interested to try and help me.
Same problem here
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
ferreirix said:
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
Click to expand...
Click to collapse
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
tallman43 said:
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
Click to expand...
Click to collapse
I can start to see the light with the tuto you recommended thank you so much !
Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile
Nice! Can you provide a dump from /system and /boot maybe?
BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?
Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?
I will do
Edit: OK, see if there will be an answer.
Thank you flo1k!
I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?
ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?
Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.
The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.
I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work
These are great news!
"Which ones do you need?"
Probably all of them
Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!
Someone was "helping" me root my Mi Mix2. I can't be 100% sure what went wrong, but he managed to get it stuck in Fastboot mode, such that no matter what I do (i.e. any combination of power offs, or simultaneous button presses, or commands from terminal). I suspect he did not understand me when I said Magisk was tool best suited...he may have used some more familiar or standard tool like SuperSU or something to try and root.
Assuming I have sufficiently described my problem, is there anything I can do to get the phone back into a usable state?
Is your bootloader unlocked? If yes try to flash ROM using miflash tool.
I appreciate the response/suggestion.
fotocreaman said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes. I double checked with "fastboot oem device-info" commmand
fotocreaman said:
If yes try to flash ROM using miflash tool.
Click to expand...
Click to collapse
On your advice I did that, including downloading current (?) version and current(?) version of stock ROM. I received a message to effect that a flash script (.bat) file was missing (or at least not found).
Other threads regarding this error suggest unzipping something (?) twice but I didn't see a file inside the original zip file that could be additionally unzipped, and certainly nothing with a .bat extension.
Can you put here the exact error message and when it exactly occurs? Describe the steps you did to get to that point
Hi aa040371
1- download fastboot rom for your phone and unzip it twice , put folder in C:\ storage http://update.miui.com/updates/v1/fullromdownload.php?d=chiron_global&b=F&r=global&n=
2- Look at the tutorial to use miflashtool https://c.mi.com/thread-1857937-1-1.html
regards
I'm Still Here...
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
aa040371 said:
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
Click to expand...
Click to collapse
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
HrX said:
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
Click to expand...
Click to collapse
Hello...thanks. I definitely don't care about MIUI...in fact the whole exercise I am struggling through is so I can get LineageOS onto my phone. I've probably read 50+ threads/posts on 6-7 different forums regarding unbricking/unlocking/rooting/TWRPing/customROMing my particular phone, but this is the first time I've seen mention of DM-Verity. I'll look into it...not really hopeful, though. But anyway...thanks again.
I have a g710pm with a v35 unlocked bootloader that is completely dead I use qfil to fix but keep getting error fh_gpt_header is 0 any ideas?
Yeah obviously the gpt headers can't be read (for some reason, probably they were 'erased' by doing 'chip erase').
Before qfil can show you any partition info, you have to find the gpt headers for your rom variant / version, then flash them to the device.
If u don't find them, use kdz extractor to get them, assuming you have a rom that has a kdz available.
Not sure what info is in the guides thread here for G7, but the G8 guides thread has some great info for doing things like this.
cheers