Related
Hi guys!!
NEW UltraJack-Recovery 6.2.2!!Codename:Cappuccino
NO MORE BLUE SCREEN!!!!
Changelog:
FIX: Backup/restore of /cust partition (Bug present in all releases of Ultrajack -up 5.2.2 too- and Clockworkmod too!! )
Added:
mount and umount /cust partition
WIPE /cust
Amend support to CUST partition (Edify is supporting CUST alredy)
Amend/Edify are both supported! (the oldest and newest and future roms can be flashed )
New Base (RA_Recovery 2.2.2!)
FULL EXT4 support (read-write and formatting partition!)
Backup/restore menu (and scripts) updated
Backup/restore google apps
New menù colors
ADB Updated
Kernel sources Modded and compiled to solve an issue on toggle USB function
Download it now!! (6.2.2)(IMG only)
guide and zip file with fastboot binary and scripts here:
http://forum.xda-developers.com/showpost.php?p=11771509&postcount=39
If some1 liked my work and want donate me a beer (or a new micro-SD), there is the link link, or just say tnx
Thanks to:
Me, Myself and I!
Udk ( my best compiler-friend )
Maja (beta tester, and many great ideas! )
Amon_RA(this recovery was based on him RA_Recovery 2.2.1 sources, and many thx about compiling tips!)
JackTheVendicator (without his modded tools the boot.img and recovery wouldn't be possible)
Old versions:
Hi guys there was a problem on some devices with amonra 1.6.2 for the pulse mini.
The BSOD!!!! (windows like)
But now this issue has been SOLVED!!!!
NEW VERSION!!
NO MORE BLUE SCREEN!!!!
Download it now!! (4.6.2)
Changelog:
Fixed SD-MassStorage function
Fixed all Wipes!
Ext2/3/4 support
if some1 liked my work and want donate me a beer (or a new micro-SD), there is the link link
Thanks to:
Me, Myself and I!
Udk ( my best compiler-friend )
Maja (beta tester, and many great ideas! )
Amon_RA(this recovery was based on Amonra pulse mini v1.6.2, and many thx about compiling tips!)
JackTheVendicator (without his modded tools the boot.img and recovery wouldn't be possible)
UltraJack-Recovery_v2.6.1
you are f***ing great!!!
Now is the time for the dedicated section
NVM fastboot install. Nice.
I hope you don't mind but I linked this to the IDEOS group over at www.simply-android.com
THANKS!
What i should do with this .img file?
This recovery won't allow you to do a boot or system wipe. just data/cache and dalvik. If you do the wipes included you can still boot the phone afterwards...that's not a full wipe.
Just FYI.
nobreak1970 said:
This recovery won't allow you to do a boot or system wipe. just data/cache and dalvik. If you do the wipes included you can still boot the phone afterwards...that's not a full wipe.
Just FYI.
Click to expand...
Click to collapse
So are you saying this is just like Googles own recovery?
It wont actually allow you to wipe the phone like AmonRA does?
Then thats useless wouldn't you agree?
@ Ultrakiller
plz plz plzzz somebody teach me how to Flash a custom recovery like the one above for my Ideos U8150-B......
I've been all around the forums and internet ....but nothings working for me ..... im using Windows7 x86 Ult Ed .....
i've even tried 1.6.2-pulsemini-amonrarecovery Instructions for windows ......but still no luck !!!
i Even tried to Flash Image through Terminal .... but for some reason it said " Flash_image not found" .....even though the filename was accurate !!! ........
Kindly Kindly Kindly guide me through the process ..... im so frustrated now .... and im dying to try new ROMS on my Ideos .....
(Also wat ROM u think is better DjDroid's or Sudomod ??????)
Plz Help ASAP !!!!
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
stevenmirabito said:
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
Click to expand...
Click to collapse
well awesome man ....it worked this time .....u ppl are awesome !!!
GOD BLESS !!!
btw what Ideos ROM is Best in your opinion !! ????
Great, I'm glad it worked out for you!
I am currently using the stock ROM, simply because I currently see no reason to install any of the currently available custom ROMs for the Comet. As soon as someone has created a stable port of Cyanogen however, you better believe I'm going to be one of the first people on board!
Sent from my Comet using XDA App
fvckyougooglescammer said:
So are you saying this is just like Googles own recovery?
It wont actually allow you to wipe the phone like AmonRA does?
Then thats useless wouldn't you agree?
Click to expand...
Click to collapse
It has a Wipe option but it only wipes the caches it seems and not the boot and system areas.
stevenmirabito said:
Great, I'm glad it worked out for you!
I am currently using the stock ROM, simply because I currently see no reason to install any of the currently available custom ROMs for the Comet. As soon as someone has created a stable port of Cyanogen however, you better believe I'm going to be one of the first people on board!
Sent from my Comet using XDA App
Click to expand...
Click to collapse
+1
Sent from my Comet using XDA App
Nand + Ext backup doesn't work properly, an error messages with regards to :adb something .
New version done!
First post updated.
Well done!
stevenmirabito said:
How To: Flash UltraJack Recovery to your Phone (Windows/Mac/Linux)
NOTE: This is a modified version of the AmonRA recovery flashing package.
The only thing I really did was modify the .sh/.bat files and include the UltraJack Recovery.
@devilzeye793 and whoever else may be wondering: Here you go!
1. Download the attached ZIP and extract
2. Make sure you have the necessary drivers installed for bootloader mode (installing PDAnet seems to do the trick on Windows: http://forum.xda-developers.com/showthread.php?p=9861928#post9861928)
3. Boot your phone into bootloader mode (Google it, I can't list all the ways here).
4. Plug your phone into your computer and let Windows install the drivers automatically (if you're on Windows, unfortunately I'm not really sure how this happens on Mac/Linux). NOTE: On some phones (i.e. the U8150), the phone will stay on the carrier logo screen. THIS IS NORMAL!
5. Run the installer for your OS from the extracted folder (.bat file on Windows, .sh file on Mac/Linux) and let it work its magic
6. After the script has flashed the recovery image (should take ~1-5 seconds), unplug your phone and remove/re-insert the battery to get out of bootloader mode
7. Enjoy your new recovery image!
Hope this helped some people out there!
Click to expand...
Click to collapse
Can this be uninstalled? I need to send mine back so I need to get the phone back to it's original state...
I'm not an expert, but you probably need to find an IMG of the original recovery image and flash it to the phone.
Anyone have it?
Sent from my Comet using XDA App
Finally with help from people from many other forums Defy with BL7 was rooted.
For now we have no script to make it on the phone without wipe but I'm very happy that it's working.
Rooting Procedure
1. Wipe phone twice (2x make Wipe Data/Cache in stock recovery)
2. Flash 4.5.1-134 DFP-231 CN or 4.5.1-134 DFP-231 Retail.en.EU CEE (It doesn't matter what version of this two You flash but it must be the same with version from point 4).
3. Wipe again (Data/Factory Reset)
4. Flash rooted SBF 4.5.1-134 DFP-231 CN Rooted SBF Part.1, 4.5.1-134 DFP-231 CN Rooted SBF Part.2 or 4.5.1-134 DFP-231 Retail.en.EU CEE Rooted SBF
Thanks List:
- People from http://bbs.mfunz.com for ShellRoot and Rooted SBF
- coelho_ from XDA for help and translation ShellRoot procedure
- Joe31 from XDA for CEE Rooted SBF
- Math43 from XDA for links to CN Rooted SBF
- free2livefrom XDA for testing and helping with patching under linux
- and everyone who tried to help in this thread - THANK YOU
Old Post to let everyone know what we worked here.
Code:
I couldn't find any thread about rooting it and only few posts under roms threads so maybe we can start here. I was making backup of rooted DFP-231 en.EU but after this by mistake I restored 2.3.5 DFP-125 and I needed to reflash my Defy with full sbf of DFP-231 cause to make OTA I had to upgrade to BL7 so any chance to restore my backup is root full sbf DFP-231.
I was trying:
Root Tools:
- (XT800+)ROOT_MOTO_2.3.6
- Defy_2.3.6Root
- DooMLoRD_v4_ROOT-zergRush-busybox-su
- DROID 3 easy root script v7
- ME525 2.3.6 Root
- ROOT_MOTO_2.3.6
- root4defy134
- SuperOneClickv2.3.3-ShortFuse
- ZOC_FlashMasterV1.70
- unlockroot23-eng
- Motofail for Droid 4 and Razr
- SuperOneClick with new Exploit motofail hangs on 5th step
Downgrade to:
Every verion MB525, MB526, ME525, ME525+ starting from early versions of Eclair ending on DFP-2311 but only DFP-188 and DFP-231/DFP-2311 has BL7 and on all other verion phone is dead.
I was trying also modding sbf files by myself and few from Walter79 on DFP-188 thread and trying to force reflash under stock recovery but unfortunately still no luck and every time I had bootloader error or just dead phone.
From last few days I'm monitoring all German, Chinese, Spain and Russian forums about rooting this but still even no clue.
Only thing I learn is that every tool for root has problems with writing su app to phone so I think script to make it is wrong but I'm new in android and I have no idea how to edit it. I tried superuser under Ubuntu 11.04 also but I couldn't mount phone so another fail.
I'm screwed with BL7 so if someone have some ideas I'm opened for most options.
are you try this ...3 link attached from xda http://www.android-hilfe.de/2729429-post10.html
All tries to repack and pack back sbf ending with bootloader error.
and if you flash the su zip http://www.android-hilfe.de/2742491-post20.html
Signature Verification failed. Walter79 posted recovery from 4.5.1-134-DFP-74 for root with stock recovery but bootloader error after flash.
Someone (walter79 I think) was talking of a tweaked sbf that could do the trick. Basically to create this you need to
1) unpack the bl7 sbf to a folder and get cg39.smg.
2) Mount cg39.smg as ext4 in ubuntu (sudo mkdir /mnt && sudo mount cg39.smg /mnt -o loop).
3) Now place su binary(su) in /mnt/xbin and Superuser.apk in /mnt/app (To find these files look inside superonclick zip archive)
5) Set perm (sudo chmod +x /mnt/xbin/su)
6) Unmount (sudo umount /mnt)
7) Repack sbf.
8) Flash your phone with new sbf using Rsdlite
9) See if it's booting, if yes, let us know.
10) If no, reflash orginal sbf again.
Find most tools you need here : http://forum.xda-developers.com/showthread.php?t=966537
Ok, I'll try it and maybe it gonna work but I'm afraid that bootloader error shows after repacking sbf.
Chamelleon said:
Ok, I'll try it and maybe it gonna work but I'm afraid that bootloader error shows after repacking sbf.
Click to expand...
Click to collapse
If this fails with bl error it means that bl7 somehow checks the patency of mmcblk1p31 during boot. If that's the case then rooting these new sbf will be very very very difficult.
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
Edit : use motoandroidepacker 1.3 from http://and-developers.com/sbf
royale1223 said:
If this fails with bl error it means that bl7 somehow checks the patency of mmcblk1p31 during boot. If that's the case then rooting these new sbf will be very very very difficult.
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
Edit : use motoandroidepacker 1.3 from http://and-developers.com/sbf
Click to expand...
Click to collapse
Hi.
Yes it is like this,i tried a things above, the result is boot err.
Tried, mount CG39.smg (no moding) umount than flash, Bootloader err.
I could try 1 more thing, from rooted telephone (bl7) you can pull CG39.smg by ADB.
adb shell:
su
dd if=/dev/block/system of=/sdcard/CG39.smg
Edit this, than flash.
Thanks
Ok, I did what You said and used files from superuser site (bin su ofc) and unfortunately Bootloader error Err:A5,69,35,00,27 and after simple repack and build again without modification CG39.smg phone booting normally.
Joe31 said:
I could try 1 more thing, from rooted telephone (bl7) you can pull CG39.smg by ADB.
adb shell:
su
dd if=/dev/block/system of=/sdcard/CG39.smg
Edit this, than flash.
Thanks
Click to expand...
Click to collapse
Sorry but I don't understand what You just said cause I'm on Ubuntu from yesterday and it's my first contact with this system and to do thing with modding CG39.smg I needed to google how to copy something in Linux console so please explain steb by step what to and I'll try it if You can't.
Chamelleon said:
Sorry but I don't understand what You just said cause I'm on Ubuntu from yesterday and it's my first contact with this system and to do thing with modding CG39.smg I needed to google how to copy something in Linux console so please explain steb by step what to and I'll try it if You can't.
Click to expand...
Click to collapse
you can always go back and get your phone work with flashing this http://115.com/file/e7z2d0jd
it's a bl7
Chamelleon said:
Sorry but I don't understand what You just said cause I'm on Ubuntu from yesterday and it's my first contact with this system and to do thing with modding CG39.smg I needed to google how to copy something in Linux console so please explain steb by step what to and I'll try it if You can't.
Click to expand...
Click to collapse
It is only for people who have rooted phone.
Please who has rooted phone, help. (OTA update)
ADB:
Download sdk:LINK
http://www.change.org/petitions/motorola-mobility-inc-unlock-all-smartphone-bootloaders-2#
coelho_ said:
you can always go back and get your phone work with flashing this http://115.com/file/e7z2d0jd
it's a bl7
Click to expand...
Click to collapse
Not work!
Black screen!!
Ofc it's not working, it's bl6 file and if u flash it on BL7 it's like reflash DFP-231 with any other lower version except DFP-188.
Chamelleon said:
Ok, I did what You said and used files from superuser site (bin su ofc) and unfortunately Bootloader error Err:A5,69,35,00,27 and after simple repack and build again without modification CG39.smg phone booting normally.
Click to expand...
Click to collapse
Just to confirm : Did you use MotoAndroidDepacker 1.3? If it was MAD 1.2x, please repeat the steps with MAD 1.3.
I could see that you used a control to verify if depacker is working properly. That's smart. You could also try this: make a new sbf that only contains the modified cg39.smg. Delete other smg after depackin. Make sure that you use MAD 1.3. Good Luck.
OFC I did all on MAD 1.3 but I think that problem isn't in content of package but modding CG39 cause after rebuilding clean sbf everything working fine and as someone said after only mount and unmount CG39 without modding bios shows error.
Hi, new update for T-Mobile DFP-188 shows up and it's available here but already edited by uploader. I didn't installed it but I downloaded it and tried to modify it by myself. Added su, Superuser.apk and busybox from root4defy134 and added permissions for update script under rest of bin permissions but ofc after trying flash it by stock recovery, recovery shows error at verification. So maybe someone have any idea how to modify it to add root files and update?? Or maybe there isn't any chance to do it??
I want to talk about his attempt to gain root access. I have a PC installed eclipse and android SDK. If you try to copy any file in the System folder at once shows the error (read only filesystem). Today I tried to use the Kindle Fire Utility. Now, almost enable to copy the file to the section of System (ie it is copied by 99% and then gives an error). It seems to me that it might somehow help.
http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.3.zip
Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)
Now I am stuck @ finding a proper file host to upload the files.
waiting for this!
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.
Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2
UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.
Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.
So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Nice work! Thanks!
Sent from my GT-I9103
nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.
This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts
So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app
special thanks to rrileypm at freaktab.com
Pipo updated their stock firmware for the U8 on 8/22/2013. This new ROM is based on this firmware.
It is:
Rooted
Debloated
English set as default language
Google Play Store fixes added
Init.d support added
Busybox commands added
tun.ko added for VPN support
Thanks to Tattman65 for the boot animation
Thanks to Finless for the flash tool
Thanks to Fun for the generic CWM Recovery
Thanks to Pr0xZen for the First Time User's Guide
You might notice some things are different in the ROM kit.
1. I included the Rockchip Batch Tool as an alternative for resetting you tablet into flash mode. You can also use this tool to flash the stock ROM if you need to, for some reason.
2. I also included a template for you to build your own CWM flashable ROM. There is a readme file in that folder that tells you how it's done. I would not recommend changing to a different ROM using this feature, it is just a way to re-flash this ROM without having to use PC. You can't change parameter settings through CWM.
3. The default recovery.img is stock recovery. As an option, I included the generic version of CWM Recovery...you can flash it instead of the stock recovery by just renaming the files...recovery.img to stockrecovery.img and cwmrecovery.img to recovery.img before flashing.
Enjoy!!!!!!
Download :good:
I would like to install CM7 alpha9 MTD from this thread http://forum.xda-developers.com/showthread.php?t=2309390
The process I imagine is as following:
- backup things (I'm not sure how exactly this part works, if you know how to backup application data please help)
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar kernel with ODIN without repartitioning (as PDA I'm guessing, unless there's an option for "kernel" in which case it's kernel, which one is it? )
- boot to recovery
- format /system, /data, /preload
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- install SuperSU ? is this necessary with CM? Although I have doubts, as it was never mentioned unlike for Omni, so I guess not for this one
- reboot phone
- enjoy CM7
So basically I'm asking, am I missing out on anything basic but important that would result in bricking? And
- how to backup application data to be retrieved after flashing
- is the kernel a "PDA" or is there another thingy for it in Odin that needs be done?
- do you need to install any previous versions of CM7 for this MTD thing to work?
- does the kernel provide a recovery with which this ROM can be installed?
If you managed to get to the end, thank you - And thanks in advance for the help
Installing a rom
Zhuinden said:
I would like to install CM7 alpha9 MTD from this thread http://forum.xda-developers.com/showthread.php?t=2309390
The process I imagine is as following:
- backup things (I'm not sure how exactly this part works, if you know how to backup application data please help)
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar kernel with ODIN without repartitioning (as PDA I'm guessing, unless there's an option for "kernel" in which case it's kernel, which one is it? )
- boot to recovery
- format /system, /data, /preload
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- install SuperSU ? is this necessary with CM? Although I have doubts, as it was never mentioned unlike for Omni, so I guess not for this one
- reboot phone
- enjoy CM7
So basically I'm asking, am I missing out on anything basic but important that would result in bricking? And
- how to backup application data to be retrieved after flashing
- is the kernel a "PDA" or is there another thingy for it in Odin that needs be done?
- do you need to install any previous versions of CM7 for this MTD thing to work?
- does the kernel provide a recovery with which this ROM can be installed?
If you managed to get to the end, thank you - And thanks in advance for the help
Click to expand...
Click to collapse
Reboot to recovery, make a backup (you'll find in the menu)
Make a full wipe(in recovery)
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar
Install all these 3 zip with One Package ticked
Reboot and enjoy
Good luck
to install CM7 alpha 9 MTD you first need to be running CM7 alpha 9, which you flash with ODIN http://forum.xda-developers.com/showpost.php?p=14240212&postcount=1
then follow the instructions in the previous reply from sakenas to update to CM7 alpha 9 MTD using clockwork mod recovery.
only flash the 1ghz kernel after you have updated to CM7 alpha9 MTD.
you flash the kernel with ODIN using the one package method, exactly the same way you will have flashed CM7 alpha 9.