Related
I have somehow messed up my folio 100, and its BCT and bootloader information.
So im hoping someone else with little experience, knows how to use the nvflash utilities and dump the information for me and send me a link on where to get it.
the combo to get into bootloader mode is: POWER button pressed 4 times + VOL- key and it will go into bootloader mode.
I can extract these tomorrow evening.
Can you be clearer with the bootload sequence?
Tried to get the booload seq. Ended up with a partial reset of settings...
tshoulihane said:
I can extract these tomorrow evening.
Can you be clearer with the bootload sequence?
Tried to get the booload seq. Ended up with a partial reset of settings...
Click to expand...
Click to collapse
well, i dont think you should try it..!!
another user did, he ended up with a semi-bricked device too.. so thanks but now the fun stops.. it seems that Toshiba included a very,very bad key combo that terminates the device to a deadlocked machine..
so ill just figure out another way to get the partitions off it.. but my 4xpower + vol- is really scary, do NOT try it
at least until is cleared on how to get out of this bootloader state again.
I dumped the partitions which are visible from android already. Don't quite know what got resentment with your key sequence - DATA wiped? Some of the preloaded apps are broken now, but they were a bit broken before.
tshoulihane said:
I dumped the partitions which are visible from android already. Don't quite know what got resentment with your key sequence - DATA wiped? Some of the preloaded apps are broken now, but they were a bit broken before.
Click to expand...
Click to collapse
so you mean, you can extract all partitions from a shell?
ie. bootloader of partition2 and so forward?
i didnt notice that all 8 partitions were accessable there?
can you upload the dump of them somewhere?
A guy made the dumps of the ROM (not the recovery image though) on the forum of Frandroid DOT fr but I cannot post you the link directly here (anti spam as I do not have many messages on the forum).
I will PM you (if it allows me)
bootoo said:
A guy made the dumps of the ROM (not the recovery image though) on the forum of Frandroid DOT fr but I cannot post you the link directly here (anti spam as I do not have many messages on the forum).
I will PM you (if it allows me)
Click to expand...
Click to collapse
i have the dump of the /system i need all of the other partitions ie. 0 to 8
i cannot restore system, as i got no bootable tablet at all, i need raw partition dumps which i hope can be used using nvflash
Is it possible to extract opera mobile 10.1 apk?
toca79 said:
Is it possible to extract opera mobile 10.1 apk?
Click to expand...
Click to collapse
look for it here
Dexter_nlb said:
look for it here
Click to expand...
Click to collapse
Thx a lot found it.
I think the resolution is too high though.
Hi Dex, did you was able to restore your bricked folio?
roglio said:
Hi Dex, did you was able to restore your bricked folio?
Click to expand...
Click to collapse
decided to get another one..
ok!
I was hoping you did it because I'm a little tired of android (apple fan ).
My idea was to build and flash linux (ubuntu 10.10 works on toshiba AC100).
But if there isn't a way to restore the factory default (bootloader, etc.), I'll give up.
roglio said:
My idea was to build and flash linux (ubuntu 10.10 works on toshiba AC100).
Click to expand...
Click to collapse
when i was debugging bootloader configs, i was provided some config files that Ac100 users said would work on our folio, but i see now partition setup is very different, so we need to make proper configs for our folio before experimenting with the bootloader..
again, as you metion backup seems to do , when recover seems unavailable currently. it will be hard to verify if the parition table layout is working.
Hi,
sorry, maybe I missunderstood someting, but I cannot understand your problem in reading out the whole flash.
1. I have opened / disassembled my Filio 100. And like I have suspected there is a 16GB micoSD card connected (soldered) to the PCB and fixed with glue. One could read out the whole flash in a card reader.
2. You have fully access to the microSD card out of Android:
/dev/block/mmcblk0
sh-4.1# cd /dev/block
cd /dev/block
sh-4.1# pwd
pwd
/dev/block
sh-4.1# ls -l
ls -l
brw------- root root 254, 1 2010-12-07 08:46 dm-1
brw------- root root 254, 0 2010-12-07 08:46 dm-0
drwxr-xr-x root root 2010-12-07 08:45 vold
brw------- root root 179, 17 2010-12-07 08:45 mmcblk1p1
brw------- root root 179, 16 2010-12-07 08:45 mmcblk1
brw------- root root 7, 7 2010-12-07 08:45 loop7
brw------- root root 7, 6 2010-12-07 08:45 loop6
brw------- root root 7, 5 2010-12-07 08:45 loop5
brw------- root root 7, 4 2010-12-07 08:45 loop4
brw------- root root 7, 3 2010-12-07 08:45 loop3
brw------- root root 7, 2 2010-12-07 08:45 loop2
brw------- root root 7, 1 2010-12-07 08:45 loop1
brw------- root root 7, 0 2010-12-07 08:45 loop0
brw------- root root 179, 8 2010-12-07 08:45 mmcblk0p8
brw------- root root 179, 7 2010-12-07 08:45 mmcblk0p7
brw------- root root 179, 6 2010-12-07 08:45 mmcblk0p6
brw------- root root 179, 5 2010-12-07 08:45 mmcblk0p5
brw------- root root 179, 4 2010-12-07 08:45 mmcblk0p4
brw------- root root 179, 3 2010-12-07 08:45 mmcblk0p3
brw------- root root 179, 2 2010-12-07 08:45 mmcblk0p2
brw------- root root 179, 1 2010-12-07 08:45 mmcblk0p1
brw------- root root 179, 0 2010-12-07 08:45 mmcblk0
sh-4.1#
Regards, Artem
Hi DerArtem! Nice first post indeed!!!!
Thank you for your information.
A micro SD soldered is a nice gift from toshiba!!! This means upgrades, full dumps, etc.
Great
A request: could you please post some pictures?
DerArtem said:
sorry, maybe I missunderstood someting, but I cannot understand your problem in reading out the whole flash.
Click to expand...
Click to collapse
did i write i had problem dumping the entire mmc device? not really.
Yes, you misunderstood,Writing a proper cfg file describing the different areas is required.. dumping is easy part, documenting is harder..
but feel free to contribute and document the .cfg file for bootloader, that is of course appreciated...
I just got back from my business trip, and finally had some more time to take a closer look at the device.
roglio said:
Hi DerArtem! Nice first post indeed!!!!
Thank you for your information.
A micro SD soldered is a nice gift from toshiba!!! This means upgrades, full dumps, etc.
Great
A request: could you please post some pictures?
Click to expand...
Click to collapse
The device has a warranty seal inside. If you open the device completly the seal will break. I have just opened the device soo far, that the seal will not break. To make photos I will have to open it copletly. I will think about it....
Dexter_nlb said:
did i write i had problem dumping the entire mmc device? not really.
Yes, you misunderstood,Writing a proper cfg file describing the different areas is required.. dumping is easy part, documenting is harder..
but feel free to contribute and document the .cfg file for bootloader, that is of course appreciated...
Click to expand...
Click to collapse
Ok, I see. I have duped the mmc and mounted the partitions on my pc:
Here is the partition table on my PC:
Code:
[email protected] ~/bin/folio $ /sbin/fdisk -u -l folio.img
Platte folio.img: 15.9 GByte, 15920005120 Byte
1 Köpfe, 63 Sektoren/Spur, 493551 Zylinder, zusammen 31093760 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Gerät boot. Anfang Ende Blöcke Id System
folio.img1 2048 526335 262144 83 Linux (/system)
folio.img2 526336 2623487 1048576 83 Linux (/cache)
folio.img3 2623488 2627583 2048 83 Linux (/misc)
folio.img4 2627584 31093759 14233088 5 Erweiterte
folio.img5 2628608 2644991 8192 83 Linux (???)
folio.img6 2646016 4743167 1048576 83 Linux (/data)
folio.img7 4744192 4754431 5120 83 Linux (???)
folio.img8 4755456 31093759 13169152 83 Linux (13G - storage)
Now you can mount the partitions on your pc:
Code:
sudo mount -o loop,ro,offset=$((512*2048)) folio.img /mnt/floppy/
I was not able to find the kernel or the bootloader or the root partition in the dump. I have also checked it with a hex editor.
Is the Folio using an other storage for kernel and bootloder? Does it have more NOR/NAND flash inside?
While looking at the size of the microSD (15920005120 bytes) I think that the bootloader is hiding a part of the microSD from the OS where the kernel and the bootloader are...
Where is the .cfg file you are talking about located?
DerArtem said:
Where is the .cfg file you are talking about located?
Click to expand...
Click to collapse
its a file assoiciated with the nvflash utility. search for the toshiba AC100 or here for more details for them it works fine.
the part 5 and 7 are boot kernel(8Mbyte) + recovery kernel(5Mbyte) , bootloader is as i know from ac100 on part0 , but thats not 100% yet.
Dexter_nlb said:
the part 5 and 7 are boot kernel(8Mbyte) + recovery kernel(5Mbyte) , bootloader is as i know from ac100 on part0 , but thats not 100% yet.
Click to expand...
Click to collapse
So, I have checked part 5 and 7. The content is the same like in boot.img and recovery.img. So the BCT is somewhere else...
Very bad news.
I appear to have had an accident with /efs. Not 100% sure what I did but suspect it related to a product code change.
My SGS2 now will not show an IMEI or connect to the cell network.
I connected with /adb and saw a number of files were updated earlier today
drwxrwxr-x 5 root root 4096 Jan 1 2000 .files
drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei
-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log
-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_data.bak.md5
-rwx------ 1 radio radio 2097152 Jan 1 2011 .nv_data.bak
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5
-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak
-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode
drwx------ 3 system system 4096 Jan 1 2011 dmp
-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone
-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result
-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin
-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data
-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p
-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena
bled
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock
-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata
-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5
-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin
-rw-r--r-- 1 system system 0 Nov 3 18:02 cryptprop_onetimeboot
drwxrwx--x 5 radio system 4096 Nov 3 21:23 .
drwxr-xr-x 21 root root 0 Nov 3 21:58 ..
You can see the changes to nv_data.bin.md5 and nv_data.bin -- I have no idea what crptprop_onetimeboot is but it looks a little suspicious.
Firstly I have a copy of the above as
- a directory on my sdcard
- a dd'd image on my sdcard
- a file copy on my PC (!)
I also see I still have backup files, so with a lot of difficulty (fs kept going read only when trying to copy files, so I ended up renaming the old name to the new name)
ie
.nv_data.bak -> nv_data.bin
.nv_data.bak.md5 -> nv_data.bin.md5
This didn't work (still no service/no imei), so I removed(renamed) the .md5 file -- but it still doesn't work
so it now looks like
# ls -latr
ls -latr
drwxrwxr-x 5 root root 4096 Jan 1 2000 .files
drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei
-rwx------ 1 radio radio 32 Jan 1 2011 nv_data.bin.md5.orig
-rwx------ 1 radio radio 2097152 Jan 1 2011 nv_data.bin
-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log
-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5
-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak
-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode
drwx------ 3 system system 4096 Jan 1 2011 dmp
-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone
-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result
-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin
-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data
-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p
-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena
bled
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock
-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata
-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5.bk
-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin.bk
-rw-rw-rw- 1 root root 0 Nov 3 20:55 p
drwxrwx--x 5 radio system 4096 Nov 3 21:48 .
-rw-r--r-- 1 system system 0 Nov 3 21:52 cryptprop_onetimeboot
drwxr-xr-x 21 root root 0 Nov 3 21:58 ..
#
[/FONT]
I DID NOT BACKUP EFS beforehand (only just learnt I need to) and know this may now be screwed, but I'm still hopeful I have the original file and just made a silly error.
I could also
- try recreating the whole fs and copying files back
- checking the prod code within the rom (but why?)
- flashing original firmware
- modifying the dd'd image *offline*, swapping the files, and dd'ing the image back
Any advice. PLEASE....
if you have a backup the easiest way I have found is to use root explorer.
go in to the /efs folder, set to read/write, mark everything and delete (not scrictly necessary simply copying over will work) but if you have been tinkering probably better.
then paste all the back up files and folders in
finally reboot (in my experience when something has gone wrong even this is not necessary)
Root explorer is worth every penny
and keep multiple backup's of your /efs on different drives
If this does not work you are screwed. The file contains your IMEI encrypted and the only way to get that restored is by returning it.
oh I just realised you are saying the back up you have is only of it in the current state?
If that's the case you are probably screwed, have you ever used any apps like nitrality or any unlocking tools? they will create copies of your efs folder on the scard in various locations. have you run a file seach on you sdcard to see if there is any copies at all?
if you have no backups of this folder then I think you will find its a return to manufacturer / sevice centre / provider issue.
I *think* I have restored the files -- and the dates look reasonable, as if they were the originals.
I've now flashed an old ROM (KE5) for good measure, but still no signal
One discrepancy I did notice is that after installing a rom there was some bootup message about csc and XEU when copying files.
My original sales code was VOD (UK vodafone). I had then run XEU firmware and just recently tried to set the sales code to XEU using a *# code. I subsequently flashed back to vodafone firmware today.
So somewhere there's a lingering reference to XEU -- this prod code incompatability could be causing the error?
I definately feel I should have the data to fix this -- after all I have the encrypted file, but am not quite sure of all the factors involved (one being "you're stuffed I know")
type *#06# this should display you IMEI number
if this does not match your IMEI from the box then you have not fixed this
if it shows all zeros or 004999010640000 then you are on a generic IMEI number
strangely when I screwed mine up and got the generic one above I was still able to use mine with a vodafone (UK) sim but not an orange on
if this is the case, and there is no efs backup prior to this you might well be screwed.
if this backup is all you have an you believe the .bak file is intact then I believe you will find solutions for deleting the primary version of the file and keeping only the backups and rebooting
the log file should give you more information on how successful this was, but if this was the result of flashing you probably overwrote both primary and backup
*#1234# is returning a reasonable CSC I9100VODKE2
Checking the nv data files, it appears
- the new ones modded today contain XEU
- the original ones contain VOD
This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.
Some remnant of XEU?
*#06# is currently showing blank -- but those .bak files looked fine.
Annoyed and frustrated...
In that case I would try deleting nv_data.bin and nv_data.m5 and rebooting
(assuming you have copies of everything
with just nv_data.bak nv_data.bak.md5
At least with the SGS1 this would work provided those bak files are the originals but the nv.log file will tell you more after the boot.
HOWEVER the SGSII has a lot more in this folder and I do not claim to fully understand them all but if you have a back up it's worth a shot
planetf1 said:
*#1234# is returning a reasonable CSC I9100VODKE2
Checking the nv data files, it appears
- the new ones modded today contain XEU
- the original ones contain VOD
This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.
Some remnant of XEU?
Click to expand...
Click to collapse
Took some inspiration from http://www.communityhosting.net/sgsunlock/i9000.html and decided to check permissions & recreation of md5.
md5 wasn't recreated, so no matter, I had a backup. that is restored, but I don't know if the .bak files are needed. Yet trying to create them I get:
# mv nv_data.bin.md5.orig nv_data.bin.md5
mv nv_data.bin.md5.orig nv_data.bin.md5
# cp nv_data.bin .nv_data.bak
cp nv_data.bin .nv_data.bak
cp: write error: Read-only file system
#
This isn't a space issue.
There could be another cause -- /efs/imei/mps_info.dat contains the 3 characters "XEU" even though the file is dated Jan 2011
So either
- the date has been manually fudged
OR
- the code always was XEU -- unlikely.
I'm currently working on the basis that fundamentally the IMEI is intact, that the original nv_data.bin is intact & that the phone is validating the CSC in mps_info.dat (XEU) against nv_data.bin (VOD) and failing.
Though this wouldn't explain why before the fix, with XEU in the nv_data.bin, it wasn't working
Unless the issue is the filesystem itself. could it be corrupt? Is this in fact why it switched to R/O mode each time? I've tried multiple kernels including insecure. surely they wouldn't all "protect" this fs.
But if this is the case where is fsck? maybe I need to copy the fs image to another linux box with ext4 & inspect/correct before shipping back and dd'ing
Continuing.
Found /system/bin/e2fsck -- ran this against /efs with
# /system/bin/e2fsck /dev/block/mmcblk0p1
/system/bin/e2fsck /dev/block/mmcblk0p1
e2fsck 1.41.11 (14-Mar-2010)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determini
ng whether /dev/block/mmcblk0p1 is mounted.
/dev/block/mmcblk0p1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y>? y
yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(3202--3203) +4104
Fix<y>? yes
/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p1: 60/1280 files (1.7% non-contiguous), 2188/5120 blocks
**** >>> I NOW HAVE AN IMEI <<< ****
AND SIGNAL
LOGGED ONTO VODAFONE
WOOOHAY.
THIS HAS BEEN FUN. LOOK AND LEARN..
and seriously thanks to all the other articles and some moral support here tonight.
Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
planetf1 said:
Continuing.
Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
Click to expand...
Click to collapse
and make several backups of the /efs folder in its current state one would assume
Phone seems working. restoring over a HSPA connection happily, recognized voda sim.
now reinstalling titanium backup and copying down from dropbox...
The final step was restoring from titanium backup.
I had erased my sdcard -- though my backup was on dropbox.
However titanium backup is awful at copying files to/from dropbox -- as is IMO the phone when in "phone/kies" mode.
Finally I simply copied the dropbox directory back in USB debug=mass storage mode which was quick and reliable -- and then restored most items en-masse (I have a pro license).
For the record so far phone is fine - and indeed I've since run a new efs backup
The key takeaways from this are
* Backup efs and save it somewhere offline
* get titanium backup pro. it's good (better if it backed up efs too!)
* usb mass storage mode is the most reliable way for file xfer
* backup efs (again)
* don't get complacent
And of course if you do get a similar problem to mine
a) take a backup of efs with dd if=/dev/mmcXXX of=/mnt/scard/myefs.img (check name - I forget)
b) copy files you can to sdcard
c) copy both of this to a seperate pc
d) Just try running fsck (as above) - If I'd done this sooner I'd have saved hours. I should have gone with the obvious -- I've seen this on enough linux systems in the past to know what was happening but was thrown by no kernel messages.
Thanks for letting us know, might be a nice reference for future problems, especially the filesystem check.
Writing about it also helped keep me sane.giving up and hitting the beer was becoming increasingly attractive.
I do think making the warning about efs clearer would help.backup really should be a must at the earliest opportunity
Sent from my GT-I9100 using Tapatalk
Another thought.do unmount /efs before fsck
Sent from my GT-I9100 using Tapatalk
Unable to restore
I know I had a valid IMEI during the last week or so.
I have flashed several ROM's during the last month.
Last night lost IMEI
Now , no matter what I try, I can't seem to restore my IMEI. I have the fake one that ends in a bunch of zero''s
My SDCARD has a folder called EFS_BACKUP with multiple efs_xxxxxxx.tar.gz files in it. If I extract any of these and try to restore them to the /EFS folder I still have the fake IMEI number.
Please help - I didn't understand all the adb code in this post
Hi there,
/efs is fairly new to me too, to be honest it took hours of careful rooting before I gained some useful knowledge in how that area works.
-- what I would suggest before *anything else* is to copy anything you do have left in /efs. You will need to be root to do this. I found the gui root explorer type tools a bit clunky so I used the android SDK (adb is one of the tools in this package) to help. IF YOU NEED HELP WITH THIS SAY. You need to copy the files to multiple places for safety. Someone OFF your phone, ie on a PC. This is just in case things get worse. Do the same with any of those .gz backups you have. Maybe you'll need them *if* you make things worse...
If you're familiar with linux/unix systems this is all fairly easy, but if you're not it can be quite scary. For example you have to be able to write to /efs as well as list files and move them around. One wrong step and you could make things worse.
If you're unsure perhaps you could find a friend who knows *nix well to help you out. The bottom line is that you need to
a) ensure the right files are in there
b) The filesystem itself was intact
I definately suffered from b -- less sure about a.
What you need to do will depend a fair bit on what files you find in there, and what dates they are.
You said you had some backup files. Are you sure you have some from before the problem started? Can you look inside those backup files (I think winzip or similar will expand them for you). WIthout divoluging the actual contents (since you don't want to share your IMEI with anyone), is there an nv_data.bin file in there? Out of all the files it seems to be the most critical. When's it dated (mine was Jan 2011). If you cant' find that file how about .nv_data.bak - is that a good size, and again an old one.
If you have either of these -- even without anything else I think you can probably recover.
If you can get up and running with adb, a good start would be
adb shell
ls -laR /efs
Thank you very much, fsck method fixed my efs. Phone just broke it while doing nothing :/
I love you
You just saved my Galaxy S2
Yay. Brilliant news
So..... I've been fussing with the kernel these days.
I managed to add cwm recovery just by editing initramfs.
also, I could enable init.d support
I had a repacker script that only involves original zImage and edited initramfs folder and it made my work easier.
Now, I became greedy and I wanted to add cpu governor.
If I want to do so, I 've gotta actually compile the kernel from source.
I first used this command
export ARCH=arm
export CROSS_COMPILE=/home/xxxxxxxx/arm-2009q3/bin/arm-none-eabi
make venturi_kor_defconfig #I have Korean device
make menuconfig # at the menu, i located my initramfs folder
make -j2
I've got numerous errors no matter what toolchain I used.
arm-eabi-4.4.0
arm-eabi-4.4.3
arm-eabi-4.7
arm-2009q3
arm-eabi-linaro 4.6.2
arm-eabi-linaro 4.7
all the zImages created had similar sizes as the original ones but none of them passed samsung logo (they do boot into recovery though)
4.4.3 and 4.7 didn't even make zImage so I guess that's guaranteed failure.
But Samsung's YP-GB70 Opensource zip says that I should use arm-2009q3 and when I do, it still gives me error
I use 12.04 LTS 64bit
any suggestion please? I'm dire
stylemate said:
So..... I've been fussing with the kernel these days.
I managed to add cwm recovery just by editing initramfs.
also, I could enable init.d support
I had a repacker script that only involves original zImage and edited initramfs folder and it made my work easier.
Now, I became greedy and I wanted to add cpu governor.
If I want to do so, I 've gotta actually compile the kernel from source.
I first used this command
export ARCH=arm
export CROSS_COMPILE=/home/xxxxxxxx/arm-2009q3/bin/arm-none-eabi
make venturi_kor_defconfig #I have Korean device
make menuconfig # at the menu, i located my initramfs folder
make -j2
I've got numerous errors no matter what toolchain I used.
arm-eabi-4.4.0
arm-eabi-4.4.3
arm-eabi-4.7
arm-2009q3
arm-eabi-linaro 4.6.2
arm-eabi-linaro 4.7
all the zImages created had similar sizes as the original ones but none of them passed samsung logo (they do boot into recovery though)
4.4.3 and 4.7 didn't even make zImage so I guess that's guaranteed failure.
But Samsung's YP-GB70 Opensource zip says that I should use arm-2009q3 and when I do, it still gives me error
I use 12.04 LTS 64bit
any suggestion please? I'm dire
Click to expand...
Click to collapse
Hmmm. First make sure you downloaded source for the gingerbread kernel (2.6.35) and not froyo (2.6.32) - it should also be a zip.
Second 4.4.3 is what I use, so that's quite strange. I'll need complete output to see what the problem is.
Mevordel said:
Hmmm. First make sure you downloaded source for the gingerbread kernel (2.6.35) and not froyo (2.6.32) - it should also be a zip.
Second 4.4.3 is what I use, so that's quite strange. I'll need complete output to see what the problem is.
Click to expand...
Click to collapse
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
stylemate said:
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
Click to expand...
Click to collapse
Do you have the initramfs packed into the rom because Samsung kernels have the initramfs inside them.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Do you have the initramfs packed into the rom because Samsung kernels have the initramfs inside them.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
stylemate said:
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
Click to expand...
Click to collapse
Oh sorry I meant kernel instead of ROM. Hmm why don't you take an initramfs from another source or copy-paste the scripts from your device and add the cwm binaries from entropy's?
Sent from my Nexus 7 using Tapatalk HD
stylemate said:
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
Click to expand...
Click to collapse
stylemate said:
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
Click to expand...
Click to collapse
As far as I know, you didn't do anything wrong. The issue must be somewhere in the init scripts (init.<whatever>, recovery.rc, ueventd.<whatever>). Did you copy those from Entropy's ramdisk too? Which ones?
zaclimon said:
Oh sorry I meant kernel instead of ROM. Hmm why don't you take an initramfs from another source or copy-paste the scripts from your device and add the cwm binaries from entropy's?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I think I'm the only one with korean SGP5 initramfs source.....
anyway, I had a repacking script which doesn't bother with compiling the actual kernel.
I could make a kernel with just CWM recovery and it worked.
But I figured out that I had to compile the actual kernel to add governor or OC stuff... so......
Mevordel said:
As far as I know, you didn't do anything wrong. The issue must be somewhere in the init scripts (init.<whatever>, recovery.rc, ueventd.<whatever>). Did you copy those from Entropy's ramdisk too? Which ones?
Click to expand...
Click to collapse
Ho Thanks for your suggestion. I didn't copy the actual files of those scripts, I looked at his commit and saw those lines changed when he was adding CWM. So I just added or replaced few lines at recovery.rc
Then I copied bunch of files in sbin, which seemed necessary for the recovery.
I copied the clockworkmod image file
Then finally i copied the recovery.fstab
to misc/
I edited recovery.fstab several times to get mount and storage work.
So I think initramfs itself has no problem....... It got me a working kernel with CWM recovery.
But it's the problem when I actually try to compile kernel from the scratch.....
stylemate said:
Ho Thanks for your suggestion. I didn't copy the actual files of those scripts, I looked at his commit and saw those lines changed when he was adding CWM. So I just added or replaced few lines at recovery.rc
Then I copied bunch of files in sbin, which seemed necessary for the recovery.
I copied the clockworkmod image file
Then finally i copied the recovery.fstab
to misc/
I edited recovery.fstab several times to get mount and storage work.
So I think initramfs itself has no problem....... It got me a working kernel with CWM recovery.
But it's the problem when I actually try to compile kernel from the scratch.....
Click to expand...
Click to collapse
When you were just modifying the initramfs, did it boot normally then?
Mevordel said:
When you were just modifying the initramfs, did it boot normally then?
Click to expand...
Click to collapse
yes. very smoothly
I used linaro tool chain 4.6.2 and also arm-eabi-4.7 both worked fine when i just modified the initramfs with a simple script.
stylemate said:
yes. very smoothly
I used linaro tool chain 4.6.2 and also arm-eabi-4.7 both worked fine when i just modified the initramfs with a simple script.
Click to expand...
Click to collapse
Can you boot into CWM and (using adb shell) give me the output of
Code:
cat /proc/cpuinfo
ls -la /
Thanks.
Mevordel said:
Can you boot into CWM and (using adb shell) give me the output of
Code:
cat /proc/cpuinfo
ls -la /
Thanks.
Click to expand...
Click to collapse
Sorry I couldn't do anything because my device was hard bricked and I fixed it today 0.0
Hope you are still around here.
I can't run adb shell with my newly compiled kernel
computer does not detect my device and i tried plugging it in and out several times, killing adb server each time.
interesting thing is that i can't mount USB storage, system, efs or anything else in CWM recovery.
Only cache partition is mounted which is strange. I used same initramfs source for both working kernel and newly compiled kernel,
but i don't know what happened during the compiling process.
I tried compiling with the original intiramfs folder (not modified one) and <3e> recovery also gave me numerous errors like can't mount where, where, where, where.
so there mustn't be a problem in both init.rc-like scripts and ultimately initramfs. It's probably the compiling process and how I set up the compilation.
Do i have to check all lines in venturi_kor_defconfig......?
oh btw, sdcard can be mounted with original ramdisk compiled kernel also, just checked it now.
stylemate said:
Sorry I couldn't do anything because my device was hard bricked and I fixed it today 0.0
Hope you are still around here.
I can't run adb shell with my newly compiled kernel
computer does not detect my device and i tried plugging it in and out several times, killing adb server each time.
interesting thing is that i can't mount USB storage, system, efs or anything else in CWM recovery.
Only cache partition is mounted which is strange. I used same initramfs source for both working kernel and newly compiled kernel,
but i don't know what happened during the compiling process.
I tried compiling with the original intiramfs folder (not modified one) and <3e> recovery also gave me numerous errors like can't mount where, where, where, where.
so there mustn't be a problem in both init.rc-like scripts and ultimately initramfs. It's probably the compiling process and how I set up the compilation.
Do i have to check all lines in venturi_kor_defconfig......?
oh btw, sdcard can be mounted with original ramdisk compiled kernel also, just checked it now.
Click to expand...
Click to collapse
I mean from CWM on your repacked-but-not-compiled kernel -- the one you said worked.
Also, which exactly zip did you download from Samsung's site? You don't need to go through the defconfig as long as you got the right one.
Third, please only compile with 4.4.3 or the one Samsung recommends. Anything newer will probably not work.
Fourth, as to partitions, they are all formatted to RFS, right? And can you run in CWM (where everything mounts and is mounted):
Code:
mount
fdisk -l /dev/block/mmcblk0
Mevordel said:
I mean from CWM on your repacked-but-not-compiled kernel -- the one you said worked.
Also, which exactly zip did you download from Samsung's site?
Third, please only compile with 4.4.3 or the one Samsung recommends. Anything newer will probably not work.
Click to expand...
Click to collapse
1st
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 99.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : SMDKC110
Revision : 0000
Serial : 08c5603ec1690711
-rw-r--r-- 1 system system 118 Dec 25 12:19 default.prop
drwxr-xr-x 9 root root 2840 Jan 23 01:26 dev
drwxrwxr-x 1 radio system 0 Jan 23 01:26 efs
drwxr-xr-x 2 root root 0 Jan 23 01:26 emmc
lrwxrwxrwx 1 root root 11 Jan 23 01:26 etc -> /system/etc
-rwxr-xr-x 1 system system 1876 Dec 25 12:19 fota.rc
-rwxr-xr-x 1 system system 168364 Dec 25 12:27 init
-rw-r--r-- 1 system system 1677 Dec 25 12:19 init.goldfish.rc
-rwxr-xr-x 1 system system 30941 Dec 28 08:32 init.rc
-rwxr-xr-x 1 system system 30931 Dec 25 17:46 init.rc~
-rwxr-xr-x 1 system system 4489 Dec 25 12:19 init.smdkc110.rc
drwxr-xr-x 3 system system 0 Dec 25 12:19 lib
-rwxr-xr-x 1 system system 1419 Dec 25 12:19 lpm.rc
drwx------ 2 system system 0 Dec 26 16:21 misc
drwxrwxr-x 3 root root 0 Jan 23 01:26 mnt
drwxr-xr-x 2 root root 0 Jan 23 01:26 preload
dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 system system 410344 Dec 25 12:19 recovery
-rw-r--r-- 1 system system 2182 Dec 25 12:39 recovery.rc
drwxr-xr-x 3 system system 0 Dec 25 12:40 res
drwxr-xr-x 2 system system 0 Dec 26 16:31 sbin
drwxr-xr-x 2 root root 0 Jan 23 01:26 sdcard
drwxr-xr-x 12 root root 0 Jan 23 01:26 sys
drwxr-xr-x 1 root root 0 Jan 23 01:26 system
drwxrwxrwt 2 root root 60 Jan 23 01:26 tmp
-rw-r--r-- 1 system system 0 Dec 25 12:19 ueventd.goldfish.rc
-rw-r--r-- 1 system system 4245 Dec 25 12:19 ueventd.rc
-rwxr-xr-x 1 system system 1749 Dec 25 12:19 ueventd.smdkc110.rc
drwxrwxr-x 3 system system 0 Dec 28 08:33 vendor
init.rc~ file is the autocreated backup file that i forgot to erase
2nd
I downloaded YP-GB70-WW GB Opensource.zip
3rd
Yes I've been using the right toolchain that the readme file specified.
I have tried 4.4.3 too and many other toolchains.
4th
{
"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"
}
it's very normal... I had to fix this part of partition cause my partition was messed up beginning from block 12 but now it's perfect.
picture stolen from Siraki......
stylemate said:
1st
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 99.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : SMDKC110
Revision : 0000
Serial : 08c5603ec1690711
-rw-r--r-- 1 system system 118 Dec 25 12:19 default.prop
drwxr-xr-x 9 root root 2840 Jan 23 01:26 dev
drwxrwxr-x 1 radio system 0 Jan 23 01:26 efs
drwxr-xr-x 2 root root 0 Jan 23 01:26 emmc
lrwxrwxrwx 1 root root 11 Jan 23 01:26 etc -> /system/etc
-rwxr-xr-x 1 system system 1876 Dec 25 12:19 fota.rc
-rwxr-xr-x 1 system system 168364 Dec 25 12:27 init
-rw-r--r-- 1 system system 1677 Dec 25 12:19 init.goldfish.rc
-rwxr-xr-x 1 system system 30941 Dec 28 08:32 init.rc
-rwxr-xr-x 1 system system 30931 Dec 25 17:46 init.rc~
-rwxr-xr-x 1 system system 4489 Dec 25 12:19 init.smdkc110.rc
drwxr-xr-x 3 system system 0 Dec 25 12:19 lib
-rwxr-xr-x 1 system system 1419 Dec 25 12:19 lpm.rc
drwx------ 2 system system 0 Dec 26 16:21 misc
drwxrwxr-x 3 root root 0 Jan 23 01:26 mnt
drwxr-xr-x 2 root root 0 Jan 23 01:26 preload
dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 system system 410344 Dec 25 12:19 recovery
-rw-r--r-- 1 system system 2182 Dec 25 12:39 recovery.rc
drwxr-xr-x 3 system system 0 Dec 25 12:40 res
drwxr-xr-x 2 system system 0 Dec 26 16:31 sbin
drwxr-xr-x 2 root root 0 Jan 23 01:26 sdcard
drwxr-xr-x 12 root root 0 Jan 23 01:26 sys
drwxr-xr-x 1 root root 0 Jan 23 01:26 system
drwxrwxrwt 2 root root 60 Jan 23 01:26 tmp
-rw-r--r-- 1 system system 0 Dec 25 12:19 ueventd.goldfish.rc
-rw-r--r-- 1 system system 4245 Dec 25 12:19 ueventd.rc
-rwxr-xr-x 1 system system 1749 Dec 25 12:19 ueventd.smdkc110.rc
drwxrwxr-x 3 system system 0 Dec 28 08:33 vendor
init.rc~ file is the autocreated backup file that i forgot to erase
2nd
I downloaded YP-GB70-WW GB Opensource.zip
3rd
Yes I've been using the right toolchain that the readme file specified.
I have tried 4.4.3 too and many other toolchains.
Click to expand...
Click to collapse
Thanks. I edited my post after you quoted it. But from what you posted, everything looks in order. (A minor OCD is that you should delete init.rc~, but it shouldn't make a difference.)
It's somewhat a hunch, but try downloading the "YP-G1 US" source and compiling it with venturi_kor_defconfig,
And I'm not sure, as I don't have any of the Korean devices, but isn't there a difference between YP-G70 and YP-GB70? If so, then venturi may not even be the right config.
Mevordel said:
Thanks. I edited my post after you quoted it. But from what you posted, everything looks in order. (A minor OCD is that you should delete init.rc~, but it shouldn't make a difference.)
It's somewhat a hunch, but try downloading the "YP-G1 US" source and compiling it with venturi_kor_defconfig,
And I'm not sure, as I don't have any of the Korean devices, but isn't there a difference between YP-G70 and YP-GB70? If so, then venturi may not even be the right config.
Click to expand...
Click to collapse
DMB function and Camera is the major and maybe the only difference. But That doesn't really matter.
As long as i get bootable kernel I will be fine with it. Haha
Thank you, I will try with YP-G70 later.
Is it possible to dual-boot on the Evo 3D? I have tried Boot Manager and it fails to download all the data and BootStrap won't work either...it says installed but does nothing beyond that
What do you mean that it failed to download all the data? I successfully used boat manager on my 3vo.
I did however have to get the paid version. For whatever reason, the free version wouldn't install.
Also, I know development stopped on boot manager awhile back. You can't install jellybean roms in the alternate rom slots; only as your main rom... Also, you can't install a rom that uses the aroma installer.
I'm looking into a new method of dual booting on the Evo 3d using kexec
Sent from my PG86100 using Tapatalk
Brian706 said:
What do you mean that it failed to download all the data? I successfully used boat manager on my 3vo.
I did however have to get the paid version. For whatever reason, the free version wouldn't install.
Also, I know development stopped on boot manager awhile back. You can't install jellybean roms in the alternate rom slots; only as your main rom... Also, you can't install a rom that uses the aroma installer.
Click to expand...
Click to collapse
Okay, I guess i'll have to get the paid version....i'll find an APK of it that way i don't "waste" money on something I may not keep or not like or I can't get to work. What I was wanting to do is have a Custom ROM as the Main ROM and a "Stock" ROM as the secondary one...that way I can use something like LiquidSmooth as primary and keep a "stock" ROM (or variant of it) for editing PRL and having Sense UI)
EDIT: I tried installing the Pro Version and it STILL throws up an "error downloading files" message
So is this after it's installed? When you're going through the setup?
Sorry, it's been awhile since I've gone through this... I never had any errors like that though.
This is about all I could find on that error: http://forum.xda-developers.com/showthread.php?p=22716341&postcount=132
Brian706 said:
So is this after it's installed? When you're going through the setup?
Sorry, it's been awhile since I've gone through this... I never had any errors like that though.
This is about all I could find on that error: http://forum.xda-developers.com/showthread.php?p=22716341&postcount=132
Click to expand...
Click to collapse
Yes, it errors after the APK install, when it says "loading" up top....the bar moves to about halfway and then shoots to the end then it says error downloading files......
I wonder if they have issues with wherever the files are downloading from? I'll have to get on my evo tomorrow and see if I get the same issue. The app hasn't been supported for a pretty long time now, so it may just be that they didn't maintain something server side or whatever.
the pro version has win-init server check for key.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
jcfunk said:
the pro version has win-init server check for key.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
I guess that explains why its so hard to find an APK for it...well, I refuse to pay for an app that I am not sure if it will work for me or not....I tried SafeStrap and it didn't work and its free.....
the free version should work
https://play.google.com/store/apps/details?id=com.drx2.bootmanager.lite
Sent from my PG86100 using Tapatalk
The free version may work for you. I should have clarified. The free version wouldn't install from the play store for me (for whatever reason) so I bought the pro version which installed.
Not that you are, but earlier I mentioned not being able to install a rom that uses aroma installer... That's only half true. You can't install the rom through rom manager, but if you install it normally and make a nandroid backup, you can then restore the backup to a rom slot in boot manager.
I retried, I've deleted the bootmanager folder from sdcard, need to backs of sdcard for files. Will post if I find,
Sent from my PG86100 using Tapatalk
Here is the data files for lite version, but files are same for pro without key file. Just put into /data/data
bootmanager data files
Sent from my PG86100 using Tapatalk
jcfunk said:
the free version should work
https://play.google.com/store/apps/details?id=com.drx2.bootmanager.lite
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It doesn't work, that was the original issue, it would get like 1/3rd downloaded and the download bar would shoot across the screen and say "Error downloading files"
Dvdxploitr said:
It doesn't work, that was the original issue, it would get like 1/3rd downloaded and the download bar would shoot across the screen and say "Error downloading files"
Click to expand...
Click to collapse
Did you download the files in his next post? He uploaded his boot manager folder.
Brian706 said:
Did you download the files in his next post? He uploaded his boot manager folder.
Click to expand...
Click to collapse
Yea, i tried those files too.....still says "error downloading data"...it acts like its not even there
Dvdxploitr said:
Yea, i tried those files too.....still says "error downloading data"...it acts like its not even there
Click to expand...
Click to collapse
those file go into /data/data .
the folder in the zip is for lite version, if you copy contents of com.drx2.bootmanager.lite to com.drx2.bootmanager then you should not need to download. I just used the lite version as to not pass licence key.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
jcfunk said:
those file go into /data/data .
the folder in the zip is for lite version, if you copy contents of com.drx2.bootmanager.lite to com.drx2.bootmanager then you should not need to download. I just used the lite version as to not pass licence key.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Well, I don't know whats wrong. I have copied that directory to SEVERAL places on my phone and STILL get the error message....I copied it to the root directory, data directory data/data directory, boot manager directory.....i renamed it from com.drx2.bootmanager.lite to com.drx2.bootmanager and put it in various places.....
Here's my log:
Current Version Boot Manager V1.5
extracting assets
getting files
/data/data/com.drx2.bootmanager.lite/files/busybox
/data/data/com.drx2.bootmanager.lite/files/message
/data/data/com.drx2.bootmanager.lite/files/message
/data/data/com.drx2.bootmanager.lite/files/dump_image
/data/data/com.drx2.bootmanager.lite/files/erase_image
/data/data/com.drx2.bootmanager.lite/files/flash_image
/data/data/com.drx2.bootmanager.lite/files/reboot
/data/data/com.drx2.bootmanager.lite/files/mke2fs
/data/data/com.drx2.bootmanager.lite/files/morebinarys/mke2fs
/data/data/com.drx2.bootmanager.lite/files/morebinarys/busybox
/data/data/com.drx2.bootmanager.lite/files/morebinarys/flash_image
/data/data/com.drx2.bootmanager.lite/files/morebinarys/dump_image
/data/data/com.drx2.bootmanager.lite/files/zip
/data/data/com.drx2.bootmanager.lite/files/unyaffs
/data/data/com.drx2.bootmanager.lite/files/e2fsck
/data/data/com.drx2.bootmanager.lite/files/unpackbootimg
/data/data/com.drx2.bootmanager.lite/files/mkbootimg
/data/data/com.drx2.bootmanager.lite/files/resize2fs
Binary files downloaded and checked
sh: <stdin>[1]: /data/data/com.drx2.bootmanager.lite/files/command.sh: No such file or directory
java.io.FileNotFoundException: /data/local/tmp/edit.sh: open failed: EACCES (Permission denied)
Jcfunk, what permissions does the folder have? It's possible that when he is pasting it in /data/data that the permissions aren't correct.
I assume they would need to be rw-r--r--
But I'm not 100% sure on that.
Code:
sh-4.3# ls -lhR /data/data/com.drx2.bootmanager.lite/
/data/data/com.drx2.bootmanager.lite/:
drwxrwx--x 2 10107 10107 4.0K May 19 10:30 cachedrwxrwx--x 3 10107 10107 4.0K May 22 01:10 filesdrwxr-xr-x 2 1000 1000 4.0K May 19 10:29 lib
drwxrwx--x 2 10107 10107 4.0K May 21 23:38 shared_prefs
/data/data/com.drx2.bootmanager.lite/cache:
/data/data/com.drx2.bootmanager.lite/files: -rwxrwx--x 1 10107 10107 5.3K Jan 5 19:10 bootmanagerSS -rwxrwxrwx 1 0 0 1.0M May 22 01:09 busybox -rwxrwx--x 1 10107 10107 189 Jan 5 19:10 command.sh -rwxrwx--x 1 0 0 13.6K Jan 5 19:10 dump_image -rwxrwx--x 1 0 0 108.9K Jan 5 19:10 e2fsck -rwxrwx--x 1 0 0 9.5K Jan 5 19:10 erase_image -rwxrwx--x 1 10107 10107 14.6K Jan 5 19:10 fix_permissions -rwxrwx--x 1 0 0 13.6K Jan 5 19:10 flash_image -rwxrwx--x 1 0 0 62.4K Jan 5 19:10 mkbootimg
-rwxrwx--x 1 0 0 34.0K Jan 5 19:10 mke2fs
drwxr-xr-x 2 10107 10107 4.0K May 22 01:09 morebinarys
-rwxrwx--x 1 0 0 5.4K Jan 5 19:10 reboot
-rwxrwx--x 1 0 0 21.7K Jan 5 19:10 resize2fs
-rw------- 1 10107 10107 330 May 22 01:09 tmpmes
-rwxr-xr-x 1 10107 10107 330 May 20 14:14 tmpmessage
-rwxrwx--x 1 0 0 57.4K Jan 5 19:10 unpackbootimg
-rwxrwx--x 1 0 0 5.5K Jan 5 19:10 unyaffs
-rwxrwx--x 1 10107 10107 236.3K Jan 5 19:10 wget
-rwxrwx--x 1 0 0 803.5K Jan 5 19:10 zip
-rwxrwx--x 1 10107 10107 2.4K Jan 5 19:10 zipalign
/data/data/com.drx2.bootmanager.lite/files/morebinarys:
-rwxrwx--x 1 0 0 718.1K May 22 01:09 busybox
-rwxrwx--x 1 0 0 13.6K Jan 5 19:10 dump_image
-rwxrwx--x 1 0 0 13.6K Jan 5 19:10 flash_image
-rwxrwx--x 1 0 0 29.9K Jan 5 19:10 mke2fs
/data/data/com.drx2.bootmanager.lite/lib:
/data/data/com.drx2.bootmanager.lite/shared_prefs:
-rw-rw---- 1 10107 10107 568 May 21 23:38 DeviceInfo.xml
sh-4.3#
Sent from my PG86100 using Tapatalk
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
craftsvision said:
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
Click to expand...
Click to collapse
here´s the patition table, if it is of any use for you...
lrwxrwxrwx 1 root root 16 Jan 1 00:12 aboot -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Jan 1 00:12 abootbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Jan 1 00:12 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 Jan 1 00:12 bluetooth -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 Jan 1 00:12 boot -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Jan 1 00:12 bootconfig -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64 -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64bak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlibbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfg -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfgbak -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Jan 1 00:12 devinfo -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dpo -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dsp -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Jan 1 00:12 factory -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 frp -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg_gap -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Jan 1 00:12 kernellog -> /dev/block/sdf14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymaster -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymasterbak -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Jan 1 00:12 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvconfig -> /dev/block/sdf10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letveui -> /dev/block/sdf11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvreserve -> /dev/block/sdf13
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvsecure -> /dev/block/sdf12
lrwxrwxrwx 1 root root 16 Jan 1 00:12 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Jan 1 00:12 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 modem -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1_gap -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2_gap -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 Jan 1 00:12 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmic -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmicbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 recovery -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Jan 1 00:12 recoveryconfig -> /dev/block/sdf9
lrwxrwxrwx 1 root root 15 Jan 1 00:12 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rootconfig -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 sec -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Jan 1 00:12 splash -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Jan 1 00:12 sti -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 Jan 1 00:12 system -> /dev/block/sde19cmd
lrwxrwxrwx 1 root root 15 Jan 1 00:12 xblbak -> /dev/block/sdc1
never blank partitions if you don´t have a backup anywhere, meaning: not part of qfil, stockrom customrom (zip or fastboot), not pulled from the/a phone(x820/29)
i would pull any single partitiom first (that are not part of roms etc.) and save it, you shoud be safe to restore the phone to the condidtion as it is now at least.
if you think one of theese could cause the problem, be sure to get the partition images from a working phone before you erase those!
also, backup your efs/qcn!
from what you tell it sounds like a harrdware fault but try! i would also try everything, had success the last time.
it bet it´s a x829, isn´t it?
i have some spare time the rest of the week and already helpded some xda users remotely. if you want i could (try) to help you too.
i´m an it guy, so this is my nature.
good luck
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
craftsvision said:
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
Click to expand...
Click to collapse
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
A.N.Droid said:
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
Click to expand...
Click to collapse
It would be really helpful of you make a video about the complete fix. I have a x821 in which I forgot to remove encryption before flashing a custom ROM and now in twrp there is a system image partition which is 4GB in size and is non accessible. I want to delete that but being inaccessible I an unable to do so.
Can you guide me on how to do that? Can you at least give me the step by step procedure to fix this issue?
Thanks in advance.
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
azzammalik said:
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
Click to expand...
Click to collapse
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Thanks a lot brother
ThE_MarD said:
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Click to expand...
Click to collapse
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
azzammalik said:
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
Click to expand...
Click to collapse
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
ThE_MarD said:
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
Click to expand...
Click to collapse
Hey,
I am here after 12 hours of usage.
Yes, I am using twrp 3.2.1-2.First flashed 30s firmware then flashed rom and gapps which you recommended and then magisk.
And to my amazement I had only 3 fcs right now which are too less then which I have faced before.
Also didn't reboot once in 12 hours but suddenly got 2 reboots in quick succession.
But still it's a lot more usable now as a daily driver for me just because of ya. Maybe problem will come back in a day or two as that happened before too.
But until then it's all OK for now.
A big thanks to you. .
Have a good day ahead
Cheers
Update: not even a single reboot or fc even after installing system less xposed. NO WORDS FOR YA. A BIG THANKYOU
2nd Update: 2nd day of usage. No more fcs. Single reboot. Perfect now.