Alright, this thread is going to be dedicated to "Nooky" the supertool. What this script will do, is multiple things. Reset to factory firmware (exploit the /factory partition / bootcount.), Root, fix broken recoveries, and with root comes all of the mods for stock that I came up with. This is so then we can have everything in one tool without worrying about certain things. (also, after root, it could also install CWM recovery.)
Instructions:
I suggest that you have some kind of root shell. Either by using the adb hijack app I made found here or by being in recovery.
Extract the zip, and click "Nooky.bat" Ignore all other files, just click "Nooky" not nook and zergy. Nooky. Just needed to clarify. Anyway, then you just go through the menus and choose what you want. Enjoy.
*Note, you need to have an adb shell running as root on some of these options. So you may want to be booted into recovery off sd or something.
Features:
Root (includes nook and zergy script)
Md5sum check for recovery images.
Recovery flashers (root only.)
Reboot menu (Android and Recovery)
Reset nook to factory state (including /system and boot.) {8 failed boots method}
Auto device checker
More to come (maybe)
Download, screenshots, and changelog will be in 2nd post.
Download link:
download the awesomeness here.
Changelog:
Code:
1.0: Initial Release
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, it would be great if that tool has an ablility to resize the system partition of NT,
at the moment, users are only able to access 1GB via usb and repartitioning process is pretty complicated.
since there are CWM recovery img floating around the forum we can just reflash that after we repartition.
Very cool!
psh, seems more like a discussion thread >.> lol, J/k Will post video when made.
when you say install recovery, is this stock or CWM? If it is CWM, might I suggest a restore to stock flash as another option? or the reverse?
Other suggestions- stock image flasher? Stock image checker? check mounting of SD card? is it possible to use this tool to force people to boot from SD card by choosing an option here?
Just thoughts.
seems a good tool!
leegoon84 said:
Thanks, it would be great if that tool has an ablility to resize the system partition of NT,
at the moment, users are only able to access 1GB via usb and repartitioning process is pretty complicated.
since there are CWM recovery img floating around the forum we can just reflash that after we repartition.
Click to expand...
Click to collapse
We should have full use of the storage on the Nook Tablet after the next release of the CM7 ROM that Celtic, Gonce and Indirect are working on, without changing partitions at all.
Repartitioning is kinda dangerous with these things, it's not like repartitioning an SD card or a PC. This tool is for prepping/rooting/factory-resetting a nook tab, among other things. I think it's going to be pretty important as a recovery/prep tool when everyone's flashing ROMs to their NTs.
Mike is right. Also, fixed a small bug.
Sorry i don't understand only one think (i hope), To use this supertool, i have to install adb and usbdriver?
Sorry for the stupid question? but i not sure
i want to buy NT, but first, i want know how to root it?
Thanks
Related
Hi Folks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you may or may not be aware, I have been working on get CWM Recovery working on the Gen9's and basically make the layout of the Filesystems etc reflect some sort of Android Standard, In SDE mode at least. This is coming along nicely and I should be ready to kick out a Early Beta in the Next Couple of Weeks.
I would like to gather some input on any additional options people who like to see in CWM, Basically CWM Recovery Comes with a standard set of features but they maybe options that you have found useful on Device's you have had in the past etc.
I already plan to make it possible to boot into all modes on the device, that Archos Recovery, Archos Android, SDE Android and SDE CWM Recovery.
So Yeah, Give me Ideas and I'll seen If I can accomadate them
NOTE: Obviously We are just getting started on this and alternative recoveries will come in time, TWRP for example but one thing at a time eh :good:
Okay, Here's a currently "wishlist" of feature I think would be quite useful
Archos Specific Features
Include Stock Repair and Recovery Options
Include Stock Developer Edition Options
Reboot to Stock Recovery Option as a Fail Safe.
Reboot Stock Android
Flash Archos aos update
Upgrade Existing SDE Images to new structure
An the list goes on.....
Print system Properties
Print dmesg
Resize Partitions
Manage FS Image Location ( mainly nice to have on HDD Version I suppose )
Backup to Sparse Image ( I'm sure CWM5 Nandroid did this with ext4 partitions, god knows why they changed to a default choice between tar archives or dup differential blobs, What If I just a single portable file for my data partition backup!! )
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Power Off ( Suprisingly not include by default )
Full Touch Support with on screen keyboard and command line
I think those features will do nicely but If anyone has anymore then get involved!
The nandroid backup interests me a lot... its always nice to be able to "return" to when it was working if anything breaks.
Im watching this thread with interest good luck!!
TrOjAn
Maybe an ability to mount the whole system through usb? So one could DD clone the whole memory chip to PC. That could recover some bricks.
trevd said:
Resize Partitions
Click to expand...
Click to collapse
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
trevd said:
Start Fastboot support ( could be useful for flash images rather the 'ffing around with edify scripts and update zips )
Click to expand...
Click to collapse
But fastboot works on the bootloader level
gen_scheisskopf said:
I'm not sure if this would be actually usefull for flash partitions (one-time update.zip flashing should be enough)
But fastboot works on the bootloader level
Click to expand...
Click to collapse
Hi There,
I think, You've got your wires crossed None of this is related to letama CWM Recovery./ If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
I well aware of how fastboot works but to supporting the fastboot protovol allows the same workflow when it come to work with the AOSP source as any over device. which is
Build Rom
Flash the Partitions with fastboot
Reboot Into Rom.
???
Profit
When you control both ends of the conversation, We are free to do as we please.
Any news ... are there any files to do some testing?
shalkam said:
Any news ... are there any files to do some testing?
Click to expand...
Click to collapse
Would you mind reading... ???
trevd said:
If you haven't already you may want to have a read of this thread in the development section I won't go into details here because It's all in there!
Click to expand...
Click to collapse
Follow the link and you are there.
Regards,
scholbert
Flash splash screen?
Swiped from my Galaxy Nexus using Tapatalk 2
Hello everyone; I've been desperately attempting to get CM7 installed on my Samsung Fascinate since its release, and I have been unable to do so despite it being 'so very easy'. Today I had installed CM10 on my HP touchpad with zero issues, so I decided to attempt to install CM7 on my Fascinate again.
While following this tutorial (http://forum.cyanogenmod.org/topic/32474-cyanogenmod-7-for-the-samsung-fascinate-v710-9-oct-2011/) I came across a step that 'bricked' my phone. Below are the steps that I was required by the tutorial to take:
Root the device and install ClockworkMod Recovery. Instructions are available here.
My phone had been previously rooted; I purchased, downloaded and flashed ClockworkMod Recovery onto my phone successfully.
Perform a NANDroid backup of your current ROM.
I elected NOT to do a NANDroid backup; my phone was cluttered and I decided that if things wen't wrong, I'd like to reboot into a factory reset phone and re-root from scratch (where inlies my issues).
Format the system, data & cache partitions of your device.
I did, successfully.
Perform a factory reset.
This is the last step in which I was able to complete (for obvious reasons) after the factory reset was complete, however, I was UNABLE to get into download mode to be able to finish the ClockworkMod Recovery (all files for CM7 are still on my SD card ready to go). However, upon rebooting my phone I've noticed that my home screen manager does NOT function, and I am unable to navigate within my phone. It does NOT launch when I hit my home button, and I've been unable to do anything else with my phone.
Flash CyanogenMod.
I was unable to get to this step.
Optional: Install the Google Apps addon package.
I was unable to get to this step.
Being a tech geek, I would not open a thread unless I've exhausted all options at my disposal; A quick Google search resulted in this thread (http://forum.xda-developers.com/showthread.php?t=1026746) in which I was sure I'd be able to get my phone working again. However, the files associated with it (EB01All in 1) are no longer hosted at the links provided. An extensive Google search yielded no results.
What I'd like to be able to do is to get my phone operational to the point where I can continue with the installation of CM7. Any and all help that you can provide would be greatly appreciated.
Thanks!
I would use section 4 of that guide by droidstyle
And flash a jelly bean 4.2.x Rom
.
hhp_211 said:
I would use section 4 of that guide by droidstyle
And flash a jelly bean 4.2.x Rom
.
Click to expand...
Click to collapse
From what I can gather by your post, you're suggesting that I use section 4 of this tutorial: http://forum.xda-developers.com/showpost.php?p=17050028
In which I would not be able too, considering almost all of the pertinent files that were uploaded for use cannot be found, and are no longer hosted. Anything else?
=========================
Update:
By some sort of miracle I was able to get my phone into download mode by using the SDK command; as of now I'm loading up CI500_VZW_EH03_GB_CM.tar.md5 as you've suggested. I'll update this post again once the process is complete.
zQueal said:
From what I can gather by your post, you're suggesting that I use section 4 of this tutorial: http://forum.xda-developers.com/showpost.php?p=17050028
In which I would not be able too, considering almost all of the pertinent files that were uploaded for use cannot be found, and are no longer hosted. Anything else?
Click to expand...
Click to collapse
okay so, why did you root the phone? that was an extra step that was unneeded. you just had to flash cwm_fix_cm7 or whatever and then boot into cwm and flash cm7. also, I'd flash EH03, that's gingerbread, you don't have to go back all the way to EB01 or whatever, no need to. and lastly, you shouldn't of factory reset it. it sounds to me like you have soft bricked it, does it boot up, even with errors? if you can bout it, try powering it off and then take out the battery and the SD card, then hit the vol - and power and it should boot into download mode. (also put the usb into the port and phone before) but like hhp said I'd go read droidstyles guide
What I don't get is why you'd want to use CM7 when there's a ton of great 4.2 roms available for the Fascinate (including CM10.1) that run very nicely
Crawshayi said:
What I don't get is why you'd want to use CM7 when there's a ton of great 4.2 roms available for the Fascinate (including CM10.1) that run very nicely
Click to expand...
Click to collapse
So far I've been unable to find any, which is why I was under the impression that I would be required to use CM7; if possible, could you link me to the files necessary?
zQueal said:
So far I've been unable to find any, which is why I was under the impression that I would be required to use CM7; if possible, could you link me to the files necessary?
Click to expand...
Click to collapse
Come on now ,, section 4 has all the info you need...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you are done there look in the development section
.
The only rom you won't find here is CM10.1 which can be found over at rootzwiki
Thread closed
Situation has been resolved per the OP.
Hey there, I know this has been asked before because I've seen it but I can't seem to find it again. Maybe someone else can help out. I've flashed through a few ROMs and I've ended up with quite a hefty load of about 5GB of data that I can't seem to find. I don't have any nandroid backups on my phone at the moment. I've deleted almost everything I could find. I'm running NuSense Six m7 base. RC6.8. Attached are a couple screenshots illustrating my issue. What is taking up so much space?!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you sure you don't have any backups hiding....?
Current versions of twrp backups can be found, using a root enabled file explorer.
Check in /data/media/0/TWRP/backups
I'm using CWM but I didn't have any backups there. I know "Other" is supposed to store the OS, but is 5GB an acceptable size?
DanielWEWO said:
I'm using CWM but I didn't have any backups there. I know "Other" is supposed to store the OS, but is 5GB an acceptable size?
Click to expand...
Click to collapse
Not really, no.
The Rom should only use about half of that.
Which is why it seems you have one backup hiding somewhere.
If I were you, I'd back up anything important to my computer.
Then I'd wipe everything and sideload or adb push the Rom.
That should clean everything up.
Then just put back what you need or want.
This is also dependent on how many apps you've restored or installed since loading the base Rom.
Some games and various apps data can be rather large.
santod040 said:
Not really, no.
The Rom should only use about half of that.
Which is why it seems you have one backup hiding somewhere.
If I were you, I'd back up anything important to my computer.
Then I'd wipe everything and sideload or adb push the Rom.
That should clean everything up.
Then just put back what you need or want.
This is also dependent on how many apps you've restored or installed since loading the base Rom.
Some games and various apps data can be rather large.
Click to expand...
Click to collapse
Okay. I'll give that a shot, I'll have to do some googling to figure out how to do that xD.
DanielWEWO said:
Okay. I'll give that a shot, I'll have to do some googling to figure out how to do that xD.
Click to expand...
Click to collapse
Yeah, Google it, it's actually really easy.
Just a word of advice:
Place a working rom.zip on your device. (as a failsafe in case sideload or adb push doesn't work for you.)
Practice at least once, adb pushing or sideloading a rom, prior to wiping the device.
That way you can be sure you have the process working before you wipe the device.
This way, while practicing, if you have any troubles with adb or drivers, etc,..you'll still have at least one rom zip on your internal storage that you can flash back to until you get it working.
I don't wanna see you end up with no OS and no working method to get a rom back on the device.
(only reason you would have any issues would be due to adb drivers)
Once you know the process is working with your PC setup and drivers, then you can wipe and sideload for real...
santod040 said:
Yeah, Google it, it's actually really easy.
Just a word of advice:
Place a working rom.zip on your device. (as a failsafe in case sideload or adb push doesn't work for you.)
Practice at least once, adb pushing or sideloading a rom, prior to wiping the device.
That way you can be sure you have the process working before you wipe the device.
This way, while practicing, if you have any troubles with adb or drivers, etc,..you'll still have at least one rom zip on your internal storage that you can flash back to until you get it working.
I don't wanna see you end up with no OS and no working method to get a rom back on the device.
(only reason you would have any issues would be due to adb drivers)
Once you know the process is working with your PC setup and drivers, then you can wipe and sideload for real...
Click to expand...
Click to collapse
I think I've done it with my Galaxy Nexus and that was cake.
Ok, so I don't want to continue with this after I get some specified things in order to pursue the root methods.
My phone is Allview V2 viper x+ 3 gb ram bla bla (http://allview.ro/produse/telefoane/viper/v2-viper-x-plus-gold.html)
I'm backing up now few things and after that will backup the system files like recovery, imgs and more so, just for to be sure I have some back up in order to get it back to life if something gone's wrong.
I have 2 problems to solve with this phone.
1. After I changed my sd card to be the default internat storage for apps, everytime I try to install some app from market it's says something about hardwer is not compatible or something like this, but If i'll download the apk from some site (same apk) is working, well this is the first problem and is unsolved.
2.I want to have the phone rooted, I saw many posts with this method of supersu beta root and I have to flash some recovery img (I'm always trying and I see if is working, but I have a lot to save from my phone, so I'll have to wait to finish the full backup, reset the phone, get the sd card off and so on).
I tried to search a good version of TWRP for my phone, but I don't find any good compatbile.
My question for you is :
1.Did anybody had a successful root with this phone?
2.Which method is better to root an marshmallow? (6.0)
3.There is some recovery of twrp compatbile with this phone?
4.Does the ota update will work after the root process? (because I'm thinking that they could have some update to 6.0.1, but Idk when).
##Update##
I came back to previous version of 5.1 and root it and then I'll try the method from here with flashfire.
http://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
Click to expand...
Click to collapse
##Update-2##
Failed every method I tried.
- Failed installing custom recovery carliv, cwm, twrp (all failing, is not booting after flashing custom recovery, the only one who works is that carliv touch but if I install it, will not boot anymore)
- Failed kingroot (suppose to have some 6 method of rooting one click root)
- Failed flashing supersu, not working without a custom recovery .
- Tried to search for some custom rom to install with carliv, but I didn't find any good, all had errors that I didn't find to solve. and is crazy that I can't root the phone.
Note : What method remains?
If someone know..
##Update-3##
After many many unsucessful custom recoverys, successful bootloader unlock and many resets, didn't get any luck.
I'll remain on 5.1 till I have a clearly method of rooting the marshmallow without having to change the custom recovery, or maybe till I find a good custom recovery that works with anything I need.
Or till they update the android 6.0 to 6.0.1 (I saw that they have some root access option).
Maybe someday someone will text here with some method or similar, so I'll look here everyday till I find a way ;3
Ps. : Even if is a gionee s plus, the methods I saw for it, didn't worked aswell.
Cya.
##Up1x##
Tried this too and voilla .. ..
Another error ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
##Final Update (Can close this)##
After a lot of of of of searching and mental stress and a lot of digging, I finally find a very one and good solution to get supersu flashed by a custom recovery.
For those who have problems like me and have same phone (Gionee Splus), follow this guide : https://atozhacks.blogspot.ro/2016/08/gionee-splus-marshmallow-philz-touch.html
I just want to finally try and install a custom rom into my Mi A3 which I rooted a while ago. I know I need this tool called TWRP, after encountering a myriad of errors trying to follow this guide step-by-step, I finally got to the point when I need to type "fastboot boot twrp.img" to boot into TWRP temporarily. But alas that couldn't be so easy now could it... Now I get this thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it's 11:41 PM and I'm about to burst a vein. I made an account solely to make this post because I can't seem to get an actual answer anywhere else... Any ideas before I give up?
is the bootloader unlocked ?
i think i got same message and it was because i forgot this.
I think there are better guides. Not sure what state your system is in. I would re-install the stock rom and start afresh. Unlock your bootloader, check which slot 'a' or 'b' is the current slot, and then follow the instruction of the Custom ROM you are trying to install. It might need TWRP but Lineage Recovery is equally as good.
#1jonna said:
is the bootloader unlocked ?
i think i got same message and it was because i forgot this.
Click to expand...
Click to collapse
Yes sir it very much is, don't think it'd have been possible to get this far otherwise
bjlabuk said:
I think there are better guides. Not sure what state your system is in. I would re-install the stock rom and start afresh. Unlock your bootloader, check which slot 'a' or 'b' is the current slot, and then follow the instruction of the Custom ROM you are trying to install. It might need TWRP but Lineage Recovery is equally as good.
Click to expand...
Click to collapse
how do I do this?
2. does Lineage Recovery even work on Mi A3s? I don't find anything about this device on their website
Follow the guide in the thread 'Slot A is destroyed'.
bjlabuk said:
Follow the guide in the thread 'Slot A is destroyed'.
Click to expand...
Click to collapse
I assume this means I can just go back to magisk and hit restore images, then return to fastboot and switch to slot b and install twrp there?
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ said:
View attachment 5554333
I assume this means I can just go back to magisk and hit restore images, then return to fastboot and switch to slot b and install twrp there?
Click to expand...
Click to collapse
As I said, as I am not sure what state your system is in I would suggest 're-installing' the stock rom from your PC, rather than 'restoring' an image from your phone. If you have backed up your data etc (eg on Google Drive) you can restore it after you have re-installed the stock rom. You can then start again from scratch.
The latest stock rom fastboot images can be found here
https://xiaomifirmwareupdater.com/miui/laurel/
Tbh I haven't restored an image from magisk myself so I can't confirm what you are proposing, though yes I switched to slot b and installed TWRP.
You might also want to read this article on A/B partitions
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Try this
https://play.google.com/store/apps/details?id=com.smartpack.smartflasher
Flash TWRP installer through the app
Just a few tips when you do get to TWRP:
Disable dm-verity
Format data and wipe cache after you flash the new rom before first boot
Use a patched boot method instead of flashing magisk in TWRP on custom ROMs. High chance of soft brick.
DM me if you need help.