hey,guys..
i confront a problem
1. when i flash anything contain ( mount /system), the phone will reboot immediately when the script run at the line ( mount /system)
2. when i use rootexplorer copy or move anything to the /system ( rw), it also reboot immediately and when reboot into os ,it wiped the file i copied
os: sense 4.2.2 | stock kernel
ps: already try flash boot.img via fastboot and erase cache
has any one know how-to , thks in adv..:crying:
Related
can somebody please tell me how to setup a custom 145mb mtd, so that I can try the new ics build. I have the right spl and radio. thank u guys so much!
edit... moderator please delete thread, i got it working...
You need to set up a file called "mtdpartmap.txt" must be located in the root of the /sdcard directory and which contains the following line:
mtd 145 2
Then reboot into recovery and flash Firerat's fr_recovery-xxx.zip, reboot into recovery and use Ohsakas Superwipe or reboot into fastboot mode and enter
fastboot erase system -w
Now reboot into recovery again and you have the new partition map installed.
AndDiSa said:
You need to set up a file called "mtdpartmap.txt" must be located in the root of the /sdcard directory and which contains the following line:
mtd 145 2
Then reboot into recovery and flash Firerat's fr_recovery-xxx.zip, reboot into recovery and use Ohsakas Superwipe or reboot into fastboot mode and enter
fastboot erase system -w
Now reboot into recovery again and you have the new partition map installed.
Click to expand...
Click to collapse
thank u my friend. got it working. by the way, love adsmagpie.
whenever i go into recovery mode i get an error on the bottom of the screem
BUILD : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No Space left on device)
i cant nand backup or anything
rickyiswhite said:
whenever i go into recovery mode i get an error on the bottom of the screem
BUILD : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No Space left on device)
i cant nand backup or anything
Click to expand...
Click to collapse
There are two possibilities:
1) The log is occupiing really the whole space on cache. In that case try to remove the log file from cache directory
2) Did you mess up with custom partion tables? To me this happened some time ago when I forgot to flash fr_boot_xxx.zip onto a boot.img while having installed custom partitions. In that case you have to clean everything. Eventually you need also to flash recovery again. If you have a recent backup, you can try to do a
fastboot erase system -w
then boot into recovery and see, if everything works for you again. If not you need to flash a new recovery:
fastboot flash recovery recovery.img
After that everything should work again, i.e. you can install your backup or you can install a new ROM.
AndDiSa said:
There are two possibilities:
1) The log is occupiing really the whole space on cache. In that case try to remove the log file from cache directory
2) Did you mess up with custom partion tables? To me this happened some time ago when I forgot to flash fr_boot_xxx.zip onto a boot.img while having installed custom partitions. In that case you have to clean everything. Eventually you need also to flash recovery again. If you have a recent backup, you can try to do a
fastboot erase system -w
then boot into recovery and see, if everything works for you again. If not you need to flash a new recovery:
fastboot flash recovery recovery.img
After that everything should work again, i.e. you can install your backup or you can install a new ROM.
Click to expand...
Click to collapse
hmm ok ill try that... thanks... and sometimes it says cant open cache or something
Am sorry if am Making this Guide in the Wrong section..
NOTE:
AM not responsible for any data lose or Result in brick etc..
.
Do Charge your device 100%
Have a Copy of Stock image to revert back to stock if something goes wrong, or a nandroid backup...
Steps To follow for Rooted users:
Use Nexus Tool kit to flash Stock Kernel and Recovery... ( you will lose your Root cos of this )
Download and extract Stock Factory image of 4.4 and edit flash-all.bat ( Remove "-w" and save it )
Copy the Extracted files into Fastbood Folder
Now Boot your device into Bootloader ( adb reboot-bootloader )
Now execute Flash-all.bat
Your device will be flashed back to stock without wiping your data or user files... Settings Apps will be intact.
Once device boots up, Reboot into Recovery Mode ( Stock Recovery )
Use Volume button to select "apply update from ADB"
Now Open Fastboot and type in " adb sideload xxxx.zip " ( xxxx denotes your 4.4.2 or 4.4.1 file name ) ( type without " " )
Once done wipe cache and reboot...
You are now on Android 4.4.2
Download links:
Nexus 4 Stock 4.4
Update from 4.4 to 4.4.2
Update:
Am Attaching flash-all.bat modified here,
users who are not able to edit flash-all.bat, can download the attachment and replace it with stock flash-all.bat
Hi,
I have got Galaxy SL GT-i9003. The problem is the /data partition can't be mounted. I have already flash stock rom + pit, but it doesn't solve the problem.
Now is there any HACK I can use to fix it ? right now I am stuck in bootlooping on GB and Encryption unsuccessfull on ICS [EHNDROIX] ROM.
Any Help is Really Appreciated. Thanks.
yokowasis said:
Hi,
I have got Galaxy SL GT-i9003. The problem is the /data partition can't be mounted. I have already flash stock rom + pit, but it doesn't solve the problem.
Now is there any HACK I can use to fix it ? right now I am stuck in bootlooping on GB and Encryption unsuccessfull on ICS [EHNDROIX] ROM.
Any Help is Really Appreciated. Thanks.
Click to expand...
Click to collapse
Greetings;
I don't know if you've solved your problem.
But i'll leave some tips.
First of all i want to mention that:
I also came from an ehndroix ICS Rom when i got that problem.
"emmc" Stands for external SDCard
"sdcard" Stands for Internal "SDCard"
Note: "sdcard" it's not an SDCard. This is the device internal storage with a little bit more than 1.5GB.
If you need to fix the emmc (the "real" external SDCard) you can download and install an application that (usually fixes many SDCard problems and size issues)
Application Name: "SDCard Formater"
Download Link: www.sdcard.org
Also know that most custom roms will resize your partitions; wich usually cause that error.
The common fix for your partition problems is to make a clean install.
For a clean install:
1) Remove SD Card
Note: Remove if you have important data there; or leave it if you will flash a ROM from there.
2.1) If you have CWM Recovery on your Device:
Reboot your device in CWM Recovery Mode.
Select: "Advanced" and Erase Dalvik Cache.
Go back and Select: "Mounts and Storage"
And Format:
- Data
- System
- Boot
- Cache
2.2) If you don't have CWM Recovery:
- Flash DDLF2 Full or Stock Firmware from sammmobile.com
- DDLF2 Full Link: http://forum.xda-developers.com/showthread.php?t=2329200
- Flash CF-Root (wich Contains CWM and Roots the Device)
- Reboot your device in CWM Recovery Mode.
Select: "Advanced" and Erase Dalvik Cache.
Go back and Select: "Mounts and Storage"
And Format:
- Data
- System
- Boot
- Cache
After that Power Off your device and boot into download mode.
Open Odin; plug the USB Cable; select the files in Odin (note that last 2 files are switched - Modem and CSC)
Press start; and wait untill Odin says "Pass".
Note that 1st boot takes longer.
Also do not remove the cable utill Odin says "Pass"
My device will restart 1 time for each Rom and CF-Root Flash and only then Odin will show the "Pass" message.
I'm not aware of any hacks.
But If there's a way to do it manually for this device (like in previous android devices) then it would be loading into a pseudo "bootloader Mode" wich i think it doesnt exist on this device.
If it does... The steps would be (briefly) Downloading android SDK; locate the folder wich contains adb.exe and fastboot.exe.
Copy | Paste that folder to an easier path to access it through terminal | command prompt.
"adb" will allow you to show all your partitions
"Fastboot" will allow you to erase|format partitions.
But like i said. I tried to do that on my device but without luck. Even with Vendor ID the device wont let me use fastboot.
My solution went to make clean installs.
Please press thanks if i helped you.
This will motivate me into researching more; provide more help; make some applets; tutorials and some more.
@yokowasis You have posted in the i9000 section. Best delete the text from this post and post it in some Galaxy SL thread.
tetakpatalked from Nexus 7 flo
I was using TWRP 3.0.0 and AOSP Android 7.1 uptil last week.
Last week, I flashed TWRP twrp-3.2.1-0-s2.img and ROM: AOSP Extended : https://forum.xda-developers.com/le-2/development/rom-aospextended-rom-v6-0-t3841473
Guide Followed While Flashing TWRP and Magisk: https://www.guidingtech.com/59895/le...-installation/
Problem: Everything was fine until I tried Downloading an apk using chrome and it couldn't find storage/emulated/0 and none of the apps were able to access storage..
So I fired up ADB and $ adb shell gave me a list of folders with no storage folder.
~ # ls boot init.recovery.service.rc selinux_version cache init.recovery.usb.rc sepolicy charger license service_contexts data oem sideload default.prop persist supersu dev proc sys dsp property_contexts system etc recovery tmp file_contexts res twres firmware root ueventd.rc init sbin usbstorage init.rc sdcard init.recovery.hlthchrg.rc seapp_contexts
I realised I had no /storage/emulated/0 folder.
I tried reflashing the rom, it didn't make a difference. I tried flashing a different ROM, no result.
I tried to open the folder sdcard, it says 'sdcard' is not mounted.
I tried mounting it using adb but it didn't work. I tried symlinking storage/emulated/0 to sdcard, no results.
How to I get my sdcard back/mount it?
I tried format data from TWRP. I tried flashing this kernel too: https://forum.xda-developers.com/le-2/development/project-illusionkernel-v1-0-t3677897
I tried other roms and twrp versions..
The internal sdcard just won't mount.
Any ideas on how to mount it manually using adb or something?
You can try this twrp-3.2.1-1-codeworkx-s2.img from
https://forum.xda-developers.com/le-...o-le2-t3541959
- wipe -> format data
- advance wipe these 4 dalvik, cache, system and data
- flash your rom of choice
- flash gapps
- reboot
solution
IDK what the issue was but it got resolved by flashing Graphene Kernel.
Here's what I did:
adb reboot bootloader
adb reboot bootloader fastboot oem unlock
fastboot oem unlock-go fastboot flash recovery twrp-3.2.1-0-s2.img fastboot format userdata
Flashed the ROM.
Fasjed Gapps
Flashed MAgisk.
Reboot Phone.
Flashed : https://forum.xda-developers.com/le-2/development/project-illusionkernel-v1-0-t3677897