[ROOT] Howto root easily your Gen8 device [fw 2.0.71 - 2.4.83] + R/W FILESYSTEM - Gen8 General

Hello community
First of all, thanks to dogmaphobia for his initial work (click for fw 2.0.71)
Don't forget: I'm not responsible for anything
Installing SDE or rooting your Archos device in any way may or definitly will void your warranty. You can find more information about it on the Archos website: link
Now here we go, you need four things:
An Archos Gen8 device (e.g. A101IT)
Archos Firmware
- 2.1.02: [Archos server]
- 2.1.03: [Archos server, Mirror #1]
- 2.1.04: [Archos server, Mirror #1]
- 2.1.08: [Archos server]
- 2.3.20: [Archos server]
- 2.3.26: [Archos server]
- 2.3.81: [Archos server]
- 2.4.19: [Archos server]
- 2.4.65: [Archos server]
- 2.4.80: [Archos server]
- 2.4.81: [Archos server]
- 2.4.82: [Archos server]
- 2.4.83: [Archos server]
Archos SDE
- [Archos server], [Mirror #1]
Rooted initramfs + kernel
- [fw 2.0.71 +rw]
- [fw 2.1.02]
- [fw 2.1.02 +rw]
- [fw 2.1.03]
- [fw 2.1.03 +rw]
- [fw 2.1.04]
- [fw 2.1.04 +rw]
- [fw 2.1.08]
- [fw 2.1.08 +rw]
- [fw 2.3.20]
- [fw 2.3.20 +rw]
- [fw 2.3.26]
- [fw 2.3.26 +rw]
- [fw 2.3.81]
- [fw 2.3.81 +rw]
- [fw 2.4.19]
- [fw 2.4.19 +rw]
- [fw 2.4.65]
- [fw 2.4.65 +rw]
- [fw 2.4.80]
- [fw 2.4.80 +rw]
- [fw 2.4.81]
- [fw 2.4.81 +rw]
- [fw 2.4.82]
- [fw 2.4.82 +rw]
- [fw 2.4.83]
- [fw 2.4.83 +rw]
*: +rw = permanent root, changes to filesystem will be stored in /dev/mmcblk0p2. it has ~30 megabytes free, this should be sufficient for most changes and scripts.
BE CAREFULLY: if you delete or corrupt important system files and aren't able to boot anymore, you have to flash the "non-rw" root kernel+initramfs, go to /mnt/system/unionfs and remove the changes.
Then you have to the following:
Install SDE (you only have to do this only once, it will even survive a full reformat)
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by USB to your computer
upload the SDE firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install android firmware
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by usb to your computer
upload the Android firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install the custom kernel + initramfs
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Flash Kernel and Initramfs"
connect your Archos device by USB to your computer
upload zImage and initramfs.cpio.gz to your device
safely disconnect the USB connection
press ok on Archos device
reboot and hold down "Vol-" button after screen went black
choose "Developer Edition"
now you have temporary root (you always have to boot "Developer Edition" to get root again)
(optional!) permanent root
thus it will boot always the custom kernel (to revert, reinstall Android firmware)
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Remove Android Kernel"
reboot
For Updates:
Just go like this:
chulri said:
@Techngro
I was in the same situation as you are: 2.1.03 and permanent root.
Then did a firmware upgrade from the rescue menu, flashed the new kernel and initramfs and removed again the stock android kernel --> working
If it says "update failed" the aos file might be corrupt
Click to expand...
Click to collapse
Have fun!
Big thanks to jfmcbrayer for helping me out!
Links for developers:
[DEV] Thread
Project site at code.google.com

Quick Question: If I remove Android's kernel would I also get rid of the firmware?
TIA!

chemical1der said:
Quick Question: If I remove Android's kernel would I also get rid of the firmware?
Click to expand...
Click to collapse
No, of course it does not. Because if it would, what should the device boot then?

that's what i thought. my Archos gave me a rather ominous warning about removing the kernel. i'm used to flashing kernels on my DINC but am brand new to doing so on my Archos. thanks for the quick response and the root solution!

Update and temp-root worked on Archos 32
chulri said:
...
You need four things:
An Archos Gen8 device (e.g. A101IT)
Firmware 2.1.02
Archos SDE
My custom initramfs + kernel
Click to expand...
Click to collapse
* Sorry - can't post links - me = newbie here - lol
Many thanks for the links and the how to...
My first android device, first time flash/upgrade (2 weeks old). Took a guess that when uploading the files, they just go onto the root, it wasn't mentioned anywhere. Figured if it was the wrong location, nothing would be damaged.
Worked like a charm, even though I messed up the order due to file naming issues, downloaded in the order listed above, so file and file(2) were in the wrong order . Both the firmware and SDE have the same filename, and I mixed them up on upload the first time due to listed and downloaded order above, but it just updated the firmware to 2.1.2, saved all my applications and settings. I then went back, put on the SDE, missed the reboot Vol- and it loaded the alt-OS Armstrong or something , rebooted and did the firmware again just to be funny, then the temp-root, and it all work really well.
I luckily didn't brick it, although it took a super long time at the archos boot screen after the first push of firmware 2.1.2, seemed hung, so I restarted it, and it booted, checked and was upgraded. Not sure if I farked the process by restarting it while in that Archos boot screen or not, not sure if it was actually doing anything after 10 minutes, so took the chance. The firmware update progress bar goes quick, just took ages on that reboot. I hope it wasn't trying to convert the fs or something.
My quadrant score is still the same, between 1328 - 1447 depending on junk running in background when testing.
Market and Youtube
I had installed the market using that gApps4Archos2.apk when on 2.0.71 then killing the youtube.apk and downloading it from the market. Didn't have to do anything after the 2.1.2 firmware update this time since everything was in place. Tested youtube and it works.
SMB
Also tested the SMB issues that I and others were having, and they are not resolved. I can pull media from a Vista and XP accessing shares via SMB, but after playing a couple videos, it give either media server error, or file incomplete or damaged error. If I clear the media library and reboot, I can play those same files again until something is overloaded. Long files names, paths, or mixed, nested both seem to quicken the need for a reboot in my case. I have not tested on my debian box to see if it is a windows (mainly Vista) thing or not. I have noted that once I get these media server errors, even locally stored video give the error until rebooted. FWIW.
Mount
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw)
/dev/block/mmcblk0p2 on /mnt/system type ext3 (rw,nosuid,noexec,noatime,errors=continue,data=ordered)
/dev/block/mmcblk0p4 on /data type ext3 (rw,nosuid,noatime,errors=continue,data=ordered)
At least the battery now can reach 100% and show "charged" instead of only reaching 99%. That is a plus.
Thanks again, I am just coming up to speed on this device and look forward to hacking it. I wonder if I can safely disassemble and upgrade the storage to a high speed mmc.
dmesg: mmc0: card is mmc v4 but doesn't support any high-speed modes.
this is going to be fun....
Keep up the great work...

To do this, do you each step right after the other? I was going to allow my 101 to boot into the newly installed 2.1.02 after a full system wipe but i'm getting a bootloop when trying to start.
EDIT: Followed from the beginning again (already had the SDE firmware installed), & still ends in bootloops =\ Guess i'm trying a few more times but i was wondering if anyone else had success?

Veritas06 said:
To do this, do you each step right after the other? I was going to allow my 101 to boot into the newly installed 2.1.02 after a full system wipe but i'm getting a bootloop when trying to start.
EDIT: Followed from the beginning again (already had the SDE firmware installed), & still ends in bootloops =\ Guess i'm trying a few more times but i was wondering if anyone else had success?
Click to expand...
Click to collapse
This has nothing to do with rooting.. it is a problem many are having, including myself with the new firmware. It might be because the kernel is a little bigger and it won't fit in some boot partitions that may have bad blocks. I've contacted Archos support so they know of the problem and hopefully they'll get a fix out soon.

good job!
But Rotating the device took about 10 seconds for the home screen to update all the icons. Any way to imporve the speed?
Thanks much for help!
chulri said:
Hello community
First of all, thanks to dogmaphobia for his initial work (click)
Don't forget: I'm not responsible for anything
Now here we go:
You need four things:
An Archos Gen8 device (e.g. A101IT)
Firmware 2.1.02 ([Archos server], [Mirror #1])
Archos SDE ([Archos server], [Mirror #1])
My custom initramfs + kernel ([archos-gen8-dvb project], [Mirror #1])
Then you have to the following:
Install SDE (you only have to do this only once, it will even survive a full reformat)
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by USB to your computer
upload the SDE firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install android firmware 2.1.02
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by usb to your computer
upload the Android firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install the custom kernel + initramfs
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Flash Kernel and Initramfs"
connect your Archos device by USB to your computer
upload zImage and initramfs.cpio.gz to your device
safely disconnect the USB connection
press ok on Archos device
reboot and hold down "Vol-" button after screen went black
choose "Developer Edition"
now you have temporary root (you always have to boot "Developer Edition" to get root again)
(optional!) permanent root
thus it will boot always the custom kernel (to revert, reinstall Android firmware)
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Remove Android Kernel"
reboot
Have fun!
Click to expand...
Click to collapse

Tesla74 said:
This has nothing to do with rooting.. it is a problem many are having, including myself with the new firmware. It might be because the kernel is a little bigger and it won't fit in some boot partitions that may have bad blocks. I've contacted Archos support so they know of the problem and hopefully they'll get a fix out soon.
Click to expand...
Click to collapse
Thanks for the heads up. I have an EVO so i've seen users with bad blocks but assumed this was after flashing a few dozen times, guess i was wrong =\. Hopefully we'll see a modified update soon.
Thanks again!

sorry for the noobish question...
does this method gain full root access to the system partition, so that adfree, rootexplorer, ... will work correctly?

yes you get root access and yes you can modify the system files, but after a reboot, everything is reverted

thx for the quick reply
but if i use step 4 of your howto:
(optional!) permanent root
thus it will boot always the custom kernel (to revert, reinstall Android firmware)
* reboot Archos device and hold down "Vol-" button after screen went black
* Go to "Recovery Menu" and then "Developer Edition Menu"
* choose "Remove Android Kernel"
* reboot
Click to expand...
Click to collapse
then should be everthing fine...

changes to system directories / files aren't saved on disk (tmpfs) so after a reboot all changes are reverted, even if you boot again into root.

ok.
is there allready a way, or will there be a way someday with full access without tmpfs?

either you go with the very custom UrukDroid or wait some time until myself or someone else starts investigating into this (my approach would be, using stock archos firmware and add simple but persistent r/w acces, no less no more)

chulri said:
either you go with the very custom UrukDroid or wait some time until myself or someone else starts investigating into this (my approach would be, using stock archos firmware and add simple but persistent r/w acces, no less no more)
Click to expand...
Click to collapse
Slightly OT but am currently using UrukDroid and am pretty happy with it. However, it is always good to see different people's ways of implementing things, so if you do decide to look into rooting your way, I'd certainly be up for giving it a try!

+1
I'm always up for testing. Let me know!

Anyone tried with the 250GB A70?
I will do tonight, but away from my charger to connect for the initial upgrade.

UPDATE
Now compatible with 2.1.03

thank you very much for this!
works perfectly on my 101

Related

Wayteq xPAD-70 and xTAB-70 ICS 4.0.3 [ROM] /older roms

Disclaimer: I am not responsible for what YOU do to your tablet...
You assume all responsibility and risk associated with flashing any ROM. Make a backup!!!
ICS 4.0.3 for our xPAD-70 (Type 1 iDx7) and xTAB-70 (Type 2 iDx7).
I must say, that these roms very fast and stable.
What's Working:
camera
touchscreen
physical buttons
wifi
audio, ringtones, notifications, alarms
microphone
root
adb
sdcard
sensors
usb host
everything
Install instruction/download links:
1. Connect the home charger to the Tablet PC. Charge the battery.
2. Download the compressed file to your PC/Laptop.
3. Create an empty folder on your desktop PC / laptop. Extract the downloaded .zip file into this empty folder.
4. Copy the four extracted files ("update.zip", "uImage_recovery", "uImage", "u-boot-512M-UartB.bin","factory_update_param.aml") to the root folder of an empty microSD card (2GB or higher). I you want to wipe and install manually, just delete the factory_update_param.aml file and boot into recovery without that.
5. Safely remove (disconnect) the microSD card.
6. Turn off the Tablet PC, but keep the home charger connected to it.
7. Insert the microSD card into the Tablet PC. After this step, don't pull out the microSD card.
8. Press and hold down the "volume up" button.
9. While holding down the "volume up" button , press and hold down the "power on" button for 6-9 seconds, and release the buttons after the last "upgrading... please wait" like messages.
Navigation inside the menu:
- Volume up and down buttons can be used to select a menu item.
- The "back" button (which is between the "home" and "menu" buttons) will activate a menu item.
10. Dont forget to hit the thanks button
Downloads:
==============
xPAD-70 (Type 1 iDx7) ICS 4.0.3 :
==============
ROM:http://www.mediafire.com/?1iqt5f1uamtrw2f
==============
xTAB-70 (Type 2 iDx7) ICS 4.0.3 :
==============
ROM: http://www.mediafire.com/?gtlqgdk33bhhtj2
===============================
ROOT packcage for ICS roms, xPAD/xTAB(apply after installig the upgrade) :http://www.mediafire.com/download.php?pfrrx7ja502qz2j
===============================
Older ROMs:
soon...
The language could be hungarian, but you can change to english with these settings:
1. Beállítások (its the hungarian word for Settings. Its in the menu) 2. Nyelv és billentyűzet (means Language and keyboard) 3. Nyelv kiválaszása (Select language) 4. Chose the English languge from that list. Thats all.
Copyright:
=========================================
[email protected]___________________
=========================================
2 links for xPAD-70 ?
murigny64 said:
2 links for xPAD-70 ?
Click to expand...
Click to collapse
Sry, i corrected, the second is the xTAB-70 ICS 4.0.3
I can't get BBC I player or Netflix to run with this rom. I get sound but no picture. Does anyone know why. Avi files run fine. Otherwise the from is very good. Been following this on the Hungarian forum but relying on google translate. Only other issue is the inertia scrolling.
Cheers carrotts
Sent from my xPAD-70 using xda premium
I have no idea about Netflix. Is seems to be working with CM nightlies. There is a XDA thread about netfix. I hope there is a solution for this.
This is the link: http://forum.xda-developers.com/showthread.php?t=1076150
The inertia scrolling fix appears in the next rom update. I hope.
cant use boot menu
Hi when i restart in boot menu i cant navigate it
When i press any button it reboots,
Anyone know if a setting needs adjusted?
As really needs updated
I got a question too....
I copied the files on SD Card but when i Press "volume Up" and "Power" Butten i get the upgrade Message and after the secon one he starts flashing but he doesnt start. i only get the waycom logo and the he reboots ....
Can someone help me?
Hello,
Do you have copy of ROM for similar device xTAB-70i ?
I am looking for Wayteq_xTAB_70i_20120620.zip.

Root+Xposed+Busybox for Bootloader Locked Moto X ATT/VZW

Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat
Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.
DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.
s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method
Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.
Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.
Hehe got to love step 9
System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks
jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here
Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.
DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?
Those files are needed by Jahrule
Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))
It works
It works great! Thank you very much! ATT xt1058.
eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.
Could someone please do a video on this. I'm having a little trouble.

A Complete Thread About Upgrading Samsung Galaxy S III to Android Lollipop 5.1.1

Hello everybody! I have searched for all the topics talking about How to your S III to Lollipop 5.1.1? So i'm here today to show you the complete steps to:
I - Root your Phone.
II - Flashing the recovery Mode.
III - Installing the ROM in your device.
IIII - Enjoying the Lollipop 5.1.1
HTML:
WARNING:
-I'm not responsable for any damage can caused in your device or losing your SD Card. Everything is working fine in my device.
I - Root your phone:
Rooting your device is so easy that means to give your OS a new options contains Flashing ROMs
So to root your phone you need a PC and a software called Odin. First search on it and download it
After downloading software: to open it:
1) Right Click on the Winrar ZIP.
2) Choose "extract files" option.
3) Then you'll have a folder open it.
4) Right Click on Odion.exe (application)
5) Choose "Run as administartion".
6) The Proogram will be opened.
7) Next to complete the rest of rooting you should get the access to download in your device by :
_Click the "-" Volume button + Power Button + Home Button together for a little while.
_ Then click "+" Volume Button.
8) Now Connect your PC with your device using USB cable then wait windows installs drivers (for 10 or 20 secs) and you'll see a blue case in the left corner upper.
9) Click on "PDA" Button and search the file "CF-Root".
10) Click on "Start" button after few minutes Odin will show in the up of the bleu square "RESET!"
If everything is done like the above steps then Reboot your phone and remove the USB cable . then you'll see a new application added called "Super SU" that means your device rooted successfully
Note: if you are not seeing the "CWM" on your device that means the "ClockWorkMod" application not installed yet so you must download it by the following steps:
1) Go to the PlayStore and write in the search bar: "Rom Manger".
2) Then you'll see "Rom Manager" application download it.
II - Flashing the recovery Mode:
So after you downloadthe clockworkmodmod application now you have to install the recovery on your device to do that:
1) Open the applicaion installed.
2) Choose the first option "Flash ClockWorkMod Recovery".
3) Choose your phone's name from the list once you find it, click on it.
4) Once the installing finished, Power off your phone
_Click "+" Volume Button + Power Button + Home Button simultanity (to ckeck the result).
And now the last part of all this.
III- Installing the ROM on your device:
Note: you must have a SD Card of 2GB or more
First thing to install the ROM you need to download GAPPS (Google Apps) and the ROM
Why we are needing GAPPS?
GAPPS is the complitation of google Apps on the new ROM.
You can download them from any website
After downloading them as a Winrar ZIP on your PC copy them and past them on your SD Card. Now to flash everything and install Lollipop on your Android device:
1) Put your SD Card on your device.
2) Click on "+" Volume Button and the power button and the home button in the same time.
3) The ClockWorkMod Recovery will open
_Go to "Wipe data/cache " option and click on it by the power button, then Select YES.
_ The Same thing in "Wipe cache" option.
Currently your device is wipped or formatted
Now Flash Your ROM:
_ Go to "install ZIP from SD Card " option, Select your ROM that u installed it on your SD Card by the power button.
_then the same thing to installing GAPPS.
Once Everything is done and you see "installing complete", Reboot your system now (open your device)
Finally your device is upgrading to Lollipop 5.1.1!
So yeah! that's all, Thank you for your support and we hope this work be helpful!! :laugh:
Reb0t said:
Hello everybody! I have searched for all the topics talking about How to your S III to Lollipop 5.1.1? So i'm here today to show you the complete steps to:
I - Root your Phone.
II - Flashing the recovery Mode.
III - Installing the ROM in your device.
IIII - Enjoying the Lollipop 5.1.1
HTML:
WARNING:
-I'm not responsable for any damage can caused in your device or losing your SD Card. Everything is working fine in my device.
I - Root your phone:
Rooting your device is so easy that means to give your OS a new options contains Flashing ROMs
So to root your phone you need a PC and a software called Odin. First search on it and download it
After downloading software: to open it:
1) Right Click on the Winrar ZIP.
2) Choose "extract files" option.
3) Then you'll have a folder open it.
4) Right Click on Odion.exe (application)
5) Choose "Run as administartion".
6) The Proogram will be opened.
7) Next to complete the rest of rooting you should get the access to download in your device by :
_Click the "-" Volume button + Power Button + Home Button together for a little while.
_ Then click "+" Volume Button.
8) Now Connect your PC with your device using USB cable then wait windows installs drivers (for 10 or 20 secs) and you'll see a blue case in the left corner upper.
9) Click on "PDA" Button and search the file "CF-Root".
10) Click on "Start" button after few minutes Odin will show in the up of the bleu square "RESET!"
If everything is done like the above steps then Reboot your phone and remove the USB cable . then you'll see a new application added called "Super SU" that means your device rooted successfully
Note: if you are not seeing the "CWM" on your device that means the "ClockWorkMod" application not installed yet so you must download it by the following steps:
1) Go to the PlayStore and write in the search bar: "Rom Manger".
2) Then you'll see "Rom Manager" application download it.
II - Flashing the recovery Mode:
So after you downloadthe clockworkmodmod application now you have to install the recovery on your device to do that:
1) Open the applicaion installed.
2) Choose the first option "Flash ClockWorkMod Recovery".
3) Choose your phone's name from the list once you find it, click on it.
4) Once the installing finished, Power off your phone
_Click "+" Volume Button + Power Button + Home Button simultanity (to ckeck the result).
And now the last part of all this.
III- Installing the ROM on your device:
Note: you must have a SD Card of 2GB or more
First thing to install the ROM you need to download GAPPS (Google Apps) and the ROM
Why we are needing GAPPS?
GAPPS is the complitation of google Apps on the new ROM.
You can download them from any website
After downloading them as a Winrar ZIP on your PC copy them and past them on your SD Card. Now to flash everything and install Lollipop on your Android device:
1) Put your SD Card on your device.
2) Click on "+" Volume Button and the power button and the home button in the same time.
3) The ClockWorkMod Recovery will open
_Go to "Wipe data/cache " option and click on it by the power button, then Select YES.
_ The Same thing in "Wipe cache" option.
Currently your device is wipped or formatted
Now Flash Your ROM:
_ Go to "install ZIP from SD Card " option, Select your ROM that u installed it on your SD Card by the power button.
_then the same thing to installing GAPPS.
Once Everything is done and you see "installing complete", Reboot your system now (open your device)
Finally your device is upgrading to Lollipop 5.1.1!
So yeah! that's all, Thank you for your support and we hope this work be helpful!! :laugh:
Click to expand...
Click to collapse
Hi Thanx, where to download the ROM package from?
ukchy123 said:
Hi Thanx, where to download the ROM package from?
Click to expand...
Click to collapse
Hi, Sorry but i can't add outside links that's why i didn't put links to download. (you know XDA rules :crying: )
Lollipop ROMs
[INDEX] Galaxy S3 - ROMs, Kernels, MODs, GUIDES [19/01/16]
Look there, to find a Lollipop ROM for S3.
Yes you can find there.
Trafalgar Square said:
[INDEX] Galaxy S3 - ROMs, Kernels, MODs, GUIDES [19/01/16]
Look there, to find a Lollipop ROM for S3.
Click to expand...
Click to collapse
yes you can find in this link.

