Develop Bugs

[Discounted] [ONSCREEN KEYBOARD] [20-oct-2012] Linux on your Kindle Fire

hi!
This is my manual for how to install linux on your Kindle Fire.
there are some some steps you should to do.
1. Assure you have working adb and fastboot.
2. Download the follwing files: kernel (http://narod.ru/disk/59236733001.2e2d29e2c7bd762bd285ddf22a9c3fc6/boot1.img.html), bootloader (http://www.mediafire.com/?l6aaqgsdkiksfw0), and linux rootfs (new image has been uploaded.[url]http://depositfiles.com/files/mkpjrbixe
) , COTR recovery (http://narod.ru/disk/59880845001.8639567518823dcc1a9e4d51161ad75b/recovery_CTOR.img.html)
3. unpack these files and place them to adb & fastboot directory
4. reboot your kindle into fastboot.
5. boot CWM recovery by fastboot boot recovery_COTR.img
6.it's very important step. be careful with your sdcard partition.
now you'll resize it and make partition for Linux installation.
type the following in command line (windows/msdos) (terminal (linux/mac)):
~$: adb shell
then parted /dev/block/mmcblk0
then resize
then 12
then 2309 (start?)
then 5680 (end?) (it takes some time to resize partition)
then mkpart 13 5680 7597
then mkpart 14 7597 7609
then type quit
then mke2fs -T ext4 /dev/block/mmcblk0p13
then parted /dev/block/mmcblk0 name 14 linuxboot
then parted /dev/block/mmcblk0 name 13 linux
after doing this do the following:
mount sdcard storage to computer
now you must format sdcard partition.
in Windows select "Format" in main menu.
then place deb.img file to storage (it also called sdcard)
after copying debian image select safely remove in tray, but don't disconnect your kindle from computer.
on the screen tap Unmount button.
then type in command line: adb shell
then cd /mnt/sdcard/
then dd if=/deb.img of=/dev/block/mmcblk0p13
it took me about 20 minutes.
after that reboot into fastboot and type the following:
fastboot flash linuxboot boot1.img
fastboot flash bootloader u-boot.bin
7. all done.
8. enjoy
videos of how-to:
http://www.youtube.com/watch?edit=vd&v=4DBELK0cCpI
http://www.youtube.com/watch?edit=vd&v=F-IjFgBVHVM
there are images and video:
http://www.youtube.com/watch?v=NEXxSxhLoOI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to:
Hascode
Seishuku
And others

If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium

rbeavers said:
If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
what does you mean by p`n`p?

rbeavers said:
If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
you should follow guide by seishuku to install this. i simply solved some causes for myself. i think that my vision of this debian setup is rather good.
i also working on touchscreen bug and wifi.
later i`ll add suspending by power button and ability to managing sound volume and screen brightness

I was downloading it. But it looks kind of hard to install
Sent from my Amazon Kindle Fire using XDA Premium HD app

Very good job .
Envoyé depuis mon GT-I9000 avec Tapatalk

partition layout
link to download deb.img: http://depositfiles.com/files/aq1vtxbr0
after downloading my image you should make the same partition layout.
simply reboot your kindle in fastboot and boot it from CWM recovery (it contains program parted( partition manager). you should know how to use it).
after repartitioning select "reboot into fastboot" in reboot options in "reboot options"
and flash debian partition with my image (i called mine as "linux"(flash command is: fastboot flash linux deb.img))).
also you must install the seishuku's bootloader http://www.mediafire.com/?l6aaqgsdkiksfw0
and make empty partition to flash kernel (it must be named linuxboot link to download is:http://upwap.ru/2675690) (partition number for debian should be 13!!!!)
you MUST flash bootloader ONLY after flashing debian image!!!
because every when you flash bootloder you update partition scheme in bootloader configuration.
MacBook-Aroslav:~ yaroslav$ adb shell
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 5680MB 3371MB fat32 media msftres
13 5680MB 7597MB 1917MB ext2 linux
14 7597MB 7609MB 12.0MB linuxboot
(parted)
after doing all this you`ll get fully working deabian tabletop
installing is easy)
enjoy)
just for fun.

