[Q] recovery.img is too large - Dell Streak 7

Hello everybody,
I know that I should put this threat in Development but I have no rights to write there.
I tried to install CM10.1 and everything is going good until I receive such infromation: "recovery.img is too large for partition" and installation is stopped and Streak is bricked. I can repeat installation one more time with the same error.
Is anybody able to help me, what to do. How to reformat partition or change it size?
OK I solved the problem. I installed previous edition and now it works
best regards,

Actually a pretty easy fix. I need to adjust that in the scripts.

da1k said:
Hello everybody,
I know that I should put this threat in Development but I have no rights to write there.
I tried to install CM10.1 and everything is going good until I receive such infromation: "recovery.img is too large for partition" and installation is stopped and Streak is bricked. I can repeat installation one more time with the same error.
Is anybody able to help me, what to do. How to reformat partition or change it size?
OK I solved the problem. I installed previous edition and now it works
best regards,
Click to expand...
Click to collapse
I also have this size problem when using the original kernel.
What did you do to fix this? What previous version?\
thanks

You have to adjust the flash configuration file. My newest build has this fixed.

giveen said:
You have to adjust the flash configuration file. My newest build has this fixed.
Click to expand...
Click to collapse
i as asking because I try to compile recovery for mtk6589 based phones.
I cannot compile because the size is too large.
When I try to compile the wrong block size is shown, while the parameter is set to the proper value in the board config file.
It seems it is not read somehow.
It is very hard to find this kind of stuff when googling .
well, of to bed now, better luck next time

OpenMinded said:
i as asking because I try to compile recovery for mtk6589 based phones.
I cannot compile because the size is too large.
When I try to compile the wrong block size is shown, while the parameter is set to the proper value in the board config file.
It seems it is not read somehow.
It is very hard to find this kind of stuff when googling .
well, of to bed now, better luck next time
Click to expand...
Click to collapse
Adjust the size in your BoardConfig

giveen said:
Adjust the size in your BoardConfig
Click to expand...
Click to collapse
I did but according to compiler output it is not used.
Maybe some config error in my build setup.
I just followed the cm wiki with no luck.
There is also a message when using lunch,something like device not configured.
I'll muddle on,thanks

OpenMinded said:
I did but according to compiler output it is not used.
Maybe some config error in my build setup.
I just followed the cm wiki with no luck.
There is also a message when using lunch,something like device not configured.
I'll muddle on,thanks
Click to expand...
Click to collapse
You have this in BoardConfig.mk?
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 6042880
Make sure yours is large enough to hold your recovery image size and is smaller than your recovery partition.

giveen said:
You have this in BoardConfig.mk?
Code:
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 6042880
Make sure yours is large enough to hold your recovery image size and is smaller than your recovery partition.
Click to expand...
Click to collapse
I have 0x00600000 . I will try your setting.
If I allocate too much, it will overwrite the sec_ro partition.
I have not seen it being used.
I'll report back. the strange thing is also that the compiler reports a blocksize of 135xxx while it is set tot 131xxx.
Thank you for your input, cheers
---------- Post added at 03:46 PM ---------- Previous post was at 03:33 PM ----------
OpenMinded said:
I have 0x00600000 . I will try your setting.
If I allocate too much, it will overwrite the sec_ro partition.
I have not seen it being used.
I'll report back. the strange thing is also that the compiler reports a blocksize of 135xxx while it is set tot 131xxx.
Thank you for your input, cheers
Click to expand...
Click to collapse
Well just tried it, it now wrongly reports a bigger size for the max 103xxxxx.
It build fine now, it's 6.3 mb, but the bloody piece of crap just does not boot.
I'm pretty much done for the moment.
Following multiple tutorials that lead to all kinds of errors other people lack to have is getting a bit annoying now .
thanks anyway, cheers

Try setting it to 6291456
0x00600000 = 6291456
What device are you developing for? What is the partition size?

