Related
Any one know command to mtty for atom exec\orsio n725 or RoverPC G5.
Phone connect to pc by rs-232, standart command not work
PS sorry for my english
Sorry, just want to understand further, why you using a serial cable (RS-232) to connect to your PC. is your phone hanged at bootloader mode?
Winterice said:
Any one know command to mtty for atom exec\orsio n725 or RoverPC G5.
Phone connect to pc by rs-232, standart command not work
PS sorry for my english
Click to expand...
Click to collapse
mtty is made for HTC devices. Atom is made by Quanta. I've been looking for the same tool myself. have you tried putty? If I'm not mistaken, you are trying to reformat the DOC? or upgrade the device thru mtty?
I have looked into the things we can upgrade from SDCARD flashing, and DOC.IMG is one of the option. I think this will change the format of DOC. One way to get a copy of this DOC.IMG is to dump the ROM thru SDCard using buzz romdumper64.
Please let me know of your developments.
Phone in bootloader, i am try dump rom. if plug phone with USB mtty doesn't see phone. if use command 'r' phone write message Format DOC.OK
Sorry for my English.
This experiments with the MTTY.
This experiments to copy ROM to the SD card or file.
I'm Running MTTY.
connecting PC and the Rover G5 (Atom Exec/Orsio N725), using a serial cable (RS-232).
Run bootloader mode.
On the PC screen :
-----------------
*******Beginning System Initialization*******
Run Mode = 104 MHz
Turbo Mode = Run Mode
MemClk = 104 MHz
Bus Mode = NORMAL
SDCLK[1] = MemClk (SDRAM Clk)
SDCLK[0] = MemClk/2 (Sync. FLASH Clk)
Mode = RUN
Boot FLASH in Asynchronous mode
******************************************************
OEMInitDebugSerial using STUART888
Microsoft Windows CE Ethernet Bootloader built Jun 13 2006 20:41:44
Copyright © 2006 Microsoft Corporation
Portions copyright © 2006 Intel Corporation
Original MSC0 12801282
New MSC0 12807FF2
New MDREFR = 0x11E018
New SXCNFG 40044004
Flash type L18
main:InitDisplay()
InitLCDCtrl..
ClearFrameBuffer..0xA6000480
+Check LCM ID:
==PreBL_Ver = 0.0.0
==2nd_BL_Ver = 0.0.0
Ethernet Boot Loader Configuration:
0) IP address: 0.0.0.0
1) Subnet mask: 0.0.0.0
2) # bootme's: 0
3) Boot delay: 0 seconds
4) DHCP: Disabled
5) Reset to factory default configuration
6) Launch existing flash resident image at startup
7) Program RAM image into FLASH (Disabled)
8 ) Program SMSC MAC address
9) Boot device order: SMSC -> PCMCIA S0 -> PCMCIA S1
D) Download image now
E) Erase flash image
L) Launch existing flash resident image now
U) Download os image now (USB1.1)
O) Overwrite eboot image now (USB1.1)
H) Jump to DM
I) Sim Lock
------------------
But ...
There are undocumented commands.
If press "R" - a message on the screen
Formating DOC.
OK
So there are undocumented commands
we are interesting other command
It would help us if we get hold of Service Manual.
Winterice said:
Phone in bootloader, i am try dump rom. if plug phone with USB mtty doesn't see phone. if use command 'r' phone write message Format DOC.OK
Click to expand...
Click to collapse
Have you tried buzz grab_it ROM dumper? it worked perfectly well with the Atom. It dumped everything to SD Card. You just have to break it apart and identify the sections.
For the Atom:
diskimg.nb0
eboot.nb0
dm.nb0
flash.img
agent.mot
mot.mot
cpld.img
assetinf.img
extended.img
MDOC.img
what particularly interest me is MDOC.img because I believe we can change DOC format with this.
our device have 192 mb rom, i or Alex_beda try this dumper today
This dumper not working.
Message in the screen "cannot create file!"
Using the miniSD 2 GB Kingmax
May be need to use mini SD less 1 GB?
Or using any other dumper?
alex_beda said:
This dumper not working.
Message in the screen "cannot create file!"
Using the miniSD 2 GB Kingmax
May be need to use mini SD less 1 GB?
Or using any other dumper?
Click to expand...
Click to collapse
you have to modify the name of SDCard. It is named "memory card" in your device. the program looks for "Storage Card". Search this value using registry editor.
"Folder"="\Storage\Card"
jiggs said:
you have to modify the name of SDCard. It is named "memory card" in your device. the program looks for "Storage Card". Search this value using registry editor.
"Folder"="\Storage\Card"
Click to expand...
Click to collapse
Thank you!
I'm downloading dump in the miniSD card.
But...
Problem.
Dump size 128 MB maximum
ROM size in my divice 192 MB.
How downloading full size (192 mb)?
alex_beda said:
Thank you!
I'm downloading dump in the miniSD card.
But...
Problem.
Dump size 128 MB maximum
ROM size in my divice 192 MB.
How downloading full size (192 mb)?
Click to expand...
Click to collapse
Your ROM chip size is 192MB. BUT I think, your ROM system size is only 64mb. Same as ATOM. The rest is only persistent storage, extended partition, and checksum partition.
to verify, you can pdocread the memory layout of your device. don't forget to install the RAPI before pdocread; otherwise, it will not work.
my ELF's mac address may be lost
every times, when my elf restart,
a document named HTCExcpthLog_mmdd_hhmmss.txt will be build in SDcard at \storage card\HtcLog\
mmdd_hhmmss is the restart time.
Fix:
- Input Types: (注音) + (倉頡) + (手寫) + (全螢幕手寫) works with no doubt
- relpllog.exe error exixts if 手寫(mboxcht.dll) is called, i dunno why, have checked so many versions from ATOM LIFE to ATOM AKU2.2....still finding. But I think 全螢幕手寫 is good enough.
- Finally I am able to change the program links in the initflashfiles.dat to unicode 16
- SMS issue: If you have SMS issue, please go to phone - options - service and check the SMS default gateway number, for HK it is +8536800852 somewhat like that, just change it to the number your operator provided.
Programs added:
- Total Commander
- Regedit
- pBar
- 1 extra IME is hidden (CHS 併音), a registry hack need to apply in order to activate this IME
Download Link: http://www.mediafire.com/?ffklanjl2gy
Missing eBoot.nbo: http://www.mediafire.com/?1xrxmtlymrz
If you do not want a CHT version WM6 but wanna have CHT input, check this: http://forum.xda-developers.com/showthread.php?t=332012
Version:
Windows Mobile 6 Professional AKU0.3.0
CE OS 5.2.1413(17913.0.3.0)
NEVER ATTEMPT TO FLASH WM6 USING SD CARD FLASHING!!!
Upgrade Procedure:
1. just extract the rar file and flash you phone in BOOT LOADER MODE!!!
Congratulations!!! Great stuff.
Anybody know whats happen with me?
Atom show
Mar 29 2006
CPLD Ver:A0060109
.
.
.
Downloading progress:100%
Usb Transfer Completed
Write Bootloader...
Please wait...
I reflash Xda-Atom-CHT-20060426-MOT0822 and its worked(Thanks God)
Goodbye WM6..
How about atom exec?
Would that be released soon as well?
help ~....
nthan said:
Anybody know whats happen with me?
Atom show
Mar 29 2006
CPLD Ver:A0060109
.
.
.
Downloading progress:100%
Usb Transfer Completed
Write Bootloader...
Please wait...
Click to expand...
Click to collapse
i faced the same problem too ~!oh my god ~! ~!~ some more i can't open my atom now ~! ? jst the screen show up update utility `!??? isn't it the rom spoil d ?~!~? help me pls ~! ........
Guys....
the rar file consists of 6 files:
- (268,288)7zr.exe
- (258,048)Device Software Update Utiltity.exe
- (65,536,012)diskimage_Ver.nb0
- (16,384,000)ExtendedROM.img
- (110,261)nova_pda_033105.mot
- (6,022,611)vl1d_pda_Ver.mot
- (524,288)eBoot.nb0 - http://www.mediafire.com/?1xrxmtlymrz
If one of these files are missing / corrupted, the upgrade / flash will failed.
Here are the size the dump screen
dcoloane said:
Guys....
the rar file consists of 6 files:
- (268,288)7zr.exe
- (258,048)Device Software Update Utiltity.exe
- (65,536,012)diskimage_Ver.nb0
- (16,384,000)ExtendedROM.img
- (110,261)nova_pda_033105.mot
- (6,022,611)vl1d_pda_Ver.mot
If one of these files are missing / corrupted, the upgrade / flash will failed.
Here are the size the dump screen
Click to expand...
Click to collapse
Hi dcoloane
It seems the CHT input doesn't compatible with the WM6 WWE version so is possible to rip the original CHT handwriting file to be cab let us try this ????
Or just translate the CHS 0.4 to CHT is much faster to solve the problem ?
dcoloane said:
Guys....
the rar file consists of 6 files:
- (268,288)7zr.exe
- (258,048)Device Software Update Utiltity.exe
- (65,536,012)diskimage_Ver.nb0
- (16,384,000)ExtendedROM.img
- (110,261)nova_pda_033105.mot
- (6,022,611)vl1d_pda_Ver.mot
If one of these files are missing / corrupted, the upgrade / flash will failed.
Here are the size the dump screen
Click to expand...
Click to collapse
i think this folder must have eboot.nb0 to completed rom-update
Missing eboot.nbo
tube216 said:
i think this folder must have eboot.nb0 to completed rom-update
Click to expand...
Click to collapse
You are correct.......................sh.......there are too many versions in my PC now and I forgot to dump a eboot.nbo to the rar file!
That's why.................thank you tube216.........
Sorry guys, mmmmissing the most important file for eBoot
http://www.mediafire.com/?1xrxmtlymrz
*Updates*
Added ROMs & updated Links and Q&A - 21/04/2012
Updated Links - 16/04/2012
Now is possible to downgrade Nokia bootloader to Qualcomm one on the Lumia 710 More Info - 15/04/2012
Questions & Answers
Q: I've a Lumia 800 or 710 can I Interop-Unlock it?
A: The short answer is yes if you have a Lumia 710 - you must firstly downgrade your bootloader - and "maybe" for the Lumia 800, because only some of them can be Interop-Unlocked at the moment.
Q: I've got a Lumia 710 how can I downgrade my bootloader to the Qualcomm one?
A: You must flash this firmware with Nokia Care Suite (mirror splitted in two parts: Part1 Part2)
Q: Cool how can I discover if I'm a lucky owner or not?
A: For first go to "Settings -> About -> more info" and if your "Hardware revision number" ends with 2.4 you are probably screwed out.
Q: I've got 2.4 hw rev how can I check eventually?
A: You don't need to check if your hw rev is 2.4 and your Lumia came with firmware 11500 or higher you have the new nokia bootloader.
Q: I've got 2.3 hw rev how can I check if I'm eligible?
A: If you've got hw rev 2.3 but you have flashed your device with a firmware 11500 or higher - flashed mean with Nokia Care Suite because Zune doesn't update your bootloader - you have the new Nokia Bootloader; if you want eventually to check see below "check if my device is interop-unlockable".
Q: So at the moment which can be interop-unlocked?
A: As for now can be interop-unlocked hw rev 2.3 with firmware version 11141 or below.
Q: I've got the NOKIA DLOAD can I put the Qualcomm bootloader?
A: Yes but ONLY if you have a Lumia 710, on the 800 is not possible at the moment.
Q: Can I get the Qualcomm bootloader by downgrading my Lumia ?
A: No, you can't flash the Qualcomm bootloader with a backup, as explained here.
Q: I have interop-unlocked my Lumia but now I can't access Windows Live services!
A: You can find your solution here.
Q: I've got the NOKIA DLOAD how can I flash my device?
A: You can ONLY flash your device with Nokia Care Suite.
Q: I've got the Qualcomm bootloader how can I flash my device?
A: You can ONLY flash your device with Qualcomm QPST.
The Story so far: Nokia Interop-Unlock plus bootloader and NAND access
As many of you may have seen our beloved user biktor_gj found firstly that some Lumia 800 and 700 have Qualcomm unlocked bootloader that expose the entire nand of the device as removable media and permit to read write it. This discover lead to make custom rom as you can easily write raw data back to the NAND with dd linux - or any unix like variant - with the modifications for gaining Interop-Unlock.
As for now we have a tested Lumia 800 Rom that lead us to a Interop-Unlocked Lumia 800, pay attention that the devices, as stated Heathcliff74 here, is not fully rooted and need more patching.
Check if my device is Interop-Unlockable
Shut down your device
Hold pushed VOL + and POWER
Plug into your USB, you will hear a short vibration
If you are running Windows it will ask to format an USB drive, say no!
if you are running Linux you will se something like this:
Code:
[ 655.912077] usb 2-2: new high speed USB device number 9 using ehci_hcd
[ 661.797096] usb 2-2: USB disconnect, device number 9
[ 765.836050] usb 2-2: new high speed USB device number 10 using ehci_hcd
[ 765.968707] usb 2-2: config 1 has an invalid interface number: 20 but max is 1
[ 765.968713] usb 2-2: config 1 has no interface number 1
[ 766.869700] usbcore: registered new interface driver uas
[ 766.905673] Initializing USB Mass Storage driver...
[ 766.905816] scsi2 : usb-storage 2-2:1.20
[ 766.906108] usbcore: registered new interface driver usb-storage
[ 766.906110] USB Mass Storage support registered.
[ 767.906264] scsi 2:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 767.964504] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 767.968542] sd 2:0:0:0: [sdb] 31047680 512-byte logical blocks: (15.8 GB/14.8 GiB)
[ 767.969066] sd 2:0:0:0: [sdb] Write Protect is off
[ 767.969069] sd 2:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 767.970061] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 767.977005] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 >
[ 767.977264] sdb: p9 size 30632075 extends beyond EOD, enabling native capacity
[ 767.983196] sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 >
[ 767.983463] sdb: p9 size 30632075 extends beyond EOD, truncated
[ 767.988075] sd 2:0:0:0: [sdb] Attached SCSI removable disk
then you can Interop-Unlock your Lumia with one of the following ROM:
Lumia 800: Interop Unlock (no full unlock yet)
ROM based on: RM819_059P453_1600.2487.8107.12070_002
Mediafire folder access: http://www.mediafire.com/?kknt4lnc3tn7w
http://www.mediafire.com/download.php?yx44fkyfgu41yne
http://www.mediafire.com/download.php?86qevy94hm0zrsa
http://www.mediafire.com/download.php?vdbyehr99i7dirq
http://www.mediafire.com/download.php?47d57h9avew1bxa
Lumia 710: Interop Unlock (no full unlock yet)
ROM Based on: RM803_059N2L6_1600.3015.8107.12070_010
Mediafire folder access: http://www.mediafire.com/?9z6og65ozgrnr
http://www.mediafire.com/download.php?d3bj3dkfbffbakn
http://www.mediafire.com/download.php?l35zjaebdrsm315
http://www.mediafire.com/download.php?ys5bapu8ubezybo
http://www.mediafire.com/download.php?tnadd4uuoxhatv3
CAUTION: these images AREN'T TESTED. Use at your own risk.
PLEASE DO A FULL BACKUP OF THE NAND BEFORE PLAYING AROUND
if you want to flash this is the procedure on linux:
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone:
Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate.
After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds.
This will trigger the hard reset.
If when you plug your device and you see NOKIA DLOAD for now your out of luck because your bootloader is locked and you can't flash the roms above.
Lumia 710 & 800 ROMs
Full Unlocked ROM for Nokia Lumia 710 by lucifer3006:
Direct: http://xdafil.es/Lumia710/ROM/full-unlock-os-new.nb
Zipped: http://xdafil.es/Lumia710/ROM/Zipped
Full Unlocked ROM for Nokia Lumia 800 by biktor_gj:
Direct Link: http://xdafil.es/Lumia800/ROM/full-unlock-os-new.nb
Zipped Files: http://xdafil.es/Lumia800/ROM/Zipped
Qualcomm Disk layout
Completed the file uploads: http://www.mediafire.com/?kknt4lnc3tn7w
Dump_in_parts.part*.rar : Dump of the OS partition (IMGFS dump)
Dumpmap-imgfsobjects.zip: logs and stuff from OSBuilder
sd*.rar: compressed DD dumps of the rest of the filesystem
NOT INCLUDED:
Partition #5: contains product code and stuff from phone, 64kb
Partition #4: Extended partition container for partitions 5-9
Partition #9: Cannot post that enormous partition, 15Gb in size (but should be enough with the dumped os).
LUMIA 800 FLASH FILE SYSTEM LAYOUT:
Partition Begin End Blocks ID
/dev/sdb1 * 1 1000 500 4d Initial Bootloader - SECBOOT
/dev/sdb2 1001 4000 1500 46 Second stage loader? - OSBL, also looks like it has the download mode and seems to init LCD, enable USB etc.
/dev/sdb3 4001 304000 150000 c W95 FAT32 (LBA) - Writable partition with EMMCBOOT, AMSS etc.
EMMCBoot is responsible for loading Windows Kernel (nk.exe). I got a copy of Samsung Galaxy i9001's emmcboot.mbn, and putted it in there. It tries to start, but seems to crash (expected). But hey! it tries to boot it (it even vibrates for 1/10 of a second), so getting something else (did anyone say...android?)running on this phone should be easier than in lots of other phones... Does anyone have u-boot ports for Qualcomm 8255?
/dev/sdb4 304001 31037579 15366789+ 5 Extended partition which holds the OS
/dev/sdb5 304006 304133 64 ef EFI (FAT-12/16/32) - Linux detects it as an EFI partition, but it's just 64Kb size, and seems to have some markers, not sure yet what it is, but could be anything from IMEI and simlock to an actual efi partiton for WinCE...
EDIT AGAIN: this partition contains phone serial number and product code, and possibly imei and simlock. For sure its not an efi partition
/dev/sdb6 304134 310277 3072 58 3Mb size
/dev/sdb7 393216 399359 3072 4a 3Mb size
/dev/sdb8 399360 405503 3072 4b 3Mb size
These three partitions have similar start and end data on their partitions, no idea what they are, since I haven't been able to see if it's even a file system. All the documentation I see seems to tell Windows Mobile uses exFAT for the filesystem, but can't seem to find its header anywhere on the flash... still looking. It could even be where WinMo stores application installers for first boot on the device (but could be perfectly wrong)
All of them start with the following header (hex):
7D 8D 27 82 D7 40 F8 90 53 22 82 43 6D EC 6F 69 49
/dev/sdb9 524288 31156362 15316037+ 48
This las partition is 15Gb size, and contains all the Operating System and all the data on the phone.
Anyone know about how does Windows Phone manage filesystems on NAND? Some help would be really appreciated...
The file system for the 15Gb partition has _wmstore header, still incompatible with some kitchens, but still looking...
Here's part of the header:
Code:
_wmstore
!zLH?k
_wmpart_B
_wmpart_S
_wmpart_S
_wmpart_N
_wmpart_U
_wmpart_D
_wmpart_I
_wmpart_P
_wmpart_U
PSBdX
GFCB
SRPX
LK Bootloader for Lumia
beldi setupped a git repo of LK Android bootloader for Lumia devices here
Code:
*** Compiling the LK Android bootloader ***
** Tested on Ubuntu 11.10 with Lumia 710 **
1) Get the toolchain and install:
wget https://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
sudo tar xvf arm-2009q1-203-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 --directory /opt/
2) Compile the bootloader:
PATH=/opt/arm-2009q1/bin:$PATH TOOLCHAIN_PREFIX=arm-none-linux-gnueabi- PROJECT=msm7630_surf make EMMC_BOOT=1
3) Get your Lumia into diagnostics mode (turn it on using VOL UP + VOL DOWN + POWER)
4) BACKUP EVERY SINGLE FILE FROM THE 150MB PARTITION! (Just to be safe)
5) Replace the image/emmcboot.mbn file with your freshly compiled LK bootloader
cp <repo dir>/build-msm7630_surf/EMMCBOOT.MBN /media/<mount point>/image2/emmcboot.mbn
6) Unmount the bootloader partition from your PC and pull the phone's battery
7) Turn on, wait a few moments, and plug the phone to the PC
8) Test the fastboot connection:
fastboot devices
fastboot getvar version
for now is working only the fastboot protocol but nothing more, is in current alpha stage.
For ANY NON TECHNICAL question please post here instead of posting into the dev thread.
Links.
NAND access + InteropUnlock for Lumia 710 & 800 Dev Thread ONLY tech posts.
Unlocks explained by Heathcliff74Here
Qualcomm Product Support Tool (QPST™) 2.7 Here
Nokia.WIndows.Phone.Test.Introduction: Here
OSBuilder V 1.4.205 (16.04.2012) : Changelog & Download
i have lumia 710 qualcomm.
I have updated twice via NCS before gettiing a qualcomm bootloader. Just downloaded 12050 firware ang later i wasnt able to update via NCS.
I performed a nund backup. But i'm afraid to flash rom. One 710 was killed, i dont want to have the second. Will wait for the tested rom and then flash.
Done the procedure, strange that mine shows nothing at all....it's just straight up blank screen after the short vibration, then does the standard vibrate and boots like normal. No sign of Qualcomm or Nokia DLOAD....
To mention, running Windows 8 CP.
I think you can put in the first post :
Q : I have Nokia DLOAD, how can I get the Qualcomm bootloader ?
A : For now, you can't.
Q : Can I get the Qualcomm bootloader by downgrading my Lumia ?
A : No, you can't.
updated with questions and answers! thanks x3n0n.
Can a mod sticky if judge it fine?
sHaHiN786 said:
Done the procedure, strange that mine shows nothing at all....it's just straight up blank screen after the short vibration, then does the standard vibrate and boots like normal. No sign of Qualcomm or Nokia DLOAD....
To mention, running Windows 8 CP.
Click to expand...
Click to collapse
If nothing is showed and nothings happens you have a nokia locked bootloader, if not you would have be prompted by a "format USB drive".
suzughia said:
If nothing is showed and nothings happens you have a nokia locked bootloader, if not you would have be prompted by a "format USB drive".
Click to expand...
Click to collapse
Just to let you know, easiest way of doing it, as mentioned by JaxBot is to switch off phone, hold volume + and volume -, the first vibration, plug in USB.
For Windows users and Noobs like me, easiest way to check, is to go to Computer Management > Device Manager > other devices, check that when you connect the USB.
My lumia have revision number 2.3 and 12070 firmware. i updated my phone using Zune. but i still have nokia DLOAD when pressing Volume UP+DOWN and connect it to USB. according to the Q&A :
If you've got hw rev 2.3 but you have flashed your device with a firmware 11500 or higher - flashed mean with Nokia Care Suite because Zune doesn't update your bootloader - you have the new Nokia Bootloader;
Click to expand...
Click to collapse
it means, even i updated my lumia via Zune, my Bootloader have been updated to the new one. am i correct? because it showed Nokia DLOAD when i am connecting the phone. :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
suzughia said:
Q: I've got 2.4 hw rev how can I check eventually?
A: You don't need to check if your hw rev is 2.4 and your Lumia came with firmware 11500 or higher you have the new nokia bootloader.
Click to expand...
Click to collapse
I have HW Rev 2.4 and firmware 11451 which i get through zune and i still got the nokia dload
I have my lumia 710 with revision 2.1
I had a locked bootloader, but I have unlocked it while flashing 12050 firmware with NCS. Really interesting
---------- Post added at 01:17 PM ---------- Previous post was at 01:05 PM ----------
http://narod.ru/disk/45935058001.2aaca38c9acf622332f4a81b5bf0e331/RM-803.rar.html
the same files but uploaded to mediafire:
file 1: http://www.mediafire.com/?79z739zzf5cuhxa
file 2: http://www.mediafire.com/?6fed8oaz87j9ln9
.not sure, but I think I've flashed my lumia 710 with this firmware and had unlocked my bootloader
saud__19 said:
I have HW Rev 2.4 and firmware 11451 which i get through zune and i still got the nokia dload
Click to expand...
Click to collapse
Hw rev 2.4 seems to have locked bootloader either on firmware below 11150
xorizont said:
I have my lumia 710 with revision 2.1
I had a locked bootloader, but I have unlocked it while flashing 12050 firmware with NCS. Really interesting
---------- Post added at 01:17 PM ---------- Previous post was at 01:05 PM ----------
http://narod.ru/disk/45935058001.2aaca38c9acf622332f4a81b5bf0e331/RM-803.rar.html
.not sure, but I think I've flashed my lumia 710 with this firmware and had unlocked my bootloader
Click to expand...
Click to collapse
Can you post your product code that you flahed so we can grab it from nokia care? are sure of your status?
My product code is 059M5Z4.
you see, this firmware was uploaded to navifirm, 3 days later deleted and new version esp uploaded. Try downloading the file, that I linked
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
And yes, I'm sure that my bootloader is unlocked. When I enter Qualcomm mode windows 7 wants to format it. And with Linux I gad grabed a nand backup
can you attach some pics?
suzughia said:
can you attach some pics?
Click to expand...
Click to collapse
here they are.
I'll flash that Lumia 710 firmware over my Lumia 800 to change the firmware then.
Then I'll flash a standard Lumia 800 firmware (minus bootloader) over that.
Should work right?
Are you sure your bootloader was actually locked (DLOAD) before?
Not all Lumia 710 firmwares have the new bootloader. So you could have flashed the new 12050 and it wouldn't have changed your existing bootloader (keeping it unlocked).
xsacha said:
I'll flash that Lumia 710 firmware over my Lumia 800 to change the firmware then.
Then I'll flash a standard Lumia 800 firmware (minus bootloader) over that.
Should work right?
Are you sure your bootloader was actually locked (DLOAD) before?
Not all Lumia 710 firmwares have the new bootloader. So you could have flashed the new 12050 and it wouldn't have changed your existing bootloader (keeping it unlocked).
Click to expand...
Click to collapse
i've flashed twice with NCS, so i think it was closed
if pics in previous post cant be opened, here the zip file with it
xorizont said:
I have my lumia 710 with revision 2.1
I had a locked bootloader, but I have unlocked it while flashing 12050 firmware with NCS. Really interesting
---------- Post added at 01:17 PM ---------- Previous post was at 01:05 PM ----------
http://narod.ru/disk/45935058001.2aaca38c9acf622332f4a81b5bf0e331/RM-803.rar.html
.not sure, but I think I've flashed my lumia 710 with this firmware and had unlocked my bootloader
Click to expand...
Click to collapse
First up I noticed it has a smaller than normal nokia_osbl.esco
I opened up nokia_osbl.mbn in a hex editor and wahlah, it's a qualcomm bootloader!
Who at Nokia screwed up? I don't care, I'm flashing it.
It seems to have qualcomm bootloader + cert.
xsacha said:
First up I noticed it has a smaller than normal nokia_osbl.esco
I opened up nokia_osbl.mbn in a hex editor and wahlah, it's a qualcomm bootloader!
Who at Nokia screwed up? I don't care, I'm flashing it.
It seems to have qualcomm bootloader + cert.
Click to expand...
Click to collapse
So is this easily flashed through NCS by placing the qualcomm nokia_osbl.esco file in a standard RM-801 package folder?
Only you have a way to provide a valid cert for passing NCS check, if so everyone would had have the Qualcomm bootloader from time, so the answer is no, you can just sticky the qualcomm bootloader and flash
Sent from my Lumia 800 using XDA Windows Phone 7 App
@ everyone i am discontinuing myKIT_BATCH and replacing it with a standalone batch script / shell script for rooting & the tethered recovery launcher ; with Intel Tablets increasing in use i feel this is the best course of action and will make it easier for new users . . .
The new thread is up but its still very much under construction : Intel Android Devices Root / Temp CWM Session
[TOOL KIT] myKIT_BATCHV1.1.x :
social-design-concepts : said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression myKIT wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
myKIT_BATCH TOOLv1.1.2 : "and Yet Another Generic Android Tool Kit "
any issues using this tool kit please use :
Code:
@social-design-concepts : myKIT_BATCHv1.1.2 ISSUE
DOWNLOAD / SETUP myKIT_BATCHv1.1.x
save the download somewhere on your computer using 7-zip , right click on the file and select extract here
myKIT_BATCHv1.1.2 : myKIT_BATCHv1.1.x.7z
Additional Downloads :
download any additional _ASSETKIT's / _ROOTKIT's needed for your device save the downloads in folder :
mykit-downloads
located in the top of the myKIT_BATCHv1.1.x directory where the run-me.bat file is located.
note : do not extract the files or rename them each time myKIT_BATCHv1.1.x is started it searches for .7z files with specific name endings and automatically extracts them to the correct location. . .
_PATCHKIT's :
place _PATCHKIT in mykit-downloads start myKIT_BATCH after patch is applied you'll need to close and restart myKIT_BATCH
myKIT_BATCHv1.1.2d_PATCHKIT.7z
change log :
Fix DERP in ADB Driver for Dell Venue 7 / Acer A1-830
Make ADB backup Quick Restore select-able instead of typing the full backup name
Prep For Flash Tool
Other Misc Corrections
_ROOTKIT'S :
10/06/2014 TRIAL2 : SDC_INTEL2_ROOTKIT Jellybean 4.1.2 - KitKat 4.4.x
note : This _ROOTKIT does not require the device specific _ASSETKIT that were needed before , should work on the :
Dell Venue 7 3730 / 8 3830 Clovertrail Plus , Acer Iconia A1-830 , Acer Iconia B1-730HD ,
Possibly other Intel Android Devices that have a method of starting the adbd service via fastboot oem command . . .
SDC_INTEL2_ROOTKIT.7z
OLDER _ROOTKIT'S : Recommend using the _ROOTKIT above
Jellybean 4.2.2 - Jellybean 4.3 note : this _ROOTKIT is already loaded in myKIT_BATCHv1.1.x there is no real need to download this . . .
jb4.2.2-jb4.3_ROOTKIT.7z
supported devices :
Dell Venue 7 3730 / Venue 8 3830 US Wifi / US 3G jb4.2.2 - jb4.3
Acer Iconia A1-830 jb4.2.2
Kitkat 4.4.2 note : requires device specific _ASSETKIT
DELL VENUE 7 Model 3730 US NoModem / VENUE 8 Model 3830 US NoModem WiFI Only
Kitkat 4.4.2 Dell SW v1.33 DellVenue-kk4.4.2v1.33_WiFi_ROOTKIT.7z
ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.2014062.120901:user/release-keys
ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.build.20140624.115655:user/release-keys
DELL VENUE 7 Model 3730 US 3G / VENUE 8 Model 3830 US 3G
IMPORTANT NOTICE : THERE WAS A MISTAKE IN THE ORIGINAL _ROOTKIT FOR DELL VENUE 7 3G DEVICE THAT BRAKES OTA COMPATIBILITY . . .
IF YOU ROOTED YOUR DEVICE WITH THE OLD ROOT KIT PLEASE RE-ROOT WITH THIS ONE TO RESTORE YOU ABILITY TO INSTALL DELL OTA UPDATES. . .
YOU CAN TELL IF THE OLD _ROOTKIT IS LOADED BY LOOKING AT THE NAME IN myKIT_BATCH THE NEW _ROOTKIT SAYS "KK ROOT TOOL Dell Venue 7 / 8 US 3G SW v1.33 date : 9-01-2014"
Kitkat 4.4.2 Dell SW v1.33 DellVenue-kk4.4.2v1.33_3G_ROOTKIT.7z
ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.20140624.122423:user/release-keys
ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.XYX.20140624.150615:user/release-keys
_ASSETKIT'S :
DELL VENUE 7 Model 3730 US WiFI : DeviceWIFI-Venue7_ASSETKIT.7z
DELL VENUE 8 Model 3830 US WiFI : DeviceWIFI-Venue8_ASSETKIT.7z
DELL VENUE 7 Model 3730 US 3G : Device3G-Venue7_ASSETKIT.7z
DELL VENUE 8 Model 3830 US 3G : Device3G-Venue8_ASSETKIT.7z
_PKGKIT'S :
coming soon . . .
ROOTING INSTRUCTIONS :
please make sure to disconnect all other device besides the device your working on. . . do not disconnect your device during rooting process . . .
open up the myKIT_BATCHv1.1.x folder and double click the run-me.bat to launch myKIT_BATCHv1.1.x
at the initial disclaimer screen type " ACCEPT " case sensitive without the quotes to continue
next on initial menu screen choose option 1 to update the driver ( update the driver more than likely the driver you have installed doesn't have all the modes included with it.
note : instructions for unsigned driver installation if running windows 8 or 8.1
Unsigned Driver Installation Windows 8
Unsigned Driver Installation Windows 8.1
Click to expand...
Click to collapse
after the driver installation is complete follow the instructions on the screen
once at the main menu , verify that your device is visible and showing " DEVICE STATUS: ADB-ONLINE "
next choose option A1 ROOT KITS to view the ROOT KIT MENU
at the ROOT KIT MENU select the appropriate ROOT KIT
note : the ROOT KIT MENU is dynamic and the menu option will change depending on the number of root kits found
please be sure to select the correct ROOT KIT for your Device / Software version. . .
Click to expand...
Click to collapse
next select the su / supersuer installation
next type " ACCEPT "
device will reboot and rooting / su installation will start after windows installs additional drivers if needed . . .
Click to expand...
Click to collapse
Driver Installations Language Error :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you are getting the above language error when trying to install the driver please see this link for editing dpinst.xml for your language:
The current language is not supported by the device Driver Installation Wizard
the driver is located in the myKIT_BATCHv1.1.xmykitsdriverKITADB
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
XDA:DevDB Information
[TOOL KIT] myKIT_BATCHV1.1.x, ROM for the Dell Venue
Contributors
social-design-concepts
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2016-05-28
Last Updated 2016-05-27
Downloads :
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
Stock Image Downloads :
Note : do not extract the <file name>.system.img.gz contained with in the 7zip file .img.gz is the correct format for flashing through fastboot for intel. . .
Acer
A1-830_WW_GEN1 :
JB4.2.2 : ro.build.fingerprint=acer/a1-830_ww_gen1/ducati:4.2.2/JDQ39/eng.svnadmin.20140620.161423:user/release-keys
Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=acer/a1-830_ww_gen1/ducati:4.4.2/KOT49H/241:user/release-keys
Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG.7z
Dell
Venue 7 WiFi 3730 :
JB4.2.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.2.2/JDQ39/eng.XYX.20131114.170109:user/release-keys
Venue_7_WiFi_JB4.2.2v1.42_FLASHPKG.7z
JB4.3 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.3/JSS15Q/eng.XYX.20140226.114853:user/release-keys
Venue_7_WiFi_JB4.3v1.25_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.2014062.120901:user/release-keys
Venue_7_WiFi_KK4.4.2v1.33_FLASHPKG.7z
Venue 7 HSPA+ 3730 :
JB4.3 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.3/JSS15Q/eng.XYX.20140111.111157:user/release-keys
Venue_7_3G_JB4.3v1.22_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.20140624.122423:user/release-keys
Venue_7_3G_KK4.4.2v1.33_FLASHPKG.7z
Venue 8 WiFi 3830 :
JB4.2.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.2.2/JDQ39/eng.DYY.20131114.160805:user/release-keys
Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG.7z
JB4.3 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.3/JSS15Q/eng.XYX.20140226.115029:user/release-keys
Venue_8_WiFi_JB4.3v1.25_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.build.20140624.115655:user/release-keys
Venue_8_WiFi_KK4.4.2v1.33_FLASHPKG.7z
Venue 8 HSPA+ 3830 :
KK4.4.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.XYX.20140624.150615:user/release-keys
Venue_8_3G_KK4.4.2v1.33_FLASHPKG.7z
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
Tethered CWM Recovery Trial 11/5/14
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
Tethered CWM Recovery Trial :
Note : This is a Trial CWM Recovery for some Intel Devices with locked boot loaders , it still has a few bugs . . .
WARNING : This is Tethered CWM Recovery is for some Intel Devices with locked boot loaders , it is not intended for installing custom roms as if the devices has a locked boot loader the device will fail to boot the unsigned images
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
Tethered CWM Recovery Trial 11/5/14 : INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z
Launch the recovery by placing it in the mykit-downloads folder the start myKIT_BATCHv1.1.x from the main menu select option A2 then select the tethered recovery program.
See this post for latest version : http://forum.xda-developers.com/showpost.php?p=57227753&postcount=2310
Note : WORKING
adb root shell
backing up to external storage
unsigned .zip installation
you tell me
Note : KNOWN BUGS
backing up to internal storage is currently broken
installing using adb side-loading of zips doesn't work and breaks adb
you tell me
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
I just wrote a PM to Chainfire. Let`s see if he`ll respond.
If this thing is flawless....
Then I would understand Dell for locking the boot loader.. But I am very very mad at Dell. This piece of device IS piece of junk with Android 4.3. Almost all appLications at some point in time will locked up and froze and for you to get back to it, you would have to press the power button momentarily, i.e turn off the display and turn it back on. Too bad I did not play with it very hard w/in 21 days of owning it. Now I don't know if it is worth talking to dell of repairing (AND/or REPLACING IT.)
Dell you can PM me. I will be actively watching this V8 (i GOT A 32 GIG v8) on www-facebook-com-DellHomeUS.
Thanks,
Tik
tikblang said:
Then I would understand Dell for locking the boot loader.. But I am very very mad at Dell. This piece of device IS piece of junk with Android 4.3. Almost all appLications at some point in time will locked up and froze and for you to get back to it, you would have to press the power button momentarily, i.e turn off the display and turn it back on. Too bad I did not play with it very hard w/in 21 days of owning it. Now I don't know if it is worth talking to dell of repairing (AND/or REPLACING IT.)
Dell you can PM me. I will be actively watching this V8 (i GOT A 32 GIG v8) on www-facebook-com-DellHomeUS.
Thanks,
Tik
Click to expand...
Click to collapse
Tik, while i under stand your frustration, I started this thread to move the devices out of the low activity section and for discussing and sharing any information that may lead to root method and aid in future development of these devices not to complain about Dell or the device..
if you wish to address to Dell your frustration with the device i urge you to post a commit to the facebook post:
Dell Venue 7/8 Intel Unlock Request
if you have a general question about the device please feel free to post in the new QA thread:
Dell Venue 7 & Venue 8 Intel General Q&A
or search in the original dell thread:
Original 2013 Dell Venue Tablet - root progress
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
wowbro said:
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
Click to expand...
Click to collapse
I think that social-design-concepts has them.
wowbro said:
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
Click to expand...
Click to collapse
Tell me what you want, jcase rooted 1 Venue 8 on 4.3 but the exploit was never made public, but that user allowed me access so i have, extracted boot, recovery, droidboot, kernel and ramdisk only no real images, and the rooted system.img, also took cat /proc/kallsyms from the rooted device, but have since figured out how to get kallsyms from a non rooted device, i probably have most everything you just tell me what you need.
i hope to have everything i have up by the end of the weekend, till then list what your wanting and ill post what i can provide.
social-design-concepts said:
boot.img, root.img, droidboot.img, kernel and ramdisk only no real images, and the rooted system.img, also took cat /proc/kallsyms from the rooted device.
Click to expand...
Click to collapse
Quick couple questions, how are you getting into fastboot? I can't get it. Have you tried using fastboot to flash the rooted system image?
adb reboot-bootloader even works powered off as the device use a charging os mode, or from powered off hold down vol down and the power key to boot to droidboot.
No I have the V7 not the V8, flashing a fake data.img to data I've had issues flash any img larger than 100mb or sparse images. Dell hasn't released a full restore firmware yet so I've not risked flashing system.img.
By the end of the weekend I should have everything I know up. The flashing a prerooted system image does seem to be a common root for Intel devices but with out a factory restore firmware / full-install.zip that's a huge risk knowing if it doesn't work dell won't warranty the device. So you'd be stuck with a soft brick until Dell released a full-install.zip and i don't think dells done that for any device they have ever released. Knowing that the device can be rooted with out flashing a prerooted system.img this should be a last option.
Sent from my XT907 using xda app-developers app
I am just wondering, can we dump partitions without root? If yes, then we could dump them, try to flash this rooted img`s and in case of any errors we could go back by flashing dumped files via fastboot.
social-design-concepts said:
adb reboot-bootloader even works powered off as the device use a charging os mode, or from powered off hold down vol down and the power key to boot to droidboot.
No I have the V7 not the V8, flashing a fake data.img to data I've had issues flash any img larger than 100mb or sparse images. Dell hasn't released a full restore firmware yet so I've not risked flashing system.img.
By the end of the weekend I should have everything I know up. The flashing a prerooted system image does seem to be a common root for Intel devices but with out a factory restore firmware / full-install.zip that's a huge risk knowing if it doesn't work dell won't warranty the device. So you'd be stuck with a soft brick until Dell released a full-install.zip and i don't think dells done that for any device they have ever released. Knowing that the device can be rooted with out flashing a prerooted system.img this should be a last option.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
OK. I don't know how much side chat anyone has has with jcase. He literally says the root method on his webpage i think he has registered in his xda profile. We also know he required Linux with the one and only root on the current dell ROM. He also posts on his site the basic method which he explains pretty clearly. Looks to have adb waiting for a device during the boot process to; I'm sure quickly mount something RW and script out a copy and execute a root. So, I know Linux treats hardware different and it may require less time to initiate communication with devices. Windows may not be showing you all the hardware/hardware ID's this thing reports it is so quickly during boot. It may not be possible to apply his method in a Windows environment. That said have you tried to get all the different types off hardware this thing reports that it is running on Linux and attempted a adb wait then immediate adb root method while its booting/rebooting?
I was never able to get it to work on the dell venue, I actually discovered it independent of jcase, he wasn't gonna publish it but I leak it, mine is down at the moment, when I get my new one i'all try it again.
Sent from my XT907 using xda app-developers app
deansouth8 said:
OK. I don't know how much side chat anyone has has with jcase. He literally says the root method on his webpage i think he has registered in his xda profile. We also know he required Linux with the one and only root on the current dell ROM. He also posts on his site the basic method which he explains pretty clearly. Looks to have adb waiting for a device during the boot process to; I'm sure quickly mount something RW and script out a copy and execute a root. So, I know Linux treats hardware different and it may require less time to initiate communication with devices. Windows may not be showing you all the hardware/hardware ID's this thing reports it is so quickly during boot. It may not be possible to apply his method in a Windows environment. That said have you tried to get all the different types off hardware this thing reports that it is running on Linux and attempted a adb wait then immediate adb root method while its booting/rebooting?
Click to expand...
Click to collapse
how it is in the HP 1800la
init.debug.rc:
....
on charger
# basic networking for "adb root"
ifup lo
hostname localhost
domainname localdomain
#mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered
mount ext4 /dev/block/mmcblk0p9 /data nosuid nodev barrier=1,data=ordered
mkdir /data/logs 0755 system system
mkdir /data/logs/modemcrash 0775 system system
mkdir /data/logs/stats 0775 system system
mkdir /data/logs/gps 0775 system system
mkdir /data/logs/aplogs 0775 system log
setprop persist.service.apklogfs.enable 1
setprop sys.usb.config adb
setprop ro.debuggable 1
how it is on the venue 8 JB-4.2.2
init.debug.rc:
....
on charger
# basic networking for "adb root"
ifup lo
hostname localhost
domainname localdomain
# mount data partition for get charger log
#mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered
mount ext4 /dev/block/mmcblk0p9 /data nosuid nodev barrier=1,data=ordered
mkdir /data/logs/modemcrash 0775 system system
mkdir /data/logs/stats 0775 system system
mkdir /data/logs/gps 0775 system system
mkdir /data/logs/aplogs 0775 system log
setprop persist.service.apklogfs.enable 1
setprop sys.usb.config iadb
setprop ro.debuggable 1
how it is on the venue 8 JB-4.3
init.debug.rc:
....
on charger
on charger
# basic networking for "adb root"
ifup lo
hostname localhost
domainname localdomain
mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered
mkdir /logs/modemcrash 0775 system system
mkdir /logs/aplogs 0775 system log
setprop sys.usb.config iadb
Do you have an uncompressed boot.img off the 4.3 ? I'd like to try enabling ADB and making system mount rw. That was how we got root on the Le Pan S originally.
kairnage said:
Do you have an uncompressed boot.img off the 4.3 ? I'd like to try enabling ADB and making system mount rw. That was how we got root on the Le Pan S originally.
Click to expand...
Click to collapse
All files we have are here:
https://www.dropbox.com/sh/tqx1j2cpi155v2n/hPZPEnsZfi
maxld said:
All files we have are here:
https://www.dropbox.com/sh/tqx1j2cpi155v2n/hPZPEnsZfi
Click to expand...
Click to collapse
Right, unpacked, I would like the original boot.img.
kairnage said:
Right, unpacked, I would like the original boot.img.
Click to expand...
Click to collapse
Sorry, I misread that. I think that Social-design-concepts has them. I will try to contact him, cheers.
maxld said:
Sorry, I misread that. I think that Social-design-concepts has them. I will try to contact him, cheers.
Click to expand...
Click to collapse
Thanks, If I try to pack it and fastboot can't boot it I won't know if it's the edit or the method I used to pack it. With the original image I can try to boot it first, and make sure that the system will even allow it. Then I will be certain I am a screw up if my version doesn;t work. :doh:
[Q&A] [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery
Q&A for [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
This looks like a really great tool but I'm having troubles with it.
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a MTK image with regular script?
If so, please use unpack_MTK_img script. ERROR!
>> Exit script
when I use MTK it says
Unpacking the ramdisk....
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a regular image with MTK script?
If so, please use unpack_img script. ERROR!
>> Exit script
this is for the LG Optimus F3 Boot.img from Team Win 2.8.0.0
is there any way to extract this puppy?
Code:
Printing information for "boot.img"
Android image info utility by [email protected]
Header:
Magic : ANDROID!
Magic offset : 0x00000000
Page_size : 2048 (0x00000800)
Base address : 0x80200000
Kernel address : 0x80208000
Kernel size : 7602936 (0x007402f8)
Kernel offset : 0x00008000
Ramdisk address : 0x88f108f0
Ramdisk size : 2048 (0x00000800)
Ramdisk offset : 0x08d108f0
Second address : 0x81100000
Tags address : 0x80200100
Tags offset : 0x00000100
Cmdline : 'androidboot.hardware=fx3s user_debug=31 vmalloc=308M'
Id : 46c3c0e3d52bc3f86497ddd8f07eae74643c5f0e
Successfully printed all informations for boot.img
HappyRoms said:
This looks like a really great tool but I'm having troubles with it.
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a MTK image with regular script?
If so, please use unpack_MTK_img script. ERROR!
>> Exit script
when I use MTK it says
Unpacking the ramdisk....
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Your ramdisk archive is corrupt. Are you trying to unpack a regular image with MTK script?
If so, please use unpack_img script. ERROR!
>> Exit script
this is for the LG Optimus F3 Boot.img from Team Win 2.8.0.0
is there any way to extract this puppy?
Code:
Printing information for "boot.img"
Android image info utility by [email protected]
Header:
Magic : ANDROID!
Magic offset : 0x00000000
Page_size : 2048 (0x00000800)
Base address : 0x80200000
Kernel address : 0x80208000
Kernel size : 7602936 (0x007402f8)
Kernel offset : 0x00008000
Ramdisk address : 0x88f108f0
Ramdisk size : 2048 (0x00000800)
Ramdisk offset : 0x08d108f0
Second address : 0x81100000
Tags address : 0x80200100
Tags offset : 0x00000100
Cmdline : 'androidboot.hardware=fx3s user_debug=31 vmalloc=308M'
Id : 46c3c0e3d52bc3f86497ddd8f07eae74643c5f0e
Successfully printed all informations for boot.img
Click to expand...
Click to collapse
Can you attach that image here, to take a look? It sounds like there is no ramdisk in it. There are some phones that doesn't have ramdisks in boot images.
carliv said:
Can you attach that image here, to take a look? It sounds like there is no ramdisk in it. There are some phones that doesn't have ramdisks in boot images.
Click to expand...
Click to collapse
Sure thing, just remove .zip from the file name, had to do that as it only allows 8Mb img uploads
I'm trying to edit the boot so that I might be able to make the external SD into the data drive, is this even possible or am I wasting my time?
Thanks!
HappyRoms said:
Sure thing, just remove .zip from the file name, had to do that as it only allows 8Mb img uploads
I'm trying to edit the boot so that I might be able to make the external SD into the data drive, is this even possible or am I wasting my time?
Thanks!
Click to expand...
Click to collapse
Ok, I see... Your image is "lokified". In order to use my tool you need to "de-lokify" it first, then after modding you need to "re-lokify" it back. Some infos here and here. It may be many other infos but I didn't have time to do a full search; you have to do it for yourself.
Some LG and Samsung devices have that "Loki" thing and you need to deal with it. Maybe when I'll have a phone like that I'll make an automated process for it, but now I haven't and I can't work "in blind".
I don't know what to say about your last question... I'm not even sure what you're talking about.
carliv said:
Ok, I see... Your image is "lokified". In order to use my tool you need to "de-lokify" it first, then after modding you need to "re-lokify" it back. Some infos here and here. It may be many other infos but I didn't have time to do a full search; you have to do it for yourself.
Some LG and Samsung devices have that "Loki" thing and you need to deal with it. Maybe when I'll have a phone like that I'll make an automated process for it, but now I haven't and I can't work "in blind".
I don't know what to say about your last question... I'm not even sure what you're talking about.
Click to expand...
Click to collapse
Awesome, thanks!
basically, the LG Optimus F3 comes with too little memory built in, there's a program that mounts an external SD's second partition as a data folder, but even still it runs out of internal memory or won't install apps larger than the internal memory because the "System" partition still has little room.
so the goal was to edit the boot so it will boot using an external SD directly as the system drive, it would read it's maximum memory available as whatever the external SD's maximum is.
this would solve the problem, if it works, if not then it'll probably just brick the phone :good:
I just wanted to update and say thanks. This helped out great! I was able to successfully boot /data from my external SD card as desired, however, my card is only a class 2 so it won't be a good idea until I upgrade it to a class 10.
Lg Optimus F3 comes with very little internal storage, which was giving me a headache, so I wanted to make the phone boot using an external SD as the /data partition.
after following your tip, I unloki'd the boot image and used your Carliv Image Kitchen to extract the contents, edited the fstab and edited out the original code: "/dev/block/platform/msm_sdcc.1/by-name/userdata /data" telling it to mount /data on the /dev/block/mmcblk1p2 instead.
after repacking and re-loking and flashing the .img it had some problems, for some reason it was just booting to a black screen, so I used dd from the team win terminal to copy the /dev/block/platform/msm_sdcc.1/by-name/userdata over to the /dev/block/mmcblk1p2, and it worked!
being a class 2, it booted slowly and responded slowly but works none the less.
to be sure there was no problem with partition size, being how I used dd to mirror userdata over to the sdcard, I ran gparted in linux and resized the partition smaller, then larger to full size (just in case)
thanks for your wonderful tool and for pointing me in the right direction.
help sir carliv please
I was trying to install cm12 using carliv touch recovery 3.3 for kit kat on my alcatel pop d3 but it failed now my phone is stuck and wont turn on
what version of cm can that recovery install??????
DONTEGO said:
I was trying to install cm12 using carliv touch recovery 3.3 for kit kat on my alcatel pop d3 but it failed now my phone is stuck and wont turn on
what version of cm can that recovery install??????
Click to expand...
Click to collapse
The answer is already in your question:
I was trying to install cm12 using carliv touch recovery 3.3 for kit kat....
Click to expand...
Click to collapse
As I already posted in recovery's thread, it will work with kitkat kernels. Some people port it to lollipop but I never recommended that.
So to answer clearly cm11 because cm12 means lollipop, or it will work with any other kitkat based ROM if your phone has any kitkat kernel released.
You need to ask the one who released that cm12 for your phone to provide a matching recovery along.
Now you probably need to reflash the phone with SPFlashTools.
ok thanks a whole lot but im having another issue the sd card is now only readable by my phone how do i go about copying a rom to it whenever i plug it into the pc it doesnt come up
DONTEGO said:
ok thanks a whole lot but im having another issue the sd card is now only readable by my phone how do i go about copying a rom to it whenever i plug it into the pc it doesnt come up
Click to expand...
Click to collapse
im trying to install Mystic_OS_v4DL750.zip does it require a gapps package?
Can some one port ne a recovery for xolo era 4g
Sent from my Hacked_Era_4G using Tapatalk
Is it able to unpack stock recovery?
---------- Post added at 03:25 AM ---------- Previous post was at 03:23 AM ----------
Raakib Zargar said:
Can some one port ne a recovery for xolo era 4g
Sent from my Hacked_Era_4G using Tapatalk
Click to expand...
Click to collapse
Which chipset?
Hi there... I woul like to ask if this tool works for Helio x20 cpu's... (Mt6797 - Leagoo T10) because I'm trying to extract the stock recovery but having trouble with the ramdisk... It says "compression used unknown..." I've seen it mentioned in the discussion some times but the explanation was to use the 1. Metod ??? I'm using the windows 1.1 version and I really don't see any other method to use (start bat, r, 1 recovery.img, , 1 unpack image, error....) I'm just installing Ubuntu to see the difference but would be grateful for some advise... Thanks.
Since main Carlive Image Kitchen thread has been closed in 2017 all the util builds have been lost for some unknown reason. Dev claimed he have personal problems and adviced users to help each other.
I've found latest official version 1.3 builds and publish them here for practical and historic reasons. This util mentioned in a various manuals so people will look for it for a long time then. Old Linux modded version by yuweng is also added for completeness.
View attachment CarlivImageKitchen_Windows_v1.3.zip
View attachment CarlivImageKitchen_Windows_x64_v1.3.zip
View attachment CarlivImageKitchen-Linux_v1.3.zip
View attachment CarlivImageKitchen-Linux_x64_v1.3.zip
View attachment CarlivImageKitchen-Linux-DnD-yuweng.zip
Furthermore user FOV5 @ 4pda.ru forums have modded latest 1.3 version a few times so I do publish here his latest modded version 1.5B3 (12-Jan-2018)
Changes history:
- v1.4: Support for some non-standard kernel images (e.g. LibreELEC and similar).
- v1.5B1:
- Removed 'Boot' and 'Recovery' prefixes from file names while unpacking Boot/Recovery images. This is due to ability to easily compare whole Boot and Recovery folders after unpacking.
- Added optional experimental AmLogic core unpacking. This could be helpful to patch storage media layout when device partition build into the core.
- v1.5B2: Fixed 32 bit app crash after core unpacking. A few other small non critical fixes.
- v1.5B3:
- New while core slitting, parameters like Name, Load Address and Entry Point are preserved.
- Fixed: New app will try to pack core only when all the 4 kernel parts are found in the unpacking folder. If core unpacking process some kind failed, one or more kernel.* files will be missing, so repack process will use original core instead of trying to assemble broken one.
View attachment CarlivImageKitchen_Windows_v1.5B3.7z
If you have any questions related to this modded app version look for FOV5 user at 4pda.ru forums and ask him (I don't know does he speak any langs except Russian, online translators available anyway. There is also Russian numeric captcha problem for non-Russian speakers when loggin in to that forums, sorry guys). I do not often use this app and occasionally visit XDA, so I can't support this product in a professional manner. Help each other guys!