Related
Hi, I cant download or transfer apps to my sd card! people say that if i download astro it will fix but it didnt! So im looking for a way to fix it. can anyone help me
Sent from my MSM using the XDA mobile application powered by Tapatalk
x12CHRIS18x said:
Hi, I cant download or transfer apps to my sd card! people say that if i download astro it will fix but it didnt! So im looking for a way to fix it. can anyone help me
Sent from my MSM using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
If you're referring to USB Mass Storage in FRX07, then don't hold your breath.. unfortunately, it's a known issue.
maff1989 said:
If you're referring to USB Mass Storage in FRX07, then don't hold your breath.. unfortunately, it's a known issue.
Click to expand...
Click to collapse
It's unfortunately an issue with the loop'd mounts. If you create dedicated partitions for at the very least data - USB mass storage actually does work. hyc did some patching on this, not sure if that's in FRX07 or not. I haven't tried 07 on dedicated partitions yet.
Droid Explorer does a pretty damned good job of faking it tho...
arrrghhh said:
It's unfortunately an issue with the loop'd mounts. If you create dedicated partitions for at the very least data - USB mass storage actually does work. hyc did some patching on this, not sure if that's in FRX07 or not. I haven't tried 07 on dedicated partitions yet.
Droid Explorer does a pretty damned good job of faking it tho...
Click to expand...
Click to collapse
Ohhh I see thanks for the correction.
I noticed in the default rootfs.img for FRX07 that the init does in fact check for a dedicated data partition, although I'm not sure if it puts that partition to use as the data partition (that coding looked a little confusing :\). I assume it would otherwise it wouldn't make sense to check if there's no mount commands following...
It sounds intriguing, though.. May give the dedicated data partition a try; could help with performance, let alone fix USB MS
EDIT: Seems this idea has already been put into effect for FRX07... http://www.neopeek.com/viewtopic.php?f=14&t=7441
maff1989 said:
Ohhh I see thanks for the correction.
I noticed in the default rootfs.img for FRX07 that the init does in fact check for a dedicated data partition, although I'm not sure if it puts that partition to use as the data partition (that coding looked a little confusing :\). I assume it would otherwise it wouldn't make sense to check if there's no mount commands following...
It sounds intriguing, though.. May give the dedicated data partition a try; could help with performance, let alone fix USB MS
EDIT: Seems this idea has already been put into effect for FRX07... http://www.neopeek.com/viewtopic.php?f=14&t=7441
Click to expand...
Click to collapse
Indeed, but CWM of course uses different mount points than XDAndroid...
so XDA:
p1 - fat32
p2 - rootfs
p3 - system
p4 - data
CWM from Neopeek:
p1 - fat32
p2 - system
p3 - data
p4 - cache
So you can certainly setup dedicated partitions and use XDAndroid's rootfs. If you use CWM, just be wary, the layout is different. CWM is easier because it installs Android to these partitions for you - otherwise you have to move the data to the partitions yourself .
arrrghhh said:
CWM is easier because it installs Android to these partitions for you - otherwise you have to move the data to the partitions yourself .
Click to expand...
Click to collapse
By this, you mean copying, say, the rootfs.img to the second partition, or would the rootfs need to be extracted to the partition? I assume the latter..
maff1989 said:
By this, you mean copying, say, the rootfs.img to the second partition, or would the rootfs need to be extracted to the partition? I assume the latter..
Click to expand...
Click to collapse
Yes, the latter. Same with system.ext2 and data.img - these need to be expanded onto the dedicated partitions.
What I did was mount the system.ext2 file (looped) on my Ubuntu server. Mount a data.img (looped) as well. Then I stuck a mSD -> USB converter plug in the server, and formatted the card with fdisk assigning the partitions. Mounted those partitions in Ubuntu, then tar'd the data over (IIRC there's issues with cp, doesn't preserve permissions).
Code:
cd /dir1; tar cf - . | (cd /dir2; tar xf -)
is how I tar'd it.
arrrghhh said:
Yes, the latter. Same with system.ext2 and data.img - these need to be expanded onto the dedicated partitions.
What I did was mount the system.ext2 file (looped) on my Ubuntu server. Mount a data.img (looped) as well. Then I stuck a mSD -> USB converter plug in the server, and formatted the card with fdisk assigning the partitions. Mounted those partitions in Ubuntu, then tar'd the data over (IIRC there's issues with cp, doesn't preserve permissions).
Code:
cd /dir1; tar cf - . | (cd /dir2; tar xf -)
is how I tar'd it.
Click to expand...
Click to collapse
Oh wow... that's a bit different than I anticipated, although your information is very much appreciated the dir1 and dir2 refer to the mount points for the system.ext2 and data.img, respectfully, correct? And it's two commands in one, separated by the "|" correct?
Off-topic.. What's IIRC?
And also, I can comprehend that "tar'ing" files means copying them in some way, shape, or form, but how would that preserve permissions over simply cp'ing them from the mount point in Ubuntu to the partition on the SD card? Or perhaps even manually copying the files to the SD partition? Considering these actions are performed in Ubuntu, I would assume permissions wouldn't be altered :\
maff1989 said:
Oh wow... that's a bit different than I anticipated, although your information is very much appreciated the dir1 and dir2 refer to the mount points for the system.ext2 and data.img, respectfully, correct? And it's two commands in one, separated by the "|" correct?
Off-topic.. What's IIRC?
And also, I can comprehend that "tar'ing" files means copying them in some way, shape, or form, but how would that preserve permissions over simply cp'ing them from the mount point in Ubuntu to the partition on the SD card? Or perhaps even manually copying the files to the SD partition? Considering these actions are performed in Ubuntu, I would assume permissions wouldn't be altered :\
Click to expand...
Click to collapse
IIRC = if I recall correctly
Yes, that's all one command and dir1 is the system.ext2 mount or the data.img mount (the source), dir2 is the mount point on the card (destination).
I don't know why cp doesn't preserve permissions - there's probably some switch you can pass that will preserve perms. I'm not an expert here, I only know I had a boatload of issues when I just used cp... Talked to some experts, and they gave me that tar command - which worked perfectly.
Idk what you are talkin about! so is there way to fix this situation?!
x12CHRIS18x said:
Idk what you are talkin about! so is there way to fix this situation?!
Click to expand...
Click to collapse
You can fake USB mass storage with Droid Explorer. That's really the only option on looped mounts.
Where can I get droid explorer?
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
Where can I get droid explorer?
Sent from my Touch Pro II with Froyo
Click to expand...
Click to collapse
Here, let me Google that for you...
Haha thanks man! But I'm still having trouble.... I downloaded droid explorer then it told me that I have to download android sdk tool so I did and its still telling me that I have to download android sdk tools
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
Haha thanks man! But I'm still having trouble.... I downloaded droid explorer then it told me that I have to download android sdk tool so I did and its still telling me that I have to download android sdk tools
Click to expand...
Click to collapse
So... did you click the link to "do it for me" or whatever it says during install, or did you pick a manual install? You should just let the application do it for you, otherwise you have to download it yourself and then point it to whatever directory you installed it at... Oy.
I downloaded the zip file
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
I downloaded the zip file
Click to expand...
Click to collapse
Ok, would you like a cookie?
I still have a problem, droid explorer doesn't recognize my phone. i have my phone in debug mode
x12CHRIS18x said:
I still have a problem, droid explorer doesn't recognize my phone. i have my phone in debug mode
Click to expand...
Click to collapse
Did you get an 'XDA' device in device manager? Did you read the FAQ and install PDAnet if the drivers with Droid Explorer don't work?
yeah i got XDA but it wont let me install it, it keeps on saying "cant find device". Do I have to download PDAnet if i cant install it?
Hi,
I have a Nook Tablet in version 1.4.1 reset it back to 1.4.0, root it, tried to put cm9 in it...messed up royally, format a whole bunch of things that I shouldn't.
Now it's stuck in CWM v5.5.0.4
Tried just about everything, but can't get out. can't access adb, not very familiar with it anyway...but downloaded sdk, jkd, etc...but can't see device...tried recovery image also...doesn't work.
Is there any method aside from adb method? Is there an SD method...think I messed up the partitions or whatever...
tried this method:
http://forum.xda-developers.com/showthread.php?t=1555832
but doesn't work...
again can't see devices in adb...tried this & other methods...nothing..
http://forum.xda-developers.com/showthread.php?t=1363652
please help...
I actually have 2 Nook Tablets...one for my kids & another I'll give to a nun friend...1 is correctly rooted & has cm9...can I image one & flash it on another? If so, how?
Thank you & God bless
Have you tried making a bootable CM7 or CWM microSD card?
Solar.Plexus said:
Have you tried making a bootable CM7 or CWM microSD card?
Click to expand...
Click to collapse
I have a recovery.img...tried that didn't work
have boot.img tried that...CWM microSD
tried to flash SD_ROOT_NT16gbV4_6 onto microSD, but after that can't add anything else to it...the directions to partition microSD is somewhat confusing to me...don't quite know what to do or where to put boot file, etc...after I partitioned it...any advice is greatly appreciated...
"format a whole bunch of things that I shouldn't." BAD IDEA. Can you tell us what exactly you formatted?
Is always good to have adb working so you should troubleshoot it. In my FAQ there is a link for a how-to i made to install and use adb tool, run the runmefirst.bat from the package i provide is a must.
As an alternative (to non use of adb, etc tools) you can use Adam's total wipe (sdcard), which has been fixed by Adam to not affect serial ID's and MAC address from ROM partition.
~ Veronica
lavero.burgos said:
"format a whole bunch of things that I shouldn't." BAD IDEA. Can you tell us what exactly you formatted?
Is always good to have adb working so you should troubleshoot it. In my FAQ there is a link for a how-to i made to install and use adb tool, run the runmefirst.bat from the package i provide is a must.
As an alternative (to non use of adb, etc tools) you can use Adam's total wipe (sdcard), which has been fixed by Adam to not affect serial ID's and MAC address from ROM partition.
~ Veronica
Click to expand...
Click to collapse
I formatted....
bootdata, cache, data, emmc, rom, system, sd-ext....everything with the format in front of it...I did it...I know...not smart...
did the acclaim_update...doesn't work...CWM seems to be working...but just can't install acclaim_update or SD_ROOT_NT16gbV4_6...again can't access adb at all
What does it say when in CWM when you try to flash something?
thungrac221 said:
I formatted....
bootdata, cache, data, emmc, rom, system, sd-ext....everything with the format in front of it...I did it...I know...not smart...
did the acclaim_update...doesn't work...CWM seems to be working...but just can't install acclaim_update or SD_ROOT_NT16gbV4_6...again can't access adb at all
Click to expand...
Click to collapse
they won't work because you formatted most of your partitions, use Adam's total wipe as i said before or soshite unbrick method but for that one you need adb working.
~ Veronica
lavero.burgos said:
they won't work because you formatted most of your partitions, use Adam's total wipe as i said before or soshite unbrick method but for that one you need adb working.
~ Veronica
Click to expand...
Click to collapse
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
nevermind...found the link...will try...thanks again
thungrac221 said:
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
Click to expand...
Click to collapse
I use virtual box: https://www.virtualbox.org/wiki/Downloads
If he has cwm he has adb.
Just guide him to install correct drivers for it.
Solar.Plexus said:
What does it say when in CWM when you try to flash something?
Click to expand...
Click to collapse
tried to install recover.img, but Error mounting /sdcard..tried mounting, but can't
thungrac221 said:
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
nevermind...found the link...will try...thanks again
Click to expand...
Click to collapse
Well, I download the adam's image for windows, but in CWM cannot mount sd card...oddly, when I plug it into my computer, it sees the nook but cannot start adb...tried methods to recognize usb, but can't...
please advise....thank you
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Make a new recovery card from the instruction. Forget your old recovery card.
Install these two,
flash-restore-stock.zip (use it to restore partition 1-6)
flash_stock_1.4.2.zip (use it to restore to stock 1.4.2)
Then install whatever rom you want after.
succulent said:
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Make a new recovery card from the instruction. Forget your old recovery card.
Install these two,
flash-restore-stock.zip (use it to restore partition 1-6)
flash_stock_1.4.2.zip (use it to restore to stock 1.4.2)
Then install whatever rom you want after.
Click to expand...
Click to collapse
Thank you, thank you...used only this flash-restore-stock.zip & was able to find my way back... thanks a lot...my friend who is a nun will enjoy this when she goes to Ghana on her mission...she wanted this instead of carrying loads of spiritual books...thanks again... & God bless
I second that succulent with your post I was able to find my way back after flash-restore-stock.zip. My issue was Nook kept on booting CWM. Now I have to figure out how to boot CWM via USB again to flash stock rom. For now it takes me up to B&N member setup page, but only shows error when I enter info
Okay I wiped my internal emmc, so there is no OS. When I turn it on I get B&N stock setup menu. Than after account sign in it gives me error message with device info.
I can boot on SD CWM, but when I try to flash any zip it aborts and also I can't seem to find the right CWM SD that leaves me enough room to copy the OS.zip on the SD.
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
- I tried press Power and N button or 8 times fail reboots but it still boot into recovery
- I tried flash new ROM from sd card, and the status is shown Installing Update.... and then it shown Install from sd card completed!!! There was no any notification more (as usual). And after "completed" by this way, reboot and still went into recovery mode again
- I also tried flash new cwm version 6.0.x, wipe data, format system, data,.... and flash ROM again from sdcard but still didnt work.
- I also tried reset to factory default http://forum.xda-developers.com/showthread.php?t=1663836 but it still boot into CWM again and again.
- and follow many topics on google search but still no luck
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
I want to flash a new ROM, a fresh tablet to make a gift for my dad on father's day, but it is brick :crying::crying::crying:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
DavDoc said:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
Click to expand...
Click to collapse
I have adb set up, but it doesn't recognize my NT , it always boot to recovery mode
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
DavDoc said:
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
Click to expand...
Click to collapse
Hello DavDic,
Thank you for your help,
I follow your link and I success to boot from SD card, and CWM version is 5.0.5, then I success install the update.zip too, unfortunately after removing the sd card and reboot, it still boot to CWM version 6.0.2.9 - this is the version that I flash from ROM Manager before my NT is bricked (I flashed wrong device when I choose Nook Color in Rom Manager)
So I try to reboot again from sdcard, cwm version 5.0.5, then flash new CM10.1 ROM, and reboot and still go to CWM 6.0.2.9
and again, I boot from sdcard, cwm version 5.0.5, flash to new cwm version 6.0.2.9, flash new ROM and still boot to CWM screen
So, I can create and boot from a Sdcard, But can not boot to OS, always go to cwm 6.0.2.9 screen (that I think the wrong file since I flash from Nook Color file ). Thank you!
h a l t said:
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
...
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
...
Click to expand...
Click to collapse
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
digixmax said:
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
Thank you, I did but no luck still boot to recovery mode
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
DavDoc said:
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
Click to expand...
Click to collapse
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
h a l t said:
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
Click to expand...
Click to collapse
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
DavDoc said:
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
Click to expand...
Click to collapse
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
h a l t said:
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
Click to expand...
Click to collapse
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
DavDoc said:
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
Click to expand...
Click to collapse
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
h a l t said:
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
Click to expand...
Click to collapse
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
F5, F5, ..... I see the light at the end of the tunnel,... God, what is the adb, shell command to help me escape this trouble :angel::angel:
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
These two files are in the /bootdata partition (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for a list of the NT partitions and their content).
But if OP's flashing Succulent's flashable_fix_bootloop.zip (which basically re-install a fresh copy of these two files) didn't fix the problem then he might have wiped out some other critical components of the system.
I follow Adam's guide, unbrick my NT, and then flash new CM10.1 ROM perfectly.
Thank you again DavDoc and digixmax for helping me so much! :good:
Glad you got it working again
Sent with my Dinc4G
Disclaimers :
#i am no-developer.im just a geek xperian..like many of u.i have created this ,my first ever thread typing on my mob keypad.so forgive me for short words and untidy post.
#links included below is noway related to me.respective links are included as per my findings to support the main moto of this thread.im thankfull to all of them who have tried to scratch on this through their posts and threads
#with all do respect,this thread is intended for our devs who can take this as pre-requsites for development.
#its a humble request for devs to put there effort on this.
#i request all xperians...from devs to simple users...whoever thinks this post worth discussing/developing,ur valueable words on this are highly appreciated.
#and please no trollers
Click to expand...
Click to collapse
I was doodling around today,i got my eyes poped-up wen i encounterd this
[samsung kernel flashing from cwm zip] -> http://forum.xda-developers.com/showthread.php?t=1301756 and this
[samsung general cwm kernel updater] ->http://forum.xda-developers.com/showthread.php?t=2132208
It all began then when i had to be far from my pc.then flashing new kernls for new custom roms began to be a problem.i presume their are a lot of users like me who cant access pc with as ease as many can.or simply to them who dont want to connect to pc just to flash kernels.if this would be success,just imagine how ease it would be?
But before starting to dream lets put together what i have come across till now.
Then i started digging more...on google & found this Tutorial [many devs might be intrestd &could help xperia users& start to run xperiment in our xperia ] --> http://www.modaco.com/topic/360180-howto-build-and-update-kernel-using-cwm/
In my findings i did aknowledge that this matter has/have/had been left out in corner just for some taboos/nerms like our xperia doesnt ship with normal recovery partition or like our custm recovry doesnt support some disk formats.
But whatsoever, i was little arosed by above things....then came a point whereafter i was too excited,wen i found this in our very xperia forum,xperia p forum ->> http://forum.xda-developers.com/showthread.php?t=2409021
Here the dev has created a zip with updatr script writng the kernel image,which stays inside the boot.img file .i couldnt dig more on this zip,as it was not so popular thread.i dont even know for it works or not,all i know is there are devs wanting to build,which is the main moto of this thread to let devs rethink the possibilty.
And yes, its a convincing reason for acceptance that our xperia doesnt have recovry partition like as other vendors device..and what we get as a recovry is hard coded to ramdisk.but like as ,A xperia s user,i too want to question an enlightning point on this...like using recovry fota partition,wich gets blokd and remains unusable aftr bootloader unlockd....why not use that...if not what about repartitioning empty space in device for recovry usage partition... http://forum.xda-developers.com/showthread.php?t=2163643
i too presume, even though we dont have that heavy intrnl space,but i guess we have enough for just a recovry partition.i guess so.correct me.
FOTA partition :
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Kernel changes : extract_elf_ramdisk setup in kernel
if some body wants a detailed info it can be found here (( **thanks to @officiallysonyrebel ,for the supportive conversation.above words are his ** )) -- http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
*** Summing up in total ***
It may b a horizon-touching dream..but as a geek user, like me,we dream of it.
Our charming devs can unlock bootloaders/root/giv us custm roms/give us a taste with unimaginable upgrowing ever, android version updates in roms/ ports.these all would also be impossible without their immense hardwork/researchs/xperimnts...i do aknowledge its a lot to ask for this.but with all do respect i wish devs get ther hands on it.
I predict most of xda-ians might already know abt all this,if yes do enlighten us more...ur comments and findings are most needed thing currently.
but truely saying i really dream of using cwm @ its maximum capacity,as of its easeness,isnt it? Different vendors like samsung,zte,etc evn can get rooted simply from cwm only...even most htc can. So why cant our xperia?is it coz of less devs in our xperia?i humbly request all devs to put some work on this so that me,like users who cant access pc with ease/dont want to,can easily get the work done.i also presume there r a lot of xperians,who want this.it cant be more handy than this...can it?
Hope in near future ,we xperians could getwith like these features as others.(rootng/flashng kernels from cwm).
Cheers!!
Xperia-lover!!
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
officiallysonyrebel said:
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
Click to expand...
Click to collapse
Ya i had read in the link u dirctd...i got to know that aftr unlockng bootloadr, that partition becomes unusuable/inaccessble.if that could be attained...then we can hope...isnt it?if i undrstud... wish devs could wave their magicstick soon.
Sent from my Xperia Ray using xda premium
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Nope...You are still using the same kernel....just booting from different ramdisk when "installed in /system"...
We need to boot from a "second" kernel which can be used to flash the primary kernel ...Most other phone can boot into two kernels ,one stock and one recovery ,hence they can be used to flash kernels via recovery and use flash_image to install recovery in system ...
The problem is not where kernel/recovery is installed
The problem is how to boot the secondary kernel after installation ...It's very difficult to do that ...
lets say I dd the recovery.img to /mmcblk0p4 which is the fourth partition in an SD card
How do I instruct the bootloader to boot the device from /mmcblk0p4(or fota 1 or whatever) instead of /boot ...Thats the problem ...
Okay that's sad
But what about checking the partitions and if we know which blocks contain the Fota partition, could we try to mount it?
The problem would be how to tell the bootloader to boot the recovery or the 2nd kernel right?
Sent from my Nexus 4 running Android 4.3
Still the same problem ,how to instruct the bootloader to boot from fota 1 instead of /boot !!
Check that. It's exactly the same what we want to do, right?
Okay not exactly but we could use that too. But I'm not sure if he is able to install another kernel in the recovery...
Sent from my Nexus 4 running Android 4.3
mihahn said:
Check that. It's exactly the same what we want to do, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
karandpr said:
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
Click to expand...
Click to collapse
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
mihahn said:
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
karandpr said:
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
Click to expand...
Click to collapse
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
mihahn said:
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
karandpr said:
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
Click to expand...
Click to collapse
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
mihahn said:
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
karandpr said:
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
Click to expand...
Click to collapse
Yes the HTC HD2 has great development support and I already worked with a HD2 of a friend, but I have actually no idea how to use the method they are using for the HD2 for our devices. I think I will dive into it when I'm back at home from my vacation trip
Sent from my Nexus 4 running Android 4.3
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
officiallysonyrebel said:
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
Click to expand...
Click to collapse
Ehh...no it won't work ...the S1boot boots only from /boot...
The thread you cited is too old and worked probably due to an exploit in nook color ...
I think something like LK should work ,provided it waits for sd card to mount...
officiallysonyrebel said:
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
Click to expand...
Click to collapse
Correct me if i m wrong.its a noobish thought.
Can we access fota partition before bootloader is unlocked?if we can so what r we waiting for?
lets rehearse for the magick show,do what u have thought of.
(I presume when device is still locked....or if we revert back to locked state from unlocked... we could acces that partition.. .we get space for secondry kernel...if still quesn is letting bootloader know we want to boot from that,then again we r far behind)
Sent from my Xperia Ray using xda premium
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.