Hi all as you have read Jack is trying to make a recovery backup of a 1.6 rom i have found a way that Jack can get this but i need a users who still has a 1.6 rom rooted with terminal emulator installed and to use these commands
info:
Your phone has several devices which hold different parts of the filesystem:
#cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
the commands i need you to run are these
Commands:
Code:
su
cat /dev/mtd/mtd0 > /sdcard/backup1.6/boot.img
cat /dev/mtd/mtd4 > /sdcard/backup1.6/system.img
cd /sdcard/backup1.6/
md5sum *img > nandroid.md5
running these commands will give use a fully flashable 1.6 backup so please users if you are running 1.6 then please run the commnds and upload the rom.
only problem is that nobody is on 1.6 anymore
hmm, still it is COOL project. Are you sure it is going to work? I mean why can not we just flash v1.x KDZ file (that should bring us 1.6 back, but LG says do not do this cause you will break phone).
so... if KDZ method doesn't work are you sure that recovery will work
yes recovery will work just think people have 2.3 and can still flash back to 2.1 or 2.2
Sent from my GT540 using XDA Premium App
max1919 said:
only problem is that nobody is on 1.6 anymore
hmm, still it is COOL project. Are you sure it is going to work? I mean why can not we just flash v1.x KDZ file (that should bring us 1.6 back, but LG says do not do this cause you will break phone).
so... if KDZ method doesn't work are you sure that recovery will work
Click to expand...
Click to collapse
You cant downgrade using KDZ as the bootloader wont downgrade, but our method should work when we get it sorted.
Jack
GOOD NEWS:
I'd sent my phone back to LG people coz my phone was totally bricked!! So they said that they'll replace my phone's motherboard with a new one. Currently my phone's still with the LG people and they're waiting for the new motherboard. The new motherboard will be having 1.6 pre-installed. Once I get it, I'll upload it soon.
But it seems that the LG people are quite lazy, and it may take another week to get my phone.
Cheers!
one step closer i have the 1.6 system.img just need to get a 1.6 boot.img
i have also edited the fitst post for are filesystem partitions
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
one step closer i have the 1.6 system.img just need to get a 1.6 boot.img
i have also edited the fitst post for are filesystem partitions
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
Why don't you try to extract the 1.6 ROM's KDZ file? Here's a thread that might help you: http://forum.xda-developers.com/showthread.php?t=899580 . I would gladly try it myself, if my Internet wasn't too slow (~0.2MB/s).
that what me and jack have been using im am going to have an optimus tonight running 1.6 so ill root that and get a proper flash files
Sent from my GT540 using XDA Premium App
in a few hours i should have update.zip made for the CPW 1.6 rom so look out for the title changing from [REF] to [ROM] also from what i can remember the boot.img should work with different 1.6 roms
Yay
Thank you so much, I've always wanted 1.6 for no reason what so ever
haha its always good for warrenty repairs if needed lol
Sent from my GT540 using XDA Premium App
airbus360 said:
Thank you so much, I've always wanted 1.6 for no reason what so ever
Click to expand...
Click to collapse
You're taking the piss, I only wanted to do this as a fun project because I wanted to, so if you have something bad to say, don't say it at all. Arse.
Jack
haha i dont even no if it will work im still trying lol
Im being serious
I was getting bored of android 2.x so I wanted to try 1.6 again
airbus360 said:
I was getting bored of android 2.x so I wanted to try 1.6 again
Click to expand...
Click to collapse
Oh sorry, I thought you were taking the piss lmao XD Sorry about that, slap me please
Jack
just tried the backup and it get stuck at the lg logo but i shall keep trying
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
just tried the backup and it get stuck at the lg logo but i shall keep trying
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
Try with fastboot, maybe you have to erase the total boot and system, and flash it after that.
Joost
thats the way i was trying to and i also tryied recovery
Sent from my GT540 using XDA Premium App
@Jack have you any other ideas to get 1.6 again
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=GT540
Cheers =)
Related
Hello all. Jdfroyo is a free community based distro of HTC Sense ROMs for the Droid Incredible. My Main goal was to bring the community a fast, yet very polished rom based off HTC Leaks and official releases for the EVO and Incredible.
This ROM is based off of the Official OTA for the Inc. It is deodexed, zipaligned, and all bloat is removed, yet the rom still features the very handsome Sense-UI interface by HTC.
Sense Version includes:
1. Deodexed
2. Zialigned
3. Most bloat removed
4. VERY FAST!!!!!
5. Can be stably overclocked to 1.2 ghz !!!!
6. Can be used with HYdra or KING Kernels.
Bloat Removed:
Mode 10 and Magic smoke livewallpaper
VZNav
Footprints
MyVerizon
Footprints Widget
VisualVoicemail
Amazon MP3
Vanilla Version:
All Sense Bloat removed- including weather, clockwidget, and Rosie!
Themed vanilla
General Changelog:
9/7 update- added buildprop edit so wifi scans every 2 mins, removed oj wake
RC3- fixed boot.img problem and temed vanilla ROM
v2.5- inital revival of jdfroyo
Link: Downloads - MOD Edit: Links Removed
FAQ:
Q. Why should I flash your ROM? There are others just as good.
A. The jdfroyo project aims to provide a very customized rom that most usere will like. It is stble, fast and not buggy.
Q. You had some boot.img bugs in previous bugs. Is that dangerous?
A. The boot.img contains the kernel and ramdisc, so the boot.img bug did cause severe overheating, and couldnt mount emmc, but that bug was cleared up in RC3, so no worries (actuaslly i replaced the whole boot.img)
Q. Does this give me root?
A. If you flash a coustom recovery after flashing the RUU (and have S_off) Then it gives you SU perms again, but not for anyone who wasnt previously rooted before.
Q. Are there any specific risks in flashing this
A. THere are potential risks in flashing ANY rom (even the ruu). This rom was tested and proven that it is ok for day to day use and will not brick.
Q. What is this based off?
A. The newer versions (2.5 and up) are based on the offical 2.2 release, and versions before v2.5 is based on the old 7/27 leak.
Q. Why dont you have screen shots up? We have only been asking you for weeks.
A. I am putting up some screens tonight. They will be here and on my site.
Q. What is your site?
A. check my sig (and no i am not trying to website spam)
Q. What is required before flashing this ROM?
A. S_OFF, custom recovery (Clockwork or AMON_RA) the 2.15 radio and 92hboot.
Q. Where can i find the things you mentioned in the previous answer?
A. 1.SOFF: www.unrevoked.com/forever
2. Closkwork or Amon ra: Clockwork can be found on unrevoked.com/forever , Amon can be found floating around on XDA
3. 92 hboot and 2.15 radio: can be found on adrynalyne's site
PLEASE eNJOY MY ROM!!!!!!!!!!!!!!!!!!!!!!
Isn't this the same thing as before?
Sent from my HTC Incredible
no it has various fixes, mostly the wifi fix....and for the sense version, i ixed the buildprop whaer ot said jdfroyo vanilla....it is very different from the version that i posted here last eek, but if you followed me on AF, then this is a bit similar
I thought you said you were done developing for the incredible.
I mean, I couldn't care less... just wondering why you decided to come back after two times of saying it.
And stable at 1.2.... hmm. I'd like this to be tested by others before I try this.
Hehe
Sent from my ADR6300 using XDA App
Lcsglvr said:
I thought you said you were done developing for the incredible.
I mean, I couldn't care less... just wondering why you decided to come back after two times of saying it.
And stable at 1.2.... hmm. I'd like this to be tested by others. Hehe
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Its hard to stay away
Link isn't working.
try it now
I don't think anybody likes you
Sent from my ADR6300 using XDA App
theguitarguy58 said:
I don't think anybody likes you
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
its not about liking me, its about liking my rom
jdkoreclipse said:
its not about liking me, its about liking my rom
Click to expand...
Click to collapse
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Touche...let's get back in topic
theguitarguy58 said:
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Is it just me, or do you always come out with a new version of *cough* a rom with almost the same name and number as skyraider. I guess it's like"the distinguished gentleman", if you have a familiar name, people will vote. At least make some attempt to be different so no one accidentally downloads this crap. How about POS ROM VERSION, oh hell, does it really matter?
And you use the same bull**** op almost every time. "Sorry no screens or info, just check my website, but I'm not spamming my website, and if it doesn't work, use other peoples fixes who I'll give no credit to ever never, but my rom is prefect and full of awesome." Give it a rest bud.
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Berzerker7 said:
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Click to expand...
Click to collapse
He's gotta be a relative or something right?
Berzerker7 said:
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Click to expand...
Click to collapse
screenshots are in the first post!!!!!!!!!111
theguitarguy58 said:
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I don't know the story since I just joined a few weeks ago but that made me laugh, thanks ! great wit sir!
Sent from my ADR6300 using XDA App
jdkoreclipse said:
screenshots are in the first post!!!!!!!!!111
Click to expand...
Click to collapse
I have to tell skyraider that my pinch to zoom isn't working with his rom, cuz those screens must be hella small.
Rather than continuing to have to discuss what is obvious to us all, let's try the objective approach with this. I downloaded jdfroyo Sense (for comedic value, honestly) and opened up the updater-script.
Going through this in sequence (I did not change the ordering):
So far so good.
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
Deleting files on a freshly formatted filesystem. What's supposed to be there?
Code:
delete_recursive("/system/etc/init.d");
delete("/system/xbin/a2sd");
delete("/system/xbin/apps2sd");
delete("/system/xbin/e2fsck");
Data isn't mounted, but delete operations are running, on /data.
Code:
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache/");
delete_recursive("/data/a2sd/");
delete("/data/.dalvikcache");
delete("/data/dta2sd.log");
Runs a script against /data, which still isn't mounted. Then extracts the contents of his zip to it. Into the void.
Code:
run_program("check_data_app");
package_extract_dir("data", "/data");
set_perm(0, 0, 0777, "/data/dalvik-cache");
Deleting more files on a newly formatted volume.
Code:
delete("/system/xbin/busybox");
delete_recursive("/system/xbin");
Oh, now we'll put some files on system. Since we've formatted it and deleted files which weren't there.
Code:
package_extract_dir("system", "/system");
I could go on but I think the point is clear. He's either not reading his updater-script, doesn't understand any of it or both. I'm going with both. So yeah, download at your own risk.
Still using evo framework?
Hey does anyone know what the artifact is in the middle of the 3rd screenshot?
*This is my first ever ROM port, so expect not much working*
*I take no responsibility for anything that you do to your phone or what happens to it*
FrostMod GingerSense v1a
This is the first version of what is going to hopefully get more and more working and functional with time.
Working: Not much. Post in comments what's not/what is for you.
This right now is a pretty bare OP, but hopefully with continued development, will grow with time.
NAND Backup before flashing, it's always safe!
Download: http://www.megaupload.com/?d=2TLM7ZMA
(MD5) fd6e8b7b613ed07225e601397944ee7a
Ported from the Desire HD leaked Android 2.3.2 Gingerbread leak found here: http://forum.xda-developers.com/showthread.php?t=983847
Changelog:
v1a: Initial Release
reserved.......
another just in case........
downloading now
Just had to change my pants
Sent from my ADR6300 using XDA App
With not much working. Does that include basic phone functions? Eg. The radio. Calling, sms?
Sent from my ADR6300 using XDA App
Just tried flashing with cwm2 & cwm3.
got installation aborted each time.
Sent from my ADR6300 using XDA App
What cwm is required? Ill give it a shot to see what is working, just sittin in front of tv watchin golf anyways.
Sent from my Incredible using XDA App
theguitarguy58 said:
Just tried flashing with cwm2 & cwm3.
got installation aborted each time.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Same here. Used 2.5.1.2 and 3.0.0.8.
This will not install at all
I may not be a developer but I think I may have an idea on what's going wrong:
1. I think that there's too much being put into the System partition. Correct me if I'm wrong but you're only given so much.
2. I think that the ROM is packaged wrong. When I open up the ROM in 7zip, I don't see the system and boot.img file first, I see a subfolder and THEN the system and boot.img.
Again, I just wanted to give a heads up, I'm in no way educated in this stuff. I'm just reporting as I sees 'em.
Was just gonna say that the structure was jacked. The ROM does seem large as well
kschwarz88 said:
I may not be a developer but I think I may have an idea on what's going wrong:
1. I think that there's too much being put into the System partition. Correct me if I'm wrong but you're only given so much.
2. I think that the ROM is packaged wrong. When I open up the ROM in 7zip, I don't see the system and boot.img file first, I see a subfolder and THEN the system and boot.img.
Again, I just wanted to give a heads up, I'm in no way educated in this stuff. I'm just reporting as I sees 'em.
Click to expand...
Click to collapse
You're right, I was in a hurry and packaged it wrong. Thanks for pointing this out. Will rezip and upload when I get home.
Sent from my Incredible using XDA App
For what it's worth, I repackaged the ZIP myself and am installing it at the moment. It requires CM 2.x (I'm using the temporary flashable 2.5.1.2 that was floating around to bypass my already-installed 3.x series).
I think I did it right, but here's the error I get:
E:Can't symlink /system/xbin/su
E:Failure at line 81:
symlink /system/bin/su SYSTEM:xbin/su
Installation aborted.
donnyp1 said:
What cwm is required? Ill give it a shot to see what is working, just sittin in front of tv watchin golf anyways.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
At the moment, CWM2.
It is not going to install until the system folder in below 250mb or so.
The OP has it at 350mb.
There is no way the OP even knows whether it even works because it will not install like this.
Thanks for the link in the first post. I'm trying a quick test build that I ported. I'll know if this DHD version is any easier to port in a few mins.
Tough to gain confidence if this is how thread starts. Good luck.
ANything yet?
UPDATE: 2 Cyanogen developers have picked up the Incredible S and it is being officially supported!! The ROM is in Beta and will be released when ready.
Remeber, the first rule of cyanogen: Don't ask for deadlines!!
Click to expand...
Click to collapse
Previous version of this post, kept for historical reasons:
Code:
I am sure everyone here wants to see CM7 hit this device. I am also sure that in our collective efforts, we can do it. At the moment, it is just me (or no one else is saying they are trying ;)) I basically want to try and get a team of people to crack the porting problem, because so far I am unable to do it on my own.
Finding information is proving difficult, and I just keep hitting dead ends. Is anyone willing to help? Has anyone ported a ROM from one device to another before? Can anyone point me towards information on how to start / debug?
As a community, this will get done a lot quicker, so if anyone can help please post here. If you idea of helping is posting "[I]I can help, what can I do / tell me what to do /give me something to do[/I]" then thanks, but no thanks.
[SIZE=3][B]Please keep this thread clear of chatter so it can be used for discussing the problem at hand.[/B][/SIZE]
I have ported from the HTC Dream to the HTC Diamond ...
If you wish to get started the way i do it ... Take a cm build from the closest device ... Say the DHD ... And chuck the system.img into an official update zip or any other zip with a working boot.img etc ... Then try booting directly ... If it bootloops ... The first thing you should try is to replace /lib from a stock rom ...
This will get you to boot surely ... But if you manage to boot directly then keep the libs ... After that we need the appropriate libs extra things like the secondary cam that u can take from the stock rom ...
A more detailed way to do it would be to get the ported libs working by using logcat to see whats wrong and replace only the related libs from a stock rom ... Keeping stock libs will make performace related things such as battery in the same state as stock ... So it is best to keep the ported libs ...
I would have done this myself by now but i have a s-on devoce :-/
Anyway can you tell me whats wrong with your attempts? Where do you get stuck? Which device are u trying to port from?
EDIT: idon see why you hit dead ends if u port from a similar device it should be no problem to boot ... Heck ports from the dream to the bloody winmo diamond worked out of the box ... The dream libs worked fine ... Would be nice if u could chuck us a logcat ... Even if i cant figure it out ill ask neopeek ...hes a pro but idon think this will go that far
Sent from my HTC Incredible S using XDA App
I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25
I will try what you said, it's a good starting point, thanks!
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...
Hehe ... Good point ... U cant get a bootloop if u dont even start boot ... I admit ... U sure have a funky way of trying things out ...
EDIT: that logcat ... Did u get it with what i said or what u tried?
Sent from my HTC Incredible S using XDA App
Both gave me that result. Can't really find out what it means other than it couldn't mount the system partition, no idea why
Sent from my HTC Incredible S using Tapatalk
I think the problem comes earlier ... Look at what you have said ... That failed to format part ... I think it screwed up halfway and now its empty ... Have you compared the update script with the one from the dhd? You are porting from the dhd right? Its the best option ...
Sent from my HTC Incredible S using XDA App
I use the same script I use for lpremix so I know the script is fine. Which is why I am stuck.
Sent from my HTC Incredible S using Tapatalk
Hmmm ... We need to narrow this down ... Try copiying in only /app /framework /media ... And also try using the older setup with the stock build.prop ... If u can boot this then the problem is in the rest ...
EDIT: did u also try different update scripts? Try using the dhd one as it is ... I think the problem is there might be a difference in the way the IS is partitioned compared to the dhd ... Cuz idon think we really have a mmc's upto 25
Sent from my HTC Incredible S using XDA App
Have you tried converting the Ace updater script to update script then changing the mount partitions to say from:
Code:
format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p27");
format("ext3", "EMMC", "/dev/block/mmcblk0p22");
to
Code:
format SYSTEM:
format CACHE:
format BOOT:
Then convert back?
K bro i think ive got some thing ... In /system/etc there is a file called vold.fstab ... Please do a comparison ... There might be a difference there ... Check the cm one with stock ... Also compare the cm7 update script from ace and the update script from a lp remix ... Maybe you just need to change the partition name ... Also try removing those lines completely from the script you are using ... Chuck all the lines related to format...
EDIT: its getting a little late ... Its around 330 am now ... I think ill go to sleep ... Ill see if i can think up of anything else for u bro ... Gnite every1 -_-
Sent from my HTC Incredible S using XDA App
looks like u have the same prob as me bro
l0st.prophet said:
I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25...
Click to expand...
Click to collapse
As far as i know Desire HD is ext3 and IS/DS are ext4.
Try to change the partition information.
See my previous post.
l0st.prophet said:
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...
Click to expand...
Click to collapse
Also here in your script you have a reference to /system/bin/sh which is probably missing from your rom.
hmm didnt even read that, but yes it shud be 4 o.0 or is that why my script is fkin me up?
imma test 3 anyway...
Im back from bed ... Maybe marylandcookie is right ... But where can that problem be? He is using the lpremix update script that usually works not the dhd script ... So why is it trying to chuck up ext3? Are u sure we are ext4?
@marylandcookie: do you have a nickname ... Ur name is real handfull to type out -_-
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Sent from my HTC Incredible S using XDA App
Ext3 works fine, but I will try ext4 anyway. It's us more likely to be a problem in the system files so I will check void.fstab file
The sh file is there, the system partition just isn't mounts properly
Sent from my HTC Incredible S using Tapatalk
it's too diffcult for me...but i believe we can
knightrocker said:
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Click to expand...
Click to collapse
I'm not sure what you mean, I suggest you look at the partition table. It's differant from mtd blocks cause its nand, system is definately mmcblk025
Sent from my HTC Incredible S using Tapatalk
Really? Still not used to this whole nand partition thing
Much better with android itself have made any progress?
Sent from my HTC Incredible S using XDA App
I won't today or until Tuesday as I am on holiday and away from a pc, but I will get back to it next week
Sent from my HTC Incredible S using Tapatalk
Ok then ... Ill see if i can think of something by then ...
Sent from my HTC Incredible S using XDA App
Hello everybody!
Yesterday I was thinking about a new app for Android, and this app would be able to comunicate with the recovery to schedule things like backup and restore. In 2011 I released "ROM Updater" (not that big success though) which used extendedcommands, an extension to the recoveries made by the team of CyanogenMod (it was indeed created to let the CM updater work).
ClockworkMod Recovery adopted this system, but the author probably didn't want the competition, so started to release the ClockworkMod recovery with encrypted extendedcommands. You can still recompile CWM and redistribute with the unencrypted commands, though I decided to opt for something less rouge-ish (why the hell should I recompile something that already "works"?).
Team Win Recovery Project is a 100% open-source recovery with a new scripting language, called "OpenRecoveryScript". It's just like extendedcommands, but without all the implications of "Premium"* or in any case limited API.
Well, TWRP is not only that, it's a full-multitouch recovery, easy to use. It's being built for a list of devices, and this list will be updated every time someone will compile the recovery for his own device. I decided to compile it for the P7500, hoping it will be added soon to the official list. In the mean while, I'll release the builds right here.
I've built and tested the recovery image for the P7500 (WiFi+GSM) and it's been confirmed that it works on the P7510 device too (WiFi only).
Goo.im GT-P7500 TWRP repository
TechErrata GT-P7500 TWRP repository
TWRP 2.2.1.5 - GT-P7500
openrecovery-twrp-2.2.1.5-gt-p7500.img (on Goo.im)
openrecovery-twrp-2.2.1.5-gt-p7500.img (on TechErrata.com)
TWRP 2.2.2.0 - GT-P7510 (thanks to MapleSyrup)
openrecovery-twrp-2.2.2.0-gt-p7510.img
How to flash:
- Copy the recovery into the storage partition (alias /sdcard)
- In adb, as root, execute dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p2
Cheers
*I personally think that Koushik Dutta (the ClockworkMod guy), encrypting the commands with his distributions, played hard: ROM Manager is the "official" CyanogenMod updater (it's distributed along with any CM release even if it's not opensource (and the CM guys worked hard to take the closed-source apps out of their release)), de-facto everybody install the CWM recovery just 'cause it's already there (déjà vu Internet Explorer?). I think this is called "monopoly" and should be fought in any possible way.
I'm all for true open source development, and will be watching your progress on this. Kudos and a thanks to you!
Sent from my GT-P7510 using XDA Premium HD app
I'd be willing to test for the p4vzw. If you build an image for it.
Sent from my Galaxy Nexus using Tapatalk 2
This appears to work on my Wifi Galaxy Tab 10.1 (p7510). Although the log says "E: Unable to mount /sdcard" I can access the sdcard just fine. I tried updating to the latest droidbasement.com kernel and it flashed perfectly.
Oh, and thanks for the quick and easy non-odin way of flashing recoveries.
The recovery is already in the goo.im repository
http://goo.im/devs/OpenRecovery/gt-p7500
The dropbox image is already update to fix the /sdcard "problem" ^^
Would this work on a Galaxy Tab 10.1 wifi (p4wifi)?
Sent from my Nexus One
According to AAccount yes. Please confirm this, so that I'll tell the TWRP guys to add the repo for that device too and I'll update the title of the conversation here.
I can say without a doubt that this is the best recovery I have used on any device in my 3 years with android phones. Wow! Graphics a bit grainy on the p7500, but functionality is fantastic! Thanks!
Very nice recovery system, good to see other options. HTC users had several choices such as AmonRa and 4ext.
Can confirm that it works on the WiFi only version. Thanks for the options , friend. Been running TWRP on my One X since the boot loader was unlocked, and I was missing it.
Sent from my GT-P7510 using Tapatalk 2
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
You don't actually need to use adb. Any terminal app should do it. Just tyope "su" before issuing the dd command. I used this app https://play.google.com/store/apps/details?id=jackpal.androidterm&feature=nav_result. I suppose a word of caution would be to make sure you have the command correctly. Don't make a typo like mmcblk0p3 or you could be in a nasty situation.
Adb can be found in the android sdk. Google "android sdk" and download the appropriate one. After that have the sdk download platform tools.
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
An easy and safe way if you have the SDK installed is to run adb shell
Then type su
paste in the dd command posted earlier
Thanks....I went on google and am now learning about Android SDK. Interesting stuff. I know how I will be spending my weekend!
EDIT: In the meantime, I went ahead and used terminal emulator for the commands. I definitely like the touch interface...and it looks nicer than cwm for sure! It is a little slow graphically, but I think that can be forgiven based on the look of the interface.
Confirmed working on the p7510 wifi
Sent from my GT-P7510 using XDA Premium HD app
Hi
It works like a charm on my 7500.
Thanks for that. Maybe some one could make the install more user friendly, a recovery zip?
Sent from my GT-P7500 using XDA Premium HD app
I could create an update zip... if only I could remember where I left the signing tool...
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
elegos said:
The dropbox image is already update to fix the /sdcard "problem" ^^
Click to expand...
Click to collapse
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
That is a nice one, thank you very much for this project.
MapleSyrup said:
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/gt-p7500/openrecovery-twrp-gt-p7500-2.1.8.img
^-- this works for the 7510 too
BTW it's just a line in recovery.fstab in the device sources: comment the /sdcard one.
Works great for me although it's a bit slow to boot into compared to CWM or even to TWRP on my brother's HP Touchpad. Also text is a bit pixelated. Other than that though it seems to work well. I use 4ext on my Nexus One so it's really nice to finally get a touch recovery on my tab too
Sent from my GT-P7510 using Tapatalk
Before everyone starts flaming me and trying to kill me for being such a noob, i would like to say that i'm a teen and a noob.
ANYWAYS, i got bored and decided to have a go at porting Firefox OS to the Optimus 2X. After figuring out how to make a flashable zip out of .img's, I tested a bit. Unfortunately ADB doesnt work and I don't know how to do live kernel debugging.
What works: Kernel
What doesn't work: everything else
Source code: http://github.com/JordanRulz
Download:
First Semi-working attempt: http://d-h.st/juX (not a flashable zip)
2nd attempt: link on http://jordanrulz.tk/ (flashable)
3rd attempt (current): http://d-h.st/0We(flashable)
Turn signature verification off before flashing
BUILD INSTRUCTIONS (still doesn't work, but for anyone who thinks they might have the answer, go right ahead)
1.
Code:
git clone http://github.com/JordanRulz/B2G.git
2.extract a cm9 rom to B2G/my_device_backup
3.cd to the B2G directory and
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh p990
and wait for the code to download. This has a good chance of failing because repo and git are stupid.
4.
Code:
./build.sh
5.edit core/sysroot/init.rc so that it imports init.p990.rc
6.go to line 98 of build/core/Makefile and change the build fingerprint to something acceptable by the build system
7.go online and find a wpa_ctrl.h and put it in hardware/libhardware_legacy/wifi/libwpa_client/wpa_ctrl.h
8.copy libcamera.so and libwpa_client.so from a cm9-based rom to out/target/product/p990/obj/lib/
9.it should turn out boot,img, system.img, a system folder, userdata.img, a userdata folder, etc. with adaptations, you should be able to craft a flashable zip out of the folders.
Please hit donate if you feel my work is worth donating to.
Good effort bro!
Way to go buddy.... Expecting this Rom for our beloved Optimus 2x. (me too a noob cant help much)..
Thanks and wish u best of luck..
ahahaha, great work! bring to the old O2X a new system!
Interesting tread, I'll look at the files. Let's hope this will be a cooperative tread to make this
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
nicholaschw said:
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
Click to expand...
Click to collapse
doesn't work. "invalid image file"
i think probably you can pm any recognised dev's for help....if you post a thread here i dont think anybody will try to help....you can pm the dev's like tonyp, harsh, carburano or anyone and you can ask for help in packaging and later on continue with your development....just an idea....:good:
good stuff man., were not the flaming community of yester year
This is getting really frustrating, after restarting multiple times and over 10 failed attempts. I have forked all the repos to my github so that all that want to help are able to do so. http://github.com/JordanRulz
Hello everyone. It's for new bl or old bl? Thanks
Sent from my LG-P990 using xda app-developers app
I say it´s for the old BL, if i don´t read the updater-script inside completly wrong.
It's for old bl
Sent from my LG-P990 using xda app-developers app
build instructions (for a non-working build, but still useful for f*cking around) were added.
JordanRulz said:
build instructions (for a non-working build, but still useful for f*cking around) were added.
Click to expand...
Click to collapse
:good::good:
Don't know if you're going at it the right way but good luck, and you should contact another dev just to make sure at least that you're on the right path.
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
JordanRulz said:
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
Click to expand...
Click to collapse
I hope if you develop successful, it will have 1 for SU660 :victory:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob report on f.b.i
alexcyb said:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob
Click to expand...
Click to collapse
Its not a "virus java drive", its a hidden bitcoin miner. If u use a secure browser like Firefox, it will prompt you before running it.
Sent from my LG Optimus 2x using xda app-developers app