trying to root Samsung Galaxy On5 G550T1 - TWRP, CF Autoroot FAILS

I can't figure out why my attempts to root my new On5 continue to fail halfway through.
I've tried different Odin versions...
can anyone offer some help, please?
can I use the AP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 stock rom...?
thanks for anyone's kind help...
Glenn
I just rooted my G550T1 (On5) yesterday - Odin/TWRP/SuperSU
I just went through this process for virtually the same phone. [G550T1UVU2AQC4; For your exact Model's S/W# like this, look in battery compartment or the box the phone came in]
Despite being over 6 months old, I figured I may as well post the information for future onlookers. I could have used this info yesterday.
For this post specifically regarding "failing half way through," I would hazard to guess that the firmware already installed on the phone is slightly more up-to-date than what you're trying to flash. Either that, or you don't have the right settings turned on to allow Odin to flash over the AP. Plus, how were you planning on rooting by flashing over the stock firmware in the first place? lol
Either way, I recommend just making sure what I'm about to say is what you've done so far.
Disclaimer: Rooting your phone, even attempting to, or using rooted apps can cause irreparable damage and turn it into a brick. Always make sure what you are using the root for is compatible with your model!!!
Notes:
- For rooting the Galaxy On5, Odin is merely to flash the recovery software to the device. The recovery software is where you install the root.
- For extra precaution, my method does not involve the external SD card. They seem to cause random issues for the first boot after rooting.
If you insist on doing it with the external SD card installed, MAKE SURE YOU HAVE NO APPS ALREADY TRANSFERRED TO THE EXTERNAL SD CARD!
So to start....
Requirements:
Windows PC with open USB port to download files and transfer the files [Back USB ports are more reliable for PC Desktops; All USB ports are fine with a laptop]
USB-A to USB-B cable [Stock micro-USB cable]
Samsung On5 [Recommended ~100% battery]
A little patience
Galaxy On5 Settings:
#1 - Enable Developer Options
Settings > About device > Build Number - Keep tapping the Build Number until it says you're enabling Developer options, and continue tapping until you succeed.
#2 - OEM Unlock and USB Debugging
Settings > Developer options > Make sure both "OEM Unlock" and "USB Debugging" are turned on
#3 - Enable Unknown Sources
Settings > Lock screen and security > Make sure "Unknown sources" is turned on
Downloads: [4]
Samsung USB Driver - Link to Samsung's download for their Android USB driver for mobile phones. [Install regardless of whether you can already transfer from PC to Android]
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin - Link to an XDA Forum Post which, unlike most, has kept updated and added all versions. [I recommend to use the most up-to-date version; Remember to click the file name of the attachment to download]
https://forum.xda-developers.com/showthread.php?t=2711451
Extract the Odin zip file to an easily accessible folder like "My Documents" and/or create its own file "Odin"
TWRP - Link to the always most up-to-date version for the Galaxy On5. [I don't recommend other recoveries; This is simple and reliable]
https://twrp.me/devices/samsunggalaxyon5tmobile.html
Don't unzip TWRP. Leave file zipped as-is and move it to the same folder as Odin; and/or create its own Sub-Folder for organization "Documents\Odin\TWRP"
SuperSU - Link to the SuperSU version I used that worked smoothly.
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Link to the official website for an updated version. [I would just use what you know works though; From the official page, follow the most recent SuperSU release link and find the .zip file]
https://chainfire.eu/
Where to put SuperSU
- Connect PC to Galaxy On5 [After installing USB Driver]
- Open the file where your SuperSU download is.
- Right-click SuperSU > Click Copy
- Now navigate to your On5 [Should be available in the left panel; if not go to "My Computer" and it should pop up]
- Find, or create, a folder you can easily remember inside the phone's internal memory [i.e; "Phone\Android" or create your own folder "Phone\TWRP"]
- Right click while inside the designated folder and paste the SuperSU zip
Time to start rooting:
Double check that android's settings, and the rooting files are in the right places.
Download Mode:
- Disconnect from your PC, and completely shut down your On5.
- After it is off; Press and hold first the Volume Down Button + The Home Screen Button + Then The Power Button.
- Hold the combination until download mode pops up
- Press Volume Up
- You are now ready for Odin
Odin:
- Start Odin on your PC [Run as Administrator for extra assurance]
- Click the "AP" slot, and navigate to the folder where you saved the TWRP zip file, and select it
- In a moment, the file should be listed in the "AP" section
- Verify that the AP selection's checkbox is checked
- Under options on Odin, MAKE SURE "Re-Partition" IS NOT checked.
- Make sure "Auto-Reboot" and "F. Reset Time" are checked. [Auto-Reboot not required; Can manually shut off by battery removal after Odin gives the green "PASS" light]
- Plug your On5 into your PC now
- Odin will verify the connection with a little light blue box in the "ID:COM" section
- Double check settings
- Press the "Start" button
Odin results should say "PASS!" is green if the operation was done successfully.
If red "FAIL," then either try different versions of Odin, different USB slots, double check everything, or troubleshoot at your own risk. [Must remove battery and restart in download mode again to retry]
After Odin gives a "PASS!"
Booting Into TWRP Recovery:
- You might get lucky, and Odin automatically reboots the phone into TWRP.
-- If it does not reboot into TWRP, then let the phone finish loading to your homescreen and then fully shut it off. [If stuck in boot screen, then force shut-off with battery removal after disconnecting the device]
- To get into recovery from the phone being shut off, do the same as the Downloader, but by holding volume up instead of down.
[Hold Volume Up + Home Button + Power/Lock]
TWRP:
- On the start page, there will be a slider that will allow TWRP full access. Slide it.
- Go into recovery/restore/backup and create a recovery image in an easily-accessible folder like your other files [With SuperSU would be easiest]
- This may take a moment so be patient
- Once that is complete DO NOT REBOOT YET
- Go back to the home screen and go to "Install"
- Navigate to the file where you put the SuperSU zip [NOTICE: Instead of "Phone\TWRP"; your folder would be "sdcard\TWRP" despite it being on internal storage]
- If you can't see the zip file, make sure the button "Install from zip" is clicked instead of "install from image"
- Select the file
- Swipe to install, and then use the quick "erase cache" option TWRP gives after
- Click the reboot option
- You will be taken to their final page asking if you want to install their app, you don't have to. I actually recommend doing that at a later time. Swipe to reboot.
VUELA!
It will take some time to boot, but you should now be rooted!
Bootloop or boot screen freezing? [Make sure to give it time]
If you didn't take my advice and did it with the external SD card, shut off the phone, take out the SD card, and try booting again [Again allowing time to boot]
Wait until device is fully booted before reinserting SD card, then use a file browser to delete all Android files inside the SD card before you ever reboot or shut down again. [You might not remember what could have caused the problem after a while]
everything worked until i tried to go into recovery mode is there a alternative
Randeag said:
I just went through this process for virtually the same phone. [G550T1UVU2AQC4; For your exact Model's S/W# like this, look in battery compartment or the box the phone came in]
Despite being over 6 months old, I figured I may as well post the information for future onlookers. I could have used this info yesterday.
For this post specifically regarding "failing half way through," I would hazard to guess that the firmware already installed on the phone is slightly more up-to-date than what you're trying to flash. Either that, or you don't have the right settings turned on to allow Odin to flash over the AP. Plus, how were you planning on rooting by flashing over the stock firmware in the first place? lol
Either way, I recommend just making sure what I'm about to say is what you've done so far.
Disclaimer: Rooting your phone, even attempting to, or using rooted apps can cause irreparable damage and turn it into a brick. Always make sure what you are using the root for is compatible with your model!!!
Notes:
- For rooting the Galaxy On5, Odin is merely to flash the recovery software to the device. The recovery software is where you install the root.
- For extra precaution, my method does not involve the external SD card. They seem to cause random issues for the first boot after rooting.
If you insist on doing it with the external SD card installed, MAKE SURE YOU HAVE NO APPS ALREADY TRANSFERRED TO THE EXTERNAL SD CARD!
So to start....
Requirements:
Windows PC with open USB port to download files and transfer the files [Back USB ports are more reliable for PC Desktops; All USB ports are fine with a laptop]
USB-A to USB-B cable [Stock micro-USB cable]
Samsung On5 [Recommended ~100% battery]
A little patience
Galaxy On5 Settings:
#1 - Enable Developer Options
Settings > About device > Build Number - Keep tapping the Build Number until it says you're enabling Developer options, and continue tapping until you succeed.
#2 - OEM Unlock and USB Debugging
Settings > Developer options > Make sure both "OEM Unlock" and "USB Debugging" are turned on
#3 - Enable Unknown Sources
Settings > Lock screen and security > Make sure "Unknown sources" is turned on
Downloads: [4]
Samsung USB Driver - Link to Samsung's download for their Android USB driver for mobile phones. [Install regardless of whether you can already transfer from PC to Android]
http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin - Link to an XDA Forum Post which, unlike most, has kept updated and added all versions. [I recommend to use the most up-to-date version; Remember to click the file name of the attachment to download]
https://forum.xda-developers.com/showthread.php?t=2711451
Extract the Odin zip file to an easily accessible folder like "My Documents" and/or create its own file "Odin"
TWRP - Link to the always most up-to-date version for the Galaxy On5. [I don't recommend other recoveries; This is simple and reliable]
https://twrp.me/devices/samsunggalaxyon5tmobile.html
Don't unzip TWRP. Leave file zipped as-is and move it to the same folder as Odin; and/or create its own Sub-Folder for organization "Documents\Odin\TWRP"
SuperSU - Link to the SuperSU version I used that worked smoothly.
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Link to the official website for an updated version. [I would just use what you know works though; From the official page, follow the most recent SuperSU release link and find the .zip file]
https://chainfire.eu/
Where to put SuperSU
- Connect PC to Galaxy On5 [After installing USB Driver]
- Open the file where your SuperSU download is.
- Right-click SuperSU > Click Copy
- Now navigate to your On5 [Should be available in the left panel; if not go to "My Computer" and it should pop up]
- Find, or create, a folder you can easily remember inside the phone's internal memory [i.e; "Phone\Android" or create your own folder "Phone\TWRP"]
- Right click while inside the designated folder and paste the SuperSU zip
Time to start rooting:
Double check that android's settings, and the rooting files are in the right places.
Download Mode:
- Disconnect from your PC, and completely shut down your On5.
- After it is off; Press and hold first the Volume Down Button + The Home Screen Button + Then The Power Button.
- Hold the combination until download mode pops up
- Press Volume Up
- You are now ready for Odin
Odin:
- Start Odin on your PC [Run as Administrator for extra assurance]
- Click the "AP" slot, and navigate to the folder where you saved the TWRP zip file, and select it
- In a moment, the file should be listed in the "AP" section
- Verify that the AP selection's checkbox is checked
- Under options on Odin, MAKE SURE "Re-Partition" IS NOT checked.
- Make sure "Auto-Reboot" and "F. Reset Time" are checked. [Auto-Reboot not required; Can manually shut off by battery removal after Odin gives the green "PASS" light]
- Plug your On5 into your PC now
- Odin will verify the connection with a little light blue box in the "ID:COM" section
- Double check settings
- Press the "Start" button
Odin results should say "PASS!" is green if the operation was done successfully.
If red "FAIL," then either try different versions of Odin, different USB slots, double check everything, or troubleshoot at your own risk. [Must remove battery and restart in download mode again to retry]
After Odin gives a "PASS!"
Booting Into TWRP Recovery:
- You might get lucky, and Odin automatically reboots the phone into TWRP.
-- If it does not reboot into TWRP, then let the phone finish loading to your homescreen and then fully shut it off. [If stuck in boot screen, then force shut-off with battery removal after disconnecting the device]
- To get into recovery from the phone being shut off, do the same as the Downloader, but by holding volume up instead of down.
[Hold Volume Up + Home Button + Power/Lock]
TWRP:
- On the start page, there will be a slider that will allow TWRP full access. Slide it.
- Go into recovery/restore/backup and create a recovery image in an easily-accessible folder like your other files [With SuperSU would be easiest]
- This may take a moment so be patient
- Once that is complete DO NOT REBOOT YET
- Go back to the home screen and go to "Install"
- Navigate to the file where you put the SuperSU zip [NOTICE: Instead of "Phone\TWRP"; your folder would be "sdcard\TWRP" despite it being on internal storage]
- If you can't see the zip file, make sure the button "Install from zip" is clicked instead of "install from image"
- Select the file
- Swipe to install, and then use the quick "erase cache" option TWRP gives after
- Click the reboot option
- You will be taken to their final page asking if you want to install their app, you don't have to. I actually recommend doing that at a later time. Swipe to reboot.
VUELA!
It will take some time to boot, but you should now be rooted!
Bootloop or boot screen freezing? [Make sure to give it time]
If you didn't take my advice and did it with the external SD card, shut off the phone, take out the SD card, and try booting again [Again allowing time to boot]
Wait until device is fully booted before reinserting SD card, then use a file browser to delete all Android files inside the SD card before you ever reboot or shut down again. [You might not remember what could have caused the problem after a while]
Click to expand...
Click to collapse
everything worked until I got into recovery mode and nothing would load the android icon gear were turning then said it was nothing is there an alternative to gt into recovery mode????

[GP, G3, GP7.8] TWRP & alternative firmware

TWRP for Nook Glowlight Plus / Nook Glowlight 3 / Nook Glowlight Plus 7.8:
Download: https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases
Alternative firmware
Version: 1.04.4140
URL: https://drive.google.com/open?id=1mvCv3GR0KR56-NTuubIuGcuxS8Ymc9t-
Supported devices:
- Nook Glowlight Plus;
- Nook Glowlight 3;
- Nook Glowlight Plus 7.8";
Installation:
- unmount /system partition (if mounted);
- install (using TWRP);
- (when coming from other firmware) reset to factory defaults; // Wipe > Swipe to Factory Reset
- clear dalvik-cache;
Features:
- better stability (compared to stock fw);
- convenient status-bar;
Changes (against original firmware):
- slimmed down the firmware by removing all trash;
- pre-installed Simple Ink Launcher;
- device-specific adaptation;
Changes (1.02.4140):
- added: buttons config for Nook Glowlight 3;
- fixed: screen redraw issue in some apps (CoolReader, AlReader, FBReader, etc);
Changes (1.03.4140):
- fixed: disabled wi-fi auto switch-off after 10 minutes;
- added: file manager - MiXplorer;
Changes (1.04.4140):
- added support for Nook Glowlight Plus 7.8";
Screenshot:
see attachment
Notes:
If you your wi-fi connection is unstable try to disabled "Wi-Fi optimization" (Settings -> Wi-Fi -> Advanced).
From author:
The only firmware that does not freezes completely in my usage scenario.
Has feature not found in any other firmware - ability to adjust screen contrast.
Has a dedicated button for screen refresh in status-bar.
I highly advice to flash TWRP before tinkering with firmware or else in case anything goes wrong it may be difficult to restore your device (since stock recovery is not very functional you may need to pry your device open to access serial console).
As usual: I'm not responsible for any harm done, use it on you own risk.
Hello
Can I return original firmware?
Thank you!
dnt83 said:
Can I return original firmware?
Click to expand...
Click to collapse
For sure. You may need to fix updater-script from original update.zip thou.
Got GP 7.8 recently and installed ReLaunch on it. It works fine mostly except for the lack of contrast control.
Wanted to try this firmware to see how the contrast control will work. First started TWRP in test mode. After installing the firmware and rebooting there is the standard android "optimising packages" messages. However the boot process is then stuck at a three dots animation.
Is this supposed to take a long time or did I miss some step?
---------- Post added at 13:03 ---------- Previous post was at 13:03 ----------
RyogoNA said:
For sure. You may need to fix updater-script from original update.zip thou.
Click to expand...
Click to collapse
I don't have that file, could you share it?
---------- Post added at 13:04 ---------- Previous post was at 13:03 ----------
GLP781 said:
Got GP 7.8 recently and installed ReLaunch on it. It works fine mostly except for the lack of contrast control.
Wanted to try this firmware to see how the contrast control will work. First started TWRP in test mode. After installing the firmware and rebooting there is the standard android "optimising packages" messages. However the boot process is then stuck at a three dots animation.
Is this supposed to take a long time or did I miss some step?
Click to expand...
Click to collapse
Hello
Try to Wipe remove all data (Using TWRP) then install this firmware again
Hello
Try to Wipe remove all data (Using TWRP) then install this firmware again
Click to expand...
Click to collapse
Thanks. This worked.
The firmware is clean and quite stable. Thanks RyogoNA.
Is there a way to re-install the original NOOK reader (the app only)? It is not the best reader but the physical buttons page turning is nice option to have sometimes.
GLP781 said:
Is this supposed to take a long time or did I miss some step?
Click to expand...
Click to collapse
No, not longer than 5 minutes. Please make sure that you perform a "factory reset" in TWRP - this is crucial.
GLP781 said:
Is there a way to re-install the original NOOK reader (the app only)?
Click to expand...
Click to collapse
Well... You can try to extract it from stock fw and copy it into /system/app, but I don't think it will work correctly.
GLP781 said:
It is not the best reader but the physical buttons page turning is nice option to have sometimes.
Click to expand...
Click to collapse
If you just need physical buttons, you can modify /system/usr/keylayout/imx-keypad.kl. Keys 191/192 are left buttons, and keys 193/194 are right buttons - you can change them to PAGE_UP/PAGE_DOWN or VOLUME_UP/VOLUME_DOWN, depending on what you need. Or you may use any application that does button remapping.
dnt83 said:
I don't have that file, could you share it?
Click to expand...
Click to collapse
Glowlight Plus stock fw: http://su.barnesandnoble.com/nook/piper/5.0/piper/0.118/update.zip
Glowlight 3 stock fw: http://su.barnesandnoble.com/nook/piper/5.0/jay/0.117/update.zip
Glowlight Plus 7.8 stock fw: http://su.barnesandnoble.com/nook/piper/5.0/quill/0.133/update.zip
The part you may need to remove is highlighted (see attached pics), but you can try without removing it - it may work just like that.
RyogoNA said:
The part you may need to remove...
Click to expand...
Click to collapse
Or you could just:
Code:
# setprop ro.product.device ntx_6sl
Thank you for your support
Thank you for your support. How can I change my sleep mode photos?
How can I change my sleep mode photos?
Click to expand...
Click to collapse
Well... Putting images in /sdcard/sleep should work, but I got some reports that it work not for everyone and I'm still not sure what the issue is.
but how do you install this alternative firmware...how does one install TWRP on a Nook Glowlight device? I googled it all over and I could not find specific information anywhere...would really appreciate the help!
thanks
RyogoNA said:
TWRP for Nook Glowlight Plus / Nook Glowlight 3 / Nook Glowlight Plus 7.8:
Download: https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases
Alternative firmware
Version: 1.04.4140
URL: https://drive.google.com/open?id=1mvCv3GR0KR56-NTuubIuGcuxS8Ymc9t-
Supported devices:
- Nook Glowlight Plus;
- Nook Glowlight 3;
- Nook Glowlight Plus 7.8";
Installation:
- unmount /system partition (if mounted);
- install (using TWRP);
- (when coming from other firmware) reset to factory defaults; // Wipe > Swipe to Factory Reset
- clear dalvik-cache;
Features:
- better stability (compared to stock fw);
- convenient status-bar;
Changes (against original firmware):
- slimmed down the firmware by removing all trash;
- pre-installed Simple Ink Launcher;
- device-specific adaptation;
Changes (1.02.4140):
- added: buttons config for Nook Glowlight 3;
- fixed: screen redraw issue in some apps (CoolReader, AlReader, FBReader, etc);
Changes (1.03.4140):
- fixed: disabled wi-fi auto switch-off after 10 minutes;
- added: file manager - MiXplorer;
Changes (1.04.4140):
- added support for Nook Glowlight Plus 7.8";
Screenshot:
see attachment
Notes:
If you your wi-fi connection is unstable try to disabled "Wi-Fi optimization" (Settings -> Wi-Fi -> Advanced).
From author:
The only firmware that does not freezes completely in my usage scenario.
Has feature not found in any other firmware - ability to adjust screen contrast.
Has a dedicated button for screen refresh in status-bar.
I highly advice to flash TWRP before tinkering with firmware or else in case anything goes wrong it may be difficult to restore your device (since stock recovery is not very functional you may need to pry your device open to access serial console).
As usual: I'm not responsible for any harm done, use it on you own risk.
Click to expand...
Click to collapse
pieta9999 said:
but how do you install this alternative firmware...how does one install TWRP on a Nook Glowlight device? I googled it all over and I could not find specific information anywhere...would really appreciate the help!
thanks
Click to expand...
Click to collapse
Not going to cover it here completely, but:
1) you need to enable adb;
2) then in command line "adb reboot fastboot";
3) and "fastboot flash recovery twrp.img";
This is awesome! I’ve been cobbling together some of the various tweaks but this looks to have the vast majority of the stuff and has an awesome status bar.
thank you so much for the answer. I installed TWRP following the instructions you provided. but how do I start TWRP now so that I can proceed to the next step of installing the new software, please?
thank you so much!
RyogoNA said:
Not going to cover it here completely, but:
1) you need to enable adb;
2) then in command line "adb reboot fastboot";
3) and "fastboot flash recovery twrp.img";
Click to expand...
Click to collapse
pieta9999 said:
thank you so much for the answer. I installed TWRP following the instructions you provided. but how do I start TWRP now so that I can proceed to the next step of installing the new software, please?
thank you so much!
Click to expand...
Click to collapse
Well... What makes me sad is the fact that there an instruction on github (where you downloaded twrp from).
But anyway, the only stable way to get into recovery is to execute "adb reboot recovery" from command line.
thank you very much for your patience. for some reason the instructions would not show up on github on firefox, unless I would click on Code...(sorry for that)
So, I was able to boot to TWRP, but once I install the 1.04.4140 zip I get an error saying:
"assert failed: package extract die (system, /system)...I also attaching a picture.
thank you thank you
RyogoNA said:
Well... What makes me sad is the fact that there an instruction on github (where you downloaded twrp from).
But anyway, the only stable way to get into recovery is to execute "adb reboot recovery" from command line.
Click to expand...
Click to collapse
pieta9999 said:
thank you very much for your patience. for some reason the instructions would not show up on github on firefox, unless I would click on Code...(sorry for that)
So, I was able to boot to TWRP, but once I install the 1.04.4140 zip I get an error saying:
"assert failed: package extract die (system, /system)...I also attaching a picture.
thank you thank you
Click to expand...
Click to collapse
For some reason I cannot see the picture, but I'm guessing there is an "error status 7" which means that you need to unmount /system partition before installation.

Categories

Resources