giveen said:
Try setting it to 6291456
0x00600000 = 6291456
What device are you developing for? What is the partition size?
Click to expand...
Click to collapse
Thanks for explaining. I am developing for Alps e2001v21_v89_gq3008s.
It is sold as Star / Haipai N9599 / N9589 .
The buildprop shows Alps and the string e2001v21_v89_gq3008s.
It is a MTK6589 based device with 1 Gb rom/ 16 gb ram and some kind of screen that supports a pen.
What do you mean with partition size?
I thought it was that 0x00600000.
It was very hard to find out the real device list and partitions, so I extracted it from a working recovery image.
Please find it attached.
Thanks for any help!
I just tried to fix things by fiddling with local_manifest, not sure if it has influence.
It's frustrating not to be able to build this darn thing, your help is greatly appreciated!
I'm trying to recompile now and also attached the scatter file for mtk droid tools.

Hex vs Decimal
Local_manifest is just where things download from

giveen said:
Hex vs Decimal
Local_manifest is just where things download from
Click to expand...
Click to collapse
thanks, I know hex/decimal difference.
I am just unable to use the partition size and make a fitting recovery, let alone one that boots .

OpenMinded said:
thanks, I know hex/decimal difference.
I am just unable to use the partition size and make a fitting recovery, let alone one that boots .
Click to expand...
Click to collapse
I finally solved it.
I took the number of bytes from the compiler output that were claimed as reserver.
I added that to the maximum decimal number and all is fine.
Booting also worked, the issue was caused by a problem in the binary kernel I was using, which I found out by extracting it with unpack mtk tools again and comparing it.
So I have a working CWM 6.0 now for my mtk6589 based device.
Yeah!
thanks for the help, cheers

Would you share it?
OpenMinded said:
I finally solved it.
I took the number of bytes from the compiler output that were claimed as reserver.
I added that to the maximum decimal number and all is fine.
Booting also worked, the issue was caused by a problem in the binary kernel I was using, which I found out by extracting it with unpack mtk tools again and comparing it.
So I have a working CWM 6.0 now for my mtk6589 based device.
Yeah!
thanks for the help, cheers
Click to expand...
Click to collapse
I've got a very similar phone, the STAR N9599 and would appreciate it if you could share your work. I'm having trouble with my Camera not auto-focusing and wonder if a ROM upgrade would resolve it.

byb4 said:
I've got a very similar phone, the STAR N9599 and would appreciate it if you could share your work. I'm having trouble with my Camera not auto-focusing and wonder if a ROM upgrade would resolve it.
Click to expand...
Click to collapse
This is not the place to discuss that I guess.
Look here:
http://forum.xda-developers.com/showthread.php?p=44216874#post44216874
I will post the CM 6 I compiled there soon, there is a ROM here:
http://www.needrom.com/phone-roms/star/n9599/
Make sure you backup first (google it) and be sure the hardware is identical.
No warranties and of course no one to blame when you brick it, but yourself.
Please remember that before flashing. You might try to find the camera files first to try, or download the ICS camera app from the market, to check if it is a software or hardware problem.

i started working on ubuntu touch every thing is going well up to now :fingers-crossed:
here the problem is with the recovery.img, and boot.img they were too large to flash.... how to change the partition table before flashing ??
i made some changes to partition sizes in bord config finally i built those images ,here my question is how does the remaining partitions adjust AND how to flash
where to adjust all of these
:good: in advance

Hello, same prob here...
Also, do I need the kernel source for this to work? And if so, where do I put it?

hahagu said:
Hello, same prob here...
Also, do I need the kernel source for this to work? And if so, where do I put it?
Click to expand...
Click to collapse
Kernel source is on my github

giveen said:
Kernel source is on my github
Click to expand...
Click to collapse
What's ur github? And what is the kernel src for?

Related

[DISCUSSION/TESTING] Ubuntu Linux on Blackstone

