Related
Has any one of you guys here successfully compiled and booted up a kernel for the A31s? I downloaded and installed the toolchain already, and decided to cobble up one out of curiosity (and partly to get a Dragonrise USB joystick to work on my device), but I'm at a bit of a loss as to how to build one. I know there are instructions at Linux-Sunxi, but there doesn't seem to be a specific guide on the 32, only for A23, A20 and the A1x.
I made some progress on this but got stuck
blakegriplingph said:
Has any one of you guys here successfully compiled and booted up a kernel for the A31s? I downloaded and installed the toolchain already, and decided to cobble up one out of curiosity (and partly to get a Dragonrise USB joystick to work on my device), but I'm at a bit of a loss as to how to build one. I know there are instructions at Linux-Sunxi, but there doesn't seem to be a specific guide on the 32, only for A23, A20 and the A1x.
Click to expand...
Click to collapse
I was able to make a little more progress. I was able to download the sdk, whose link I cannot post because I am a new user, and successfully downloaded and built a stock image but when I use the pheonix suite to update the tablet it just hangs.
I suspect that hardware is different from what is available with the stock SDK and tried to build my own target but that did not work either. Any help or pointers would be great. Even an explanation as to why the pheonix suite update too hangs at the beginning of the update process.
obsktr said:
I was able to make a little more progress. I was able to download the sdk, whose link I cannot post because I am a new user, and successfully downloaded and built a stock image but when I use the pheonix suite to update the tablet it just hangs.
I suspect that hardware is different from what is available with the stock SDK and tried to build my own target but that did not work either. Any help or pointers would be great. Even an explanation as to why the pheonix suite update too hangs at the beginning of the update process.
Click to expand...
Click to collapse
I made some progress with the SDK too, and in my case I used the Fiber-3G target for Android along with the a31s kernel config. Both SDKs work, but my probs with the aforementioned SDKs is that they're riddled with issues - RTC isn't persistent in SDK 3.3, besides the LCD displaying funky coloured spots in some high-contrast areas. SDK 4.5 could've been perfect if it wasn't for the screen turning white whenever I put the tab to sleep.
I'd like to extract the kernel config on the one that came with my tab, but the problem here is that it didn't came with config.gz support, and my question here is that will extract-ikconfig work on those kernels?
blakegriplingph said:
I made some progress with the SDK too, and in my case I used the Fiber-3G target for Android along with the a31s kernel config. Both SDKs work, but my probs with the aforementioned SDKs is that they're riddled with issues - RTC isn't persistent in SDK 3.3, besides the LCD displaying funky coloured spots in some high-contrast areas. SDK 4.5 could've been perfect if it wasn't for the screen turning white whenever I put the tab to sleep.
I'd like to extract the kernel config on the one that came with my tab, but the problem here is that it didn't came with config.gz support, and my question here is that will extract-ikconfig work on those kernels?
Click to expand...
Click to collapse
Could you share how you got the SDK to work? Did you just do a stock build of fiber-3g. What compiled did you use? Did you use the pheonix suite to install the image?
Seedy
obsktr said:
Could you share how you got the SDK to work? Did you just do a stock build of fiber-3g. What compiled did you use? Did you use the pheonix suite to install the image?
Seedy
Click to expand...
Click to collapse
Yeah, all I did was to use fiber-3g, provided that you already cooked up a kernel, and yes I did use Phoenixsuit for flashing it. The tutorial at https://olimex.wordpress.com/2014/0...d-4-2-2-for-a20-olinuxino-micro-from-scratch/ should work, though since it's for the A20 you do need to change some specific parts in it. Let me know if you come across some hurdles, dude, I'll see what I can do with it.
blakegriplingph said:
Yeah, all I did was to use fiber-3g, provided that you already cooked up a kernel, and yes I did use Phoenixsuit for flashing it. The tutorial at .. should work, though since it's for the A20 you do need to change some specific parts in it. Let me know if you come across some hurdles, dude, I'll see what I can do with it.
Click to expand...
Click to collapse
Thanks for the link. It is very similar to the PDF file that came with the SDK, but did not work at all. I have tried building with 3 different combos: fiber_3g, fiber_w02 and fiber_a31st with the same problem. I do get an image file after the build which is placed in the lichee/tools/pack_brandy/, but when I use phoenixsuite to flash it, it just says it will take 0 minutes and then hangs there.
Pheonix suite detects my board with the following model: fiber_wifibt_mtk and I cannot find this model when I run lunch. I tried creating a spec for it and changing the target name to match but that did not work. My rational was that perhaps pheonix suite saw a model mismatch and then stopped but I guess something else is wrong.
Any help or tips would be grate
Hmm, are the drivers for Phoenix properly installed? Can you flash a stock image, or at least a known working image to your device?
Got a new firmware update tonight. Tablet seems faster now. Anyone else get it? Glad to see they are still updating this tab.
can't update.
i got error on installing update.
please help me.
i also got the update
waingro808 said:
Got a new firmware update tonight. Tablet seems faster now. Anyone else get it? Glad to see they are still updating this tab.
Click to expand...
Click to collapse
i also got the update on my dell venue 7 3740. but it disabled the fastboot, now i cant root it.
Got it as well. Seems snappier. I would like to know what got updated? Kernel tweaked again?
As far as the problem your having golfyrider, reboot them just keep selecting system update under "about tablet" eventually it will download.
It's still 4.4.4 and the source code hasn't shown any signs of change yet either. Still can't pull the boot.img or recovery.img from the device, having trouble splitting the ones from hharte, still no email replies yet, kinda hate to think my email yesterday caused this as this isn't an answer to my questions, I'm just not stoked about an update that is basically the same as previous, going to snatch it and post it for those who think it's worthy of an update. excuse this rant, been sweating out my days and nights trying with this tablet, not going to stop, just isn't much of an update to me. Sound is still distorted, which really grinds my gears. ... ok, I feel an insey bit better. thanks 4 reading my O.
justlovejoy said:
It's still 4.4.4 and the source code hasn't shown any signs of change yet either. Still can't pull the boot.img or recovery.img from the device, having trouble splitting the ones from hharte, still no email replies yet, kinda hate to think my email yesterday caused this as this isn't an answer to my questions, I'm just not stoked about an update that is basically the same as previous, going to snatch it and post it for those who think it's worthy of an update. excuse this rant, been sweating out my days and nights trying with this tablet, not going to stop, just isn't much of an update to me. Sound is still distorted, which really grinds my gears. ... ok, I feel an insey bit better. thanks 4 reading my O.
Click to expand...
Click to collapse
Take a look at the kernel source for the 7840 it has a py script intended to unpack / pack the unsigned images a small modification can be made to the script to take into account the Sig . if you wanna better idea of the Intel image assembly I suggest at signing up for the baytrail bsp from wind river or other vendor.
If your on windows this might unpack the signed image and repack as a unsigned image so you'll need the boot loader unlocked.
https://www.androidfilehost.com/?fid=95864024717073970 AndImgTool_1_3_0.rar
https://www.androidfilehost.com/?fid=95864024717071926 xImgTool_1_3_32.rar
social-design-concepts said:
Take a look at the kernel source for the 7840 it has a py script intended to unpack / pack the unsigned images a small modification can be made to the script to take into account the Sig . if you wanna better idea of the Intel image assembly I suggest at signing up for the baytrail bsp from wind river or other vendor.
If your on windows this might unpack the signed image and repack as a unsigned image so you'll need the boot loader unlocked.
https://www.androidfilehost.com/?fid=95864024717073970 AndImgTool_1_3_0.rar
https://www.androidfilehost.com/?fid=95864024717071926 xImgTool_1_3_32.rar
Click to expand...
Click to collapse
Thanks for the tools that'll hopefully help a great deal. I've played with the 7840 kernel code for two days and still was left with a non-flashable boot.unsigned.img, I truly appreciate any help I can get with this. I've tried like 5 different device tree cobinations and probably more than that. Hopefully this will truly bring a light for a breakthrough. Thanks a million social-designs-concepts
Here's the update zip that this thread is based off of:
incremental4.4.4update.zip - 24.09 MBBe advised though, this is a direct download from OTA and unmodified by me other than the name of the zip.
It will temporarily disable your root and does something funky to the button combo of down and power to get into bootloader mode (I used adb reboot bootloader-perfect) but if you already obtained root, you can get it back. theres a couple patches and 3 or 4 libs added. other than that? IDK you check it, lol.
It's good your tablet is still getting updates, the 3830, and 3730 hasn't received any updates since 4.4.2.
Lollipop is suppose to start rolling out to the Venue xx40 series on Tuesday April 21st, I suspect this is a preliminary update to make the device work for lollipop. The 3x30 saw similar small updates days before the JB to KK update.
@vampirefo maybe we'll luck out and get Lollipop too, the 3x30 was suppose to get 4.4.4 and it's yet to be seen so maybe they scrapped working on 4.4.4 when Intel did the 360 on supporting 32bit ART and Clovertrail Plus. Though not going to hold my breath. You also might wanna try building cm12 since the 3830 has an unlocked bootloader , they seem to be making progress with it on a couple of other Redhookbay devices.
social-design-concepts said:
Lollipop is suppose to start rolling out to the Venue xx40 series on Tuesday April 21st, I suspect this is a preliminary update to make the device work for lollipop. The 3x30 saw similar small updates days before the JB to KK update.
Click to expand...
Click to collapse
You sure about that? I only saw the 7840 mentioned on Dell's support site for the Apr 21 update to Lollipop.
waingro808 said:
You sure about that? I only saw the 7840 mentioned on Dell's support site for the Apr 21 update to Lollipop.
Click to expand...
Click to collapse
I saw it in a 3740 thread and the 7840 all three devices are merrifield based tablets and the last email I got from dell legal said it was going to start rolling on the 21st and that at this time they have no word on if or when it would be available for the 3x30 I'd post the email but it full of Dell Private Confidential headings.
social-design-concepts said:
Take a look at the kernel source for the 7840 it has a py script intended to unpack / pack the unsigned images a small modification can be made to the script to take into account the Sig . if you wanna better idea of the Intel image assembly I suggest at signing up for the baytrail bsp from wind river or other vendor.
If your on windows this might unpack the signed image and repack as a unsigned image so you'll need the boot loader unlocked.
https://www.androidfilehost.com/?fid=95864024717073970 AndImgTool_1_3_0.rar
https://www.androidfilehost.com/?fid=95864024717071926 xImgTool_1_3_32.rar
Click to expand...
Click to collapse
This andimgtool is very interesting, works on 3830, changes output boot.img into an img that 7840 packing script can unpack and repack that flashes and works.
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
This andimgtool is very interesting, works on 3830, changes output boot.img into an img that 7840 packing script can unpack and repack that flashes and works.
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
it removes the 480byte signature and corrects the image flag to be unsigned what ever image it was
boot.img wasn't signed, haven't used or seen a signed boot.img since I unlocked the bootloader on this tablet.
pm-cz scripts leave the signature ? Never checked.
Sent from my T1 using XDA Free mobile app
vampirefo said:
boot.img wasn't signed, haven't used or seen a signed boot.img since I unlocked the bootloader on this tablet.
pm-cz scripts leave the signature ? Never checked.
Sent from my T1 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah the uos firmware doesn't validate the sig
social-design-concepts said:
Yeah the uos firmware doesn't validate the sig
Click to expand...
Click to collapse
Alright maybe I am missing a major point if dude are capable of unpacking, repacking and all that good stuff, My question is wtf, why not me? what on earth can i do to get the appropriate file sizes to know where the boot sector is so I can extract it and if need be modify a script that'll allow me to do all of this and re-flash it for testing? the 7840 builds so smooth and I am losing my mind. I feel like theres a whole lot of know how in a small click. Initiate me, make me an apprentice, study buddy. idk I'm loosing my mind. Must have over 20GB worth of trials and errors. I'm going to Google the mentions of sdc from earlier but am really not sure of what I am looking for. If I could get a pm tutor that'd be nice. I can do all the work. But nothing I have tried so far has been acceptable. I'm getting other things done but this is my priority goal. Thanks for helping guys. I'm generous when I got it. I fell so behind in learning the specs of this new device to be successful at what I wanna do with it. There I go again giving reading material for the pooper seat. I need to build and sign a Sig for starts, lol, if momma only knew what I did all day and night now, lol.
thanks again for reading my troublesome O.
Normally I'm just a joy, ROFL, heh
justlovejoy said:
Alright maybe I am missing a major point if dude are capable of unpacking, repacking and all that good stuff, My question is wtf, why not me? what on earth can i do to get the appropriate file sizes to know where the boot sector is so I can extract it and if need be modify a script that'll allow me to do all of this and re-flash it for testing? the 7840 builds so smooth and I am losing my mind. I feel like theres a whole lot of know how in a small click. Initiate me, make me an apprentice, study buddy. idk I'm loosing my mind. Must have over 20GB worth of trials and errors. I'm going to Google the mentions of sdc from earlier but am really not sure of what I am looking for. If I could get a pm tutor that'd be nice. I can do all the work. But nothing I have tried so far has been acceptable. I'm getting other things done but this is my priority goal. Thanks for helping guys. I'm generous when I got it. I fell so behind in learning the specs of this new device to be successful at what I wanna do with it. There I go again giving reading material for the pooper seat. I need to build and sign a Sig for starts, lol, if momma only knew what I did all day and night now, lol.
thanks again for reading my troublesome O.
Normally I'm just a joy, ROFL, heh
Click to expand...
Click to collapse
The 7840 build script is be able to unpack and repack your boot.img, don't know if it will boot on your tablet as I don't have your tablet and not interested in it, I did download a 3840 boot.img, unpacked and repacked boot.img flashed to my tablet just to see if it would flash, and it does flash without any problems, wont boot cause my tablet is a 3830.
Below is flashing same boot.img on my iview i-700 same results as 3830 both will flash the boot.img but neither can boot from image.
Code:
fastboot flash boot '/home/vampirefo/Desktop/dell-venue-boot-tools-master-3840/boot_script/Vamp_packed_boot.img'
target reported max download size of 1324206762 bytes
sending 'boot' (9610 KB)...
OKAY [ 1.402s]
writing 'boot'...
OKAY [ 1.073s]
finished. total time: 2.475s
[email protected]:~/Desktop/dell-venue-boot-tools-master-3840/boot_script$
I have uploaded image here http://www.mediafire.com/download/xbmq8h6c12l55tr/Vamp_packed_boot.img
justlovejoy said:
Alright maybe I am missing a major point if dude are capable of unpacking, repacking and all that good stuff, My question is wtf, why not me? what on earth can i do to get the appropriate file sizes to know where the boot sector is so I can extract it and if need be modify a script that'll allow me to do all of this and re-flash it for testing? the 7840 builds so smooth and I am losing my mind. I feel like theres a whole lot of know how in a small click. Initiate me, make me an apprentice, study buddy. idk I'm loosing my mind. Must have over 20GB worth of trials and errors. I'm going to Google the mentions of sdc from earlier but am really not sure of what I am looking for. If I could get a pm tutor that'd be nice. I can do all the work. But nothing I have tried so far has been acceptable. I'm getting other things done but this is my priority goal. Thanks for helping guys. I'm generous when I got it. I fell so behind in learning the specs of this new device to be successful at what I wanna do with it. There I go again giving reading material for the pooper seat. I need to build and sign a Sig for starts, lol, if momma only knew what I did all day and night now, lol.
thanks again for reading my troublesome O.
Normally I'm just a joy, ROFL, heh
Click to expand...
Click to collapse
Which device 3840 Correct? And you already unlocked the BL?
social-design-concepts said:
Which device 3840 Correct? And you already unlocked the BL?
Click to expand...
Click to collapse
LOL, yeah, if he hasn't unlocked his bootloader, he just been wasting his time. :good::good:
my 3840 has updated ......... it seem faster?
No difference. :silly:
Hi,
I followed your instructions, but my God damned Windows 8.1 doesn't see my God damned Android 4.4.2, so I "adb devices" command -- pc doesn't see my Android. "file transfer (MTP) files" command is useless.
Is there any of you in the whole wide world could help me?
My phone is in recovery mode can't boot stuck in boot loop.
Nobody answeres. This is said to be the best geeks' forum.
Sorry, I am disappointed, fed up, etc. as none of you give a damn about my f***ing problem.
Thx if any...
You could try using the latest adb and some universal driver ***,
but not much use from ADB really, if it has a stock recovery Then also
making update zip s could be problematic... signing...
Best to try contacting the manufacturer or seller, what ever, and try to get the firmware + tools.
http://smartnavon.eu/
http://hungaroflotta.hu/page-7.html
http://hungaroflotta.hu/contact.html
If no luck, try to find out its soc. You could even try to open the damn thing...
Or just assume it's a MTK. If so -> MTK drivers, DroidTool, Wwr, SP_FlashTool, etc..
and make a backup. Worked ok? Good! Now find someone having the same piece of...
and ask her to do the same and share his system...
Good luck! :fingers-crossed::good:
*** For example this installer of mine. Contains universal adb driver and adb/fastboot downloader
https://forum.xda-developers.com/an...taller-universal-adb-driver-package-t3595277/
Thx 4 UR reply!
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Don't open it yet! :laugh: I did a bit more searching. It's a MT6572. This "dazexy" fellow
most likely can help if you cannot get that factory firmware.
http://forum.gsmhosting.com/vbb/f29...nfinity-box-725574-post10962286/#post10962286
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...rum.gsmhosting.com/vbb/10962286-post1173.html )
At least he helped "kaller1" at the same forum.... see the second post here.
(if needed you can find kaller1's email by clicking his paypal donate button)
http://forum.gsmhosting.com/vbb/f82...nck-dongle-1314877/index147.html#post11354667
(gsmhosting is not working at the moment, so here is the page at google's cache:
http://webcache.googleusercontent.c...d-phones-via-nck-dongle-1314877/index147.html )
Some more helpful people having d402??
https://mobilarena.hu/tema/navon_mizu_d402/hsz_1-50.html
So no worry, I think your problem will be solved. :highfive: (Hopefully...)
(if it is that Navon Mizu D402, as I assumed because of this post
https://forum.xda-developers.com/showthread.php?t=3501143 )
edit: gsmhosting works again. The second link (kaller1) updated to be more accurate.
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Here is another fellow who gives a damn. "donrico" is sharing the full rom here
http://forum.gsmkabelek.com/showthread.php?28404-navon-d402-rom&p=250246&viewfull=1#post250246
Because that 4shared site is a bit nasty, i copied it to mega, here
https://mega.nz/#!v4MgVIbJ!htsUcjHSrwwGIDuTeNRMAXKhxZOvVxJ8mnY3vMZoVks
Taking a full backup first might be a good idea.
SP_Flashtool should do the trick. You probably
can use the scatter file from that rom dump.
Or make your own: https://forum.hovatek.com/thread-21970.html
Nikkka said:
Thx 4 UR reply!
Click to expand...
Click to collapse
Sub forum changed... Okay, let us continue here if needed.
Though you should be able to fix that damn thing now...
:victory:
Thank you so much for making such a hard effort to help me! ?
I'll do my best and will keep you informed.
Partitions "nvram" and in in my case also "pro_info" are important backups.
Nvram contains IMEI values etc... anyway it can be important to save it/them.
And pro_info might have some extra values defined in it. At least if the device
has some faked firmware showing wrong hardware values like in my case.
Then there might be some real values needed, defined there along with the faked ones...
I'm no MTK expert but managed to fix my tablet by restoring those partitions...
Ehh!
I've read all the info you linked. ????
OMG!
Well, I guess that I should download the rom.
After that do I have to do all the instructions?
How will my pc be able to see my phone?
I need no data backup.
I swear I got in touch with the store in which I bought the data cable and asked if it is really a data cable and not just a charging one.
I can do anything I just need to know the steps to be taken one by one.
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Nikkka said:
Ehh!
1. After that do I have to do all the instructions?
2. How will my pc be able to see my phone?
<snip>
3. There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Thanks for your kind reply in advance!
Click to expand...
Click to collapse
1. I can relate your "shock". That Wwr route isn't the easiest one, I can imagine.
Haven't done it myself. Maybe that SP_FlashTool + scatter file is enough for
the backup. If you have those IMEI numbers saved you probably can skip
the backup, but as I said I'm no expert, so you might want to do some
Googling before deciding anything...
2. Install the MTK drivers (search). any tool will need them too.
3. IDK. Maybe someone else has an answer to this?
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Nikkka said:
Ehh!
There is no way to see the system files on my dead phone to be able to delete the rest files of SELinuxModeChanger?
Click to expand...
Click to collapse
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
CXZa said:
Checked. The stock recovery doesn't use test keys, so making update zip is not possible.
Click to expand...
Click to collapse
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
CXZa said:
Checked SELinuxModeChanger's info - and its source code too.
It shouldn't do any writing that factory reset wouldn't remove.
https://forum.xda-developers.com/showthread.php?t=2524485
Easiest would be that the vendor would give you a full OTA/recovery update zip package.
(Not such that just patches the old one. ) That most likely would fix it.
Click to expand...
Click to collapse
Yep. Thanks.
Well, actually the antivirus Zemana asked if I wanted to make SELinuxModeChanger a part of the system/a system file. I agreed. I made the wrong decision. I used ES File Manager to delete SELinuxModeChanger. Well, I succeeded in half... but failed to delete it from all system maps and couldn't reinstall it again. Rebooted... The rest is history...
I guess phone thinks that it has a corrupted system and that's why it doesn't boot.
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Nikkka said:
Navon... They never ever update. No system security patches ever.
Actually, 1 yr ago I had a problem nobody was able to help. I was advised to take my phone to Navon asking for refurbishing. I had no money and I wanted to fix the problem myself anyway. It took a year, but I found out how to fix it. ES File Manager was the key.
Click to expand...
Click to collapse
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
h t t p s://w w w . getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
(Bad site, sorry. While the info in this article might be ok, all at this site is not.
So better to search if the info can be found elsewhere.)
+ lots of more similar articles + videos. Almost too much really...
CXZa said:
Yes I have seen that post. For "fun" I added the fota values from your build.prop to
my tablet and installed the apks needed for the OTA update. The OTA server
http://adups.cn didn't respond. It seems that the programs needs to be
updated or they don't provide updates for the older models...
Something to read....
How to use SP Flash tool to backup Mediatek firmware
https://forum.hovatek.com/thread-526.html
How to Flash Stock Rom using Smart Phone Flash Tool
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
How to Flash IMEI
https://androidmtk.com/use-sn-write-tool
How to Backup and Restore IMEI/ NVRAM data on Mediatek Chipset Android Device
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek/
+ lots of more similar articles + videos. Almost too much really...
Click to expand...
Click to collapse
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
I guess it will be a hard effort to make my phone work again. I seem to give it up. Unfortunately, sending the phone to Navon for refurbishing... would cost too much and phone must be sent by post (!!!). It is a great phone, but customer service at Navon is...
Nikkka said:
It came across my mind that 1 yr ago my phone was rooted also. Do you think that having my phone rooted makes Recovery Mode especially Factory Reset disabled?
Unfortunately twrp is not compatible with KitKat.
Click to expand...
Click to collapse
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Nikkka said:
I guess it will be a hard effort to make my phone work again.
Click to expand...
Click to collapse
Maybe not that hard if you're able to connect to PC... but..
(it looks like that at the moment I cannot make a connection either, LOL
re-installing the drivers probably fixes it, IDK, have to check it some day... )
---
That OTA update needed (at least) one program more (to be run as a service).
Did that too. And I also disabled the firewall that was blocking the connection. :laugh:
It just says that my system is up to date. (Changing version numbers etc. doesn't help).
The server response hints to http://europedownhw.mayitek.com/ site
that seems to be dead...
Navon...
https://forum.hovatek.com/thread-25956-post-155741.html#pid155741
Oh yeah? http://smartnavon.eu/smartphones/navon-t503 (not even an old model)
https://logout.hu/bejegyzes/cappa72/sp_flashtool_readback_kiolvaso_opcio_hasznalata_gy.html
https://itcafe.hu/tema/android_dual_sim_ket_sim_okostelefonok_topikja/hsz_16132-16132.html
[QUOTE
CXZa said:
I don't think that rooting is causing it. How do you know that
Factory Reset doesn't work?
You have a twrp for it? Older one, or what do you mean?
Factory Reset doesn't work. I mean that in Recovery Mode it doesn't matter how many times I do Factory Reset nothing happens.
I have no twrp. Only KingRoot was able to root my phone. TWRP said my phone not compatible with it.
Click to expand...
Click to collapse
Nikkka said:
Thank you so much for your trying to help me!
I guess I need some time to let it go for a while.
Click to expand...
Click to collapse
While you're are letting go, you could read some stuff linked below. Good
instructions. What to do and what not to do. (Unlike at that "getdroidtips"
site I linked earlier. Some of the tips and articles there are total rubbish.
Mixed stuff copied somewhere else, I guess. Some might work, but not all.
Also they use wrong words in article names to get better Google rankings.)
SP Flash Tool + MediaTek MT65xx drivers download and installation guide including bricked devices
Download MTK Drivers (32 & 64 bit) XP Vista Win7 Win8
Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Drivers installation tutorial (Might be useful with win8 too.)
Download SP Flash Tool v3 & v5 – Latest versions ( Tip: read to the end)
Remove, Disable & Uninstall MTK USB Drivers and inactive COM Ports – USBDeview (if having driver problems)
(And I also sent you some info in Hungarian already in the previous post. Backup etc.)
Again. just for fun sake, I tried again if my MTK tablet/phone would be recognized by SP flash tool.
No luck. Previously it wasn't a problem. Still, the adb/fastboot works okay.
So, some problem with MTK drivers. I have used SP_Flashtool, BeTools,, even older ones
like WiseLinkTool. And maybe some that were between those two.
Well, I don't have any good reason to fix those driver problems at the moment,
everything works ok, but still it kind of sucks.
Anyway adb/fastboot works okay. And that is the problem mentioned originally in the title.
So, does the fastboot work?
With fastboot, if it works, you might be able to boot some modified recovery without flashing and then maybe do some backups etc.
My adb driver package, mentioned in my signature has some options to remove the
old adb installations and the old (maybe problematic) values from the registry...
USBDeview is better choice in some situations though...
Hey guys, how's it going? I have run into a problem that I have never faced on a previous Pixel device in the past. Usually, you can download the factory images from Google's site, run the flash-all.bat/flash-all.sh, and start fresh with the latest images. However with the Pixel 6, it just results in a bootloop for me regardless if I force a factory reset or not. I have tried on both Windows and Linux Mint with the same result. I have tried:
Formatting before running flash-all.sh = bootloop
Formatting after flash-all.sh by directly booting into recovery = bootloop
Running flash-all.sh, rebooting directly to fastboot, then disabling verity and verification = bootloop.
The only way I have gotten it to work is by using Google's online Android Flash Tool and selecting: wipe, disable verity, and disable verification (which I have done manually with an unsuccessful result).
Has anyone manually flashed firmware (not the OTA) without getting a bootloop?? I'm starting to think they have uploaded courupted files or something. I've downloaded them multiple times to be sure it wasn't bad on my end. It's got me seriously scratching my head. Again, I have been doing the same with each previous Pixel for years now, so I don't know what the deal is.
jal3223 said:
Hey guys, how's it going? I have run into a problem that I have never faced on a previous Pixel device in the past. Usually, you can download the factory images from Google's site, run the flash-all.bat/flash-all.sh, and start fresh with the latest images. However with the Pixel 6, it just results in a bootloop for me regardless if I force a factory reset or not. I have tried on both Windows and Linux Mint with the same result. I have tried:
Formatting before running flash-all.sh = bootloop
Formatting after flash-all.sh by directly booting into recovery = bootloop
Running flash-all.sh, rebooting directly to fastboot, then disabling verity and verification = bootloop.
The only way I have gotten it to work is by using Google's online Android Flash Tool and selecting: wipe, disable verity, and disable verification (which I have done manually with an unsuccessful result).
Has anyone manually flashed firmware (not the OTA) without getting a bootloop?? I'm starting to think they have uploaded courupted files or something. I've downloaded them multiple times to be sure it wasn't bad on my end. It's got me seriously scratching my head. Again, I have been doing the same with each previous Pixel for years now, so I don't know what the deal is.
Click to expand...
Click to collapse
Might be a problem with your setup. I don't have a Pixel 6 / Pro so I can't confirm this, but I've had zero issues with the factory images on my Pixel 5. Others in this forum have used the factory images with no problems.
Disabling verity/verification is no longer necessary if you're rooting with Magisk.
V0latyle said:
Might be a problem with your setup. I don't have a Pixel 6 / Pro so I can't confirm this, but I've had zero issues with the factory images on my Pixel 5. Others in this forum have used the factory images with no problems.
Disabling verity/verification is no longer necessary if you're rooting with Magisk.
Click to expand...
Click to collapse
I've never had any issues with any other Pixel devices (granted, the latest device I have other than the Pixel 6 is the Pixel 4XL).
Do you have any advice on making sure my setup is correct? I mean, I tried in both Linux and Windows. It should be an all in one package in either environment though I would think.
I may try again in Linux to see what happens after a fresh download.
jal3223 said:
I've never had any issues with any other Pixel devices (granted, the latest device I have other than the Pixel 6 is the Pixel 4XL).
Do you have any advice on making sure my setup is correct? I mean, I tried in both Linux and Windows. It should be an all in one package in either environment though I would think.
I may try again in Linux to see what happens after a fresh download.
Click to expand...
Click to collapse
Have you tried a different USB cable? Are your platform tools and drivers up to date? I assume the bootloader is unlocked, otherwise you wouldn't be able to flash a factory image.
interesting.... i haven't manually flashed the whole image because the web installer is soo easy! I have just recently flashed the radio (had signal issues on december update so i tried the november radio) And it went fine.
Edit: I would maybe see if you have the newest version of ADB
thewraith420 said:
interesting.... i haven't manually flashed the whole image because the web installer is soo easy! I have just recently flashed the radio (had signal issues on december update so i tried the november radio) And it went fine.
Edit: I would maybe see if you have the newest version of ADB
Click to expand...
Click to collapse
Doesnt the firmware come with its own platform tools within the firmware zip? I was thinking it was a self contained package. At least on Windows.
jal3223 said:
Doesnt the firmware come with its own platform tools within the firmware zip? I was thinking it was a self contained package. At least on Windows.
Click to expand...
Click to collapse
No, Not at all. whats in the zip is several image files and a flash-all.bat for windows and flash-all.sh for linux. the .sh and .bat files are just scripts that send commands to adb and fastboot to flash the phone. If you open the bat or .sh file in a text editor you can actually see the commands it issues. It is all reliant on ADB and Fastboot being correctly installed.
thewraith420 said:
No, Not at all. whats in the zip is several image files and a flash-all.bat for windows and flash-all.sh for linux. the .sh and .bat files are just scripts that send commands to adb and fastboot to flash the phone. If you open the bat or .sh file you can actually see the commands it issues. It is all reliant on ADB and Fastboot being correctly installed.
Click to expand...
Click to collapse
Ah, for some reason I was thinking it had platform tools in it. I'll double-check and try to update everything on Windows. On Linux I definitely have everything updated though. Thank you for the advice.
jal3223 said:
Ah, for some reason I was thinking it had platform tools in it. I'll double-check and try to update everything on Windows. On Linux I definitely have everything updated though. Thank you for the advice.
Click to expand...
Click to collapse
if you continue to have trouble with the flash-all you can open it with a text editor and use it as a guide to flash the firmware manually. It'll at least give you an idea why the flash-all fails. I just took another looks at the script and looks like i forgot that the factory image only uses fastboot not adb. Looks like i have fastboot version 28.0.2.... looks like that means i'm a bit behind lol its up to 31.0.3
thewraith420 said:
if you continue to have trouble with the flash-all you can open it with a text editor and use it as a guide to flash the firmware manually. It'll at least give you an idea why the flash-all fails. I just took another looks at the script and looks like i forgot that the factory image only uses fastboot not adb. Looks like i have fastboot version 28.0.2.... looks like that means i'm a bit behind lol its up to 31.0.3
Click to expand...
Click to collapse
I feel stupid now. I updated to the latest fastboot from google platform tools and it is working now. I really appreciate the advice. It seems it's always the simple stuff that gets overlooked. lol
V0latyle said:
Have you tried a different USB cable? Are your platform tools and drivers up to date? I assume the bootloader is unlocked, otherwise you wouldn't be able to flash a factory image.
Click to expand...
Click to collapse
Thank you as well. I should have made sure things were up to date when you mentioned it earlier.
Trying to follow the various guides to move from A12 DE2118 back to A11 DE2117 (and then on to Lineage or Libre). I'm passing everything through to a Windows VM, but the tools dont see the phone in EDL mode, and neither the google or oneplus drivers seem to help.
I'd really like to just flash this whole puppy with Linux, but I'm getting stuck on a few points. Do I "need" to us MSM? Seems like the answer is no as there is a non-MSM guide here, but it's still windows related. Where are all these image files coming from in the various guides? When I download the images from the mirrors, or OnePlus directly they have a payload.bin, but not the 30+ named .img files I see listed in some of the guides.
Feeling confused, and I know I'm capable of getting this done, I just need someone to help fill in the blanks for me. I "was" able to unlock the bootloader, that's how far I am now. Thanks!
lurkio said:
Where are all these image files coming from in the various guides? When I download the images from the mirrors, or OnePlus directly they have a payload.bin, but not the 30+ named .img files I see listed in some of the guides.
Click to expand...
Click to collapse
https://github.com/ssut/payload-dumper-go will extract .img files for you from a payload.bin. Also supports zip packages that contain payload.bin.
A linux guide is sorely lacking. Would be great if you could document your steps for others.
blueberry.sky said:
https://github.com/ssut/payload-dumper-go will extract .img files for you from a payload.bin. Also supports zip packages that contain payload.bin.
A linux guide is sorely lacking. Would be great if you could document your steps for others.
Click to expand...
Click to collapse
Thanks. And definitely have been along the way.
I'm working through this as well, so feel free to ask questions if you need help along the way, @lurkio. I have lots of linux experience, and like you, this device has been a little confusing for me.
My goal is to go from stock A12 on DE2118 --> LOS19 on DE2117
For this device specifically, all the info we need is here -- it's just a bit hard for me to piece it all together for myself.
Try the drivers I've attached here. I think one of them worked for me for QDL in windows.
Here's some of what I found here on the forums:
justauserthatusesaphone said:
Note: if you're on T-Mo OOS 12, then you have to go back to OOS 11 via MSM tools in order to do this.
Click to expand...
Click to collapse
Looks like the downgrade comes first, then the conversion.
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Click to expand...
Click to collapse
The conversion process in this post worked beautifully for me last year. I was on one of the later stock A11 builds, and carefully followed the guide in the first post.
blueberry.sky said:
https://github.com/ssut/payload-dumper-go will extract .img files for you from a payload.bin. Also supports zip packages that contain payload.bin.
Click to expand...
Click to collapse
+1 for payload-dumper-go. That tool makes it so easy to get the images, and it looks really cool doing it. (And for the Arch crowd like me, it's in the AUR!)
Also, check that you're running the latest ADB/Fastboot. I found a lot of small issues magically disappeared once I was up-to-date. Here are the links to the latest and greatest.
https://dl.google.com/android/repository/platform-tools-latest-LINUX.zip
https://dl.google.com/android/repository/platform-tools-latest-WINDOWS.zip
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Click to expand...
Click to collapse
I haven't tried to downgrade yet, but this guide looks promising. Sideload an APK to device instead of (I'm guessing?) MSM.
---rrryannn--- said:
I haven't tried to downgrade yet, but this guide looks promising. Sideload an APK to device instead of (I'm guessing?) MSM.
Click to expand...
Click to collapse
Let me know if that tool works for you, I get the failed verification on the official OnePlus image or the A11 image that was posted.
I have a separate post about it, but I get stuck at fastbootd. I just didnt have enough luck in linux so I used a VM to get the MSM tool to flash A11 on the device, and that worked. So currently I'm on A11 DE2118, and I need to get to DE2117 to get to Lineage.
If I watch dmesg or the journal I see the phone constantly connecting and disconnecting in fastbootd mode, it's fine in fastboot mode, and all other modes. I might just have to spin up windows on another PC to get this moving. Stuck!