a little later i`ll make a detailed guide how to install this if you have stock kindle.
it'll be simple, so beginners colud follow my future guide and install debian and make dualboot for android and debian

a little later i`ll make a detailed guide how to install this if you have stock kindle.
it'll be simple, so beginners colud follow my future guide and install debian and make dualboot for android and debian
I will continue to fix bugs and add features and improve performance

Please feel free to ask any questions about this topic

Someone needs to try booting Chromium on it!
BTW, you still need OTG, correct?

Jessical said:
Someone needs to try booting Chromium on it!
BTW, you still need OTG, correct?
Click to expand...
Click to collapse
yes of course.
you still need OTG. but. but. i`m working on wifi and touchscreen. also i want not to use OTG with kbd and mouse.

He would be nice if you could make a video about how to install it
Sent from my Amazon Kindle Fire using XDA Premium HD app

jsisaev said:
what does you mean by p`n`p?
Click to expand...
Click to collapse
I can flash it, and it works ;')
Sent from my MB855 using xda premium

rbeavers said:
I can flash it, and it works ;')
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
you can flash this using dd or fastboot. i recommend you to reboot in recovery, place deb.img to sdcard and do the folowing: open a terminal. do adb shell (your kindle must be in recovery). then change current directory to /sdcard and enter this: dd if=deb.img of=/dev/block/mmcblk0p13

Do you need a keyboard or can you use the on-screen one?

FroyoShark said:
Do you need a keyboard or can you use the on-screen one?
Click to expand...
Click to collapse
i'm searching onscreen keyboard.
at once i got touchscreen working correctly.

I`ll upload new image tomorrow

After installing it on my Fire, I have a few questions, One: Do you have the mouse bugout fixed? Two: Am I going to have to download a big IMG again? And three: Can you make a DSL port after this one is perfected?
Also, Can you fix it to support OTG please?

Starzie said:
After installing it on my Fire, I have a few questions, One: Do you have the mouse bugout fixed? Two: Am I going to have to download a big IMG again? And three: Can you make a DSL port after this one is perfected?
Also, Can you fix it to support OTG please?
Click to expand...
Click to collapse
otg is supported.
at once you may not to download new image. just do the following:
in file /usr/shrare/X11/xorg.conf.d/10-evdev.conf replace last section with the following:
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Option "SwapAxes" "yes"
Option "InvertY" "yes"
#Option "InvertX" "no"
Option "Calibration" "0 3950 0 2370"
#Option "IgnoreRelativeAxes" "yes"
Driver "evdev"
EndSection
after that reboot.
all done. you now have correctly working touchscreen

WILDFIRE BUZZ: Mount permission denied

Hello,
Everything started with my intention of installing the supercharger v6 script. I found a post read how stuff should be, so i started doing it step by step until i hit a rock bottom. I couldnt install busybox. I downloaded busybox installer did everything the post said and nothing it just doesnt want to install so i just searched for alternatives. Found info about push command that forces a file into the system, okay but for that i need a RW system. Found info on how to make my system RW:
1) USB debugging on
2)i type adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and the PC says: PERMISSION DENIED
3) i try adb root and it says that i already got root access, adb remount then again the RW command, still says PERMISSION DENIED
I tryed from the Terminal Emulator and still the same effect... If someone is able i`ll be very pleased if he could help me All the best!

Are you s–off by revolutionary or xtc clip? Or is your hboot unlocked by HTC dev?
Sent from my GT-I9100 using Tapatalk 2

Scratch0805 said:
Are you s–off by revolutionary or xtc clip? Or is your hboot unlocked by HTC dev?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Yes my S-off is by revolutionary and i think i used HTC devices. :S

notorious1322 said:
Hello,
Everything started with my intention of installing the supercharger v6 script. I found a post read how stuff should be, so i started doing it step by step until i hit a rock bottom. I couldnt install busybox. I downloaded busybox installer did everything the post said and nothing it just doesnt want to install so i just searched for alternatives. Found info about push command that forces a file into the system, okay but for that i need a RW system. Found info on how to make my system RW:
1) USB debugging on
2)i type adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and the PC says: PERMISSION DENIED
3) i try adb root and it says that i already got root access, adb remount then again the RW command, still says PERMISSION DENIED
I tryed from the Terminal Emulator and still the same effect... If someone is able i`ll be very pleased if he could help me All the best!
Click to expand...
Click to collapse
After adb shell type
Su
This will give you root rights and stop the permission denied issue.
Sent from my Nexus 7 using xda premium