Hi men.
Let's talk here about running Ubuntu on our blackstones.
Right now we can boot Ubuntu arm on our blackstones, based on the 'omnibuntu' files. it seems to work well but screen calibration is still difficult...
you can find useful links on the last pages of the android thread (i'm on my blackstone right now and it's difficult to copy and paste all the links) but let's leave the android thread for android...
let's see how far we can get from now
FIRST I WANT TO SAY BIG THANKS FOR THOSE WHO HAD MADE GREAT WORK TO BUILD BLACKSTONE LINUX KERNEL!
WITHOUT IT THIS TREE IS NOT TO BE POSSIBLE.
Here is lidle howto because make lidle bit sense to boot ubuntu.
1.First you have to make partitions to your memory card.(WARNING!!!!!! IF YOU DONT KNOW WHAT YOU ARE DOING YOU MAY LOSE YOUR DATA)
-start ubuntu live cd 9.04 in your pc wich you find here:http://releases.ubuntu.com/9.04/ (I think that everyone can burn iso image to cd, but if not just ask)
-in your blackstone go Start-Settings-Connections-USB to PC and select Disk Drive (If you want use activesync you have to change it back to ActiveSync)
-connect your blackstone to pc and make partitions with those instructions witch found here:http://linuxomnia.sourceforge.net/Howto.pdf
2.Second you have to put ubuntu files write places.
-download attachs (fatfiles.zip) and extract to first partition
-download omniubuntu-rootfs.tar.gz here:http://sourceforge.net/projects/linuxomnia/files/ and extract it and put files to second partition
3.Boot.
-in blackstone filemanager go to storage card and start haret
-select run and ubuntu will boot
-as fast as you can, move the keyboard lidle bit down because until you can`t calibrate the screen
-when it seems to stop buuting is time calibrate screen
-tap first up left to screen and move up the cross and let off, next make same up right, down right, down left and middle of the screen
This is how i get it works(First i only tap the screen.Second tap i let and hold stylus on the sceen and move it up the cross.In the same way i do to top right....ec.)
-one more tap and that is it
AND AS USUALLY ALWAYS IT IS YOUR OWN RESPONSIBILITY IF SOMETHING GOES WRONG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Start debian installer
You can run debian install by downloading one iso from:http://cdimage.debian.org/debian-cd/5.0.3/arm/iso-cd/ and extract it to second partition wich is ext2 and put attachs and initrd.gz in first partition wich is fat.Initrrd.gz you will find here:http://people.debian.org/~joeyh/d-i/armel/images/daily/versatile/netboot/
Also put vmlinuz in second ext2 partition and after all boot installation with haret.I am not yet finished installation.
You can extract iso file with 7zip.
You have nearly 400 views and only 2 replies. I feel that if you are going to keep this thread alive and vibrant with lots of posts you need to layout exactly what it is you are doing because a large number of people have no idea what this is all about and why they should get involved.
Then give very detailed and straight forward instruction on how to install such software, but make the instruction idiot proof.
Consider a description or screenshots to help people grasp your concept.
Thanks and good luck as whatever it is you are doing sounds interesting.
hi sakkeus.
very interesting, thanks!
a couple of questions:
-which initrd were you using with ubuntu?
-can we use the same ubuntu partitions to run debian?
thanks!
let's keep trying and testing
Heefy said:
You have nearly 400 views and only 2 replies. I feel that if you are going to keep this thread alive and vibrant with lots of posts you need to layout exactly what it is you are doing because a large number of people have no idea what this is all about and why they should get involved.
Then give very detailed and straight forward instruction on how to install such software, but make the instruction idiot proof.
Consider a description or screenshots to help people grasp your concept.
Thanks and good luck as whatever it is you are doing sounds interesting.
Click to expand...
Click to collapse
I am myself still checkin out how to use linux in blackstone.
I will make sense instructions abaut what i get out, but it takes lidle time.
kingofslide54 said:
hi sakkeus.
very interesting, thanks!
a couple of questions:
-which initrd were you using with ubuntu?
-can we use the same ubuntu partitions to run debian?
thanks!
let's keep trying and testing
Click to expand...
Click to collapse
None initrd to fat partition.All system files are in second ext2 partition except zimage default.txt and haret.
I think that debian installation needs more room in ext2, but otherwise same parts.
sakkeus11 said:
None initrd to fat partition.All system files are in second ext2 partition except zimage default.txt and haret.
Click to expand...
Click to collapse
thanks, sakkeus, but when I try to launch ubuntu using your default, haret says 'couldnt find initrd'. when I remove the initrd line from the default, ubuntu boots well (excepting the screen calibration) so I think ext2 files are ok.that's why I asked.
if it works it would be interesting to see if anyone can get Maemo to work on the hd it's the same os used on the Nokia N900 and heavily based on Linux
yes, Heefy is right!
everything sounds interesting,but i know just a little about linux.
can u explain us?
thanx
3lixir said:
if it works it would be interesting to see if anyone can get Maemo to work on the hd it's the same os used on the Nokia N900 and heavily based on Linux
Click to expand...
Click to collapse
That would be very nice!!
Ubuntu MID
Hi, sakkeus.
What do you thing about trying ubuntu MID edition?
Pics here:
http://www.ubuntu.com/products/mobile
It is distributed as an image file, but if you know how to install it (and which image would be the best) I can give it a try.
Images here:
http://cdimage.ubuntu.com/mobile/releases/hardy/
kingofslide54 said:
thanks, sakkeus, but when I try to launch ubuntu using your default, haret says 'couldnt find initrd'. when I remove the initrd line from the default, ubuntu boots well (excepting the screen calibration) so I think ext2 files are ok.that's why I asked.
Click to expand...
Click to collapse
Did you really get fat files from this thread second post because i just chek the default text wich is there and there in no initrd.
I think you should redownload fatfiles from second post.
kingofslide54 said:
Hi, sakkeus.
What do you thing about trying ubuntu MID edition?
Pics here:
http://www.ubuntu.com/products/mobile
It is distributed as an image file, but if you know how to install it (and which image would be the best) I can give it a try.
Images here:
http://cdimage.ubuntu.com/mobile/releases/hardy/
Click to expand...
Click to collapse
Yeah!....................
wow!
amazing!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
sakkeus11 said:
Did you really get fat files from this thread second post because i just chek the default text wich is there and there in no initrd.
I think you should redownload fatfiles from second post.
Click to expand...
Click to collapse
You're right... can't understand why, coz I downloaded the files from the phone itself and overwrote everything... I'll try again.
sakkeus11 said:
Yeah!....................
Click to expand...
Click to collapse
Yeah!!!!!
I found it looking for a good on-screen keyboard, wondering if I should code one... but this looks better
Found something than can be useful.
Once in the ubuntu desktop, if you press 'ctrl+alt+del', go to console mode and type 'exit', you go back to the calibration screen.
kingofslide54 said:
Found something than can be useful.
Once in the ubuntu desktop, if you press 'ctrl+alt+del', go to console mode and type 'exit', you go back to the calibration screen.
Click to expand...
Click to collapse
This would be useful because it maybe not go well first time.
sakkeus11 said:
This would be useful because it maybe not go well first time.
Click to expand...
Click to collapse
Well, in fact, I wasn't able to get it well till now but I'll keep trying
kingofslide54 said:
Hi, sakkeus.
What do you thing about trying ubuntu MID edition?
Pics here:
http://www.ubuntu.com/products/mobile
It is distributed as an image file, but if you know how to install it (and which image would be the best) I can give it a try.
Images here:
http://cdimage.ubuntu.com/mobile/releases/hardy/
Click to expand...
Click to collapse
I have been tried install ubuntu MID edition, but as like debian it not found install files because there is no internet connection.Needed get internet connection works or some how load install files from storage.

[Question]:zImage and modem binary swaps

I like to tweak my ROMs before a flash. i.e. make changes to /system apps; framwork tweaks... etc.
However, whenever I try to replace a kernel zImage or modem binary(using 7z, so as not open archive), I get stuck at a bootloop.
I can replace .apks and .pngs no problem using this method.
Can zImage and .bin be replaced as well? Does redbend also need to be copied? Since .bin and zImage reside in same folder in ROM... which redbend to use if needed?
Thank you?
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Exactly what Br1cK'd said. Use the redband that's with the kernel. If pulling the kernel from a rom and a modem from a different one same deal. Also be careful which kernels you use ie: right kernel for phone and version of Android.
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
No sir it is not quite that simple. Proper settings have to be in the update script for everything to install properly. Replacing one file for another of the same name usually works and some files can be added but system apps and additional folders need to be in the update script.
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
1. I believe redbend is samsung tool for flashing volatile memory (NAND).
2. You can use 7zip to explore archives/apks without extracting them and breaking signings. Thus you can simple copy paste .apks/.pngs to appropriate directories without extracting
Most update zips are the actually apk and simple scripts in a flashable container. Roman form EDT has an excellent tool for creating flashable zips if interested... but yes you can manipulate file system of phone and archives. I use adb from recovery. Or android commander is a useful tool as well
EDIT: Explodingboy gives better explanation above
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
birgertime said:
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Very cool... thanks.
Also, you are going to think I am crazy... but that ugly blue splash screen can tell me if it is a bad flash or not. When it happens on the top of screen= good flash, on bottom = gonna need to flash again, cause behavior goes wonky. Maybe just bizarre coincidence???
Poser said:
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
Click to expand...
Click to collapse
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
I have no issues doing this with winrar.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
Br1cK'd said:
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
Click to expand...
Click to collapse
<Palm to forehead> Probably should logcat... duh.
Just flashed with with custom kernel/modem combo... seems to be booting fine, will report any anomalies.
Only thing I did different was copy zImage and redbend from Kernel.zip
Thanks peoples!

[Q] Custom Boot Animation Help?

Is anyone experienced with making custom boot animations? I tried making one, following a guide, but can't seem to get it working. The problem is probably with the archive compression, though I've tried multiple methods / programs, as everything else is in order. If anyone is willing to take a look, it'd be greatly appreciated - I've uploaded it to Mediafire here: mediafire.com/?x8v3b7b0mdb7a5u
Thanks,
marie :]
Take a look at my thread although its for a particular device you just need to change the resolution for other devices
And I'll try solving your problem one I get back home
PM if you want to know anything more
im takign a look at it and will test on my device, give me a minute or two and i will pm you when i have it figured out.
edit: i sent you a PM here is the fixed .zip works fine now just put it in your devices /data/local folder
might also suggest enlarging the image some as its REALLY small on my device
NSCoyote said:
might also suggest enlarging the image some as its REALLY small on my device
Click to expand...
Click to collapse
its because the resolution is set to 480x480 in desc.txt
change it to that of your device and it'll work fine
Thank you all. NSCoyote found that the problem was a thumbs.db file within the archive. Yikes.
Thanks again.
no problem glad i could help

[TOOL] The O2x Nullifier 2.2 - Single & Dual Passes!!! P990

Hello my fellow Android crack flashers! So Volk and I have wrote(him) and tested(me) his g2x nullifier for our phones. Well it works flawlessly! Which his thread is here. So with our learning adventures he has helped me port it to the O2x. So here is the run down. This was originally created as the g2xscrubber was insufficient enough for our flashberry addiction, and on top of that if wouldn't wipe our /cache either.
So the domino effect has begun. This is a simple script that will wipe your internal partitions cleaner then a whistle and get it dam near like new status, perfectly ready for a ROM. Like as if you just purchased it and didnt have any data on it nor a ROM and needed to be flashed. And yes it came all tricked out like that with CWM and all.. haha
So here it is...
The O2x Nullifier
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats the partitions afterward, including /cache too! Enjoy!
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it. I've ran this Nullifier like 20 times in the last two days of first testing and on average its about 1204 seconds or about 19.8 minutes, on average. The Single pass zip is only half of the time of course. Or you can just watch the progress bar. After 20 times of nullifing and log pulling in 2 days, im pretty dang sure the bar is accurate. So enjoy!
2. ONCE THE NULLIFICATION PROCESS HAS BEEN COMPLETED DO NOT, I REPEAT, DO NOT TURN OFF OR LET YOUR PHONE DIE BEFORE FLASHING A ROM OR RESTORING... or you will brick your phone.
3. I will provide help, support, etc. for this, but as always flash at your own risk and I am not responsible if you turn your phone into your next non-aerodynamic frisby.
Enjoy!
Also I have now decided to copy the log to sdcard at completion (thanks to DARKSIDE for the idea). But from now on the log created in /tmp while in cwm is now copied to sdcard as O2x-Nullified-recovery.log. So it will still be deleted from RAM but never lost any more!!!!! muhahahahahahah... love it!
Thanks go to Волк aka Volk for letting me test and learn from his G2x Nullifier script. And also to owain94 for helping me make sure that this thing will run ok on the O2x, since I dont actually have the O2x..
Also if is doesn't work, please we need logs. You need to use a file explorer or put the external sdcard into your pc and grab and upload or pm me the log from your sdcard the file will be named 'O2x-Nullified-recovery.log'
mini change log:
1.2 -> fixed sleep command, 1.2
1.3 -> updated binary script and added /cache info per vadonka's advice
1.3.1 -> Bad zip... reupped
1.3.2 -> zipped with 7zip should work now.. dumb winzip... reupped
skipped to 1.5 -> updated script and binary. Also removed /cache format command; instead do a manual wipe for now
skipped to 2.0 -> updated script and binary again. Manual format still.
2.1 -> No more manual /cache wipe and working progress bar!
2.2 -> Single/Dual pass zip options. Thanks to Volk for error check and darkside for log creation idea. Added support for su660
nice work mate!
Ok so i'm hijacking this post to use while i'm at work (with crappy lowest bid PC) and using this FOR MY TEST UPLOADS ONLY. THIS WILL CONSIST OF G2X TESTS GETTING READY FOR THE O2X... DO NOT DOWNLOAD ANY ATTACHMENT ON THIS POST OR ATTEMPT TO FLASH IT BECAUSE IT WONT WORK FOR YOU UNLESS YOU HAVE A G2X!
Thanks a lot mate
da-pharoah said:
This was originally created as the g2xscrubber was not sufficent enough for our flashberry addiction.
Click to expand...
Click to collapse
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>
carburano said:
Thanks a lot mate
Click to expand...
Click to collapse
No worries
Волк said:
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>.
Click to expand...
Click to collapse
lol nice catch.. was in a hurry to leave from work. Fixed now.
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
owain94 said:
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
used win7 and notepad++
error with op link or updated link by Волк?
carburano said:
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Click to expand...
Click to collapse
Волк said:
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Click to expand...
Click to collapse
OP updated thanks again Волк!
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
hackworks said:
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
Click to expand...
Click to collapse
Well really thats kind of a longer process.. thats a rom, this is just a tool to wipe clean your internal storage. Basically take it back to like new status, but still having full root ability. CWM will flash the rom of your choice after your done with the nullification process and manual /cache wipe. This will not take you back to a predetermined state (in terms of a rom), it will leave your phone a nice paper weight however until you decide to flash a rom.
nice work!
i have a little advice for you. use this method for the cache wipe and no need to manual wipe cache anymore
unmount("/cache");
run_program("/sbin/mke2fs", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-O", "extents,uninit_bg,dir_index,has_journal", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-o", "journal_data_writeback", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
this create an ext4 partition, if you want ext3 just skip the first tune2fs row, and use the -j option in the mke2fs.
mke2fs recreate a new empty partition no need to fill with zeroes before, so the nullifying parts is unneded, just use the mke2fs. its enough, except if you want to wipe the data for reason.
I still receiving get the error message:
E: Can't Open /sdcard/O2x_Nullifier_1.2.zip (bad) Installation Aborted (Status 6)
Click to expand...
Click to collapse
What I'm doing wrong?
ev!denz said:
I still receiving get the error message:
What I'm doing wrong?
Click to expand...
Click to collapse
its because the update-binary is a bit old
use a newer update binary.
vadonka said:
its because the update-binary is a bit old
use a newer update binary.
Click to expand...
Click to collapse
How can I use a newer one?
Darn it! Ok im on my way to work.. I'll see if I can get around the limitations there an update for y'all...
Sent from my LG-P999 using xda premium
ev!denz said:
How can I use a newer one?
Click to expand...
Click to collapse
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
vadonka said:
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
Click to expand...
Click to collapse
OP updated

[MOD] [DEV] Insecure Boot Image for Nexus S on Android 4.1.1 Jelly Bean (JRO03E)

Hello everyone,
This is my first mod/hack at this level, so I am extremely excited about it. Here's some history:
I flashed the JB OTA and then started missing using adb remount. I looked around for an insecure boot image but couldn't find a JB-based one. I looked into the OTA's zip file and didn't find boot.img there so at first, I thought JB used previous ICS 4.0.4's boot.img but upon looking into updater-script from the OTA's zip file, I saw the OTA patched the existing one rather than flashing a new one.
So long story short, I extracted it from the phone, unpacked it, set ro.secure=0, repacked it and tried booting it, and it worked, so I just flashed it and have been using it for a while now.
Note that this is not for everyone, and most will not even require it but for those who do, here it is. Enjoy, and don't forget to hit the Thanks button.
Download Nexus S Insecure Boot Image for Jelly Bean (Off-site link on my blog; I have also written a guide there for those interested in learning how to flash it but if you just want to download it, skip to the end of the post to find the download link.)
What is the insecure boot?
Sent from my nexus s using xda app
Spidergio said:
What is the insecure boot?
Sent from my nexus s using xda app
Click to expand...
Click to collapse
Insecure boot image lets you use adb remount, and adb push or adb pull etc. to /system and its contents. Basically it's using ADB as root. If you don't require it, I don't recommend going for it; it's just for those who really want the convenience of these commands.
Do you happen to have a link that explains this process? I have found a couple but they never fully explained it in detail.
medizen said:
Do you happen to have a link that explains this process? I have found a couple but they never fully explained it in detail.
Click to expand...
Click to collapse
The link provided in the OP aims to do that. =) If you need further information after reading through that, feel free to ask me here.
Thanks just what I was looking for....works great!!
elamalaka said:
Thanks just what I was looking for....works great!!
Click to expand...
Click to collapse
Glad it helped =)
HQRaja said:
Glad it helped =)
Click to expand...
Click to collapse
Two questions:
1) I'm running JROO3E is it still ok to use your boot.img or does my boot.img needs to be modified? (The reason why I asked is because I got two random reboots after flashed insecure).
2) File sizes of boot.img files are different. My boot.img is 8192 kb and your insecure is 3972 kb is that a problem?
Please advise.
Thanks!!
elamalaka said:
Two questions:
1) I'm running JROO3E is it still ok to use your boot.img or does my boot.img needs to be modified? (The reason why I asked is because I got two random reboots after flashed insecure).
2) File sizes of boot.img files are different. My boot.img is 8192 kb and your insecure is 3972 kb is that a problem?
Please advise.
Thanks!!
Click to expand...
Click to collapse
1. This is the version for JRO03E (I had mistakenly typed JRO03H in the post), so it should work for yours. I am myself using it on mine, with no random reboot at all. Though as we all know, when it comes to these things, your mileage may vary. Not sure what's causing them though; you are on the international variant (soju / crespo) of Nexus S, right?
2. When you extract the boot image from the phone, it dumps the entire content of the boot partition, including the empty bytes. That's why the extracted one should be 8192 kb (or 8,388,608 bytes to be precise). Once it is unpacked, edited and repacked by the script, the empty bytes are removed when repacking. Therefore, the size of the repacked one is 3972 kb (or 4,067,328 bytes to be precise).
Hope it clears things up.
HQRaja said:
1. This is the version for JRO03E (I had mistakenly typed JRO03H in the post), so it should work for yours. I am myself using it on mine, with no random reboot at all. Though as we all know, when it comes to these things, your mileage may vary. Not sure what's causing them though; you are on the international variant (soju / crespo) of Nexus S, right?
2. When you extract the boot image from the phone, it dumps the entire content of the boot partition, including the empty bytes. That's why the extracted one should be 8192 kb (or 8,388,608 bytes to be precise). Once it is unpacked, edited and repacked by the script, the empty bytes are removed when repacking. Therefore, the size of the repacked one is 3972 kb (or 4,067,328 bytes to be precise).
Hope it clears things up.
Click to expand...
Click to collapse
Maybe the random reboot was the result of something else I did because I was testing a few apps from the market. I'm running the stock (sojua / crespoa) variant GT-I9020A. I tried to unpack/edit/repack my original boot.img but the repacked size of the file is 3964 kb and not 3972. When I try the fastboot boot <bootname.img> it says that fastboot was ok but it just hangs at the Google initial screen.
Can I send you my boot.img so that you can give it a try?
Thanks again for all your help!.
Don't bother explaining what insecure boot is, they should use search or Google it.
Which version of the boot img is this?
elamalaka said:
Maybe the random reboot was the result of something else I did because I was testing a few apps from the market. I'm running the stock (sojua / crespoa) variant GT-I9020A. I tried to unpack/edit/repack my original boot.img but the repacked size of the file is 3964 kb and not 3972. When I try the fastboot boot <bootname.img> it says that fastboot was ok but it just hangs at the Google initial screen.
Can I send you my boot.img so that you can give it a try?
Thanks again for all your help!.
Click to expand...
Click to collapse
It could be because of your phone being GT-I9020A (sojua / crespoa) rather than GT-I9020T (soju / crespo) ? Not too sure; I'm quite a noob myself and this was my very first time of doing something like this. Though feel free to send me your boot image and I'll see if I can make it work. =) Just put it on minus.com or any sharing service and DM me the link or post it here.
SamuelDebruyn said:
Don't bother explaining what insecure boot is, they should use search or Google it.
Which version of the boot img is this?
Click to expand...
Click to collapse
Heh it's OK I guess; not all of us are good at Googling or reading what's already written out there (or here, for that matter. )
About the image, it's the latest Android 4.1.1 Jelly Bean JRO03E boot image for the International Nexus S GT-I9020T (soju / crespo).
HQRaja said:
1. This is the version for JRO03E (I had mistakenly typed JRO03H in the post), so it should work for yours. I am myself using it on mine, with no random reboot at all. Though as we all know, when it comes to these things, your mileage may vary. Not sure what's causing them though; you are on the international variant (soju / crespo) of Nexus S, right?
2. When you extract the boot image from the phone, it dumps the entire content of the boot partition, including the empty bytes. That's why the extracted one should be 8192 kb (or 8,388,608 bytes to be precise). Once it is unpacked, edited and repacked by the script, the empty bytes are removed when repacking. Therefore, the size of the repacked one is 3972 kb (or 4,067,328 bytes to be precise).
Hope it clears things up.
Click to expand...
Click to collapse
HQRaja said:
It could be because of your phone being GT-I9020A (sojua / crespoa) rather than GT-I9020T (soju / crespo) ? Not too sure; I'm quite a noob myself and this was my very first time of doing something like this. Though feel free to send me your boot image and I'll see if I can make it work. =) Just put it on minus.com or any sharing service and DM me the link or post it here.
Click to expand...
Click to collapse
HQRaja:
Can't post external links just add the http stuff in fron of it.
min.us/mRk5DoUxD
Thanks!!
elamalaka said:
HQRaja:
Can't post external links just add the http stuff in fron of it.
min.us/mRk5DoUxD
Thanks!!
Click to expand...
Click to collapse
Here you go, my friend. Do lemme know if it works. =)
elamalaka said:
HQRaja:
Can't post external links just add the http stuff in fron of it.
min.us/mRk5DoUxD
Thanks!!
Click to expand...
Click to collapse
HQRaja said:
Here you go, my friend. Do lemme know if it works. =)
Click to expand...
Click to collapse
Works like a charm!!
Thanks for all your help.....great work!!
elamalaka said:
Works like a charm!!
Thanks for all your help.....great work!!
Click to expand...
Click to collapse
Pleasure. Always glad to help. =)
Thanks for this. I'm gonna run stock with a custom kernel and I needed to get rid of that nasty gradient as well. haha
chronophase1 said:
Thanks for this. I'm gonna run stock with a custom kernel and I needed to get rid of that nasty gradient as well. haha
Click to expand...
Click to collapse
Glad it helped. BTW if you are flashing a custom kernel anyway, it probably comes as a boot.img (in the flashable zip file of the kernel) and is most likely already insecure. Also, if you flash that kernel, it will likely overwrite this boot image (unless you somehow flash only the kernel and not the ramdisk. I don't really know if that works). =)
This might seem like a stupid question; is this compatible with all versions of the Samsung Nexus S?
I don't mean the 4G version, but I do mean:
the 850MHz version, the international version and the korea version
Thanks for quick answers!
EDIT: Question already answered!

Categories

Resources