If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
TWRP Recovery with UBIFS Support For Amlogic Nextbook Tablets (Support Thread)
I've always done it on windows, and had to increase the memory quite a bit. I believe it has to read the entire ROM into memory to generate one or more checksums in addition to generating and adding the key file.
I stopped signing my ROMs after moving to TWRP, because TWRP by default doesn't check the keys at all.
ShaunMT
TWRP is great that way, just sluggish with the touch driver. The swipe for confirmation is a great idea too but in this case it prevents it from using TWRP altogether. YES/NO confirmation would make it work even with a slow touch response.
I signed SMT-Next7P12-8G-NXM727MC_WM-102312-8192cu_wifi on windows but still no luck verifying with modified stock recovery. It could be that the downloaded file is not passing checksum test.
Incidentally the file SMT_Next7P12-8G_Stock_Rom-signed.zip when I downloaded from a Quebec server wasn't working until I downloaded it from an Arizona mirror site that verified on the first try.
I did it on a pretty small 1GB lubuntu netbook, it didn't report any errors just created the signed file. It took a while though. I will check the command line switch to give it more memory and I will give it a try on a windows machine as well.
Thanks for helping out,
Branko
I've always done it on windows, and had to increase the memory quite a bit. I believe it has to read the entire ROM into memory to generate one or more checksums in addition to generating and adding the key file.
I stopped signing my ROMs after moving to TWRP, because TWRP by default doesn't check the keys at all.
The eclipse signapk.jar is what I use, but I'm not sure about the version (or if the version matters).
Are you sure it signed successfully? You might need to increase the amount of memory available to java. There is a command line option that does this as part of the signing command.
The FTP server should be available again soon... it's down due to a network routing problem at the service provider... so we are all waiting on the service provider to resolve the problem on their end...
ShaunMT
I did it on a pretty small 1GB lubuntu netbook, it didn't report any errors just created the signed file. It took a while though. I will check the command line switch to give it more memory and I will give it a try on a windows machine as well.
Thanks for helping out,
I did sign one of the roms a while ago with test keys that come with eclipse signapk.jar but the modified stock recovery wouldn't verify it. My eclipse is old i will try with newer version of signapk again. I can't get the other rom to try, the FTP server is down, I wanted to do a fresh download of both.
Will see tonight...
The eclipse signapk.jar is what I use, but I'm not sure about the version (or if the version matters).
Are you sure it signed successfully? You might need to increase the amount of memory available to java. There is a command line option that does this as part of the signing command.
The FTP server should be available again soon... it's down due to a network routing problem at the service provider... so we are all waiting on the service provider to resolve the problem on their end...
I stopped making or supporting the modified stock recoveries for a variety of reasons including:
It can't perform back up or restore functions.
It can't install any package that wasn't signed with the matching keys.
The update_binary (installer application) has limitations.
You are welcome to try signing the ROM files with the Google Test Keys yourself. Its a simple process that is well documented all over the internet. The modified recovery stock recoveries that I made will attempt to install any .zip that was signed with the public Google test keys, although it may not be able to process the update_script in the ROM correctly.
ShaunMT
I did sign one of the roms a while ago with test keys that come with eclipse signapk.jar but the modified stock recovery wouldn't verify it. My eclipse is old i will try with newer version of signapk again. I can't get the other rom to try, the FTP server is down, I wanted to do a fresh download of both.
Will see tonight...
I stopped making or supporting the modified stock recoveries for a variety of reasons including:
It can't perform back up or restore functions.
It can't install any package that wasn't signed with the matching keys.
The update_binary (installer application) has limitations.
You are welcome to try signing the ROM files with the Google Test Keys yourself. Its a simple process that is well documented all over the internet. The modified recovery stock recoveries that I made will attempt to install any .zip that was signed with the public Google test keys, although it may not be able to process the update_script in the ROM correctly.
ShaunMT
That means that there is no way to make a recovery for my model ShaunMT?
Looking at the symptoms I must have the same model as haumzahkalid. No luck with TWRP, the touch too sluggish to make a swipe.
I was able to flash rom file "SMT_Next7P12-8G Stock Rom-Signed.zip" with your Modified Stock 3e Recovery, but no working WiFi.
Why did you give upon the Modified Stock 3e Recovery? Can you sign the new rom packages so the 3e recovery can be used?
Branko
I stopped making or supporting the modified stock recoveries for a variety of reasons including:
It can't perform back up or restore functions.
It can't install any package that wasn't signed with the matching keys.
The update_binary (installer application) has limitations.
You are welcome to try signing the ROM files with the Google Test Keys yourself. Its a simple process that is well documented all over the internet. The modified recovery stock recoveries that I made will attempt to install any .zip that was signed with the public Google test keys, although it may not be able to process the update_script in the ROM correctly.
Looking at the symptoms I must have the same model as haumzahkalid. No luck with TWRP, the touch too sluggish to make a swipe.
I was able to flash rom file "SMT_Next7P12-8G Stock Rom-Signed.zip" with your Modified Stock 3e Recovery, but no working WiFi.
Why did you give upon the Modified Stock 3e Recovery? Can you sign the new rom packages so the 3e recovery can be used?
just so let you know i'm still waiting,....take all the time you need,..i'm not annoying you,.. just giving you a reminder that I still looking forward for your help,.....
I don't know why some people are able to use lock slider control in the TWRP for the Next7P12-8G and some people can't...
I don't own this model so I can't do any troubleshooting...
Unless someone wants to donate a Next7P12-8G model that they are no longer using, I don't see any improvements coming for this model...
just so let you know i'm still waiting,....take all the time you need,..i'm not annoying you,.. just giving you a reminder that I still looking forward for your help,.....
You need TWRP. Sorry it is difficult to use, but it does work. Unfortunately I dont own that model so I cant do any troubleshooting to even attempt improving the touch ui. I suspect the issue is due to the way amlogic handles screen resolution and touch... I dont know if I could do anything about it even if I did own one to test on...
I did have an idea the other day that might maybe possibly work.... ill try to test it on one of the models I do own.... if it solves the issue an one model, it should work on all of them... dont get your hopes up though...
Sent from my SM-G900P using Tapatalk
alright , I think i'll wait because there is no other way left for me,.. hope to hear from you soon......
You need TWRP. Sorry it is difficult to use, but it does work. Unfortunately I dont own that model so I cant do any troubleshooting to even attempt improving the touch ui. I suspect the issue is due to the way amlogic handles screen resolution and touch... I dont know if I could do anything about it even if I did own one to test on...
I did have an idea the other day that might maybe possibly work.... ill try to test it on one of the models I do own.... if it solves the issue an one model, it should work on all of them... dont get your hopes up though...
sir @ShaunMT I have Next7P12-8G , It somehow don't get pass the boot loading screen so I thought of flashing it with a custom ROM or stock build ROM then here I found your thread for sec I thought I could be able to save my dying TAB but im way too annoyed of the fact that TWRP Recovery don't let me do anything I have placed all the right files in the right places of SD card , even I started TWRP Recovery , but the annoying touch system of it don't let me flash "I just can't swap, "Swap To Flash Rom" button the touch is way too lagging and sometimes it won't work , please its a request provide me something good instead of TWRP recovery through which i could flash without getting signature error (P.S: Also tried your modified stock 3e recovery still won't work)
please please do me favor of giving a proper solution ,....
waiting for your reply,....
The "fresh" one I bought and used was a SanDisk Ultra Plus UHS-1 Class 10.
I'm just happy it's working now.
.....
and another thing..
I tried to install SuperSU and it wouldn't load properly. It needed to update the binary, tried both ways no luck.
I loaded a terminal app, no # at the command line so I tried the su command, and it said I didn't have permission.
I thought this rom was rooted, or am I missing something?
If you are running one of my ROMs, it should be pre-rooted, although I have not personally tested the Next7P12-8G ROMs because I don't own that model. You should also have a custom boot logo if you successfully flashed one of my ROMs.
You might want to either flash the ROM again, or flash my Kyser_Root package (which only installs a su binary).
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Leave a comment: