Related
If you are using ADB Shell on a Windows machine and try to LS with busybox on your phone it will add color coding along with directory and file names.
To get rid of this you need only need to type [1] in the command prompt.
If you would like an LL type function added you can also put in [2].
[1] alias ls='ls --color=never'
[2] alias ll='ls -la --color=never'
Is there any way to get these aliases to stick?
The aliases go away every time I open a new ADB Shell. :\
##########edit1
I found that you can use PuTTYcyg to properly display the colors if you have Cygwin installed on your machine.
I just selected "Cygterm" for "Connection type" and put "adb shell" in "Command (use - for login shell)".
I would still like to have an alias for LL at least if we can figure out a way to get the aliases to stick.
Thanks!
##########edit2
In case people have no idea what I'm talking about.
Busybox LS output with color in Windows CMD:
Code:
# ls
ls
←[1;34mcache←[0m ←[1;36metc←[0m ←[1;34mroot←[0m
←[1;34mconfig←[0m ←[1;32minit←[0m ←[1;34msbin←[0m
←[1;36md←[0m ←[1;32minit.desirec.rc←[0m ←[1;34msdcard←[0m
←[1;34mdata←[0m ←[1;32minit.goldfish.rc←[0m ←[1;34msqlite_stmt_journals←[0m
←[0;0mdefault.prop←[0m ←[1;32minit.rc←[0m ←[1;34msys←[0m
←[1;34mdev←[0m ←[0;0mlogo.rle←[0m ←[1;34msystem←[0m
←[1;34memmc←[0m ←[1;34mproc←[0m
Busybox LS output without color in Windows CMD:
Code:
# ls --color=never
ls --color=never
cache etc root
config init sbin
d init.desirec.rc sdcard
data init.goldfish.rc sqlite_stmt_journals
default.prop init.rc sys
dev logo.rle system
emmc proc
And now color just looks like one of the weirdest words to me after looking at it for so long....
COLOR.
I got an LL going if anyone is interested. Basically using this guys instructions but making it for ll instead of dir.
1) Create a file named ll in /system/xbin
With this in it [NO COLOR]:
Code:
#!/system/xbin/sh
ll(){
ls -la --color=never [email protected]
}
ll [email protected]
OR
With this in it [COLOR]:
Code:
#!/system/xbin/sh
ll(){
ls -la [email protected]
}
ll [email protected]
2) Set file ownership/permissions
Get an ADB Shell:
Code:
cd /system/xbin
chown 0 ll
chmod 755 ll
The LL command will work immediately after setting ownership/permissions on the LL file. It's a workaround for now but works great.
Updated first post.
Not at all
The shortest way to do it is:
Code:
# alias ls="ls --color=never"
What I wonder is how to get rid of the annoying ECHO..
Long term fix?
Any better ways to fix this? I never used to have this problem, but all of a sudden, after messing with ADB over WiFi, now I do have this problem
http://forum.xda-developers.com/showthread.php?p=14564633
The alias only works for a single cmd session
update
ScottHW said:
Any better ways to fix this? I never used to have this problem, but all of a sudden, after messing with ADB over WiFi, now I do have this problem
Click to expand...
Click to collapse
Small update: I noticed that I actually only have the problems with ls -al when the phone is fully booted. When I use adb booted in Recovery (CWM) the file listings are fine.
It's possible that I have never used adb while the phone is fully booted before, and just assumed that the Recovery behavior was universal and when I got the funky behavior, it wasn't messing around with ADB, it was just because I didn't know what "normal" was.
Short term fix is still just to use an alias for ls
But you have to redo it every time you restart adb
Hi!
I just upgraded to 4.4.3 and lost root access. The /system/xbin/su binary is still present, but does nothing:
Code:
[email protected]:/ $ which su
/system/xbin/su
[email protected]:/ $ ls -l /system/xbin/su
-rwsr-sr-x root shell 104576 2013-12-13 19:17 su
[email protected]:/ $ su
1|[email protected]:/ $ whoami
whoami: unknown uid 2000
I booted into fast boot mode. The information there says (if it is of any help):
Code:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - XXX
SIGNING - not defined yet
LOCK STATE - UNLOCKED
And I can't seem to boot into recovery mode - it just shows "android" lying on his back with his tummy open with a red triangle (with exclamation mark) .
I guess the 4.3 update changed some stuff. I'm on a Mac. What can I do to regain root access?
Regards,
Miha.
Further to that, I stupidly also accepted the update - CWM seems to have been wiped, and when I try to flash it, I get the following error. The weird (and gratifying) thing is that other than that, the tablet seems to operating fine - for which I'm grateful - is there anything I can try to sort it out?
I was completely stock (but rooted with CWM 6.0.4.3).
Code:
goatees-MacBook-Air:platform-tools goatee$ fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_read failed with status e00002ed
ERROR: usb_read failed with status e000404f
sending 'recovery' (7318 KB)...
ERROR: usb_read failed with status e000404f
FAILED (status read failed (No such file or directory))
finished. total time: 3.057s
mihaval said:
Hi!
I just upgraded to 4.4.3 and lost root access. The /system/xbin/su binary is still present, but does nothing:
Code:
[email protected]:/ $ which su
/system/xbin/su
[email protected]:/ $ ls -l /system/xbin/su
-rwsr-sr-x root shell 104576 2013-12-13 19:17 su
[email protected]:/ $ su
1|[email protected]:/ $ whoami
whoami: unknown uid 2000
I guess the 4.3 update changed some stuff. I'm on a Mac. What can I do to regain root access?
Regards,
Miha.
Click to expand...
Click to collapse
Ok, so I've resolved my problem. I don't know if it's coincidence, but this time when I tried to reflash cwm
Instead of doing
Code:
fastboot flash recovery recovery-blah-grouper.img
I did this - and it worked
Code:
./fastboot flash recovery recovery-blah-grouper.img
This time, it flashed successfully, which let me reinstall root (by flashing the Super SU .zip)
I'm in OS X, (used *nix for the past 18 years or so), and it was successfully starting the fastboot binary before - so perhaps it's just a coincidence. The only other thing I did different was that my USB keyboard wasn't plugged in.
---------- Post added at 09:14 PM ---------- Previous post was at 09:06 PM ----------
And in fact, if that doesn't work for you - towelroot should do the job. See http://forum.xda-developers.com/showthread.php?t=2783157 or http://www.towelroot.com
goatee said:
Ok, so I've resolved my problem. I don't know if it's coincidence, but this time when I tried to reflash cwm
Click to expand...
Click to collapse
I confirm that it works for me too. CWM asked me whether to fix su: "Possible root access lost. Fix su?" and I chose yes (the first time and now, when I reflashed recovery too). And that actually breaks it. On second run, I chose no, and su is working again.
I saw reports about 4.4.4 update coming - we'll what that brings us...
Miha
Ah. . . I wonder why the SWM root fix didn't work correctly. Anyhow, glad you're also back to normal .
mihaval said:
I confirm that it works for me too. CWM asked me whether to fix su: "Possible root access lost. Fix su?" and I chose yes (the first time and now, when I reflashed recovery too). And that actually breaks it. On second run, I chose no, and su is working again.
I saw reports about 4.4.4 update coming - we'll what that brings us...
Miha
Click to expand...
Click to collapse
Hello, I hope someone has seen this before. I am not sure how I managed to break S7, as it was working, initially. I am running PE1 firmware, and factory reset before following the root guide, in the verizon guide forums. But now I have the problem where supersu will not auto start on bootup. I have to connect the usb cable to my pc, and use adb and manually start it. Root and Supersu are loaded. The only thing I have to run is:
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
Then disconnect the usb cable, and all is well. Everything seems to be correct. What am I missing? I really do not want to start completely over. I have run the verizon debloat v2 and v8. I had to manually start supersu to flashfire the v8 script. Also in the same guide. All the root checker apps will see that you have root, but they say you are missing a super user app.
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
mkdir: '/su': File exists
cp: /cache/stock_boot_*: No such file or directory
cp: bad '/cache/stock_boot_*': No such file or directory
/data/su.img: recovering journal
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 25/2048 files, 1399/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mount: No such file or directory
mount: No such file or directory
supolicy v2.74 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
(Android M policy compatibility mode)
- Success
<Then disconnect the usb cable, supersu will work fine now.>
C:\adb>adb shell cat /system/etc/init.sec.boot.sh
#!/system/bin/sh
echo "init.sec.boot.sh: start" > /dev/kmsg
# start deferred initcalls
cat /proc/deferred_initcalls
## strace for system_server
#str=""
#while [ "$str" = "" ]; do
# str=`ps | grep system_server`
# sleep 0.1
#done
#
#pid=${str:10:4}
#echo "init.sec.boot.sh: strace -tt -T -o /data/log/strace.txt -p ${pid}" > /dev/kmsg
#strace -tt -T -o /data/log/strace.txt -p ${pid}
/system/etc/launch_daemonsu.sh
/data/s7startup/startupscript.sh
C:\adb>adb shell ls -la /system/etc/launch_daemonsu.sh
-rwx------ root root 4686 2016-07-03 13:32 launch_daemonsu.sh
Thanks again.
Did you push the supersu app to you device?
Is that to say uve got supersu installed but it won't start? If that's so I would check the box for start supersu during bootup. Unless im just completely missing your issue and im sorry if I am.
You have to use the dd method to flash the misc.img.
do this in adb.
adb shell
su
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img
exit
exit
adb pull /sdcard/misc.img
Then post a link to your misc.img so I can edit it for you.
Or just post the backup of your misc.img. You did make one I hope.
Always make a backup before you change things. That's a golden rule.
If not no big deal this time. But get in that habit.
If you didn't make a backup then let me know.
Also put the phone in download / fastboot mode.
type
fastboot getvar all
Post that info for me. It should look like
C:\Windows\system32>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a32eul
(bootloader) version: 1.0
(bootloader) imei: 352678075675006
(bootloader) version-main: 1.23.1550.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U113251151_47.00.51016G
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PM911000
(bootloader) cid: 11111111
all:
finished. total time: 0.015s
@BigCountry907 thanks a lot for your time. So I pulled the misc.img and zipped it which I have attached to this comment. However, it's that of metro PCs that flashed and I didn't make a backup of the Sprint one sadly. Going forward, I will make backups before editing anything. These are the details of my fastboot getvar all
bootloader) kernel: lk
(bootloader) product: htc_a32ewhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.00.0000.0
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PM920000
(bootloader) cid: 11111111
all:
finished. total time: 0.080s
As regards moving comments from the previous thread, I think the best way would be to identify the mod of the 626 thread and mail him to do the moving
@doyin116
It's not a good idea to post your imei #
I do it cause my device isn't activated and I'm lazy.
But if your phone is activated I think they could identify you by imei.
Or someone might try to use it.
Edit your post and take that out.
Also I notice your cid is set to supercid.
If you are s-off you don't even need to edit the misc to downgrade.
Are you s-off.
@doyin116
Try and flash the regular marshmallow RUU from HTC.
We will just start fresh that way.
The misc image for your phone
(bootloader) version-main: 1.00.0000.0
Should be. version-main: 1.00.000.0. ,---Notice 3 digits and not 4 in the 3rd set.
Flashing the RUU will put everything back and then we will work on the downgrade
BigCountry907 said:
@doyin116
It's not a good idea to post your imei #
I do it cause my device isn't activated and I'm lazy.
But if your phone is activated I think they could identify you by imei.
Or someone might try to use it.
Edit your post and take that out.
Also I notice your cid is set to supercid.
If you are s-off you don't even need to edit the misc to downgrade.
Are you s-off.
Click to expand...
Click to collapse
@BigCountry907 thanks for the heads up, I've removed the imei. Yeah I'm S-off and set to supercid. I guess I have to try flashing the ruu again, will do that and get back to you
Update:
I'm glad to report that I successfully downgraded to 5.1. @BigCountry907 I guess the next step now is building a custom kernel to flash. How's that going?
@BigCountry907 please is there any update on the creation of a custom kernel for the Sprint 626s?
@ doyin116
I will see what I can do.
I've been jumping around between my projects thus not really finishing any specifically.
Are you good with ADB?
I have not generated a flashable zip so you will need to use adb to copy the modules to the device and flash the kernel with fastboot.
At any rate I will attempt to do this today.
@doyin116
I have the sprint kernel ready to rock.
Let me put it all together and write an instruction how to get it all loaded.
You must have ADB on the computer in order to load everything right.
I hope you know how to use adb.
I will give you the commands but it is up to you to get this custom kernel and modules installed correctly.
Be back momentarily
Loading Custom Kernel For Sprint
Ok Here We Go.
1 ) Download the zip file " kernel-a32ewhl.zip"
2 ) Unzip the file
Create a folder somewhere on the computer.
Move kernel-a32ewhl.zip into that folder.
Unzip the kernel-a32ewhl.zip in that folder
You should see all of the following
A ) File "a32ewhl-boot.img" <<<<------ ( This is the kernel / boot image )
B ) Folder "modules" <<<<------ ( This is all the modules not including the required symlinks )
a. There are 2 modules "itson_module1.ko" & "itson_module2.ko" These have not been re compiled. I don't have source code for these.
The version has been set correctly for the new kernel so they should run hopefully.
The modules have something to do with Sprint Activation so check and make sure activation is working right.
b. There are 4 Moc_ modules. Theese are for crypto and affect running paid for apps. They should work since the kernel version is
set right. If you have any paid for apps test them.
c. The rest of the modules have been built with the new kernel and will be no trouble. Be sure to test wi-fi well. We might need an
adjustment.
C ) Folder "wcnss" these are configuration files for the wi-fi. Since we rebuilt the wlan module I recommend using these configuration files.
Some of the configuration can be changed and settings changed. You can look into that if you want. But we are not going there today.
3 ) Copy everything to the external sd card.
PLEASE FOLLOW ALL THESE INSTRUCTIONS EXACTLY !!
Make a folder on the external sdcard called new-kernel. You can do this with the phone connected to the computer or with the sdcard in a card reader connected to the computer.
Copy the modules folder inside of the new-kernel folder
Copy the wcnss folder inside of the new-kernel folder
Copy the a32ewhl-boot.img to the place on your computer where you can use fastboot.
If you are running windows search for fastboot.exe using file explorer.
Copy a32ewhl-boot.img to the same folder as fastboot.exe
Open a command window and cd to the directory where fastboot.exe is in.
Similar to
cd c:\android\sdk\platform-tools\
If you type dir
You should see fastboot.exe and a32ewhl-boot.img in the list of files.
4 ) Install the new modules into the phone
After you have copied all the files to the sd card and put the sd card in the phone and rebooted the phone.
Connect the phone to the computer via USB.
PAY ATTENTION HERE THEESE STEPS ARE CRUCIAL>
Start a shell as root.
Code:
adb shell
su
Re-Mount /system as read write. ( ERRORS ARE NOT ACCEPTABLE )
Code:
mount -o rw,remount,rw /system
Remove all exsisting Modules
Code:
rm -rf /system/lib/modules/
rm -rf /system/etc/firmware/wlan/prima/WCNSS_cfg.dat
rm -rf /system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
rm -rf /system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin
Copy new modules
Code:
cp -rf /sdcard2/new-kernel/modules/ /system/lib/modules/
Copy new wcnss config
Code:
cp /sdcard2/new-kernel/wcnss/WCNSS_cfg.dat /system/etc/firmware/wlan/prima/WCNSS_cfg.dat
cp /sdcard2/new-kernel/wcnss/WCNSS_qcom_cfg.ini /system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
cp /sdcard2/new-kernel/wcnss/WCNSS_qcom_wlan_nv.bin /system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin
Re-Create all symlinks
Code:
ln -s /system/lib/modules/pronto/pronto_wlan.ko /system/lib/modules/wlan.ko
ln -s /system/lib/modules/moc_crypto.ko.3.10 /system/lib/modules/moc_crypto.ko
ln -s /system/lib/modules/crypto_test_mod.ko.3.10 /system/lib/modules/crypto_test_mod.ko
ln -s /system/lib/modules/moc_crypto_api_tmpl.ko.3.10 /system/lib/modules/moc_crypto_api_tmpl.ko
ln -s /system/lib/modules/moc_platform_mod.ko.3.10 /system/lib/modules/moc_platform_mod.ko
Set the file permissions.
Code:
chmod 0644 /system/lib/modules/pronto/pronto_wlan.ko
chmod 0644 /system/lib/modules/ansi_cprng.ko
chmod 0644 /system/lib/modules/core_ctl.ko
chmod 0644 /system/lib/modules/crypto_test_mod.ko
chmod 0644 /system/lib/modules/crypto_test_mod.ko.3.10
chmod 0644 /system/lib/modules/dma_test.ko
chmod 0644 /system/lib/modules/ecryptfs.ko
chmod 0644 /system/lib/modules/evbug.ko
chmod 0644 /system/lib/modules/gpio_axis.ko
chmod 0644 /system/lib/modules/gpio_event.ko
chmod 0644 /system/lib/modules/gpio_input.ko
chmod 0644 /system/lib/modules/gpio_matrix.ko
chmod 0644 /system/lib/modules/gpio_output.ko
chmod 0644 /system/lib/modules/ice40-hcd.ko
chmod 0644 /system/lib/modules/itson_module1.ko
chmod 0644 /system/lib/modules/itson_module2.ko
chmod 0644 /system/lib/modules/mcDrvModule.ko
chmod 0644 /system/lib/modules/mcKernelApi.ko
chmod 0644 /system/lib/modules/moc_crypto.ko
chmod 0644 /system/lib/modules/moc_crypto.ko.3.10
chmod 0644 /system/lib/modules/moc_crypto.ko.sig.3.10
chmod 0644 /system/lib/modules/moc_crypto_api_tmpl.ko
chmod 0644 /system/lib/modules/moc_crypto_api_tmpl.ko.3.10
chmod 0644 /system/lib/modules/moc_platform_mod.ko
chmod 0644 /system/lib/modules/moc_platform_mod.ko.3.10
chmod 0644 /system/lib/modules/msm-buspm-dev.ko
chmod 0644 /system/lib/modules/mtd_nandbiterrs.ko
chmod 0644 /system/lib/modules/mtd_nandecctest.ko
chmod 0644 /system/lib/modules/mtd_oobtest.ko
chmod 0644 /system/lib/modules/mtd_pagetest.ko
chmod 0644 /system/lib/modules/mtd_readtest.ko
chmod 0644 /system/lib/modules/mtd_speedtest.ko
chmod 0644 /system/lib/modules/mtd_stresstest.ko
chmod 0644 /system/lib/modules/mtd_subpagetest.ko
chmod 0644 /system/lib/modules/mtd_torturetest.ko
chmod 0644 /system/lib/modules/radio-iris-transport.ko
chmod 0644 /system/lib/modules/spidev.ko
chmod 0644 /system/lib/modules/texfat.ko
chmod 0644 /system/lib/modules/wlan.ko
chmod 0644 /system/etc/firmware/wlan/prima/WCNSS_cfg.dat
chmod 0644 /system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
chmod 0644 /system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin
Now boot the phone to download mode if everything was successful. :good:
From the terminal command window on the computer flash the new boot image.
REMEMBER
Open a command window and cd to the directory where fastboot.exe is in.
Similar to
cd c:\android\sdk\platform-tools\
If you type dir
You should see fastboot.exe and a32ewhl-boot.img in the list of files.
Code:
fastboot flash boot a32ewhl-boot.img
If all went well then hit the reboot button.
You should now be running my custom kernel for sprint.
Let us know please.......You are the First.
I forgot to mention.
The kernel is compiled with a custom optimized toolchain.
Hopefully you see some performance improvement.
After your running go to about phone in your settings and check the kernel version your running.
It should be the following if your running the new kernel.
Linux version 3.10.49-perf-ga4f8dc4 ([email protected]) (gcc version 4.9.4 20160726 (optimized) (UBERTC-4.9.4) ) #1 SMP PREEMPT Thu Nov 17 14:09:00 EST 2016
This is the original kernel version.
Linux version 3.10.49-perf-ga4f8dc4 ([email protected]) (gcc version 4.7 (GCC) ) #2 SMP PREEMPT Fri Nov 6 18:11:47 CST 2015
@BigCountry907 thanks a lot. I will read the steps over and over to get them correctly and get back to you when I've flashed the kernel with a screenshot
@BigCountry907 after
adb
su
I did # mount -o rw,remount,rw /system and this came up:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
And with the thought that this is the normal result it was to come up with, I proceeded to remove the modules but at the end of every module, it wrote : read-only e.g rm: /system/lib/modules/ansi_cprng.ko: Read-only but I proceeded to Re-create sym links but the first sym link brought at the end 'file exists'. At this point, I knew something was wrong
What could I be doing wrong?
@doyin116
First make sure you are using this command.
mount -o rw,remount,rw /system
# should be at your shell command line allready.
If you typed #
That is the problem.
also -o is lower case O not number Zero.
Just in case.
You have to remember.
In linux or android. It's not like windows.
Every letter counts. And uppercase lowercase must match exactly.
Windows don't care about case, but android and linux do.
LINUX and linux and Linux would be considered the same file in windows.
In android world these would be considered 3 different files.
I double checked the command.
mount -o rw,remount,rw /system
It is working on my end so I am not sure why your having trouble.
Your boot-loader needs to be unlocked.
Your phone must be rooted.
If you are s-off this shouldn't be a problem. I never had trouble even with s-on.
At any rate you will need system mounted as RW in order to load the new modules.
Try again one line at a time.
copy and paste
Code:
adb shell
su
mount -o rw,remount,rw /system
The command should not reply back with anything in the terminal.
It will just go to the next line.
Your terminal will look similar to this.
Make sure you have the # and not $.
Code:
[email protected]:~$ adb shell
[email protected]_a13wlpp:/[COLOR="Red"] $[/COLOR] su
[email protected]_a13wlpp:/[COLOR="DarkGreen"] #[/COLOR] mount -o rw,remount,rw /system
[email protected]_a13wlpp:/ #
Every command that is posted above must complete without any errors.
If you are getting any errors post a screenshot.
Note I have added a section of commands in the flashing guide to set the file permissions.
Make sure to go back and do that too.
@BigCountry907 the problem was rather than mount -o rw,remount,rw /system, I added spaces between rw, remount and rw before /system. Will go through it again when I get home
@BigCountry907 everything was going on smoothly until I got to cp /sdcard2/new-kernel/wcnss/WCNSS_qcom_wlan_nv.bin /system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin and it came up with cp: /system/etc/firmware/wlan.prima/WCNSS_qcom_wlan_nv.bin: No such file or directory error and everything command I put in from then on came up with a no such file or directory error. Any advice please?
Check your sdcard and see if the files are actually there.
If you got all the modules installed then go ahead and flash the kernel.
The phone should boot ok.
BigCountry907 said:
Check your sdcard and see if the files are actually there.
If you got all the modules installed then go ahead and flash the kernel.
The phone should boot ok.
Click to expand...
Click to collapse
After many trials and errors, I was able to write the commands but after flashing the kernel via fastboot, my phone kept bootloping. I had to flash the stock boot.img back
Well flashing the stock boot image back is the way to go. You can also flash the ruu again to restore everything to default. That is the good thing.
I'm not 100% sure why the kernel will not boot for you.
I believe that the bootloader is not allowing the custom kernel to boot.
Even though the device is s-off and unlocked I think depending on carrier the bootloader is still verifying the signature of the kernel.
I have tried to load the spcs ruu on my metro and it flashes and loads but there is some kind of security that will not allow the rom to run. Actually the rom is running but the homescreen gets covered by the HTC boot-logo. I know it is booted up because when i press the power button I get the normal power off menu that you get when your booted into the rom.
I need to do some more testing. I have successfully booted the custom kernel I sent you on my metro-pcs.
The metro pcs is the the gen unlocked version. hence the a32eul.
I am downloading some more ruu's that I have access to to do some testing.
Either we are going to have to replace your radio and bootloaders or flash a ruu that accomplishes the same.
I have a JTAG box showing up tomorrow so If I brick my device I can fix it.
I would guess you are not in the same boat.
So we can try flashing the gen-unlocked ruu on your device. But I need to flash it on mine and make sure sprint is available in the ruu as a carrier.
Otherwise I am not sure how you will get all the settings like PRL ect. for sprint installed.
Worse case scenario I might have to make a sprint ruu with the replaced bootloader and radio from the unlocked ruu.
These are the kind of things I like to figure out.
BigCountry907 said:
Check your sdcard and see if the files are actually there.
If you got all the modules installed then go ahead and flash the kernel.
The phone should boot ok.
Click to expand...
Click to collapse
BigCountry907 said:
Well flashing the stock boot image back is the way to go. You can also flash the ruu again to restore everything to default. That is the good thing.
I'm not 100% sure why the kernel will not boot for you.
I believe that the bootloader is not allowing the custom kernel to boot.
Even though the device is s-off and unlocked I think depending on carrier the bootloader is still verifying the signature of the kernel.
I have tried to load the spcs ruu on my metro and it flashes and loads but there is some kind of security that will not allow the rom to run. Actually the rom is running but the homescreen gets covered by the HTC boot-logo. I know it is booted up because when i press the power button I get the normal power off menu that you get when your booted into the rom.
I need to do some more testing. I have successfully booted the custom kernel I sent you on my metro-pcs.
The metro pcs is the the gen unlocked version. hence the a32eul.
I am downloading some more ruu's that I have access to to do some testing.
Either we are going to have to replace your radio and bootloaders or flash a ruu that accomplishes the same.
I have a JTAG box showing up tomorrow so If I brick my device I can fix it.
I would guess you are not in the same boat.
So we can try flashing the gen-unlocked ruu on your device. But I need to flash it on mine and make sure sprint is available in the ruu as a carrier.
Otherwise I am not sure how you will get all the settings like PRL ect. for sprint installed.
Worse case scenario I might have to make a sprint ruu with the replaced bootloader and radio from the unlocked ruu.
These are the kind of things I like to figure out.
Click to expand...
Click to collapse
I'I'm not based in the U.S so getting the prl setting won't matter to me. The end game of all this is I can't get 3G and 4G to work in my country apparently because of some limitations Qualcomm made even though I've flashed the necessary bands that apply in my country through QPST. All I just need is something to remove the restrictions that prevent me from using 3g and 4g. I'm really frustrated nothing is working. Thanks anyways for trying to help
@doyin116
Are you using sprint as a carrier.
If not let me know what carrier you are using.
Either way follow my instructions below.
Ok Here we go.
I have an Idea. It's a little tricky but it should work.
You will need to follow my instructions to the letter.
First thing I want you to do is get your phone back to factory state.
#1 Flash the Lollipop RUU that I gave you before.
#2 Make sure you are S-off and Super CID 11111111 and boot loader is unlocked.
#3 Make sure you activate the phone and have everything working.
#4 Install TWRP Recovery and make a full backup select /system /system image /data /boot
I need to upload the general unlocked RUU for you to flash.
So I will do that now.
Let me know when you have completed the above steps.
What were gonna try is to flash the developer RUU.
Unfortunately it dosen't have sprint as a option for carrier.
So once we have the developer RUU installed we will install your backup in twrp.
Only to restore the /system /system image and /data.
Then maybe your sprint activation and settings will stick.
But you will still have the unlocked radio and bootloader.
Like I said let me know when your have done the previous steps.
So here's my issue. I transfered an epub file to my Nook Glowlight 3 using calibre, but when i ejected the device and started using the Nook. Not only did it not recognize my Epub file, the device slowed to a crawl! I restarted my Nook to see if this would fix the issue and now it's stuck at an infinite loading screen. I have tried hard resetting by holding the power button, but it keeps rebooting to an infinite loading screen. Could my device be possibly bricked? I think the issue might have been that I transfered a wrong type of epub file into the nook (the file was imported using calibre), which is incompatible with the nook software.
Any help would be appreciated, how do i get out of this infinite loading screen! I just want to be able to use my device again :/
Thanks.
No, it sounds like you did something else.
Do you have ADB working? Do:
Code:
# ps|grep u0 [color="red"]<- that's a zero[/color]
Do you see a bunch of processes?
That means that the Android subsystem is mostly running ok.
Is your launcher listed?
Code:
# getprop|grep bootanim
What does bn.bootanim.exit and service.bootanim.exit say?
You can disable the bootanimation entirely:
Code:
# mount -o rw,remount /system
# cd /system/bin
# mv bootanimation bootanimation.bak
# reboot
Can you start stuff?
Code:
# am start -n com.android.settings/.Settings
I'm actually having a *very* similar problem *only* when i have a 'real' launcher installed. In this case i'm using ReLaunchX, a launcher/file manager built for epaper devices. During boot the screen seems to be stuck on the boot animation. Here are some of the values from the commands you've reccomended to the OP:
Code:
[email protected]_6sl:/ $ ps|grep u0
u0_a2 2501 2080 321148 24152 ffffffff 00000000 S com.android.systemui
u0_a3 2517 2080 449348 87660 ffffffff 00000000 S com.nook.partner
u0_a0 2588 2080 319964 24852 ffffffff 00000000 S android.process.media
[email protected]_6sl:/ $ getprop|grep bootanim
[init.svc.bootanim]: [running]
[service.bootanim.exit]: [1]
[email protected]_6sl:/ $ am start -n com.android.settings/.Settings
Starting: Intent { cmp=com.android.settings/.Settings }
I have gone through the process of installing the launcher, rebooting, waiting for boot anim to finish (for up to 15-20 minutes), removing my launcher through adb, rebooting then re-installing the launcher. The launcher is the only thing that i've been chaning and it gets stuck on reboot *everytime* with the launcher installed.
P.S. I don't have root and i'm not interested in root, just the launcher and my safari queue app
If you have something taking over the Home intent, then the B&N stuff doesn't run.
The B&N stuff has the bootanimation termination hijacked.
Therefore the bootanimation will run for ever.
This will stop the bootanimation (just as a test).
Code:
$ setprop bn.bootanim.exit 1
You could write an app to do this.
You could modify the Glow3 bootanimation.
You could replace the Glow3 bootanimation with the Glow2 bootanimation.
You could delete the bootanimation.
You could write an app to do this.
You could modify the Glow3 bootanimation.
You could replace the Glow3 bootanimation with the Glow2 bootanimation.
You could delete the bootanimation.
Click to expand...
Click to collapse
Wouldn't these options require root?
Well, writing an app wouldn't need any special privilege, but it would be a round-about way to do it.
There's root & root & root. There's different degrees:
Disable all security on your normal boot image
Install a "superuser" app on your normal boot image to allow some apps to run as root
Set ro.secure to 0 to allow root ADB access
Set ro.debuggable to 1 to allow ADB to reconnect as root
Use a rooted recovery image to allow modification of your normal boot image
Load a rooted image over fastboot to allow modification of your normal boot image
Use the hardware root console that's already inside the Nook case
I wouldn't do #1, #2.
The other options don't really undermine security.
#7 requires opening the case.
Renate NST said:
[*]Set ro.secure to 0 to allow root ADB access
[*]Set ro.debuggable to 1 to allow ADB to reconnect as root
Click to expand...
Click to collapse
Hi Renate! I've tried to set these settings on a Glowlight 3, but as they don't seem to have effect might they require a pre-existing root to run them?
Code:
DESKTOP:~$ adb shell
[email protected]_6sl:/ $ setprop ro.secure 0
[email protected]_6sl:/ $ setprop ro.debuggable 1
[email protected]_6sl:/ $ mount -o rw,remount /system
mount: Operation not permitted
255|[email protected]_6sl:/ $
And just for good measure:
Code:
DESKTOP:~$ adb shell
[email protected]_6sl:/ $ su
/system/bin/sh: su: not found
Thank you for pointing me in any direction.
dotancohen said:
I've tried to set these settings on a Glowlight 3, but as they don't seem to have effect...
Click to expand...
Click to collapse
All the "ro.whatever" properties are read-only. They can only be set once.
They are usually already set in init.rc, default.prop or /system/build.prop.
ro.secure is in default.prop which is packed in the ramdisk of the image.
To modify it manually (vs. whatever scripts some people use), you need to pull the image, extract default.prop, text edit it, replace it, push the image.
Renate NST said:
To modify it manually (vs. whatever scripts some people use), you need to pull the image, extract default.prop, text edit it, replace it, push the image.
Click to expand...
Click to collapse
Thank you, I will try to pull and push the files directly. Have a great week!