Related
If you like that I'm doing this, then a thanks is cool, PLEASE DONATE, TIME OR MONEY BUT GIVE SOMETHING TO THESE DEVS!
http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
New - No more partition editing required!
HC16JUN2011
HD Video
-Changelog
Like with any rom, YOU MUST WIPE CACHE, SYSTEM AND DATA, this rom especially, the is a pre alpha and has issues with cache, if you don't clear your info every time you will run into problems. I also clear Dalvik Cache and Battery Stats.
Old info on how to partition
STEP 1 – You need the new NVFlash click here for the unpartitioned onces(may need these)
NVflash edit- pretty simple you need to change the android fastboot full, you'll find that file towards the top of the nvflash folder or you can download my premade ones: (BUT I DIDN'T FORCE YOU TO DOWNLOAD THESE, IF YOU BRICK YOUR DEVICE BY USING THESE THEN YOU BRICKED IT NOT ME, YOU HAVE BEEN WARNED)
Sorry about the mega upload, working on getting my server up, also CWM is untested, it had some problems but I believe that was due to file size.
Clockwork Mod folder
Stock Recovery Folder
The section your looking for looks like this
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=209715200 <---(here is the money)
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=system.img
minus the arrow and the here is the money you'll find the size listed as 209715200, you need to change that to 536870912, once you save go to here to setup your APX drivers and prepare to flash according to the link
STEP 1.1 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY Download Here
Make a copy of your nvflash folder, I name it PIXEL QI CW Mod
STEP 1.2 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY
Thank you darknao
Quick & Dirty method :
Extract the recovery.img from the clockwork.zip, and copy it to the nvflash folder(replace the original one).
Step 2
You need then to put your device into force recovery mode, so turn off your device, then power it on while holding the power + the volume down button till a orange and a yellow lite light up.
Step 3
Run the download.bat file described in the nvflash or unbrick your adam thread - now you can change the file name of the rom to update.zip and flash freely!
Reserved for other usage
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Amon Darthir said:
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Click to expand...
Click to collapse
Gapps are included however this build didn't have them, they had alot of problems with the sync feature, but in theory you should be able to use the latest gingerbread gapps, I will test that right now.
-OK I tested it out, the google setup frooze up on me, after restarting I was able to get into the initial setup, but I have the wifi only model, so I'm going to look into the gapp issue, see if I can find a way around.
-Tried a couple more copies of gapps including a HC edit for the nook sdk HC-- I would press more into this but with the rate of the updates I think its kinda pointless, for now Im going to adb push the market and see what I can get working, hopefully not in-vain since MrGuy and DJSteve move so fast with the updates.
after you use nvflash it will start to boot.. (this would be before flashing update zip) so should I power it down while its booting that first time in order to reboot to recovery and flash the zip?
I do but you don't have to if you use clockwork mod, it doesn't really matter, since you will be building your Dalvik cache once you install your rom.
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
jakobdroid said:
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
Click to expand...
Click to collapse
what operating system do you have? Is your adam in apx mode, and did you edit the android fastboot already? is it still a .bat file
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
jakobdroid said:
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
Click to expand...
Click to collapse
APX is the force recovery, the drivers are included with the NVflash, you must put your device into force recovery, with your device off you press volume down + power till you get your two lights to light up by the power cord, it'll be red and yellow, this is force recovery mode, I am using CW with it and I have listed above how to flash the CW with the increased partition. If you can't figure it out I will be adding the NVflash files with CW mode and non CW mode with the partition edits tonight. I will be turning the change log into a FAQ as well.
Just flashed the ROM and it is awesome. I was just wondering how to get a file managers working. I can't see my sd card. But otherwise, its amazing that honeycomb is up so fast.
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
I'm downloading the file now, working on military lines so its slow to download but that way I can get a better idea of whats going on, also whats your operating system.
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Sounds like you're using linux like me. Are you on ubuntu. Cause I tried and tried and even with chmod and sudo and still got the same error. Consider this post though from: http://notioninkhacks.com/forums/viewtopic.php?f=90&t=1651&start=30
Hey gibson, thanks heaps for that! Actually, yourncomment before asking which folder I was in did it. Very strange, I had to run the commands from 2 folders above the extracted one, then symlink all the other files into the folder I was running from. Will post more later for people who run into similar issues, likely over at the unbricking thread. For now I've got a dualboot setup, and am running a minimal natty rootstock. I tried using the full omap4 image (ubuntu's default arm), but could only get it booting with lots of errors and no gui. Will be aiming to install the netbook desktop (unity 2d) in the next few days.
Re the post above, rayman's boot image already includes the kernel, so it's not needed in the rootstock command. Re the other options, probably will work, but remember rootstock is limited in what you can build... I.e., unless you have heaps of physical ram, you will probably only be able to build a few packages. Head over to xda, and the ubuntu on adam thread there for more info. We have experimented a lot with rootstock builds, and some of that might be useful.
Has anyone tried raymans boot.img with a natty rootstock? Did it work, and has anyone gotten a 2d unity gui up and running? My minimal natty rootstock boots fine, though I notice a few errors. Not sure if they are problematic or not. In any case, the build I made seems to be missing some important wireless tools, so I will likely rebuild it again with them in it soon. Am I likely to run into any problems using rayman's boot image, and steveh's kernel, with a natty build? Happy to post up my work if I get anything decent. Cheers.
osx 10.6.6, thank you!
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Also consider this: http://forum.xda-developers.com/archive/index.php/t-895388.html
Saved me some time thank you...
daiuton said:
Saved me some time thank you...
Click to expand...
Click to collapse
Don't know if the problem is solved yet but that doesn't take away from this honeycomb coolness. So happy to have so much use out of this Adam. Thanks.
that really didnt help, thanks though. i guess i will instal ubuntu in parallels and give it a shot...
Two problems here:
-How can i mount the adam with the computer? To move next updates and update in the next releases
-There is any gapps working (market,etc...)?
Could somebody provide instructions on using the psouza script? I soft bricked my brand NEW d3. I already dl the 467 mb file and the psouza script. do i use it in ap fastboot or what? Also, it says in the instructions to put the large file in the files folder or something. I tried that and it says I cannot create a folder. Please someone. I know this isn't a dev contribution but I've got issues.
The Psouza script has a file with instructions. Tells you what to do to the last step. Open it up with adobe reader or some type of reader and follow each step and you should be good to go.
Sent from my DROID3 using XDA App
http://rootzwiki.com/content.php?264-How-to-Un-Brick-your-D3. Go here, all the files are there.
Sent from my DROID3 using XDA App
Apparently I am still having trouble. If someone else could help with this, I would be very thankful. It says to extract the update to the files folder however, it will not allow me. During that process, i get a couple of errors. I am very computer literate, however, not necessarily d3 literate. Please someone.
http://www.vodahost.com/web-hosting-winzip-free-download.html/. You have to extract the files using 7zip or a Zip program. I used WinZip,the 45 day trial. Go online download one of these programs, run them. They should automatically zip your files. This way you'll be able to extract them all.
Sent from my DROID3 using XDA App
Can you describe your soft brick? You may have other options depending on your current condition (needs a launcher replacement, etc).
Sent from my DROID3 using XDA App
I rooted installed the bootstrap that had tweaked at bottom. went to install steel rom. rebooted and stayed at dual core motorola splash screen for at least 15 minutes. i thought something must be wrong so i pulled batt and did the same thing. i have since tried to use rsd but i am not real well versed on that method. i am currently trying psouza's method on rootzwiki with no luck. I dl all the files there and used 7 zip to extract but it says files are broken. please help somebody. ive been at this for hours now.
the most hopeful solution so far is rsd using the 466 mb xml file. I get an error on 13/18 flash system.img though and it fails. Help please.
sorry it actually fails on the 16/18 cd rom it appears.
Were you able to install Steel Droid or did it never reach that menu?
Sent from my DROID3 using XDA App
it said it installed on the phone but when i rebooted it stayed on the dual core screen for a longgggggggggggggg time.
duncan254 said:
it said it installed on the phone but when i rebooted it stayed on the dual core screen for a longgggggggggggggg time.
Click to expand...
Click to collapse
i used this link. i no theres a thread out there that has the two updates back words. i had that issue before. i download every one i could find and started going through them till i found one that worked.
http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
Maybe a factory restore or simply clearing the cache would help if a previous backup is unavailable or cannot be used. It may not fix everything, but restore has saved me numerous times.
Sent from my DROID3 using XDA App
qudwis said:
use x + power button and go to android recovery
1. press x first then power button
2. when the m logo shows let go the power button but keep pressing the x
3. when triangle shows, press volume up and down at the same time
then the screen will show android system recovery
do a wipe cache first then wipe data/factory reset
then reboot your phone..
if this doesn't work, sbf is the only choice left as far as i know of
Click to expand...
Click to collapse
Try that. I went through the same thing. Even though I use the script to unbrick my phone. This was suggested and it may help.
Sent from my DROID3 using XDA App
Sent from my DROID3 using XDA App
I dl the flashboot file. When i try and extract i get an error that says failed and check to make sure there's enough disk space. It does this when i try and extract when in rsd. when i try to extract using winzip to a misc folder, i get errors saying that system, radio, and preinstall.img files are corrupt. btw this is the second time ive dl this package. HELP
the phone will not boot into anything other than m plus power menu.
The M menu should suit your needs as well. Go into recovery and press the up and down volume buttons to access the recovery menu. Clearing the cache then doing a factory restore should get you functional.
I fumbled my way into Clockwork without the bootstrap somehow earlier today but haven't been able to reproduce it.
Sent from my DROID3 using XDA App
whenever i go into rsd 5.5 and select the large zip file, it starts unzipping but stops at different points and says something about not enough disk space. does it mean on hard drive. i have almost 5 gb free.
when i boot to the m menu and try recovery, i get these three lines at the bottom:
Invalid CG OTV (CG; system); invalid sp data
invalid cg hab (cg; system, status; 0x004e)
invalid cg otv (cg; system)
PLEASE ANYONE HELP
Sorry, I have no experience with RSD, though I believe only a certain amount of storage is set aside for system use. Most of the phone is partitioned for storage.
After a bit of tinkering I brought up Clockwork again - reboot into your M menu, leave it selected on the first option, press and hold your power button for about five seconds then release. Once the menu times out your Motorola screen will come up for a bit then drop you into Clockwork. With this menu you can try reflashing the Steel Droid zip or a restore a backup if you prefer not to do the factory reset mentioned earlier.
Sent from my DROID3 using XDA App
when trying to extract fastboot files i get this in winzip diagnostic:
! C:\Users\duncan254\Desktop\Online DL's\VRZ_XT862_5.5.1_84_D3G-55_1FF_01.zip: CRC failed in SWupdatefile\cdrom. The file is corrupt
! C:\Users\duncan254\Desktop\Online DL's\VRZ_XT862_5.5.1_84_D3G-55_1FF_01.zip: CRC failed in SWupdatefile\preinstall.img. The file is corrupt
! C:\Users\duncan254\Desktop\Online DL's\VRZ_XT862_5.5.1_84_D3G-55_1FF_01.zip: CRC failed in SWupdatefile\radio.img. The file is corrupt
! C:\Users\duncan254\Desktop\Online DL's\VRZ_XT862_5.5.1_84_D3G-55_1FF_01.zip: CRC failed in SWupdatefile\system.img. The file is corrupt
WTF
Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?
I'm having hard time flash custom recovery. I installed ROM Manager, when I tried to go to recovery I got stuck at android logo with EXCLAMATORY POINT. I already followed this instructions http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638 (deleted these files /system/etc/install-recovery.sh and /system/recovery-from-boot.p)
Followed these instructions:
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
I also installed 4Ext Touch Recovery, but I think it need a wifi to connect to server, but I can't access a wife connection as of now.
What am I missing? I'm about to flash a ROM, my problem is just the recovery.. Anyone can help me with this? :crying:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
demkantor said:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
Click to expand...
Click to collapse
I really dont know what is happening. Still I can't go to recovery. Btw, does locking/unlocking bootloader affects in flashing custom recovery. But I think I already unlock mine, how would I know if unlock or lock my bootloader?
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
demkantor said:
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*BlackRose - Made by Lecabel(dla5244) *
jb-260/10/166
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PB9911000)
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Apr 21 2012, 04:53:16
HBOOT
VOL UP
VOL DOWN
TRACKBALL
FASTBOOT
RECOVERY - when I select this, I will be stuck at android logo with !
REBOOT
POWERDOWN
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
demkantor said:
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally.. Thank you so much.. I can now go to custom recovery.. Now I will backup and wipe then flash.. :good::good: Will press THANK button now, maybe a million times.. hehe
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Okay. I will try to read my left time for this day. Thanks a lot..
demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, I have a follow up question regarding sd partition, I will just raise my question here than making another thread. I have 4GB SD card but I forgot how much ext partition I made before but my total space in my SD card is 3.21GB. I want to partition my sd card again and increase it maybe to 1gb. If I will increase my partition should I flash again my ROM (VJ CM10.1 | Jelly Bean 4.2.2 - v6.0) and execute a2sd command in terminal emulator? or it's okay to partition my sd card without flashing the ROM again?
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
demkantor said:
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I think a2sd is not working in my device. When I tried to install a2sd or reinstall it there was a line written in termenal emulator (/dev/block/mmcblkop2) I think that the reason why I easily having internal memory full, even I already partition my sd card, with 1024 ext partition using 4ext touch recovery. Check my screenshot in titanium backup showing my memory status..
Sent from my Nexus One using xda app-developers app
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
demkantor said:
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Im using VJ CM10.1 | JB 4.2.2 V 6.0. How to move data to ext partition? I will post screenshot in my internal storage too.
Sent from my Nexus One using xda app-developers app
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
demkantor said:
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
Click to expand...
Click to collapse
Thanks. Btw what rom are you using?
Sent from my Nexus One using xda app-developers app
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
demkantor said:
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Thanks, Btw, what if I wanted to change my ROM, what procedure should I follow? Should I go back to Stock ROM before flashing a new ROM?
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
demkantor said:
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply. So, you're saying that I should partition my system first and flash recovery just like what you taught me in our previous posts? Just to be sure and making all things clear to my self.
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Beta 1 zip is bad i am just goinmg to make a windows bat file that will do it lol
instructions.
if you want to keep your rom and data you will need and external sd card that is big nough to hold a backup of system and data.
okay i made a bat script that **SHOULD** work i havent been able to test one part of it so if youd like to test ill attach the zip to the bottom of the post
DISCLAIMER
i am not resposible if you brick your device doing this i can only confirm it will work on D415 if your onj a variant and want to know if itll work PM me the output put either from adb or a terminal emulator ls -l /dev/block/platform/msm_sdcc.1/by-num
now there are instructions on screen to follow so make sure you fread them or you could screw something uyp lol
demonslayer12349 said:
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Click to expand...
Click to collapse
so how do u increased it.....???
using sd card ext partitions or shrinking of other partitions..???
kprsnt said:
so how do u increased it.....???
using sd card ext partitions or shrinking of other partitions..???
Click to expand...
Click to collapse
shrinking of others. my final shrinking puts the total at 5.65GB
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
sorabh.v6 said:
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
Update..???
This works (because i tried this kind of method in p500)..
But I didnt tested it because my device is new ..
If u wanna try PM him
sorabh.v6 said:
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
just posted the first beta
I'm going to try this then give feed back
Sent from my LG-D410 using Tapatalk
---------- Post added at 05:26 AM ---------- Previous post was at 05:25 AM ----------
Just curious if this will work with stock rom
Sent from my LG-D410 using Tapatalk
I got an error flashing the .zip on TWRP, something related to binary. My model is the 410hn. Thanks for the support to L90.
Using cwm, got and error 6 during flash. D410. Stock ROM
Sent from my LG-D410 using Tapatalk
goldfinv said:
Using cwm, got and error 6 during flash. D410. Stock ROM
Sent from my LG-D410 using Tapatalk
Click to expand...
Click to collapse
InfinitusDesigner said:
I got an error flashing the .zip on TWRP, something related to binary. My model is the 410hn. Thanks for the support to L90.
Click to expand...
Click to collapse
working on a windows script right now to do it or to restore it to defazult
demonslayer12349 said:
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Beta 1 zip is bad i am just goinmg to make a windows bat file that will do it lol
instructions.
if you want to keep your rom and data you will need and external sd card that is big nough to hold a backup of system and data.
okay i made a bat script that **SHOULD** work i havent been able to test one part of it so if youd like to test ill attach the zip to the bottom of the post
DISCLAIMER
i am not resposible if you brick your device doing this i can only confirm it will work on D415 if your onj a variant and want to know if itll work PM me the output put either from adb or a terminal emulator ls -l /dev/block/platform/msm_sdcc.1/by-num
now there are instructions on screen to follow so make sure you fread them or you could screw something uyp lol
Click to expand...
Click to collapse
I tried using this and it at first didn't find adb. I moved the .bat into the tools folder, and it ran and booted to recovery. When it booted to recovery it sat there saying "waiting for device to enter recovery"
Sent from my LG-D415 using Tapatalk
blondgod said:
I tried using this and it at first didn't find adb. I moved the .bat into the tools folder, and it ran and booted to recovery. When it booted to recovery it sat there saying "waiting for device to enter recovery"
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Okay. I need to refresh my bat scripting obviously XD and do you have twro installed? I should have mentioned that and if nothing else just unplug plug back in.
demonslayer12349 said:
Okay. I need to refresh my bat scripting obviously XD and do you have twro installed? I should have mentioned that and if nothing else just unplug plug back in.
Click to expand...
Click to collapse
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
blondgod said:
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
Click to expand...
Click to collapse
I've tried making a flashable zip but with no success. Right now twrp is the only way this works
blondgod said:
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
Click to expand...
Click to collapse
Sorry should have mentioned you needed twrp. I've tried flashable zips but can't seem to get a working one
demonslayer12349 said:
Sorry should have mentioned you needed twrp. I've tried flashable zips but can't seem to get a working one
Click to expand...
Click to collapse
Its no problem at all. I've got enough space for now. Thanks for the work!
Sent from my LG-D415 using Tapatalk
blondgod said:
Its no problem at all. I've got enough space for now. Thanks for the work!
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
No problem.
What about restoring original partition scheme? Is this possible via kdz tools (or what's called)? Is kdz reparitioning device?
Or it has to be done manually (then we have repart making it EXACTLY the same, every single byte?
@demonslayer12349, your script is a little strange.
Code:
@adb shell su -c "mount -o remopunt rw, /"
It should be:
Code:
@adb shell su -c "mount -o remount rw, /"
isn't it?
Then another thing. You delete 4 partitions and create only three.
For D410 partition 31 is "eksst". It is 0.5mb only. What is the reason to delete it?
Or the script is device-specific?
judas1977 said:
What about restoring original partition scheme? Is this possible via kdz tools (or what's called)? Is kdz reparitioning device?
Or it has to be done manually (then we have repart making it EXACTLY the same, every single byte?
Click to expand...
Click to collapse
As I know LG software doesn't recreate partitions, so you have to do it manually.
@up
Thx for the answer. Spoony bards they are