Develop Bugs

ARM Cortex A8 Roms

Hi Guys
looked everywhere for answers, so thought i would ask the best
8 tablet running 2.3.1
ARM Cortex A8
Samsung S5Pv210
Any roms out there????
tried Uberoid no luck
Sorry if this has been asked b4 guys but its driving me mad, stuck on 2.3.1 and cant find a 2.3.7 update anywhere???
Would love Cyanogenmod (got it on my desire) but Uberoid will do ;-)
Thanks in advance
Danny

did you look it there http://www.techknow.t0xic.nl/forum/index.php?topic=95.0 ?
not forget to check anywhere in the site , you will find somethings !!!!!!

Yeah looks good cheers, only issue is the firmware wont update? rom manager just reboots to stock rom, recovery mode gives me message "signiture verification failed" aborting process?? any ideas, is there a program to get around this/
Thanks

fault come to recovery tools , try to find what your firmware need to woork ..
may be found where you download firmware

bootloader
Well i have found some roms out there, turns out my tablet is a MID816R2 trouble is i think the bootloader is locked? tried to update/install new roms but always get signature verification failed
so it aborts
Rom manager does not show my device so recovery from there aint an option either?
any news guys?

put in the link where you downloaded firmware ..

[SOLVED] MIUI 8 Flashing Error