heavy_metal_man said:
After adb shell type
Su
This will give you root rights and stop the permission denied issue.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tryed that, still the same answer from the CMD. I cant upload a photo but i`ll write exactly what i do:
adb root
cmd:adbd is already running as root
adb shell
# su
su
# mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system
cmd: mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system: permission denied

notorious1322 said:
I tryed that, still the same answer from the CMD. I cant upload a photo but i`ll write exactly what i do:
adb root
cmd:adbd is already running as root
adb shell
# su
su
# mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system
cmd: mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system: permission denied
Click to expand...
Click to collapse
Hmmm. Do you have any apps like root explorer? You could try use that app to mount the system as rw and then try the command. Or you could use a root file explorer to copy over the files to where you need them to be
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

heavy_metal_man said:
Hmmm. Do you have any apps like root explorer? You could try use that app to mount the system as rw and then try the command. Or you could use a root file explorer to copy over the files to where you need them to be
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
How can i mount my system as rw via Root explorer?

notorious1322 said:
How can i mount my system as rw via Root explorer?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9100 using Tapatalk 2

P6 state clarify and develop and brainstorming(recovery, boot, fastboot, kitchen)

Hi!
As I promiss, here is the thread for clarify and brainstorming for Ascend P6 avaible development.
First of all, clarify the bootloader and phone status.
Our phone is an "emulator". It is not running Android natively. It's just emulated, Android is running in QEMU. Similar like the real Android SDK.
Huawei patched the QEMU for running Android our MTK chipset.
Huawei take a tricky step. He did the RSA5 encrypt to not able to write any files to the partition system, without a digital signature of Huawei.
Xloader check this signature and if it missing, you won't be able to update. (We are s*cking @ here...)
Bootloader Unlock
It means, you able to send boot image and recovery img via fastboot. I think, our fastboot haven't got some instructions and permission.
DON'T FORGET YOU ARE IN AN EMULATED STATE!!!
If Huawei "unlock the bootloader", 2 way to get this( I think):
1. Modified fastboot, to able flash boot image via fastboot like this:
Code:
fastboot flash boot boot.img/recovery.img
or
Code:
flash_image boot boot.img/recovery.img
2. Ignore the whole system signature check. (which is best for we and able to running native Android but it won't be happen)
1 is a big step forward to custom kernel/Custom rom/CM/AOSP.(Of course second is bigger)
I'm just praying first at this moment.
Partitions.
ONE REAL partition are in the MTK NAND chip. Called: hi_mci.1.
The other partitions are NOT REAL! They are emulated. Just like you running LINUX in Virtualbox or something like this.
Those partitions:
/sdcard vfat /dev/block/platform/hi_mci.1/by-name/sdcard
/system ext4 /dev/block/platform/hi_mci.1/by-name/system
/cache ext4 /dev/block/platform/hi_mci.1/by-name/cache
/data ext4 /dev/block/platform/hi_mci.1/by-name/userdata length=-16384
/misc emmc /dev/block/platform/hi_mci.1/by-name/misc
/boot emmc /dev/block/platform/hi_mci.1/by-name/boot
/recovery emmc /dev/block/platform/hi_mci.1/by-name/recovery
/cust ext4 /dev/block/platform/hi_mci.1/by-name/cust
/uboot emmc /dev/block/platform/hi_mci.1/by-name/uboot
/splash2 ext4 /dev/block/platform/hi_mci.1/by-name/splash2
/modem/modem_image ext4 /dev/block/platform/hi_mci.1/by-name/modemimage
/usb vfat /dev/block/sda
For native Android, we need to repartition the hole NAND chip. I think, it is impossible.
BOOT
Android boot system need boot.img for booting. Which contain the kernel and some system specific files.
This is formatting the device own emulated partition. It contains the ramdisks, etc.
We have an Huaewei Update Extractor, which can be unpack the update.app.
We get boot.img, recovery.img. Good.
Our bootloader is UNLOCKED from the begining. I think, our fastboot haven't got some instructions and permission.
With dsiXDA Kitchen you able to unpack boot and recovery.img, modify it and repack.
Just after the B118 update, I hope Huawei unlock this feature. It is a good point to start.
The new driver for ADB/fastboot
To be continued...
And feel free to contribute!
Take a test and build boot.img from b122. Two modification in:
1. ro.secure=0
2. ro.debuggable=1
Is this mean, you get true root acces to everywhere.
See in attachment.
Of course, it won't be able to to push via fastboot, because the limitations our fastboot.

Hi!
After new firmware B118, nothing will be changed , because secure lock loader was not removed !
You can not push boot.img by fastboot , but you can easy flashed a new kernel by this command :
# dd if=/sdcard/boot.img of=/dev/block/mmcblk0p12
Click to expand...
Click to collapse
and your device will never boot cause you need a signed image !
I was able to flash by this command only the stock kernel !
Good luck !

There appears to be a signed flashable CWM recovery.img with scatter file for the ascend mate over at needrom - I know the P6 is pretty much the same device save the screen size so maybe it can be of some use ?
(assuming it it genuine and works).
Needs an app called SP Flash Tool which is for MTK chipsets.
http://www.needrom.com/mobile/ascend-mate-mt1-u06-s4ui/

lonespeaker said:
There appears to be a signed flashable CWM recovery.img with scatter file for the ascend mate over at needrom - I know the P6 is pretty much the same device save the screen size so maybe it can be of some use ?
(assuming it it genuine and works).
Needs an app called SP Flash Tool which is for MTK chipsets.
http://www.needrom.com/mobile/ascend-mate-mt1-u06-s4ui/
Click to expand...
Click to collapse
Hi!
Yes, you are right , seem they managed to signed a recovery.img to be flashed on partition /recovery !
As long as the loader is locked ( This phone is secure lock state ! ) I do not think it helps us....

surdu_petru said:
Hi!
Yes, you are right , seem they managed to signed a recovery.img to be flashed on partition /recovery !
As long as the loader is locked ( This phone is secure lock state ! ) I do not think it helps us....
Click to expand...
Click to collapse
Yeah maybe you're right, but a bit odd releasing what appears to be an asop based rom with a signed recovery and signed boot.img rom and no way to actually install it. maybe one day...

surdu_petru
What do you think about not removing the hole security, just removing the boot image security. Loader not check the boot image signature. You able to run custom kernel. But not able to change recovery. Only for boot.img. And with this and your method(Blueandroid), we can get custom roms like AOSP. And every time we can go back to stock with our stock recovery.

bukest said:
surdu_petru
What do you think about not removing the hole security, just removing the boot image security. Loader not check the boot image signature. You able to run custom kernel. But not able to change recovery. Only for boot.img. And with this and your method(Blueandroid), we can get custom roms like AOSP. And every time we can go back to stock with our stock recovery.
Click to expand...
Click to collapse
Nop, loader also check boot image signature , because I can not flash a custom kernel ( boot.img ) !
Edit :
I think, I'm not 100% sure, xloader partition is check signature for all partitions on boot !

Who have courage to try this?
Finding some usefull info.
How should our device look like(NAND)
xloader => /dev/block/mmcblk0p1 /first stage bootloader
round => /dev/block/mmcblk0p2
nvme => /dev/block/mmcblk0p3
misc => /dev/block/mmcblk0p4
splash => /dev/block/mmcblk0p5
oeminfo => /dev/block/mmcblk0p6
reserved => /dev/block/mmcblk0p7 /It’s the Huawei digital signature of the boot partition, checked by the bootloader.
reserved2 => /dev/block/mmcblk0p8
splash2 => /dev/block/mmcblk0p9
recovery2 => /dev/block/mmcblk0p10
recovery => /dev/block/mmcblk0p11 /stock recovery
boot => /dev/block/mmcblk0p12 /kernel+ramdisk
modemimage => /dev/block/mmcblk0p13
modemnvm1 => /dev/block/mmcblk0p14
modemnvm2 => /dev/block/mmcblk0p15
system => /dev/block/mmcblk0p16
cache => /dev/block/mmcblk0p17
cust => /dev/block/mmcblk0p18
userdata => /dev/block/mmcblk0p19
mmcblk0boot0
This is the second stage bootloader. Huawei in his UPDATE.APP files call this partition as FASTBOOT!!!!
So, someone in this forum sad, B118 FASTBOOT.IMG is the different size. It's true! B118 FASTBOOT.IMG size is smaller then B122.
I think, we found the trick!
Huawei not unlock the Xloader(1st low-level loader), just unlock the second stage loader which will allow to flash and boot custom boot.img and recovery.img!
Who have any courage, to do this:
1. Place attached FASTBOOT.IMG to sdcard/
2. Connect phone in MTP
3. Enable USB Debug.
4. CMD on PC with administrator privileges
5. Navigate to the folder which contain adb.exe
6. type: ADB.exe shell
7. type su
8.
Code:
# dd if=/sdcard/fastboot.img of=/dev/block/mmcblk0boot0
with fastboot.img from extract from Chinese B118! File attached.
If am I right, after this we are able to use it on any version(unicom/mobile) and version of firmware(B111,B112,B119,B122, etc...)
If anything went wrong, you need to reflash the hole UPDATE.APP. So, I recommend to place update.app file to sdcard/dload/
Maybe if some of you think is real, I will do!

delete

bukest said:
So, someone in this forum sad, B118 FASTBOOT.IMG is the different size. It's true! B118 FASTBOOT.IMG size is smaller then B122.
I think, we found the trick!
Huawei not unlock the Xloader(1st low-level loader), just unlock the second stage loader which will allow to flash and boot custom boot.img and recovery.img!
Click to expand...
Click to collapse
You can not flash a custom kernel on B118 ! Take a look here !

surdu_petru said:
You can not flash a custom kernel on B118 ! Take a look here !
Click to expand...
Click to collapse
And what boot.img he had flashed?
What happend when boot.img needed to signed but not just Huawei. Bootloader allow every digital signed boot.img(public key or something like this)?
Not parse the signature with one stored in the OEMINFO or RESERVED. Just only need to contain a digital signature in the front of the file, which mean, you are little bit better than a hobby weekend engineer.

bukest said:
And what boot.img he had flashed?
What happend when boot.img needed to signed but not just Huawei. Bootloader allow every digital signed boot.img(public key or something like this)?
Not parse the signature with one stored in the OEMINFO or RESERVED. Just only need to contain a digital signature in the front of the file, which mean, you are little bit better than a hobby weekend engineer.
Click to expand...
Click to collapse
Do you already signed a custom kernel with a private key ( not from Huawei ofcourse ), and your device was able to boot ?

surdu_petru said:
Do you already signed a custom kernel with a private key ( not from Huawei ofcourse ), and your device was able to boot ?
Click to expand...
Click to collapse
NOT. If you read a few post back, you will see it's just an idea. But I want to walk around fully all around aspect and all possibility.
Another idea.
What about Huawei check you are on P6-U06 or P6-U00?
And with B118 fastboot.img only flashed if you are on U00. Think about this.
But what happend if we push it manually...

Someone on P6-U00(Originally)!
Extract the boot.img from B118. Make a small modification. Flashed via fastboot. And if it doesn't work, we are able to write down, Bootloader is not unlocked.
Edited:
Attached for this an edited boot.img for B118.
Of course, NOT signed! just unpack original, edit(default.prop) and repack.

Bad news!
Permission denied!
[email protected]:/ $ dd if=/sdcard/fastboot.img of=/dev/block/mmcblk0boot0
dd if=/sdcard/fastboot.img of=/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot0: cannot open for write: Permission denied
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bukest said:
Permission denied!
View attachment 2431245
Click to expand...
Click to collapse
In the way you use the command, this answer " Permission denied!" is 100% correct !
Please, use "#" instead "$" ! Good luck !

surdu_petru said:
In the way you use the command, this answer " Permission denied!" is 100% correct !
Please, use "#" instead "$" ! Good luck !
Click to expand...
Click to collapse
Ohhhh, stupid me...
Forgot to get su!
Thanks surdu.
But after a little research I find some other info with FASTBOOT partition. I will write down later at the day(have go to work at the moment).

WARNING!!!!
Do not use that method!!!
mmcblk0boot0 partition maybe contain some other information!!!
Unique FOR YOUR DEVICE!!!
Just like wifi MAC adress, etc!
And on a running system, partition around 2MB!
First backup your current boot0 partition!
# dd if=/dev/block/mmcblk0boot0 of=/sdcard/mmcblkboot0.img
It means, if we push the 500k image to 2mb partition directly, you may damage 1,5MB data.
I think, with update.app method, you just install the image file, not pushing directly!

IDEA
If we backup xloader partition:
# dd if=/dev/mmcblk0p1 of=/sdcard/xloader.img
Edit it in hex to remove digital signature check.
Push back and pray...
If it works, you have totally unlock phone, but if not YOUR PHONE TOTALLY DEAD!

hex-editing the xloader.img ...
I also like to live dangerously

"Couldn't mount SD card" rooting Nexus 7 (2013)

Hi,
I have been trying to root a Nexus 7, and I always end up having the problem that the recovery cannot mount the sdcard. I have wiped the entire device several times and tried installing different google stock images: marshmallow (6.0.1 MMB29O and MMB29Q) and lollipop (5.1.1 LMY48T). I tried installing Cyanogenmod, but couldn't install it without access to the sdcard from the recovery. I also tried different recovery methods.
This is the bootloader loading screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The stock recovery function failing to mount:
Team Win Recovery:
And ClockworkMod Recovery:
I also tried other versions of those recovery tools, but with the same result. I have no problem accessing the SD card from the Android OS, and accessing the device in USB mode was not a problem either.
It would be great if someone knew what the problem is. I have been searching, but couldn't find anything that helped.
Thanks for the help.

Aitor86 said:
I have no problem accessing the SD card from the Android OS
Click to expand...
Click to collapse
Android works fine but recovery does not? Unusual.
Please boot TWRP, run the following and post the log file:
Code:
adb shell blkid > data.txt
adb shell cat proc/partitions >> data.txt
adb shell head /sys/block/mmcblk0/device/* >> data.txt
adb shell dmesg >> data.txt
adb shell cat /tmp/recovery.log >> data.txt

k23m said:
Android works fine but recovery does not? Unusual.
Please boot TWRP, run the following and post the log file:
Code:
adb shell blkid > data.txt
adb shell cat proc/partitions >> data.txt
adb shell head /sys/block/mmcblk0/device/* >> data.txt
adb shell dmesg >> data.txt
adb shell cat /tmp/recovery.log >> data.txt
Click to expand...
Click to collapse
Hi, thanks for the help. This is the output of that code:
pastebin.com/fP5q3DPE

Aitor86 said:
Hi, thanks for the help. This is the output of that code: pastebin.com/fP5q3DPE
Click to expand...
Click to collapse
Hi mate, you wrote "I have no problem accessing the SD card from the Android OS" but the reality is "a few weeks ago I had no problem" - correct?
Your log:
Code:
mmc0: unrecognised EXT_CSD revision 7
mmc0: error -22 whilst initialising MMC card
Try the latest TWRP first, OK?

k23m said:
Hi mate, you wrote "I have no problem accessing the SD card from the Android OS" but the reality is "a few weeks ago I had no problem" - correct?
Your log:
Code:
mmc0: unrecognised EXT_CSD revision 7
mmc0: error -22 whilst initialising MMC card
Try the latest TWRP first, OK?
Click to expand...
Click to collapse
I have no idea what the problem was, but using the latest TWRP (3.0) did the trick. The sdcard is visible, and I can access any file I want from there.
Just to answer your question, the SD card was still accessible from the Android OS, so summing up, the only recovery tool that worked was the latest version of TWRP.
Thanks for the help!!!! I thought I was using the appropriate version, and I had spent more time than I would admit trying to get this working.

Hi
Sent from my iPhone using Tapatalk

Working viper4a with easy steps.

STEP 1: Root the phone with the link provided in the op7t forum.Now you have magisk.
STEP 2: Install the SE LINUX SWITCH APP link: https://labs.xda-developers.com/store/app/com.ibuprophen.selinux
STEP 3: change selinux to permissive. now to go settings-battery optimisation-change the selinux app to not optimised.turn off googleplay protect.
STEP 4:now all you need is a modded stock recovery. download it from here. link: https://drive.google.com/file/d/1S-1Np5CFx9z98Ntp8vUTWFU1ksqIeBSN/view
STEP 5:now go to fastboot and flash the stock modded recovery. CODE: fastboot flash recovery RECOVERYNAME.zip now you have adb enabled stock recovery.
STEP 6:now boot to stock recovery while connected to pc and type adb devices in cmd. it should go to adb. if yes proceed to next step.
STEP 7:now install viper4fx from magisk. phone will reboot. go into viper4a app and install drivers. it will go to fastboot ofcourse.
STEP 8: boot to recovery from fastboot. then just type in the following commands/
1. adb shell
2. cd data
3. cd adb
4. cd modules
5. cd ViPER4AndroidFX
6. rm post-fs-data.sh
7. exit
STEP 8: phone will now boot. again go to viper4a app and install drivers and repeat step 8 again.
VOILA now you have viper fully working on our beloved op7t.
NOTE: disable bluetooth absolute volume for bluetooth to work in v4a.
Dont try installing viper in 10.3.1. you will be stuck in fastboot. so instead download 10.3.0 fastboot image and flash it. then follow the above steps and update the phone by the following.
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot. Root, viper and all the magisk modules will be retained. Give a thumbsup

Anyone tried this?

VIZT said:
Anyone tried this?
Click to expand...
Click to collapse
perfectly working in mine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

why do i need always to set os to permissive?

Snake.s9 said:
why do i need always to set os to permissive?
Click to expand...
Click to collapse
Permissive sets SELinux to behave in a different way than Enforcing(default), which is required for V4A to work.
As far as technical details, I have no idea.

Permissive is dangerous.

Batfink33 said:
Permissive is dangerous.
Click to expand...
Click to collapse
Why ? Explain more please

Snake.s9 said:
Why ? Explain more please
Click to expand...
Click to collapse
Leaves the kernel open to any malicious apps that want to take control of your phone.

Snake.s9 said:
why do i need always to set os to permissive?
Click to expand...
Click to collapse
permissive mode allows some features to run on some instances which are not allowed in enforcing mode. like for example debugging.

Apparently its not meant for me to have viper. Modded recovery won't even work.

i tired it says no such file or directory on rm command
had to load app and install driver first

shorty1993 said:
Apparently its not meant for me to have viper. Modded recovery won't even work.
Click to expand...
Click to collapse
not working in the sense? not able to flash or adb isnt responding?

chwads2k8 said:
i tired it says no such file or directory on rm command
had to load app and install driver first
Click to expand...
Click to collapse
yes. postfs file will be generated only after installing the app. it is necessary to remove it for the phone to boot and for viper to work aswell.

I got to step five say
C:\adb>adb shell
error: device not found

AboNaya said:
I got to step five say
C:\adb>adb shell
error: device not found
Click to expand...
Click to collapse
Why would you type adb shell in fastboot?
Read the instructions again
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Why would you type adb shell in fastboot?
Read the instructions again
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
C:\Users\MY>adb shell
OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
Thank you very much for responding to me. I have taken the steps back to step 8 and the phone, of course, does not start the problem now, it is as follows What is the solution to overcoming this problem, please, I am a fan of this program and after moving to OnePlus SevenT I could not run it for more than ten to twenty attempts

AboNaya said:
C:\Users\MY>adb shell
OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
Thank you very much for responding to me. I have taken the steps back to step 8 and the phone, of course, does not start the problem now, it is as follows What is the solution to overcoming this problem, please, I am a fan of this program and after moving to OnePlus SevenT I could not run it for more than ten to twenty attempts
Click to expand...
Click to collapse
Ah.
After typing adb shell and your prompt shows:
OnePlus7T:/ $
type: su <press enter>
Prompt should now look like this:
OnePlus7T:/ #
Now you have root access and can cd into /data/adb/.

not working
adb shell
# cd data
cd data
# cd adb
cd adb
/system/bin/sh: cd: /data/adb: No such file or directory
what to do now?

grandpajiver said:
Ah.
After typing adb shell and your prompt shows:
OnePlus7T:/ $
type: su <press enter>
Prompt should now look like this:
OnePlus7T:/ #
Now you have root access and can cd into /data/adb/.
Click to expand...
Click to collapse
C:\adb>adb shell
# su
su
/system/bin/sh: su: inaccessible or not found
#

AboNaya said:
C:\adb>adb shell
# su
su
/system/bin/sh: su: inaccessible or not found
#
Click to expand...
Click to collapse
Don't type su, just adb shell and proceed
Sent from my OnePlus7TPro using XDA Labs