Hello,
im trying to flash miui 8 on to my one m8 but it keeps saying failed, the error is "this package is for "htc_m8" devices; is is a "m8"". i think the model name changed when i flashed google assistant onto my previous rom, i do not have ant backups as i forgot to make one before i formatted lol, luckily this isnt my mail phone. please help
Thanks.
UPDATE 4/3/17 1:51PM: tried adb sideloading the custom rom i made (modifying it to work with the device model name and i am currently flashing gapps, no errors yet. will see what happens when i try to boot.
UPDATE 5/3/17 10:12AM: i got the miui to flash but upon skipping the insert sim card step the settings app kept crashing so i ended up flashing an the resurrection remix nougat rom and it works fine

twosaltyy said:
Hello,
im trying to flash miui 8 on to my one m8 but it keeps saying failed, the error is "this package is for "htc_m8" devices; is is a "m8"". i think the model name changed when i flashed google assistant onto my previous rom, i do not have ant backups as i forgot to make one before i formatted lol, luckily this isnt my mail phone. please help
Thanks.
UPDATE 4/3/17 1:51PM: tried adb sideloading the custom rom i made (modifying it to work with the device model name and i am currently flashing gapps, no errors yet. will see what happens when i try to boot.
Click to expand...
Click to collapse
pm me with your email and ill send you how can yo do it, i cant place links here

Downgrade Android 8.0 stock to 7.0 stock

Hello to all of you!
I'm a newbie in flashing ROMs... ahaha
I'm trying to install LineageOS 14.1 into my Samsung A5 17 but I'm running into some problems... I hope that someone around here can help me out
So right now I’m on Android 8.0 with the stock Samsung experience, bootloader ecc… I’ve tried to install TWRP and lineageOS 14.1, and it runs fine but it can’t recognize the SIM card! I did some research and turns out that I’ve to install first the stock Samsung ROM with 7.0 nougat and then install lineage in order to make the SIM show up. So I’ve tried to do so but when I try to flash the original stock ROM with Odin it returns this problem:
The flash fails after it tries to insert the param.bin file
The device in download mode return this error:
sw rev. check fail(bootloader) device: 7, binary: 4
Can you give me some advice?
Thanks :angel:

Why would you want to downgrade?
Make sure you have the proper ROM, as well as CS file.
Download said files again.
For some reason my brothers windows 10 partition hates downloading the files properly, on my Linux partition I never had said issues.

Because the I've read in other topics that if downgrade my phone to 7.0 it would be able to read the SIM card after install LineageOS 14.1, but I'm not sure about that. Am I right?
Don't worry I've tried to download the stock ROM multiple times but in every case it returns me this error.
I think that the ROM files aren't the problem.
Other advice? Thx you btw

Same here , my phone doesnt recognize sim aswell , but i didnt installed any custom rom i just had stock rom. It started with android 8 i tried a lot , but i cant make it work , if someone knows how to fix tell me.
And about the Binary on the device , you have to download a rom with a higher binary that you already have , since you have 7 you can only update to a 7 binary or higher , to know which is the binary on the rom ill Tell you how to realize the binary
The rom's file name is like this FXX5UIR7XVBR that seven in the last characters is the binary number of this rom. It was just an example.
Sorry about my english.
So if someone knows how to fix sim card problem it will help me so much , i tried to flash another stock rom , like 3 or 4 and nothing happened , imei is right its not corrupted or something.
Thx

Aliwu said:
Same here , my phone doesnt recognize sim aswell , but i didnt installed any custom rom i just had stock rom. It started with android 8 i tried a lot , but i cant make it work , if someone knows how to fix tell me.
And about the Binary on the device , you have to download a rom with a higher binary that you already have , since you have 7 you can only update to a 7 binary or higher , to know which is the binary on the rom ill Tell you how to realize the binary
The rom's file name is like this FXX5UIR7XVBR that seven in the last characters is the binary number of this rom. It was just an example.
Sorry about my english.
So if someone knows how to fix sim card problem it will help me so much , i tried to flash another stock rom , like 3 or 4 and nothing happened , imei is right its not corrupted or something.
Thx
Click to expand...
Click to collapse
Don't worry for the English I'm learning it too ahaha
Can you give me a more detailed explanation of that binary stuff that you were writing about? I didn't get how it fit with our problem, maybe I've just missed something ^^'
Also if you can find anything about our problem, please post it on this thread!
Thank you

Sahara fail error while flashing stock firmware with qfil

I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me

having exactly same issue
hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
keep posting so that solution come out

hilarioustiwari said:
I am using ARROW Os (pie), Now i want to get back to official stock rom with locked bootloader plox help me how to do so.
JUST now I HAVE FLASHED Lenovo_Z2_Z2132_Q01017.1_M_ZUI_2.0.093_ST_160811_QPST with QFIL and it is showing error ownload Fail:Sahara Fail:QSaharaServer Fail:The directory name is invalid. plz help me
Click to expand...
Click to collapse
Dude, this post is not a valid one.
To solve your error, extract the stock ROM files in a close directory to the pathname like ( c:\Stock\) .
ANd the next error you did was u did not launch qfil using admin rights.
do both the steps and try flashing stock.
hope I helped you. press the thanks button if so.:laugh:
 @Az Biker

Try QFIL 2.7.460.
Here is the link https://www.google.co.in/amp/s/www....atest-qualcomm-flasher-qfil-qpst-2-7-460/amp/

Bro this post is a valid one
akshay pro said:
Dude, this post is not a valid one.
To solve your error, extract the stock ROM files in a close directory to the pathname like ( c:\Stock\) .
Andd the next error you did was u did not launch qfil using admin rights.
do both the steps and try flashing stock.
hope I helped you. press the thanks button if so.:laugh:
@Az Biker
Click to expand...
Click to collapse
Ok after successfully flashing my zuk z2 plus this is what i have to say about sahara.
I Still dont know why this error happens, i reinstalled new windows after which i followed the whole step. basically a fresh start.
although there are lots of tutorial available in youtube and xda dev forms the one i suggest is attached below:
https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
and for youtube walkthrough there is this link:
https://www.youtube.com/watch?v=wSHX-9S_oRc
now there are multiple workaround mentioned which i don't claim to be not useful or useful, but may workout for you:
shortening the path of zui rom from where it will be flashed: they recommend to past it directly to root of a drive
running the QPST Application with admin privileges which i would personally recommend
Disable Driver Signature Verification through out the process:
Click the Start Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
You can search in google for more accurate steps, but one of the issue i faced was in latest version of window 10 i couldn't see the startup setting straight away. but at the bottom there is a link for additional option where you will find it.
[*]Downgrading to lower version or Upgrading to Higher Version QPST which for me, personally seems misleading and suggest you to stay with latest version
[*] and Last which i think made mine work, that is to reinstall Zuk Driver if there is an error which is persistent​
​
HAPPY FLASHING

Anthony Finix said:
Ok after successfully flashing my zuk z2 plus this is what i have to say about sahara.
...
HAPPY FLASHING
Click to expand...
Click to collapse
A really simple solution is to use MiFlash @mi-globe.com/download-xiaomi-mi-flash-tool-all-versions instead of any others along with the Qualcomm QDLoader drivers @AndroidFileHost.com

I had the problem but when i flashed the proper firmware in order, the problem resolved itself
ps i used an old version of qfil 2.0.xxx or something idk

MiFlash Problems, Device Bricked?

Hi, after an error 7 when flashing a custom rom via recovery, I tried to flash the actual stock rom with MiFlash.
Tried it serveral time, get allways the error message as shown in the attachement.
Is there any solution?

robert_b said:
Hi, after an error 7 when flashing a custom rom via recovery, I tried to flash the actual stock rom with MiFlash.
Tried it serveral time, get allways the error message as shown in the attachement.
Is there any solution?
Click to expand...
Click to collapse
Re-download custom ROM again. Use file manager if needed. Most likely a corrupt download.

usgaap said:
Re-download custom ROM again. Use file manager if needed. Most likely a corrupt download.
Click to expand...
Click to collapse
I tried downloads from several places. This is not the reason for the problem, sorry.

robert_b said:
I tried downloads from several places. This is not the reason for the problem, sorry.
Click to expand...
Click to collapse
Hi Robert,
My apologies for the short answer earlier.
Your device does not seem te be bricked. Yet. At least, not with the info you provided thus far. I am guessing you already googled "MiFlash crc check fail." Some of the options were; use a different archiver, re-download, sideload, rename file and folder into short names or boot a custom recovery (instead of flashing) and install that way.
I've had this exact same problem before (see bottom of post), hence my short reply.
Do you have custom recovery? Can you tell me what happens if you flash custom ROM for the Mi Max 3 that way?
It seems your goals is to flash official. Out of the top of my head, you could also install Official Global ROM through adb & fastboot. This needs unlocked bootloader though if I'm not mistaken, not sure if that's the case here. Alternatively, you can try using another computer. Or don't use MiFlash.
My issue with installing Global ROM was that the first 85% of the download took 3 minutes. The last 15% 5 seconds. I downloaded from official site. Install gave CRC Check Fail everytime. I tried 3 times. Nothing seemed out of the ordinary. I then used a Google Drive link with matching size and details and everything worked like a charm.
I sincerely hope any of this helps. As with everything Mi Max 3 related, please be aware of arb. Sorry for the generic warning but you can never be sure.
Regards